service level objective
A target for a service level indicator over a time window, such as 99.9 per cent of checkouts succeeding over 30 days.
In more detail
The gap between the target and 100 per cent is the error budget. An SLO turns a vague wish for stability into a decision rule: while budget remains, the team can ship; when it is spent, reliability work comes first. Write it as a proportion of requests, never as an average.
Examples
99 per cent of checkouts complete in under half a second, measured over 30 days.In this course: Choose a percentile your users actually feel, not the one that makes the graph look calm, and investigate any breach before tuning the numbers. It is usually stated as a percentile over a time window, and the gap to one hundred per cent is the error budget.Related terms
- service level indicator — A measurement of how well a service is doing for users, usually good events divided by eligible events.
- service level agreement — An agreement with customers that promises a service level and states a consequence, such as a refund or service credit, if it is missed.
- error budget — The amount of failure an SLO allows over its window: one minus the target, for example 0.1 per cent of requests at 99.9 per cent.
- burn rate — How fast the error budget is being spent, compared with spending it exactly evenly over the SLO window.
- percentile — The value below which a given percentage of measurements fall; p99 latency is the time 99 in 100 requests beat.
- tail latency — The latency of the slowest requests, measured by high percentiles such as p99.
Taught in
- Finding The Problem: The Composite Alarm That Stayed Quiet — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- The Four Keys History And Retiring MTTR — DevOps & Site Reliability Engineering
- The Pitfalls Of Measurement — DevOps & Site Reliability Engineering
- Percentiles Rather Than Averages — DevOps & Site Reliability Engineering
- Service Level Objectives — DevOps & Site Reliability Engineering
- Service Level Agreements: The Consequence Discriminator — DevOps & Site Reliability Engineering
- Error Budgets — DevOps & Site Reliability Engineering
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
- Prometheus Scraping And The Pull Model — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Indicators — Full-Stack Observability: Metrics, Tracing & Logging
- Service Level Objectives — Full-Stack Observability: Metrics, Tracing & Logging
- Error Budgets And Burn Rate Alerts — Full-Stack Observability: Metrics, Tracing & Logging
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep
- Third-Party Risk: Choosing And Watching Vendors — CompTIA Security+ (SY0-801) Exam Prep
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Load Testing: Percentiles Over Means — Automated Testing, TDD & Quality Engineering
- The Customers Noticed First: SLAs, SLOs, Alerts, SNMP And Log Aggregation — CompTIA Linux+ (XK0-006) Exam Prep