A message from our sponsor, Costory:
You didn’t sign up to do FinOps.
Costory automatically explains why your cloud costs change, and reports it straight to Slack.
Built for SREs who want to code, not wrestle with spreadsheets.
Now on AWS & GCP Marketplaces.
Start your free trial at costory.io
I didn’t know that some resolvers care about the order of some DNS records in a response, but I’m not surprised. The DNS spec, despite its age and multiple revisions, has a number of ambiguities like this.
Sebastiaan Neuteboom — Cloudflare
Severity isn’t always the best indicator of the incidents we can learn the most from. What if we rate our incidents on their potential for learning?
Lorin Hochstein
This one discusses three ways you can lose time in incidents and ideas for what you can do about it.
Hrishikesh Barua — Uptime Labs
An interesting discussion of a bias: we tend to solve problems by adding things to our systems, and that increases complexity. AI can amplify this bias.
Uwe Friedrichsen
Ever wondered how OTel auto-instrumentation works? This article explains it in detail (with code examples) for Python, Java, and Go.
Elizabeth — Observability Real Talk
This article stands out from others about AI SRE agents because it goes into some detail on their method for evaluating whether their agent works. I’d love to see more of the actual evaluation results, and examples of it getting things right vs wrong.
Daniel Shan and Tristan Ratchford — Datadog
I recently got an error from GitHub saying I’d exceeded a rate limit (when I definitely didn’t), and this article explains why.
See why observability and lifecycle management are critical for defense systems.
Thomas Kjær Aabo — GitHub
Poor telemetry makes us want to add more telemetry, which can decrease our telemetry quality and make us add more, yikes! How can we fix the feedback loop?
Note for blind or low-vision readers: there’s a pretty important diagram in this one without a caption or alt text.
Ash Patel