lwlog VS pino

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project:https://github.com/ChristianPanov/lwlog

I am working on a c++ logging library, which you can check out here: https://github.com/ChristianPanov/lwlog

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project:https://github.com/ChristianPanov/lwlog

• UTF support

I have done benchmarks against spdlog, and you can take a look at them in the README in the repository

Also benchmarking is not done correctly in the main repository. I have benchmarks in my private dev repository and I am benchmarking either with picobench or nanobench. So if you want to benchmark, do NOT rely on the Benchmark.h file in the project (it's a temporary file that is meant to be removed)

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project: https://github.com/ChristianPanov/lwlog

Learn more about logging in Fastify and how to customize the Pino logger.

The Fastify framework includes the Pino logger by default (a really great logger with lots of cool features that doesn't compromise on performance). The framework itself allows a lot of really cool stuff, like controlling the level of logs at runtime.

Fastify provides a built-in logging mechanism based on Pino that allows you to capture various events in your applications. Once enabled, Fastify logs all incoming requests to the server and errors that occur while processing said requests. It also provides a convenient way to log custom messages through the log() method on the Fastify instance or the request object.

1. pino

Vitest is for frontend. Jest is not good for backend (I don’t like it for frontend either), take a look at this issue.

Have a look at https://github.com/pinojs/pino

NodeJS -> Pino, Winston, Bunyan, Npmlog, e.t.c.

Use a configurable logger like pino

Using pino as a logger, for every request on the _server_ , a unique ID generated client side in the headers, so a log may be something like: