analyze-metric-dotnet

What problem does it solve?

Developers and SREs often struggle to interpret .NET CLR runtime metrics (GC, JIT, thread pool, exceptions) on Grafana dashboards, frequently confusing them with HTTP request metrics or custom application metrics, leading to incorrect root cause analysis during incidents.

Core Features & Use Cases

• Runtime Metric Interpretation: Provides clear explanations for all panels on the Dotnet Runtime Metrics dashboard, covering both built-in .NET 9+ dotnet_* metrics and OpenTelemetry.Runtime process_runtime_dotnet_* metrics.
• Incident Troubleshooting: Offers a structured workflow to diagnose empty Grafana panels, missing metric series, and common configuration issues with Prometheus scraping or .NET runtime instrumentation.
• Use Case: When you see a GC pause time spike correlated with increased P99 latency after a deploy, this skill helps you quickly determine if the spike is expected JIT warm-up activity or a sign of memory pressure requiring further investigation.

Quick Start

Use the analyze-metric-dotnet skill to explain the Gen2 GC collection spike and rising committed memory trend on your Dotnet Runtime Metrics dashboard for the payment-service job over the last 2 hours.