Add GHCP telemetry correlation fields for tool responses and response turns#317855
Merged
connor4312 merged 5 commits intoMay 21, 2026
Conversation
Contributor
There was a problem hiding this comment.
Copilot encountered an error: Your billing is not configured or you have Copilot licenses from multiple standalone organizations or enterprises. To use premium requests, select a billing entity via the GitHub site, under Settings > Copilot > Features.
Contributor
Author
|
@microsoft-github-policy-service agree company="Microsoft" |
connor4312
approved these changes
May 21, 2026
roblourens
approved these changes
May 21, 2026
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.
Summary
Adds correlation fields to GHCP
agent.tool.responseLengthtelemetry and reports the current turn onresponse.successtelemetry.Problem
The GHCP
agent.tool.responseLengthevent only emittedtoolNameandtokenCount, making it difficult to correlate individual tool result token usage with a chat conversation, request, or model.response.successdid not include the current turn value, which made response-level telemetry harder to align with request-level telemetry for a conversation.Changes
toolCalling.tsxsendInvokedToolTelemetry()to accept request-scoped telemetry propertiesconversationId,requestId, andmodelonagent.tool.responseLengthpromptContext.conversation?.sessionIdforconversationIdso it matches the conversation session used bypanel.requestconversationId,requestId, andmodelchatVariables.tsxconversationIdandrequestIdthrough for tool references invoked from chat variablestoolCalling.spec.tsconversationIdrequestIdmodeltoolNametokenCountmeasurementchatMLFetcherTelemetry.tsturntoresponse.successmeasurementsturnValidation
toolCalling.spec.tstest passedRelated issue
https://github.com/microsoft/vscode-internalbacklog/issues/7765