Bug #71607 Improve MEM agent removal procedure
Submitted: 6 Feb 2014 11:41 Modified: 26 Feb 2014 10:01
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version:3.0.6 OS:Any
Assigned to: CPU Architecture:Any
Tags: Agent, cleanup, windmill

[6 Feb 2014 11:41] Simon Mudd
Removing a MEM agent on the dashboard does just that.
Yet, the mem agent is probably monitoring a host and one or more MySQL servers.
There is no mention made that it may be necessary to clean up to remove the "disconnected" MySQL instance info, and it is not clear to me what happens to the host information that the agent was collecting.

How to repeat:
Remove an agent and see that there is no "feedback" on things that need to be taken into account when this is done, and MEM does not do anything else either.

Suggested fix:
I can see various reasons for removing an agent:

(1) server removal, so the server, agent and MySQL instance(s) it was monitoring will no longer be monitored. it may be that the history is still wanted. (not my case in this specific instance).
(2) agent credentials mixed up or changed so the data for the appropriate host should not be removed, just any reference to that agent.  In fact the MySQL instance that was being monitored before  may still be up (and monitored by another instance?) so even the MySQL instance information may be needed. 

It would be good if the documentation explains what clean up tasks may be needed.
It would be good perhaps if removing the agent also (optionally) removed information on the host, and monitored MySQL instances.

MEM 2.3 had a simpler model and anything that was "red is dead" could just be deleted.

Not sure the best way to tackle this but right now MEM does not help much, or give guidance as to what other work I might need to do.
[26 Feb 2014 10:01] MySQL Verification Team
Hello Simon,

Thank you for the feature request!