oxidecomputer / oxidecomputer/p4
Better observability on parse rejections
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 137
- Forks
- 12
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 3
Description
When a parser stage rejection happens, we need better observability. Ideally, we would have a USDT probe that shows the complete set of parser state transitions that led to the rejection, including the specific rejection point. Right now, one can only look at the packet that got rejected and try to reason through the state machine code manually.
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 by locating the parser stage rejection path and the state machine code mentioned in the issue. Determine how a rejection point and preceding state transitions can be exposed through a USDT probe. Done means rejected parses provide the complete transition history, including the specific rejection point, for observability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100