Service Level Terminology: SLI, SLO, and SLA
What you'll learn: How to distinguish between Service Level Indicators, Objectives, and Agreements — the three core terms that formalize reliability expectations.
When building dashboards and observability systems, you need a language to describe how reliable your service should be. These three terms form a hierarchy that moves from measurement to promise.
Service Level Indicator (SLI)
An SLI is a quantitative measurement of a service's behavior — the actual metric you observe. Think of it as your thermometer reading.
Examples:
- Request success rate:
99.5% - API latency P95:
250ms - Message processing throughput:
10,000 msg/sec
SLIs are the raw numbers from your metrics and traces — they answer "What did we just measure?"
Service Level Objective (SLO)
An SLO is your internal target for an SLI — the goal you set for your team. This is like saying "We want the temperature between 68-72°F."
Examples:
- "99.9% of requests should succeed" (availability SLO)
- "95% of API calls should complete in under 200ms" (latency SLO)
SLOs are what drive your dashboard thresholds, alerts, and error budgets. They're aspirational but realistic targets based on user needs, not contracts.
Service Level Agreement (SLA)
An SLA is a contractual promise to customers, often with financial consequences if violated. This is the legally binding thermostat setting in a lease.
Examples:
- "We guarantee 99.5% uptime monthly, or you receive a 10% credit"
SLAs are typically looser than SLOs (e.g., SLO of 99.9%, SLA of 99.5%) to give you an error budget cushion.
The Hierarchy
SLI (measurement) → SLO (internal goal) → SLA (external promise)
Your dashboard visualizes SLIs, compares them to SLOs, and helps you stay well above SLA thresholds.
Key Takeaway: SLIs measure what's happening, SLOs define what you aim for internally, and SLAs are the contractual promises you make to customers — each builds on the previous layer to create a reliability framework.