Site Reliability Engineering: Service-Level Agreements and Objectives

Site Reliability Engineering: Service-Level Agreements and Objectives

42mIntermediate2019-09-16

Authors

Laura Stone

Laura Stone

Software Engineer

Course details

Software teams are expected to both maintain the quality of existing applications and innovate on new features that excite users. For engineering and operations teams, tackling both of these efforts on a deadline can be challenging. In this course, learn how to leverage error budgets and service-level indicators (SLIs), service-level objectives (SLOs), and service-level agreements (SLAs) to set realistic performance expectations and measure system performance within your organization. Instructor Laura Stone shows how to create SLIs to measure the reliability of a system, as well as how to make those SLIs meaningful with SLOs. Laura also shows how to use error budgets to ensure that poor service performance has consequences. To wrap up, she goes over the main components of SLAs.

Learning objectives
Service-level indicators and objectives
Defining reliability
Making measurements meaningful
Documenting service-level objectives
Setting up dashboards and reporting
Consequences of poor service performance
Creating an error budget
Service-level agreements

Skills covered

Customer Service ManagementCustomer ServiceServer AdministrationFoundationsNetwork and System Administration

Concepts

Introduction

  • Why measure service performance
  • What you should know

Service-Level Indicators

  • Defining reliability
  • Implementing measurements
  • Common measurements
  • Measurement and calculation

Service-Level Objectives

  • Objectives vs. indicators
  • Making measurements meaningful
  • Stakeholder agreement
  • Documenting SLOs
  • Dashboards and reporting
  • Continuous improvement

Error Budgets

  • Consequences of poor service performance
  • Creating an error budget
  • Drafting an error budget policy

Service-Level Agreements

  • Service-level agreements
  • Components of agreements

Conclusion

  • Next steps
40,000 Toman