[JIRA] Created: (LBCLASSIC-116) SyslogAppender should support RFC 5424
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-116: -------------------------------------- Hello Ralph, Would you supply a patch?
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- I'd be happy to but I can't say when. I'm buried with other work. My employer has been evaluating using rsyslog and if they do this will bubble up to be a requirement for me to have.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- Hopefully I did this git stuff right. I created a fork at git@github.com:rgoers/logback.git and put the syslog work under a branch named Syslog. The changes are a bit more than I anticipated since I needed to be able to pass more options to the syslog converter. In order to make use of the structured data defined as part of RFC 5424 I also added support for incorporating the SLF4J EventData. There is a bit more work to do as it isn't completely spec compliant. The RFC says that structured parameter names are limited to 32 characters and that certain characters in the value should be escaped. I haven't dealt with either of those yet. Also, no attempt is being made to enforce the rules regarding structured data ids. Also, I refactored the MDCConverter to extend a MapConverter which is shared with the StructuredDataConverter.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers edited comment on LBCLASSIC-116 at 8/28/09 9:11 AM: ---------------------------------------------------------------- Hopefully I did this git stuff right. I created a fork at git@github.com/rgoers/logback.git and put the syslog work under a branch named Syslog. The changes are a bit more than I anticipated since I needed to be able to pass more options to the syslog converter. In order to make use of the structured data defined as part of RFC 5424 I also added support for incorporating the SLF4J EventData. There is a bit more work to do as it isn't completely spec compliant. The RFC says that structured parameter names are limited to 32 characters and that certain characters in the value should be escaped. I haven't dealt with either of those yet. Also, no attempt is being made to enforce the rules regarding structured data ids. Also, I refactored the MDCConverter to extend a MapConverter which is shared with the StructuredDataConverter. was (Author: rgoers@apache.org): Hopefully I did this git stuff right. I created a fork at git@github.com:rgoers/logback.git and put the syslog work under a branch named Syslog. The changes are a bit more than I anticipated since I needed to be able to pass more options to the syslog converter. In order to make use of the structured data defined as part of RFC 5424 I also added support for incorporating the SLF4J EventData. There is a bit more work to do as it isn't completely spec compliant. The RFC says that structured parameter names are limited to 32 characters and that certain characters in the value should be escaped. I haven't dealt with either of those yet. Also, no attempt is being made to enforce the rules regarding structured data ids. Also, I refactored the MDCConverter to extend a MapConverter which is shared with the StructuredDataConverter.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers edited comment on LBCLASSIC-116 at 8/28/09 9:13 AM: ---------------------------------------------------------------- Hopefully I did this git stuff right. I created a fork at git://github.com/rgoers/logback.git and put the syslog work under a branch named Syslog. The changes are a bit more than I anticipated since I needed to be able to pass more options to the syslog converter. In order to make use of the structured data defined as part of RFC 5424 I also added support for incorporating the SLF4J EventData. There is a bit more work to do as it isn't completely spec compliant. The RFC says that structured parameter names are limited to 32 characters and that certain characters in the value should be escaped. I haven't dealt with either of those yet. Also, no attempt is being made to enforce the rules regarding structured data ids. Also, I refactored the MDCConverter to extend a MapConverter which is shared with the StructuredDataConverter. was (Author: rgoers@apache.org): Hopefully I did this git stuff right. I created a fork at git@github.com/rgoers/logback.git and put the syslog work under a branch named Syslog. The changes are a bit more than I anticipated since I needed to be able to pass more options to the syslog converter. In order to make use of the structured data defined as part of RFC 5424 I also added support for incorporating the SLF4J EventData. There is a bit more work to do as it isn't completely spec compliant. The RFC says that structured parameter names are limited to 32 characters and that certain characters in the value should be escaped. I haven't dealt with either of those yet. Also, no attempt is being made to enforce the rules regarding structured data ids. Also, I refactored the MDCConverter to extend a MapConverter which is shared with the StructuredDataConverter.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-116: -------------------------------------- Cool! Before I go off reading RFC 5424, do RFC 5424 compliant syslog daemons exist?
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-116 at 8/28/09 9:38 AM: --------------------------------------------------------------- Cool! Before I go off reading RFC 5424, do RFC 5424 compliant syslog daemons exist? (It looks like the new format just structures the contents of what was free format. So existing syslog daemons should work just fine.) was (Author: noreply.ceki@qos.ch): Cool! Before I go off reading RFC 5424, do RFC 5424 compliant syslog daemons exist?
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] 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.... 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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- I fixed the version and discovered I had misnamed one of the options. However, after pushing to github I ran mvn clean intall and I am now getting a test failure I haven't seen before: Results : Failed tests: dailySizeBasedRollover(ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest) Tests run: 256, Failures: 1, Errors: 0, Skipped: 1 java.lang.AssertionError: expected:<6> but was:<5> at org.junit.Assert.fail(Assert.java:74) at org.junit.Assert.failNotEquals(Assert.java:448) at org.junit.Assert.assertEquals(Assert.java:102) at org.junit.Assert.assertEquals(Assert.java:323) at org.junit.Assert.assertEquals(Assert.java:319) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.checkPatternCompliance(TimeBasedRollingWithArchiveRemovalTest.java:280) at ch.qos.logback.core.rolling.TimeBasedRollingWithArchiveRemovalTest.dailySizeBasedRollover(TimeBasedRollingWithArchiveRemovalTest.java:126)
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-116: -------------------------------------- Some of the tests are fragile. You've been unlucky. When tests erros occur, just file a bug report with the exception and as much info as you can (per usual). I'll look into it. Once you file the report, run the build again, the build error should go away.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- I synched my repository with yours and now the tests all run fine.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- Just wondering if you've had a chance to look at this and if you have any feedback.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-116: -------------------------------------- No I have not. Is it urgent?
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] 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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- I reworked the support for this. I added "Structured Data" to SLF4J. I was able to enhance LocationAwareLogger by creating a new interface so that it is completely backward compatible. So this change will require both git@github.com:rgoers/logback.git and git@github.com:rgoers/slf4j.git.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers edited comment on LBCLASSIC-116 at 9/7/09 9:16 AM: --------------------------------------------------------------- I reworked the support for this. I added "Structured Data" to SLF4J. I was able to enhance LocationAwareLogger by creating a new interface so that it is completely backward compatible. So this change will require both git://github.com/rgoers/logback.git and git://github.com/rgoers/slf4j.git. was (Author: rgoers@apache.org): I reworked the support for this. I added "Structured Data" to SLF4J. I was able to enhance LocationAwareLogger by creating a new interface so that it is completely backward compatible. So this change will require both git@github.com:rgoers/logback.git and git@github.com:rgoers/slf4j.git.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-116: --------------------------------------- I added some basic formatting using OptionHelper.substVars. I have tested this with rsyslog running on Ubuntu and it seems to behave correctly, as long as rsyslog is appropriately configured.
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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] 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
[ http://jira.qos.ch/browse/LBCLASSIC-116?page=com.atlassian.jira.plugin.syste... ] Daniel Serodio commented on LBCLASSIC-116: ------------------------------------------ It would be great to have this integrated into Logback, because logging on a remote syslog server over TCP is a requirement for a project I'm beginning to work on.
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
participants (3)
-
Ceki Gulcu (JIRA) -
Daniel Serodio (JIRA)
-
Ralph Goers (JIRA)