oxidecomputer / oxidecomputer/omicron
Publish NAT exhaustion metrics to `oximeter`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We don't currently track NAT exhaustion as a stat in OPTE (see https://github.com/oxidecomputer/opte/issues/318), but once that's done, we need to publish and export those to oximeter. Same as related issues, either the sled-agent or Propolis could do this.
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 reviewing oxidecomputer/opte#318 to confirm when NAT exhaustion becomes available as an OPTE stat. Then inspect the related issues and the sled-agent and Propolis paths for existing oximeter metric publishing; done means the NAT exhaustion metrics are published and exported through oximeter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100