dotnet-trace-collect

仓库创建 2026年2月4日最近提交 14 小时前SkillHot 收录 20 天前

▸ 精选理由

帮助在不同环境下高效收集可诊断数据，减少盲目采集。

这个 Skill 做什么

指导采集 .NET 性能诊断工件并推荐合适的工具与策略。

在定位线上 .NET 性能问题时，教你选合适的诊断工具并指导如何采集性能工件（CPU、内存、traces 等）。遇到高 CPU、内存泄露或需要在不同环境（Windows/Linux、.NET Framework/现代 .NET、容器）做诊断时用。重点是指导采集策略和工具权衡，本身不替你写代码修复或做深度分析。

▸ 展开 SKILL.md 英文原文

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).

开发编程诊断收集.NET 追踪生产环境通用

4.8k

Stars

351

Forks

仓库内 Skill

+610

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/dotnet/skills/main/plugins/dotnet-diag/skills/dotnet-trace-collect/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/dotnet/skills/main/plugins/dotnet-diag/skills/dotnet-trace-collect/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# .NET Trace Collect

This skill helps developers diagnose production performance issues by recommending the right diagnostic tools for their environment, guiding data collection, and suggesting analysis approaches. It does not analyze code for anti-patterns or perform the analysis itself.

## 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)
- Colle

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有