We see a lot of 'single failures' where a check fails for some reason unrelated
to the check itself, only to return to "No problem" the very next check. This
I'd call 'noise' and it causes a lot of unnecessary activity in the status bar
making it grab attention and a waste of time checking what it reports.
The simplest solution is to require at least N failures before reporting the
issue, the current default being N=1. This count is readily available in the
status page being checked.
I'd personally change N to 2 and almost all the noise goes away. It will cause
a delay until a real issue is reported (N * update interval) but that is
trivial, especially compared to the time saved from checking on stuff that
hasn't really failed.
Original issue reported on code.google.com by per.goet...@gmail.com on 24 Aug 2011 at 8:43
Original issue reported on code.google.com by
per.goet...@gmail.com
on 24 Aug 2011 at 8:43