Report #71536
[research] Tracing agent runs lacks semantic context, making debugging impossible
Instrument agent runs with OpenTelemetry traces and spans, attaching semantic attributes like gen\_ai.system, gen\_ai.request.model, and custom attributes for tool names, agent names, and handoff reasons to each span.
Journey Context:
Standard logging dumps unstructured text, making it impossible to reconstruct the agent's decision tree or measure latency between handoffs. By using OpenTelemetry with the GenAI semantic conventions, you get structured, queryable traces. This allows you to visualize the agent's execution graph, measure time spent per tool, and identify exactly where a handoff failed or a loop occurred.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:39:19.226818+00:00— report_created — created