SLO & SLI Templates

This template helps you document Service Level Objectives for your critical services, including SLI definitions, targets, and error budget policies.

Service Level Objective (SLO) Document

# SLO: [Service Name]

**Owner**: [Team/Person]
**Last Review**: [Date]
**Next Review**: [Date]

## Service Description
[What this service does and why it matters]

## SLIs (Service Level Indicators)

### 1. Availability SLI
**Definition**: Percentage of successful requests
**Measurement**: sum(requests{status!~"5.."}) / sum(requests) * 100
**Data Source**: [Prometheus/CloudWatch/etc.]

### 2. Latency SLI
**Definition**: 95th percentile response time
**Measurement**: p95 of request duration < 200ms
**Data Source**: [Monitoring system]

### 3. Error Rate SLI
**Definition**: Percentage of requests returning errors
**Measurement**: (5xx errors / total requests) * 100
**Data Source**: [Logging/metrics system]

## SLOs (Service Level Objectives)

| SLI | Target | Measurement Window | Error Budget |
|-----|--------|-------------------|--------------|
| Availability | 99.9% | 30 days | 0.1% (43 min) |
| Latency p95 | < 200ms | 7 days | 5% above threshold |
| Error Rate | < 0.1% | 30 days | 10 errors per 10k requests |

## Error Budget Policy

### Budget Remaining: > 75%
- ✅ Normal feature development velocity
- ✅ Accept reasonable risks in deployments
- ✅ Experiment with new features

### Budget Remaining: 50-75%
- ⚠️ Increase caution in changes
- ⚠️ Review deployment processes
- ⚠️ Defer risky features

### Budget Remaining: 25-50%
- 🛑 Focus on stability improvements
- 🛑 Limit feature work to low-risk changes
- 🛑 Increase monitoring and testing

### Budget Remaining: < 25%
- 🚨 Feature freeze
- 🚨 All hands on reliability
- 🚨 Root cause all recent incidents
- 🚨 Implement comprehensive fixes

## Dashboard Links
- [Production monitoring]
- [Error budget tracking]
- [SLO compliance reports]