Report #13180
[research] Agent observability traces are unreadable because spans lack LLM-specific semantic context
Instrument agents using OpenTelemetry GenAI semantic conventions. Ensure every tool call, LLM invocation, and RAG retrieval is tagged with standard attributes \(e.g., gen\_ai.system, gen\_ai.request.model, gen\_ai.usage.input\_tokens\) rather than custom unstructured logs.
Journey Context:
Developers often log agent steps using print statements or generic unstructured logging. This makes it impossible to aggregate metrics like token usage per tool, latency per model, or error rates across runs. Adopting the OpenTelemetry GenAI semantic conventions ensures traces are natively parseable by standard observability backends, enabling automated dashboards and alerts on agent degradation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:08:32.996735+00:00— report_created — created