agentleFS
paulip114paulip114/sre-practice-skills/sre-monitoring-and-alerting/SKILL.md

sre-monitoring-and-alerting

Skill59 starsChanged 28 days agoApache-2.0View on GitHub

Use when designing or reviewing monitoring, dashboards and alerts — golden signals, white-box vs black-box, alert hygiene, and turning SLOs into multiwindow multi-burn-rate alerts (with Prometheus templates and a burn-rate calculator). Based on Google SRE practice.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Measure distributions, not averages: Use histograms/percentiles for latency.

    line 20
  2. Distinctive:

    Test the monitoring: Verify alerts fire by injecting failures in staging or by unit-testing rules.

    line 46
  3. Distinctive:

    Add alert suppression/inhibition so one big outage doesn't produce three notifications.

    line 104
  4. Distinctive:

    Don't hand-tune windows and burn rates per service.

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monitoring and Alerting

Monitoring answers what is broken and why. Page humans only when the error budget is under real threat; everything else is a ticket or a dashboard.

Monitoring Design

Monitoring exists to answer two questions: what is broken (symptom) and why (cause). Build it so that a human is only interrupted for the first, and can find the second quickly.

Principles

  • Alert on symptoms, investigate with causes. Users feel "checkout is slow", not "DB CPU is 90%". Page on user-visible symptoms (ideally SLO burn — see Alerting on SLOs below); keep cause metrics for dashboards and debugging.
  • Every page must be urgent, actionable, and need human judgment. If a script could respond, automate it. If it can wait until morning, it's a ticket. If nobody acts on it, delete it.
  • Keep it simple. Rules that rarely fire, signals nobody looks at, and clever heuristics rot. Prefer a small set of well-understood signals and remove what isn't used (review quarterly).
  • Black-box + white-box. Black-box probes show what users see right now (and catch problems that never reach your servers). White-box metrics show internals and imminent problems. You need both.
  • Measure distributions, not averages. Use histograms/percentiles for latency; averages hide the tail. Choose bucket boundaries that match SLO thresholds.

The four golden signals (request-serving systems)

SignalWhat to measureWatch for
LatencyTime to serve, separately for successes and errorsFast errors hide in blended averages; slow errors are worse than fast ones
TrafficDemand: requests/s, sessions, transactions, bytesSudden drops can mean an upstream outage, not good news
ErrorsRate of failed requests: explicit (5xx), implicit (wrong content), policy (slower than promised)Some errors are only visible end-to-end
SaturationHow full the most constrained resource is (CPU, memory, I/O, threads, queue depth, connection pools)Latency increase is often the earliest sign; predict "full in N hours"

For pipelines add freshness, throughput and backlog; for storage add durability and capacity headroom.

