Can’t see logs of levels silly, verbose, debug, fine in Nest

[tukusejssirs]

I use Ogma in Nest. When I try to log messages of silly, verbose, debug, fine levels, nothing is output.

In the module, I have this:

@Module({
  imports: [
    OgmaModule.forRoot({
      interceptor: {
        http: FastifyParser
      },
      service: {
        application: 'app-name',
        color: true,
        json: false,
        // It does not matter what log level I set in here.
        logLevel: 'ALL'
      }
    }),
    OgmaModule.forFeature(SomeService.name)
  ]
})
export class SomeModule {}

In the service, I have this:

@Injectable()
export class SomeService {
  constructor(@OgmaLogger(SomeService.name) private readonly logger: OgmaService) {}

  someMethod() {
    // These logs won't show up.
    this.logger.silly('some log')
    this.logger.verbose('some log')
    this.logger.debug('some log')
    this.logger.fine('some log')

    // These logs work as expected.
    this.logger.info('some log')
    this.logger.log('some log')
    this.logger.warn('some log')
    this.logger.error('some log')
    this.logger.fatal('some log')
  }
}

Is there something I am missing or is it a bug?

[jmcdo29]

That's super interesting. Got a reproduction you can share with it? Everything looks fine

[jmcdo29]

You don't happen to somehow call OgmaModule.forRoot() twice in your server do you? I'm wracking my brain here trying to think of what could be happening

[tukusejssirs]

Well, no, not in SomeModule module. However, I have a Nest library that I import in SomeModule and that library also imports OgmaModule.forRoot() and OgmaModule.forFeature(). Both are in an Nx monorepo.

Could that be related? 🤔

[jmcdo29]

I think so. Under the hood, OgmaModule.forRoot() ends up calling to OgmaCoreModule.forRoot() which sets up a couple of global providers. If forRoot() gets called to multiple times, it could be overwriting the providers from earlier and no longer persisting the options from the first call

[tukusejssirs]

Okay, so how should I deal with this? Should I simply remove OgmaModule.forRoot() from the library and keep there only OgmaModule.forFeature()? I’ve just tried that out, but it still does not work.

Just I note: I use an env var (LOG_LEVEL) which is used to define the log level throughout all apps (gateway and microservices), thus it should be the same. I’ve set it to ALL, but I don’t get any messages of silly, verbose, debug, fine level.

[jmcdo29]

Hmm, that's super strange. Really wish there was a way to replicate this, cause it sounds like a possible configuration issue, but it's hard to say why, y'know?

[tukusejssirs]

If this is a TCP server, you should use rpc: TcpParser

Just to make sure: in TCP microservices I should use rpc: Parser and in gateway (regular Nest app with Fastify) I should use http: FastifyParser, right?

Hmm, that's super strange. Really wish there was a way to replicate this, cause it sounds like a possible configuration issue, but it's hard to say why, y'know?

It does not matter if I log the messages in a microservice or in the gateway, it always defaults to INFO log level and thus I get only a subset of logs.

Yeah, it seems to be a configuration issue, as I am still quite new to TS/Nest/Nx and evething in between (I work with these for about a year and I have only self-taught myself from online resources).

I understand it is hard to debug without a reproduction. I’ll try to find some time to reproduce it again, however, the thing is I have no idea what to reproduce and is not needed. The code is quite complex, thus there might be to many stuff that (potentially) could interfere.

---

Anyway, I removed OgmaModule.forRoot() from the library, however, it didn’t solve the issue.

[jmcdo29]

Quick question: are you using a hardcoded string for the log level or is it a env variable or ternary expression here?

---

Just to make sure: in TCP microservices I should use rpc: Parser

Yes

in gateway (regular Nest app with Fastify) I should use http: FastifyParser, right?

Yes

It does not matter if I log the messages in a microservice or in the gateway, it always defaults to INFO log level and thus I get only a subset of logs.

And these are separate applications, so they shouldn't be sharing configuration which makes this even weirder

[tukusejssirs]

Quick question: are you using a hardcoded string for the log level or is it a env variable or ternary expression here?

For debugging purposes, I hard-coded it to ALL string, otherwise I use an env variable defined in a file, loaded at gateway startup, validated if it contains a valid value, defaults to WARN if not provided or if invalid value provided. No ternary expression is used in this case.

Thanks for the answers. 🙏