返回 Skill 列表
extension
分类: 开发与工程无需 API Key

azure-diagnostics

在Azure上调试和解决生产问题。涵盖容器应用和函数应用诊断、使用KQL进行日志分析、健康检查以及针对镜像拉取、冷启动、健康探测和函数调用失败的常见问题解决方案。适用场景:调试生产问题,故障排除容器应用,故障排除函数应用,故障排除Azure Functions,使用KQL分析日志,修复镜像拉取失败,解决冷启动问题,调查健康探测失败,检查资源健康状况,查看应用程序日志,查找错误的根本原因,函数应用不工作,函数调用失败 不适用场景:部署应用程序(请使用azure-deploy),创建新资源(请使用azure-prepare),成本优化(请使用azure-cost-optimization)

person作者: jakexiaohubgithub

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

Rules

  1. Start with systematic diagnosis flow
  2. Use AppLens (MCP) for AI-powered diagnostics when available
  3. Check resource health before deep-diving into logs
  4. Select appropriate troubleshooting guide based on service type
  5. Document findings and attempted remediation steps

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/ | | Function Apps | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | functions/ |


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