1.4 Monitored MySQL Server

MySQL Enterprise Monitor can monitor any MySQL server running MySQL 4.1 or higher. The advisors and rules provide specific support for different versions. For example, there are unique rules 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 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 mysql.inventory within the instance. MySQL Enterprise Monitor creates this table if it does not exist already.

  • Each MySQL Server has a UUID, stored in the mysql.inventory table, that uniquely identifies the MySQL server to the rest of MEM. The server UUID is used to collate information about a single MySQL instance.

  • 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 mysql.inventory table.

  • Each agent has a UUID to identify the agent to MEM. The agent UUID is defined within the agent-uuid parameter within the agent configuration file.

These UUIDs are used in combination to register and collate information, and to determine the location and source of an issue.


Because each host must be unique, be careful when restoring from a backup 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:

Download this Manual
PDF (US Ltr) - 4.0Mb
PDF (A4) - 4.0Mb
EPUB - 3.2Mb
HTML Download (TGZ) - 3.1Mb
HTML Download (Zip) - 3.1Mb
User Comments
  Posted by Скибицкий Артур on July 31, 2015
Problem occurs when there is MEM-agent installed on master and if DBA deploys slave from full backup, in this case mysql.inventory table comes equal on master and slave. After addition slave server to MEM for monitoring you can see odd situation - MEM determines both master and slave servers as one single MySQL instance and fairy miracles begining...
Solution is to take UUID from "show variables" on slave and update `value` field in mysql.inventory where `name` = 'uuid' with taken from variables value. After this you can add your new slave to MEM instances list.
Sign Up Login You must be logged in to post a comment.