SLO (Service Level Objective)
In one line
SLO is a reliability target (e.g., 99.9% uptime) that guides how much effort to spend on reliability vs new features.
In simple words
A Service Level Objective (SLO) is a specific, measurable reliability target. For example: 99.9% of API requests succeed within 200ms over 30 days. SLOs guide engineering decisions.
Key concepts: SLI (measurement), SLO (target), SLA (contract), Error budget (allowed failures = 1 - SLO). For 99.9%, you can fail 0.1% of the time.
Error budget: under budget → ship features. Over budget → focus on reliability. This creates a data-driven balance.
Example
const slo = { target: 0.999, window: '30d' };
async function checkSLO() {
const total = await getMetric('requests_total', '30d');
const errors = await getMetric('requests_errors', '30d');
if (errors / total > 1 - slo.target) alert('SLO violated! Stop features.');
}SLO target is 99.9%. Error budget (0.1%) allows some failures. Over budget → stop features and fix reliability. Under budget → ship features.
Common confusions
Confused with: SLA
The difference: SLO is an internal target set by the team to guide engineering. SLA is an external contract with customers with consequences (refunds). SLO is stricter than SLA — you want margin.
Related terms
Related Resources
Related Lessons
- SRE
SLOs.
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.