Mark Wolff

[PerfCounters] Available memory metric does not match system values

2

https://github.com/microsoft/ApplicationInsights-node.js/blob/439bd18f74f167d903f40b2e63f872f934b8d089/AutoCollection/Performance.ts#L230 `AVAILABLE_MEMORY` metric is calculated with `os.fremem()`, which is [not equivalent to available memory](https://stackoverflow.com/questions/51911849/node-js-os-freemem-do-not-work-correctly). An investigation should be done on how to properly measure and track this metric

feat: add mssql subs/tests

1

Requires https://github.com/microsoft/node-diagnostic-channel/pull/68 - Adds TDS patch subscribers, function tests

[core-http] Add compression request policy (gzip)

2

Monitor sends gzipped http requests by default with an uncompressed fallback. https://github.com/Azure/azure-sdk-for-js/pull/10615#discussion_r470286416