oxidecomputer / oxidecomputer/crucible
Crucible metrics V2
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
In the spirit of trying to answer the question "My VM IO is slow, why?", we want more metrics.
These metrics will help us either exonerate crucible, or identify where in crucible the problem is.
There are a bunch of dtrace probes in both crucible upstairs, crucible downstairs, and the crucible volume layer. These dtrace probes should be turned into actual metrics that are collected by Oximeter. In this case crucible should do the work of creating the histogram buckets and Oximeter would just collect them.
Additional metrics around throughput and queue depth are also desired, with more detail to come.
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 inventorying the existing dtrace probes across crucible upstairs, crucible downstairs, and the crucible volume layer, then review how Oximeter collects metrics. The desired metric set is not fully specified: throughput and queue-depth details still need definition, along with the histogram buckets crucible should create. Done requires an agreed scope and implementation plan for collecting these metrics.
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
- Needs clarification
- Newbie friendliness
- 25/100