microsoft / microsoft/CLRInstrumentationEngine
Add in-depth diagnostics logging
Open
Nobody has claimed this yet.
task
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
This type of logging should be granular to the InstrumentationMethod level, allowing easier triaging of conflicts. Consider introducing a new logging flag 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 names no files, tests, or entry points. Start by locating the engine's existing logging and InstrumentationMethod handling, then determine how a granular diagnostic mode and its proposed logging flag should be scoped. Done should include an agreed design and validation that conflicts can be triaged at the InstrumentationMethod level.
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