check-prod

Assess Azure production health across API, telemetry, PostgreSQL, and alerts.

801|25|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill check-prod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-prod
Source: https://github.com/learntocloud/learn-to-cloud-app/tree/main/.github/skills/check-prod
Command: npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill check-prod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking production health across Azure resources, Application Insights telemetry, and PostgreSQL metrics is slow and error-prone. This Skill performs a read-only health assessment of the production environment and returns a single verdict with supporting evidence.

Core Features & Use Cases

  • Comprehensive Health Signals: Checks /ready endpoint status, resource health, fired alerts, 5xx counts, P95 latency, exceptions, and dependency failures in one pass.
  • Database and Container Diagnostics: Reports PostgreSQL CPU, memory, storage, connections, and CPU credits, plus Container App crash, OOM, and unhealthy-replica events.
  • Clear Verdicts: Classifies the environment as Critical, Warning, Healthy, or Unknown with a compact table of signals, values, and time windows.
  • Use Case: Before a release or during an incident, ask for a production health check and immediately see whether the API, database, and dependencies are operating normally.

Quick Start

Ask the assistant to check prod status and report any errors in the Azure production environment.

Frequently Asked Questions about check-prod

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

FAQPage Schema
How do I check Azure production health with Azure CLI?

Authenticate with Azure CLI, then run Azure Monitor and Log Analytics queries against your workspace tables to inspect requests, exceptions, dependencies, and availability. This Skill automates that workflow and returns a single Critical, Warning, or Healthy verdict.

What signals indicate a production outage in Azure?

Key signals include a non-200 readiness endpoint, any 5xx responses, unavailable resources, PostgreSQL dependency failures, OOM or crash events, and fired Sev1 alerts. Database CPU above 80% or CPU credits below 10 also indicate critical conditions.

Does this health check modify any Azure resources?

No, the assessment is strictly read-only. It only runs Azure Monitor and Log Analytics queries and discovers resource names at runtime without changing any configuration or data.

Why does the health check report Unknown instead of Healthy?

Missing telemetry is reported as Unknown rather than Healthy because absent data cannot confirm normal operation. This distinguishes genuine health from gaps in logging or query failures.

Can I check PostgreSQL performance metrics in Azure Monitor?

Yes, the assessment queries PostgreSQL peak CPU, memory, storage, connection counts, and minimum CPU credits. Warning thresholds apply at 50-80% CPU and 70-85% memory or storage.