How to Write Multiple Streams Similar to Bunyan about pino HOT 6 CLOSED

@dtothefp side note, you should really not use bind, it is super slow. Wrap the other call inside a function.

from pino.

I hacked around this by creating multiple Pino instances. Seems sloppy, wondering if there is a better way?

const serializers = pino.stdSerializers;
const name = APP_NAME;

if (LOG_ENV === 'development' || NODE_ENV === 'development') {
  const pretty = pino.pretty();

  pretty.pipe(process.stdout);

  logger = pino({
    name,
    level: 'info',
    serializers
  }, pretty);
} else {
  const noop = arg => arg;
  const streams = [
    {
      level: 'warn',
      path: path.join(LOG_DIRECTORY, `${APP_NAME}-warn.log`)
    },
    {
      level: 'error',
      path: path.join(LOG_DIRECTORY, `${APP_NAME}-error.log`)
    }
  ];

  logger = streams.reduce((acc, data) => {
    const {level, path: logPath} = data;
    const writeStream = fs.createWriteStream(logPath, {
      flags: 'a',
      encoding: 'utf8'
    });
    const inst = pino({
      name,
      level,
      serializers
    }, writeStream);

    acc[level] = inst[level].bind(inst);

    return acc;
  }, {});

  logger.info = noop;
}

from pino.

Hi @dtothefp

The "pino way" is to avoid any in-process overhead - only having one output stream is entirely deliberate - any other log processing should be done out-of-process

So what we'd need is

node app.js | pino-split-by-log-type 

This ties into https://github.com/mcollina/pino#how-to-use-transports-with-pino

Currently, we don't have pino-split-by-log-type, but if you're up for building it, here's some transports you can take inspiration from

• https://www.npmjs.com/package/pino-syslog
• https://www.npmjs.com/package/pino-elasticsearch
• https://www.npmjs.com/package/pino-socket

Let me know if you'd like to build it, and I'll support you (just open issues on your own repo and cc me (and Matteo) and we'll give feedback etc)

from pino.

@davidmarkclements thanks for the tips, if I get some time I will definitely try to work on this

from pino.

@mcollina good call, didn't know bind was slower

from pino.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from pino.