Ironically, SyslogProtocol.js does not support plain RFC 3164's
timestamps, which are in
who-knows-what time zone and lack a year part. If you can, don't use them. If
you're really keen on them, please let me know and I'll see about implementing.
Tour
Supports RFC 3164 with high-precision timestamps (RFC
3339, ISO 8601).
For example, Rsyslog's RSYSLOG_ForwardFormat uses those.
Process identifier (taken from brackets after process name). If the message lacks one, pid won't be set at all. If it looks like a number, it'll be cast to Number.
Facilities
Facility names returned by SyslogProtocol.js match <syslog.h> and
syslog(3).
Code
Facility
0
kern
1
user
2
mail
3
daemon
4
auth
5
syslog
6
lpr
7
news
8
uucp
9
cron
10
authpriv
11
ftp
12
Severities
Severity names returned by SyslogProtocol.js match <syslog.h> and
syslog(3).
Blame them for the inconsistent naming.
Code
Severity
0
emerg
1
alert
2
crit
3
err
4
warning
5
notice
6
info
7
debug
License
SyslogProtocol.js is released under a Lesser GNU Affero General Public License, which
in summary means:
You can use this program for no cost.
You can use this program for both personal and commercial reasons.
You do not have to share your own program's code which uses this program.
You have to share modifications (e.g. bug-fixes) you've made to this
program.
For more convoluted language, see the LICENSE file.