A message from our sponsor, BigPanda:
When a P1 fires, scope, impact, and cause should be instant.
Instead you’re 10 minutes in, pinging people across tools and teams to understand what’s happening. BigPanda surfaces the full picture the moment an incident starts so you fix, not hunt.
This article gives you the failure data, cost data, and risk picture you need to make an accurate decision about AI SRE adoption.
James A. Wondrasek — softwareseni
The blind spot isn’t delivery, its legibility: DORA measures work flowing through the pipe, not whether anyone can explain what’s in it.
Paul LaPosta — LeadDev
But what happens when your observability stack is dependent on the same systems that are failing? In that moment, the dashboards go dark, alerts stop firing, and the tools meant to guide recovery become part of the outage.
Abdurrahman J. Allawala — Airbnb
A thoughtful analysis of GitHub’s availability trouble of late, including some excellent reporting work to get more details on a growth graph previously shared by GitHub.
Gergely Orosz — The Pragmatic Engineer
Here’s a good one introducing the concept of distancing through differencing.
By focusing on the differences, they see no lessons for their own operation and practices.
Lorin Hochstein
In this post, we’ll peek behind the curtain and see how one seemingly innocuous change overwhelmed a system multiple hops away and how our not-fun afternoon helped us improve Discord.
Discord
Oof. GCP suspended their account “as part of an automated action”, killing production.
This may sound familiar, because GCP did something very similar almost exactly 2 years ago.
Chandrika Khanduri & Cody De Arkland — Railway
What a story! They discovered that they had inadvertently installed a quite harmful agent ruleset. Before you dismiss this by thinking “I’d never do that”, go back up and read Lorin Hochstein’s article above.
u/dvrkstar — r/bard (Reddit)