[logback-dev] [JIRA] Commented: (LBCLASSIC-116) SyslogAppender should support RFC 5424

Ralph Goers (JIRA) noreply-jira at qos.ch
Tue Sep 1 16:29:36 CEST 2009

    [ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11290#action_11290 ] 

Ralph Goers commented on LBCLASSIC-116:

Urgent isn't the right word. I'm working on a POC that needs to use the IETF Syslog format for event logging (using the EventData from SLF4J). But as I worked on this I realized the concept of "Structured Data" might be something you want to incoporate throughout the framework. My change makes a start at that but you might want to handle it differently. In any case, supporting structured data in the syslog appender without providing a good mechanism for getting it to the appender would be a problem. 

> 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


More information about the logback-dev mailing list