slo-implementation

# Skill: SLO Implementation > **Expertise:** Prometheus recording rules for SLOs, multi-window burn rate alerts, Sloth code generation, error budget Grafana panels. ## When to load When implementing SLOs for a service in Prometheus, setting up burn rate alerts, or creating error budget dashboards. ## Full SLO Stack (single service) ### Step 1: Define the SLI Recording Rules ```yaml # prometheus-rules/slo-checkout-service.yaml groups: - name: slo:checkout-service:recording interval: 30s rules: # Good requests: 2xx, latency < 500ms (combine availability + latency SLI) - record: slo:http_requests_good:rate5m labels: { service: checkout-service } expr: | sum(rate(http_requests_total{ service="checkout-service", status=~"2.." }[5m])) # For latency SLI, intersect with bucket: # sum(rate(http_request_duration_seconds_bucket{ # service="checkout-service", le="0.5"}[5m])) - record: slo:http_requests_total:rate5m labels: { service: checkout-service } expr: | sum(rate(http_requests_total{service="checkout-service"}[5m])) # SLI ratio (5m window) - record: slo:http_availability:ratio_rate5m labels: { service: checkout-service } expr: | slo:http_requests_good:rate5m{service="checkout-service"} / slo:http_requests_total:rate5m{service="checkout-service"} # Pre-compute multiple windows ...