The MySQL Process Discovery Advisor enables you to find and, optionally, establish a connection with unmonitored MySQL instances.
If you disable this advisor, notifications for unmonitored instances, and the associated events, are not displayed in the user interface.
Table 19.1. MySQL Process Discovery Controls
|Attempt Connection||Whether or not to attempt a connection. If this is set to No, the
advisor continues to raise events related to unmonitored
If set to Yes, a connection is attempted using the credentials supplied.
|Alert Level||Level of alert generated if an unmonitored instance is discovered.|
The root user of the instance or a user that has the SUPER privilege, and the CREATE and INSERT privileges on the schema in which the inventory table is created. The inventory table stores unique identifiers for the instance, and is created in the mysql schema by default.
The SUPER privilege is required to temporarily switch off replication when creating and populating the inventory table.
If you choose to Auto-Create Less Privileged Users, this user is used to create those with the required privileges to monitor this instance. In this case, it should also have the PROCESS, REPLICATION CLIENT, SELECT and SHOW DATABASES privileges globally WITH GRANT OPTION.
|Admin Password||The password for the Admin User.|
|Auto-Create Less Privileged Users||When monitoring an instance, multiple levels of user can be employed to
ensure that a Process connection is not held open
If you do not have appropriate users already, they are automatically created if this option is selected. Otherwise, you will need to check if any of the users specified below already exist. Holding on to a connection that has a SUPER privilege could potentially lock out administrators when the server reaches max_connections, so using these lower privileged users is recommended.
|General User||This user handles general monitoring tasks that do not require SUPER level privileges. Lower privileged users will be used in favor of a SUPER user, unless higher privileges are required. In which case we temporarily log in as the SUPER privileged user, and then fall back to the general user. If you are manually managing this user, it should have at least the PROCESS, REPLICATION CLIENT, SELECT and SHOW DATABASES privileges globally.|
|General Password||The password for the user with general privileges.|
|Limited User||This user is used for statements that are limited to a single connection, and can be run with global SELECT privileges. Examples of these kinds of statements include retrieving database metadata from INFORMATION_SCHEMA tables, or any custom SQL that is used to monitor application specific statistics. If you are manually managing this user, it should have at least the SELECT and SHOW DATABASES privileges globally.|
|Limited Password||The password for the user with limited privileges.|
|MySQL Instance Identity Source||Choose the mechanism used to generate a unique identity for the MySQL
instance if one does not already exist.