Depending upon your use of MySQL Enterprise Monitor, you might perform some or all of these tasks after installation:
Email settings: Test email notification by deliberately triggering an alert.
Auto Startup: On Unix systems, the MySQL Enterprise Service Manager does not automatically restart when the system is rebooted. To enable automatic startup, create a system initialization script appropriate to your operating system.
Log files: Check the log files for any irregularities. For the locations of the various log files see Section C.1.3, “Log Files for the MySQL Enterprise Service Manager”.
Agent Log file rotation: Implement log file rotation for the monitor agent.
Back up the repository: For details, see Section B.5, “Backing up MySQL Enterprise Service Manager”.
Configuration backup: Back up the
mysql-monitor-agent.inifile and the associated
instancesdirectory and contents.
For more information about the
mysql-monitor-agent.inifile see Section C.2, “MySQL Enterprise Monitor Agent Reference”.
Configuration file: Store the
configuration_report.txtin a safe place. There is no mechanism for retrieving the password stored in this file.
Repository credentials: The repository user name and password are stored in unencrypted form in the
config.propertiesfile. Take care to protect this file.
Disk management: Remove installation files, and monitor the space used by the repository. Ensure that you have adequate disk space by regularly purging data. For more information, see Data Purge Behavior.
Firewall changes: Consider limiting or expanding access to the MySQL Enterprise Service Manager.
Open ports: As with firewall changes, consider limiting or expanding access to the MySQL Enterprise Service Manager. The dashboard uses nonstandard ports, none of which are usually open by default.
Server upgrades: See Section 184.108.40.206, “Upgrading the Monitored MySQL Server” for instructions on upgrading a server.
Repository access: Add any other needed users.