Monitoring Agentic Systems Before They're Reliable
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
Agentic systems entering production typically operate as partially integrated assemblies where structural defects, not task-level errors, dominate the failure landscape. At this maturity level, task-level error detection may be infeasible: structural failure modes mask the signal that task-level monitors are designed to detect.We present a monitoring and triage methodology that decomposes agentic system evaluation into three dimensions (quality, suitability, efficiency) at three monitoring scopes (within-run, cross-run, structural), using variance as a characterization signal. Findings are routed through severity classification adapted from FMEA, concentrating human attention on the subset that warrants investigation. We evaluate on a synthetic testbed of 220 runs across 120 document bundles with controlled error injection.Three results emerge. Monitor scope determines failure type: within-run monitors surface deterministic stage defects (CV = 0.02), cross-run monitors surface stochastic integration consequences (CV = 1.25, 24% at L2), and a structural monitor identifies an integration gap with perfect consistency (CV = 0.00). Injected task-level errors are indistinguishable from clean baselines, confirming structural defects mask task-level signal. Deterministic triage routes 97% of findings to automated tracking, leaving the 2% reflecting variable behavior for human investigation.We propose, on Stage 1 evidence, a maturity-staging model in which monitoring transitions from structural characterization to error detection to reliability tracking as integration defects resolve. The taxonomy, CV-based scope characterization, and severity model transfer architecturally to document-driven, multi-stage agentic workflows in regulated industries; specific calibrations are domain-specific. Deploy monitoring early: the first thing it finds is the most important thing to fix.
Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 2 of its 17 references that are in the map. First posted on arXiv 1 Jun 2026.
Builds on
2 of 17 references.
References · 2
- 2023Judging LLM-as-a-Judge with MT-Bench and Chatbot Arenacited by 8,393
- 2026Towards a Science of AI Agent Reliabilitycited by 58
Built on by
Not cited yet.
Similar, not cited
Close in wording, no citation either way
- 2026AgentEval: DAG-Structured Step-Level Evaluation for Agentic Workflows with Error Propagation Tracking
- 2026When Agentic Executions Fail: Detecting and Localizing Runtime Faults from Telemetry
- 2026TelemetrySuffBench: Is Agent Telemetry Sufficient for Failure-Origin Diagnosis?
- 2026AgentCollabBench: Diagnosing When Good Agents Make Bad Collaborators
- 2026AgentDebugX: An Open-Source Toolkit for Failure Observability, Attribution, and Recovery in LLM Agents
- 2026TraceSIR: A Multi-Agent Framework for Structured Analysis and Reporting of Agentic Execution Traces
- 2026OrchestraBench: Evaluating Multi-Agent Orchestration Failure Modes, Recovery, and Decomposition Quality
- 2026Coding Agents Are Guessing: Measuring Action-Boundary Violations in Underspecified DevOps Instructions