Sentry Profiling Integration doesn't work about nestjs-sentry

[StPaulis]

Any news about that? I can confirm that the problem exists in 7.36.0 also.

[AdamGerthel]

Has anyone managed to solve this issue?

[svachmic]

This seems to be a problem with all integrations. I get type error since @nestjs version 9.2.1 and @sentry version 7.26.0.

Versions 9.1.6 and 7.17.2 work fine.

The problem is probably somewhere between NestJS -> ntegral -> Sentry.

[yepMad]

@sentry/tracing not working either? Or it's the same package?

[AdamGerthel]

@sentry/tracing not working either? Or it's the same package?

According to the Sentry docs for NodeJS, tracing is already enabled: https://docs.sentry.io/platforms/node/performance/#enable-tracing

[StPaulis]

Has anyone managed to solve this issue?

I end up using the plain @sentry package.

I forked a repository with a generic nestjs implementation and develop this to support tracing.

[ossamaweb]

It appears that SentryService gets initiated twice. And because of that Sentry.init gets called twice also.

A workaround:

1. Add fromFactory guard in sentry.service.ts constructor to initiate Sentry.

constructor(
    @Inject(SENTRY_MODULE_OPTIONS)
    readonly opts?: SentryModuleOptions,
    readonly fromFactory?: boolean
  ) {
    super();
   ...
   if (fromFactory) {  // <-- here
      Sentry.init(opts);
    }
  ...
}

2. Add it to the Service instantiation in forRootAsync/ forRoot in sentry-core.module.ts

public static forRootAsync(options: SentryModuleAsyncOptions): DynamicModule {
    const provider: Provider = {
      inject: [SENTRY_MODULE_OPTIONS],
      provide: SENTRY_TOKEN,
      useFactory: (options: SentryModuleOptions) =>
        new SentryService(options, true), // <-- here
    };
   ...
}

[ossamaweb]

Has anyone managed to solve this issue?

@AdamGerthel @StPaulis check my workaround above.