domains / families / software-engineering / dotnet-trace-collect

dotnet-trace-collect

separate

Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).

When to use

• A developer needs to investigate a production performance issue (high CPU, memory leak, slow requests, excessive GC, networking errors, etc.)
• Choosing the right diagnostic tool for a specific runtime, OS, or deployment topology
• Setting up and running diagnostic tool commands for data collection
• Understanding trade-offs between available tools (e.g. PerfView vs dotnet-trace)
• Collecting diagnostics from containerized or Kubernetes workloads

When not to use

• Reviewing source code for performance anti-patterns (use a code review skill instead)
• Benchmarking during development (e.g. BenchmarkDotNet setup)
• Analyzing collected trace or dump files (this skill recommends tools for analysis, but does not perform it)

Skill page

Source