Meet the Author
Reid Savage
Manager, Site Reliability Engineering
Reid went from consultant - migrating tens of startups into AWS while just out of college - to "DevOps Engineer", to SRE, and then Engineering Manager at Honeycomb where they find joy in the mire of ambiguity (then cutting through it). They spend their free time playing Soulslikes and projecting the pink V0 in the corner of the climbing gym.
Explore Author's Blog
Touching Grass With SLOs
One of the things that struck me upon joining Honeycomb was the seemingly laissez-faire approach we took towards internal SLOs. From my own research (beginning with the classic SRE book, following Google’s example), I came to these conclusions: -SLOs are strict. They aren’t as binding as an SLA, but burning through your error budget is bad. -SLOs/SLIs need to be documented somewhere, with a formal specification, and approved by stakeholders. -SLOs should drive customer-level SLAs. -Teams should be mandated to create a minimum number of SLOs for the services they own.