[FEATURE REQUEST] Logger usage outside HTTP context

• I’ve read the docs of nestjs-pino
• I’ve read the docs of pino
• I couldn’t find the same question about nestjs-pino

Question

I’m trying to use logger.assign outside of HTTP context. Specifically, inside sqs consumer’s handleMessage function.

I figured out with the help of #788 to initiate the storage.run on my own. The problem was that i don’t have access to req.log so i used PinoLogger.root instead. Is this supposed to be used like this?

import { storage, Store } from 'nestjs-pino/storage';
import { PinoLogger } from 'nestjs-pino';

---

    this.consumer = Consumer.create({
      // this magic creates AsyncLocalStorage context
      // for nestjs-pino to work with. It allows the use
      // of this.logger.assign() method.
      handleMessage: message =>
        storage.run(new Store(PinoLogger.root), () =>
          this.processMessage(message),
        ),
    });

It seems to work fine. But want to make sure we won’t break something in strange ways.

I guess this also relates to @nestjs/bull and @nestjs/microservices are those environments supported? As they are similarly not inside HTTP context (not passing middlewares afaik).

Edit: If this is a valid usage, maybe it could be wrapped in a nicer withNestPinoContext(() => this.processMessage(message)) like function.

[iamolegga]

OK, in next month or two I’m going to investigate if it’s possible to make such feature work with different microservices’ transports including custom strategies.

For implementing this feature in a clear way we need middlewares for microservices to be landed in nest. Until then this solution could be used.

[iamolegga]

Desired behavior is not supported at the moment. You can try any hacks (as presented above) to make it work but on your own risk. This is not tested and not supported.

For this feature we need something similar to pino-http-like settings with a lot of settings beside pino-related ones. So this is huge feature and it need a lot of time for implementation. Unfortunately I’m not able to invest in this at the moment. But maybe this year on my current project we will need such feature too, then I think we can invest some time for this. But that’s not 100%. In case anyone would like to implement this, feel free to open detailed RFC for this first, before opening PR.

Will change this issue to feature request.