Closed timlohse1104 closed 1 year ago
With option --hideMetadata it is possible to transform a basic log line like this:
--hideMetadata
[25.7.2023, 15:57:32] INFO: [Nest] 25.7.2023, 15:57:32 [RoutesResolver] | OcrController {/ocr}: {"context":"RoutesResolver"}
into a simulated NestJS log line like this (provided you use the messageFormat option):
messageFormat
[Nest] 25.7.2023, 15:57:32 [RoutesResolver] | OcrController {/ocr}: {"context":"RoutesResolver"}
--hideMetadata option effectively hides epoch, leveland other metadata like reqId from beeing printed in front of the actual log message.
epoch
level
reqId
@jsumners or @mcollina What do you think? Would love to provide you with further pull requests.
I'm closing this due to lack of response. If you'd like to finish this work, please open a new PR.
See https://github.com/pinojs/pino-pretty/issues/444
With option
--hideMetadata
it is possible to transform a basic log line like this:[25.7.2023, 15:57:32] INFO: [Nest] 25.7.2023, 15:57:32 [RoutesResolver] | OcrController {/ocr}: {"context":"RoutesResolver"}
into a simulated NestJS log line like this (provided you use the
messageFormat
option):[Nest] 25.7.2023, 15:57:32 [RoutesResolver] | OcrController {/ocr}: {"context":"RoutesResolver"}
--hideMetadata
option effectively hidesepoch
,level
and other metadata likereqId
from beeing printed in front of the actual log message.