skills.rest
sayedihashimi
sayedihashimiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dotnet-trace-collect

Select .NET diagnostic tools and collect traces for production performance issues.

2|Updated Mar 17, 2026
Search Tags:#performance#diagnostics#containers#linux#windows#dotnet-trace#trace-collection
One-click install
npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-trace-collect-sayedihashimi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-trace-collect
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-skills/dotnet-diag/skills/dotnet-trace-collect
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-trace-collect-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers identify and diagnose production .NET performance issues by guiding tool selection and trace collection across Windows, Linux, .NET Framework, modern .NET, and containerized deployments.

Core Features & Use Cases

  • Provides a cross-platform decision framework to choose the right diagnostic tools (PerfView, dotnet-trace, perfcollect, dotnet-monitor) and generate traces for performance analysis.
  • Supports scenarios including slow requests, high CPU, memory pressure, leaks, and networking problems across Windows, Linux, and container environments.
  • Enables an end-to-end workflow from tool selection to trace collection and data formats for subsequent analysis.

Quick Start

Install the needed tooling and run guided trace collection to diagnose a production .NET 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 traces for performance diagnostics in production?▼

Collect .NET traces for performance diagnostics by selecting the right toolset, such as dotnet-trace or dotnet-monitor, and following a guided workflow to capture data for slow requests, high CPU, or memory leaks across Windows, Linux, and container environments.

What is the best way to trace .NET application performance issues in containers?▼

Trace .NET application performance issues in containers by using cross-platform diagnostic tools like dotnet-trace and dotnet-monitor, which support Kubernetes deployments and generate data formats suitable for analyzing memory pressure or networking problems.

Can I use dotnet-trace to collect diagnostic data on both Linux and Windows?▼

Yes, dotnet-trace collects diagnostic data on both Linux and Windows. The cross-platform decision framework supports modern .NET and .NET Framework, guiding tool selection and trace collection across different operating systems and containerized deployments.

When do I need dotnet-monitor versus PerfView for .NET trace collection?▼

Choose dotnet-monitor for modern .NET production environments including containers and Kubernetes, while PerfView is better suited for .NET Framework diagnostics. The right trace collection tool depends on your specific platform and performance issue.

Does .NET trace collection work with .NET Framework and modern .NET applications?▼

Yes, .NET trace collection works with both .NET Framework and modern .NET applications. The diagnostic workflow specifies requirements for cross-platform tracing, outlining tool options and prerequisites across Windows, Linux, and containerized deployments.

Related Skills

Explore More Software Engineering Skills→
ojrojasojrojas

dotnet-trace-collect

Guide diagnostic artifact capture for .NET performance analysis.

Community
Advanced
h4v1dh4v1d

csharp-dotnet-debugging

Diagnose .NET runtime issues in C# applications using CLI tools.

Community
Advanced
wshaddixwshaddix
71

dotnet-profiling

Diagnoses .NET performance issues using dotnet-counters, dotnet-trace, and dotnet-dump.

Community
Advanced
AGIBuildAGIBuild
10

dotnet-profiling

Diagnose .NET performance issues using dotnet-counters, dotnet-trace, and dotnet-dump.

Community
Advanced