So using these two features (phone home and process discovery adviser), you can easily incorporate MySQL Enterprise Monitor into your private cloud or DevOps environments. This means that you get to save time from having to manually configure everything.

After this, you will find that the Service Manager will automatically begin monitoring all those previously known unmonitored instances. Edit the global configuration for the adviser and choose default authentication information. You can find the advisers in the monitoring and support services group in your Service Manager. Those instances that are not monitored are automatically identified, which leads us to the process discovery adviser in the Service Manager. You can also check how many whole machines are being monitored, the number of MySQL instance that are being monitored and how many instances are not being monitored. If your specified production group did not previously exist, that group will be automatically created for you. When you check back on Service Manager, you will see that the instance is already being monitored. The good news is that if you are using Oracle VMServer, Open Stack or any other private cloud, you can just incorporate the agent in the base virtual machine easily. You can write a script that would specify the unattended installation mode, as well as all the options that are related to your instance, local host and port, and other options related to the Service Manager and the default group where the new instance is to be added in MySQL Enterprise Monitor. If you have a fresh install of the MySQL Service Manager, you will want to go to shell and run an unattended install of the agent. There are two functionalities that you should know: phone home and process discovery adviser. Setting up MySQL Enterprise Monitor version 3.0 with your private clouds is easy.

Mysql enterprise monitoring