azure-diagnostics

Diagnose Azure Container Apps and Function Apps failures using KQL, Azure Monitor, and resource health checks.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/qprjack86/apexbase --skill azure-diagnostics-qprjack86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-diagnostics
Source: https://github.com/qprjack86/apexbase/tree/main/.github/skills/azure-diagnostics
Command: npx skills add https://github.com/qprjack86/apexbase --skill azure-diagnostics-qprjack86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps troubleshoot Azure production issues by turning vague failures into a structured diagnosis process, reducing time spent guessing at the cause of outages, failed deployments, and unhealthy services.

Core Features & Use Cases

  • Systematic Root Cause Analysis: Guides a step-by-step flow from symptom identification to health checks, log review, metric analysis, and change investigation.
  • Azure Service Troubleshooting: Covers Container Apps and Function Apps, including image pull failures, cold starts, health probe failures, invocation errors, timeouts, and binding issues.
  • Operational Evidence Gathering: Uses KQL queries, Azure Resource Graph, Azure Monitor, and AppLens/MCP-style diagnostics to collect and interpret logs, resource health, and activity history.
  • Use Case: A Function App stops responding after a deployment, and this Skill helps locate linked telemetry, verify resource health, inspect recent errors, and produce a remediation-focused report.

Quick Start

Ask the skill to diagnose the failing Azure resource, identify the most likely root cause, and recommend the next validation steps.

Frequently Asked Questions about azure-diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Azure Container Apps health probe failures and image pull errors?

To troubleshoot Azure Container Apps failures, you need a systematic diagnosis flow that checks resource health, analyzes logs with KQL, and inspects metrics. This approach identifies root causes for image pull errors and health probe failures by gathering operational evidence from Azure Monitor.

What is the best way to diagnose Azure Function Apps cold starts and invocation timeouts?

The best way to diagnose Azure Function Apps cold starts and invocation timeouts is using AppLens-style diagnostics and Azure Resource Graph. This method locates linked telemetry, verifies resource health, and inspects recent errors to produce remediation-focused reports.

How do I use KQL queries to find the root cause of Azure production outages?

You use KQL queries within Azure Monitor to analyze logs and activity history during Azure production outages. This operational evidence gathering identifies symptoms and recent changes, supporting evidence-driven remediation for failing services.

Can I use Azure CLI to check resource health for failed deployments?

Yes, you can use Azure CLI to perform health checks on resources after failed deployments. This verifies the operational status of Container Apps and Function Apps, helping to locate binding errors and broken telemetry links before applying fixes.

Why does my Azure Function App stop responding after a deployment?

Azure Function Apps may stop responding after a deployment due to binding errors, invocation failures, or broken telemetry links. A structured diagnosis process investigates recent changes, checks resource health, and reviews metrics to pinpoint the exact failure.