Repository navigation
Parent AI SDK OpenTelemetry spans from incoming HTTP trace context #33124
Description
OpenTelemetry AI SDK spans currently export as independent traces when opencode is embedded behind an HTTP server that receives trace context. This makes spans such as ai.streamText, ai.streamText.doStream, and ai.toolCall difficult to correlate with the caller trace.
Expected behavior:
- inbound W3C trace context should parent Effect request spans
- AI SDK spans should inherit the same active OpenTelemetry context
- users should be able to export only traces with OTEL_LOGS_EXPORTER=none
This issue tracks adding trace-context propagation for AI SDK telemetry while preserving existing OTLP configuration behavior.
Activity
github-actions commentedon Jun 20, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:title prefix and the verification checkbox confirming the feature hasn't been suggested before. Please use the Feature Request template.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
traceparent/tracestateextraction and parenting of Effect/AI SDK spans at the HTTP server boundary.If you believe this was flagged incorrectly, please let a maintainer know.
iw-an commentedon Jun 20, 2026
Closing this as a duplicate of #18801. I updated the PR to link the existing issue instead.