Becoming SRE by David N. Blank-Edelman

Author:David N. Blank-Edelman
Language: eng
Format: epub
Publisher: O'Reilly Media, Inc.
Published: 2024-02-19T00:00:00+00:00

Are they willing to gate new releases based on missed service level objectives?

Are they willing to actively work toward making sure postincident reviews are not perfunctory?

Is their on-call schedule humane such that the work is sustainable?

Are SREs in the right meetings early in the development process?

Do SREs have direct access to resources like source code repositories, which would allow them to make changes to improve reliability?

I can keep going like this, but you get the idea. Quick observation: none of these questions are fundamentally technical in nature.

When I talk to organizations that are brand new to SRE, I discuss SLIs and SLOs, but I seldom go into detail about error budgets. I make this choice because “real” error-budget implementations have policies attached to them—policies that specify what the organization will do when the budget is exceeded or, more importantly, when it is depleted. This policy has to be agreed upon before they get to this point (and actually held to when they are there) because that’s one of the clearest places where the reliability rubber meets the reliability road.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.