skills.rest
Jhabbig
JhabbigCOMMUNITY
Explore all skills by this author →
GitHub

slo-implementation

Translates operational metrics into Prometheus-based SLIs, SLOs, and error budgets for web services and APIs.

Updated Apr 5, 2026
Search Tags:#observability#prometheus#alerting#error budget#slo#sli
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill slo-implementation-jhabbig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slo-implementation
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/observability-monitoring/skills/slo-implementation
Command: npx skills add https://github.com/Jhabbig/Habbig --skill slo-implementation-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams define measurable reliability targets instead of guessing at uptime, so they can balance product velocity with user trust and service stability.

Core Features & Use Cases

  • SLI Design: Choose availability, latency, or durability indicators that reflect real user experience.
  • SLO Planning: Set practical targets, calculate downtime allowances, and establish error budget policies.
  • Alerting and Reporting: Build burn-rate alerts, compliance checks, and dashboard views for ongoing reliability review.
  • Use Case: A platform team can use this Skill to turn raw request metrics into SLOs, error budget alerts, and a weekly reliability report for an API service.

Quick Start

Use this skill to define SLIs for your service, set a realistic SLO target, and generate the Prometheus rules and alerts needed to track error budget burn.

Frequently Asked Questions about slo-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define SLIs and SLOs for a web service using Prometheus metrics?▼

To define SLIs and SLOs, you translate raw Prometheus request metrics into availability and latency indicators, set practical reliability targets, and calculate downtime allowances to establish error budget policies. This provides measurable service reliability targets instead of guessing uptime.

What is an error budget and how do I track its burn rate?▼

An error budget is the allowable downtime or failed requests based on your SLO target. You track error budget burn rate by applying multi-window alert thresholds and recording rules to your Prometheus metrics, generating alerts when compliance drops and burn accelerates.

How do I create burn-rate alerts and compliance checks for API reliability?▼

You create burn-rate alerts by configuring Prometheus-style recording rules and multi-window alert thresholds on your service metrics. This generates dashboard-friendly SLO calculations and alerts for ongoing reliability review when API availability or latency degrades.

Does this SLO implementation approach work for production API monitoring workflows?▼

Yes, this SLO implementation applies directly to production web services and API monitoring workflows. It translates operational metrics into availability, latency, burn-rate, and compliance tracking specifically designed for environments using Prometheus-style metric expressions.

What is the best way to calculate downtime allowances for service reliability targets?▼

The best way to calculate downtime allowances is through SLO planning, where you set practical reliability targets based on your defined SLIs. This establishes clear error budget policies that help balance product velocity with user trust and service stability.

Related Skills

Explore More Software Engineering Skills→
ricardorochericardoroche
2

monitoring-alerting

Automate Prometheus/Grafana monitoring, alerting, and SLO/SLI definitions.

Community
Intermediate
TravisLeeeeeeTravisLeeeeee
110

SRE (Site Reliability Engineer)

Define SLOs, multi-window burn-rate alerts, and observability plans for production microservices.

Community
Advanced
PrepLabsAIPrepLabsAI
94

monitoring-alerting-interviewer

Design monitoring and alerting strategies using SRE principles and golden signals.

Official
Advanced
weirdgmeweirdgme
4

observability-engineering

Instrument distributed systems with OpenTelemetry and correlate logs, metrics, and traces.

Community
Advanced