From 9eb500af2d1f0f16fd4b118b4f9cb5c9883570da Mon Sep 17 00:00:00 2001 From: puru-khedre <101047627+puru-khedre@users.noreply.github.com> Date: Fri, 7 Oct 2022 17:26:10 +0530 Subject: [PATCH] Add content of Logging node (#2213) * Update readme.md * Update content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md * Update content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md Co-authored-by: Kamran Ahmed --- .../107-nodejs/content/112-nodejs-logging/readme.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md b/content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md index 36ac77143..460d3117e 100644 --- a/content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md +++ b/content/roadmaps/107-nodejs/content/112-nodejs-logging/readme.md @@ -1 +1,7 @@ -# Nodejs logging \ No newline at end of file +# Node.js Logging + +**Logging** is an essential part of understanding the complete application life cycle of the `Node.js` application. We can much more easily and quickly fix errors by looking at logs throughout the development process, from creating to debugging to designing new features. **Error**, **warn**, **info**, and **debug** are the four basic logging levels in `Node.js`. Logging involves persistently collecting information about an application's runtime behaviour. + +Free Content +Node.js Logging +Logging best practices