Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
After MultiProcessCollector used, the exposed endpoint `/metrics` has no value returned
See original GitHub issueI’m using MultiProcessCollector with UWsgiPrometheusMetrics, why does the endpoint /metrics return none?
I have tried some of the cases in the examples and found that none of them worked.
Issue Analytics
- State:
- Created a year ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Support sharing registry across multiple workers ... - GitHub
The MultiProcessCollector() is a collector, you need to add it on it's own to a registry and use that to generate the metric...
Read more >4. Exposition - Prometheus: Up & Running [Book] - O'Reilly
Exposition to Prometheus is done over HTTP. Usually you expose metrics under the /metrics path, and the request is handled for you by...
Read more >Spring Boot 2 - Actuator Metrics Endpoint not working
To make an actuator endpoint available via HTTP, it needs to be both enabled and exposed. By default: only the /health and /info...
Read more >prometheus-flask-exporter - PyPI
When uWSGI is configured to run with lazy-apps, exposing the metrics endpoint on a separate HTTP server (and port) is not functioning yet....
Read more >Metrics and Alerts in Azure Traffic Manager - Microsoft Learn
use 0 if the endpoint is down. This metric can be shown either as an aggregate value representing the status of all the...
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
Awesome, glad you found the issue! Perhaps I should document it in the README, though it’s probably more a property of the underlying prometheus_client library than this one.
There are some examples mixing uwsgi with other frameworks in the repo, so I think it should be doable but didn’t try it. Feel free to open a new issue if you try it and find it that it doesn’t work.
Thanks a lot!
The problem is solved, the developer does need to set the environment variables directly before the program starts, the settings in the code don’t take effect.
By the way, can uwsgi be mixed and matched with restful?