Append the process ID to the file name created for holding disk cached telemetry. This should resolve the issue with multiple Azure Functions cores attempting to read/write/delete the same file when functions are scaled to use multiple cores.
Extended this logic outside of Azure Functions so that in any case where the SDK could be run concurrently we create distinct cache files.
https://github.com/microsoft/ApplicationInsights-node.js/issues/1230
Append the process ID to the file name created for holding disk cached telemetry. This should resolve the issue with multiple Azure Functions cores attempting to read/write/delete the same file when functions are scaled to use multiple cores.
Extended this logic outside of Azure Functions so that in any case where the SDK could be run concurrently we create distinct cache files.