oxidecomputer / oxidecomputer/omicron
Firewall flow logging
Open
Nobody has claimed this yet.
networking
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
We've pitched firewall flow logging as an enabling feature for network visibility and promised some fancy pictures. This is a tracking issue for 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
The issue mentions no files, tests, or entry points. Start by clarifying the intended firewall flow-log scope and the promised network-visibility output, then identify the affected Omicron components and tests. Done should include an agreed implementation scope and validation for the resulting logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100