prometheus / prometheus/client_rust
Metric names containing spaces are not valid
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 606
- Forks
- 113
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 8
Description
Code like e.g. this suggests that this crate permits metric names containing spaces. The data model asserts that
The metric name. . . may contain ASCII letters and digits, as well as underscores and colons. It must match the regex
[a-zA-Z_:][a-zA-Z0-9_:]*.
Names that don't meet these criteria should be rejected.
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
Read src/bridge.rs at the linked lines and compare its metric-name handling with Prometheus's documented name regex. Confirm the relevant validation path and check that names containing spaces are rejected while valid names remain accepted; the issue does not name a test file to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100