Pass options to pino logger

[rishi-afk]

Looks like Payload is making use of Pino for logging. It would be great to see if we could pass an optional configuration to the Payload config to setup Pino for a more standard logging setup to log data along with the request context and also disabling pretty json print.
This would help a lot as I am using Payload as a microservice and would benefit from a more standard logging setup. Any feedbacks are welcome. Thank you.

[denolfe]

Hey @rishi-afk, this is something we can look into. I don't think it would be too difficult to add some logger override options to the payload config. Thoughts on that?

[denolfe]

I've done some initial investigation on this. We do some logging before loading the Payload config, so I'm mulling over the best way to go for that. No ETA, but this is definitely considered planned work in the next few weeks.

[zaunermax]

@denolfe I remember that being a problem in the nestjs framework as well. So they then introduced a parameter which was smth like bufferLogs which lets you decide if all logs shoud adhere to a custom config which as loaded later on in the bootstrap process or if nest just logged the bootstrap logs with its own config and then continued with the custom config once it was loaded. Maybe this is useful input 🙌

[jmikrut]

Hey @rishi-afk — this has now been deployed as of 0.15.4 and documentation can be found here!

[rishi-afk]

@denolfe @jmikrut This looks great. Finally we can move into production. Payload is just getting better and better 🙌

[DanRibbens]

Just a heads up—we had a bug in yesterdays release that is now fixed in 0.15.5.