microsoft / microsoft/CLRInstrumentationEngine
suggestion - apply flood protection/throttling of log events
Open
Nobody has claimed this yet.
suggestion
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
Error logs can also be verbose at times when many things catastrophically fail. We might consider providing some mechanism to reduce or aggregate similar errors together while still maintaining enough information to diagnose issues.
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 names no files, tests, or entry points, so first locate where error logs are emitted and review the surrounding logging behavior. Define the scope of flood protection or aggregation, then verify that repeated catastrophic failures are reduced while retaining enough diagnostic information.
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