oxidecomputer / oxidecomputer/omicron
Publish basic statistics about customer external DNS queries to `oximeter`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We'd like to have a few basic statistics about the public-facing customer external DNS server, which maps names for the console (and maybe instances) to rack-external IP addresses. The goal is to make sure we have a basic handle on the load on this server. Will flesh out more later.
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 clarifying the intended basic statistics and scope for the public-facing customer external DNS server, including whether instance name mappings are included. The issue names oximeter as the destination, but no files, tests, or entry points are identified. Done means the agreed DNS load statistics are published to oximeter.
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
- Needs clarification
- Newbie friendliness
- 25/100