sre-slos

Topics in the source

• SRE SLOs
• Quick Start
• Key Concepts
• When to Use
• Step-by-Step
• Examples
• Best Practices
• Troubleshooting

Implement Service Level Indicators, Objectives, and Agreements following SRE best practices. SLIs measure service reliability (latency, availability, durability). SLOs set targets (e.g., 99.9% availability over 28 days). Error budget = (1 - SLO) × total events. Use burn rate alerts for early detection. Defining reliability expectations for services Making data-driven decisions about deployment velocity Balancing feature development with reliability investment 1. Pick service boundaries: define the user-visible promise (e.g., "API replies within 300ms p50, 99.9% available"). 2. Define SLIs as ratios: good events / valid events, per endpoint, aggregated over a rolling window. 3. Set SLO targets with error budgets: availability = 99.9% over 28 days → budget = 43 min of downtime. 4. Wire monitoring: export latency histograms and counters from Prometheus; compute SLIs with recording rules. 5. Add burn-rate alerts: page on 2h lookback at 14.4x budget consumption, ticket on 6h/1d windows. 6. Gate change velocity: pause deployments when remaining budget crosses the policy threshold (e.g., 20%). Define SLIs that measure real user experience, not internals. Set SLOs with error budgets and bu

This is an excerpt. Refer to the complete source and its current requirements.