Site Reliability Practices for DevOps Engineers
Site reliability practices are methods for running services dependably. Service level indicators measure behaviour, service level objectives set targets, and error budgets show how much unreliability is acceptable. The practice also includes blameless incident response, postmortems, chaos engineering to test failure handling, and capacity planning.
Stage: Observability and Reliability · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Site Reliability Practices
- Define an SLI and an SLO for a user-facing service
- Calculate an error budget and what it allows in a month
- Run an incident with roles, communication and a timeline
- Write a blameless postmortem with actions
- Plan a small chaos experiment with a hypothesis and a stop condition
- Forecast capacity needs from traffic growth
Site Reliability Practices interview questions
What is an error budget?
An error budget is the allowed amount of unreliability, equal to 100 percent minus the SLO. A 99.9 percent monthly SLO allows about 43 minutes of failure. While budget remains teams can ship quickly, and when it is spent they prioritise reliability.
Why are postmortems blameless?
Blame makes people hide information and avoid reporting problems. A blameless postmortem focuses on system and process causes, such as missing alerts or unsafe defaults, so the team learns and fixes weaknesses instead of punishing individuals.
Where Site Reliability Practices fits in the DevOps Engineer roadmap
Site Reliability Practices belongs to the Observability and Reliability stage (advanced level), which takes about 1 hours. Know what is happening and respond well.
Other units in this stage
Back to the full DevOps Engineer roadmap