What problem does it solve? Debugging Azure production incidents requires jumping between portals, logs, metrics, and CLI tools. This Skill provides a systematic triage workflow that routes symptoms to the right diagnostic path, checks resource health first, and surfaces root causes with evidence before remediation. ## Core Features & Use Cases - Service-Specific Troubleshooting Guides: Dedicated playbooks for Container Apps (image pull failures, cold starts, health probes), App Service (high CPU, deployment failures, TLS issues), Function Apps (invocation failures, missing App Insights linkage), AKS (CrashLoopBackOff, node NotReady, DNS, ingress), and Event Hubs/Service Bus SDK errors across .NET, Java, JavaScript, and Python. - AI-Assisted Diagnostics via MCP Tools: Uses AppLens for automated root cause analysis, Azure Monitor for KQL log queries, and Resource Health checks before deep-diving into logs. - Ready-to-Run Query Libraries: Includes KQL query references for errors, failed requests, and slow dependencies, plus Azure Resource Graph queries to find degraded resources across subscriptions. - Use Case: When an AKS pod is stuck in CrashLoopBackOff, the Skill routes you to the pod-failures playbook, checks exit codes and previous logs, and maps exit code 137 to an OOMKilled memory-limit fix. ## Quick Start Ask the assistant to troubleshoot your Azure resource, for example: diagnose why my App Service app is returning 503 errors and check its recent deployments and logs.
