iamolegga

@rojomisin yes, but still not available 😅 checked just now

Hi, I'm ready to merge a PR that's reviewed by anyone else from the community

@KieronWiltshire answering your [question from different issue](https://github.com/iamolegga/nestjs-pino/issues/1191#issuecomment-1292098953) Some thought on design for this feature: I believe the configuration for microservices should be as close as possible to the configuration of...

> @iamolegga consider setting up a bounty program. I'd be willing to contribute funding for you to do this if you'd prefer to handle it yourself. I'm ok to handle...

> sorry, didn't mean to insult no worries 🙂 > this package assumes the logging through HTTP or now at this point, microservice, but what about during queue workers etc....

So what's the difference from current implementation that doesn't fit your needs? You can use NestJS built-in logger as a facade for pino implementation. If you don't need automatic logging...

Have you tried something like: ```ts LoggerModule.forRootAsync({ imports: [ConfigModule], inject: [ConfigService], useFactory: async (config: ConfigService) => { return { pinoHttp: { logger: pino(pino.transport({ target: 'my-transport', options: config.transportOptions })), }, };...

> that only allows transport for the pino-http module @KieronWiltshire could you please open an issue with the bug type and a minimal example repo? > Would you consider reopening...

👍 for this feature, exactly `job.cancel()`

Hi, I'm gonna try to solve this soon, just wanted to clarify something before writing code: I've just dived to the problem with overwriting headers. So, what I think is...