July 2017
Intermediate to advanced
656 pages
16h 1m
English
It's advisable to keep as much log processing work outside of the main web server Node process as possible. To this end the Pino logging philosophy promotes piping log output to a separate process (which we call a logging transport).
This separate process may move the logs into a database, or message bus, or may apply data transforms or both.
For instance, if we wanted to marshal logs into an Elasticsearch database (which would allow us to analyze log messages with Kibana, which is an excellent data visualization and analysis tool for Elasticsearch) in a production setting, we could use the pino-elasticsearch transport and pipe our server log output to it like so:
$ node index | pino-elasticsearch
See the ...