Design procedure

  1. Start from SLIs (sre-slos-and-error-budgets). Those become the top of every dashboard and the source of pages.
  2. Instrument the golden signals at each tier (load balancer, service, critical dependencies). Label by endpoint/request class, response code, and version so you can slice by release.
  3. Add saturation metrics for the resource that runs out first. Know what that is from load tests (sre-capacity-and-system-design).
  4. Add black-box probes for each critical user journey, from outside your network.
  5. Decide metrics vs logs vs traces. Metrics for things you alert on and trend (cheap, aggregated). Logs for per-event detail and forensic debugging. Traces for latency breakdown across services. Don't page from log scraping if a metric can carry the signal.
  6. Build dashboards in layers:
    • Service overview: SLIs + budget remaining, golden signals, current release version.
    • Dependency view: each critical dependency's latency/errors as seen from the caller.
    • Resource view: saturation per component. Annotate deploys, config pushes and incidents on graphs.
  7. Write alert rules with: a clear name, severity (page/ticket), the user impact in the description, and a runbook link with first diagnostic steps.
  8. Test the monitoring. Verify alerts fire by injecting failures in staging or by unit-testing rules. Monitor the monitoring (a dead-man's-switch alert that fires when the pipeline stops sending).

Alert hygiene checklist

For every existing page:

  • Did it detect something users would notice (or will soon)?
  • Was action required immediately, and did a human need to decide what to do?
  • Has it fired spuriously in the last quarter? How often was it ignored?
  • Does it duplicate another alert for the same symptom?
  • Does its runbook exist and still match reality?

Anything failing these: convert to ticket, automate the response, merge, or delete. Track pages per shift as a health metric (sre-on-call-and-toil).

Anti-patterns

  • Paging on every cause metric "just in case".
  • Static thresholds copied from another service without understanding.
  • Dashboards with dozens of graphs and no ordering by importance.
  • Monitoring that depends on the system it monitors (same cluster, same network path).
  • Long for: durations used to hide flapping instead of fixing the signal.

Alerting on SLOs

Page a human only when the error budget is under real threat. Everything else is a ticket or a dashboard.

Judge any alerting strategy on four properties

  • Precision — share of alerts that were significant.
  • Recall — share of significant events that alerted.
  • Detection time — how fast it fires.
  • Reset time — how long it keeps firing after recovery.

A "significant event" means it consumed a meaningful fraction of the error budget.

Why the simple options fail

ApproachProblem
Alert when the short-window (e.g. 10 min) error rate ≥ SLO thresholdPoor precision: can fire many times a day while the SLO is still met
Same threshold, long window (e.g. 36 h)Good precision, but it keeps firing for hours after the problem is fixed and is expensive to compute
Short window + for: durationDetection time ignores severity (a total outage waits as long as a tiny one); a flapping signal resets the timer and may never fire. Don't use durations for SLO alerts.
Single burn-rate alert (e.g. 14.4× over 1h)Good precision and detection, but misses slower burns that still exhaust the budget

Recommended: multiwindow, multi-burn-rate

Burn rate = observed error ratio ÷ (1 − SLO). Burn rate 1 spends exactly the whole budget over the window; burn rate 1,000 on a 99.9%/30-day SLO spends it in ~43 minutes.

Starting configuration for a 30-day window (scale thresholds by your SLO):

SeverityLong windowShort windowBurn rateBudget consumed when it fires
Page1 h5 min14.42%
Page6 h30 min65%
Ticket3 d6 h110%
  • Fire only when both long and short windows exceed the threshold. The long window gives precision; the short window (≈1/12 of the long) makes it stop firing soon after recovery.
  • Threshold for each row = burn_rate × (1 − SLO).
  • Burn rate for "X% of budget in window W" over period P = X × P / W. (2% of 30 days in 1 h → 0.02 × 720 = 14.4.)
  • Add alert suppression/inhibition so one big outage doesn't produce three notifications.
  • Pages and tickets are the only alert outputs that ask a human to act; route the ticket row to a queue, not a pager.

Rule templates: references/prometheus-rules.md. Calculator: scripts/burn_rate.py.

Special cases

Low-traffic services — one failure out of a handful of requests looks like a 1,000× burn. Options, usually combined:

  • Generate synthetic traffic with probers (but synthetic success can mask real-user failure).
  • Aggregate related low-traffic services that share failure domains into one alerting group.
  • Make the product tolerate single failures (client retries with exponential backoff and jitter, queued/deferred execution).
  • Reconsider whether the SLO or window is right if a single failure really doesn't merit a page.

Very loose SLOs (e.g. 90%) — a total 1-hour outage may never reach "2% of budget in 1h"; recompute thresholds so achievable outages can still fire.

Very tight SLOs (e.g. 99.999%) — a full outage burns the monthly budget in under a minute, faster than alerting can react. Defend these with design: progressive rollouts (a 1% canary stretches the time-to-exhaustion 100×), automated rollback, isolation. See sre-release-and-launch.

Alerting at scale

Don't hand-tune windows and burn rates per service. Pick one parameter set and apply it everywhere. Group request types into a few classes with shared targets, e.g.:

ClassExampleAvailabilityLatency
CRITICALlogin, payment99.99%tight
HIGH_FASTinteractive core features99.9%tight
HIGH_SLOWreports, exports99.9%relaxed
LOWbackground polling99%none
NO_SLOdark launches, alphanonenone

Reviewing existing alerts

For each alert ask: Is it tied to user-visible impact (symptom) or to an internal cause? Does it require immediate human action? What did responders actually do the last N times? Delete or downgrade anything that is routinely ignored or auto-resolves. See also Alert hygiene checklist above and sre-on-call-and-toil.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.