The Agent uses three users with different connection levels: Admin, General (optional), and Limited (optional). These can be created manually or by the installation and 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.

Agents automatically detect MySQL instances on a host. Adding the new MySQL instance may be performed in 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 are detected and reported in MySQL Enterprise Monitor User Interface. From there, you can add the appropriate configuration information.

To detect a local connection in IPv6, the Agent requires forward resolution configured on the system from localhost to ::1, which could mean editing the /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, the Agent cannot detect a local IPv6 MySQL server connection.

You can assign a monitored MySQL instance to a group via the Agent installer, which is displayed in MySQL Enterprise Service Manager.

The old Agent's configuration files (mysql-monitor-agent.ini and agent-instance.ini) no longer exist. Use custom.xml instead.

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 monitors the host on which it is installed, scans for all MySQL instances on the host, and also monitors 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.html.