The Site Reliability Engineer path
The reliability path. You start from production Linux and networking, build real observability, then learn to define SLOs, alert on burn rate, run an incident and turn it into lasting fixes. Incidents along the way are the on-call reps.
Who it is for
Engineers joining an on-call rotation, operations engineers moving into SRE, and developers who want to understand how their services fail.
Milestones
-
01
Production Linux under pressure
The host-level skills and the calm, methodical loop that every incident starts with.
- ModuleLinux Essentials 34 lessons
- ModuleTroubleshooting Mindset 6 lessons
- IncidentStorefront Stuck in Maintenance Mode
- IncidentBackup Pager Fires After Every Run
-
02
Networks that fail in interesting ways
Bad host entries, proxies and stale DNS: the classic outage shapes.
- ModuleNetworking Fundamentals 8 lessons
- IncidentStorefront API Calls Fail
- IncidentOutbound CLI Requests Fail
- IncidentInternal API Hostname Does Not Resolve
-
03
See the system
Logs, metrics, dashboards and traces, wired so the next outage explains itself.
- ModuleLogging Foundations 11 lessons
- ModulePrometheus Metrics 6 lessons
- ModuleGrafana Dashboards & Visualization 6 lessons
- ModuleDistributed Tracing & APM 6 lessons
-
04
SLOs and error budgets
Turn reliability into a number the whole team can plan against.
- LessonSLIs, SLOs, & Error Budgets in Infrastructure Reliability
- ModuleSLO Operations 9 lessons
- LessonSLO Alerting in SLO Operations
- ModuleMetrics Engineering 9 lessons
-
05
Own the pager
Alert routing, runbooks and the first fifteen minutes of an incident.
- ModuleAlerting & Incident Response 6 lessons
- ModuleObservability Field Guide 9 lessons
- IncidentIncident Notes Service Fails to Start
- IncidentDatabase Backup Archive Is Missing
-
06
Learn from every incident
Timelines, MTTR and action items that make the next outage shorter.
- ModuleIncident Analytics 15 lessons
- ModuleInfrastructure Ops Lab 3 lessons
- AssessmentMonitoring & Observability track final