TL112 – Red Hat Transformational Learning: Introduction to Pragmatic Site Reliability Engineering — Lesson 2: SLIs, SLOs, SLAs, Error Budgets, and Reliability Decision-Making

Learning Objectives

• Configure the principal services, objects, workflows, and controls for service-level indicators, service-level objectives, and service-level agreements.
• Apply error budgets and reliability decisions while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• service-level indicators: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• service-level objectives: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• service-level agreements: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• error budgets: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• reliability decisions: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates slis, slos, slas, error budgets, and reliability decision-making by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for SLIs, SLOs, SLAs, Error Budgets, and Reliability Decision-Making and add the verified result to the service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences service-level indicators in the stated scenario.
• Compare two approaches for error budgets and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior were checked and recorded.
• The normal path and a course-specific exception were tested.
• The service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply SLIs, SLOs, SLAs, Error Budgets, and Reliability Decision-Making, explain the observed platform behavior, and support the result with a reviewable service reliability charter, SLI and SLO register, error-budget policy, and improvement roadmap.