Course description:

Day 1:

• SRE Practitioner course introduction
• Module 1: 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?)
• Module 2: 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)
• Module 3: 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)

Day 2:

• Module 4: 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)
• Module 5: 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)
• Module 6: 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)

Day 3:

• Module 7: 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)
• Module 8: 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)
• SRE Foundation mock exam
• Exam tips and tricks
• Course summary

During the training, participants perform practical assignments to facilitate understanding of the topics discussed.

Additional information:

In the price of the training, the participant receives

• A set of accredited SRE Practitioner training materials
• DevOps dictionary
• Value added resource: videos, case studies, articles, books
• Exam specification
• SRE Practitioner sample exams with answers and rationales

Mandatory addition:

• Voucher for SRE Practitioner exam.

Training organization

• Type of training: public or in-house
• Form of delivery: on-site or remote (instructor-led live online classes)
• Training language: English
• Material language: English
• Group size: up to 14 participants

On-site training organization

• The workday will run from 9:00am to 5:00pm CET
• A set of accredited training materials is distributed electronically

Remote training organization

• Each participant should register for a remote training session between 8:30-8:50am CET
• The workday will run from 9:00am to 3:30pm CET
• There will be several breaks during the working day, including a 60-minute lunch break and 10-minute coffee breaks after each hour of training
• A set of accredited training materials is distributed electronically

Accreditation granted to Asseco Data Systems S.A. (Asseco Academy) by DevOps Institute & PeopleCert.