Closed omidkrad closed 4 years ago
Thanks for raising this. We're working with the current maintainer to move this package forwards.
Transferred to the new datalust/pino-seq repository.
Fixed in #2 :)
This is still an issue in build 9.4.0
@SquareLi thanks for the note. The current package version is 1.2.0 so the build number you mention might be of Pino itself. Since this was resolved long ago, it's likely the details and causes of a similar issue now will be different - a new ticket with an example of what you're logging, what you get in Seq, and what is expected, is needed for us to track this down. Thanks!
Since pino-seq does not have issues section I'm submitting this issue here. The project owner of
pino-seq
is @simihartstein.Please see comments below:
Note that the
log.error({ err })
syntax is recommended by pino author but it doesn't work withpino-seq
. This could be related to an issue withseq-logging
that is used bypino-seq
.