How do error budgets affect development velocity?

Error budgets provide a mathematical framework for decision-making; if a budget is exhausted, the team prioritizes reliability improvements over new feature development until the service returns to its SLO target.

What is the difference between an SLI and an SLO?

An SLI (Service Level Indicator) is a quantitative measure of some aspect of the level of service provided, such as latency. An SLO (Service Level Objective) is a target value or range of values for a service level that is measured by an SLI.

How does this skill handle alert fatigue?

The skill implements multi-window burn rate alerts, which combine short-term and long-term windows to ensure that alerts are only triggered for significant reliability threats, filtering out transient spikes.

Does this skill work with Prometheus and Grafana?

Yes, it includes specific PromQL recording rules for SLI calculations and alerting rules for burn rates, as well as a structured blueprint for Grafana dashboards.

Site Reliability SLO Framework

Name: Site Reliability SLO Framework
Author: HermeticOrmus

byHermeticOrmus

分析と監視

Defines and implements Service Level Indicators (SLIs) and Service Level Objectives (SLOs) to establish data-driven reliability targets.

概要

This skill provides a comprehensive framework for implementing Site Reliability Engineering (SRE) practices through the definition of SLIs, SLOs, and error budgets. It guides users through the technical setup of Prometheus recording rules, multi-window burn rate alerts, and Grafana dashboard structures, allowing teams to balance innovation velocity with service stability. By moving away from arbitrary uptime goals toward user-perceived reliability metrics, this skill helps developers implement proactive monitoring and automated error budget policies.

主な機能

Automated error budget calculation and management policies
Standardized SLI/SLO/SLA hierarchy for clear internal and external communication
Multi-window burn rate alerting logic to reduce false positives and alert fatigue
0 GitHub stars
Prometheus recording rules for availability, latency, and durability SLIs
Templated Grafana dashboard structures for real-time reliability visualization

ユースケース

Governing feature release velocity based on remaining error budget availability
Implementing SRE-based alerting to prioritize critical service degradations
Establishing measurable reliability targets for production microservices

概要

主な機能

Automated error budget calculation and management policies
Standardized SLI/SLO/SLA hierarchy for clear internal and external communication
Multi-window burn rate alerting logic to reduce false positives and alert fatigue
0 GitHub stars
Prometheus recording rules for availability, latency, and durability SLIs
Templated Grafana dashboard structures for real-time reliability visualization

ユースケース

Governing feature release velocity based on remaining error budget availability
Implementing SRE-based alerting to prioritize critical service degradations
Establishing measurable reliability targets for production microservices