skills.rest
kierunb
kierunbCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-trace-collect

Guide .NET performance diagnosis across Windows, Linux, and containers.

Updated Mar 19, 2026
Search Tags:#performance#profiling#diagnostics#tracing#containers#dotnet-trace
One-click install
npx skills add https://github.com/kierunb/ReliableAppDemo --skill dotnet-trace-collect-kierunb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-trace-collect
Source: https://github.com/kierunb/ReliableAppDemo/tree/main/.github/skills/dotnet-diag/skills/dotnet-trace-collect
Command: npx skills add https://github.com/kierunb/ReliableAppDemo --skill dotnet-trace-collect-kierunb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides developers to diagnose production .NET performance issues by helping choose the right diagnostic tools, collect traces, and understand cross-environment trade-offs (Windows/Linux, .NET Framework/modern .NET, container vs non-container).

Core Features & Use Cases

  • Tool recommendations across Windows, Linux, and containers, including PerfView, dotnet-trace, and dotnet-monitor.
  • Step-by-step data-collection guidance with environment-aware workflows and practical trade-offs.
  • Clear guidance on when to use each tool, how to collect data, and how to analyze results to derive actionable insights.

Quick Start

Identify your environment and run the recommended diagnostic workflow to begin collecting traces.

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 dotnet traces to diagnose production .NET performance issues?▼

To collect dotnet traces for production .NET performance issues, you must identify your environment (Windows, Linux, or containers) and run the environment-aware diagnostic workflow to gather data with tools like dotnet-trace or PerfView.

When should I use dotnet-trace versus PerfView for .NET profiling?▼

Use dotnet-trace for modern .NET cross-platform profiling, whereas PerfView is typically geared towards .NET Framework and Windows-specific diagnostic workflows, with the choice depending on your deployment target and framework.

Can I collect diagnostic traces from .NET applications running in containers?▼

Yes, you can collect diagnostic traces from .NET applications running in containers by applying environment-aware workflows that account for container prerequisites and use compatible tools like dotnet-monitor or dotnet-trace.

What is the best way to analyze collected .NET traces to find actionable insights?▼

The best way to analyze collected .NET traces is to follow the recommended analysis paths provided after data collection, turning raw diagnostic data into actionable insights by identifying specific performance bottlenecks within the application.

Do I need dotnet-monitor to trace .NET workloads in production environments?▼

You do not strictly need dotnet-monitor to trace .NET workloads, as dotnet-trace and PerfView are viable alternatives, but dotnet-monitor is highly recommended for streamlined, continuous diagnostics in containerized deployments.

Related Skills

Explore More Software Engineering Skills→
sayedihashimisayedihashimi
2

dotnet-trace-collect

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

Community
Advanced
paleoterrapaleoterra
2

performance-profiler-tools

Analyze Instruments trace files to identify performance bottlenecks and memory growth patterns.

Community
Intermediate
ojrojasojrojas

dotnet-trace-collect

Guide diagnostic artifact capture for .NET performance analysis.

Community
Advanced
AGIBuildAGIBuild
10

dotnet-wpf-migration

Guide migration of legacy .NET Framework desktop apps to .NET 8+ and WinUI 3.

Community
Advanced