View the monitoring information for an ApsaraDB for ClickHouse cluster to understand its resource usage. This topic describes how to view monitoring information for an ApsaraDB for ClickHouse cluster.
Prerequisites
The cluster is a Community-compatible Edition or Enterprise Edition instance.
Alerts for ApsaraDB for ClickHouse rely on the alert management service of Application Real-Time Monitoring Service (ARMS). If you are a Resource Access Management (RAM) user, you must have the AliyunARMSFullAccess permission to manage ARMS. For more information about how to grant permissions, see Grant permissions to a RAM user.
Usage notes
You cannot view the monitoring information of Enterprise Edition clusters in the CloudMonitor console.
For Community-compatible Edition clusters purchased before December 1, 2021, you can click the Upgrade ClickHouse button on the Cluster Monitoring page to manually enable Managed Service for Prometheus.
ImportantThis operation restarts the ClickHouse and ZooKeeper nodes. We recommend that you perform this operation during off-peak hours or when data writes are stopped.
Procedure
Use the ApsaraDB for ClickHouse console
Log on to the ApsaraDB for ClickHouse console.
In the upper-left corner of the page, select the region where the target cluster is located.
On the Clusters page, select the Clusters of Community-compatible Edition tab or the Enterprise Edition Clusters tab, and then click the ID of the target cluster.
In the navigation pane on the left, click Monitoring and Alerting.
Select Cluster Monitoring.
NoteBy default, monitoring data from the last hour is displayed.
For descriptions of metrics for Community-compatible Edition clusters purchased before December 1, 2021, see Metrics for earlier-version clusters.
For descriptions of metrics for Community-compatible Edition clusters purchased after December 1, 2021, see Metrics for ApsaraDB for ClickHouse clusters.
Use the CloudMonitor console
Log on to the CloudMonitor console.
In the navigation pane on the left, choose Cloud Resource Monitoring > Cloud Service Monitoring.
On the Cloud Service Monitoring page, click Database.
In the Database area, select the product name.
Product Name
Description
clickhouse
ApsaraDB for ClickHouse Community-compatible Edition clusters purchased before December 1, 2021.
ClickHouse Community-compatible Edition
ApsaraDB for ClickHouse Community-compatible Edition clusters purchased after December 1, 2021.
In the upper-left corner of the page, select the region where the cluster is located.
Click the ID of the target cluster to view its metrics.
NoteBy default, monitoring data from the last hour is displayed.
You can query monitoring data for up to the last 30 days.
For descriptions of ClickHouse metrics, see Appendix 1: Cloud service monitoring metrics.
FAQ
Q: Why do the CPU utilization and memory usage vary significantly among nodes?
If your cluster is a master-replica or single-replica multi-node cluster, when you perform multiple write operations, the write node's CPU and memory usage will be higher than other nodes. After data is synchronized to other nodes, CPU and memory usage will become more balanced.
Q: Why are there gaps in the monitoring data?
The common causes are as follows:
The query triggers an out-of-memory (OOM) error.
Modifying the configuration triggers a restart.
You restart the instance after you increase or decrease the quota.
Related API operations
References
If you are unfamiliar with CloudMonitor, see What is CloudMonitor?.