prometheus / prometheus/exporter-toolkit
Add structured way of generating metric names
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 311
- Forks
- 109
- Avg merge
- 3d 59m
- Merged PRs (30d)
- 6
Description
There are a lot of instances of metric names that go against the best practices, whether it be in external or official projects. I think it would be cool if the exporter toolkit provided a structured way of generating these names. This would promote more compliance with the official guidance and make it easier to follow.
I'm still not exactly sure what this interface would look like.
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
The issue proposes a structured way to generate Prometheus metric names, but names no files, tests, or entry points and says the interface is not yet defined. Start by surveying the exporter toolkit's current metric-name handling and the relevant Prometheus naming guidance; done requires an agreed interface and a clearly scoped implementation with validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100