This course introduces a range of practices for advancing service reliability engineering through a mixture of automation, organizational ways of working and business alignment. Tailored for those focused on large-scale service scalability and reliability.


* Actual course outline may vary depending on offering center. Contact your sales representative for more information.

Learning Objectives

After completing this course, students will have learned:

Practical view of how to successfully implement a flourishing SRE culture in your organization.
The underlying principles of SRE and an understanding of what it is not in terms of anti-patterns, and how you become aware of them to avoid them.
The organizational impact of introducing SRE.
Acing the art of SLIs and SLOs in a distributed ecosystem and extending the usage of Error Budgets beyond the normal to innovate and avoid risks.
Building security and resilience by design in a distributed, zero-trust environment.
How do you implement full stack observability, distributed tracing and bring about an Observability-driven development culture?
Curating data using AI to move from reactive to proactive and predictive incident management. Also, how you use DataOps to build clean data lineage.
Why is Platform Engineering so important in building consistency and predictability of SRE culture?
Implementing practical Chaos Engineering.
Major incident response responsibilities for a SRE based on incident command framework, and examples of anatomy of unmanaged incidents.
Perspective of why SRE can be considered as the purest implementation of DevOps
SRE Execution model
Understanding the SRE role and understanding why reliability is everyone’s problem.
SRE success story learnings

  • SRE Anti-patterns

  • Rebranding Ops or DevOps or Dev as SRE

    Users notice an issue before you do

    Measuring until my Edge

    False positives are worse than no alerts

    Configuration management trap for snowflakes

    The Dogpile: Mob incident response

    Point fixing

    Production Readiness Gatekeeper

    Fail-Safe really?

  • SLO is a Proxy for Customer Happiness

  • Define SLIs that meaningfully measure the reliability of a service from a user’s perspective

    Defining System boundaries in a distributed ecosystem for defining correct SLIs

    Use error budgets to help your team have better discussions and make better data-driven decisions

    Overall, Reliability is only as good as the weakest link on your service graph

    Error thresholds when 3rd party services are used

  • Building Secure and Reliable Systems

  • SRE and their role in Building Secure and Reliable systems

    Design for Changing Architecture

    Fault tolerant Design

    Design for Security

    Design for Resiliency

    Design for Scalability

    Design for Performance

    Design for Reliability

    Ensuring Data Security and Privacy

  • Full-Stack Observability

  • Modern Apps are Complex & Unpredictable

    Slow is the new down

    Pillars of Observability

    Implementing Synthetic and End user monitoring

    Observability driven development

    Distributed Tracing

    What happens to Monitoring?

    Instrumenting using Libraries an Agents

  • Platform Engineering and AIOPs

  • Taking a Platform Centric View solves Organizational scalability challenges such as fragmentation, inconsistency and unpredictability.

    How do you use AIOps to improve Resiliency

    How can DataOps help you in the journey

    A simple recipe to implement AIOps

    Indicative measurement of AIOps

  • SRE & Incident Response Management

  • SRE Key Responsibilities towards incident response

    DevOps & SRE and ITIL

    OODA and SRE Incident Response

    Closed Loop Remediation and the Advantages

    Swarming – Food for Thought

    AI/ML for better incident management

  • Chaos Engineering

  • Navigating Complexity

    Chaos Engineering Defined

    Quick Facts about Chaos Engineering

    Chaos Monkey Origin Story

    Who is adopting Chaos Engineering

    Myths of Chaos

    Chaos Engineering Experiments

    GameDay Exercises

    Security Chaos Engineering

    Chaos Engineering Resources

  • SRE is the Purest form of DevOps

  • Key Principles of SRE

    SREs help increase Reliability across the product spectrum

    Metrics for Success

    Selection of Target areas

    SRE Execution Model

    Culture and Behavioral Skills are key

    SRE Case study

  • Post-class assignments/exercises

  • Non-abstract Large Scale Design (after Day 1)

    Engineering Instrumentation- Instrumenting Gremlin (after Day 2)


The target audience for the SRE Foundation course are professionals including: 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




It is highly recommended that learners attend the SRE Foundation course and earn the SRE Foundation certification prior to attending the SRE Practitioner course and exam. An understanding and knowledge of common SRE terminology, concepts, principles and related work experience are recommended.


Length: 3.0 days (24 hours)


Not Your Location? Change

Course Schedule:

Schedule select
9:00 AM ET -
5:00 PM ET