A simple node module that makes console.log/error/warn/debug statements log through winston (simply include at the beginning of your app)

logging.js

'use strict';

var util = require('util'),
    winston = require('winston'),
    logger = new winston.Logger(),
    production = (process.env.NODE_ENV || '').toLowerCase() === 'production';

module.exports = {
    middleware: function(req, res, next){
        console.info(req.method, req.url, res.statusCode);
        next();
    },
    production: production
};

// Override the built-in console methods with winston hooks
switch((process.env.NODE_ENV || '').toLowerCase()){
    case 'production':
        production = true;
        logger.add(winston.transports.File, {
            filename: __dirname + '/application.log',
            handleExceptions: true,
            exitOnError: false,
            level: 'warn'
        });
        break;
    case 'test':
        // Don't set up the logger overrides
        return;
    default:
        logger.add(winston.transports.Console, {
            colorize: true,
            timestamp: true,
            level: 'info'
        });
        break;
}

function formatArgs(args){
    return [util.format.apply(util.format, Array.prototype.slice.call(args))];
}

console.log = function(){
    logger.info.apply(logger, formatArgs(arguments));
};
console.info = function(){
    logger.info.apply(logger, formatArgs(arguments));
};
console.warn = function(){
    logger.warn.apply(logger, formatArgs(arguments));
};
console.error = function(){
    logger.error.apply(logger, formatArgs(arguments));
};
console.debug = function(){
    logger.debug.apply(logger, formatArgs(arguments));
};

thx!

thx!

helpful

helpful

line 44 - >
logger.info.apply(logger, formatArgs(arguments));
should be (?) ->
logger.log.apply(logger, formatArgs(arguments));

line 44 - >
logger.info.apply(logger, formatArgs(arguments));
should be (?) ->
logger.log.apply(logger, formatArgs(arguments));

awesome, thanks!

awesome, thanks!

The code is right. I've tried your suggestion and it doesn't work.

The code is right. I've tried your suggestion and it doesn't work.

This is a very useful idea because it allows you to program as you normally would in debug mode yet override logging in production so that it isn't synchronous. Simple and good.

This is a very useful idea because it allows you to program as you normally would in debug mode yet override logging in production so that it isn't synchronous. Simple and good.

Simple ES6 syntax :)

    console.log = (...args) => logger.info.call(logger, ...args);
    console.info = (...args) => logger.info.call(logger, ...args);
    console.warn = (...args) => logger.warn.call(logger, ...args);
    console.error = (...args) => logger.error.call(logger, ...args);
    console.debug = (...args) => logger.debug.call(logger, ...args);

Simple ES6 syntax :)

    console.log = (...args) => logger.info.call(logger, ...args);
    console.info = (...args) => logger.info.call(logger, ...args);
    console.warn = (...args) => logger.warn.call(logger, ...args);
    console.error = (...args) => logger.error.call(logger, ...args);
    console.debug = (...args) => logger.debug.call(logger, ...args);

This is helpful! Thanks!

This is helpful! Thanks!

Thanks @fega!

Thanks @fega!

@fega surely it could be more simple, the .call seems redundant.

  console.log = (...args) => logger.info(...args);
  // etc

@fega surely it could be more simple, the .call seems redundant.

  console.log = (...args) => logger.info(...args);
  // etc

@spmason thanks for the great simple reference here!

@fega much easier to read, but important to note that it's not semantically equivalent to normal syntax; binds this to current scope which could or might cause people unfamiliar to get confused or have debugging problems somewhere (if they want to override with any other logic as well). Not to say it's bad, just pointing out in case somebody is bashing their head on the keyboard somewhere one day :)

@spmason thanks for the great simple reference here!

@fega much easier to read, but important to note that it's not semantically equivalent to normal syntax; binds this to current scope which could or might cause people unfamiliar to get confused or have debugging problems somewhere (if they want to override with any other logic as well). Not to say it's bad, just pointing out in case somebody is bashing their head on the keyboard somewhere one day :)

Thanks for the info everyone.

@spmason and @fega -- I've quoted your answers in this stackoverflow answer, and marked it as a community wiki since I did not write the answers myself. Cheers.

Thanks for the info everyone.

@spmason and @fega -- I've quoted your answers in this stackoverflow answer, and marked it as a community wiki since I did not write the answers myself. Cheers.

tnks

tnks