Book Image

Becoming a Rockstar SRE

By : Jeremy Proffitt, Rod Anami
Book Image

Becoming a Rockstar SRE

By: Jeremy Proffitt, Rod Anami

Overview of this book

Site reliability engineering is all about continuous improvement, finding the balance between business and product demands while working within technological limitations to drive higher revenue. But quantifying and understanding reliability, handling resources, and meeting developer requirements can sometimes be overwhelming. With a focus on reliability from an infrastructure and coding perspective, Becoming a Rockstar SRE brings forth the site reliability engineer (SRE) persona using real-world examples. This book will acquaint you the role of an SRE, followed by the why and how of site reliability engineering. It walks you through the jobs of an SRE, from the automation of CI/CD pipelines and reducing toil to reliability best practices. You’ll learn what creates bad code and how to circumvent it with reliable design and patterns. The book also guides you through interacting and negotiating with businesses and vendors on various technical matters and exploring observability, outages, and why and how to craft an excellent runbook. Finally, you’ll learn how to elevate your site reliability engineering career, including certifications and interview tips and questions. By the end of this book, you’ll be able to identify and measure reliability, reduce downtime, troubleshoot outages, and enhance productivity to become a true rockstar SRE!
Table of Contents (27 chapters)
1
Part 1 - Understanding the Basics of Who, What, and Why
5
Part 2 - Implementing Observability for Site Reliability Engineering
10
Part 3 - Applying Architecture for Reliability
16
Part 4 - Mastering the Outage Moments
20
Part 5 - Looking into Future Trends and Preparing for SRE Interviews

First Thing – Runbooks and Low Noise Outage Notifications

Institutional knowledge is the experience and understanding that staff have about a company. From the long-standing engineers who wrote the code that runs the day-to-day business, to network engineers familiar with the topology of the data center, and even customer service representatives, who know how to leverage internal company processes to resolve customer issues. This employee understanding takes years to build in employees and can be difficult – if not impossible – to replace. Runbooks are the embodiment of institutional knowledge about applications and systems in a tangible document to aid in troubleshooting and resolving issues.

Runbooks may embody the knowledge needed to resolve issues, but we must combine them with alerts that tell us when an outage occurs. When I think of alerts, I’m always reminded of the boy who cried wolf – the story of a boy who is bored at night tending sheep...