The document provides an introductory overview of Site Reliability Engineering (SRE) and its relationship with DevOps, highlighting essential concepts such as Service Level Objectives (SLOs), Service Level Indicators (SLIs), and Service Level Agreements (SLAs). It emphasizes the importance of reducing toil, implementing on-call practices, and fostering a blameless postmortem culture in a production environment. The author, Daniel Uhlmann, shares insights from his expertise and experience in SRE and DevOps.

1. You want to start with SRE? Start with this talk.
Page 1 / 20

2. What can you expect
should you implement DevOps or SRE or both?
important components explained
fundamentals from a beginners perspective
Page 2 / 20

3. About me
Daniel Uhlmann
T-Systems Multimedia Solutions
GmbH
passion for Linux and OpenSource
Twitter: @xfuturecs
Blog: xfuture-blog.com
Page 3 / 20

4. What is Site Reliability Engineering?
Page 4 / 20

5. Still uncertain? Here is a real world example!
Page 5 / 20

6. Short recap about DevOps
Page 6 / 20

7. Which principles we add with SRE
reduce toil
embrace risks
observe distributed systems
SLIs SLOs and SLAs
Page 7 / 20

8. What is a SLO?
Service Level Objective
agreement within an SLA about a specific metric like uptime or response time
Page 8 / 20

9. What is a SLI?
Service Level Indicator
measures compliance with an SLO
SLIs are the real numbers of your performance
Page 9 / 20

10. What is a SLA?
Service Level Agreement
it's a contract between you and your customer
it includes consequences for missing (or meeting) the contained SLOs
Page 10 / 20

11. What is toil?
Toil is:
manual
repetitive
automatable
work, necessary to run a production service
Page 11 / 20

12. Not everything is toil
overhead work != toil
team meetings, HR paperwork etc. could have value so it's no toil
Page 12 / 20

13. Don't just ignore the toil
it can quickly fill 100% of everyone's time
you won't have time for the important work
Page 13 / 20

14. Less toil is better?
Page 14 / 20

15. New practices we add with SRE
on-call
effective troubleshooting
emergency response
learning from failure
Page 15 / 20

16. Emergency response
things break - that's normal
it's all about a predefined plan
if you feel overwhelmed = pull in more people
Page 16 / 20

17. Blameless Postmortem Culture
"The cost of failure is education."
Devin Carraway
Page 17 / 20

18. No dedicated SRE Team yet?
Page 18 / 20

19. Sources
https://sre.google/sre-book/table-of-contents/
https://www.ibm.com/cloud/learn/site-reliability-engineering
https://www.atlassian.com/incident-management/postmortem/blameless
https://pics.me.me/developers-devops-operations-what-the-hell-is-this-no-hate-
67656003.png
Page 19 / 20

20. Thank you for listening!
Page 20 / 20