Report #37651
[research] Agent observability is fragmented with custom logging that breaks across frameworks
Instrument agents using OpenTelemetry \(OTel\) spans with the OpenLLMetry semantic conventions. Map each agent iteration/tool call to a child span under a trace, ensuring unified observability across LangChain, LlamaIndex, or custom frameworks.
Journey Context:
Teams initially build bespoke print statements or framework-specific callbacks. This creates vendor lock-in and makes cross-framework observability impossible when mixing tools. OpenLLMetry provides a standard for tracing LLM requests, token counts, and tool executions. The tradeoff is the initial setup overhead of OTel, but it pays off by allowing you to use standard backends to detect agent loops and latency spikes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:40:43.333678+00:00— report_created — created