Runtime: Tracing and Counters Interest Group - Announcements

[noahfalk]

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]

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.

https://github.com/dotnet/coreclr/pull/27522
https://github.com/dotnet/corefx/pull/42104

[noahfalk]

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 https://github.com/dotnet/diagnostics/issues/515 or new issues in the diagnostics repo as needed). Thanks!

[noahfalk]

@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!