Skip to content
BENIBIX Learn

Service Level Objective (SLO)

Infrastructure📟 ReliabilityService Levels

Also known as SLO, SLOs, Reliability Target

The goal a team sets for a number it measures. An example is 99.95% of requests working.

Think of it like

It is like the score you aim for on a test. You hope to get at least that much.

Example

Jack's team sets an SLO of 99.95% for logins each month. When the SLI drops to 99.96% mid-month, they slow down new releases.

Why it matters

It tells a team when things are fine and when they need work. It does this before users start to leave.

Definition

A service level objective is the target a team sets for one SLI. It says how good is good enough, like 99.95% of requests working over 30 days. It is an inside goal, not a promise to customers. It is set a little stricter than any contract. That way the team gets a warning before a promise is broken.
The SLO is the middle line. It is the team's own goal, set above the contract.

Common mistake

Aiming for 100%. No service gets there, and chasing it stops all change for very little gain.

Key takeaways

  1. 1
    One SLI, one target. Each goal names what it measures.
  2. 2
    Inside goal. Kept by the team, not signed with buyers.
  3. 3
    Stricter than the SLA. It warns before a promise is broken.

Compare