nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-29 00:19:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update usematurelogger.md

Browse Source
This commit is contained in:
Yoni Goldberg
2017-11-09 23:53:03 +02:00
committed by GitHub
parent f606c95da3
commit 4d850ab7f1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
sections/errorhandling/usematurelogger.md
View File

@ -2,7 +2,7 @@
### One Paragraph Explainer
We all loovve console.log but obviously a reputable and persisted Logger like [Winston][winston], [Bunyan][bunyan], [Pino][pino] or L4JS is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software
We all loovve console.log but obviously a reputable and persisted Logger like [Winston][winston], [Bunyan][bunyan] (highly popular) or [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software
(4) Expose and curate log statement for the operation team using operational intelligence tool like Splunk
[winston]: https://www.npmjs.com/package/winston