The monitoring data outlined in this guide is accessible in ClickHouse Cloud. In addition to being displayed through the built-in dashboard described below, both basic and advanced performance metrics can also be viewed directly in the main service console.
- Utilization of hardware resources.
- ClickHouse server metrics.
Built-in advanced observability dashboard
ClickHouse comes with a built-in advanced observability dashboard feature which can be accessed by$HOST:$PORT/dashboard (requires user and password) that shows the following metrics:
- Queries/second
- CPU usage (cores)
- Queries running
- Merges running
- Selected bytes/second
- IO wait
- CPU wait
- OS CPU Usage (userspace)
- OS CPU Usage (kernel)
- Read from disk
- Read from filesystem
- Memory (tracked)
- Inserted rows/second
- Total MergeTree parts
- Max parts for partition
Resource utilization
ClickHouse also monitors the state of hardware resources by itself such as:- Load and temperature on processors.
- Utilization of storage system, RAM and network.
system.asynchronous_metric_log table.
ClickHouse server metrics
ClickHouse server has embedded instruments for self-state monitoring. To track server events use server logs. See the logger section of the configuration file. ClickHouse collects:- Different metrics of how the server uses computational resources.
- Common statistics on query processing.
HTTP GET request to /ping. If the server is available, it responds with 200 OK.
To monitor servers in a cluster configuration, you should set the max_replica_delay_for_distributed_queries parameter and use the HTTP resource /replicas_status. A request to /replicas_status returns 200 OK if the replica is available and is not delayed behind the other replicas. If a replica is delayed, it returns 503 HTTP_SERVICE_UNAVAILABLE with information about the gap.