Please use the latest version of vscode-extension-telemetry dependency

[ramya-rao-a]

This C++ extension uses version 0.0.11 of vscode-extension-telemtetry module.

The latest version of vscode-extension-telemtetry module (0.0.22) uses the latest version of applicationinsights module (1.0.5) which has the fix to prevent unnecessary patching of the require and other 3rd party modules.

For more details, please see microsoft/vscode-extension-telemetry#16

[ramya-rao-a]

@sean-mcmanus, @bobbrow I see that a PR was merged to use 0.0.22 version. Unfortunately, we recently learned of an issue where there are multiple powershell processes being spawned and stay stuck on older Windows versions when using version 1.0.5 of applicationInsights module.

This bug has been fixed in version 1.0.6 of applicationInsights module which is being used by version 0.1.0 of vscode-extension-telemtetry

Therefore, please update the version of vscode-extension-telemetry dependency to 0.1.0

[sean-mcmanus]

Thanks for letting us know. We've only shipped with the changes with our Insider builds so far, so we should be able to fix this for our release version.

[sean-mcmanus]

@ramya-rao-a Updating to the new vscode telemetry API is truncating our telemetry to 1000 characters. Our previous limit was 16384 characters. How can we increase the data limit for these particular cases that we need longer data? It looks like the regression started with 1.0.6 of applicationsInsights.

[sean-mcmanus]

This looks like bug microsoft/ApplicationInsights-node.js#444 . What version of vscode-extension-telemetry should we use? We're missing telemetry data which may be important so we'd like to switch to an older version.

[OsvaldoRosado]

Adding a note that even after a bugfix you shouldn't have a limit of 16K. The schema defined limit on custom dimension values is 8K, anything beyond this should be dropped by the telemetry ingestion endpoint. You should consider using a telemetry type designed for large data storage, like trace, rather than custom dimensions.

[ramya-rao-a]

You should consider using a telemetry type designed for large data storage, like trace, rather than custom dimensions.

@OsvaldoRosado Can you elaborate on this?

@sean-mcmanus You can use 0.0.22 version of the vscode-extension-telemetry

[OsvaldoRosado]

@ramya-rao-a Custom dimensions aren't intended for storing large amounts of data. Very long strings will not be accepted by our backend. The SDK truncates to avoid the backend dropping your telemetry entirely.

If long strings must be stored in telemetry, use trackTrace rather than putting the string in a custom dimension. Trace telemetry has a 32K length limit on its message field, rather than the 8K limit on custom dimension properties. https://github.com/Microsoft/ApplicationInsights-Home/blob/master/EndpointSpecs/Schemas/Bond/MessageData.bond#L13