Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

writing in both files

See original GitHub issue

This is writing in both log file success and error.log if i called with log.fail I would expect it should write in error-date.log file. I don’t know what’s wrong here

const fs = require('fs');
var winston = require('winston');
const env = process.env.NODE_ENV;
const logDir = 'logs';

if (!fs.existsSync(logDir)) {
    fs.mkdirSync(logDir);
}

const now = new Date();
var logger = winston.createLogger({
    transports: [
        new (require('winston-daily-rotate-file'))({
            filename: `${logDir}/success-%DATE%.log`,
            timestamp: now,
            datePattern: 'DD-MM-yyyy',
            prepend: true,
            json: false,
            level: 'info',
        }),
        new (require('winston-daily-rotate-file'))({
            filename: `${logDir}/error-%DATE%.log`,
            timestamp: now,
            datePattern: 'DD-MM-yyyy',
            prepend: true,
            json: false,
            level: 'error',
        }),
    ],
    exitOnError: false,
});
const log = {
    fail: function (ee) {
        logger.error(`${now.toISOString()} - ${JSON.stringify(ee)}`);
    },
    success: function (ee) {
        logger.info(`${now.toISOString()} - ${JSON.stringify(ee)}`);
    },
};
module.exports = log;

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

mattberthercommented, Aug 2, 2020

This is not really how levels work in log mechanisms. What you could do, if this is a requirement, is to have your log module contain 2 loggers, each with a separate transport configured. For example:

const fs = require('fs');
var winston = require('winston');
const env = process.env.NODE_ENV;
const logDir = 'logs';

if (!fs.existsSync(logDir)) {
    fs.mkdirSync(logDir);
}

const now = new Date();
var errorLogger = winston.createLogger({
    transports: [
        new (require('winston-daily-rotate-file'))({
            filename: `${logDir}/error-%DATE%.log`,
            timestamp: now,
            datePattern: 'DD-MM-yyyy',
            prepend: true,
            json: false,
            level: 'error',
        }),
    ],
    exitOnError: false,
});

var successLogger = winston.createLogger({
    transports: [
        new (require('winston-daily-rotate-file'))({
            filename: `${logDir}/success-%DATE%.log`,
            timestamp: now,
            datePattern: 'DD-MM-yyyy',
            prepend: true,
            json: false,
            level: 'info',
        }),
    ],
    exitOnError: false,
});

const log = {
    fail: function (ee) {
        errorLogger.error(`${now.toISOString()} - ${JSON.stringify(ee)}`);
    },
    success: function (ee) {
        successLogger.info(`${now.toISOString()} - ${JSON.stringify(ee)}`);
    },
};
module.exports = log;

0reactions

indraraj26commented, Aug 2, 2020

Hi @mattberther , Is there any way not to write error i.e level: error log in info log, Basically i would like to create two separate log based on success and error.