Releases: microsoft/ApplicationInsights-JS
2.3.1
2.3.0
2.2.4
2.2.3
#1051 Add to call track trace on user init sending browser info to the end point when loggingLevelTelemetry config is on
#1050 Address issue MicrosoftDocs/azure-docs#39011
#1049 Fix issue with PageViewPerformance event being sent with undefined name property
#1041 Add tslint error screening
#1038 Re-organize repo folders
#1035 Update to use PerformanceNavigationInterface for supported browsers
2.2.2
2.2.1
Changelog
#1015 Update to use beaconSender for page unload when browser supports Beacon API
#1028 Fix issue where window.location is not defined
#1021 Fix issue with not parsing correlationContext
#1020 Disable by default logging to console internal SDK errors. Enable by default logging as telemetry for internal SDK errors
2.2.0
Changelog
- #946 Feature: Adds automatic incoming/outgoing header tracking. Outgoing header tracking is experimental and may be miss some headers
- #973 Feature: Support propagation of W3C compatible distributed tracing headers
- #983: Fix issue regarding incorrect referrer uri when using
enableAutoRouteTracking
- #984: Fix issue where adding custom properties/tags would not work in telemetry processors
- #999: Fix IE issue when using
enableAutoRouteTracking
- #1000
2.1.1
2.1.0
2.1.0 Highlights
Source Map Support
*You do not need to upgrade for drag and drop to work. It will work on all previous and future versions of the javascript (and Node.js) SDK
https://i.imgur.com/Efue9nU.gif
You can now drag and drop your source maps onto your Exception Telemetry in the Azure Portal to unminify your callstack. Please open an issue or use the Feedback button in the Portal if a source map you've uploaded is not working as intended. This is a first iteration and in a future update, your source maps will be automatically unminified.
SPA Route Change Tracking
You can set enableAutoRouteTracking: true
to enable state based route tracking for your Single Page Application (React, Angular, Vue, etc). You do not need to install a separate plugin to use this configuration option.
This setting will cause a new Page View telemetry item to be sent each time your app's route changes (including Hash route changes).
Changelog
- #920 Resolve jest testing issues when using React plugin
- #928 Make analytics plugin have last priority
- #936 Fallback to XHR Sender when beacon sender tries to send >64 KB
- #947 Add SPA route change tracking
- #948 Docs: Source map support
- #952 Re-enable
samplingPercentage
functionality - #918, #919, #932 #933 #935 #939 #940 #951
2.0.1
trackException Change
This update has a couple of non-breaking API changes. Namely, trackException
is now consistent with the Node.js SDK. The only change here is the named argument is renamed from error
to exception
. A shim is in place so any existing usages of trackException
will still work, and the old field is marked as optional, so any type-checked files will still "compile". There are no breaking changes with this change, but you are encouraged to use exception
as your named argument field as error will be deprecated in a future major version.
Old
appInsights.trackException({ error: new Error() });
New
appInsights.trackException({ exception: new Error() });
Correlation Header Domain Whitelisting #869
Second, the ability to only send correlation headers to specific, whitelisted domains is now available as a configuration option , correlationHeaderDomains
. It accepts an array
of domain strings
. Wildcards ("*") are okay. By populating this array, all other domains which your application makes requests to will not have correlation headers included. This setting makes it easy to avoid OPTIONS requests to services outside of your control.
You can use the inclusion list and the exclusion list in conjunction with each other to add correlation headers to a particular domain, example.com
, and at the same time exclude headers from a prefixed version of it, no-headers.example.com
.
Tag Override Change #903
Performing custom tag overrides is now more consistent with all of the other Application Insights SDKs, in that it is modified via a simple key-value dictionary. There are no breaking changes with this update, and if you are setting any tags via the old way, they will still work as they do now. You are encouraged to update them since the old way will be deprecated in a future major version release.
Old
var telemetryInitializer = (item) => {
item.tags.push({ "ai.cloud.role": "My Web App" });
};
appInsights.addTelemetryInitializer(telemetryInitializer);
New
var telemetryInitializer = (item) => {
item.tags["ai.cloud.role"] = "My Web App";
};
appInsights.addTelemetryInitializer(telemetryInitializer);
Changelog
#869 - config: add ability to whitelist specific domains for adding correlation headers
#893 - docs: fix sample configuration settings
#899 - common: replace Array.some with Array.forEach to simplify polyfill story, add tests
#902 - snippet: add missing methods to lazy loaders
#903 - tags can now be set with same API as other AI SDKs
#904 - rename IExceptionTelemetry.error --> IExceptionTelemetry.exception
#905 - react: fix plugin causing jest tests to fail
#907 - docs: add mention of how to update current context's operation
#908 - react: remove analytics package dependency
#910 - docs: update context refresh information
#913 - Remove code from adding libVer from extensions
#918 - automatically add ai.operation.name
tag, add id
to pageview telemetry
#919 - fix issue with namePrefix
not affecting send buffers