monitoring-and-alerting

Design monitoring and alerting frameworks with SLIs, SLOs, and tiered alerts.

523|69|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/rampstackco/claude-skills --skill monitoring-and-alerting-rampstackco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-and-alerting
Source: https://github.com/rampstackco/claude-skills/tree/main/skills/monitoring-and-alerting
Command: npx skills add https://github.com/rampstackco/claude-skills --skill monitoring-and-alerting-rampstackco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and run a robust monitoring system for a website or web app to ensure the right people are alerted when things break, reducing alert fatigue and blind spots across the tech stack.

Core Features & Use Cases

  • Define the four monitoring layers (availability, correctness, performance, and errors) and specify thresholds and baselines.
  • Create SLOs and error budgets, build SLO dashboards, and establish burn-rate policies to guide releases.
  • Design tiered alerting (page, notify, log) with clear escalation paths and on-call rotations.
  • Build end-to-end dashboards for real-time ops, SLO status, per-service views, and executive summaries.
  • Conduct quarterly alert audits, tune thresholds, and maintain up-to-date runbooks.

Quick Start

Define a basic monitoring plan for your site, set one availability SLO, and configure an initial alert for critical incidents.

Frequently Asked Questions about monitoring-and-alerting

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

FAQPage Schema
How do I set up SLOs and error budgets for web service monitoring?▼

Design tiered alerting by creating distinct page, notify, and log tiers with clear escalation paths and on-call rotations. Conduct quarterly alert audits and tune thresholds to ensure on-call workflows reduce alert fatigue while maintaining coverage across the tech stack.

What is the best way to structure monitoring layers for a web application?▼

Build end-to-end dashboards by creating real-time ops views, SLO status panels, per-service metrics, and executive summaries. This layered approach provides visibility into multi-region deployments and supports periodic audit processes for threshold tuning.

Can I use this monitoring framework for multi-region deployments?▼

Multi-region deployments benefit from the framework's ability to maintain up-to-date runbooks and conduct quarterly alert audits, ensuring that thresholds and escalation paths remain properly tuned as infrastructure scales across regions.

Why does my alerting system cause alert fatigue and miss critical incidents?▼

Missing critical incidents often results from lacking SLOs and error budgets. Establish burn-rate policies, define SLIs for correctness and performance, and build SLO dashboards to ensure alerts trigger based on service reliability rather than raw metrics.

Do I need runbooks to maintain an effective observability and uptime strategy?▼

Runbooks complement SLO dashboards and tiered alerting by providing actionable guidance for incident response. Quarterly audits verify that runbooks remain accurate as multi-region deployments and service architectures evolve over time.