fix for winston.config.syslog.levels which are not in the right priority order for winston

[yonjah]

winston default logging priority order is ascending goes from lowest 0 (silly) to highest 5 (error)
but syslog priority order is descending from lowest 7 (debug) to highest 0 (emerg)

this means that when setting a log level for winston when using syslog
you will actually log below that level instead of above it
so setting logger.level='info' (which is the default)
will actually log debug and info but will not log notice warning and so on.

I'm not sure if this is the right place for this fix
but I opend an issue for winston a few days ago and didn't get any attention
since the bad config mostly affects winston-syslog users I thought it can be fixed within
winston-syslog a better fix might be to have the levels conf under Syslog namespace and not requiring winston config at all but that will require changing the docs

[indexzero]

Fixed in [email protected] (see: winstonjs/winston#732). Could you let me know if you plan on upgrading? That will help us inform if this backwards compatibility layer would be necessary.

[yonjah]

@indexzero thanks.
I'll probably try to upgrade in a week or two

[santigimeno]

I've tested winston-syslog with latest [email protected] and the levels seem fine now

[indexzero]

Thanks for the confirmation @santigimeno. Closing this.