feat(ai): wrap the model call in telemetry context#15479
Merged
Conversation
lgrammel
approved these changes
May 26, 2026
Contributor
|
🚀 Published in:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
continuing from #14732
There seems to be a regression with telemetry spans from v6 -> v7 where the AI Gateway stream fetch request spans seem to be disconnected from the AI SDK traces.
For v6, those requests were visibly child spans. In v7, the AI Gateway requests are not child spans.
The reason seems to be that in v6, we used to wrap the entire doStream model call with OpenTelemetry context and so all subsequent calls/requests were nested properly
Summary
introduce another helper execute composite (similar to what we do for tool execution
executeTools) that will help wrap the language model calls for generate text and stream textManual Verification
na
Checklist
Documentation has been added / updated (for bug fixes / features)pnpm changesetin the project root)Future Work
monitor issues for any regressions