SLOs help you re-think how you achieve reliability.
THE CHEAT SHEET BOOK HOW TO
Here’s a bunch of tips about how to do that! You need to evangelize for this to work well. The whole SLO thing is as much cultural as it is anything else. So let’s make sure you can communicate using them WELL. Part of what SLOs do is help you communicate. Let’s talk about when and why they should!Ĭhapter 15: Discoverable and Understandable SLOs You need lessons and advice to help you and your team and your organization actually do this whole SLO thing instead of just talking about it. Let’s talk about an example company with exemplary service and how they do the whole SLO thing pretty well! Also, there are cute dog pictures in this one. Thinking about the reliability of data is waaaay different than thinking about other kinds of reliability, so here is a whole chapter about how to do that. Let’s talk about how you can make your new services more reliable by thinking about SLOs during the design phase. You probably don’t actually have the right data you need for this whole SLO thing. Threshold alerts are stupid! Here’s how to do something better!Ĭhapter 9: Probability and Statistics for SLIs and SLOs What even are the ways you can actually do this whole SLI/SLO measurement stuff? Leadership, operations, development, legal, product, QA, etc. How to convince everyone that SLOs are good. Let’s list a bunch of things you can actually use error budgets for and also go into the math for how to calculate them (although that’s not relevant anymore cause the answer is to use Nobl9, of course.) Also, let’s use some basic statistics to help you pick a good target. It would help if you had a target percentage, but people think they need to be close to 100% and, for some reason, think they should use only the number 9, and these things are both false. How do you come up with SLIs that are actually meaningful to users instead of just “availability” or “latency,” which don’t really tell you much?Ĭhapter 4: Choosing Good Service Level Objectives This is important!Ĭhapter 3: Developing Meaningful Service Level Indicators
Reliability is an often misunderstood phrase. What even are SLIs, SLOs, and error budgets and why should I care?Ĭhapter 2: How To Think About Reliability While I read this tweet, I realized that I had written up a “cheat sheet” for The SLO Book a little while back for my coworkers and then realized there wasn’t any reason it shouldn’t be public! So, in about 500 incredibly colloquial words, I present to you: The SLO Book Cheatsheet. The SLO Book goes even a step further: a little under half of the chapters were actually written by collaborators! This can make it even more difficult to conjure up important details. As the author of a book myself, I immediately connected with the concept of needing to look stuff up in my own work.
0 kommentar(er)
