spring-cloud / spring-cloud/spring-cloud-gateway
Trace/Span name for downstream services
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the Spring Cloud Gateway flow from the reported PoC with Jaeger, then trace where gateway span names are assigned and compare them with Spring Boot downstream spans. Done means gateway spans consistently show the full request path instead of only the route ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100