Prometheus exporter does not work with multiprocessing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- prometheus, python
- Domain
- documentation, observability
Research direction
Start in the Prometheus exporter documentation under exporter/opentelemetry-exporter-prometheus and review the linked prometheus_client multiprocess documentation. Document that multiprocess mode does not work with custom collectors and can cause metrics to be missing from the endpoint. Done means the limitation is clearly explained for users configuring multiprocessing.
Written by the indexing model from the issue text.
Description
Describe your environment
When instrumenting metrics using OpenTelemetry Python 0.44b0 and exporting them using opentelemetry-exporter-prometheus when using multiprocessing, not all metrics are exposed on the metrics endpoint.
I assume that this comes from the underlying limitation from prometheus_client, which states that multiprocess mode does not work with custom collectors. It could be worth mentioning this limitation in the Prometheus exporter docs.
Steps to reproduce
- Raise metrics in multiprocessing mode when having the Prometheus exporter enabled
- Not all metrics are exposed on Prometheus endpoint
What is the expected behavior?
All raised metrics are exposed on the Prometheus endpoint.
What is the actual behavior?
Not all metrics are exposed on the Prometheus endpoint.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 5d 29m
- Merged PRs (30d)
- 17
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.
More from open-telemetry/opentelemetry-python
-
Baggage is ignored by W3CBaggagePropagator and erronously causes warning 'Invalid baggage entry' Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5678 · 1 reaction ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
open-telemetry/opentelemetry-python#5664 · 4 comments ·
-
bug tests
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
All issues in open-telemetry/opentelemetry-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100