chore(core): reassign telemetry keys to avoid server conflict (#18161)

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
This commit is contained in:
matt korwel
2026-02-03 06:43:57 -06:00
committed by GitHub
parent ad8796b02d
commit a8b4c38c89
7 changed files with 113 additions and 15 deletions
+3 -3
View File
@@ -489,7 +489,7 @@ describe('Telemetry Metrics', () => {
initializeMetricsModule(mockConfig);
const event = new ModelRoutingEvent(
'gemini-pro',
'classifier',
'Classifier',
200,
'test-reason',
true,
@@ -502,7 +502,7 @@ describe('Telemetry Metrics', () => {
'installation.id': 'test-installation-id',
'user.email': 'test@example.com',
'routing.decision_model': 'gemini-pro',
'routing.decision_source': 'classifier',
'routing.decision_source': 'Classifier',
'routing.failed': true,
'routing.reasoning': 'test-reason',
});
@@ -513,7 +513,7 @@ describe('Telemetry Metrics', () => {
'installation.id': 'test-installation-id',
'user.email': 'test@example.com',
'routing.decision_model': 'gemini-pro',
'routing.decision_source': 'classifier',
'routing.decision_source': 'Classifier',
'routing.failed': true,
'routing.reasoning': 'test-reason',
'routing.error_message': 'test-error',