src/vs/platform/agentHost/common/agentHostTelemetryEnv.ts
48 LOC · 48 covered · 0 uncovered · 2 ranges · 1486 concepts · 2 introducers · 686 tests
File neighbourhood
The centred file is linked to every concept that introduces one of its ranges, every test that runs code from the file, and the gray connector concepts standing between those tests and the file's own introducer concepts. Undirected links join concepts to every file where they introduce source and concepts to the tests they introduce; arrows show specialization between the displayed concepts and bridge only concepts omitted from this view. Concept colors match the source ranges below; connector concepts have no source color and are shown in gray.
Focused file, its introducer and connector concepts, their introduced files, and tests that run code from the file
In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the related-file, concept, and source links on this page.
Graph controls are ready.
Interactive rendering requires JavaScript and WebGL. Use the related-file, concept, and source links on this page while the interactive map is unavailable.
/*---------------------------------------------------------------------------------------------
agentHostTelemetryEnv.ts ×1
* Copyright (c) Microsoft Corporation. All rights reserved.
* Licensed under the MIT License. See License.txt in the project root for license information.
*--------------------------------------------------------------------------------------------*/
/**
* Environment variables used to forward the host's resolved telemetry
* identifiers into the agent host process.
*
* The agent host runs in its own utility process and would otherwise compute
* its own `machineId`/`devDeviceId` live from the MAC address / device-id store
* on every launch. That can diverge from the workbench's persisted, state-backed
* identifiers (e.g. when `state.json` was seeded by imaging/migration, or when
* the "first valid MAC" changes), breaking per-user joins across event sources.
*
* To keep the identifiers consistent, the local starter
* (`ElectronAgentHostStarter`, which runs in the main process where these are
* already resolved) forwards them via these env vars, and
* `createAgentHostTelemetryService` prefers them over recomputing.
*/
export const AgentHostMachineIdEnvKey = 'VSCODE_AGENT_HOST_MACHINE_ID';
export const AgentHostSqmIdEnvKey = 'VSCODE_AGENT_HOST_SQM_ID';
export const AgentHostDevDeviceIdEnvKey = 'VSCODE_AGENT_HOST_DEV_DEVICE_ID';
export interface IAgentHostForwardedTelemetryIds {
readonly machineId: string;
readonly sqmId: string;
readonly devDeviceId: string;
}
/**
* Builds the env var bag that forwards the resolved telemetry identifiers to
* the agent host process. Empty identifiers are omitted so the host falls back
* to computing them itself.
*/
export function buildAgentHostTelemetryIdEnv(ids: IAgentHostForwardedTelemetryIds): Record<string, string> {
if (ids.machineId) {
env[AgentHostMachineIdEnvKey] = ids.machineId;
}
if (ids.sqmId) {
env[AgentHostSqmIdEnvKey] = ids.sqmId;
}
if (ids.devDeviceId) {
env[AgentHostDevDeviceIdEnvKey] = ids.devDeviceId;
}
return env;
}