[Parser]: Custom LogLevels

Feature Request

It would be great to overwrite the log levels.

Describe the solution you’d like

A way to overwrite the log levels for printing. The methods should stay the same, just the print would change.

Teachability, Documentation, Adoption, Migration Strategy

Example from Pino using nestjs-pino

return LoggerModule.forRootAsync({
    imports: [ConfigModule],
    useFactory: (configService: ConfigService<Configuration>) => {
      const severityLookup: Record<string, string> = {
        default: 'DEFAULT',
        silly: 'DEFAULT',
        verbose: 'DEBUG',
        debug: 'DEBUG',
        http: 'INFO',
        info: 'INFO',
        warn: 'WARNING',
        error: 'ERROR',
      };

      return {
        pinoHttp: {
          formatters: {
            level(label, number) {
              return { severity: severityLookup[label], level: number };
            },
          },
        },
      };
    },
    inject: [ConfigService],
  });

What is the motivation / use case for changing the behavior?

Some cloud providers require certain log levels for their log collectors to pick it up properly. See Googles log levels as an example.

[jmcdo29]

@ogma/logger 2.0.0 was released yesterday. This is included in functionality of it

[jmcdo29]

I think I could make some sort of special or originalLevel property on the JSON work. I’d be concerned about it adding more clutter to the JSON, but usually devs aren’t looking at raw JSON anyways, so I don’t think it should be too big a deal. Maybe some sort of ool (Ogma original level) to keep the key short.