Hector Hernandez
Hector Hernandez
@johnib correlation will be stored using [cls-hooked](https://www.npmjs.com/package/cls-hooked) or [continuation-local-storage](https://www.npmjs.com/search?q=continuation-local-storage) if using node.js < 8.2.x, these libraries will take care of multiple contexts by requests and associated callbacks, sounds like something...
Application Insights code to handle the request "ending " is available [here](https://github.com/microsoft/ApplicationInsights-node.js/blob/develop/AutoCollection/HttpRequests.ts#L239), it should end the correlation and generate the request telemetry, is there a specific HTTP event being triggered...
@johnib context should be maintained for all code executed in the request, the SDK will bind to cls-hooked session/workspace [here](https://github.com/microsoft/ApplicationInsights-node.js/blob/develop/AutoCollection/HttpRequests.ts#L110), code I share before just end the request and create...
@AXLLLOW are you enabling Application Insights in Azure Portal?  If you are running in Azure Windows App Service is possible .NET Application Insights SDK is generating the unexpected telemetry,...
@asklar error looks like a configuration issue with webpack, other person was having similar issue before please take a look at the conversation [here](https://github.com/microsoft/ApplicationInsights-node.js/issues/710#issuecomment-763128225)
@vpetersen can you provide some repro environment?
@brianpham93 there is a plan for this SDK to fully support [Open Telemetry](https://github.com/open-telemetry/opentelemetry-js) next semester, OpenTelemetry Winston integration is available [here](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-winston) I don't know if primitive type metadata is supported...
@krystianolech unfortunately we do not support that in the SDK, like you mentioned the root request could fail once all the other telemetry was already generated, we sample using a...
@LitalReuveni we are not adding support for full transaction logging for failed requests when sampling is enabled, that will require big changes on how the sampling works in this SDK...
The context is used to build the telemetry envelopes that eventually would be send to ingestion endpoint, every "track" call will use it, having different user_id properties mean your "intercept"...