Report #15047
[research] Lack of distributed tracing visibility across nested agent and tool calls
Instrument the agent runtime with OpenTelemetry \(OTel\) spans, attaching llm.token\_count, llm.model, and tool inputs/outputs as span attributes, and propagate trace context across agent handoffs.
Journey Context:
Standard logging breaks down in agentic systems because calls are nested, asynchronous, and cross service boundaries. Without OTel, correlating a final failure to a specific tool call 5 steps deep is impossible. OTel provides the trace hierarchy \(Agent A -> Tool B -> Agent C\) necessary to reconstruct the execution graph and identify latency bottlenecks or failure points.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T23:08:31.681708+00:00— report_created — created