Help Center/ Application Performance Management/ User Guide（2.0）/ Performance Monitoring/ Monitoring Component Performance Metrics/ Viewing the Database Monitoring Item of a Component
Updated on 2026-02-25 GMT+08:00
View PDF
Share

Viewing the Database Monitoring Item of a Component

This type of monitoring item monitors database access. The databases that can be monitored include the C3P0, Cassandra, ClickHouse, DBCP, Druid, EsRestClient, GaussDB, Hikari, Jetcd, ObsClient, MySQL, PostgreSQL, Oracle, HBase, and MongoDB. APM collects statement execution details to help you locate performance problems in code.

Procedure

  1. Log in to the APM console.
  2. Click on the left and choose Management & Governance > Application Performance Management.
  3. In the navigation pane, choose Performance Monitoring > Components.
  4. In the filter bar on the left, select a region and an application.
  5. Click a component name in the Component column. The component details page is displayed.
  6. Click the Databases tab. By default, the MySQL database information of all instances is displayed.
  7. On the displayed Databases tab page, select a target instance and monitoring item to view the monitoring data in different metric sets.

    You can also perform the following operations if needed:

    • Set a time range to view data. Select a time range. Default: Last 20 minutes.

      Options: Last 3 minutes, Last 5 minutes, Last 10 minutes, Last 20 minutes, Last 1 hour, Last 3 hours, Last 6 hours, Last day, Today, Yesterday, Last week, Last month, and Custom.

    • Click in the upper right corner of the list. In the Table Settings dialog box, select or deselect columns to show or hide them.
    • Click in the upper right corner of the list to export information. A maximum of 100 records can be exported.
    • View the MySQL database monitoring information. For details, see Viewing MySQL Database Monitoring Data.

Setting the Maximum Number of Rows for Monitoring Metric Data Collection

When the number of metric data records exceeds the default or configured value, a threshold-crossing alarm will be displayed.

  1. Click Config in the alarm and change the value of Maximum number of rows for monitoring metric data collection.
  2. Click Confirm.

    • Only when the number of metric data records exceeds the default or configured value will a threshold-crossing alarm be displayed.
    • If the number of collected metric data records does not exceed the default or configured value, the value of Maximum number of rows for monitoring metric data collection cannot be configured.
    • For Maximum number of rows for monitoring metric data collection, the default value is 500. You can enter 10 to 2000.
    • If the number of collected metric data records exceeds the configured value, the collection of the corresponding metric will be stopped immediately.
    • Your settings take five minutes to become effective.

For more information about databases, see SQL.