pino

Now add pino and pino-http with custom serializers to redact passwords, tokens and apiKeys from the logging output.

We found a malicious npm package pino-sdk-v2 impersonating pino, one of the most widely used Node.js loggers with nearly 20 million weekly downloads.

The rest of the project is just copied from pinojs/pino.

Not only that, libs like pino don't even support spanning, something that's pretty important for how I use logging.

Does this provide a transport plugin for Winston [1], Pino [2], etc.?

And also for whatever reason, only the pino default export is instrumented.

I also had similar issues and wrote a guide on how to use LogLayer + pino to get server-side logs working properly.

Didn't pino palladino tour with him on that one?

This approach gives Pino a performance advantage in benchmarks.

Then, for the longest time I couldn't get the pino instrumentation working.

First, pino has to be added to serverExternalPackages.

To buy Pino Devine & I each got a 10,000$ bank loan.

The primary purpose of the "halua" logger is to provide easy control over log levels and output systems in a single place As of performance, let's address why "pino" is faster than console.log.

Pino seems to be catered for backend, while this project looks to be more for web clients?

Pino avoids using the console directly, as it is designed for the node environment and appears to utilize stdout.write for output.