Bug #71535 MEM not collecting information on dedicated MEM db server despite running agent
Submitted: 30 Jan 2014 22:00 Modified: 31 Jan 2014 16:37
Reporter: Simon Mudd (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version:3.0.5 OS:Any
Assigned to: CPU Architecture:Any
Tags: windmill

[30 Jan 2014 22:00] Simon Mudd
Description:
I get this error in MEM:

We cannot report fully on this remote-monitored host, please install an Agent on the Host to enable Host data collection. (U0318)

The setup is as follows:
(a) a dedicated MEM / tomcat server using a dedicated MEM / MySQL database server to store data.
(b) the dedicated MEM / MySQL database runs a MEM agent and has correct credentials to access MEM and the "local" database.
(c) the MEM / tomcat server was originally configured to talk to the remote MEM db server.

Problem: I believe that MEM tries to prevent duplicate collection of data and so decides if it seems more than one agent is monitoring the same instance to collect the data from just one of them.

In my case it seems this is being done by the built-in agent on the MEM/tomcat server. The consequence of this is that I do not have access to the MEM db server's collected host information.

How to repeat:
See above

Suggested fix:
(1) treat the host and database specific information separately and if there is multiple collection of data from one host OR mysql server then choose one of the agents to provide that information, but at the same time ensure that all needed information is collected.

This is a little hard to explain without going into great detail but currently means I am unable to monitor the MySQL DB host metrics even though I have a locally running MEM agent "collecting data" or "able to collect data".
[31 Jan 2014 16:37] Mark Leith
Verifying
[26 Feb 2014 10:10] MySQL Verification Team
Hello Simon,

Thank you for the feature request!

Thanks,
Umesh
[13 Jan 2017 20:25] Henry Niño
Also in 3.3.2.