oxidecomputer / oxidecomputer/propolis
oximeter server registration could be more resilient to failure (and asynchronous)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
#511 is the easy fix to #497: instead of blocking in instance_ensure retrying forever, the registration will fail after a couple of retries.
The better, longer term fix is to make registration of the server endpoint asynchronous such that transient failures to connect to the oximeter consumer do not make it such that that endpoint won't be able to serve metrics for forever. This depends on some work on the oximeter side: oxidecomputer/omicron#3956.
Contributor guide
No contributing guide indexed for this repository
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 with instance_ensure and the context from #511 and #497. Review oxidecomputer/omicron#3956, which this longer-term change depends on, before designing asynchronous registration. Done means transient oximeter connection failures no longer permanently prevent the server endpoint from serving metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100