CorrelationContext.getCurrentContext() returning undefined when deeply nested

Our auto-collected dependencies are inconsistently being correlated to the request (operation).

It appears that CorrelationContext.getCurrentContext() is working properly if called directly within the middleware (express) but if called further down (within callbacks and/or promises) it is returning undefined.

I have hacked in a workaround using continuation-local-storage:

var cls = require('continuation-local-storage');
var ns = cls.createNamespace('my.request');


//hack hack hack
var correlationContextManager = require('applicationinsights/out/AutoCollection/CorrelationContextManager').CorrelationContextManager;
var origGetCurrentContext = correlationContextManager.getCurrentContext;
function getCurrentContext(){
  return ns.get('ctx') || origGetCurrentContext();
}
correlationContextManager.getCurrentContext = getCurrentContext;

module.exports = function (req, res, next) {

  ns.bindEmitter(req);
  ns.bindEmitter(res);
  ns.run(function(){
    ns.set('ctx', origGetCurrentContext());
    next();
  });

};

We have all auto-collection enabled:

appInsights.setup(config.appInsightsKey)
  .start();

We use bluebird promises heavily, which may affect how the underlying zones function.

[markwolff]

Closing this as Zone.js has been deprecated in favor of cls-hooked, so this is likely no longer an issue

[OsvaldoRosado]

This looks to me like you’re seeing the effects of multiple versions of zone.js being loaded. Notably the version of zone.js currently depended on in this SDK does not include the bluebird patch files or the __load_patch method it uses. This makes me suspect you’ve npm installed another version of zone.js that’s incompatible. We should perhaps switch zone.js to peerDependency so this isn’t possible