Pino Ecosystem

This is a list of ecosystem modules that integrate with pino.

Modules listed under Core are maintained by the Pino team. Modules listed under Community are maintained by independent community members.

Please send a PR to add new modules!

Core

express-pino-logger: use Pino to log requests within express.
koa-pino-logger: use Pino to log requests within Koa.
pino-arborsculpture: change log levels at runtime.
pino-caller: add callsite to the log line.
pino-clf: reformat Pino logs into Common Log Format.
pino-debug: use Pino to interpret debug logs.
pino-elasticsearch: send Pino logs to an Elasticsearch instance.
pino-eventhub: send Pino logs to an Event Hub.
pino-filter: filter Pino logs in the same fashion as the debug module.
pino-gelf: reformat Pino logs into GELF format for Graylog.
pino-hapi: use Pino as the logger for Hapi.
pino-http: easily use Pino to log requests with the core http module.
pino-http-print: reformat Pino logs into traditional HTTPD style request logs.
pino-multi-stream: send logs to multiple destination streams (slow!).
pino-mongodb: store Pino logs in a MongoDB database.
pino-noir: redact sensitive information in logs.
pino-pretty: basic prettifier to make log lines human readable.
pino-socket: send logs to TCP or UDP destinations.
pino-std-serializers: the core object serializers used within Pino.
pino-syslog: reformat Pino logs to standard syslog format.
pino-tee: pipe Pino logs into files based upon log levels.
pino-toke: reformat Pino logs according to a given format string.
restify-pino-logger: use Pino to log requests within restify.
rill-pino-logger: use Pino as the logger for the Rill framework.

pino-colada: cute ndjson formatter for pino.
pino-fluentd: send Pino logs to Elasticsearch, MongoDB and many others via Fluentd.
pino-pretty-min: a minimal prettifier inspired by the logrus logger.
pino-rotating-file: a hapi-pino log transport for splitting logs into separate, automatically rotating files.
cls-proxify: integration of pino and CLS. Useful for creating dynamically configured child loggers (e.g. with added trace ID) for each request.