Report #10918
[research] Distributed agent traces are broken or orphaned across microservices
Inject the OpenTelemetry trace\_id and span\_id into the agent's system prompt or metadata payload so that downstream tool-execution microservices can extract it and continue the trace.
Journey Context:
When an agent calls an external tool running as a separate microservice, the trace context is lost because the LLM API breaks standard network propagation headers. The tool service starts a new trace, making it impossible to correlate the tool execution latency with the agent's decision. Passing trace context through the LLM payload bridges this gap. The tradeoff is consuming a few tokens in the context window, which is negligible compared to the observability gained.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T12:07:47.587960+00:00— report_created — created