
Diagnostic Instrumentation for Prompt Versus Tool Call Failure Isolation in Production Agents
Span-level instrumentation isolates whether agent failures stem from bad prompts or broken tools.
Story: Tomás Erhlich
12 stories in Trace-to-Action Workflows

Span-level instrumentation isolates whether agent failures stem from bad prompts or broken tools.
Story: Tomás Erhlich

Structuring production traces for reliable agent regression testing beyond final answers.
Story: Kwame Asante-Briggs

Teams improve production agents by treating traces as structured inputs to a diagnostic cadence.
Story: Tomás Erhlich

Traces pinpoint the agent layer responsible for each failure, enabling targeted fixes.
Story: Kwame Asante-Briggs

Dashboards must label every failure to its originating agent layer to enable targeted fixes.
Story: Tomás Erhlich

Separating failures by harness layer reveals where debugging actually moves the needle.
Story: Tomás Erhlich

Behavioral patterns in agent logs reveal quality issues that explicit ratings miss.
Story: Tomás Erhlich

Use production traces to rank agent fixes by actual failure impact, not complaint volume.
Story: Tomás Erhlich

How to version prompts and safely promote changes in production agent systems.
Story: Kwame Asante-Briggs

Test prompt changes against real production failures before shipping them live.
Story: Kwame Asante-Briggs

Catch silent agent failures by replaying production traces as regression tests.
Story: Tomás Erhlich

Searching agent traces layer by layer reveals root causes traditional diagnosis misses.
Story: Kwame Asante-Briggs