What's the best practice for expressjs logging?


I am building an application based on expressjs and I’d like to log all events in it. I could find winston, which seems to be cool. Anyway, I am looking for a way how to connect it to my expressjs app.

What I also want is logging inside the application. My reqeusts are not so simple, so I’d like to log everything inside my app (not only requests).

My current situation:

server.js (I’d like to log http requests on this level)

var express = require('express');
var app = express();
var fs = require('fs');

// Post parser

// Load routes
require('fs').readdirSync(__dirname + '/routes').forEach(function(file) {
    require(__dirname + '/routes/' + file)(app);

// 404: Not found
app.use(function(req, res, next){
    res.json(404, {ERROR: 'Page not found.'});

// 500: Error reporing
app.use(function(err, req, res, next){
    res.json(500, {ERROR: 'Internal server error.'} );

// Startup new server


var something = require(__dirname + '/../controller/something.js');

module.exports = function(app) {
    app.get('/v1/something', function(req, res, next) { new something().getAll(req, res, next); });

controller/something.js (I’d like to use the same logger for debug logging)

 * Constructor
function Something() {

 * Get all the data
Something.prototype.getAll = function(req, res, next) {
    // I want to log some very important information here
    res.json({result: true, data: ['hello', 'hi', 'ciao', 'buf']});

module.exports = Something;

The other thing I am thinking about is logging all the events in functions that are called from controllers (e.g. models or other libraries).

So I think, the good way might to create some logger library, that will be called using:

var logger = require(__dirname + '/../libraries/logger.js');

containing logger definition. The other issue I don’t know how to solve is how to prefix data. You know, I have a lot of concurrent requests and I’d like to see which debug message was called by each request.


We use winston, it’s probably the most robust logging package out there.

We ended up setting it up exactly like you suggested. Creating a common library used for wrapping the logger object around our definitions and transports, and then handling any other type of objects we want to be handled differently.


Answered By – Ryan Gibbons

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published