microsoft / microsoft/CLRInstrumentationEngine
Allow purely managed instrumentation libraries to be loaded through CLRIE
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
This is inspired by @SergeyKanzhelev 's work on adding instrumentation to the methods using .NET based decoration.
http://apmtips.com/blog/2016/11/18/how-application-insights-status-monitor-not-monitors-dependencies/
It would be great to be able to do something similar and leverage CLRIE to create a managed only definition of what needs to be instrumented.
Is this something that you are planning by any chance?
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
Start by reviewing the CLRIE repository, the linked APM Tips article, and the four-comment discussion to understand the proposed managed-only instrumentation model. Done would mean defining how managed instrumentation libraries can be loaded through CLRIE, but the issue names no implementation files, tests, or concrete acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100