SRE / Basic: promises and measurements
SRE β Basic: promises and measurements
Define user risk, trustworthy events, objectives, budgets, telemetry, and toil.
What you will learn
- Write an SLI contract and interpret an SLO.
- Connect budgets and signals to user impact.
Reliability as a user and engineering decision
Connect service reliability to a specific user journey, a bounded risk decision, and shared engineering ownership before choosing reliability tools.
Start learningSLIs and trustworthy event contracts
Define good and eligible events so a ratio describes user experience and remains interpretable when instrumentation or traffic changes.
Start learningSLO windows and latency distributions
Choose a measurable target and time window, and explain why latency objectives need event thresholds rather than averages alone.
Start learningError budgets and release decisions
Translate an agreed reliability objective into a finite budget and a policy that changes engineering decisions when reliability deteriorates.
Start learningTelemetry for user impact and diagnosis
Connect traffic, errors, latency, and saturation to a user-facing symptom, using bounded labels and complementary evidence rather than a wall of charts.
Start learningToil reduction and safe automation
Distinguish recurring operational effort from engineering improvement, then design bounded automation that reduces work without hiding unsafe decisions.
Start learning