1.0.7

• #444 Fix incorrect custom dimension length truncation
• #449 Fix metric used for memory usage performance counter
• #446 Fix 3x duplicated request telemetry in applications using socket.io
• #433 Fix TypeScript error in applications using Node 10 types

1.0.6

• #438 Fix spawned PowerShell processes hanging on Windows 7
• #437 Fix infinite ACL related PowerShell processes spawning if one hangs
• #371, #428 Fix nested custom properties report as [object Object], null/undefined property values are dropped

1.0.5

• #426 Remove unused dynamic imports that prevented this SDK from being Webpack-friendly
• #427 More strictly apply the APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL environment variable to completely prevent loading diagnostic-channel when present

1.0.4

• #407 Fix error for undefined agent with puppeteer
• #416 Replace existing GUID id generation with an implementation that is compatible with W3C trace-id
• #420 Add restrictions against insecure TLS/SSL versions by default

The changes in this release to disable TLS versions earlier than 1.2 may impact you if you use a custom telemetry endpoint over HTTPS with an older TLS protocol. You can restore the previous behavior by supplying a custom https.Agent that is not configured with this restriction. See the "Advanced configuration options" section of the README for how to supply a custom https.Agent instance to this SDK.

1.0.3

• #246, #382, #400 Respect http_proxy and https_proxy environment variables. Allow for configurable HTTP(S) proxies and Node.js http agents.
• #395 Fix ACL related errors in App Services and Azure Functions. Adjust connection error logging to be more error-tolerant.
• #394 Fix missing propagation of ai_authUser cookie to userAuthUserId tag.
• #398 Fix broken correlation with some non-node SDKs and incomplete views of correlation within the Azure Portal

1.0.2

• #344 Missing test for package.json pathfinding
• #346 Receiving "Zone already loaded" error when requiring AI client in Function App
• #358 MAC signature error when reading files from Azure File Storage
• #362 TypeError: Cannot read property 'indexOf' of null
• #365 trackNodeHttpRequest does not follow type contract
• #368 Custom .trackRequest and .trackDependency not appearing in Application Insights telemetry data
• Improved internal logging coverage
• Fixes for stability issues with retry caching from disk

1.0.1

• #352 Dependency calls over HTTPS are not detected on Node 8.9.0
• #351 Sample rate should not be applied for metrics telemetry
• #349 Double dependency reporting for HTTP requests
• #348 getCorrelationContext() doesn't return correlation context
• Dependency telemetry does not contain result code
• Dependency calls over HTTP are not detected on some versions of Node

This patch release to 1.0.0 contains several important fixes for both automatic and manually tracked dependency collection. If you are missing dependency telemetry, or notice missing fields such as resultCode, updating to 1.0.1 is suggested.

1.0.0

• #333 SamplingTelemetryProcessor should ignore metrics
• #331 Unable to end node process
• #330 TSC fails to compile if SDK is used in an app with TSC < 2.4.0
• #329 TSC fails to compile if SDK is used in an app with node 0.12 types
• #328 Add functional tests to cover all diagnostic channel autocollection
• #326 EnvelopeFactory StackFrame parsing can't parse correlated stack frames
• #321 TelemetryClient.trackDependency should not assume 'data' property is a URL
• #319 Add calls to enable winston and postgres

This is the first stable release of the Application Insights Node.js SDK.

Changes since 0.22.0 are primarily bugfixes and stability improvements. Please read the migration section of the readme if you are upgrading from a version prior to 0.22.0.

0.22.0

• #155, #282 Documentation improvements
• #289 Performance counter data rate improvements
• #311 Set up of auto-correlation for http.createServer does not cover all cases
• #284 Multi-component application maps require cloud_RoleName
• #225 Better differentiate Client and Server requests
• #202 Offline mode does not persist endpoint with file, leading to date being sent to wrong endpoints
• #285 OS Reporting gives broken string
• #148 Tracking custom requests
• #286 Specify resultCode when using trackDependency
• #302, #269 Refactor API
• #256 Cannot find module diagnostic-channel
• #63 Exceptions are stored on disk even if offline mode is off and are never sent
• #56 Dispose not removing timers and exception handlers
• #147 Failure in telemetry processor should not fail telemetry delivery

This release includes breaking changes across most of the SDK in order to bring consistency with other Application Insights SDKs and allow future extensibility. Please review the README for new method and property names. For additional detail on the track API, review #302.

In general, you can migrate with the following:

• Replace references to appInsights.client with appInsights.defaultClient
• Replace references to appInsights.getClient() with new appInsights.TelemetryClient()
• Replace all arguments to client.track* methods with a single object containing named properties as arguments. See your IDE's built-in type hinting, or TelemetryTypes, for the expected object for each type of telemetry.

If you access appInsights configuration functions without chaining them to appInsights.setup(), you can now find these functions at appInsights.Configuration (eg. appInsights.Configuration.setAutoCollectDependencies(true))

Changes to default configurations also exist in this SDK. Primarily, storing telemetry to disk when your app is offline is now enabled by default.

0.21.0

• #265, #278, #279, #280 Add support for new correlation headers and exporting custom properties cross-server
• #271 Update travis ci definitions
• #274 Fix trackDependency serialization when used with fractional milliseconds
• #272 Clear all usages of implicit any
• #276 Update diagnostic-channel-publishers to 0.1.3
• #277 Fix flaky unit test failures