imsky / winston-rsyslog2 Goto Github PK

No logs were being written to rsyslog even though everything looked correct. I was able to test that the tcp port was open using nc. I traced through the code and realized the default levelMapping was {} which could be a problem. The docs say the default value should have been "winston.config.syslog.levelMapping" but the code said otherwise. I tried finding this object and it did not exist but I did find winston.config.syslog.levels. As soon as I added levelMappings: winston.config.syslog.levels to the options, the logs were forwarded as expected.

The default should be updated to use this value and the docs should be updated.

I'm using "winston": "2.4.0" and "winston-rsyslog2": "0.0.5"

Hello,

I'm the author of the winston-log-and-exit, and have some users of this package have complained that this package doesn't work with winston-log-and-exit. As you may know, cleanly exiting a process and retaining the last few log entries is a perennial problem for winston users, which is confounded by poor documentation on how Winston identifies streaming loggers, and what API streaming loggers should implement.

In short, to work with winston-log-and-exit a custom Streaming Transport needs a ._stream attribute, has an .end() method, and which issues a "finish" event when all the messages that were logged before the .end() method was called.

Cheers,

-Jason

I am starting seeing this warning after the upgrade to winston 3.0:

rsyslog is a legacy winston transport. Consider upgrading: - Upgrade docs: https://github.com/winstonjs/winston/blob/master/UPGRADE-3.0.md

Can you consider upgrading this library?
Thanks!

Hi there

Firstly thanks for making this project.

I am able to get everything working fine (logging to facility 16, i.e. local0). This creates a log file such as /var/log/local0.log

Is there a way we can use a facility so the log goes to /var/log/[custom name or name of my app] ?

Thanks

Hi, logging been working a treat then some odd "undefined" behaviour today.

var winston = require('winston');
require('winston-rsyslog2');
console.dir(winston.transports.Rsyslog);

// > undefined

package.json dependencies

"dependencies": {
    "winston": "^1.0.2",
    "winston-rsyslog2": "0.0.5"
  }

any ideas why the Rsyslog transport would be undefined?

The function was removed by this commit:

d613987

Now "npm test" fails because of the missing function.

I'm looking at repairing it now.

While syslogd are rsyslogd are different syslog servers, they speak a common protocol. Thus it seems that winston-syslog could speak to rsyslog servers, while winston-rsyslog2 could speak to a syslog server.

We should consider if the projects could be merged. For example winston-syslog code to check the connection, and if the connection fails, retry the connection several times while queuing the logs until the connection comes back up. We lack that feature. We have the feature to map winston log levels to syslog log levels, but that hasn't landed yet in `winston-syslog'.