DevOps was born of the notion that improving collaboration between developers and operators would lead to better business outcomes. Site Reliability Engineering (SRE) is a set of principles, practices, and organizational constructs that seek to balance the reliability of a service with the need to continually deliver new features.

Error Budgets are the primary construct used in the practice of SRE to help balance speed and reliability, seemingly competing goals.

This talk introduces error budgets and their components: service level indicators (SLIs) and service level objectives (SLOs). Practical, real-world examples of error budgets and their impact on an organization will be included.

By the end of this presentation, participants will be able to:
• Describe the principles of SRE
• Describe the key concepts presented, namely, Error Budget, Service Level Indicator (SLIs), and Service Level Objectives (SLOs)
• Recommend actions to take when the error budget is over consumed
• Recommend actions to take when excess error budget remains
• Describe how an error budget encourages cross-team collaboration

Error Budgets provide a quantifiable framework that enables collaboration toward a common goal: happy customers.