oxidecomputer / oxidecomputer/omicron
Metrics: Include unit of measure in metrics metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In view of #6634 and the many types of metrics we serve across the stack, it will be useful to have the unit of measure being a field/attribute so that users don't have to use documentation to decide how to label the metrics and automate the rendering with the right UOM.
This will also fill a potential gap if we support openmetrics or opentelemetry format - both of which appears to have units.
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
No files, tests, or entry points are named. Begin by tracing how metrics metadata is defined and served across the stack, then compare the required unit field with the units supported by OpenMetrics and OpenTelemetry. Done means the scope and metadata representation are settled and unit information is exposed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100