Troubleshoot 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 panel. Agent Diagnostic Events can appear if the password is incorrect or communication errors have occurred. The message summaries on the Events panel can help you diagnose and troubleshoot Collector problems.

Note: If a collector stops reporting after FIPS mode is enabled, the collector might contain a password or other sensitive attribute encrypted with a legacy algorithm. Edit the collector, re-enter the applicable sensitive values, and save the configuration. Then verify that the collector resumes reporting. See FIPS migration of Database Collector secrets.

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.