Home PageApsaraDB for ClickHouseUser GuideMonitoring and alertingCluster monitoring managementView cluster monitoring information
Search for Help Content

View cluster monitoring information

Updated at: 2025-02-21 08:52
Product
Community

You can view the monitoring information about an ApsaraDB for ClickHouse cluster to understand the resource usage of the cluster. This topic describes how to view the monitoring information about an ApsaraDB for ClickHouse cluster.

Prerequisites

  • An ApsaraDB for ClickHouse cluster that runs Community-compatible Edition or Enterprise Edition is created.

  • The alerts of ApsaraDB for ClickHouse depend on the alert management feature of Application Real-Time Monitoring Service (ARMS). If you use a Resource Access Management (RAM) user, the RAM user must have the permissions to manage ARMS resources. To grant the management permissions to the RAM user, attach the AliyunARMSFullAccess policy to the RAM user. For more information, see Grant permissions to a RAM user.

Usage notes

  • You cannot view the monitoring information about Enterprise Edition clusters in the CloudMonitor console.

  • If Community-compatible Edition clusters were purchased before December 1, 2021, you must click Upgrade on the Cluster Monitoring tab to activate Managed Service for Prometheus.

    Important

    The activation will restart ApsaraDB for ClickHouse nodes and ZooKeeper nodes. We recommend that you perform this operation during off-peak hours or when data writing is stopped.

Procedure

ApsaraDB for ClickHouse console
CloudMonitor console

  1. Log on to the ApsaraDB for ClickHouse console.

  2. In the top navigation bar, select the region where the cluster is deployed.

  3. On the Clusters page, click the Clusters of Community-compatible Edition tab or the Enterprise Edition Clusters tab and click the ID of the cluster that you want to manage.

  4. In the left-side navigation pane, click Monitoring and Alerting.

  5. On the page that appears, click Cluster Monitoring.

    Note

    • By default, the monitoring information about various resources of the cluster within the last hour is displayed.

    • For more information about the metrics of Community-compatible Edition clusters purchased before December 1, 2021, see the Metrics of old-version clusters section of the Metrics topic.

    • For more information about the metrics of Community-compatible Edition clusters purchased after December 1, 2021, see the Metrics of ApsaraDB for ClickHouse clusters section of the Metrics topic.

  1. Log on to the CloudMonitor console.

  2. In the left-side navigation pane, choose Cloud Service Monitoring > Cloud Service Monitoring.

  3. On the Cloud Service Monitoring page, click Database.

  4. In the Database section, select a cloud service.

    Cloud service

    Description

    ClickHouse

    The ApsaraDB for ClickHouse Community-compatible Edition clusters purchased before December 1, 2021.

    ClickHouse Community-compatible Edition

    The ApsaraDB for ClickHouse Community-compatible Edition clusters purchased after December 1, 2021.

  5. On the page that appears, select the region where the cluster is deployed from the region drop-down list.

  6. Click the ID of the desired cluster to view the metrics of the cluster.

    Note

    • By default, the monitoring information about the cluster within the last hour is displayed.

    • You can query the monitoring information only within the last 30 days.

    • For more information about the metrics of ApsaraDB for ClickHouse, see Appendix 1: Metrics.

FAQ

Why do the CPU utilization and memory usage significantly vary among nodes?

If you use a Dual-replica Edition cluster or Single-replica Edition cluster that has multiple nodes, the CPU utilization and memory usage of the node on which a large number of write operations are performed are higher than those of other nodes. After data is synchronized to other nodes, the CPU utilization and memory usage gradually reach a balanced state across all nodes.

Why is cluster monitoring data missing for a specific period of time?

This issue occurs due to one of the following causes:

  • When you query data, an OOM error is reported.

  • The configuration of your cluster is modified. This causes your cluster to restart.

  • The specifications of your cluster are scaled up or scaled down. This causes your cluster to restart.

Related operations

CreateMonitorDataReport: creates a monitoring data report for an ApsaraDB for ClickHouse cluster.

DescribeDBClusterPerformance: queries performance data of an ApsaraDB for ClickHouse cluster.

References

For more information about CloudMonitor, see What is CloudMonitor?

Previous: Cluster monitoring managementNext: Metrics
  • On this page （1）
  • Prerequisites
  • Usage notes
  • Procedure
  • FAQ
  • Related operations
  • References
Feedback