Why should I use multi-window burn rate alerts?

Multi-window alerts significantly reduce alert fatigue by requiring both a short-term spike and a sustained error rate before triggering, ensuring only meaningful incidents reach on-call engineers.

What is the difference between an SLI and an SLO?

An SLI (Service Level Indicator) is the specific quantitative measure of a service's performance, such as latency or availability, while an SLO (Service Level Objective) is the target value or range for that measure.

Can I use this with Prometheus and Grafana?

Yes, the skill includes specific PromQL recording rules and dashboard structures designed to be implemented directly in Prometheus and visualized in Grafana.

How does this skill help with error budgets?

It provides standardized formulas and implementation policies to calculate and track remaining error budgets, helping teams decide when to prioritize stability over new features.

SLO Implementation & SRE Framework

Name: SLO Implementation & SRE Framework
Author: HermeticOrmus

byHermeticOrmus

•

分析与监控

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

The SLO Implementation skill provides a comprehensive framework for Site Reliability Engineering (SRE) practices within Claude Code. It enables developers to define critical Service Level Indicators, set realistic Service Level Objectives, and calculate error budgets to balance service stability with development velocity. With built-in Prometheus recording rules, Grafana dashboard structures, and multi-window burn rate alerting patterns, this skill streamlines the process of measuring user-perceived reliability and automating responses to service degradation, ensuring your infrastructure meets business requirements without sacrificing innovation.

主要功能

01Pre-structured Grafana dashboard queries for real-time observability

02Prometheus recording rules for automated availability and latency metrics

03Multi-window burn rate alerting patterns to minimize false positives

04Error budget calculation formulas and management policy templates

052 GitHub stars

06Standardized SLI/SLO/SLA hierarchy definition and documentation

使用场景

01Implementing SLO-based alerting to replace noisy threshold-based alerts

02Managing development velocity by tracking remaining error budgets

03Establishing internal reliability targets for production microservices

主要功能

01Pre-structured Grafana dashboard queries for real-time observability

02Prometheus recording rules for automated availability and latency metrics

03Multi-window burn rate alerting patterns to minimize false positives

04Error budget calculation formulas and management policy templates

052 GitHub stars

06Standardized SLI/SLO/SLA hierarchy definition and documentation

使用场景

01Implementing SLO-based alerting to replace noisy threshold-based alerts

02Managing development velocity by tracking remaining error budgets

03Establishing internal reliability targets for production microservices