format logging information (?)

[JonathanLoscalzo]

With console and file, I design my own format for log:

...
format: winston.format.combine(
            winston.format.colorize(),
            winston.format.timestamp(),
            winston.format.printf(info => `[${info.label}] ${info.timestamp} ${info.level}: ${info.message}`)
        )
....

with printf

How Could I format with a similar approach with winston-mongodb? :-)

[samuelgoldenbaum]

yip, needed

[KarlNilsson]

Any update on this? Trying to use this as a middleware error logger in my express application, with the following code:

app.use(
    WinstonExpress.errorLogger({
      transports: [
        new MongoDB.MongoDB({
          level: 'error',
          db: `${loggerDBConfig.database}/logging`,
          options: {
            useNewUrlParser: true,
            useUnifiedTopology: true,
            auth: {
              user: loggerDBConfig.username,
              password: loggerDBConfig.password,
            },
          },
        }),
      ],
      format: winston.format.combine(
        winston.format.timestamp(),
        errorLogFormat
      ),
    })
  );

It seems like the format is not even applied for the MongoDB transport. It never hits my debugger breakpoint. It does do that if I add another transport, such as winston.transports.File(...). My current output to MongoDB looks like this

{
    _id: ObjectId('5ee0ea740d745a01c38b0f6f'),
    timestamp: ISODate('2020-06-10T14:13:08.422Z'),
    level: 'error',
    message: 'middlewareError',
    meta: null
}

Not very useful as of now. What I'm trying to accomplish in my errorLogFormat function is to extract data.meta.message which contains the actual error message. Any pointers on how to achieve this?

[BaalDev-Solutions]

This is a needed feature. The logger itself is not really useful without this

[BaalDev-Solutions]

@JonathanLoscalzo, @samuelgoldenbaum, @KarlNilsson. There is a dirty trick you can you do for overcoming this problem without changing all your implementation. Create two loggers, one without the MongoDb transport and other with it. Then in the logger that does not have the MongoDb transport activate add a format function, and in that function call to your other logger with the desired format.

Dirty and not really efficient. But works.

[zolero]

Could you add this feature @yurijmikhalevich? This is important to do some detailed reporting.