Lorin Hochstein argues that AI agents are now capable of handling significant on-call work, citing Boris Tane's position that on-call is becoming theatre as agents take first-responder duties. The post explores how AI will change incident response workflows and the reliability challenges this introduces.

This is the reliability economics pivot point: when agents start changing production state autonomously, your incident taxonomy breaks. You're not budgeting for 'agent decided wrong' as a root cause category, but you will be.

Grafana tested how well AI agents can debug full-stack incidents and measured performance improvements when agents have access to Grafana Cloud's Knowledge Graph versus operating without that context. The post demonstrates that agent effectiveness in RCA depends heavily on contextual infrastructure data.

Here's the hidden agent tax: graph infrastructure. Agents need semantic context about your stack to avoid expensive hallucinations during incidents, which means new platform investment before agents deliver ROI. This shifts preventive spend forward in ways most roadmaps haven't accounted for.

Grafana shares capacity planning and load testing lessons for running Alloy as a centralized telemetry gateway handling enterprise-scale volumes—tens of millions of active series, terabytes of logs daily, and tens of thousands of trace spans per second.

Agents need telemetry pipelines that can handle both human-generated and agent-generated observability data at scale—double the cardinality problem.

Atlassian describes the challenge of correlating hundreds of interconnected microservices across multiple regions during incidents, where telemetry volume overwhelms human operators and finding causal factors requires automated multi-signal correlation.

Multi-signal correlation is table stakes for agent-assisted RCA—this is the detection gap agents are supposed to close, but it requires investment in correlation infrastructure first.

The post explains how Kubernetes' minReadySeconds parameter makes new pods prove they can stay ready before a rollout proceeds, and provides guidance on setting it and identifying workloads that lack this safety control.

When agents start triggering rollouts, this config line becomes a reliability guardrail—the difference between an agent-driven deployment that self-heals and one that cascades.

GitHub experienced another major incident lasting nearly eight hours, with a public writeup posted unusually quickly. The post is the latest in Hochstein's ongoing series analyzing GitHub's operational challenges.

GitHub's incident cadence is a preview: as more companies deploy agents that touch production, expect your incident frequency to spike before it drops—agent learning curves cost MTTR budget.

Nobl9 released Nobl9 Assist, an in-context AI assistant that answers plain-language questions about SLO burn, budget drain, and feature configuration using live organizational data. It can draft and apply configuration changes with explicit user approval.

In-product AI assistants mark the shift from 'agents as tools' to 'agents as coworkers'—you're now budgeting for agent UX, agent training data pipelines, and agent approval workflows inside every platform purchase.