oncefalse opened a new issue, #13215: URL: https://github.com/apache/skywalking/issues/13215
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened When using @RequestMapping({"/user", "/account"}) in a Spring application, I noticed that the generated Span name in SkyWalking always uses the first defined path (”/user”), regardless of the actual request path. For example, when accessing /account, the Span name still shows /user, which is misleading. ### What you expected to happen The Span name should accurately reflect the real request path (/account in this case), not just default to the first declared path. This is important for correctly tracing and analyzing real user requests. ### How to reproduce 1. In a Spring Boot application, create a controller like: `@RequestMapping({"/user", "/account"}) public String handleRequest() { return "ok"; }` 2. Start the application with SkyWalking agent attached. 3. Send an HTTP request to /account. 4. Observe the trace in SkyWalking UI: the Span name will incorrectly show /user instead of /account. ### Anything else This issue occurs because the current Spring plugin in SkyWalking captures the mapping value statically, rather than detecting the actual matched request path at runtime. • A possible fix might involve accessing the HttpServletRequest during tracing to get the getRequestURI() or similar dynamic path. • This affects trace accuracy when a controller handles multiple paths. ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
