The PolarDB console allows you to monitor a variety of performance metrics and view monitoring data at intervals of seconds. You can monitor the status of your clusters and quickly locate issues based on the monitoring data.

Monitor the performance of clusters and nodes

  1. Log on to the PolarDB console.
  2. In the upper-left corner of the console, select the region where the cluster resides.
  3. Find the cluster, and then click the cluster ID.
  4. In the left-side navigation pane, choose Diagnostics and Optimization > Monitoring.
  5. View the monitoring information about a Cluster or a Node based on your business requirements. For more information, see Metric description.
    • To monitor cluster performance, click the Cluster tab. Specify a time period and click OK.Cluster performance monitoring
    • To monitor node performance, click the Node tab and select a node from the drop-down list. Specify a time period and click OK. Node performance monitoring
Note On the Real-time Monitoring Dashboard page in the Database Autonomy Service (DAS) console, you can view the monitoring data about PolarDB for MySQL. This allows you to identify abnormal clusters for further analytics and optimization.

Metric description

Type Metric Description
Cluster Storage Displays the sizes of logs such as binary logs and redo logs, as well as the data storage, system storage, and temporary storage that are used.
QPS Displays the queries per second (QPS) of each node.
TPS Displays the transactions per second (TPS) of each node.
MPS Displays the manipulations per second (MPS) of each node.
CPU Displays the CPU usage of each node.
Memory Displays the memory usage of each node.
Node QPS Displays the QPS of the selected node.
TPS Displays the TPS of the selected node.
MPS Displays the MPS of the selected node.
CPU Displays the CPU usage of the selected node.
Memory Displays the memory usage of the selected node.
Connections Displays the total number of connections and the number of active connections on the selected node.
Operations Displays the number of operations per second performed on the selected node, including the DELETE, INSERT, UPDATE, and REPLACE operations.
Memory Buffer Pool Displays the dirty ratio, read hit ratio, and usage of the buffer pool on the selected node.
I/O Throughput Displays the total I/O throughput, read I/O throughput, and write I/O throughput of the selected node.
IOPS Displays the total input/output operations per second (IOPS), read IOPS, and write IOPS.
Network Displays the input and output traffic per second of the selected node.
Scanned Rows Displays the numbers of rows that are inserted, read, updated, and deleted per second on the selected node.
InnoDB Read and Written Data Displays the amount of data that is read from or written into the storage engine per second on the selected node.
InnoDB Buffer Pool Requests Displays the number of read and write operations that are performed on the buffer pool of the selected node per second.
InnoDB Log Writes Displays the number of log write requests per second and the number of data synchronizations to disks per second on the selected node.
Temporary Table Displays the number of temporary tables that are created per second on the selected node.

Change the data collection interval

  1. Log on to the PolarDB console.
  2. In the upper-left corner of the console, select the region where the cluster resides.
  3. Find the cluster, and then click the cluster ID.
  4. In the left-side navigation pane, choose Diagnostics and Optimization > Monitoring.
  5. Click Change Data Collection Interval.
    Change the data collection interval - 1
  6. In the Change Data Collection Interval dialog box, set Data Collection Interval to 5s or 60s (default) based on your business requirements.
    Change the data collection interval
    • When the Data Collection Interval parameter is set to 5s:
      • If the queried time range is less than or equal to 1 hour, the monitoring data is displayed at intervals of 5 seconds.
      • If the queried time range is less than or equal to 1 day, the monitoring data is displayed at intervals of 1 minute.
      • If the queried time range is less than or equal to 7 days, the monitoring data is displayed at intervals of 10 minutes.
      • If the query time range is less than or equal to 30 days, the monitoring data is displayed at intervals of 1 hour.
      • If the query time range is greater than 30 days, the monitoring data is displayed at intervals of 1 day.
    • When the Data Collection Interval parameter is set to 60s:
      • If the queried time range is less than or equal to 1 day, the monitoring data is displayed at intervals of 1 minute.
      • If the queried time range is less than or equal to 7 days, the monitoring data is displayed at intervals of 10 minutes.
      • If the query time range is less than or equal to 30 days, the monitoring data is displayed at intervals of 1 hour.
      • If the query time range is greater than 30 days, the monitoring data is displayed at intervals of 1 day.
  7. Click OK.

FAQ

  • How do I fix the issue that the CPU usage is too high?
    We recommend that you perform the following steps for troubleshooting:
    • Check whether a large number of slow requests exist. We recommend that you optimize slow queries first. For more information about how to view and optimize slow SQL statements, see Slow SQL queries.
    • Check whether the trend of the CPU curve is consistent with that of the QPS or TPS curve. If the curves are consistent, the issue is caused by high concurrency of transactions. In this case, we recommend that you upgrade your cluster. For more information about how to upgrade a cluster, see Change cluster configurations.
    • If no slow request exists, and trend of the CPU curve is different from that of the QPS or TPS curve, Submit a ticket for technical support.
  • How do I fix the issue when the number of connections is much greater than the number of active connections?

    You can set the wait_timeout and interactive_timeout parameters to smaller values to accelerate the release of idle connections. However, we recommend that you close connections in time when these connections are no longer used. This reduces the number of idle connections.

Related operations

API Description
DescribeDBClusterPerformance Queries the performance data of a PolarDB cluster.
DescribeDBNodePerformance Queries the performance data of a specified node in a PolarDB cluster.
DescribeDBClusterMonitor Queries the data collection interval of a specified PolarDB cluster.
ModifyDBClusterMonitor Changes the data collection interval of a specified PolarDB cluster.