Repository navigation
Event processor migration: Vercel AI event processor #20377
Description
Activity
A note on this: After talking with @alexander-alderman-webb: Instead of continuing to accumulate the token usage stuff, maybe we can switch already to only record the attributes on the child span level and avoid setting anything on parent spans. This should reduce the complexity for streamed spans.
- added a commit that references this issue
on May 6, 2026 A PR closing this issue has just been released 🚀
This issue was referenced by PR #20608, which was included in the 10.52.0 release.
Metadata
Metadata
Assignees
Labels
No labels
core/src/tracing/vercel-ai/index.tsAnother tough one: The vercel AI event processor does a lot of post processing:
processEndedVercelAiSpan,applyToolDescriptionsAndTokens) should be easy to port toclient.processSpanaccumulateTokensForParent,applyAccumulatedTokens). This can become more dangerous because to guarantee continued correctness, we need a guarantee that the child spans end before their parent so that we can accumulate at end time. This might need careful investigation if its the case. Otherwise we loose accuracy.