uptime-monitoring-specialist

Validate health endpoints and configure multi-region uptime monitoring with alert routing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill uptime-monitoring-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uptime-monitoring-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/uptime-monitoring-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill uptime-monitoring-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production services can suffer undetected outages, slowdowns, and unclear incident ownership without reliable monitoring and alerting. This Skill provides a structured approach to implement health checks, continuous uptime monitoring, multi-region checks, escalation policies, and public status reporting so teams can detect, respond to, and learn from availability incidents quickly.

Core Features & Use Cases

  • Health Check Design: Guidance for implementing /health, /ready, and /alive endpoints that verify critical dependencies and return appropriate status codes and diagnostics.
  • Monitoring Configuration: Instructions for configuring external monitors (UptimeRobot, Pingdom, Better Uptime) with intervals, expected responses, and multi-region probes to detect regional outages.
  • Alerting and Incident Management: Patterns for alert thresholds, escalation policies, PagerDuty/Slack integrations, on-call rotations, and status page publishing to communicate incidents and SLA impact.
  • SLA & Metrics Tracking: Methods to compute uptime percentages, track MTTR, and query incident metrics for monthly reporting and compliance checks.
  • Troubleshooting Playbook: Stepwise checks for DNS, SSL, cloud platform service status, and log review to accelerate root cause identification and recovery.

Quick Start

Configure a /health endpoint that validates core dependencies and add an external uptime monitor to check that endpoint every 1-5 minutes with alerts to your on-call channel.

Frequently Asked Questions about uptime-monitoring-specialist

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

FAQPage Schema
How do I implement health checks for web APIs and dependent services?

Health checks validate critical dependencies using /health, /ready, and /alive endpoints that return appropriate status codes and diagnostics. This approach verifies core dependencies and returns diagnostic information to confirm web API availability.

What is the best way to configure multi-region uptime monitoring for production services?

Uptime monitoring uses external monitors with multi-region probes to detect regional outages by checking endpoints at 1-5 minute intervals. This configuration validates expected responses across different geographic locations to ensure service availability.

How do I route uptime alerts to Slack, Email, and PagerDuty?

Alert routing sends uptime notifications to Slack, Email, and PagerDuty by applying alert thresholds and escalation policies. This pattern integrates on-call rotations to ensure incident response teams receive immediate outage notifications.

How does SLA calculation and MTTR tracking work for incident management?

SLA calculation computes uptime percentages while tracking Mean Time To Recovery (MTTR) for incident management. This method queries incident metrics to generate monthly reporting and perform compliance checks for service availability.

Can I use synthetic monitoring for third-party dependencies and background workers?

Synthetic monitoring applies to production web services, CDNs, background workers, and third-party dependencies. This technique validates external checks and health endpoints to detect outages across dependent services in various environments.

What troubleshooting steps help identify root causes during a service outage?

Troubleshooting outages involves stepwise checks for DNS, SSL, cloud platform service status, and log review. This playbook accelerates root cause identification and recovery by systematically verifying infrastructure dependencies during incidents.