-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[next-gen] dotnet-monitor design doc #3992
[next-gen] dotnet-monitor design doc #3992
Conversation
I think that we need to add some clarification about supported scenarios (only natively supported libraries/custom diagnostics crated manually by the users). No option to auto-instrument by the bytecode manipulation and/or auto-injecting instrumentation libraries. I have also some doubts about propagation and sampling. It is not clear to me what will be supported. |
@Kielek Good call. I added a section for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CodeBlanch Thanks for putting everything together! The documentation is clear and looks good as a starting point. We can refine and enhance it further in future updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed write-up!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Changes
Adding a doc to cover details about the ongoing effort to support out-of-proc monitoring with OTLP egress via
dotnet-monitor
.@wiktork, @ramthi FYI