Node.js: Logging
summary
Explains concrete logging choices: use debug module for libraries (enable with DEBUG=module), adopt levels (error/warn/info/debug) and avoid console.log because it blocks stdio and can slow or lose output (removing consoles once showed ~10–20% speed gain). Recommends app loggers—log4js for flexibility or pino for raw speed (claims up to 5× faster)—send logs to aggregators (ELK, Graylog, CloudWatch) but watch cloud ingestion costs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:24Fundamentals of logging
- 8:21Understanding log levels
- 15:43Console vs proper libraries
- 20:17Logging in Node.js modules
- 26:06Application logging tools
- 33:23Log aggregation and conclusion
related talks
31mConsole.loggers Anonymous: A Debugging Roadmap from Local to Production
21mFoundations of Debugging Node.js
17mLogging, Metrics, and Tracing with Node.js
29mAre logs a software engineer's best friend? Yes - follow these best practices
01h 04mNode.js performance analytics and best practices
37mThe Cost of Logging
02h 24mHow to Node.js - Part 2
26mWhat every developer should know about logging