Incorrect trace name and trace group when instrumenting Spring Cloud Gateway using automatic java agent

[wwwlll2001]

**Describe the bug** For I now I adopt open telemetry agent of java to instrument my system which architecture is micro-service including a api-gateway which is built with Spring Cloud Gateway.

For the tracing architecture, it‘s open telemetry agent + otel-collector + data-prepper + opensearch trace analytics, so far i could got the tracing view on my opensearch, it works fine.

The bug(maybe it's not) is that all the name of the trace of Spring Cloud Gateway is /, so that it's hard for me to differentiate those multiple traces which have different request url so that I can not perform further analysis. After long time digging, I suspect it's somehow related with Netty, as when I instrumenting a normal spring boot service, the name is correct which is the request url, but when I instrumenting spring cloud gateway the trace name will be / or /**, this is what I found for now.

I hope the trace name of spring cloud gateway could be the same as other normal spring boot service which is not based on Netty

Steps to reproduce using opentelemetry java agent to launch spring cloud gateway service , then the trace name will be /* or /**

What did you expect to see? I hope the trace name of spring cloud gateway could be the same as other normal spring boot service which is not based on Netty

What did you see instead? all the name of the trace of Spring Cloud Gateway is /* or /**

What version are you using? opentelemetry-javaagent - version: 1.10.1

Environment

Additional context