spring-cloud / spring-cloud/spring-cloud-gateway
Routing latency collection
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
GatewayMetricsFilter has collect the total latency of a request. We want to collect the latency of the API provider server. NettyRoutingFilter doesn't collect the routing latency. Adding the corresponding latency collect feature in NettyRoutingFilter and then put as an attribute to ServerWebExchange. Then we cat get the routing latency.
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
Start by comparing how GatewayMetricsFilter collects total request latency with NettyRoutingFilter, then inspect how ServerWebExchange attributes are used. Add routing-latency collection to NettyRoutingFilter and expose it through ServerWebExchange so callers can retrieve it; verify that the provider-server routing latency is available separately from total latency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100