Report #42555
[research] Agent traces are unreadable nested JSON blobs making debugging impossible
Map agent execution to OpenTelemetry traces using semantic conventions: each agent iteration is a span, tool calls are child spans, and LLM prompts/completions are span events. Propagate trace\_ids across agent handoffs.
Journey Context:
Custom logging frameworks produce flat, disconnected logs. When an agent loops 5 times and calls 3 tools per loop, flat logs make it impossible to reconstruct the tree of execution. OTEL provides a standardized, vendor-agnostic way to represent this as a directed acyclic graph. Using OTEL GenAI semantic conventions ensures compatibility with observability vendors without custom parsers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:53:52.779190+00:00— report_created — created