Skip to main content
These settings configure the ClickHouse server and are autogenerated from ClickHouse source.

​
asynchronous_metrics_enable_heavy_metrics

Enable the calculation of heavy asynchronous metrics.

​
asynchronous_metrics_keeper_metrics_only

Make asynchronous metrics calculate the keeper-related metrics only.

​
asynchronous_metrics_key_values_mode

In which form the key-value asynchronous metrics - those broken down per CPU core, block device, network interface, disk, temperature sensor, memory controller or logging channel - are published to system.asynchronous_metrics, system.asynchronous_metric_log, the Prometheus endpoint and Graphite. Possible values:
  • key_values - every family is a single key-value metric: a Map in the key_values column of system.asynchronous_metrics, one row per key in system.asynchronous_metric_log, one Prometheus sample per key carrying a label such as device="sda", and a <prefix>.<Metric>.<key> Graphite path.
  • legacy_names - every key is a separate scalar metric with the key mangled into its name, as it was before version 26.8: OSUserTimeCPU3, CPUFrequencyMHz_0, BlockReadBytes_sda, NetworkReceiveBytes_eth0, DiskTotal_default, Temperature0, EDAC0_Correctable, and so on.
  • both - both forms are published at once, which is useful while the monitoring is being migrated. Beware of double counting in this mode: an aggregate over metric names matching a prefix, such as sum(value) ... WHERE metric LIKE 'NetworkReceiveBytes%', counts every value twice.
A key-value metric family introduced after version 26.8 has no legacy name and is always published in the key-value form. The setting is applied on the fly: it is re-read on every update of the asynchronous metrics, so SYSTEM RELOAD CONFIG is enough to switch the form without a restart.

​
asynchronous_metrics_update_period_s

Period in seconds for updating asynchronous metrics.
Last modified on August 28, 2026