{"id":808,"date":"2024-01-01T02:36:36","date_gmt":"2024-01-01T02:36:36","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2024\/01\/01\/sre-weekly-issue-405\/"},"modified":"2024-01-01T02:36:36","modified_gmt":"2024-01-01T02:36:36","slug":"sre-weekly-issue-405","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2024\/01\/01\/sre-weekly-issue-405\/","title":{"rendered":"SRE Weekly Issue #405"},"content":{"rendered":"<p><a href=\"https:\/\/sreweekly.com\/sre-weekly-issue-405\/\" title=\"Permalink to SRE Weekly Issue #405\" class=\"email_only\">View on sreweekly.com<\/a><\/p>\n<div class=\"sreweekly-sponsor-message\">\n<h2>A message from our sponsor, <a href=\"https:\/\/firehydrant.com\/\">FireHydrant<\/a>:<\/h2>\n<p>In this episode of FireHydrant\u2019s Gimme 5 video series, Asaf Gaon, Director of Technical Support for automated grocery fulfillment solution Takeoff Technologies, talks about how to handle third-party downtime in a collaborative \u2013 and automated \u2013 way.<br \/>\n<a href=\"https:\/\/firehydrant.com\/blog\/gimme-5-with-takeoff-technologies-asaf-gaon\/\">https:\/\/firehydrant.com\/blog\/gimme-5-with-takeoff-technologies-asaf-gaon\/<\/a><\/p>\n<\/div>\n<div class=\"wp-block-group is-layout-flow wp-block-group-is-layout-flow\">\n<div class=\"wp-block-group__inner-container\">\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/blog.alexewerlof.com\/p\/lagom-slo\" target=\"_blank\" rel=\"noopener\">Lagom SLO<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Using the Swedish word \u201cLagom\u201d as a jumping-off point, this article explains the importance of choosing an SLO that is just right: not too lax and not too strict.<\/p>\n<p>\u00a0\u00a0<small>Alex Ewerl\u00f6f<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/slack.engineering\/our-journey-migrating-to-aws-imdsv2\/\" target=\"_blank\" rel=\"noopener\">Our Journey Migrating to AWS IMDSv2<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>A simple security change like ceasing to use IMDSv1 can involve profound risk and necessitate a major migration process.<\/p>\n<p>\u00a0\u00a0<small>Archie Gunasekara \u2014 Slack<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/thenewstack.io\/why-people-should-be-at-the-heart-of-operational-resilience\/\" target=\"_blank\" rel=\"noopener\">Why People Should Be at the Heart of Operational Resilience<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>It can be all too easy to let a subset of your IT organization \u201chandle\u201d resiliency. If resilience is about an ability to adapt and respond to change, then it needs broad buy-in. <\/p>\n<p>\u00a0\u00a0<small>Richard Gall \u2014 The New Stack<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/surfingcomplexity.blog\/2023\/12\/17\/any-change-can-break-us-but-we-cant-treat-every-change-the-same\/\" target=\"_blank\" rel=\"noopener\">Any change can break us, but we can\u2019t treat every change the same<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>If any seemingly innocuous change can break our systems, what should we do?<\/p>\n<p>\u00a0\u00a0<small>Lorin Hochstein<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/humanisticsystems.com\/2023\/10\/20\/human-performance-in-the-spotlight-human-error-and-honest-mistakes\/\" target=\"_blank\" rel=\"noopener\">Human Performance in the Spotlight: \u2018Human Error\u2019 and \u2018Honest Mistakes\u2019<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>What exactly <em>is<\/em> \u201chuman error\u201d?<\/p>\n<p>\u00a0\u00a0<small>Steven Shorrock \u2014 Humanistic Systems<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/knock.app\/blog\/zero-downtime-postgres-upgrades\" target=\"_blank\" rel=\"noopener\">Zero downtime Postgres upgrades<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>We recently upgraded from Postgres 11.9 to 15.3 with zero downtime by using logical replication, a suite of support scripts, and tools in Elixir &amp; Erlang\u2019s BEAM virtual machine.<\/p>\n<p>They share a ton of details about how they did it.<\/p>\n<p>\u00a0\u00a0<small>Brent Anderson \u2014 Knock<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/ferd.ca\/notes\/rhip-doctors-and-pagers.html\" target=\"_blank\" rel=\"noopener\">RHIP, doctors, and pagers<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Why do doctors still use antiquated pagers?  There\u2019s a lot here that speaks to what it\u2019s really like to operate in an on-call environment, and how to evaluate new tools.<\/p>\n<p>\u00a0\u00a0<small>Fred Hebert<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/florat.net\/beyond-murphyandapos-law\/\" target=\"_blank\" rel=\"noopener\">Beyond Murphy\u2019s Law<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>This article riffs on Murphy\u2019s law, exploring various aspects of how things go wrong using anecdotes.<\/p>\n<p>\u00a0\u00a0<small> Bertrand Florat<\/small><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>SRE WEEKLY<\/p>","protected":false},"excerpt":{"rendered":"<p>View on sreweekly.com A message from our sponsor, FireHydrant: In this episode of FireHydrant\u2019s Gimme 5 video series, Asaf Gaon, Director of Technical Support for automated grocery fulfillment solution Takeoff Technologies, talks about how to handle third-party downtime in a collaborative \u2013 and automated \u2013 way. https:\/\/firehydrant.com\/blog\/gimme-5-with-takeoff-technologies-asaf-gaon\/ Lagom SLO Using the Swedish word \u201cLagom\u201d as&hellip; <a class=\"more-link\" href=\"https:\/\/fde.cat\/index.php\/2024\/01\/01\/sre-weekly-issue-405\/\">Continue reading <span class=\"screen-reader-text\">SRE Weekly Issue #405<\/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-808","post","type-post","status-publish","format-standard","hentry","category-sre","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":727,"url":"https:\/\/fde.cat\/index.php\/2023\/06\/26\/sre-weekly-issue-378\/","url_meta":{"origin":808,"position":0},"title":"SRE Weekly Issue #378","date":"June 26, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: Curious how companies like Figma, Tripadvisor, and 100s of others leverage Rootly to manage incidents in Slack and unlock instant best practices? Check out this lightning demo: https:\/\/www.loom.com\/share\/051c4be0425a436e888dc0c3690855ad Articles \u201cOne-Engined-Zulu\u201d This is the story of a fascinating incident in which a\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":297,"url":"https:\/\/fde.cat\/index.php\/2021\/08\/31\/sre-weekly-issue-265\/","url_meta":{"origin":808,"position":1},"title":"SRE Weekly Issue #265","date":"August 31, 2021","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, StackHawk: Join StackHawk and WhiteSource tomorrow morning to learn about automated security testing in the DevOps pipeline. With automated dynamic testing and software composition analysis, you can be sure you\u2019re shipping secure APIs and applications. Grab your spot: http:\/\/sthwk.com\/stackhawk-whitesource Articles Insights into\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":324,"url":"https:\/\/fde.cat\/index.php\/2021\/08\/31\/sre-weekly-issue-276\/","url_meta":{"origin":808,"position":2},"title":"SRE Weekly Issue #276","date":"August 31, 2021","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, StackHawk: Get ready for some GraphQL! Tune in this Tuesday, June 29 at 9 AM PT for an automated GraphQL security testing learning lab. Register: http:\/\/sthwk.com\/graphql-learning-lab Articles @GergelyOrosz on blaming the intern HBO accidentally sent an email to a bunch of people,\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":261,"url":"https:\/\/fde.cat\/index.php\/2021\/08\/31\/sre-weekly-issue-256\/","url_meta":{"origin":808,"position":3},"title":"SRE Weekly Issue #256","date":"August 31, 2021","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, StackHawk: Register now for the first-ever ZAPCon taking place March 9th. The free event will focus on OWASP ZAP and application security best practices. You wont want to miss it! http:\/\/sthwk.com\/zapcon-sre-weekly Articles Slack\u2019s Outage on January 4th 2021 Here\u2019s a blog post\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":477,"url":"https:\/\/fde.cat\/index.php\/2021\/09\/27\/sre-weekly-issue-289\/","url_meta":{"origin":808,"position":4},"title":"SRE Weekly Issue #289","date":"September 27, 2021","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, StackHawk: Semgrep and StackHawk are showing you what\u2019s new with automated security testing on September 30. Grab your spot: https:\/\/sthwk.com\/whats-new-webinar Articles How SREs are unique in their approach to work Here are some things that make SREs a unique breed in software\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":817,"url":"https:\/\/fde.cat\/index.php\/2024\/01\/29\/sre-weekly-issue-409\/","url_meta":{"origin":808,"position":5},"title":"SRE Weekly Issue #409","date":"January 29, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: It\u2019s time for a new world of alerting tools that prioritize engineer well-being and efficiency. The future lies in intelligent systems that are compatible with real life and use conditional rules to adapt and refine thresholds, reducing alert fatigue. https:\/\/firehydrant.com\/blog\/the-alert-fatigue-dilemma-a-call-for-change-in-how-we-manage-on-call\/ Executing\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/808","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=808"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/808\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=808"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=808"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=808"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}