configurable prometheus metrics path
See original GitHub issuemake prometheus metrics path configurable, allowing users to standardize on prometheus metrics paths across all services in a cluster.
it’s currently hard coded at /admin/metrics/prometheus
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Configuration - Prometheus.io
An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.
Read more >Different Prometheus scrape URL for every target
You currently can't configure the metrics_path per target within a job but you can create separate jobs for each of your targets so...
Read more >How to use Prometheus for metrics - Light
The metrics_path is configurable. In light-codegen, we set it as /prometheus, but it can be change to any url user want. Then user...
Read more >Prometheus Metrics | Boundary - HashiCorp Developer
Metrics are available for controllers and workers in a Boundary deployment. To quickly view metrics data, you will first use Boundary's dev mode...
Read more >Support custom path for Prometheus metrics #3800 - GitHub
Currently the Prometheus source assumes Prometheus metrics to always be exposed on the given endpoint under a path metrics .
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 FreeTop 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
Top GitHub Comments
this is fixed in #1634. I think this issue can be closed now.
Gotcha. Probably makes sense to have it be configurable including the port, then. (At the expense of adding yet another configuration option.)