[
http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11284#action_11284
]
Ralph Goers commented on LBCLASSIC-116:
---------------------------------------
Rats! I just discovered I left the version out. I'll have to fix that.
The biggest issue with compatibility is that the timestamp changed (and there
is a version between the <PRI> and timestamp.
rsyslog has added support, although it might still have some bugs. See
http://www.rsyslog.com/module-Static_Docs-view-f-features.html.phtml
syslog-ng supposedly supports it. See
http://corporate.blogs.balabit.com/2009/01/reliability-and-compliance-syslog-ng-pe.html.
I believe RedHat distributes the free version of syslog-ng.
I'm going to be working with RSA's enVision appliance which supposedly will
handle these messages.
> SyslogAppender should support RFC 5424
> --------------------------------------
>
> Key: LBCLASSIC-116
> URL: http://jira.qos.ch/browse/LBCLASSIC-116
> Project: logback-classic
> Issue Type: Improvement
> Components: appender
> Affects Versions: 0.9.16
> Environment: All
> Reporter: Ralph Goers
> Assignee: Logback dev list
>
> The SyslogAppender supports RFC 3164. RFC 5424 has been released with
> obsoletes RFC 3164. See http://www.ietf.org/rfc/rfc5424.txt. At the very
> least the format of the timestamp has been changed. Either the SyslogAppender
> should be enhanced to comply with RFC 5424 or a new SyslogAppender should be
> created which does.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
