The current diagnostics support include performance counters and trace source. .NET Core has moved towards the Activity and DiagnosticSource APIs to provide robust diagnostics and tracing. See:

https://github.com/dotnet/diagnostics/blob/master/documentation/diagnostics-planing.md

https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/ActivityUserGuide.md

https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/DiagnosticSourceUsersGuide.md

https://devblogs.microsoft.com/aspnet/observability-asp-net-core-apps/

Would this team consider a PR that added a new event subscriber that conforms to these guidelines and enables Activity and DiagnosticListener-based tracing? This would then enable a number of scenarios, including plugging into Activity-based observability tools.

I have a small PoC as an example of what the code looks like:

https://github.com/jbogard/nsb-diagnostics-poc/blob/master/MongoDB.Driver.Core.Extensions.SystemDiagnostics/DiagnosticsActivityEventSubscriber.cs