SLA, SLO, SLI
| Term | Google SRE definition, simplified | Example |
|---|---|---|
| SLI | a measure of the service level | share of requests answered in under 300 ms |
| SLO | a target for an SLI | 99.9% of requests under 300 ms per month |
| SLA | a contract with users, with consequences | credits if uptime drops below 99.9% |
The Google SRE book defines an SLA as “an explicit or implicit contract with your users that includes consequences of meeting (or missing) the SLOs they contain”. Some help desks also use SLA for response-time targets on tickets.
Quick math people ask for
99.9% uptime over a 30-day month allows about 43 minutes of downtime (0.1% of 43,200 minutes); 99.99% allows about 4 minutes.
Phrases you will hear
| Example | What it means |
|---|---|
| Are we still within our SLA this month? | Have we broken the promise? |
| This outage might breach the SLA. | Risk of consequences |
| Let's set the SLO a bit tighter than the SLA. | Internal target stricter than the promise |
| The support SLA for P1 tickets is four hours. | Response-time promise |
Practice free in the browser: pull request phrases and technical English phrases.
Learn the phrases around the word
Knowing what an acronym means is step one; using it naturally in a standup or a Slack thread is step two. Devlingo, Gambit Studio's English for developers app, has over 3,600 phrases for standups, code review, Slack, email, meetings and pull requests, ten new ones a day with real context and pronunciation guidance, plus a widget with the phrase of the day.