Конференция Arenadata
ArenaTech 2026 – для всех, кому интересны технологии Big Data
Приглашаем вас принять участие в технической онлайн-конференции, посвященной работе с большими данными. Участие бесплатно для всех желающих.

В программе 3 блока докладов:

  • СУБД: архитектура и эксплуатация. Обсудим новые возможности Greengage DB и Arenadata DB на его основе, включая hot standby, обзор утилиты изменения кластерной топологии ggrebalance, вопросы безопасности и устранения CVE.
  • Платформа данных: безопасность и Kubernetes в ADH, аналитика в ADQM. Расскажем об управлении секретами и доступом в Arenadata Hyperwave с использованием OpenBao, особенности переноса сервисов в Kubernetes, а также про аналитические методы в инструментах ADQM.
  • Инструменты: кластерный менеджер, документация, ИИ-поиск. Поделимся опытом разработки технической документации (включая интеллектуальный поиск и ИИ-ассистент) и поговорим про развитие нашего кластерного менеджера ADCM.
Онлайн-конференция состоится 29 октября 2026 года, время трансляции: с 12:00 до 19:00 по московскому времени.
Осталось до события

Configuration parameters

This article describes the parameters that can be configured for ADM services via ADCM. To read about the configuring process, refer to the relevant articles for online and offline installation.

NOTE
Some of the parameters become visible in the ADCM UI after the Show advanced flag being set.

Grafana

Parameter Description Default value

Grafana data path

Path to the Grafana data storage on the host where Grafana is deployed. If changed, the changes apply only after performing the Uninstall and then Install service actions

/opt/adm/grafana/data

Grafana provisioning path

Path to the Grafana provisioning files on the host where Grafana is deployed. If changed, the changes apply only after performing the Uninstall and then Install service actions

/opt/adm/grafana/provisioning

Grafana port

HTTP port for the Grafana web interface

3000

Admin username

Grafana administrator username used to log in to the Grafana web interface

admin

Admin password

Password for the Grafana administrator. ADCM uses it to automatically create credentials (a system user and its API token) for dashboard synchronization

 — 

VictoriaMetrics

Replication Settings
Parameter Description Default value

Replication Factor

Number of the hosts with the VictoriaMetrics Storage component used for replicating each metric.

For details on replication factor calculations depending on the hosts number, see Add components (online installation) or Add components (offline installation)

2

Deduplication Interval

The deduplication interval that, when configured correctly, prevents the overlapping of duplicate metric points, which can result in a sawtooth pattern on your Grafana dashboards.

It is recommended to keep the default value (1ms) to ensure stable cluster replication out of the box. You can change this value to match the scrape interval of your metrics source, if necessary.

Large deduplication intervals (e.g. 1m or higher) increase memory consumption on hosts with the VictoriaMetrics Storage and VictoriaMetrics Select components installed, as the system must buffer more data to compare and deduplicate incoming metrics.

Format the value using ms (milliseconds), s (seconds), m (minutes), or h (hours). Example: 1ms. Combined values are not supported (e.g. 1s500ms is invalid). Entering an invalid value will result in the VictoriaMetrics service failing to run

1ms

Storage Settings
Parameter Description Default value

Retention Period

Metrics retention period. Metrics older than this value are automatically deleted from the storage.

The minimum retention period supported by VictoriaMetrics is 1 day (1d) or 24 hours (24h).

Indefinite retention is not supported by VictoriaMetrics. To retain data long-term, specify an arbitrarily high duration, such as 100 years (100y).

Format the value using d (days), w (weeks), M (months), or y (years). Combined values are also supported. Examples: 7d, 2w, 1M, 1y, 1M2w.

If you reduce the retention period, data older than the new limit is not deleted instantly upon service restart. VictoriaMetrics removes expired metrics gradually in the background

1M

Storage Data Path

Path to the VictoriaMetrics Storage data on the host where the VictoriaMetrics Storage component is deployed.

If changed, the changes apply only after restarting the VictoriaMetrics Storage component. See the VictoriaMetrics service actions

To change the storage location without losing metrics history, stop the VictoriaMetrics Storage component and copy the data directory to the new location (e.g. using rsync). Then, update this parameter in ADCM and start the VictoriaMetrics Storage component. VictoriaMetrics will automatically recognize and load the historical data from the new path

/opt/adm/vmstorage/data

Storage minimum free disk space (bytes)

Minimum amount of free disk space (bytes), that must remain available in the file system containing the VictoriaMetrics Storage data directory

10737418240

Storage memory allowed (bytes)

Maximum amount of memory (bytes) which VictoriaMetrics Storage is allowed to use for internal cache and buffers

1073741824

Add key,value

In this field, you can define additional parameters that are not displayed in ADCM UI, but are valid for the VictoriaMetrics Storage component.

Each key/value pair specified in this field is converted into a command-line argument in the -key=value format and added to the Docker container startup command

 — 

Select Settings
Parameter Description Default value

Query Timeout

Maximum time allowed for executing a query on VictoriaMetrics Select component. Queries exceeding this limit are canceled.

Format the value using ms (milliseconds), s (seconds), m (minutes), or h (hours). Example: 1ms

30s

Maximum Concurrent Queries

