15.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 Agent and MySQL Enterprise Service Manager can determine the replication topology of your MySQL servers and monitor the replication status.

MySQL Enterprise Monitor uses a number of unique values to identify the different components, including the MySQL instance being monitored:

  • 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 hostid 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.

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 Agent with your MySQL Server, follow these guidelines:

Copyright © 2010-2017 Platon Technologies, s.r.o.           Home | Man pages | tLDP | Documents | Utilities | About
Design by styleshout