3 ms·
Are there any books that describe building an on-call practice? If not, I volunteer to write one. It's not complicated, but a lot of teams miss some of the fund
by 0xbadcafebee 5y ago
Are there any books that describe building an on-call practice? If not, I volunteer to write one. It's not complicated, but a lot of teams miss some of the fundamentals that improve the overall results. On-call's purpose is not just to wake people up in the middle of the night, it's to drive continuous reduction of on-call incidents. You should get to the point where you don't even need an on-call (but have it just in case).
- johncessna 5y ago+1 the point of on call was to wake up the team who caused the problem in the first place, and presumably have the ability to fix it via code changes etc. This is in contrast to the model where there's a team that fields issues and tries their best to fix them, but ultimately has to put fix-it tickets to the software owners. The on call rotations I've seen end up being a hybrid where you get the worst of both worlds. The team has enough responsibilities that no one person on the team knows how to handle everything and are so inundated with pages that it just becomes accepted that one person from the team every X weeks is going to be nothing but keeping the service from burning down.
- dredmorbius 5y agoGoogle have a set of SRE books, though how much they address SRE at Google Scale rather than Your Actual Situation is a point you may wish to consider. https://sre.google/books/ https://sre.google/books/