Bug #35541 Advanced Rules engine should detect flapping & "trends", be clock-aware
Submitted: 25 Mar 2008 1:37
Reporter: Mikiya Okuno Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S4 (Feature request)
Version:1.3 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[25 Mar 2008 1:37] Mikiya Okuno
During running backup, the server load becomes very high and some advisors such as "CPU Usage Excessive" reach their thresholds very easily, and the events will not fire again unless they're removed once. Events should not be triggered on such CPU high usage spikes.

Not only a black-out functionality but also accumulation is possible solution for this. For example, CPU usage should be marked high if it is really high during some certain period of time, instead of only one spike.

How to repeat:

Suggested fix:
It is good to determine averages for some certain period of times, instead of only one spike.
[8 Jun 2009 19:08] Gary Whizin
related to "auto-close events" feature, actively considering for our roadmap