{"id":835,"date":"2024-03-11T01:32:37","date_gmt":"2024-03-11T01:32:37","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2024\/03\/11\/sre-weekly-issue-415\/"},"modified":"2024-03-11T01:32:37","modified_gmt":"2024-03-11T01:32:37","slug":"sre-weekly-issue-415","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2024\/03\/11\/sre-weekly-issue-415\/","title":{"rendered":"SRE Weekly Issue #415"},"content":{"rendered":"

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

\n

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

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.
\nhttps:\/\/app.livestorm.co\/firehydrant\/better-incidents-spring-bonfire-secrets-to-fatigue-free-on-call-in-2024<\/a><\/p>\n<\/div>\n

\n
\n
\n
The Wrong Way to Use DORA Metrics<\/a><\/div>\n
\n

[\u2026] it must be said that the intent of these metrics was always to give an indicator of how well your team was delivering software, not a high-stakes metric that should be used, for example, to hire and fire team leads.<\/p>\n

\u00a0\u00a0No\u010dnica Mellifera \u2014 The New Stack<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Investigating and Optimizing Over-Querying<\/a><\/div>\n
\n

A primer on the problems with N+1 database queries and how this pattern can sneak into your code whether you realize it or not.<\/p>\n

\u00a0\u00a0neda \u2014 ReadySet<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Choosing Good SLIs<\/a><\/div>\n
\n

A great explainer on choosing the right SLIs, starting with the Golden Signals and branching out.<\/p>\n

\u00a0\u00a0Tyler Treat<\/small><\/p>\n<\/div>\n<\/div>\n

\n
You should never be responsible for what you don\u2019t control<\/a><\/div>\n
\n

My favorite part about this is the \u201clatency budget\u201d question \u2014 which team\u2019s code gets to spend how much time doing its part to serve a request?<\/p>\n

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

\n
An\u00a0unexpected crash due to\u00a0unrelated software changes<\/a><\/div>\n
\n

Changes in two programs outside<\/em> the container made Ceph suddenly grind to a halt, as detailed in this troubleshooting story.<\/p>\n

\u00a0\u00a0Vladimir Guryanov \u2014 Palark<\/small><\/p>\n<\/div>\n<\/div>\n

\n
How to set a good only one threshold for an alert?<\/a><\/div>\n
\n

The word \u201cone\u201d is the key here, as the author argues for getting rid of \u201cwarning\u201d alerts entirely in favor of using only \u201ccritical\u201d.<\/p>\n

\u00a0\u00a0Gauthier Fran\u00e7ois<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Creating An Oncall Handoff Bot<\/a><\/div>\n
\n

They wrote a Slack bot to summarize open PagerDuty incidents every day.<\/p>\n

\u00a0\u00a0Matt Weingarten<\/small><\/p>\n<\/div>\n<\/div>\n

\n
Negotiating Priorities Around Incident Investigations<\/a><\/div>\n
\n

The problems I\u2019ll explore in this blog\u2014from the SRE perspective\u2014are about time pressures (when to ship the investigation) and the type of report people expect.<\/p>\n

\u00a0\u00a0Fred Hebert \u2014 Honeycomb<\/small><\/p>\n

\u00a0\u00a0Full disclosure: Honeycomb is my employer.<\/em><\/small><\/p>\n<\/div>\n<\/div>\n

\n
How we avoided alarm fatigue syndrome by managing\/reducing the alerting noise.<\/a><\/div>\n
\n

In order to reduce the noise, first they had to define<\/em> noisy alerts and the KPIs they were looking to improve.<\/p>\n

\u00a0\u00a0Gauthier Fran\u00e7ois \u2014 Doctolib<\/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, 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 to Use DORA Metrics [\u2026]… Continue reading SRE Weekly Issue #415<\/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-835","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":835,"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 "SRE"","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":835,"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 "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":847,"url":"https:\/\/fde.cat\/index.php\/2024\/04\/01\/sre-weekly-issue-418\/","url_meta":{"origin":835,"position":2},"title":"SRE Weekly Issue #418","date":"April 1, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: FireHydrant is now AI-powered for faster, smarter incidents! Power up your incidents with auto-generated real-time summaries, retrospectives, and status page updates. https:\/\/firehydrant.com\/blog\/ai-for-incident-management-is-here\/ Redefining Observability The observability waters have been muddy for awhile, and this article does a great job of taking\u2026","rel":"","context":"In "SRE"","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":835,"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 "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":855,"url":"https:\/\/fde.cat\/index.php\/2024\/04\/15\/sre-weekly-issue-420\/","url_meta":{"origin":835,"position":4},"title":"SRE Weekly Issue #420","date":"April 15, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: FireHydrant is now AI-powered for faster, smarter incidents! Power up your incidents with auto-generated real-time summaries, retrospectives, and status page updates. https:\/\/firehydrant.com\/blog\/ai-for-incident-management-is-here\/ 1.0 Launch Retrospective The game Last Epoch launched in February, and they had a rocky start. This huge retrospective\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":823,"url":"https:\/\/fde.cat\/index.php\/2024\/02\/12\/sre-weekly-issue-411\/","url_meta":{"origin":835,"position":5},"title":"SRE Weekly Issue #411","date":"February 12, 2024","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: \u201cTo be honest, when can we switch?\u201d The first impressions are in. Check out what people are saying after seeing Signals, the new standard in alerting and on-call from FireHydrant, for the first time. https:\/\/firehydrant.com\/signals\/ Shared On-Call Is Where the SRE\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\/835","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=835"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/835\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=835"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=835"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=835"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}