# Service-Level Indicator

A service-level indicator is a quantitative measure of service behavior that represents an aspect of reliability experienced by users.

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

## What it means

A service-level indicator, or SLI, is a measured proportion or distribution that describes service performance from a user-relevant perspective. Common indicators cover successful requests, latency, freshness, durability, or correctness. An SLI needs a defined event population, a good-event rule, a measurement point, and a time window.

## Why it matters

Reliability discussions become vague when teams rely on impressions or infrastructure health alone. A well-designed SLI turns an important user experience into evidence that can support objectives, alerts, reviews, and trade-offs. It also exposes whether the telemetry actually observes what users depend on.

## When to use it

Define SLIs before setting reliability objectives or contractual commitments. Use them for critical journeys and service capabilities, especially where failure has several forms. Prefer a small set of meaningful indicators over a catalog that no one can interpret or act upon.

## How it works

1. Identify the user or system behavior that must remain dependable.
2. Choose eligible events, such as valid requests or scheduled data updates.
3. Define which events count as good using explicit success, latency, or correctness criteria.
4. Select a measurement point close enough to represent user experience.
5. Calculate good events divided by eligible events, or use an appropriate distribution, over a stated window.

## A practical example

For a search API, the team counts valid queries at the load balancer as eligible events. A query is good when it returns a non-error response within 800 milliseconds. The SLI is the percentage of eligible queries that meet both conditions during the rolling 28-day window.

## Where it breaks

An SLI is a model, not the experience itself. Server-side measurements may miss client failures, averages can hide tail latency, and exclusions can quietly make performance look better. Indicators also require stable instrumentation and periodic review as user journeys and architecture change.

## Common mistakes

- Measuring host health instead of a user-visible capability.
- Leaving the eligible population or good-event threshold ambiguous.
- Using averages that conceal severe experiences in the distribution.

## Visualization

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

## 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 Objective](<https://wiki.soroush.uk/topic/service-level-objective/>)
- [Service-Level Agreement](<https://wiki.soroush.uk/topic/service-level-agreement/>)
- [Observability](<https://wiki.soroush.uk/topic/observability/>)
