monitoring-and-alerting
Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.
Profile →npx skills add rampstackco/claude-skills --skill monitoring-and-alerting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Monitoring and Alerting Decide what to watch, what to alert on, and how to make sure the right person finds out when things break. --- ## When to use - Setting up monitoring on a new site or service - Defining SLOs (service level objectives) and error budgets - Choosing which alerts page someone vs which go to a quiet channel - Designing or fixing on-call rotation - Diagnosing alert fatigue - Filling monitoring gaps revealed by an incident - Migrating monitoring vendors ## When NOT to use - Responding to an active incident (use `incident-response`) - Writing the post-mortem (use `after-action-report`) - Designing analytics dashboards for product metrics (use `analytics-strategy`) - Performance optimization itself (use `performance-optimization`) --- ## Required inputs - The system you're monitoring (URLs, services, dependencies) - Existing monitoring tools (uptime, errors, logs, APM) - Business hours and team timezone(s) - Who is on-call or available for incidents - Existing SLOs or success metrics, if any --- ## The framework: 4 layers Monitoring works in layers. Skip a layer and you'll miss a class of problems. ### Layer 1: Availability Is the site up? The simplest, most import
- When to use
- When NOT to use
- Required inputs
- The framework: 4 layers
- Layer 1: Availability
- Layer 2: Correctness
- Layer 3: Performance
- Layer 4: Errors and anomalies
- SLOs and error budgets
- Picking SLOs
- Using error budgets
- Workflow
- Step 1: Inventory what's already monitored
- Step 2: Map the system
What does the monitoring-and-alerting skill do?
Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill monitoring-and-alerting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.