UNPKG

3.99 kBMarkdownView Raw
1# Pino Ecosystem
2
3This is a list of ecosystem modules that integrate with `pino`.
4
5Modules listed under [Core](#core) are maintained by the Pino team. Modules
6listed under [Community](#community) are maintained by independent community
7members.
8
9Please send a PR to add new modules!
10
11<a id="core"></a>
12## Core
13
14+ [`express-pino-logger`](https://github.com/pinojs/express-pino-logger): use
15Pino to log requests within [express](https://expressjs.com/).
16+ [`koa-pino-logger`](https://github.com/pinojs/koa-pino-logger): use Pino to
17log requests within [Koa](http://koajs.com/).
18+ [`pino-arborsculpture`](https://github.com/pinojs/pino-arborsculpture): change
19log levels at runtime.
20+ [`pino-caller`](https://github.com/pinojs/pino-caller): add callsite to the log line.
21+ [`pino-clf`](https://github.com/pinojs/pino-clf): reformat Pino logs into
22Common Log Format.
23+ [`pino-debug`](https://github.com/pinojs/pino-debug): use Pino to interpret
24[`debug`](https://npm.im/debug) logs.
25+ [`pino-elasticsearch`](https://github.com/pinojs/pino-elasticsearch): send
26Pino logs to an Elasticsearch instance.
27+ [`pino-eventhub`](https://github.com/pinojs/pino-eventhub): send Pino logs
28to an [Event Hub](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-what-is-event-hubs).
29+ [`pino-filter`](https://github.com/pinojs/pino-filter): filter Pino logs in
30the same fashion as the [`debug`](https://npm.im/debug) module.
31+ [`pino-gelf`](https://github.com/pinojs/pino-gelf): reformat Pino logs into
32GELF format for Graylog.
33+ [`pino-hapi`](https://github.com/pinojs/hapi-pino): use Pino as the logger
34for [Hapi](https://hapijs.com/).
35+ [`pino-http`](https://github.com/pinojs/pino-http): easily use Pino to log
36requests with the core `http` module.
37+ [`pino-http-print`](https://github.com/pinojs/pino-http-print): reformat Pino
38logs into traditional [HTTPD](https://httpd.apache.org/) style request logs.
39+ [`pino-multi-stream`](https://github.com/pinojs/pino-multi-stream): send
40logs to multiple destination streams (slow!).
41+ [`pino-mongodb`](https://github.com/pinojs/pino-mongodb): store Pino logs
42in a MongoDB database.
43+ [`pino-noir`](https://github.com/pinojs/pino-noir): redact sensitive information
44in logs.
45+ [`pino-pretty`](https://github.com/pinojs/pino-pretty): basic prettifier to
46make log lines human readable.
47+ [`pino-socket`](https://github.com/pinojs/pino-socket): send logs to TCP or UDP
48destinations.
49+ [`pino-std-serializers`](https://github.com/pinojs/pino-std-serializers): the
50core object serializers used within Pino.
51+ [`pino-syslog`](https://github.com/pinojs/pino-syslog): reformat Pino logs
52to standard syslog format.
53+ [`pino-tee`](https://github.com/pinojs/pino-tee): pipe Pino logs into files
54based upon log levels.
55+ [`pino-toke`](https://github.com/pinojs/pino-toke): reformat Pino logs
56according to a given format string.
57+ [`restify-pino-logger`](https://github.com/pinojs/restify-pino-logger): use
58Pino to log requests within [restify](http://restify.com/).
59+ [`rill-pino-logger`](https://github.com/pinojs/rill-pino-logger): use Pino as
60the logger for the [Rill framework](https://rill.site/).
61
62<a id="community"></a>
63## Community
64
65+ [`pino-colada`](https://github.com/lrlna/pino-colada): cute ndjson formatter for pino.
66+ [`pino-fluentd`](https://github.com/davidedantonio/pino-fluentd): send Pino logs to Elasticsearch,
67MongoDB and many [others](https://www.fluentd.org/dataoutputs) via Fluentd.
68+ [`pino-pretty-min`](https://github.com/unjello/pino-pretty-min): a minimal
69prettifier inspired by the [logrus](https://github.com/sirupsen/logrus) logger.
70+ [`pino-rotating-file`](https://github.com/homeaway/pino-rotating-file): a hapi-pino log transport for splitting logs into separate, automatically rotating files.
71+ [`cls-proxify`](https://github.com/keenondrums/cls-proxify): integration of pino and [CLS](https://github.com/jeff-lewis/cls-hooked). Useful for creating dynamically configured child loggers (e.g. with added trace ID) for each request.
72