triaging-prometheus-incidents-and-slos
Triages Kubernetes service incidents, latency regressions, USE saturation, firing Prometheus alerts, and Google SRE multi-window SLO error-budget burn rates using RED golden signals, period comparisons, and OpenMetrics trace exemplars. Use when investigating an outage or page, evaluating 30-day SLO error-budget burn and hours to exhaustion, generating multi-window SLO burn-rate rules, diagnosing RPS drops vs target-down blind spots, or pivoting from latency/error spikes via exemplars. Do not use for clustering Alertmanager alert storms or creating Alertmanager silences (use triaging-alertmanager-alerts or managing-alert-silences), LogQL log summarization (use triaging-loki-incidents-and-errors), or TraceQL span-cohort diffs (use triaging-tempo-service-errors).
- Version
- 0.2.0
- License
- Apache-2.0
Pinned to revision e93452925e25, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/triaging-prometheus-incidents-and-slos/SKILL.md
- skills/triaging-prometheus-incidents-and-slos/references/cross-pillar-handoffs.md
- skills/triaging-prometheus-incidents-and-slos/references/incident-triage-template.md
- skills/triaging-prometheus-incidents-and-slos/references/red-use-golden-signals.md
- skills/triaging-prometheus-incidents-and-slos/references/slo-multiwindow-burn-rates.md
- skills/triaging-prometheus-incidents-and-slos/scripts/generate_slo_rules.py
Every link opens the file at its source, pinned to the revision this page describes.