Closed binarykitchen closed 1 month ago
It looks like you are using pino-pretty
to format the written logs. Don't do that.
@jsumners
Right, done:
const forHumans = isLocal();
....
if (forHumans) {
transportTargets.push(pinoPretty);
}
:shrug:
What should I understand from that?
Please provide a minimal reproducible example. Doing so will help us diagnose your issue. It should be the bare minimum code needed to trigger the issue, and easily runnable without any changes or extra code.
You may use a GitHub repository to host the code if it is too much to fit in a code block (or two).
What should I understand from that?
It's all good. You already helped.
When you mentioned this:
It looks like you are using pino-pretty to format the written logs. Don't do that.
This made "click" in my head, and I've replied in code above: only use pinoPretty for when in local aka "human" mode :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
On a production Linux server, when you want to check the pino-generated logs, what command do you use and recommend?
Before I switched to pino, using a different format, this command worked:
But now, not anymore, due to this error:
Because a JSON was printed:
So, wondering what command you guys use for that? Thanks for any advice. Cheers :)