What is the difference between an SLI and an SLO?

An SLI (Service Level Indicator) is a quantitative measure of a service's performance, like latency. An SLO (Service Level Objective) is the target value you want that SLI to meet, such as 99.9% availability.

Can I use this for non-Prometheus environments?

Yes. While the code examples focus on Prometheus and PromQL, the framework, hierarchy, and logic for defining reliability targets are applicable to any monitoring stack.

How does this skill help with alerting noise?

It provides templates for multi-window burn rate alerts, which are an SRE best practice designed to trigger for significant reliability threats while ignoring transient spikes that don't threaten the overall SLO.

What is an error budget policy?

It is a set of pre-agreed actions to take based on how much of your error budget remains, such as freezing new feature deployments if the budget is exhausted to focus on stability.

SLO Implementation & Monitoring

Name: SLO Implementation & Monitoring
Author: HermeticOrmus

byHermeticOrmus

分析と監視

Defines and implements Service Level Indicators (SLIs) and Objectives (SLOs) to manage service reliability and error budgets effectively.

概要

This skill provides a comprehensive framework for implementing Site Reliability Engineering (SRE) practices by establishing measurable reliability targets. It guides users through defining SLIs for availability and latency, setting realistic SLO targets based on business needs, and calculating error budgets to balance innovation with stability. With built-in support for Prometheus recording rules and multi-window alerting strategies, it enables teams to move beyond basic uptime monitoring to sophisticated, user-centric reliability management that aligns technical performance with business goals.

主な機能

Error budget calculation and policy management frameworks
Prometheus recording rule generation for SLO compliance and burn rates
Multi-window burn rate alerting to reduce false positives
0 GitHub stars
Grafana dashboard structures for visualizing reliability trends
Standardized templates for Availability, Latency, and Durability SLIs

ユースケース

Configuring SLO-based alerting for production microservices
Balancing feature development velocity with system stability requirements
Establishing SRE practices within a DevOps or Platform Engineering team

概要

主な機能

Error budget calculation and policy management frameworks
Prometheus recording rule generation for SLO compliance and burn rates
Multi-window burn rate alerting to reduce false positives
0 GitHub stars
Grafana dashboard structures for visualizing reliability trends
Standardized templates for Availability, Latency, and Durability SLIs

ユースケース

Configuring SLO-based alerting for production microservices
Balancing feature development velocity with system stability requirements
Establishing SRE practices within a DevOps or Platform Engineering team