Describe the bug
I'm working on a Proof of Concept (PoC) that involves full tracing from the edge (using Spring Cloud Gateway) through to downstream Spring Boot services. When viewing traces in Jaeger, I noticed a discrepancy in the span names:
For Spring Boot services, the span names include the full request path (e.g., GET /serviceA/user).
For Spring Cloud Gateway, the span names only show the route ID (e.g., GET {route.id}) rather than the full path.
Expected behavior I would expect span names in Spring Cloud Gateway to display the full request path (similar to the format used in Spring Boot services) for consistency in trace visualization.
Describe the bug I'm working on a Proof of Concept (PoC) that involves full tracing from the edge (using Spring Cloud Gateway) through to downstream Spring Boot services. When viewing traces in Jaeger, I noticed a discrepancy in the span names:
For Spring Boot services, the span names include the full request path (e.g., GET /serviceA/user).
For Spring Cloud Gateway, the span names only show the route ID (e.g., GET {route.id}) rather than the full path.
Expected behavior I would expect span names in Spring Cloud Gateway to display the full request path (similar to the format used in Spring Boot services) for consistency in trace visualization.