What is the difference between SLIs, SLOs, and SLAs?

SLIs (Indicators) are the actual metrics measured, SLOs (Objectives) are internal targets for those metrics, and SLAs (Agreements) are the external contracts with customers regarding service performance.

How does this skill help with Prometheus monitoring?

The skill provides specific PromQL queries and YAML configuration for recording rules and alerting rules, specifically focused on calculating compliance and burn rates.

What are multi-window burn rate alerts?

They are sophisticated alerting rules that combine short-term and long-term windows to identify significant reliability issues quickly while ignoring minor, transient spikes that cause alert fatigue.

How is an error budget calculated?

An error budget is calculated as 1 minus the SLO target. For example, a 99.9% availability SLO leaves a 0.1% error budget for planned or unplanned downtime.

SLO Implementation Framework

Name: SLO Implementation Framework
Author: lingxling

bylingxling

•

Analytics & Monitoring

Implements and manages service reliability targets through SLIs, SLOs, and error budgets to balance system stability with development velocity.

This skill provides a comprehensive framework for Site Reliability Engineering (SRE) practices by helping teams define, implement, and track Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets. It offers actionable templates for Prometheus recording rules, multi-window burn rate alerts, and Grafana dashboard structures, enabling developers to measure user-perceived reliability and make data-driven decisions about release cycles. By aligning technical metrics with business goals, it helps organizations maintain high availability while sustaining a rapid pace of innovation.

Key Features

01Error budget calculation formulas and management policies

02Multi-window burn rate monitoring for reduced alert fatigue

0352 GitHub stars

04Standardized SLI definitions for availability, latency, and durability

05Pre-configured Prometheus recording and alerting rules

06SLO target setting with downtime-to-percentage conversion mapping

Use Cases

01Defining measurable reliability targets for production microservices

02Implementing automated alerting based on error budget consumption

03Establishing feature freeze policies based on remaining error budgets

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lingxling/awesome-skills-cn slo-implementation

For use in Claude.ai and ChatGPT

Key Features

01Error budget calculation formulas and management policies

02Multi-window burn rate monitoring for reduced alert fatigue

0352 GitHub stars

04Standardized SLI definitions for availability, latency, and durability

05Pre-configured Prometheus recording and alerting rules

06SLO target setting with downtime-to-percentage conversion mapping

Use Cases

01Defining measurable reliability targets for production microservices

02Implementing automated alerting based on error budget consumption

03Establishing feature freeze policies based on remaining error budgets

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lingxling/awesome-skills-cn slo-implementation

For use in Claude.ai and ChatGPT