# Service-Level Objective

A service-level objective sets a target value for a service-level indicator over a defined period, expressing the intended reliability level.

- Type: metric
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/service-level-objective/>)

## What it means

A service-level objective, or SLO, is an internal reliability target attached to a specific service-level indicator and time window. A statement such as “99.9% of eligible requests succeed within 30 days” combines the measured behavior, target, and evaluation period. The permitted shortfall becomes an error budget.

## Why it matters

An SLO makes “reliable enough” discussable. It helps product, engineering, and operations choose between feature velocity and reliability work, calibrate alerting, and recognize harmful trends before every failure becomes a crisis. A target tied to user needs is more useful than pursuing maximum availability by habit.

## When to use it

Use SLOs for services and journeys whose reliability affects users, revenue, safety, or dependent teams. Establish measurement first, then choose a target informed by user expectations, business consequences, historical performance, and dependency limits. Start simple and revise deliberately.

## How it works

1. Select a user-centered SLI with trustworthy telemetry.
2. Choose a target and window that reflect meaningful expectations.
3. Confirm the objective is achievable given dependencies and architecture.
4. Track compliance and error-budget consumption, including burn rate.
5. Define actions for unusual consumption and review the target as needs change.

## A practical example

A document editor sets an objective that 99.95% of save attempts from active sessions complete successfully within one second over 28 days. Alerts focus on rapid budget burn. If failures consume half the monthly allowance in two days, the team pauses a risky storage migration and prioritizes recovery.

## Where it breaks

A single target can hide regional, device, or customer differences. An easy objective becomes decorative, while an impossible one creates permanent emergency. SLOs do not replace capacity planning, security, qualitative research, or judgment, and they should not be confused automatically with customer contracts.

## Common mistakes

- Choosing a target before defining and validating the indicator.
- Setting 100% as the default without considering cost or feasibility.
- Reporting compliance without an agreed response to budget consumption.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/service-level-objective/#visualization-service-level-objective>)

## Sources

1. [Service Level Objectives](<https://sre.google/sre-book/service-level-objectives/>) — Google Site Reliability Engineering · Foundational book chapter
2. [Implementing SLOs](<https://sre.google/workbook/implementing-slos/>) — Google Site Reliability Engineering · Institutional implementation guide

## Related topics

- [Service-Level Indicator](<https://wiki.soroush.uk/topic/service-level-indicator/>)
- [Error Budget](<https://wiki.soroush.uk/topic/error-budget/>)
- [Service-Level Agreement](<https://wiki.soroush.uk/topic/service-level-agreement/>)
