Typically, the agent runs on the same machine as the MySQL server it is monitoring. Fortunately, this is not a requirement. If you want to monitor a MySQL server running on an operating system for which there is no agent available, you can install the agent on a machine other than the one hosting the MySQL server.
The process for installing an agent to monitor a MySQL server on a
remote machine is identical to the process described in
Section 15.6.3, “Monitor Agent Installation”. Follow the directions given
there, being careful to specify the correct IP address or host
name for the MySQL Enterprise Service Manager and likewise for the MySQL
server—since the agent is not running on the same machine as
the MySQL server, it cannot be the default,
localhost.
Don't forget that the agent must be given rights to log in to the
MySQL server from a host other than localhost
and that the port used by the MySQL server, typically
3306 must be open for remote access. For more
information about the database credentials required by agents see,
Section 15.6.3.1, “Creating a MySQL User Account for the Monitor Agent”.
The agent also needs to be able to log in to the MySQL Enterprise Service Manager,
typically using port 18080, so ensure that the
appropriate port is open.
Remote agents do not report the OS information for either the host or the agent.
For replication autodiscovery, do not use remote monitoring with replication slaves or masters. The agent must be installed on the same machine as the server you are monitoring in order for discovery to work properly. For more information, see Section 15.14, “The Replication Tab”.