MySQL Bugs: #71954: MEM connection configuration information not very usable

Bug #71954	MEM connection configuration information not very usable
Submitted:	6 Mar 2014 8:28	Modified:	6 Mar 2014 12:45
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S4 (Feature request)
Version:	3.0.7	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Various things noted when managing MEM with a few dead dolphins (bad mysql connection configurations)

How to repeat:
run MEM with a few boxes, get your config wrong a bit and then look around and see if MEM notices.

Suggested fix:
A few suggestions to improve usability.

1. Please provide the agent version in Bad Connection Configuration to identify the agent version (it's done in other panels but not here
2. If Deleting or changing the configuration information this can't be done in a group like it can be done on other panels.

- I connect to 127.0.0.1 locally from where the agent is running with certain credentials and this could be used with common information on several servers, so selecting one or more bad connection configuration instances and modifying them at the same time sometimes makes sense
- if I want to delete the configurations then I can do this "en masse", I have to do one by one. It would be consistent to be able to select and do this on one or more instances at the same time.

3. If there are bad connection configurations you see a "dead dolphin". (top right) Clicking on this leads you to ManageServers.action#down, which has several "panels" which may be open or closed. I notice that the bad connections configuration panel may not be opened if you click from the dead dolphins to this page. I suggest that somehow you ensure that this panel is open, and perhaps for clarity the others are closed.

4.  If you delete a bad connection you get something like Delete MySQL Instance Connection: 127.0.0.1:3306, but no mention is made of the host/agent on which this is happening.

So I'd suggest making this clearer with a text like:

Delete MySQL Connection:
Monitored From Host: hostname_of_agent, agent version: 1.2.3.4,
MySQL info: host:port, $datadir

Finally when removing a bad configuration as identified in 4. previously it's not clear what happens to the agent. It may be monitoring more MySQL servers, or it may not be left monitoring anything but the host. Perhaps it's worth providing the user with information on what he might want to do, as if he's removing the last monitored MySQL instance on the server he might also want to remove the agent too (which MEM can't do but could advise on.)

There's also nowhere to see which agents may be monitoring 0 hosts, the result of perhaps deleting bad configuration information and that is not ideal.

Hello Simon,

Thank you for the feature request!

Thanks,
Umesh