Prometheus server latency metrics no longer provide labels per service and method
See original GitHub issueWe recently upgraded a service from v0.14.1
to v0.18.4
. In the old version there was a way to opt in to latency metrics with labels per service and method. I may be missing something, but I’m not seeing a mechanism provided that would allow for the same sort of per-endpoint latency metrics. If that is the case, is there maybe a reason those were removed that I might be missing? And if there is no reason, would anyone be opposed to adding something back in? I would be happy to submit a PR if there are no objections to the idea.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Instrumentation - Prometheus.io
The key metrics for a cache are total queries, hits, overall latency and then the query count, errors and latency of whatever online-serving...
Read more >Document prometheus metrics · Issue #2924 - GitHub
It's just that special care has to be taken, that not all metrics have all label combinations. This will lead to DoS of...
Read more >Prometheus Metrics: Types, Capabilities, and Best Practices
Prometheus stores all metric data in a time-series format while implementing a multidimensional data model with metric names and key-value ...
Read more >How relabeling in Prometheus works | Grafana Labs
But what about metrics with no labels? Prometheus also provides some internal labels for us. These begin with two underscores and are ...
Read more >Prometheus Metrics, Implementing your Application - Sysdig
Sysdig Monitor supports Prometheus metrics out of the box. ... and the labels service="service" , server="pod50″ and env="production" could ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@tyler-clark maybe we can keep the default builder and add a new one for specifying that param. I’m ok with breaking binary compatibility and release a new minor version though but I think a different builder could be enough.
@fedefernandez That seems reasonable enough to me, but that would break binary compatibility, wouldn’t it? Maybe not a huge deal as it would just mean a new minor version at this point. Thoughts?