Skip to content
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

Tracing and Counters Interest Group - Announcements #13019

Open
noahfalk opened this issue Jul 2, 2019 · 3 comments
Open

Tracing and Counters Interest Group - Announcements #13019

noahfalk opened this issue Jul 2, 2019 · 3 comments
Labels
area-Diagnostics-coreclr area-Tracing-coreclr design-discussion Ongoing discussion about design without consensus question Answer questions and provide assistance, not an issue with source code or documentation.
Milestone

Comments

@noahfalk
Copy link
Member

noahfalk commented Jul 2, 2019

I'm making this issue as an informal way to flag other issues and discussions that might be relevant to doing tracing, logging, and performance counters in the .Net runtime. This includes technologies such as EventSource, EventPipe, ETW, Lttng, EventCounter, EventListener, DiagnosticsSource, and Activity. This thread is likely to stay closer to the bleeding edge than release notes or docs on docs.microsoft.com, but in exchange it is likely be more informal. If this is something you are interested in, subscribe to this issue to follow along.

Please don't do discussion directly in this issue, just links or short announcements. Thanks!

@noahfalk
Copy link
Member Author

I recently made a few fixes/minor feature additions for EventPipe and DiagnosticSourceEventSource. With these changes it may now be possible to make a basic distributed tracing instrumentation tool that uses only EventPipe rather than the traditional approach of in-process SDKs or profiler based IL instrumentation. I have only created prototype at this point, it has yet to be proven with a production scale implementation.

dotnet/coreclr#27522
dotnet/corefx#42104

@noahfalk
Copy link
Member Author

We are working to improve our documentation on new global tools created in .Net Core 3.0, such as dotnet-counters and dotnet-trace. Feedback on the documentation or the tools is always welcome (though please use dotnet/diagnostics#515 or new issues in the diagnostics repo as needed). Thanks!

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@noahfalk
Copy link
Member Author

@tarekgh has been hard at work planning some improvements to the Activity APIs for .NET 5. These APIs make it easier for anyone to add Activities to their distributed traces and improve the OpenTelemetry integration story. Check out #31373 and let us know what you think in the comments there. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Diagnostics-coreclr area-Tracing-coreclr design-discussion Ongoing discussion about design without consensus question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
None yet
Development

No branches or pull requests

2 participants