Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trace/Span name for downstream services #3590

Open
adamalexandru4 opened this issue Nov 12, 2024 · 0 comments
Open

Trace/Span name for downstream services #3590

adamalexandru4 opened this issue Nov 12, 2024 · 0 comments

Comments

@adamalexandru4
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant