Typically, the Agent runs on the same machine as the MySQL servers that it is monitoring. To monitor MySQL servers running 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
Chapter 5, 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
Ensure that the Agent has the appropriate 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 5.2, “Creating MySQL User Accounts 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 does not provide operating system level data, such as CPU, file, and network utilization information.
Monitoring multiple MySQL instances with a single agent 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 Chapter 16, Replication Dashboard.
This section describes how to monitor a MySQL instance in an cloud environment, such as the Amazon Relational Database Service (Amazon RDS).
It is recommended that you use MySQL 5.6 on RDS. It is also possible to use MySQL 5.5, but you must disable backup and replicas before attempting to monitor it using MySQL Enterprise Service Manager. After the agent has connected, you can enable backup and replicas again.
Remote monitoring is used when monitoring on a cloud. You can use any MySQL Enterprise Monitor Agent to monitor MySQL instances remotely, including the bundled Agent that is automatically installed and started with the MySQL Enterprise Service Manager.
When configuring a MySQL instance to monitor from the MySQL Instances Dashboard, do the following:
Do not configure MySQL Enterprise Monitor to auto-create the less privileged
Generalaccounts, and instead use the Admin account for all monitoring.
This is set in the Connection Settings tab when adding or editing a MySQL instance to be monitored. The Auto-Create Less Privileged Users setting defaults to
Yes, ensure it is set to
Also under Connection Settings is the Instance Address parameter. Set this to your endpoint, which is the entry point for your MySQL Server web service.
Change the inventory table schema for MySQL Enterprise Monitor Agent from "
mysql" to an existing, alternative schema.
This is set in the Advanced Settings tab when adding (or editing) a MySQL instance to be monitored. The Inventory Table Schema setting defaults to
mysql, which is typically not accessible to the Agent user in a cloud (or shared) environment. Change it to a schema you created.
Your MySQL instance is displayed on the MySQL Instances Dashboard.