dotnet-trace-collect

The best way to capture .NET performance data is by selecting appropriate diagnostic tools based on your runtime, OS, and deployment topology. This approach provides specific guidance on tool usage, command setup, and data collection processes for production environments.

To collect .NET traces in a containerized Linux environment, you need to choose diagnostic tools that support container deployments. The process involves configuring the correct data collection commands tailored for Linux OS and modern .NET runtimes to capture performance artifacts.

Yes, this diagnostic approach works with both .NET Framework and modern .NET. It recommends appropriate tools and data collection techniques by adapting to the specific runtime, operating system, and whether the application runs in a container or non-container environment.

You need to use specialized diagnostic tools for .NET performance analysis when you encounter production issues and must identify the root cause. This process helps you choose the right tool, understand environment trade-offs, and capture artifacts before applying analysis techniques.

You can use this to guide data collection for high CPU usage in your .NET application, but it does not perform the analysis directly. It recommends the appropriate diagnostic tools and commands to capture the necessary performance artifacts for post-collection analysis.