[Feature Request] Allow to disable console logging or allow to provide custom logger about nestjs-sentry

[holm]

I was just looking to solve the same problem. It would be nice to be able to separate these concerns.

[doctorrokter]

@holm for now I have a temp workaround in my project:

• manually edited source code in /node_modules and simply disabled super.log, super.error etc calls inside SentryService.
• created a patch using npx patch-package @ntegral/nestjs-sentry
• added a post-install hook into package.json file which will run patch every time.

Definetely worth a try to fork the repo, get rid of inheritance and do a PR.

Rather than extending ConsoleLogger class would be better to implement LoggerService interface instead. In that case we still will have NestJS-like logging API.
And in addition we could provide custom logger class (or instance) during SentryModule initialization to let SentryService write custom logs if we want.

[doctorrokter]

@ntegral @holm created PR for that FR, hope it looking not bad:

#54

[holm]

Awesome. Thanks for doing that. Added a few comments on the PR, just from my perspective, although of course this is not my library at all :)

[foxted]

Looks like by using the instance directly, it doesn't log into the console. So using: this.sentry.instance().captureMessage() instead of this.sentry.log().