Report #94848
[research] Agent traces are unreadable in observability dashboards because standard HTTP spans lack context about the agent's internal reasoning or goals
Enrich OpenTelemetry spans with GenAI semantic conventions, specifically adding gen\_ai.system, gen\_ai.request.model, and custom attributes like agent.current\_goal and agent.memory\_summary to every span.
Journey Context:
Standard APM tools show HTTP requests to the LLM API, but they do not show why the agent made that request or what it already knows. Without attaching the agent's current goal and memory context to the span, debugging an agent failure requires manually correlating dozens of API calls. The OpenTelemetry GenAI semantic conventions are actively being standardized to solve exactly this observability gap.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:47:04.717472+00:00— report_created — created