[
http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11327#action_11327
]
Ralph Goers commented on LBCLASSIC-116:
---------------------------------------
I have implemented support for TCP as well as UDP. I have tested this with both
rsyslog and syslog-ng and it is working in both. syslog-ng support for RFC5424,
5425 and 5426 is in version 3.0.x.
Here is a sample configuration for syslog-ng.
######
source s_ext { syslog(ip(0.0.0.0) port(514) transport("tcp")); };
template t_test { template("$ISODATE $HOST $PRIORITY $PROGRAM ${MSGID} $SDATA
$MSG\n"); };
destination d_test { file("/var/log/test" template(t_test)); };
log { source(s_ext); destination(d_test); };
> 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
