You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2007/07/06 00:21:24 UTC
DO NOT REPLY [Bug 42823] New: - Setting trigger on SMTPAppender unnecessarily complicated
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: log4j-dev@logging.apache.org
ReportedBy: carnold@apache.org
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/%3c405794.99416.qm@web7609.mail.in.yahoo.com%3e) 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
DO NOT REPLY [Bug 42823] - Setting trigger on SMTPAppender unnecessarily complicated
Posted by bu...@apache.org.
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
Bug 42823 depends on bug 32572, which changed state.
Bug 32572 Summary: Would like to use Filter's as TriggeringEventEvaluator's for SMTPAppender
http://issues.apache.org/bugzilla/show_bug.cgi?id=32572
What |Old Value |New Value
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
DO NOT REPLY [Bug 42823] - Setting trigger on SMTPAppender unnecessarily complicated
Posted by bu...@apache.org.
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
------- Additional Comments From jai_forums2005@yahoo.co.in 2007-07-07 20:02 -------
(In reply to comment #1)
> plus it would allow size based triggering
Would a size based triggering really be useful? I mean, would the size of the
message be considered important for triggering the mails?
--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
DO NOT REPLY [Bug 42823] - Setting trigger on SMTPAppender unnecessarily complicated
Posted by bu...@apache.org.
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
carnold@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From carnold@apache.org 2007-08-21 14:47 -------
*** This bug has been marked as a duplicate of 32572 ***
--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
DO NOT REPLY [Bug 42823] - Setting trigger on SMTPAppender unnecessarily complicated
Posted by bu...@apache.org.
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
------- Additional Comments From carnold@apache.org 2007-07-05 21:37 -------
Another possibility would be to support o.a.l.rolling.TriggeringPolicy. That would superset the capabilities
of a triggeringFilter since there is a FilterBasedTriggeringPolicy in o.a.l.rolling plus it would allow size
based triggering (however msg size is not currently calculated). However, that would require moving
o.a.l.rolling.TriggeringPolicy from extras to log4j proper and other unpleasantness.
Probably best just to add setTrigger(Level) and leave the fancy stuff for log4j 2.0.
--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org