PaperclipOrg
Claude Agent Skill · by Microsoft

Azure Diagnostics

The azure-diagnostics skill enables developers and DevOps engineers to systematically debug and troubleshoot production issues across Azure services including C

Install
Terminal · npx
$npx skills add https://github.com/microsoft/github-copilot-for-azure --skill azure-diagnostics
Works with Paperclip

How Azure Diagnostics fits into a Paperclip company.

Azure Diagnostics drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md146 lines
Expand
---name: azure-diagnosticsdescription: "Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors."license: MITmetadata:  author: Microsoft  version: "1.0.4"--- # Azure Diagnostics > **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**>> This document is the **official source** for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically. ## Triggers Activate this skill when user wants to:- Debug or troubleshoot production issues- Diagnose errors in Azure services- Analyze application logs or metrics- Fix image pull, cold start, or health probe issues- Investigate why Azure resources are failing- Find root cause of application errors- Troubleshoot Azure Function Apps (invocation failures, timeouts, binding errors)- Find the App Insights or Log Analytics workspace linked to a Function App- Troubleshoot AKS clusters, nodes, pods, ingress, or Kubernetes networking issues ## Rules 1. Start with systematic diagnosis flow2. Use AppLens (MCP) for AI-powered diagnostics when available3. Check resource health before deep-diving into logs4. Select appropriate troubleshooting guide based on service type5. Document findings and attempted remediation steps6. Route AKS incidents to the dedicated AKS troubleshooting document --- ## Quick Diagnosis Flow 1. **Identify symptoms** - What's failing?2. **Check resource health** - Is Azure healthy?3. **Review logs** - What do logs show?4. **Analyze metrics** - Performance patterns?5. **Investigate recent changes** - What changed? --- ## Troubleshooting Guides by Service | Service | Common Issues | Reference ||---------|---------------|-----------|| **Container Apps** | Image pull failures, cold starts, health probes, port mismatches | [container-apps/](references/container-apps/README.md) || **Function Apps** | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | [functions/](references/functions/README.md) || **AKS** | Cluster access, nodes, `kube-system`, scheduling, crash loops, ingress, DNS, upgrades | [AKS Troubleshooting](aks-troubleshooting/aks-troubleshooting.md) | --- ## Routing - Keep Container Apps and Function Apps diagnostics in this parent skill.- Route active AKS incidents, AKS-specific intake, evidence gathering, and remediation guidance to [AKS Troubleshooting](aks-troubleshooting/aks-troubleshooting.md). --- ## Quick Reference ### Common Diagnostic Commands ```bash# Check resource healthaz resource show --ids RESOURCE_ID # View activity logaz monitor activity-log list -g RG --max-events 20 # Container Apps logsaz containerapp logs show --name APP -g RG --follow # Function App logs (query App Insights traces)az monitor app-insights query --apps APP-INSIGHTS -g RG \  --analytics-query "traces | where timestamp > ago(1h) | order by timestamp desc | take 50"``` ### AppLens (MCP Tools) For AI-powered diagnostics, use:```mcp_azure_mcp_applens  intent: "diagnose issues with <resource-name>"  command: "diagnose"  parameters:    resourceId: "<resource-id>" Provides:- Automated issue detection- Root cause analysis- Remediation recommendations``` ### Azure Monitor (MCP Tools) For querying logs and metrics:```mcp_azure_mcp_monitor  intent: "query logs for <resource-name>"  command: "logs_query"  parameters:    workspaceId: "<workspace-id>"    query: "<KQL-query>"``` See [kql-queries.md](references/kql-queries.md) for common diagnostic queries. --- ## Check Azure Resource Health ### Using MCP ```mcp_azure_mcp_resourcehealth  intent: "check health status of <resource-name>"  command: "get"  parameters:    resourceId: "<resource-id>"``` ### Using CLI ```bash# Check specific resource healthaz resource show --ids RESOURCE_ID # Check recent activityaz monitor activity-log list -g RG --max-events 20``` --- ## References - [KQL Query Library](references/kql-queries.md)- [Azure Resource Graph Queries](references/azure-resource-graph.md)- [Function Apps Troubleshooting](references/functions/README.md)