SLO (Service Level Objective)

A Service Level Objective is the reliability target your team manages to internally. It is expressed against one or more service level indicators over a defined window — for instance, 99.9% of requests succeeding over a rolling 30 days. Unlike an SLA, an SLO carries no contractual penalty; its job is to give engineering a clear, measurable bar that turns 'be reliable' into a decision-making tool.

Why it matters: the SLO is where reliability becomes operational. The gap between an SLO and 100% is the error budget — the unreliability you're allowed to spend on risky deploys, migrations, and experiments. When the budget is healthy you can ship aggressively; when it is nearly exhausted you slow down and prioritize stability. This makes the SLO a shared language between engineers and product.

A common misconception is that the right SLO is as close to 100% as possible. Chasing extra nines is exponentially expensive and often invisible to users whose networks and devices are already less reliable than your service. A good SLO reflects the level of reliability users actually need, not the highest number you can technically reach.

SLOs should be set deliberately below the SLA you promise customers, so an objective miss is a warning sign rather than a contract breach. They also need a defined measurement window — rolling windows behave very differently from calendar months when an incident lands at month-end.