This section describes the best practices to employ when changing your MySQL Enterprise Monitor installation.
When upgrading a monitored MySQL server, first stop the agent, as explained in:
Stop the MySQL server, then perform the upgrade.
To stop and restart the MySQL daemon under Unix, Linux, and Mac OS X, see, Section 15.6.2.5, “Starting/Stopping the MySQL Enterprise Monitor Service on Unix and Mac OS X”.
For instructions on stopping and restarting the MySQL service under Windows, see Section 15.6.2.6, “Starting/Stopping the MySQL Enterprise Monitor Service on Windows”.
Once the service/daemon is stopped, upgrade your MySQL server, using the instructions from the reference manual the new server version. When the upgrade is complete, restart the MySQL server.
The agent's log file shows that the server was down during the upgrade process.
You need not reinstall the MySQL Enterprise Agent in order to change the MySQL server that it monitors. It is possible to adapt an existing agent so that it monitors a different server.
To do this you must stop the monitor agent and then remove the server that it is monitoring. To stop the agent see:
For instructions on removing a server see, Section 15.8.3.3, “Removing a Server From the Dashboard”.
Once the agent is stopped and the server is removed from the
Dashboard, you can change the
mysql-monitor-agent.ini, or the
agent-instance.ini file within the agent
instances instances directory. To find this
directory, examine the content of the
mysql-monitor-agent.ini and check the value
of the mysqld-instance-dir parameter.
To make changes to the monitored MySQL server, edit the
agent-instance.ini file. Change the
user, password,
hostname, and port values
if required. For more information, see
MySQL Server (agent-instance.ini) Configuration.
To change other settings, such as enabling proxy support
(required for Query Analyzer), the management host, or the port
number used by the agent, modify the
mysql-monitor-agent.ini file. For more
information, see
MySQL Enterprise Agent Configurable Options.
To restart the agent, see:
When adapting an existing agent to monitor a remote server, make sure that the agent has the credentials for remote access and that the port on the remote MySQL server instance is open. For more information, see Section 15.6.3.7, “Configuring an Agent to Monitor a Remote MySQL Server”.
If you have trouble starting the agent, check Section 15.6.3.10, “Troubleshooting the Agent”.
Log in to the Dashboard and you should find your new server in
the All Servers group.
When bringing down a monitored MySQL server, stop the agent first, to avoid generating a misleading “Server is unreachable” event.
For instance, if you stop the server to do a backup, follow these steps:
Stop the agent.
Stop the service/daemon.
Perform the backup.
Restart the service/daemon.
Restart the agent.
To stop or start the agent, see:
To stop the MySQL service/daemon, see the MySQL reference manual for your server version, on the web site http://dev.mysql.com/doc.
As an alternative to stopping the agent, you can change the logic associated with a rule. For instance, you could alter the threshold of the rule “Server is unreachable”:
%server.reachable% == THRESHOLD
to:
%server.reachable% == THRESHOLD && CURTIME() NOT BETWEEN '22:00:00' AND '23:00:00'
This sets a blackout period for this rule between 10 and 11 pm, during which time you could perform a backup.
For more information about editing rules, see Section 15.10.3, “Editing Built-in Rules”. To blackout all events associated with a specific server or group of servers, see Advisor Blackout Periods.