MySQL Enterprise Monitor can monitor any MySQL server running MySQL 5.1 or higher. The advisors provide specific support for different versions. For example, there are unique advisors and graphs for different MySQL versions, and some rules provide advice about MySQL upgrades.
In addition to monitoring the internal operation of the MySQL server, the MySQL Enterprise Monitor Agent and MySQL Enterprise Service Manager monitors the hosts themselves for problems like high CPU, memory, and disk usage, and can determine the topology of MySQL servers in a replication configuration, and monitor the replication status.
MySQL Enterprise Monitor uses a number of unique values known as
UUIDs to identify the different
components, including the MySQL instance being monitored. UUID
values related to the MySQL instance and the host on which it runs
are stored in a table
the instance. MySQL Enterprise Monitor creates this table if it does not exist
Each MySQL Server has a UUID, stored in the
mysql.inventory table, that uniquely
identifies the MySQL server to the rest of MySQL Enterprise Monitor. The
server UUID is used to collate information about a single
MySQL instance. When using MySQL Server 5.6 or newer, this
UUID is the same as the UUID used by replication and GTIDs.
Each host (the machine on which the agent is running) has a
UUID to uniquely identify the host to the rest of MySQL Enterprise Monitor.
This is used to collate the OS information (such as CPU, RAM
and disk data). The host ID also determines whether the MySQL
server is on the same host as it was before, to identify when
data has been moved between machines, or when a machine has
been upgraded. The host UUID is stored within the
hostid row within the
Each agent has a UUID to identify the agent to MySQL Enterprise Monitor. The
agent UUID is defined within the
parameter for an agent's configuration.
These UUIDs are used in combination to register and collate information, and to determine the location and source of an issue.
Because each host, agent, and MySQL server must be unique, be careful when restoring from a backup or cloning a virtual machine (VM) image so you do not have hosts with duplicated SSH keys or UUIDs.
You can monitor any MySQL server, because the agent communicates with the MySQL server using the same protocol as any other client. For best results when using MySQL Enterprise Monitor Agent with your MySQL Server, follow these guidelines:
Each instance must have a unique ID, as stored within the
Configure the MySQL server with a user that has the correct permissions and rights to be able to monitor the different parameters of the server. For instructions to create a suitable user, see Section 3.4.1, “Creating a MySQL User Account for the Monitor Agent”.