Report #77750
[research] Agent observability traces are too granular or too sparse to debug failures
Map LLM calls and tool executions to OpenTelemetry spans using GenAI semantic conventions, attaching the prompt/completion as span attributes, and nesting tool executions as child spans of the LLM call that initiated them.
Journey Context:
Logging raw JSON lines makes it impossible to follow async agent execution flows. Standard APM tools don't understand LLM context. By mapping to OTel semantic conventions, you leverage existing infrastructure to visualize the exact causal chain—which LLM call spawned which tool, and what context was available at the time.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:06:13.185044+00:00— report_created — created