Opmon additions for Fragment error bits
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 3
- Forks
- 5
- Avg merge
- 4h 42m
- Merged PRs (30d)
- 6
Description
We should consider adding statistics about Fragment error bits and their occurrence to operational monitoring.
As @wesketchum pointed out, the handling and visualization might need some thought (E.g.: sourceID based).
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
The issue names no files, tests, or entry points. Start by locating Fragment error-bit handling and the existing operational monitoring and visualization paths, then clarify whether statistics should be sourceID-based. Done means the required metrics and their presentation are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100