prometheus / prometheus/client_python
How to clean PROMETHEUS_ MULTIPROC_
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 876
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 1
Description
I started multiple processes in the production environment over time 'PROMETHEUS_ MULTIPROC_ ‘ There will be more and more files under dir. How can I establish cleaning rules and the volume of responses returned by the 'metrics' endpoint will eventually exceed the connection time. Any help would be greatly appreciated.
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.
Research direction
Start by reviewing the PROMETHEUS_MULTIPROC_* directory behavior and the metrics endpoint described in the issue. Determine how stale files are identified and how response growth is handled; done should include a defined cleanup approach and confirmation that the endpoint remains usable over time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100