Improve .NET diagnostics CLI tooling and libraries

[sywhang]

This issue tracks overall improvement of diagnostics tooling

The list below is not comprehensive, but tracks items that are proposed or on-deck for a future release

dotnet-counters

• UI improvement to monitor command
• Add any new .NET 6 runtime counters
  • As a user, I should be able to use new counter in .NET 6 with dotnet-counters.

dotnet-trace

• monitor command, which prints the events to console in real-time.
  • As a user, I should be able to observe events from a .NET process in real-time using dotnet-trace.
• report command, which analyzes a trace that's already been collected with the collect command.
  • As a user, I should be able to print reports of nettrace files on all platforms that contain information like "top N% method calls", <insert select initial report types>.

dotnet-stack

• Overall improvement to reliability and speed, to the extent that it can be used as a poor man's CPU tracer.
  • As a user, I should be able to use dotnet-stack to retrieve a stack in <establish perf goal> for reasonably sized* applications. (*define reasonably sized)

Microsoft.Diagnostics.NETCore.Client

• Add APIs to interact with diagnostics port.
  • As a user, I should be able to use the Microsoft.Diagnostics.NETCore.Client library to connect to .NET processes using the new Diagnostic Port features added in .NET 5.
• Add the ability to query for existing EventSources
  • As a user, I should be able to query a running process for available EventSources that I can receive events from.

[josalem]

@tommcdon @sywhang - I took the liberty of attempting to clarify some of these checkboxes with user statements. Feel free to edit them in any capacity.

[tmds]

@sywhang dotnet-stack hasn't made it on nuget.org yet. Will it become available in the near future?

[sywhang]

@tmds Let me look into it.