Conflict between @nestjs/cls and elastic-apm-node - apm.currentTransaction becomes undefined

[weikangchia]

I’m using NestJS with both nestjs-cls and elastic-apm-node to trace requests and store app context.

Problem:
As soon as I enable ClsModule with ClsModule.forRoot() in AppModule, the APM context is lost. Specifically:

apmInstance.currentTransaction // becomes undefined

How can I use both NestJS CLS and Elastic APM without losing APM context? Has anyone successfully used both together in production?

[Papooch]

I have no idea, honestly, as I've never used that package, so I can't really provide any support here.

I've been using nestjs-cls together with OpenTelemetry, which also uses AsyncLocalStorage under the hood with no problems.

[weikangchia]

Thanks, shall try using OpenTelemetry and see if it works for us.