dotnet-trace-collect

Guide diagnostic artifact capture for .NET performance analysis.

Updated May 28, 2026

Search Tags:#dotnet #performance analysis #diagnostic tools #performance diagnostics #performance issue

Ready to run

npx skills add https://github.com/ojrojas/AgentsInstructions --skill dotnet-trace-collect-ojrojas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-trace-collect
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-diag/skills/dotnet-trace-collect
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill dotnet-trace-collect-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide for developers to capture diagnostic artifacts for diagnosing production .NET performance issues, selecting the right tools, and understanding tool trade-offs.

Core Features & Use Cases

Diagnostic Tool Selection: Based on the environment, recommend the appropriate diagnostic tools for .NET performance analysis.
Data Collection: Guide the developer through setting up and running diagnostic tool commands for data collection.
Analysis Recommendations: Suggest analysis approaches and tools after data collection.
Use Case: A developer experiencing a performance issue in a .NET application can use this Skill to understand the right tools and steps to collect diagnostic data for further analysis.

Quick Start

Run the dotnet-trace-collect skill to capture diagnostic artifacts for your .NET application performance issue.

Frequently Asked Questions about dotnet-trace-collect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I collect .NET diagnostic artifacts for performance analysis?▼

Yes, you can capture .NET performance diagnostics in containers by evaluating the deployment environment and selecting compatible tools like dotnet-monitor or dotnet-trace to extract the necessary diagnostic artifacts.

What is the best way to capture .NET performance diagnostics in a containerized deployment?▼

Capturing .NET performance diagnostics in containers requires evaluating the environment to select compatible tools like dotnet-monitor or dotnet-trace to extract the necessary diagnostic artifacts.

Does dotnet-trace work with both .NET Framework and modern .NET?▼

Yes, dotnet-trace works with both .NET Framework and modern .NET environments, allowing you to capture diagnostic artifacts across different runtime versions on Windows and Linux systems.

How do I choose between PerfView and dotnet-trace for performance issue diagnostics?▼

Choosing between PerfView and dotnet-trace involves assessing your environment, such as Windows versus Linux or containerized versus non-containerized deployments, to select the tool with the best trade-offs.

What should I do after collecting .NET trace data for a performance issue?▼

After collecting .NET trace data for a performance issue, you should follow the suggested analysis approaches and utilize appropriate tools to evaluate the captured diagnostic artifacts.