oxidecomputer / oxidecomputer/omicron
Networking: Determine what event history we want to track, and how
Open
Nobody has claimed this yet.
networking
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
There are a number of events we'll want to track and make available to users. Such as
- Link up/down events.
- Saturation events.
- Router peering events.
...
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
No files, tests, or entry points are identified. Start by clarifying which networking events belong in history and how they should be exposed to users. Done would be an agreed event-history design with defined event types and tracking approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100