Reliability Enablers

What if agentic AI makes SRE more important, not less? Bennett Gould explains why autonomous AI systems may create more demand for reliability thinking — not less. Everyone seems to think AI is coming for SRE in a hard way. You might have heard the same story: “AI will write the code.” “Agents will handle incidents.” “Copilots will generate the runbooks.” “Automation will reduce operational load.”...

What if the hardest part of reliability has nothing to do with tooling or automation? Jennifer Petoff explains why real reliability comes from the human workflows wrapped around the engineering work. Everyone seems to think AI will automate reliability away. I keep hearing the same story: “Our tooling will catch it.” “Copilots will reduce operational load.” “Automation will mitigate incidents befo...

A new or growing SRE team. A copy of the book. A company that says it cares about reliability. What happens next? Usually… not much. In this episode, I sit down with Dave O’Connor , a 16-year Google SRE veteran , to talk about what happens when organizations cargo-cult reliability practices without understanding the context they were born in. You might know him for his self-deprecating wit and leg...

I know it’s already six months into 2025, but we recorded this almost three months ago. I’ve been busy with my foray into the world of tech consulting and training —and, well, editing these podcast episodes takes time and care. This episode was prompted by the 2025 Catchpoint SRE Report , which dropped some damning but all-too-familiar findings: * 53% of orgs still define reliability as uptime onl...

Most teams talk about reliability with a margin for error. “What’s our SLO? What’s our budget for failure?” But in the energy sector? There is no acceptable downtime. Not even a little. In this episode, I talk with Wade Harris, Director of FAST Engineering in Australia , who’s spent 15+ years designing and rolling out monitoring and control systems for critical energy infrastructure like power sta...

Exploring how to manage observability tool sprawl, reduce costs, and leverage AI to make smarter, data-driven decisions. It's been a hot minute since the last episode of the Reliability Enablers podcast. Sebastian and I have been working on a few things in our realms. On a personal and work front, I’ve been to over 25 cities in the last 3 months and need a breather. Meanwhile, listen to this inter...

Andrew Tunall is a product engineering leader focused on pushing the boundaries of reliability with a current focus on mobile observability. Using his experience from AWS and New Relic, he’s vocal about the need for a more user-focused observability, especially in mobile, where traditional practices fall short. * Career Journey and Current Role : Andrew Tunall, now at Embrace, a mobile observabili...

Andrew Fong’s take on engineering cuts through the usual role labels, urging teams to start with the problem they’re solving instead of locking into rigid job titles. He sees reliability, inclusivity, and efficiency as the real drivers of good engineering. In his view, SRE is all about keeping systems reliable and healthy, while platform engineering is geared toward speed, developer enablement, an...

This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit read.srepath.com

Here’s what we covered: Defining Platform Engineering * Platform engineering : Building compelling internal products to help teams reuse capabilities with less coordination. * Cloud computing connection : Enterprises can now compose platforms from cloud services, creating mature, internal products for all engineering personas. Ankit’s career journey * Didn't choose platform engineering; it found h...

Why many copy Google’s monitoring team setup * Google’s Influence. Google played a key role in defining the concept of software reliability. * Success in Reliability. Few can dispute Google’s ability to ensure high levels of reliability and its ability to share useful ways to improve it in other settings BUT there’s a problem: * It’s not always replicable. While Google's practices are admired, the...

Monitoring in the software engineering world continues to grapple with poor signal-to-noise ratios. It’s a challenge that’s been around since the beginning of software development and will persist for years to come. The core issue is the overwhelming noise from non-essential data, which floods systems with useless alerts. This interrupts workflows, affects personal time, and even disrupts sleep. S...

The question then condenses down to: Can technical leads support reliability work? Yes, they can! Anemari has been a technical lead for years — even spending a few years doing that at the coveted consultancy, Thoughtworks — and now coaches others. She and I discussed the link between this role and software reliability. This is a public episode. If you would like to discuss this with other subscrib...

