Some concerns about nginx module

Hi Team, for the nginx instrumentation, i met some problems recently.
for my nginx.conf config:

location / {
        opentelemetry_operation_name $uri;
        opentelemetry_propagate;

       ……

because my app has some urls which contains regex: such as /a/b/{c:[0-9]+}, so i found in my jaeger UI, there are so many operations which may exceed the threshold. So I wonder whether any good suggestions for location aggregation? And do i need to add each location which contains regex? o(╥﹏╥)o

The report only identifies an nginx.conf location block and Jaeger UI as the investigation points; start by reviewing how nginx instrumentation derives operation names for regex locations. Determine whether location aggregation can be configured and whether each regex location must be declared, then document the supported behavior or a concrete change request.