Telemetry: add RequestId and ConversationId to toolCallDetails and response.success events#310281
Merged
Telemetry: add RequestId and ConversationId to toolCallDetails and response.success events#310281
Conversation
Contributor
Screenshot ChangesBase: Changed (2)blocks-ci screenshots changedReplace the contents of Updated blocks-ci-screenshots.md<!-- auto-generated by CI — do not edit manually -->
#### editor/codeEditor/CodeEditor/Dark

#### editor/codeEditor/CodeEditor/Light
 |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances Copilot chat telemetry so analysts can reliably correlate tool-calling behavior and successful responses with the correct per-turn request and conversation identifiers.
Changes:
- Adds
requestIdto thetoolCallDetailstelemetry event payload (and updates its GDPR schema accordingly). - Threads
conversationIdintoresponse.successtelemetry by propagating it into the fetcher’s base telemetry and emitting it in the success event (with GDPR schema update).
Show a summary per file
| File | Description |
|---|---|
| extensions/copilot/src/extension/prompt/node/chatParticipantTelemetry.ts | Adds requestId to toolCallDetails event properties and declares it in the GDPR schema. |
| extensions/copilot/src/extension/prompt/node/chatMLFetcherTelemetry.ts | Adds conversationId to the response.success GDPR schema and includes it in emitted success telemetry properties. |
| extensions/copilot/src/extension/prompt/node/chatMLFetcher.ts | Ensures conversationId is included in the base telemetry data used downstream by response.success. |
Copilot's findings
- Files reviewed: 3/3 changed files
- Comments generated: 0
bhavyaus
approved these changes
Apr 16, 2026
82ed4e6 to
035a5a7
Compare
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.
Currently, the
toolCallDetailsevents don't contain the relevant RequestId, andresponse.successevents don't contain the ConversationId. This makes it difficult to complete some of our desired telemetry data analysis.