[logback-user] Approaches to implement RFC5424 structured data support
rgoers at apache.org
Mon Jun 18 18:53:34 CEST 2012
As you noted this subject has come up before. It was one of the things that ultimately motivated me to go off and create Log4j 2. I abandoned the fork at Github when it became clear that there wasn't going to be a good resolution to the issue.
I'm not sure what value the second link has. I've gotten RFC 5424 to work with several systems including Splunk, rsyslog and syslog-ng. FWIW, my use case is Apache Log4j 2 Flume Appender -> Apache Flume -> Apache Cassandra. What is interesting here is that while RFC 5424 isn't strictly necessary for Flume integration, structured data is, at least for what we are using it for.
On Jun 18, 2012, at 4:28 AM, Thilo-Alexander Ginkel wrote:
> Hi there,
> I was wondering whether anyone has so far been successful in
> implementing RFC5424  structured data syslog support using logback
> (despite it probably being DOA  - the alternatives are IMHO
> currently in a too early stage). In the archives I see one attempt at
> a pretty invasive approach that altered the logback implementation
> itself (unfortunately, the fork over at Github seems to be no longer
> maintained) as well as a proposal  to use a custom encoder along
> with a special "RFC5424Aware" interface.
> Would the latter still be the preferred way to go? Reading through the
> code, I guess a custom Layout (that knows how to deal with
> RFC5424Aware instances) should also do the trick...
> I guess one would also need to replace SyslogStartConverter due to the
> changed message header...
> Any input is appreciated!
>  http://tools.ietf.org/html/rfc5424
>  http://www.gossamer-threads.com/lists/rsyslog/users/6361
>  http://mailman.qos.ch/pipermail/slf4j-dev/2010-March/002878.html
> Logback-user mailing list
> Logback-user at qos.ch
More information about the Logback-user