Measuring Reliability for Site Reliability Engineers
Measuring reliability means turning user experience into numbers. A service level indicator (SLI) is a measured signal, a service level objective (SLO) is the target for it, and the error budget is the allowed shortfall. Toil is repetitive manual work that SREs aim to reduce. Together they let teams make data-driven decisions about releases.
Stage: Principles · Part of the Site Reliability Engineer roadmap · Last reviewed 19 November 2026
What to learn in Measuring Reliability
- Choose SLIs such as request success ratio and latency percentiles for a service
- Set an SLO and compute the matching error budget over a 28 or 30 day window
- Define an error budget policy that slows releases when the budget is spent
- Tell an SLO from an SLA and know who each is for
- Identify toil in daily work and rank it by automation value
Measuring Reliability interview questions
What is an error budget and how is it used?
It is the amount of unreliability an SLO permits, for example 0.1 percent of requests for a 99.9 percent target. While budget remains, teams can ship changes. When it is exhausted, the policy shifts effort toward stability work until reliability recovers.
What is the difference between an SLI, SLO and SLA?
An SLI is a measurement, like the fraction of successful requests. An SLO is an internal target for that measurement. An SLA is a contract with customers that carries consequences, such as credits, if it is missed, and is usually less strict than the SLO.
Where Measuring Reliability fits in the Site Reliability Engineer roadmap
Measuring Reliability belongs to the Principles stage (intermediate level), which takes about 40 hours. How SRE thinks about reliability.
Other units in this stage
Back to the full Site Reliability Engineer roadmap