{"id":797,"date":"2023-11-27T02:13:55","date_gmt":"2023-11-27T02:13:55","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2023\/11\/27\/sre-weekly-issue-400\/"},"modified":"2023-11-27T02:13:55","modified_gmt":"2023-11-27T02:13:55","slug":"sre-weekly-issue-400","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2023\/11\/27\/sre-weekly-issue-400\/","title":{"rendered":"SRE Weekly Issue #400"},"content":{"rendered":"<p><a href=\"https:\/\/sreweekly.com\/sre-weekly-issue-400\/\" title=\"Permalink to SRE Weekly Issue #400\" 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>How is FireHydrant building its alerting tool, Signals, to be robust, lightning-fast, and configurable to how YOU work? In this edition, of their Captain\u2019s Log, they dive into CEL and how they\u2019re using it to handle routing and logic.<br \/>\n<a href=\"https:\/\/firehydrant.com\/blog\/captains-log-how-were-leveraging-cel\/\">https:\/\/firehydrant.com\/blog\/captains-log-how-were-leveraging-cel\/ <\/a><\/p>\n<\/div>\n<div class=\"wp-block-group\">\n<div class=\"wp-block-group__inner-container\">\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/www.anadimisra.com\/microservices\/2023\/10\/22\/12-factor-network-is-reliable.html\" target=\"_blank\" rel=\"noopener\">A guide to Managing the First Fallacy of Distributed Computing<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>The network is not reliable.  What are the implications and what can we do about it?<\/p>\n<p>\u00a0\u00a0<small>Anadi Misra<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/argoday.medium.com\/incident-severity-levels-78bfe7dd7e0d\" target=\"_blank\" rel=\"noopener\">Incident severity levels for online platforms<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Beyond a run-of-the-mill severity levels article, this one goes into a couple of common pitfalls.<\/p>\n<p>\u00a0\u00a0<small>Jonathan Word<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/rootly.com\/blog\/status-pages-101-how-to-create-a-status-page-you-and-your-customers-will-actually-want-to-use\" target=\"_blank\" rel=\"noopener\">Status Pages 101: How to Create a Status Page You and Your Customers Will Actually Want to Use<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Some good tips in here, esp. the one about brevity.<\/p>\n<p>\u00a0\u00a0<small>Ashley Sawatsky \u2014 Rootly<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/sre.google\/resources\/practices-and-processes\/twenty-years-of-sre-lessons-learned\/\" target=\"_blank\" rel=\"noopener\">Lessons learned from two decades of Site Reliability Engineering<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Subtitle:<\/p>\n<p>Or, Eleven things we have learned as Site Reliability Engineers at Google <\/p>\n<p>\u00a0\u00a0<small> Adrienne Walcer, Kavita Guliani, Mikel Ward, Sunny Hsiao, and Vrai Stacey \u2014 Google<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/medium.com\/adevinta-tech-blog\/dont-name-your-eks-managed-nodegroups-unless-you-want-to-trigger-an-incident-77709c68ab6a\" target=\"_blank\" rel=\"noopener\">Don\u2019t name your EKS Managed NodeGroups (unless you want to trigger an incident)<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Good lessons to learn here that apply more broadly than just EKS.<\/p>\n<p>\u00a0\u00a0<small>Christian Alex\u00e1nder Polanco Valdez \u2014 Adevinta<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/martinfowler.com\/articles\/2023-liberal-arts.html\" target=\"_blank\" rel=\"noopener\">Three reasons a liberal arts degree helped me succeed in tech<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>This article is about project management, but a lot of the skills discussed apply to aspects of SRE at Staff+ levels.<\/p>\n<p>\u00a0\u00a0<small>Sannie Lee \u2014  Thoughtworks (via martinfowler.com)<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/www.heavybit.com\/library\/article\/generative-ai-incident-response-devops\" target=\"_blank\" rel=\"noopener\">How Does Generative AI Work with Devops and Incident Response?<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>Now this is more like it: there\u2019s a healthy does of skepticism woven through this article, including things genAI probably won\u2019t be good for, and potential pitfalls.<\/p>\n<p>\u00a0\u00a0<small>Jesse Robbins \u2014 Heavybit<\/small><\/p>\n<\/div>\n<\/div>\n<div class=\"sreweekly-entry\">\n<div class=\"sreweekly-title\"><a href=\"https:\/\/www.honeycomb.io\/blog\/slos-budget-rate-alerts\" target=\"_blank\" rel=\"noopener\">From Oops to Ops: SLOs Get Budget Rate Alerts<\/a><\/div>\n<div class=\"sreweekly-description\">\n<p>There are two different ways of alerting on SLOs, for two very different audiences, as explained in this article.  Ostensibly this is a product feature announcement, but you don\u2019t need to be using the product to get a lot out of this.<\/p>\n<p>\u00a0\u00a0<small>Fred Hebert \u2014 Honeycomb<\/small><br \/>\n\u00a0\u00a0<small><em>Full disclosure: Honeycomb is my employer.<\/em><\/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: How is FireHydrant building its alerting tool, Signals, to be robust, lightning-fast, and configurable to how YOU work? In this edition, of their Captain\u2019s Log, they dive into CEL and how they\u2019re using it to handle routing and logic. https:\/\/firehydrant.com\/blog\/captains-log-how-were-leveraging-cel\/ A guide to Managing the First&hellip; <a class=\"more-link\" href=\"https:\/\/fde.cat\/index.php\/2023\/11\/27\/sre-weekly-issue-400\/\">Continue reading <span class=\"screen-reader-text\">SRE Weekly Issue #400<\/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-797","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":797,"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":798,"url":"https:\/\/fde.cat\/index.php\/2023\/12\/04\/sre-weekly-issue-401\/","url_meta":{"origin":797,"position":1},"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":786,"url":"https:\/\/fde.cat\/index.php\/2023\/11\/13\/sre-weekly-issue-398\/","url_meta":{"origin":797,"position":2},"title":"SRE Weekly Issue #398","date":"November 13, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: \u201cChange is the essential process of all existence.\u201d \u2013 Spock It\u2019s time for alerting to evolve. Get a first look at how incident management platform FireHydrant is architecting Signals, its native alerting tool, for resilience in the Signals Captain\u2019s Log. https:\/\/firehydrant.com\/blog\/captains-log-a-first-look-at-our-architecture-for-signals\/\u2026","rel":"","context":"In &quot;SRE&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":829,"url":"https:\/\/fde.cat\/index.php\/2024\/02\/26\/sre-weekly-issue-413\/","url_meta":{"origin":797,"position":3},"title":"SRE Weekly Issue #413","date":"February 26, 2024","format":false,"excerpt":"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\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":797,"position":4},"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":835,"url":"https:\/\/fde.cat\/index.php\/2024\/03\/11\/sre-weekly-issue-415\/","url_meta":{"origin":797,"position":5},"title":"SRE Weekly Issue #415","date":"March 11, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: Join FireHydrant and talk shop with your DevOps peers on March 28! You\u2019ll gain a better understanding of what makes a fatigue-free on-call culture and how to implement practices to improve yours at this free, virtual roundtable. https:\/\/app.livestorm.co\/firehydrant\/better-incidents-spring-bonfire-secrets-to-fatigue-free-on-call-in-2024 The Wrong Way\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\/797","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=797"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/797\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=797"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=797"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=797"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}