service level indicator
A measurement of how well a service is doing for users, usually good events divided by eligible events.
In more detail
Availability can be successful requests over eligible requests; latency can be requests under a threshold over all measured requests. The numerator and denominator must be defined together, and exclusions recorded explicitly. An SLI is evidence, not a target.
Examples
availability = successful requests / valid requests, over 30 daysGood: HTTP responses below 500 that finished under 0.5 s; eligible: all checkout requests except health checks.Related terms
- 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.
- availability — The share of time, or of requests, in which a service works for the people who need it, often written as a percentage such as 99.9 per cent.
- latency — The time between asking for something and getting the answer back.
- data freshness — How recently the data a user sees was updated.
- error rate — The share of requests that fail, reported alongside latency so a fast result is not mistaken for a healthy one.
- tail latency — The latency of the slowest requests, measured by high percentiles such as p99.
- 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.
- good events — In an SLI, the requests that met the standard (numerator) out of all the requests that count (eligible events, the denominator).
Taught in
- Service Level Indicators — 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
- Pipelines And GitOps Context — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
- 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
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- The Customers Noticed First: SLAs, SLOs, Alerts, SNMP And Log Aggregation — CompTIA Linux+ (XK0-006) Exam Prep