The course highlights the evolution of SRE and its future direction, and equips participants with the practices, methods, and tools to engage people across the organization involved in reliability and stability evidenced through the use of real-life scenarios and case stories. Upon completion of the course, participants will have tangible takeaways to leverage when back in the office such as understanding, setting and tracking Service Level Objectives (SLO’s).
The course was developed by leveraging key SRE sources, engaging with thought-leaders in the SRE space and working with organizations embracing SRE to extract real-life best practices and has been designed to teach the key principles & practices necessary for starting SRE adoption.
The history of SRE and its emergence at Google
The inter-relationship of SRE with DevOps and other popular frameworks
The underlying principles behind SRE
Service Level Objectives (SLO’s) and their user focus
Service Level Indicators (SLI’s) and the modern monitoring landscape
Error budgets and the associated error budget policies
Toil and its effect on an organization’s productivity
Some practical steps that can help to eliminate toil
Observability as something to indicate the health of a service
SRE tools, automation techniques and the importance of security
Anti-fragility, our approach to failure and failure testing
The organizational impact that introducing SRE brings
Who should attend DevOps Site Reliability Engineering (SRE) Foundation Course
Target Audience
- Anyone starting or leading a move towards increased reliability
- Anyone interested in modern IT leadership and organizational change approaches
- Business Managers
- Business Stakeholders
- Change Agents
- Consultants
- DevOps Practitioners
- IT Directors
- IT Managers
- IT Team Leaders
- Product Owners
- Scrum Masters
- Software Engineers
- Site Reliability Engineers
- System Integrators
- Tool Providers
Prerequisites for DevOps Site Reliability Engineering (SRE) Foundation Course
DevOps Site Reliability Engineering (SRE) Foundation Course Outline
- What is Site Reliability Engineering?
- SRE & DevOps: What is the Difference?
- SRE Principles & Practices
- Service Level Objectives (SLO’s)
- Error Budgets
- Error Budget Policies
- What is Toil?
- Why is Toil Bad?
- Doing Something About Toil
- Service Level Indicators (SLI’s)
- Monitoring
- Observability
- Automation Defined
- Automation Focus
- Hierarchy of Automation Types
- Secure Automation
- Automation Tools
- Why Learn from Failure
- Benefits of Anti-Fragility
- Shifting the Organizational Balance
- Why Organizations Embrace SRE
- Patterns for SRE Adoption
- Sustainable Incident Response
- Blameless Post-Mortems
- SRE & Scale
- SRE & Other Frameworks
- SRE Evolution
- Sample Exam
Resources
FAQs on DevOps Site Reliability Engineering (SRE) Foundation
This course covers the fundamentals of Site Reliability Engineering (SRE), including its history at Google, core principles, Service Level Objectives (SLOs), error budgets, toil reduction, observability, automation, and anti-fragility. It also explores how SRE relates to DevOps and its organizational impact.
There are no required prerequisites. However, it is recommended that participants have an understanding of common DevOps terminology, related IT work experience, and general working knowledge in the DevOps field.
This course is ideal for IT managers, directors, DevOps practitioners, Site Reliability Engineers, Scrum Masters, software engineers, business stakeholders, and anyone leading or interested in reliability initiatives, organizational change, or modern IT leadership approaches.
Participants will learn the history and principles of SRE, how to define SLOs and SLIs, manage error budgets, reduce toil, implement observability and automation, foster anti-fragility, and understand the organizational changes needed to successfully adopt SRE.
The course explicitly addresses this comparison in its outline, exploring how SRE is both related to and distinct from DevOps, including how SRE practices complement other popular frameworks and evolve within modern IT organizations.


