oxidecomputer / oxidecomputer/omicron
Metrics: Add `collection_type` attribute to capacity usage targets to distinguish between aggregation levels
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
The following timeseries only provide an id field which can be a rack or silo or project id (in the future, we may add a fleet-level rollup as well when there are multiple racks):
- collection_target:cpus_provisioned
- collection_target:ram_provisioned
- collection_target:virtual_disk_space_provisioned
It'll be very useful to capture the collection_type from the metrics source (which I believe currently is the virtual_provisioning_collection database table) so that users can graph these usage metrics separately based on the aggregation level.
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 searching for the collection_target:cpus_provisioned, collection_target:ram_provisioned, and collection_target:virtual_disk_space_provisioned metric definitions and the virtual_provisioning_collection table. Trace how the metrics source exposes aggregation identity, then ensure these capacity usage metrics include collection_type so users can distinguish rack, silo, and project levels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100