Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

azure-diagnostics | azure

Skill

azure-diagnostics

From azure

Provides systematic diagnostic flows for Azure services: App Service, Functions, AKS, Container Apps, Event Hubs, and Service Bus using AppLens and Azure Monitor.

$

npx claudepluginhub anthropics/claude-plugins-official --plugin azure

Popularity

Stars

1,178

Forks

183

Shared by

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/azure:azure-diagnostics

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**

Supporting Files

SKILL.md

152 lines · ~1.4k tokens

Similar Skills

azure-diagnostics

1.0k

Debugs Azure production issues in Container Apps, Functions, and AKS using AppLens, Azure Monitor, resource health, KQL logs, and triage flows for pods, cold starts, image pulls.

azure-observability-investigator

16

Investigates Azure operational health using Monitor, Log Analytics, Application Insights, KQL triage, alert rules, workbooks, and telemetry-gap analysis for incident and posture investigations.

6 files4 tools

vanguard-frontier-agentic

devops-troubleshooter

40.4k

Expert DevOps troubleshooter for rapid incident response, log analysis, distributed tracing, Kubernetes debugging, network troubleshooting, and performance analysis. Guides users through root cause analysis and system reliability best practices.

antigravity-awesome-skills

Stats

LanguagePython

Stars1,178

Forks183

MaintenanceExcellent

Last CommitJun 9, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

azure-diagnostics

troubleshooting

Help us improve

Share bugs, ideas, or general feedback.

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 App Service issues (high CPU, deployment failures, crashes, slow responses, TLS/custom domains)
Respond to prompts like "troubleshoot app service", "app service high CPU", or "app service deployment failure"
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
Troubleshoot Azure Messaging SDK issues (Event Hubs, Service Bus connection failures, AMQP errors, message lock issues)

Rules

Start with systematic diagnosis flow
Use AppLens (MCP) for AI-powered diagnostics when available
Check resource health before deep-diving into logs
Select appropriate troubleshooting guide based on service type
Document findings and attempted remediation steps
Route AKS incidents to the dedicated AKS troubleshooting document

Quick Diagnosis Flow

Identify symptoms - What's failing?
Check resource health - Is Azure healthy?
Review logs - What do logs show?
Analyze metrics - Performance patterns?
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/
App Service	High CPU, deployment failures, crashes, slow responses, TLS/custom domains	app-service/
Function Apps	App details, invocation failures, timeouts, binding errors, cold starts, missing app settings	functions/
AKS	Cluster access, nodes, `kube-system`, scheduling, crash loops, ingress, DNS, upgrades	AKS Troubleshooting
Messaging	Event Hubs & Service Bus SDK errors, AMQP failures, message lock, connectivity	Messaging Troubleshooting

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.
Route Azure Messaging SDK troubleshooting (Event Hubs, Service Bus) to Messaging Troubleshooting.

Quick Reference

Common Diagnostic Commands

# Check resource health
az resource show --ids RESOURCE_ID
# View activity log
az monitor activity-log list -g RG --max-events 20
# Container Apps logs
az 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 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

# Check specific resource health
az resource show --ids RESOURCE_ID

# Check recent activity
az monitor activity-log list -g RG --max-events 20

References