MySQL Bugs: #41670: No easy way to track which advisors are running on which boxes

Bug #41670	No easy way to track which advisors are running on which boxes
Submitted:	22 Dec 2008 12:00	Modified:	9 Jan 2015 10:07
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Web	Severity:	S4 (Feature request)
Version:	2.0.0.7125	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I'll upload a screen dump of our own system. We have several instances running but not all of the rules are enabled on all instances. This makes it tricky to determine which servers are missing (and perhaps why).

How to repeat:
Click on Advisors page, and select a rule. If not all instances are shown as being enabled then it's hard to know which ones are "missing".

Suggested fix:
When managing servers (Settings-> Manage Servers) it is possible to click on "add to group" button. Something similar is needed here (add [instances] to group) as this would enable you to see a list of instances where the rule is not configured. Perhaps also a "remove [instances] from group" too?

Another option would be to enable the rules for a specific set of server groups (like All Servers, or another custom group). By simply adding new instances to merlin they should automatically be included if they are part of the specified group(s).

That would simplify administration as the rules could be configured on a per server/instance or per server/instance group basis.

The real issue is that for any largish setup you need to manage servers in groups and to be able to identify exceptions to those groups. The current page for managing the advisors is a little unwieldy.

Another thing which might be useful on this page is to show the count of each of the different statuses for each rule.

Also applicable because of this problem is when scheduling a rule for all servers you get an error about the schedule already existing. This is not an error, but a normal situation, so probably you need to change the reporting to:

Schedule already exists on XXXXXX instances.
And then add the information about the new instances to which the schedule has been added.