Maximum number of queries that can be executed concurrently by the VictoriaMetrics Select component. Queries exceeding this limit are queued for up to Maximum Queue Duration and rejected with an error if not processed during this period

16

Maximum Queue Duration

Maximum time a query can wait in the queue when the Maximum Concurrent Queries limit is reached. Any query not processed during this period is rejected.

Format the value using ms (milliseconds), s (seconds), m (minutes), or h (hours). Example: 1ms

10s

Maximum Samples Per Query

Maximum number of raw samples a single query can process. Queries exceeding this limit are rejected.

Increase for wide time ranges or high-resolution data

1000000000

Maximum Series in Response

Maximum number of time series returned by the /api/v1/series endpoint. Protects against excessively large responses.

Set to 0 to disable the limit

30000

Maximum Unique Time Series Per Query

Maximum number of unique time series a single query can select from VictoriaMetrics Storage. Set to 0 to disable the limit

300000

Disable Query Cache

Disables the VictoriaMetrics Select in-memory query results cache. When enabled, every query fetches fresh data from VictoriaMetrics Storage

false

Cache Data Path

Path inside the container for persistent query cache storage. Requires a writable volume mounted at this path. If not set, cache is kept in memory only and lost on container restart

/cache

Add key,value

In this field, you can define additional parameters that are not displayed in ADCM UI, but are valid for the VictoriaMetrics Select component.

Each key/value pair specified in this field is converted into a command-line argument in the -key=value format and added to the Docker container startup command

 — 

Insert Settings
Parameter Description Default value

Maximum Concurrent Inserts

Maximum number of insert requests that can be processed concurrently by the VictoriaMetrics Insert component. Requests exceeding this limit are queued for up to Maximum Insert Queue Duration and rejected with an error if not processed during this period

16

Maximum Insert Queue Duration

Maximum time a query can wait in the queue when the Maximum Concurrent Inserts limit is reached. Any query not processed during this period is rejected.

Format the value using ms (milliseconds), s (seconds), m (minutes), or h (hours). Example: 1ms

1m

Maximum Insert Request Size

Maximum size of a single Prometheus remote_write API request. Larger requests are rejected.

Format the value using KB, MB, GB, KiB, MiB, GiB. Example: 32MiB

32MiB

Maximum Labels Per Time Series

Maximum number of labels allowed for a single time series. Series with more labels are ignored, incrementing vm_rows_ignored_total{reason="too_many_labels"}

40

Maximum Label Name Length

Maximum length of a label name in accepted time series (bytes).

Series with longer label names are ignored

256

Maximum Label Value Length

Maximum length of a label value in accepted time series (bytes). Series with longer label values are ignored, incrementing the vm_rows_ignored_total{reason="too_long_label_value"} value

16384

Add key,value

In this field, you can define additional parameters that are not displayed in ADCM UI, but are valid for the VictoriaMetrics Insert component.

Each key/value pair specified in this field is converted into a command-line argument in the -key=value format and added to the Docker container startup command

 — 

Ports Configuration
Parameter Description Default value

vminsert HTTP Port

HTTP port used by the VictoriaMetrics Insert component to accept incoming metrics from agents like vmagent or Prometheus via the Prometheus-compatible remote_write protocol

8480

vmselect HTTP Port

HTTP port used by the VictoriaMetrics Select component to accept PromQL queries from visualization tools like Grafana

8481

vmstorage HTTP Port

HTTP port used by the VictoriaMetrics Storage component to handle health checks and self-monitoring metrics requests

8482

vmstorage vminsert RPC Port

TCP port used by the VictoriaMetrics Storage component to receive incoming metrics data from the VictoriaMetrics Insert component via an internal RPC protocol

8400

vmstorage vmselect RPC Port

TCP port used by the VictoriaMetrics Storage component to accept data read requests from the VictoriaMetrics Select component via an internal RPC protocol

8401

Security settings
Parameter Description Default value

pprof_authkey

The authentication key used to restrict access to the built-in Go profiler (/debug/pprof/) endpoints on the VictoriaMetrics Insert, VictoriaMetrics Select, and VictoriaMetrics Storage components.

ADCM always stores this key encrypted with Ansible Vault, so the ADCM UI displays it as a string starting with $ANSIBLE_VAULT;1.1;AES256. You can manage the key as follows:

  • Authentication. To authenticate requests to the profiler, pass the decrypted key as an HTTP Authorization header or as an authKey query parameter. The query parameter takes priority.

    URL template:

    http://<host>:<port>/debug/pprof/?authKey=<decrypted_key>

    Example: http://10.92.40.169:8482/debug/pprof/?authKey=xLUPib7YKNQuz0l6X9TrbncF

    Where:

    • <host> is the host address where the corresponding VictoriaMetrics component is deployed.

    • <port> is a port number of the corresponding VictoriaMetrics component (see Ports Configuration).

    • <decrypted_key> is the plaintext value of the key. To find it, log in to the host via SSH and run ps aux | grep pprofAuthKey.

  • Changing the key. Enter any plaintext string to use as the new authentication key. It will be encrypted by ADCM automatically.

     
    Leaving the key value empty disables authentication, making the profiling endpoints publicly accessible without a password.

 — 

Found a mistake? Seleсt text and press Ctrl+Enter to report it