To monitor MySQL with Database Visibility, you must run MySQL >= 2.2.
|Create New Collector
|The database type that you want to monitor.
|The Database Agent that manages the collector.
|The name you want to identify the collector by.
|Hostname or IP Address
|The hostname or IP address of the machine that your database is running on.
|The TCP/IP address of the port on which your database communicates with the Database Agent
|Custom JDBC Connection String
|The JDBC connection string generated by the database agent, for example,
jdbc:mysql://. You can also specify a custom connection string, which is useful for setting custom authentication options.
|Username and Password
|The name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for MySQL.
|The password of the user who is connecting to and monitoring the database through the Database Agent.
|Click to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to
cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file.
Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add the additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.
|Click to add a new JDBC connection property or edit an existing property for relational databases.
|The databases that you want to exclude, separated by commas.
|Monitor Operating System
|See Configure the Database Agent to Monitor Server Hardware.
User Permissions for MySQL
The MySQL user the Database Agent uses to monitor the MySQL database must have "SELECT", "PROCESS", and "SHOW DATABASES" privileges on all databases.
The user must also have the "REPLICATION CLIENT" privilege to collect these metrics:
If you do not have a suitable existing user, you can use the command below to create a new user.
GRANT SELECT,PROCESS,SHOW DATABASES on *.* to 'DBMon_Agent_User'@'host' identified by 'password';
GRANT REPLICATION CLIENT ON *.* to 'DBMon_Agent_User'@'host';
DBMon_Agent_User with the username under which you run the Database Visibility Agent. Substitute
host with the hostname or IP address of the machine running the AppDynamics Database Agent, and substitute
password with a secure password.
max_allowed_packet parameter to 1073741824 on the server.