storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Derek Dagit <>
Subject Seeking opinions on moving storm from logback to log4j 2.x
Date Fri, 13 Feb 2015 22:30:10 GMT
In the past, the storm project used log4j version 1.x as its loggingframework.
Around the time of 0.9.0, before moving to Apache, the project moved to using
logback for two reasons:

1) logback supported rolling log files, which was critical for managing disk
space usage.
2) logback supported dynamically updating its logging configuration files.

Recently, we have met a new requirement that we send logs to a syslog daemon
for further processing. The syslog daemon has a particular format described in
RFC5424, and using it basically means that things like stack traces have
newlines properly contained within a single logging event, instead of written
raw into the log making extra parsing necessary.

log4j version 2.x (or log4j2) has the following:

1) rolling log files with size, duration, and date-based triggers that can be
composed together
2) dynamic log updates that do not cause log messages to be dropped while the
new config is loaded
3) a Syslog appender that is compliant with RFC5424.

This would change the slf4j binding from logback to log4j, but it would not
change the slf4j API. Topology code that uses the slf4j logging library would
not need to change and would continue working as normal.

I would like to hear users' opinions on whether it might be good to switch
from logback to log4j2 based on the above, or else hear about alternative
solutions to the RFC5424 requirement that works well. 


View raw message