Typically, the Agent runs on the same machine as the MySQL servers that it is monitoring, . Fortunately, this is not a requirement. If you want to monitor MySQL servers that run on remote hosts, 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 3.3, “Monitor Agent Installation”. Follow the directions given
there, being careful to either select "host-only" and add remote
MySQL instances later, or 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
Don't forget that the Agent must be given rights to log in to the
MySQL server from a host other than
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 3.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
18443, so ensure that the
appropriate port is open.
Remote monitoring has limitations. For example, it does not provide operating system level data, such as CPU, file, and network utilization information.
Note that having a single Agent monitor multiple MySQL instances potentially means having a single point of failure. This is especially true for remote monitoring, as it might lose a connection, which means a black period, whereas a local Agent will continue monitoring and provides information upon reconnection.
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 4.3, “Replication”.