{"id":760,"date":"2023-09-11T02:20:59","date_gmt":"2023-09-11T02:20:59","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2023\/09\/11\/sre-weekly-issue-389\/"},"modified":"2023-09-11T02:20:59","modified_gmt":"2023-09-11T02:20:59","slug":"sre-weekly-issue-389","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2023\/09\/11\/sre-weekly-issue-389\/","title":{"rendered":"SRE Weekly Issue #389"},"content":{"rendered":"

View on sreweekly.com<\/a><\/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
Building a Successful SRE Team<\/a><\/div>\n
\n

Here\u2019s four of the lessons I learned that should help you build a successful SRE organization.<\/p>\n

Focus on Developer Training
\nFocus on the Right Abstractions
\nFocus on Self Service
\nAutomate Yourself out of a job<\/p>\n

\u00a0\u00a0Sven Hans Knecht<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Exploring distributed vs centralized incident command models<\/a><\/div>\n
\n

In this blog post, we\u2019ll talk about two incident management structure models \u2014 distributed and centralized, including the pros and cons of each, and examples of what each structure looks like in our community. <\/p>\n

\u00a0\u00a0Robert Ross \u2014 FireHydrant<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Understanding the Rasmussen model for failures<\/a><\/div>\n
\n

The Rasmussen model conceptualizes the limits of a system along 3 boundaries: Cost, System Performance, and Human Capacity.<\/p>\n

\u00a0\u00a0Nishant Modak \u2014 Last9<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Accelerator Report: Leak repaired, cooling in progress<\/a><\/div>\n
\n

Wow, this is a really interesting incident. it has all the hallmarks of a nightmare sev1: time pressure, unknown problem, inventing new procedures on the spot, multiple different teams\/specialties having to work together, etc.<\/p>\n

\u00a0\u00a0Jorg Wenninger \u2014 CERN<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Scheduling Oncall considering Sabbath and other frequent recurring conflicts<\/a><\/div>\n
\n

What do you do when many engineers all need to take the same day off each week for religious reasons?<\/p>\n

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

\n
Concerning the production order system malfunction<\/a><\/div>\n
\n

Toyota recently halted production in their factories due to a problem in their order system, about which they shared some interesting details.<\/p>\n

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

\n
Being The First SRE<\/a><\/div>\n
\n

Here\u2019s a guidebook on how to handle being the first SRE at a company.<\/p>\n

\u00a0\u00a0Sven Hans Knecht<\/small><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

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

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 Here\u2019s four of the lessons… Continue reading SRE Weekly Issue #389<\/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-760","post","type-post","status-publish","format-standard","hentry","category-sre","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":746,"url":"https:\/\/fde.cat\/index.php\/2023\/08\/14\/sre-weekly-issue-385\/","url_meta":{"origin":760,"position":0},"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":755,"url":"https:\/\/fde.cat\/index.php\/2023\/09\/04\/sre-weekly-issue-388\/","url_meta":{"origin":760,"position":1},"title":"SRE Weekly Issue #388","date":"September 4, 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 Operating effectively in high surprise\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":749,"url":"https:\/\/fde.cat\/index.php\/2023\/08\/22\/sre-weekly-issue-386\/","url_meta":{"origin":760,"position":2},"title":"SRE Weekly Issue #386","date":"August 22, 2023","format":false,"excerpt":"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\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":763,"url":"https:\/\/fde.cat\/index.php\/2023\/09\/18\/sre-weekly-issue-390\/","url_meta":{"origin":760,"position":3},"title":"SRE Weekly Issue #390","date":"September 18, 2023","format":false,"excerpt":"View on sreweekly.com Many apologies to my email subscribers, who have seen two accidental re-sends of old issues recently due to a weird glitch in my automation. I think I\u2019ve gotten a handle on it, and I\u2019ll run an internal retrospective of this incident, of course. A message from our\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":760,"position":4},"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":752,"url":"https:\/\/fde.cat\/index.php\/2023\/08\/28\/sre-weekly-issue-387\/","url_meta":{"origin":760,"position":5},"title":"SRE Weekly Issue #387","date":"August 28, 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 Software Systems: 10 Key Factors\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\/760","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=760"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/760\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=760"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=760"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=760"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}