Should packet loss monitoring be included in audit logs?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
When there is packet loss on a monitor, it will be stored in the audit log, causing user activity to be invisible or difficult to read.
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 packet-loss monitoring and audit logs but provides no file, test, or entry point. First clarify whether packet-loss events should be excluded, filtered, or displayed differently; then locate the monitor and audit-log paths. Done means the agreed behavior is implemented and audit logs remain readable during packet loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100