A MySQL Enterprise Monitor Agent monitors a MySQL server and sends data to the Advisors. The data is interpreted and displayed MySQL Enterprise Monitor User Interface. The following section describes how to install the Agent on all platforms.
The Agent uses three users with different connection levels: Admin, General (optional), and Limited (optional). These can be created manually or by the installation or configuration process.
Typically, one Agent is installed per host, and the Agent monitors the host and all MySQL instances on it. An Agent may also monitor remote MySQL instances.
An Agent will automatically detect MySQL instances on a host, and the configuration step for adding the new MySQL instance may be performed in the MySQL Enterprise Monitor UI or from the command line.
Choosing a MySQL Instance to monitor during the installation is optional. If you choose to define a MySQL Instance while running the Installer, additional MySQL Instances on the host will still be detected and reported in the MySQL Enterprise Monitor User Interface. From there, you can add the appropriate configuration information.
In order to properly detect a local connection in IPv6, the
Agent requires that forward resolution exists on the system from
::1, which could mean editing
/etc/hosts configuration file.
This is because the "SHOW PROCESSLIST" statement always reports "localhost" even when bound to ::1 without an address resolution. If localhost resolution is not configured for IPv6, then the Agent will not detect a local IPv6 MySQL server connection, even when it occurs.
The Proxy and Aggregator have been separated from the Agent. When you run the Agent installer in MEM 3.0, it will only install an Agent, whereas in MEM 2.3 it could also install a Proxy and Aggregator.
If you depend on the Proxy or Aggregator, then you will need to continue using a 2.3 Agent, as these are not options with MySQL Enterprise Monitor 3.0.
Multiple connection levels (General, Limited, Admin) are now defined and utilized by the Agent. For more information, see Section 3.3.1, “Creating a MySQL User Account for the Monitor Agent”.
You may assign a monitored MySQL instance to a group via the Agent installer, which will show up in the MySQL Enterprise Service Manager.
The old Agent's configuration files
agent-instance.ini) no longer exist. Use
Passwords are now stored in an encrypted format, so you can no longer recover passwords by looking in the configuration files.
The Service Manager now bundles an Agent, which by default will begin monitoring the host it is installed upon, scan for all MySQL instances on the host, and also monitor the Service Manager repository database.
For a list of supported platforms that the Agent installation supports, see http://www.mysql.com/support/supportedplatforms/enterprise-monitor-agent.html.