FYI: Alert limitation is implemented ++

[Jan-Henrik Haukeland]

As a result of the latest discussion on alert limitation we have
implemented this feature. The bottom line is that you will no longer
get many duplicate alerts for the same problem. See also the change
log for alert limitations just below. There is also a new icmp ping
test for remote hosts. So if you already now would like to test and
use these features, you are welcome to do so. Check out and build
monit from cvs.

See the section "Anonymous CVS Access" from this page on how to obtain
monit from cvs: http://savannah.nongnu.org/cvs/?group=monit

You can also follow the progress on our current work from this page if
you want to: http://www.tildeslash.com/monit/next.html


version 4.1

NEW FEATURES AND FUNCTIONS:
*  Web and console interface output refactored and simplified.
   Instead of printing out one line for each registered alert event-
   type, one condensed line is used.

*  Support for ICMP echo test added to remote host check

BUGFIXES:
*  Alert limitation implemented; Monit will only raise one alert when
   an error situation occurs and *not* repeatedly send error messages
   for the same problem.  When the error has gone, monit resets and
   will raise a new alert if the error should reoccur. Consider:
     if cpu > 50% then alert
   Monit will now only raise one alert if the cpu usage goes beyond
   50% and, as long as the process uses more than 50% cpu no more
   error alerts are sent. When usage drops below 50% monit will reset
   and again send a new alert if usage should raise above 50% again.
   Previous versions of monit did not have this feature and
   continuously sent alerts as long as the test validated to true.
   This change does not only applies to cpu test but also to memory
   tests, size and space tests and timestamp tests. The bottom line is
   that you will no longer get many duplicate alerts for the same
   problem.

*  Don't print html tags to the console on shutdown when monit runs in
   init mode (-I).

*  Monit now supports logging via multilog when running via
   daemontools. Thanks to Klaus Alexander Seistrup
   <bugs!magnetic-ink.dk> for reporting the problem.

*  Added the resource event type. This type was missing and would lead
   to a parse error if this alert statement was used, 'alert on {
   resource }'

*  Added a missing exec action for space and inode tests