change tool call types in traces to use api definitions #44351
Merged
Conversation
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
M-Hietala
requested review from
dargilco,
glharper,
howieleung,
kingernupur,
nick863,
trangevi and
trrwilson
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the telemetry/tracing instrumentation to use API-defined type names for tool calls instead of generic mapped types. Previously, the code was mapping API types like function_call to function, file_search_call to file_search, etc. Now it uses the actual API type names directly in traces, improving consistency and clarity.
Key Changes
- Tool call types in traces now use API definitions (e.g.,
function_callinstead offunction,function_call_outputinstead offunction) - Similar changes applied to all tool call types:
file_search_call,code_interpreter_call,web_search_call,azure_ai_search_call,image_generation_call,mcp_call, andcomputer_call - Test expectations updated to reflect the new type naming convention
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| sdk/ai/azure-ai-projects/azure/ai/projects/telemetry/_responses_instrumentor.py | Removed type mapping logic that converted API types to generic types; now uses item_type directly for all tool calls and outputs |
| sdk/ai/azure-ai-projects/tests/agents/telemetry/test_responses_instrumentor.py | Updated test expectations to use API type names (function_call, function_call_output) in trace event content assertions |
| sdk/ai/azure-ai-projects/tests/agents/telemetry/test_responses_instrumentor_async.py | Updated async test expectations to match the new API type naming convention |
| sdk/ai/azure-ai-projects/CHANGELOG.md | Added changelog entry describing the change (with a typo: "defintions" should be "definitions") |
dargilco
approved these changes
Dec 9, 2025
…of type remote_function_call and output when available
dargilco
approved these changes
Dec 11, 2025
M-Hietala
deleted the
m-hietala/updating_tool_traces_to_use_api_definitions
branch
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.
change tool call types in traces to use api definitions