Hello log4j-dev, Using Log4J in a production environment involving syslog and alerting, we would like to have some minor parametrability added to the Syslog appender (it may impact other Log4J parts): 1) Customize the syslog level corresponding to FATAL Today the syslog level corresponding to FATAL is EMERG (hardcoded). As FATAL has no equivalent in syslog, it can be desirable feature to have it customized with the log4j.properties file. In fact it is desirable for us, for we already use the ALERT syslog level to raise alerts and reserve EMERG for other specific needs. ==> Proposal: add a FatalSyslogMapping property for syslog appenders, e.g: log4j.appender.A1=org.apache.log4j.net.SyslogAppender log4j.appender.A1.SyslogHost=localhost log4j.appender.A1.Facility=LOCAL7 log4j.appender.A1.FatalSyslogMapping=ALERT 2) Customize the text corresponding to a given level Today a given Log4J level corresponds to a (hardcoded) string when you print this level in a file or a syslog log. We would like to use slightly different strings for the log4j levels, for example: Level.DEBUG => "debug" Level.INFO => "info" Level.WARN => "warning" Level.ERROR => "error" Level.FATAL => "alert" We would like to customize this with the log4j.properties too, it needs some more investigation for a concrete proposal. We already use other APIs that produce this format though, so it is an important need for us to have a unified log format through syslog. To address these needs we are going to write our own appender. We may provide you patches to merge these features to mainstream. Would you be interested in these patches? Or are you working on such features for Log4j1.3alpha? Best regards
Submit a patch off of SVN trunk.