To enable the Database Agent to collect data, you must add and configure a Database Collector for each database instance that you want to monitor. The Database Collector is the process that runs within the Database Agent to collect performance metrics about your database instances and database servers
Required Database Permissions
You must have the required permissions to monitor your databases. See Database Visibility Supported Environments.
To add, edit, and create collectors, users need a role with the proper permissions:
- Can Create Collectors
- Can Edit All Collectors
- Can Delete All Collectors
For more information, see Database Permissions.
Add a Database Collector
- Click the Configuration tab in the left panel menu.
- Click the Collectors option.
- In the Collectors window, click the Add ( + ) option.
- Complete each field of the Create New Collector dialog
If you want to add a sub-collector to be monitored, click Advanced >> +Add sub-collector to enter host and port details.
Sub-collectors are applicable only to relational database types.
- Click OK. Your database administrator can provide you with the necessary details.
After you have added a collector, you can configure the collector for your database. You can also link a database on the application flow maps to a database instance monitored by Database Visibility.
For information on the fields you must complete in order for the Database Agent to monitor the database server in addition to the database server, see Configure the Database Agent to Monitor Server Hardware.
Verify Collector Setup
Once the Collector is up and running, in just a short time you can start viewing the historical activity data.
The Collector configuration window now has a collector icon you can click to edit the details of the collector if required. The Collector will also appear in the list of Databases shown in the left navigation menu. It might take a few minutes before the Collector and its metrics are reported.
From the left navigation menu, click Databases to see a high-level view of the activity of all the configured Collectors.
Click the name of the database to see more details of the metrics AppDynamics Database Monitoring has captured.
For information on using and interpreting the Collector windows, see Monitor Databases and Database Servers.
Edit a Database Collector
From the Collectors window, you can edit any of the details of the collector except the type of database platform to monitor.
For more information on collector fields, see the collector configuration page for your database.
- Configure IBM DB2 Collectors
- Configure Microsoft SQL Server Collectors
- Configure Microsoft Azure Collectors
- Configure MongoDB Collectors
- Configure MySQL Collectors
- Configure Oracle Collectors
- Configure PostgreSQL Collectors
- Configure Sybase Collectors
- Configure Sybase IQ Collectors
Delete a Database Collector
From the Collectors window, you can delete a database Collector.
Export Database Collector Data
From the Collectors window, you can click on Actions> Export Datato generate a CSV file containing the following data for each collector:
- Collector name
- Host name
- Port number
- Database type
- Agent name
Troubleshooting Collector Problems
Collectors that have not been configured correctly, or that cannot connect to the database for any reason, will show an error on the Databases overview page and individual database dashboards. Hovering over the error icon displays the potential reason for the error.
If your Collector isn't reporting any metrics after a few minutes, and you know the database is up and running with activity, check the Events window. Agent Diagnostic Events can appear if the password is incorrect or communication errors have occurred. The message summaries on the Events window can help you diagnose and troubleshoot Collector problems.
Check the collector configuration to ensure all the values you entered are correct.
Ensure that your Database Agent has network connection to the databases you want to monitor along with the required permissions. See Database Monitoring Requirements and Supported Environments.