slos-and-triggers
Interpreting Honeycomb SLO compliance, burn rates and trigger status, and what to do about them: detecting misconfigured SLIs, freezing deploys vs paging on-call, designing burn alert thresholds. Load before calling get_slos or get_triggers. Trigger phrases: "check our SLOs", "are we meeting our SLOs", "which SLOs are healthy", "is the error budget OK", "are any alerts firing", "what's the burn rate", "set up an SLO", "create a trigger", "configure alerts", "set up burn alerts", "check trigger status", "starting on-call", "reliability picture", "should we freeze deploys", "is this SLO misconfigured", "are we within budget", "SLO is broken", "budget is negative".
- Version
- 1.0.0
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/slos-and-triggers/SKILL.md
- skills/slos-and-triggers/LICENSE
- skills/slos-and-triggers/references/alerting-strategy.md
- skills/slos-and-triggers/references/slo-design-guide.md
- skills/slos-and-triggers/references/trigger-examples.md
Every link opens the file at its source, pinned to the revision this page describes.