Bug #39954 Dashboard does not show OS data if agent went from remote to local monitoring
Submitted: 9 Oct 2008 15:40 Modified: 22 Jul 2009 8:49
Reporter: Diego Medina Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S2 (Serious)
Version:2.0.0.7071 OS:Any
Assigned to: Darren Oldag CPU Architecture:Any

[9 Oct 2008 15:40] Diego Medina
Description:
If the agent is doing remote monitoring and then you stop it. And installed the agent locally to the mysqld server. The UI will not start showing OS data, it will act as if you are still doing remote monitoring.

How to repeat:
1- Install the agent on box A
2- Install mysqld on box B
3- Install the service manager on box C (or A or B)
4- Start the agent, service manager and mysqld
5- Notice that the UI does not show any OS related data
6- Stop the agent
7- Install the agent on Box B (same as mysqld)
8- Start the agent
9- Go to the UI and notice that there is no OS data still.
[9 Oct 2008 19:35] Darren Oldag
this is the same case as any mysqld switching physical hosts, too.

i did find a workaround, because as it turns out the lower level inventory relationship is updated, but the higher up business objects are not.

workaround:

have local agent check in (to update inventory)
restart MEM service manager
schedule OS rules manually.
[6 Jul 2009 15:00] Enterprise Tools JIRA Robot
Darren Oldag writes: 
should be resolved by same fix for

https://repoman.mysql.com/jira/browse/EM-287
[6 Jul 2009 22:35] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch applied in versions => 2.1.0.1074.
[13 Jul 2009 16:37] Enterprise Tools JIRA Robot
Diego Medina writes: 
Verified fixed on 2.1.0.1074
[13 Jul 2009 18:03] Enterprise Tools JIRA Robot
Diego Medina writes: 
I first verified that the Metadata was being updated when going from remote to local monitoring. But if you look at the graphs (CPU, etc) those graphs do not update their information.

To be clear, the steps I did were:

1- You monitor a mysqld from an agent on a separate server (remote monitoring)
2- You them install an agent on the same box as the mysqld server, and I used the same agent-uuid that was generated for the remote agent. (In case it makes any difference)
[13 Jul 2009 21:11] Enterprise Tools JIRA Robot
Darren Oldag writes: 
the previous fix for transport and host variable binding changes did not
take into account the case where no previous binding existing, and needed
to be added.

now, this case should be handled -- and fixes the remote to local OS
monitoring rule and graph bindings.
[16 Jul 2009 19:20] Enterprise Tools JIRA Robot
Andy Bang writes: 
In build 2.1.0.1078
[21 Jul 2009 20:16] Enterprise Tools JIRA Robot
Diego Medina writes: 
Verified fixed on 2.1.0.1078

Now OS related graphs also show information.
[22 Jul 2009 8:49] Tony Bedford
An entry was added to the 2.1.0 changelog:

The Enterprise Dashboard did not display OS data if the Agent was changed from remote to local monitoring.