How does this skill help with error budgets?

The skill provides mathematical formulas and policy templates to calculate your remaining error budget and provides a framework for deciding when to prioritize reliability work over new feature development.

Can I use this with Prometheus and Grafana?

Yes, this skill includes specific PromQL recording rules, alerting configurations for Prometheus, and structural guidance for building SLO monitoring dashboards in Grafana.

What is the difference between an SLI and an SLO?

An SLI (Service Level Indicator) is a specific quantitative measurement of service performance, such as latency or availability. An SLO (Service Level Objective) is a target value or range for that measurement, representing the level of reliability required by users.

What are multi-window burn rate alerts?

They are advanced alerting configurations that look at multiple time windows simultaneously (e.g., 1-hour and 5-minute windows) to identify significant reliability issues quickly while filtering out transient spikes that don't threaten the overall SLO.

SLO Implementation Framework

Name: SLO Implementation Framework
Author: Microck

byMicrock

•

分析と監視

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

This skill provides a comprehensive framework for Site Reliability Engineering (SRE) practices, focusing on the definition and implementation of SLIs, SLOs, and error budgets. It guides users through creating Prometheus recording rules, multi-window burn rate alerts, and Grafana dashboards to balance system reliability with innovation velocity. By utilizing this skill, teams can move from reactive incident response to proactive, data-driven reliability management based on user-perceived performance and business requirements.

主な機能

01Standardized SLI/SLO/SLA hierarchy and definition patterns

02Visual dashboard structures for tracking compliance and error budget trends

03Multi-window burn rate alerting to minimize false positives and alert fatigue

04Prometheus-based recording rules for availability, latency, and durability

05Error budget calculation formulas and enforcement policy templates

062 GitHub stars

ユースケース

01Implementing error budget-based development velocity and freeze policies

02Establishing service reliability targets for production-grade environments

03Automating SLO-driven alerting and reporting for SRE and DevOps teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add microck/opendots-microck slo-implementation

For use in Claude.ai and ChatGPT

Download Skill