{"id":829,"date":"2024-02-26T02:14:12","date_gmt":"2024-02-26T02:14:12","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2024\/02\/26\/sre-weekly-issue-413\/"},"modified":"2024-02-26T02:14:12","modified_gmt":"2024-02-26T02:14:12","slug":"sre-weekly-issue-413","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2024\/02\/26\/sre-weekly-issue-413\/","title":{"rendered":"SRE Weekly Issue #413"},"content":{"rendered":"<p><a href=\"https:\/\/sreweekly.com\/sre-weekly-issue-413\/\" title=\"Permalink to SRE Weekly Issue #413\" class=\"email_only\">View on sreweekly.com<\/a><\/p>\n<p>Sorry about the automation fail and resend!  That definitely wasn\u2019t issue #1.<\/p>\n<div class=\"sreweekly-sponsor-message\">\n<h2>A message from our sponsor, <a href=\"https:\/\/firehydrant.com\/\">FireHydrant<\/a>:<\/h2>\n<p>Check out how global payments company Dock uses FireHydrant to streamline and consolidate their incident management stack and reduce what they call \u201cmean time to combat.\u201d<br \/><a href=\"https:\/\/firehydrant.com\/blog\/the-revolution-in-critical-incident-response-at-dock-with-firehydrant\/\">https:\/\/firehydrant.com\/blog\/the-revolution-in-critical-incident-response-at-dock-with-firehydrant\/<\/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:\/\/medium.com\/site-reliability-engineering-leadership\/the-domain-of-failure-64bca144c94b?source=rss----dc5d1a577fd6---4\" target=\"_blank\" rel=\"noopener\">The Domain of Failure<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>This article discusses building failure management directly into our systems, using Erlang as a case study.<\/p>\n<p>\u00a0\u00a0<small>Jamie Allen<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/www.uber.com\/en-GB\/blog\/cinnamon-using-century-old-tech-to-build-a-mean-load-shedder\/\" target=\"_blank\" rel=\"noopener\">Cinnamon: Using Century Old Tech to Build a Mean Load Shedder<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Building on their experience with their previous load shedding library, Uber built a new one that requires no configuration.<\/p>\n<p>\u00a0\u00a0<small>Jakob Holdgaard Thomsen, Vladimir Gavrilenko, Jesper Lindstrom Nielsen, and Timothy Smyth \u2014 Uber<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/blog.plerion.com\/conditional-love-for-aws-metadata-enumeration\/\" target=\"_blank\" rel=\"noopener\">Conditional Love for AWS Metadata Enumeration<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>These folks found a way to get tag names and values from <em>other<\/em> people\u2019s AWS resources.  I know this is more security- than SRE-related but the technique is just so cool!<\/p>\n<p>\u00a0\u00a0<small>Daniel Grzelak \u2014 Plerion<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/willgallego.com\/2024\/02\/16\/justifying-resilience-work\/\" target=\"_blank\" rel=\"noopener\">Justifying Resilience Work<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>How much does it cost to improve resilience?  What\u2019s the ROI?  It\u2019s fuzzy, but we still need to do it.<\/p>\n<p>\u00a0\u00a0<small>Will Gallego<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/sreday.com\/2024-london\/\" target=\"_blank\" rel=\"noopener\">SREday \u2013 London, UK, Sep 19-20, 2024<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Check it out, it\u2019s an entire SRE conference I was totally unaware of!<\/p>\n<p>\u00a0\u00a0<small>SREday<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/uptimerobot.com\/blog\/sla-slo-sli\/\" target=\"_blank\" rel=\"noopener\">SLA vs. SLO vs. SLI: What\u2019s the Difference?<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>It\u2019s an SLI\/SLO\/SLA explainer, but with a twist: a pros and cons list for each of the three.<\/p>\n<p>\u00a0\u00a0<small>Laura Clayton \u2014 UptimeRobot<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/www.reddit.com\/r\/sre\/comments\/1aziwx4\/what_were_your_worst_oncall_experiences\/\" target=\"_blank\" rel=\"noopener\">What were your worst on-call experiences?<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>A great reddit thread for some schadenfreude\u2026 and perhaps you\u2019d like to share your own story?<\/p>\n<p>\u00a0\u00a0<small>u\/New_Detective_1363 and others \u2014 reddit<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/uptimerobot.com\/blog\/replit-monitors-recent-issues\/\" target=\"_blank\" rel=\"noopener\">End of support for repl.co &amp; recent issues explained<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>What an interesting cause for an incident: the service your customers have pointed your product at decides to block your requests, effectively DoSing your systems.<\/p>\n<p>\u00a0\u00a0<small>Tomas Koprusak \u2014 UptimeRobot<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/blog.readyset.io\/a-developers-guide-to-the-cap-theorem\/\" target=\"_blank\" rel=\"noopener\">The Role of CAP Theorem in Modern Day Distributed Systems<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>The CAP theorem is useful as a theory, but what does it actually mean in practice?<\/p>\n<p>\u00a0\u00a0<small>neda \u2014 ReadySet<\/small><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>SRE WEEKLY<\/p>","protected":false},"excerpt":{"rendered":"<p>View on sreweekly.com Sorry about the automation fail and resend! That definitely wasn\u2019t issue #1. A message from our sponsor, FireHydrant: Check out how global payments company Dock uses FireHydrant to streamline and consolidate their incident management stack and reduce what they call \u201cmean time to combat.\u201dhttps:\/\/firehydrant.com\/blog\/the-revolution-in-critical-incident-response-at-dock-with-firehydrant\/ The Domain of Failure This article discusses building&hellip; <a class=\"more-link\" href=\"https:\/\/fde.cat\/index.php\/2024\/02\/26\/sre-weekly-issue-413\/\">Continue reading <span class=\"screen-reader-text\">SRE Weekly Issue #413<\/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-829","post","type-post","status-publish","format-standard","hentry","category-sre","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":844,"url":"https:\/\/fde.cat\/index.php\/2024\/03\/25\/sre-weekly-issue-417\/","url_meta":{"origin":829,"position":0},"title":"SRE Weekly Issue #417","date":"March 25, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: Join FireHydrant this Thursday for a conversation about on-call burnout and how to prevent it. Get a better understanding of what makes a fatigue-free on-call culture, including real-world examples from your incident management peers. No sales, just shop talk. https:\/\/app.livestorm.co\/firehydrant\/better-incidents-spring-bonfire-secrets-to-fatigue-free-on-call-in-2024 Harnessing\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":663,"url":"https:\/\/fde.cat\/index.php\/2022\/12\/19\/sre-weekly-issue-352\/","url_meta":{"origin":829,"position":1},"title":"SRE Weekly Issue #352","date":"December 19, 2022","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: Manage incidents directly from Slack with Rootly\u00a0\ud83d\ude92. Rootly automates manual tasks like creating an incident channel, Jira ticket and Zoom rooms, inviting responders, creating statuspage updates, postmortem timelines and more. Want to see why companies like Canva and Grammarly love us?:\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":798,"url":"https:\/\/fde.cat\/index.php\/2023\/12\/04\/sre-weekly-issue-401\/","url_meta":{"origin":829,"position":2},"title":"SRE Weekly Issue #401","date":"December 4, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: Join FireHydrant Dec.14 for a conversation about on-call culture and its effect on engineering organizations, featuring special guests from Outreach and Udemy. Gain a better understanding of what makes excellent on-call culture and how to implement practices to improve yours. https:\/\/app.livestorm.co\/firehydrant\/better-incidents-winter-bonfire-inside-on-call?type=detailed\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":872,"url":"https:\/\/fde.cat\/index.php\/2024\/06\/03\/sre-weekly-issue-427\/","url_meta":{"origin":829,"position":3},"title":"SRE Weekly Issue #427","date":"June 3, 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\/ Why didn\u2019t you\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":775,"url":"https:\/\/fde.cat\/index.php\/2023\/10\/23\/sre-weekly-issue-395\/","url_meta":{"origin":829,"position":4},"title":"SRE Weekly Issue #395","date":"October 23, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: Incident management platform FireHydrant is combining alerting and incident response in one ring-to-retro tool. Sign up for the early access waitlist and be the first to experience the power of alerting + incident response in one platform at last. https:\/\/firehydrant.com\/signals\/ What\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":771,"url":"https:\/\/fde.cat\/index.php\/2023\/10\/15\/sre-weekly-issue-394\/","url_meta":{"origin":829,"position":5},"title":"SRE Weekly Issue #394","date":"October 15, 2023","format":false,"excerpt":"View on sreweekly.com A warm welcome to my new sponsor, FireHydrant! A message from our sponsor, FireHydrant: The 2023 DORA report has two conclusions with big impacts on incident management: incremental steps matter, and good culture contributes to performance. Dig into both topics and explore ideas for how to start\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\/829","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=829"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/829\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=829"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=829"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}