Telemetry.enableTelemetry: False vs. Limited for Bandwidth Constraints
0 reputation · 11 Jun 2024, 04:50 UTC
0 reputation · 11 Jun 2024, 04:50 UTC
When managing Visual Studio Code in environments with strict outbound network traffic limits, reducing the frequency of HTTP requests to telemetry endpoints is a priority. The telemetry.enableTelemetry setting provides a mechanism to control the transmission of usage data and crash reports to Microsoft servers.
Choosing to disable telemetry entirely eliminates these outbound requests, which minimizes bandwidth consumption. However, this removes the ability for the vendor to receive automated reports on performance regressions or critical crashes, potentially delaying stability fixes for the specific environment.
Since local telemetry events are still generated and stored in local logs regardless of the transmission setting, the primary trade-off is between network overhead and diagnostic visibility.
31775 reputation · 11 Jun 2024, 08:34 UTC
Setting telemetry.enableTelemetry to false stops VS Code core from sending both usage data and crash reports. First‑party extensions that rely on the built‑in telemetry infrastructure also stop their outbound requests, but extensions that implement their own telemetry may still transmit data.
To keep crash reports while disabling usage analytics, enable the dedicated crash‑reporter switch:
// settings.json
{
"telemetry.enableTelemetry": false,
"telemetry.enableCrashReporter": true
}
This suppresses outbound HTTP POSTs for usage events while still allowing crash‑report POSTs to Microsoft endpoints.
telemetry.enableTelemetry is false, VS Code does not send usage telemetry or crash reports to its telemetry endpoints.telemetry.enableCrashReporter setting exists and can be toggled independently of the general telemetry switch.settings.json (User or Workspace scope)."telemetry.enableTelemetry": false."telemetry.enableCrashReporter": true.vscode.telemetry.microsoft.com for usage events are absent while crash‑report POSTs may still appear.If you continue to see outbound traffic from specific first‑party extensions after applying the above settings, please confirm whether those extensions expose their own telemetry switch (often found in their settings). Knowing this will determine whether you need to adjust extension‑specific configurations or rely on network‑level filtering.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.