We're already well into 2024 and it’s sad that people still have enough fuel to complain about various aspects of their engineering life. DORA seems to be turning into one of those problem areas. Not at every organization, but some places are turning it into a case of “hitting metrics” without caring for the underlying capabilities and conversations. Nathen Harvey is no stranger to this problem. H...

We’ll explore 3 use cases for monitoring data. They are: * Analyzing long-term trends * Comparing over time or experiment groups * Conducting ad hoc retrospective analysis Analyzing long-term trends You can ask yourself a couple of simple questions as a starting point: * How big is my database? * How fast is the database growing? * How quickly is my user count growing? As you get comfortable with...

Shlomo Bielak is the Head of Engineering (Operational Excellence and Cloud) at Penn Interactive, an interactive gaming company. He’s dedicated much of his talk time at DevOps events to talk about a topic less covered at such technical events. A lot of what he said alluded to ways to become a more valuable engineer. I’ve broken them down into the following areas: * Avoid the heroic efforts * Mind +...

Incident response is an increasingly difficult area for organizations. Many teams end up paying a lot of money for incident management solutions. However, issues remain because processes supporting the incident response are not robust. Incident response software alone isn't going to fix bad incident processes. It's gonna help for sure. You need these incident management tools to manage the data an...

According to Vlad Ukis, there are a lot of enterprises around whose IT functions are organized around ITIL. What you use SRE for is something completely different. SRE is not for setting up the IT function. It is for enabling the product organization to operate online services reliably at scale. However, the problem is that many in the industry are NOT using SRE principles but instead handing over...

Sonja Blignaut is a complexity expert. That might not sound relevant to incident response in reliability engineering. But it is! Our systems are becoming more complex and so are the resulting incidents . Learning about complexity can help reliability folk go into an incident with less anxiety, which we’ll explore in this episode. We'll explore the causes of complexity in incidents and how the Cyne...

Have you got complete monitoring of your software in effect? Are you sure? Google's SREs break monitoring down to white box versus black box monitoring. It's not the same as internal versus external monitoring, which we'll explore further. We'll cover topics like: - (quickly) What is monitoring? - What is whitebox monitoring? - What is black box monitoring? - The rising importance of blackbox moni...

Jack Neely is a DevOps observability architect at Palo Alto Networks and has a few interesting ways of extracting value from o11y data. We crammed into just under 25 minutes ideas like these 7 takeaways: * Reasserting the Need to Monitor Four Golden Signals : Focus on latency, traffic, errors, and saturation for effective system monitoring and management. * Prioritize Customer Health : in Jack’s w...

Alert noise is no joke and neither is the fatigue that results from it. I spoke with Dan Ravenstone who gave a talk at Monitorama about this very topic. He also happens to be an avid skateboarder! Here are 9 takeaways from our conversation: * Regularly Review and Update Monitoring Systems : Don’t set up monitoring once and forget about it. Continuously assess and update your monitoring systems to...

Sebastian and I scoured Chapter 5 of the Site Reliability Engineering (2016) book to find nuggets of wisdom on how to reduce toil. We hit the jackpot with concepts like: * what is toil according to a 5-point criteria * why even care about toil? * where you can find toil in your software system * Google’s goal for how much work (%) should be toil * the fact that toil isn’t always all that bad Don’t...

The common refrain after an incident is “We could and should learn from this” . To me, that alludes to the need for a robust learning culture . We might think we already have a good learning culture because we talk about problems and deep-dive them into retrospectives. But how often do we explore the nuances of how we are learning? Sorrel Harriet is an expert in supporting software engineering tea...

I continue my conversation with Manuel Pais, co-author of the seminal Team Topologies book about team topologies suitable for reliability teams. In this second part, we will talk about platform teams. A quick refresher on what platform teams do In the team topologies context: Platform teams provide a curated set of self-service capabilities to enable stream-aligned teams (product or feature teams)...