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

Expose x-envoy-upstream-service-time as a metric #37129

Open
jwestbury opened this issue Nov 13, 2024 · 0 comments · May be fixed by #37467
Open

Expose x-envoy-upstream-service-time as a metric #37129

jwestbury opened this issue Nov 13, 2024 · 0 comments · May be fixed by #37467
Labels
area/stats enhancement Feature requests. Not bugs or questions. help wanted Needs help!

Comments

@jwestbury
Copy link

Title: Expose x-envoy-upstream-service-time as a metric

Description:

I want to be able to attribute latency to each portion of my network. Whilst I have tracing data which may enable me to do this, it would be much easier if I had access to the data from the X-Envoy-Upstream-Service-Time header available as a metric. I have not been able to determine a way to calculate this with the existing exposed metrics.

[optional Relevant Links:]

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/router_filter#x-envoy-upstream-service-time

@jwestbury jwestbury added enhancement Feature requests. Not bugs or questions. triage Issue requires triage labels Nov 13, 2024
@yanavlasov yanavlasov added question Questions that are neither investigations, bugs, nor enhancements enhancement Feature requests. Not bugs or questions. help wanted Needs help! area/stats and removed enhancement Feature requests. Not bugs or questions. triage Issue requires triage question Questions that are neither investigations, bugs, nor enhancements labels Nov 13, 2024
@agrawroh agrawroh linked a pull request Dec 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/stats enhancement Feature requests. Not bugs or questions. help wanted Needs help!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants