AnalyticDB：View monitoring information of AnalyticDB for MySQL

Usage notes

You can view the monitoring information within two days in the last month.

Procedure

1. Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, click an edition tab. Find the cluster that you want to manage and click the cluster ID.

2. Go to the Monitoring and Alerts page.

   • For a Data Warehouse Edition cluster: In the left-side navigation pane, click Monitoring and Alerts.

   • For a Data Lakehouse Edition cluster: In the left-side navigation pane, choose Cluster Management > Monitoring and Alerts.

3. On the Monitoring tab, click the Standard Views tab or the Custom Views tab to view the corresponding monitoring information.

   • The Standard Views tab displays common metrics by default. To view all metrics, click More Metrics.

   • To view only specific metrics, click More Metrics on the Standard Views tab, select the metrics that you want to view and clear the metrics that you do not want to view, and then click Save As to add the selected metrics to the Custom Views tab.

   For more information about the metrics, see Metric overview.

FAQ

• Q: Why does the average CPU utilization increase after I change a cluster from reserved mode to elastic mode?

  A: After you change a C32 cluster from reserved mode to elastic mode, the specifications of a single node decrease to 8 cores. By default, BUILD jobs occupy 3 cores. In this case, the average CPU utilization increases. If the increased average CPU utilization does not affect your business, ignore this change. If your business is affected, upgrade your cluster or Submit a ticket. For information about BUILD jobs, see BUILD.

• Q: Why are the values of Regular Index and Primary Key Index metrics large?

  A: The preceding metrics may have large values due to the following reasons:

  • Indexes and primary key indexes are created for a large number of columns.

  • The length of a value in index columns is large, or the total length of all values in an index column is large. For example, the value of an index column is a long string.

  • The number of distinct values in index columns is large. This results in a low index compression ratio. For example, Index Column A has four distinct values: A1, A2, A3, and A4. Data is difficult to be compressed, which results in a low index compression ratio.

  • The length of a value in the primary key is large or multiple columns comprise a composite primary key.

• Q: A large response time is displayed on the Monitoring and Alerts page, but no corresponding time-consuming SQL statements are found on the Diagnostics and Optimization page. Why?

  A: A large amount of query result data requires an extended period of time to cache the result set. However, the total duration that is displayed on the Diagnostics and Optimization page consists of the queuing time, execution plan duration, and execution duration, excluding the cache duration of the result set. We recommend that you view the corresponding time-consuming SQL statements on the SQL Audit page.