Service-Level Objective (SLO)
Definition
An SLO sets a target value for a measured service property.
An SLO is a target value or target range for an SLI over a defined period.
Simply explained
For a defined period, it is determined how reliable or fast a service should be.
Why it matters in practice
The term contributes to secure, maintainable, and high-performance web applications as well as resilient technical decisions.
Example from business
A team sets the goal for 30 days that 99.9 percent of valid API requests succeed.
Limits and pitfalls
- Too many or unrealistic goals promote alert fatigue; measurement windows and excluded requests must be clear.
Origin & history
SLOs have become widespread in Site Reliability Engineering as the basis for error budgets and resilient operational decisions.
Use in mid-sized companies
- Possible example: A team sets the goal that 99.9 percent of valid API requests are successful over 30 days.
Frequently asked questions
What is a service level objective?
A target value or target range for a metric over a defined period of time.
What is important in this context?
Realistic, manageable goals as well as clearly defined measurement windows and excluded requests.
Sources
- Site Reliability Engineering, Service Level Objectives · Google, Site Reliability Engineering, Service Level Objectives
Source checked on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: