Nathen Harvey
Developer Advocate, Google
Actions
Nathen Harvey, Cloud Developer Advocate at Google, helps the community understand and apply DevOps and SRE practices in the cloud. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps, and is part of the DevOps Days conferences global organizing committee.
Links
Error Budgets: A Quantifiable Framework for Dev and Ops Collaboration
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.
Site Reliability Engineering (SRE) and the Art of SLOs
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. An error budget is the primary construct used to help balance these seemingly competing goals.
This workshop introduces error budgets and their components: service level indicators (SLIs) and service level objectives (SLOs). Participants will learn the art of creating and implementing SLOs through a series of guided discussions and group exercises.
By the end of this workshop, participants will be able to:
• Describe the key concepts, namely, Error Budget, Service Level Indicator (SLIs), and Service Level Objectives (SLOs)
• Create an error budget for a sample application or service
• Create an error budget for their own application or service
• Recommend actions to take when the error budget is over consumed
• Recommend actions to take when excess error budget remains
In the spirit of DevOps, Error Budgets and SLOs work best when they are agreed to in collaboration with many different constituents across the business. As such, this workshop is appropriate for:
• Product Owners and Product Managers
• Business decision makers
• Developers
• Operators
• And anyone else interested in building and operating services that deliver business and customer value.
Bring along your colleagues from other parts of the organization, a high-level architecture of one of your main services, and an appetite for learning and collaboration.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top