Emit OTel spans for non-executing tool calls #10499
Open
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
Right now, tool call spans are only created if they have a defined execute function. This means that tool calls that don't have an execute function aren't picked up in tracing. Thus, the only way to tell which tool calls were picked is to manually parse + look at the ai.response.toolCalls attribute of a doGenerate/doStream span.
See #10498
Summary
We now emit tool calls spans even if they don't have a defined
executefunction.Manual Verification
Ran AI SDK with these changes on a new app and defined a tool call without an
executefunction. Made sure the OTel spans were emitted.Example:
Checklist
pnpm changesetin the project root)Related Issues
This is a draft of proposed changes for #10498.