MySQL Bugs: #41607: Deleting a mysql instance from the UI should also delete os data

Bug #41607	Deleting a mysql instance from the UI should also delete os data
Submitted:	18 Dec 2008 22:43	Modified:	9 Jan 2015 14:35
Reporter:	Diego Medina	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:	2.0.2.7125	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Deleting a mysql server instance from the Dashboard leaves behind OS data.
If you then start monitoring a new mysqld server on the same host, old OS data will remain visible on the graph.

note, this is when you only had one mysqld on that box, or you are deleting the last mysqld from the host.

How to repeat:
1- Install and start the agent and service manager
2- Once the mysqld instance you are monitoring shows up on the UI, stop the agent (you may want to leave it running for a few minutes so that looking at the graph you can easily tell the os data is still there.
3- Delete the mysqld instance
4- Change the settings on your agent's ini files so that you start monitoring a new mysqld instance
5- Go to the UI and you will see old Os data on the graphs.

Suggested fix:
Delete os data if this is the last (only) mysqld on this host.

The same about agent instance: there is no option to delete agent from repository: even if agent was uninstalled and its uuid will be never reused.
I think it is related to this bug and doesn't worth separate report.