Bug #82619 master server status showing "Node Unmonitored" in MEM 3.2 replication topology
Submitted: 18 Aug 2016 2:06 Modified: 18 Aug 2016 7:49
Reporter: Dachao Gao Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:3.2.4 OS:Any
Assigned to: CPU Architecture:Any

[18 Aug 2016 2:06] Dachao Gao 
Description:
After add replication node (MySQL 5.5,master->slave replication) .
replication master node status showing "Node Unmonitored" in MEM 3.2 replication topology. However ,on the other side ,master node status looks normal under "event" category ,"reports and graph" category also works fine for the same node.

How to repeat:
It looks like this issue only happen on 5.5 replication group,and only happens in remote monitoring.
1 Install the latest MEM 3.2.4,use bundles agent.
2 use bundles agent to Monitor remote 5.5 replication group.
3 Check the replication group status in MEM 3.2 replication topology.
  replication master node status showing "Node Unmonitored",but slave status are    normal ,even we have multiple slave ,slave status are showing correctly.

Note:If you can't reproduce this issue ,please confirm you are monitoring 5.5 from remote. Monitoring 5.5 from local or monitoring 5.6 from remote will not reproduce this issue.
[18 Aug 2016 7:49] MySQL Verification Team 
Thank you Dachao.

Thanks,
Umesh