The "Target Host" stands for the host which is monitored by the corresponding agent, not the host which the agent is running on. We are attempting to create host monitoring agents of type FxM and notice that the "Target Host' in the Agent Status dashboard is not showing the hostname of the FxM appliance
Instead, the 'Target Host' in Agent Status dashboard shows the hostname of the machine to which the FxM agent package has been deployed, or where the FxM fglam has been deployed. However, what the 'Target Host' column ought to display is the hostname for the FxM appliance. Where is FMS getting the information to populate the "Target Host"?
There are some other Foglight cartridges that do monitor hosts that are different from the host upon which the agent is running.
The value of 'Target Host' is coming from the 'Monitored Host' property of the 'Agent' topology object.
So it looks like this "Target Host' property is working correctly, even for FxM. It's just that the field in the FxM agent topology object, the 'Monitored Host' field is not accurate, not correct. _That_ field is not showing the hostname of the FxM appliance being monitored but is instead showing the host of where the FxM agent is running (which is never the FxM appliancehost).
Looks like it may be something very similar (and similar fix) to what is going on with some other tracking tickets we have open for other Foglight cartridges such as MQ-385:"[MQAgent] Property "monitoredHost" is submitted a wrong host by MQ". And also APPB-406:"[ApacheAgent] Property "monitoredHost" is submitted a wrong host by Apache".
We need to make the 'Target Host' field for FxM agents show the hostname of the FxM machine from which it's MySQL data is being sent, not the value of the 'Monitored Host' property of the agent. That fix will, in turn, cause the "Target Host" to grab and populate the correct hosthame.