You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a SyslogTransportOptions configured for tcp protocol with a non-existing host but winston-syslog didn't complain about not being able to connect. I expected it to emit error event but it didn't. So when I tried
.on('error',...) on the logger it didn't seem to get fired.
l see there's a TODO marked in winston-syslog.js:
winston-syslog.js v2.4.0:
.on('error', function () {
//
// TODO: Pass this error back up
//
})
Is this expected to be fixed any soon?
The text was updated successfully, but these errors were encountered:
lvjkumar
changed the title
Errors during connection doesn't get propagated up
Error during connection doesn't get propagated up
Jan 15, 2020
I'm trying to use winston-syslog and I get no errors, but no logs either. Logging to other transports works fine. I can't find anything wrong with my configuration.
Now I wonder if this is why it's silently failing.
I have a SyslogTransportOptions configured for tcp protocol with a non-existing host but winston-syslog didn't complain about not being able to connect. I expected it to emit error event but it didn't. So when I tried
.on('error',...) on the logger it didn't seem to get fired.
l see there's a TODO marked in winston-syslog.js:
winston-syslog.js v2.4.0:
Is this expected to be fixed any soon?
The text was updated successfully, but these errors were encountered: