In addition to monitoring the database server, the Database Agent can also monitor the hardware that hosts the database server. To configure the Database Agent to monitor the database server hardware, complete the Hardware Monitoring section of the Collector configuration dialog.

Click Databases > Configuration > Collectors and then choose an existing collector to monitor the hardware for that database server and click Edit, or click Add to set up a new collector to monitor a different database server and the hardware hosting that server.

Complete the Hardware Monitoring Section

The following describes the fields in the Collector Configuration dialog that you must complete if you want to monitor the database server host hardware, in addition to the database server.

For Oracle database, the CPU and the Memory metrics are monitored even when hardware monitoring is disabled.

If you enable hardware monitoring for MySQL and PostgreSQL RDS databases, then to fetch vCPU, use mapping of model vs vCPU from Amazon RDS Instance Types. The fetched vCPU is used for IBL licensing model.

Monitor Operating System: Select if you want CPU consumption metrics collected from the monitored host. 

Operating System: Specify the operating system of the monitored host: Windows, Linux, Solaris, AIX, or RDS.

Use Local WMI: Check this box if you want to monitor the machine the Database agent is running on, i.e. localhost. When selected, the authorization fields are not used because no authorization is required.

Domain: For Windows only, specify the name of the domain in which the hardware resides.

SSH Port: For Linux, AIX, and Solaris only, specify the Secure Shell (SSH) port number the Controller should use for encrypted communications with the monitored host. The default port number of 22 will be used if you do not specify a different port number here.  

Use certificate: For Linux, AIX, and Solaris only, AppDynamics also supports certificate-based authentication through Privacy Enhanced Mail (PEM). To implement certificate-based authentication, enable the Use certificate option and copy the PEM file to the <db_agent_home>\keys directory. Note, if the $HOME/.ssh directory exists, the agent will use the certificate found there. This option appears only if the agent is running on a machine running Linux, AIX or Solaris.

Username: Specify the name of the user the Database Agent uses to log on to the monitored host. To collect OS metrics from a Windows host, the configured user (or Collector Service user if using Windows Authentication) must be able to establish a WMI connection to the target host and collect Windows Performance Counters.

Password: Specify the password of the user the Database Agent uses to log on to the monitored host. The number of echo characters shown in the password text field should not be interpreted to imply the number of characters stored for the (encrypted) user password.

  • Windows hardware monitoring is not supported by Database Agent installed on a Linux system. However, Database Visibility can support hardware metrics for SQL server through SQL query collection.
  • Database Visibility does not collect hardware metrics for the following database servers because these database servers require SSH connection to collect hardware metrics:
    • Apache Cassandra
    • Datastax Enterprise (DSE) Cassandra
    • Couchbase
    • IBM DB2
    • MongoDB 
    • MySQL
    • Sybase 
    You must enable Monitor Operating System to collect the hardware metrics for these database servers.
  • For Oracle and MSSQL database, hardware metrics can be collected through either SQL query collection or SSH connection. However, Database Visibility does not support collecting hardware metrics using SQL query for the preceding list of database servers.

Resolve Metric Reporter Type Mismatch Problem

Switch from the Java Hardware Monitor to the Hardware Monitor if you see messages similar to the following in the logs:

[Worker-7] 12 Sep 2014 07:27:49,449 WARN MonitorOutputHandler - Metric Reporter type mismatch for metric [Hardware Resources|Network|Incoming packets/sec] Aggregator of OBSERVATION already exists for metric Metric Identifier[Hardware Resources|Network|Incoming packets/sec] ID[0]