You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/04/02 06:42:58 UTC
[jira] Updated: (CONTINUUM-1390) ability to add a message throttle
for identical messages
[ http://jira.codehaus.org/browse/CONTINUUM-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1390:
------------------------------------
Fix Version/s: 1.2
> ability to add a message throttle for identical messages
> --------------------------------------------------------
>
> Key: CONTINUUM-1390
> URL: http://jira.codehaus.org/browse/CONTINUUM-1390
> Project: Continuum
> Issue Type: Improvement
> Components: Integration - Shell, Notification Subsystem
> Affects Versions: 1.1-beta-2
> Reporter: Brett Porter
> Fix For: 1.2
>
>
> add a throttle on messages, particularly for errors - don't send a message that is identical to one sent in the last X hours.
> Trying to avoid the mass-spamming when a service goes down (but ensure some notification does go out). As soon as the error state is reset to good, another message can be sent, but if it is already in error it shouldn't (currently, it does it every time, and alwaysSend is not granular enough).
> On the flipside - I sometimes don't see errors ever get notified (or only once, and then they are stuck in error). We should re-send if something remains in error after a certain duration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira