The PolarDB console allows you to monitor various performance metrics and view monitoring data at intervals of seconds. You can monitor the status of your cluster and identify faults based on the monitoring data.
Procedure
Log on to the PolarDB console.
In the upper-left corner, select the region where the cluster to which you want to connect is deployed.
Find the cluster and click its ID.
In the left-side navigation pane, click .
You can view the monitoring information of the Cluster, Compute Node, Advanced Monitoring, or Performance Events metric. For more information, see Metrics.
To view the performance of the cluster, click the Cluster tab. Then, specify a monitoring period in the date and time picker and click OK.
To view the performance of a compute node, click the Compute Node tab and select a node from the drop-down list. Then, specify a monitoring period in the date and time picker and click OK.
To view the information of advanced monitoring metrics for a node, click the Advanced Monitoring tab and select a node from the drop-down list. Then, specify a monitoring period in the date and time picker and click OK.
To view the information about the performance events of a node, click the Performance Events tab and select a node from the drop-down list. Then, specify a monitoring period in the date and time picker and click OK.
Metrics
Category | Metric | Description |
Cluster | Storage Capacity | Displays the storage usage of all data files, logs, and write-ahead logs (WALs), and the temporary storage usage. |
CPU Usage | Displays the CPU usage of each node. | |
Memory Usage | Displays the memory usage of each node. | |
Compute node | TPS | Displays information about the transactions that are performed per second on the selected node. The information includes the number of committed, deadlocked, and rolled back transactions per second. |
CPU Usage | Displays the CPU usage of the selected node. | |
Memory Usage | Displays the memory usage of the selected node. | |
Connections | Displays the total number of current connections, the number of active connections, and the number of idle connections on the selected node. | |
Scanned Rows | Displays the number of rows that are inserted, read, updated, deleted, and returned per second on the selected node. | |
Maximum Transaction ID | Displays the difference between the ID of the first transaction and the ID of the most recent transaction in the database. | |
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 IOPS, read IOPS, and write IOPS of the selected node. | |
Cache | Displays the number of cache reads per second and the number of disk reads per second on the selected node. | |
Cache Hit Ratio | Displays the cache hit ratio of the selected node. | |
Temporary Files | Displays the number and the total size of temporary files on the selected node. | |
Advanced monitoring | PolarDB CPU Utilization/Memory Usage | Displays the CPU usage and memory usage of the selected node. |
TPS/QPS | Displays the TPS and QPS of the selected node. | |
Sessions | Displays the number of total sessions and the number of active sessions on the selected node. | |
Temporary Files | Displays the number of temporary files generated per second on the selected node. | |
Number of Transactions | Displays the number of active transactions, the number of idle long transactions, the number of idle transactions, the number of XA transactions, the number of pending transactions, and the number of long transactions on the selected node. | |
Cache | Displays the block hit ratio, the number of block reads, and the number of block hits per second on the selected node. | |
Scanned Rows | Displays the numbers of rows that are inserted, read, updated, and deleted per second on the selected node. | |
PolarDB Storage Space Used | Display the storage usage of WALs, user data, local logs, cluster space, and temporary space on the selected node. | |
PolarDB IOPS | Displays the number of reads and writes per second for the selected node, including the total number of reads and writes per second, the number of reads per second, the number of writes per second, the total I/O throughput, the read I/O throughput, and the write I/O throughput. | |
Performance events | Exceptions | Displays the statistics about anomalous events on the selected node. |
Optimization Events | Displays the statistics about optimization events on the selected node. |
FAQ
Why does the Advanced Monitoring page display a QPS of approximately 10 queries per second despite no active service traffic on the cluster?
The monitoring, log collection, and administration tasks that run in the system background generate approximately 10 queries per second. This has little impact on the performance of your cluster.
How do I resolve the high CPU utilization issue?
We recommend that you perform the following steps:
Check whether a large number of slow requests exist. If a large number of slow requests exist, we recommend that you optimize slow SQL statements first.
Check whether the trend of the CPU utilization curve is consistent with that of the QPS or TPS curve. If the trends of the curves are consistent, the issue is caused by high transaction concurrency. In this case, we recommend that you upgrade the configuration of your cluster.
If no slow requests exist and the curves are inconsistent, contact technical support.
What do I do when the number of connections is much greater than the number of active connections?
You can specify smaller values for the wait_timeout and interactive_timeout parameters to accelerate the release of idle connections. We recommend that you close the connections that are no longer in use in time to reduce the number of idle connections.
Related API operations
Operation | Description |
Queries the performance data of a PolarDB cluster. | |
Queries the performance data of a node in a PolarDB cluster. | |
Queries the frequency at which monitoring data of a PolarDB cluster is collected. | |
Modifies the frequency at which monitoring data of a PolarDB cluster is collected. |