Foam opinion · September 2026

Your AI SRE is not dumb. Its evidence is.

Garbage in. Garbage out. A smarter model cannot recover a request body that was dropped, a database result that was never captured, or a user session stranded in another tool.

The argument

Most AI SRE products start one layer too high. They put an agent above the observability stack and inherit every gap underneath it.

The model is not the limiting factor.

When an AI SRE gives a confident but wrong answer, the reflex is to improve the prompt, add another model, or connect another tool. That treats the agent as the failure.

But an agent can only reason over what the system preserved. If the HTTP response body is absent, the database result was reduced to duration, or the queue handoff lost its parent request, there is no chain of reasoning that recreates the truth.

A frontier model cannot infer a fact your instrumentation deleted.

Observability tools were not built for agents.

They were built to make a manageable human interface. That meant sampling high-volume traces, trimming payloads, obscuring sensitive fields broadly, aggregating metrics, and dividing the production story into separate products.

Those tradeoffs can work for dashboards. They are disastrous for an agent expected to explain exactly what happened to one user across one request.

01
Missing evidence becomes invented causality.

A 200 response without its body looks successful even when it returned an empty result that caused the failure.

02
Disconnected tools become competing stories.

The trace, replay, database span, deployment, and agent run each describe a fragment without proving they belong to the same incident.

03
Noise consumes reasoning.

More tools create more calls, more schemas, and more plausible dead ends. Access is not the same as useful evidence.

RAG and connectors do not repair the picture.

RAG retrieves what already exists. A connector gives an agent faster access to another system. Neither can recover what was never captured, restore a sampled trace, or prove that five records describe the same production event.

Connecting five incomplete tools gives an agent five incomplete versions of the truth.

What production agents actually need.

01

Capture at the source

Preserve requests and responses, queries and results, sessions, queue payloads, model calls, tool calls, logs, metrics, and traces.

02

Connect the sequence

Carry one identity from the user through the browser, services, databases, workers, models, and infrastructure.

03

Redact precisely

Remove PII, PHI, credentials, and service-specific secrets without destroying the evidence required to explain the event.

04

Expose one record

Let Claude Code, Cursor, Codex, and other agents query the complete production trail directly.

The AI SRE is downstream.

The industry is racing to build agents that detect, investigate, and fix production failures. Those agents will improve. But their ceiling is set before the first prompt is sent: by what the software captured and whether the pieces still form one picture.

Fix the evidence first. Then let the agents reason.

Give your coding agents the full picture.

Foam captures and connects what your software does, then makes it queryable by the agents your team already uses.

See how Foam works