{"id":749,"date":"2023-08-22T02:02:06","date_gmt":"2023-08-22T02:02:06","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2023\/08\/22\/sre-weekly-issue-386\/"},"modified":"2023-08-22T02:02:06","modified_gmt":"2023-08-22T02:02:06","slug":"sre-weekly-issue-386","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2023\/08\/22\/sre-weekly-issue-386\/","title":{"rendered":"SRE Weekly Issue #386"},"content":{"rendered":"

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

This issue was delayed a day while I was enjoying a much-needed vacation with my family. While I\u2019m on the subject, it\u2019s hot take time: vacations are important for the reliability of our sociotechnical systems, so good SREs should take vacations regularly and encourage others to as well.<\/p>\n

\n

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

When incidents impact your customers, failing to communicate with them effectively can erode trust even further and compound an already difficult situation. Learn the essentials of customer-facing incident communication in Rootly\u2019s latest blog post:
\nhttps:\/\/rootly.com\/blog\/the-medium-is-the-message-how-to-master-the-most-essential-incident-communication-channels<\/a><\/p>\n<\/div>\n

Articles<\/h2>\n
\n
\n
\n
Broken Ownership<\/a><\/div>\n
\n

If \u201cyou build it, you run it\u201d requires mandate<\/strong>, knowledge<\/strong>, and responsibility<\/strong>, what happens when one of those is missing?<\/p>\n

\u00a0\u00a0Alex Ewerl\u00f6f<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Service Delivery Index: A Driver for Reliability<\/a><\/div>\n
\n

Slack developed an all-encompassing metric for the user experience that goes beyond a simple SLO.<\/p>\n

\u00a0\u00a0Matthew McKeen and Ryan Katkov<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Transactions in a Microservice World<\/a><\/div>\n
\n

This whitepaper delves deep into the ways a microservice architecture changes how transactions work. It presents a method of dealing with microservice transaction failures through application-specific compensation logic.<\/p>\n

\u00a0\u00a0Frank Leymann \u2014 WSO2<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Initial Investigation in the Bambu Cloud Temporary Outage<\/a><\/div>\n
\n

Bambu is a brand of 3d printers that are primarily cloud-based. A problem in their cloud system resulted in printers running jobs unexpectedly, causing significant damage to some customer\u2019s printers.<\/p>\n

\u00a0\u00a0Bambu Lab<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Google Cloud Hybrid Connectivity Incident Report<\/a><\/div>\n
\n

An interesting confluence of fiber optic line failures resulted in loss of connectivity on what should have been a redundant link.<\/p>\n

\u00a0\u00a0Google<\/small><\/p>\n<\/div>\n<\/div>\n

\n
SLOs Are Overrated<\/a><\/div>\n
\n

I know the title looks like click-bait, but this article delivers with 7 well thought-out critiques of SLOs.<\/p>\n

\u00a0\u00a0Code Reliant<\/small><\/p>\n<\/div>\n<\/div>\n

\n
GitHub \u2013 runbear-io\/awesome-runbook<\/a><\/div>\n
\n

This latest entry into the awesome-* arena is a curated list of runbooks and related resources for popular software.<\/p>\n

\u00a0\u00a0Runbear<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Normal incidents<\/a><\/div>\n
\n

You shift from asking \u201cwhat was the abnormal work?\u201d to \u201chow did this incident happen even though everyone was doing normal work?\u201d<\/p>\n

This article immediately made me think of the latest Mentour Pilot accident investigation<\/a> in which everyone acted nearly perfectly and yet still only narrowly avoided a mid-air collision.<\/p>\n

\u00a0\u00a0Lorin Hochstein<\/small><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

SRE WEEKLY<\/p>","protected":false},"excerpt":{"rendered":"

View on sreweekly.com This issue was delayed a day while I was enjoying a much-needed vacation with my family. While I\u2019m on the subject, it\u2019s hot take time: vacations are important for the reliability of our sociotechnical systems, so good SREs should take vacations regularly and encourage others to as well. A message from our… Continue reading SRE Weekly Issue #386<\/span><\/a><\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-749","post","type-post","status-publish","format-standard","hentry","category-sre","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":882,"url":"https:\/\/fde.cat\/index.php\/2024\/06\/17\/sre-weekly-issue-429\/","url_meta":{"origin":749,"position":0},"title":"SRE Weekly Issue #429","date":"June 17, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: We\u2019ve gone all out on our new integration with Microsoft Teams. If you\u2019re a MS Teams user, FireHydrant now supports the most comprehensive integration for incident management. Run the entire IM process without ever leaving the chat. https:\/\/firehydrant.com\/blog\/introducing-a-brand-new-microsoft-teams-integration\/ Virtualizing Our Storage\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":760,"url":"https:\/\/fde.cat\/index.php\/2023\/09\/11\/sre-weekly-issue-389\/","url_meta":{"origin":749,"position":1},"title":"SRE Weekly Issue #389","date":"September 11, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: When incidents impact your customers, failing to communicate with them effectively can erode trust even further and compound an already difficult situation. Learn the essentials of customer-facing incident communication in Rootly\u2019s latest blog post: https:\/\/rootly.com\/blog\/the-medium-is-the-message-how-to-master-the-most-essential-incident-communication-channels Articles Building a Successful SRE Team\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":737,"url":"https:\/\/fde.cat\/index.php\/2023\/07\/23\/sre-weekly-issue-382\/","url_meta":{"origin":749,"position":2},"title":"SRE Weekly Issue #382","date":"July 23, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: Eliminate the anxiety around declaring an incident for nebulous problems by introducing a triage phase into your incident management process. Our latest blog posts dives into why the triage phase is so important, and how you can automate yours with Rootly.\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":740,"url":"https:\/\/fde.cat\/index.php\/2023\/08\/07\/sre-weekly-issue-384\/","url_meta":{"origin":749,"position":3},"title":"SRE Weekly Issue #384","date":"August 7, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: When incidents impact your customers, failing to communicate with them effectively can erode trust even further and compound an already difficult situation. Learn the essentials of customer-facing incident communication in Rootly\u2019s latest blog post: https:\/\/rootly.com\/blog\/the-medium-is-the-message-how-to-master-the-most-essential-incident-communication-channels Articles Scaling merge-ort across GitHub They\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":746,"url":"https:\/\/fde.cat\/index.php\/2023\/08\/14\/sre-weekly-issue-385\/","url_meta":{"origin":749,"position":4},"title":"SRE Weekly Issue #385","date":"August 14, 2023","format":false,"excerpt":"View on sreweekly.com Many apologies to Matt Cooper at GitHub, who is the actual author of the article Scaling Merge-ort Across GitHub from last week. Sorry for the mis-credit, Matt! A message from our sponsor, Rootly: When incidents impact your customers, failing to communicate with them effectively can erode trust\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":826,"url":"https:\/\/fde.cat\/index.php\/2024\/02\/18\/sre-weekly-issue-412\/","url_meta":{"origin":749,"position":5},"title":"SRE Weekly Issue #412","date":"February 18, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: FireHydrant\u2019s new and improved MTTX analytics dashboard is here! See which services are most affected by incidents, where they take the longest to detect (or acknowledge, mitigate, resolve \u2026 you name it); and how metrics and statistics change over time. https:\/\/firehydrant.com\/blog\/mttx-incident-analytics-to-drive-your-reliability-roadmap\/\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/749","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/comments?post=749"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/749\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=749"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=749"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=749"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}