prometheus / prometheus/client_python
`namespace` (and `subsystem`) for `*MetricFamily` classes
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 876
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 1
Description
Hey.
The MetricWrapperBase derived classes (Counter, Gauge, etc) all have namespace and subsystem in their constructors and automatically combine that into a final name.
Wouln't it make sense to have at least namespace also for the *MetricFamily classes`
Cheers,
Chris.
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 locating the *MetricFamily classes and compare their constructors with MetricWrapperBase and its Counter and Gauge derivatives. Clarify whether namespace alone or both namespace and subsystem are required, then define the expected combined-name behavior and verify it with focused tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100