Telemetry.enableTelemetry: False vs. Limited for Bandwidth Constraints

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.

• Does disabling core telemetry also suppress outbound requests from first-party extensions?
• Is there a documented configuration to allow only crash reports while blocking usage analytics to balance bandwidth and stability?