Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.

SLO Implementation Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets. Purpose Implement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity. When to Use Define service reliability targets Measure user perceived reliability Implement error budgets Create SLO based alerts Track reliability goals SLI/SLO/SLA Hierarchy Defining SLIs Common SLI Types 1. Availability SLI 2. Latency SLI 3. Durability SLI Reference: See references/slo definitions.md Setting SLO Targets Availability SLO Examples SLO % Downtime/Month Downtime/Year 99% 7.2 hours 3.65 days 99.9% 43.2 minutes 8.76 hours 99.95% 21.6 minutes 4.38 hours 99.99% 4.32 minutes 52.56 minutes Choose Appropriate SLOs Consider: User expectations Business requirements Current performance Cost of reliability Competitor benchmarks Example SLOs: Error Budget Calculation Error Budget Formula Example: SLO: 99.9% availability Error Budget: 0.1% = 43.2 minutes/month Current Error: 0.05% = 21.6 minutes/month Remaining Budget: 50% Error Budget Policy Reference: See references/error budget.md SLO Implementation Prometheus Recording Rules SLO Alerting Rules SLO Dashboard Grafana Dashboard Structure: Example Queries: Additional patterns and templates More detailed templates and worked examples live in references/details.md . Read that file for the full pattern library.

slo-implementation