ApsaraDB for ClickHouse provides two ways to view cluster metrics: the built-in ApsaraDB for ClickHouse console (recommended for quick checks) and the CloudMonitor console (recommended for longer-term trend analysis and alert management). Use monitoring data to identify performance issues, diagnose node anomalies, and track resource utilization.
Prerequisites
Before you begin, make sure that:
-
Your cluster is a Community-compatible Edition or Enterprise Edition instance
-
(For alerting) If you are a Resource Access Management (RAM) user, your account has the AliyunARMSFullAccess permission. Alerts for ApsaraDB for ClickHouse are managed by Application Real-Time Monitoring Service (ARMS). For details on granting this permission, see Grant permissions to a RAM user
Constraints
-
You cannot view monitoring information for Enterprise Edition clusters in the CloudMonitor console. Use the ApsaraDB for ClickHouse console instead.
-
For Community-compatible Edition clusters purchased before December 1, 2021, you can enable Managed Service for Prometheus by clicking Upgrade ClickHouse on the Cluster Monitoring page. This operation restarts the ClickHouse and ZooKeeper nodes. Perform this during off-peak hours or when data writes are stopped.
View monitoring data in the ApsaraDB for ClickHouse console
This method works for both Community-compatible Edition and Enterprise Edition clusters, and shows monitoring data from the last hour by default.
-
Log on to the ApsaraDB for ClickHouse console.
-
In the upper-left corner, select the region where your cluster is located.
-
On the Clusters page, click the Clusters of Community-compatible Edition tab or the Enterprise Edition Clusters tab, then click the ID of your cluster.
-
In the left navigation pane, click Monitoring and Alerting.
-
Select Cluster Monitoring.
-
By default, monitoring data from the last hour is displayed. For metric descriptions, see:
-
Clusters purchased before December 1, 2021: Metrics for earlier-version clusters
-
Clusters purchased after December 1, 2021: Metrics for ApsaraDB for ClickHouse clusters
View monitoring data in the CloudMonitor console
This method applies only to Community-compatible Edition clusters and lets you query up to 30 days of historical data.
-
Log on to the CloudMonitor console.
-
In the left navigation pane, 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 Applies to clickhouse Community-compatible Edition clusters purchased before December 1, 2021 ClickHouse Community-compatible Edition Community-compatible Edition clusters purchased after December 1, 2021 -
In the upper-left corner, select the region where your cluster is located.
-
Click the ID of your cluster.
-
By default, monitoring data from the last hour is displayed.
-
You can query up to the last 30 days.
-
For metric descriptions, see Appendix 1: Cloud service monitoring metrics
FAQ
Why do CPU utilization and memory usage vary significantly across nodes?
In master-replica clusters and single-replica multi-node clusters, write operations are handled by the write node, so its CPU and memory usage will be higher than other nodes during bulk writes. Once data syncs to the remaining nodes, usage balances out automatically.
Why are there gaps in my monitoring data?
Gaps typically appear after one of the following events:
-
A query triggered an out-of-memory (OOM) error
-
A configuration change triggered a node restart
-
You scaled the cluster up or down (quota change)
API reference
-
CreateMonitorDataReport — Creates a monitoring data report
-
DescribeDBClusterPerformance — Queries performance data
What's next
If you are new to CloudMonitor, see What is CloudMonitor?.