{"id":256,"date":"2021-02-03T22:10:00","date_gmt":"2021-02-03T22:10:00","guid":{"rendered":"https:\/\/fde.cat\/?p=256"},"modified":"2021-08-31T14:33:58","modified_gmt":"2021-08-31T14:33:58","slug":"sre-weekly-issue-251","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2021\/02\/03\/sre-weekly-issue-251\/","title":{"rendered":"SRE Weekly Issue #251"},"content":{"rendered":"

View on sreweekly.com<\/a><\/p>\n

Happy new year!<\/p>\n

\n

A message from our sponsor, StackHawk:<\/h2>\n

Still looking for a good new years resolution? How about adding application security testing to your CI\/CD pipeline with StackHawk. Get started with our free account.
\nhttps:\/\/sthwk.com\/freeplan<\/a><\/p>\n<\/div>\n

Articles<\/h2>\n
\n
Writing Runbook Documentation When You\u2019re An SRE<\/a><\/div>\n
\n

Tips and tricks for writing effective runbook documentation when you aren\u2019t a technical writer<\/p><\/blockquote>\n

I like the discussion of the \u201cCurse of Knowledge\u201d cognitive bias.<\/p>\n

Taylor Barnett \u2014 Transposit<\/small><\/p>\n<\/div>\n<\/div>\n

\n
SLO\u200a\u2014\u200aFrom Nothing to\u2026 Production<\/a><\/div>\n
\n

Here\u2019s one engineer\u2019s SLO journey.<\/p>\n

My main focus is on how I educated myself about SLOs and how applied this to my organization.<\/p><\/blockquote>\n

Ioannis Georgoulas<\/small><\/p>\n<\/div>\n<\/div>\n

\n
How to sell SLOs to Engineering Directors<\/a><\/div>\n
\n

This blog is a redacted internal memo that aimed to familiarize SLOs with its audience, explain the value of an SLO culture, and describe how we would implement and roll them out.<\/p><\/blockquote>\n

Thomas C\u00e9sar\u00e9-Herriau \u2014 Brex<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Why I\u2019ve Been Merging Microservices Back Into The Monolith At InVision<\/a><\/div>\n
\n

Why would you do this? It\u2019s all about Conway\u2019s Law.<\/p>\n

Ben Nadel<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Incident Phenomena: Shorthand Names, \u00e0 la Danny Ocean<\/a><\/div>\n
\n

The folks at Adaptive Capacity Labs have seen a few patterns crop up over and over in their post-incident reviews. How many of these have you seen before?<\/p>\n

John Allspaw \u2014 Adaptive Capacity Labs<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Home Alone: a Post-Incident Review<\/a><\/div>\n
\n

Lots of complex contributing factors led to the main character being left behind in the movie Home Alone<\/em>\u2026 so let\u2019s treat it like a production incident!<\/p>\n

Fred Hebert<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Making sense of what happened is hard<\/a><\/div>\n
\n

This one includes a complex timeline showing the interplay of two pairs of bugs, where one in each pair masked the other.<\/p>\n

Lorin Hochstein<\/small><\/p>\n<\/div>\n<\/div>\n

Outages<\/h2>\n