Balance features and reliability
The error budget decides objectively.
Observabilité · Courses
SRE in practice: SLIs, SLOs and error budgets
Hands-on Site Reliability Engineering (SRE) course: define SLIs and SLOs, steer with the error budget, alert on burn rate and generate your SLOs with Sloth and Pyrra on Prometheus.
At your pace, through practice.By the end of this course you will be able to
- Distinguish SLIs, SLOs and SLAs and choose relevant indicators
- Calculate an error budget and write a budget policy
- Measure SLIs with Prometheus
- Set up multiwindow burn rate alerts
- Generate and track SLOs with Sloth and Pyrra
LEARNING PATH
Course curriculum
0Course overview1 lesson
1SRE fundamentals2 lessons
SLIs, SLOs, SLAs and the number of nines.
2The error budget1 lesson
Calculation, policy and windows.
3Measuring with Prometheus2 lessons
4Burn rate alerts2 lessons
Multiwindow, multi-burn-rate alerts.
5Tools: Sloth and Pyrra2 lessons
Generate and track your SLOs.
6Best practices2 lessons
Recommended practices for running the product in production.
LEARN BY DOING
Use cases & applications
Reduce on-call noise
One or two burn rate alerts per service.
Report on reliability
Figures shared with product and management.
Prepare an SLA
Measure before you commit.
Recommended prerequisites
What next?
Frequently asked questions
What is the difference between an SLO and an SLA?
The SLO is a measured internal objective; the SLA is a contractual commitment with penalties. The SLO is stricter than the SLA.
Should you aim for 100% availability?
No: it is impossible and very expensive. You set an objective that matches user expectations and use the margin as a budget.
What is a burn rate?
The speed at which the error budget is consumed: 1 exhausts it exactly over the window, 14.4 in just over two days out of 30.
Sloth or Pyrra?
Both generate equivalent Prometheus rules; Pyrra adds a web interface, Sloth a simple CLI and Grafana dashboards.