SLA defines the level of service expected between a service provider and end user. SRE combines software engineering practices with operations work to ensure site reliability. The document discusses monitoring metrics like CPU and disk utilization to ensure systems are working properly. It emphasizes being proactive, continuously improving processes, and having a team approach to meet SLAs and maintain high reliability.

1. DevopsHQ #2017
SLAs & SREs

3. SLA - Service Level Agreement
is a contract between a service provider (either internal or external)
and the end user that defines the level of service expected from the
service provider. SLAs are output-based in that their purpose is
specifically to define what the customer will receive.

4. SRE - Site Reliability Engineering
Google’s mastermind behind SRE, Ben Treynor, still hasn’t published
a single-sentence definition, but describes site reliability as “what
happens when a software engineer is tasked with what used to be
called operations.”

8. THINK!
THINK!
THINK!

9. What to take note?
- People are not generally evil, but busy
- Consider time
- Consider stress
- Consider benefits
- Consider rewards
- Help people be great on their job

10. Improvement
- Post-Mortems
- Communication
- Collaboration
- Ownership
- Standardization
- Policy
- ISMS (Optional)
>>> LOOP

12. MONITOR!
MONITOR!
MONITOR!

13. UP/RESPONSE

14. OPS METRICS
- CPU Utilization
- Memory Utilization
- Disk Utilization
- Process Monitoring
- Webserver Processes
- DB server Processes
- Custom Script Processes
- UPTIME

17. HOW DO WE KNOW IF EVERYTHING WORKS?

18. 500/502/504
200/206/
404/403
302/304

19. To the rescue: CDN

20. HOW DO WE KNOW IF EVERYTHING WORKS?

22. HOW DO WE KNOW IF EVERYTHING WORKS?

23. 500/502/504
200/206/
404/403
302/304

25. Working as SRE, everything on your metric/stats count.
SLA is hard to maintain, it takes a badass SRE (not just one but a team) to get
things rolling.
- Always be proactive
- Always improve
- Always be ready

26. @NeilUpbeta01 | upbeta01@gmail.com