ApplicationInsights-JS

Upgrading from v1.x -> v2.x of Application Insights

Breaking changes in the SDK V2 version:

• To allow for better API signatures, some of the apis such as trackPageView, trackException have been updated.
• ES3 (IE8) compatibility, while running in IE8 or lower versions of the browser is not an officially supported scenario we are working to maintain ES3 level compatibility to ensure that the SDK will not cause any unexpected failures due to Javascript parsing error. See ES3/IE8 Compatibility below for further information.
• Telemetry envelope has field name and structure changes due to data schema updates.
• Moved context.operation to context.telemetryTrace. Some fields were also changed (operation.id –> telemetryTrace.traceID)
  • If you want to maunally refresh the current pageview id (e.g. in SPA apps) this can be done with appInsights.context.telemetryTrace.traceID = generateW3CId()

If you are using the current application insights PRODUCTION SDK (1.0.20) and want to see if the new SDK works in runtime, please update URL depending on your current SDK loading scenario:

a) Download via CDN scenario: Update code snippet that you currently use to point to the following URL: "https://js.monitor.azure.com/scripts/b/ai.2.min.js"

b) NPM scenario: Call downloadAndSetup to download full ApplicationInsights script from CDN and initialize it with connection string.

appInsights.downloadAndSetup({
    connectionString: "InstrumentationKey=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx",
    url: "https://js.monitor.azure.com/scripts/b/ai.2.min.js"
});

Test in internal environment to verify monitoring telemetry is working as expected. If all works, please update your api signatures appropriately to SDK V2 version and deploy in your production environments.

This site is open source. Improve this page.