Bug #42932 Heat chart rules cannot be disabled/unscheduled anymore
Submitted: 17 Feb 2009 14:47 Modified: 22 May 2009 13:39
Reporter: Oli Sennhauser Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:2.0.4 OS:Any
Assigned to: Sloan Childers CPU Architecture:Any
Tags: chart, dashboard, disable, heat, rule, schedule

[17 Feb 2009 14:47] Oli Sennhauser 
Description:
Heat chart rules cannot be disabled or unscheduled any more.
This was possible in the release 2.0.0 and customer complains about it.

How to repeat:
Advisors > Unschedule -> Error message

or

Advisors > Disable -> Error message

Suggested fix:
Enable it again.

See also bug #41312.
[18 Feb 2009 22:26] Sloan Childers 
We are currently investigating making the heat chart dynamic so that a customer can pick and choose which rules are displayed.
[19 Feb 2009 8:59] MySQL Verification Team 
This is also a problem as default alert values may not be applicable (or create false positives) across a number of monitored servers. Not allowing disabling of predifined advisors/rules restricts tuning of these values for different servers characteristics.
[19 Feb 2009 15:24] MySQL Verification Team 
In a production context, with many MySQL servers running sensitive applications, these servers are normally well tuned (since a long time), DBAs don't need to monitor more than a dozen of indicators (advisors rules) for a server pool. Disabling some rules (not all) could make more readable the server monitoring.
[30 Apr 2009 19:55] Sloan Childers 
patch pushed to 2.1 to allow for all heat chart rules to be disabled/unscheduled except for the two agent rules which cause many parts of the product to look broken if disabled/unscheduled

be careful what you wish for...
[4 May 2009 23:35] Keith Russell 
Patch installed in versions => 2.1.0.1036.
[5 May 2009 16:28] Marcos Palacios 
Verified fixed in build 2.1.0.1036.

Note: As indicated above, the following Heat Chart rules are not allowed to be disabled/unscheduled:
 "MySQL Agent Not Communicating With Database Server"
 "MySQL Agent Not Reachable"
 "MySQL Server Not Reachable"
and will give the following errors:
 U0166 Heat chart rule "MySQL Agent Not Communicating With Database Server" scheduled against "<server-name>" may not be disabled".
 U0166 Heat chart rule "MySQL Agent Not Reachable" scheduled against "<server-name>" may not be disabled".
 U0166 Heat chart rule "MySQL Server Not Reachable" scheduled against "<server-name>" may not be disabled".
 U0166 Heat chart rule "MySQL Agent Not Communicating With Database Server" scheduled against "<server-name>" may not be unscheduled".
 U0166 Heat chart rule "MySQL Agent Not Reachable" scheduled against "<server-name>" may not be unscheduled".
 U0166 Heat chart rule "MySQL Server Not Reachable" scheduled against "<server-name>" may not be unscheduled".
[22 May 2009 13:39] Tony Bedford 
An entry has been added to the 2.1.0 changelog:

Heat Chart rules could not be disabled or unscheduled.
[3 Aug 2009 22:29] Roel Van de Paar 
As per the note above, for clarity, note there are 3 (not 2) rules that cannot be unscheduled *at all*: "MySQL Agent Not Communicating With Database Server", "MySQL Agent Not Reachable", "MySQL Server Not Reachable"
[12 Aug 2009 6:12] Roel Van de Paar 
Also note bug #46667