Thanks to visit codestin.com
Credit goes to github.com

Skip to content

copilot: emit router decision to restricted telemetry full scores#312230

Open
aashna wants to merge 1 commit intomainfrom
aashnagarg/router-restricted-telemetry
Open

copilot: emit router decision to restricted telemetry full scores#312230
aashna wants to merge 1 commit intomainfrom
aashnagarg/router-restricted-telemetry

Conversation

@aashna
Copy link
Copy Markdown
Contributor

@aashna aashna commented Apr 23, 2026

Add a sendEnhancedGHTelemetryEvent call (automode.routerDecisionRestricted) alongside the existing unrestricted routerDecision event. The restricted event lands in copilot_v0_restricted_copilot_event in Hydro and includes:

  • hydraScores: JSON-encoded 4-dim capability scores (reasoning, code_gen, debugging, tool_use)

  • binaryScores: JSON-encoded binary classifier scores (needs_reasoning, no_reasoning)

  • chosenModel, candidateModels, chosenShortfall, stickyOverride

  • All fields from the existing unrestricted event (confidence, latency, routingMethod, etc.)

This enables joining router quality data with user prompts in a single Hydro table without cross-cluster joins to ddtelvscode. Only available for users opted into restricted telemetry (~44%).

Copilot AI review requested due to automatic review settings April 23, 2026 21:32
@aashna aashna requested review from bhavyaus, devinvalenciano, lramos15 and luabud and removed request for bhavyaus and lramos15 April 23, 2026 21:34
@aashna aashna enabled auto-merge April 23, 2026 21:36
@aashna aashna changed the title copilot: emit router decision to restricted telemetry with prompt and full scores copilot: emit router decision to restricted telemetry full scores Apr 23, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a restricted/enhanced GitHub telemetry event for Auto Mode router decisions so router quality signals can be analyzed within the restricted telemetry pipeline.

Changes:

  • Emit a new automode.routerDecisionRestricted enhanced telemetry event alongside the existing automode.routerDecision MSFT event.
  • Include additional router output fields (candidate list, chosen model, hydra/binary scores, shortfall, per-class scores) in the restricted event’s payload and GDPR annotation.
Show a summary per file
File Description
extensions/copilot/src/platform/endpoint/node/routerDecisionFetcher.ts Adds a second telemetry emission to the enhanced/restricted pipeline with additional router score details and metadata.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 4

Comment thread extensions/copilot/src/platform/endpoint/node/routerDecisionFetcher.ts Outdated
Comment thread extensions/copilot/src/platform/endpoint/node/routerDecisionFetcher.ts Outdated
Comment thread extensions/copilot/src/platform/endpoint/node/routerDecisionFetcher.ts Outdated
Comment thread extensions/copilot/src/platform/endpoint/node/routerDecisionFetcher.ts Outdated
@aashna aashna force-pushed the aashnagarg/router-restricted-telemetry branch from 18c2832 to 9cd119c Compare April 23, 2026 23:30
Add a sendEnhancedGHTelemetryEvent call (automode.routerDecisionRestricted)
alongside the existing unrestricted routerDecision event. The restricted
event includes:

- hydraScores: JSON-encoded 4-dim capability scores
- binaryScores: JSON-encoded binary classifier scores
- chosenModel, candidateModels, chosenShortfall, stickyOverride
- Per-class scores (scoreNeedsReasoning, scoreNoReasoning)
- All fields from the existing unrestricted event
@aashna aashna force-pushed the aashnagarg/router-restricted-telemetry branch from 9cd119c to 672e30b Compare April 23, 2026 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants