Releases: microsoft/ApplicationInsights-node.js
Releases · microsoft/ApplicationInsights-node.js
0.20.0
- #243, #238, #222 Readme revamping
- #240 Include typescript definitions in NPM package
- #239 Enable automatic dependency correlation by default
- #235 Add support for dependency collection and correlation using diagnostic-channel
- #237, #231, #219 Support for AppId-based cross component correlation
- #236 Fix issue where we send outdated baseTypes
- #234 Provide access to contracts
- #233 Allow for overriding application version
- #232, #228 Use autogenerated schema contracts
- #223, #218 Revamp method comment documentation
- #224, #211 Update npm build and install scripts
- #217 Add sampling support
- #221 Migrate from typings to types
- #213 Fix CORS error when using browserifty
- #210 Expose tagOverrides and contextObjects on more track APIs
- #212 Add schema and typescript files to npmignore
0.19.0
- #200 Allow durations to be longer than 24 hours
- #199 Remove obsolete fields from envelope
- #198 Restrict customProperties to kv pair of strings and add warnings discouraging sensitive info storage
- #197 Add national clouds to correlationExcludedDomains
- #195 Copying all descriptors of error properties
- #194 Fixed correlationHeaderExcludedDomains only cares about first value
- #191 Fix validateStringMap function
- #187 Add automatic correlation between dependencies and requests
- #178 Allow to disable console logging
This release includes an important change to tag override functionality available on track methods. Before this release, if an override tag object was provided it was used instead of the tags available on the client context. SDK behavior is now to merge the tags set on the override object with the client context. If you were using this functionality to remove default provided tags, you should instead identify the tags you wish to remove by name in your override object, and set them explicitly to null
, undefined
, or ""
.