DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42823>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42823 Summary: Setting trigger on SMTPAppender unnecessarily complicated Product: Log4j Version: 1.2 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Appender AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] BugsThisDependsOn: 32572 SMTP appender is currently hardcoded to send emails when an ERROR level request is processed. This can be customized by providing an implementation of TriggeringEventEvaluator and specifying evaluatorClass in the configuration file, but that requires you to provide a user-written class. This issue was discussed on log4j-user on 2007-07-04 (http://mail-archives.apache.org/mod_mbox/ logging-log4j-user/200707.mbox/[EMAIL PROTECTED]) and previously in 17-Jan-2002. Also bug 32572 proposing allowing Filter's to serve as TriggeringEventEvaluators. Possible resolutions: 1. Add a triggeringLevel attribute, if set this would replace the current TriggeringEventEvaluator. 2. Add a triggeringFilter nested element that would allow a user specified filter to act as a TEE (per suggestion in 32572) and replace current TEE. Triggering on an arbitrary level would require use of o.a.l.varia.LevelRangeFilter. 3. Both of the above. Triggering on current threshold is not acceptible since it would change deployed behavior and someone might be depending on the current behavior. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
