Configuration parameters
This article describes parameters that can be configured for ADB ES services via ADCM.
|
NOTE
Some of the parameters become visible in the ADCM UI after the Show advanced flag being set.
|
AD Eureka
| Parameter | Description | Default value |
|---|---|---|
Xmx ram parameter |
A maximum Java heap size for the AD Eureka component (in GB) |
2 |
Log level |
Logging level for the AD Eureka component.
Possible values: |
INFO |
Registry app parameters |
Read-only configuration of the AD Eureka component in YAML format. The content can be used as a reference if you need to modify AD Eureka properties (see below) |
— |
AD eureka server app environment key-value |
This section lets you customize the behavior of the AD Eureka component using environment variables. Click Add property and enter the name of a variable and its value. Use the Registry app parameters read-only field to get the names of available variables |
— |
ADB Control
| Parameter | Description | Default value |
|---|---|---|
ADB user name |
ADB Control system user. A role with the same name is also created in ADB when you install the ADBC agents service in an ADB cluster. The name can only be changed before the ADB Control service is installed |
adcc |
Service password |
The password for the ADB Control system user |
— |
Listening port |
A port on which ADB Control UI is available via HTTP |
8890 |
Xmx ram parameter |
A maximum Java heap size for the ADB Control UI component (in GB) |
8 |
Log level |
Logging level for the ADB Control UI component.
Possible values: |
INFO |
UI server app parameters |
Read-only configuration of the ADB Control UI component in YAML format. The content can be used as a reference if you need to modify ADB Control UI properties (see below) |
— |
UI server app environment key-value |
This section lets you customize the behavior of the ADB Control UI component using environment variables. Click Add property and enter the name of a variable and its value. Use the UI server app parameters read-only field to get the names of available variables |
— |
| Parameter | Description | Default value |
|---|---|---|
UI LDAP authentication |
Whether to use LDAP authentication |
false |
LDAP type |
A type of the LDAP server. Possible values:
|
MSAD |
LDAP URI |
A URI for connecting to the LDAP server. Requires the following format: |
— |
Internal CA certificate in PEM format (optional) |
The internal CA certificate or certificate chain in PEM format that signed the LDAP server certificate |
— |
Users baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in users search requests |
— |
Groups baseDN |
A limitation of the search scope of objects in the LDAP directory that is used in groups search requests |
— |
Users OUs |
A list of OUs for user search.
If the option is set, users will be searched only in the specified OUs, otherwise — within full search scope specified in Users baseDN.
Enter each |
— |
Groups OUs |
A list of |
— |
Group |
A group name that is used for service requests to the LDAP server |
— |
Login |
A user name that is used for service requests to the LDAP server |
— |
Password |
A user password that is used for service requests to the LDAP server |
— |
Size limit |
A maximum number of records that can be returned by the LDAP server |
1000 |
Lowercase login |
Whether to convert user names to lowercase |
false |
| Parameter | Description | Default value |
|---|---|---|
Xmx ram parameter |
A maximum Java heap size for the ADB Control Backend component (in GB) |
8 |
Log level |
Logging level for the ADB Control Backend component.
Possible values: |
INFO |
Backend app parameters |
Read-only configuration of the ADB Control Backend component in YAML format. The content can be used as a reference if you need to modify ADB Control Backend properties (see below) |
— |
Backend server app environment key-value |
This section lets you customize the behavior of the ADB Control Backend component using environment variables. Click Add property and enter the name of a variable and its value. Use the Backend app parameters read-only field to get the names of available variables |
— |
| Parameter | Description | Default value |
|---|---|---|
Migration completion timeout |
A timeout (in minutes) for an ADB Control migration to complete |
5 |
Migration app parameter |
Read-only configuration of the ADB Control Migration component in YAML format. The content can be used as a reference if you need to modify ADB Control Migration properties (see below) |
— |
Migration server app environment key-value |
This section lets you customize the behavior of the ADB Control Migration component using environment variables. Click Add property and enter the name of a variable and its value. Use the Migration app parameter read-only field to get the names of available variables |
— |
| Parameter | Description | Default value |
|---|---|---|
Xmx ram parameter |
A maximum Java heap size for the ADB Control Scheduler component (in GB) |
2 |
Log level |
Logging level for the ADB Control Scheduler component.
Possible values: |
INFO |
Scheduler server app parameters |
Read-only configuration of the ADB Control Scheduler component in YAML format. The content can be used as a reference if you need to modify ADB Control Scheduler properties (see below) |
— |
Scheduler app environment key-value |
This section lets you customize the behavior of the ADB Control Scheduler component using environment variables. Click Add property and enter the name of a variable and its value. Use the Scheduler server app parameters read-only field to get the names of available variables |
— |
This section shows configuration of the ADBC agents service. You can use it as a reference if you want to customize the ADBC agents service in an ADB cluster.
ADBM
| Parameter | Description |
|---|---|
Password for adbm system-user |
The password for the |
| Parameter | Description | Default value |
|---|---|---|
Xmx ram parameter |
A maximum Java heap size for the ADBM Backend component (in GB) |
8 |
Log level |
Logging level for the ADBM Backend component.
Possible values: |
INFO |
Backend app parameters |
Read-only configuration of the ADBM Backend component in YAML format. The content can be used as a reference if you need to modify ADBM Backend properties (see below) |
— |
ADBM server app environment key-value |
This section lets you customize the behavior of the ADBM Backend component using environment variables. Click Add property and enter the name of a variable and its value. Use the Backend app parameters read-only field to get the names of available variables |
— |
| Parameter | Description | Default value |
|---|---|---|
Migration completion timeout |
A timeout (in minutes) for an ADBM migration to complete |
3 |
Xmx ram parameter |
A maximum Java heap size for the ADBM Database migration component (in GB) |
1 |
Migration app parameters |
Read-only configuration of the ADBM Database migration component in YAML format. The content can be used as a reference if you need to modify ADBM Database migration properties (see below) |
— |
ADBM migration app environment key-value |
This section lets you customize the behavior of the ADBM Database migration component using environment variables. Click Add property and enter the name of a variable and its value. Use the Migration app parameters read-only field to get the names of available variables |
— |
This section shows configuration of the ADBM agents service. You can use it as a reference if you want to customize the ADBM agents service in an ADB cluster.
This section shows configuration of ADBM CLI.
Clickhouse
| Parameter | Description | Default value |
|---|---|---|
Database type |
Choose the DBMS type:
|
Internal Clickhouse database parameters |
The available parameters depend on the database type that you select.
Internal Clickhouse database parameters
| Parameter | Description | Default value |
|---|---|---|
Data dir |
Directory for ClickHouse data storage |
/var/lib/clickhouse/ |
Username |
Database username for ClickHouse |
default |
Password |
Database password for ClickHouse |
— |
External Clickhouse parameters
| Parameter | Description | Default value |
|---|---|---|
Clickhouse address and port [ip_address:port] |
An external ClickHouse database address. You can use a clustered ClickHouse installation as an external database for ADB Control as well as a standalone node. To do this:
|
— |
Database name |
Database name in the external ClickHouse instance |
adcc |
Username |
Username for the external ClickHouse database |
default |
Password |
Password for the external ClickHouse database user |
— |
Database
| Parameter | Description | Default value |
|---|---|---|
Database type |
Choose the DBMS type:
|
Internal postgres database parameters |
The available parameters depend on the database type that you select in Database type.
Internal Postgres database parameters
| Parameter | Description | Default value |
|---|---|---|
Postgres user password |
Password for the |
— |
Data directory |
Directory used to store PostgreSQL data on hosts. Can only be changed before the Database service is installed |
/pg_data1 |
External postgres parameters
| Parameter | Description | Default value |
|---|---|---|
Server ip |
IP address of the external PostgreSQL database server |
— |
External database port |
Port of the external PostgreSQL database |
5432 |
Database name prefix |
Prefix for database names. The following two databases should exist in the external PostgreSQL instance: |
adcc |
Username |
Username for the external PostgreSQL database |
postgres |
Password |
Password for the external PostgreSQL database user |
— |
Monitoring
| Group | Parameter | Description | Default value |
|---|---|---|---|
— |
scrape_interval |
Target scrape frequency |
1m |
— |
scrape_timeout |
Scrape request timeout |
10s |
— |
Password for Grafana connection |
Password of a Grafana user ( |
— |
— |
Prometheus users to login/logout to Prometheus |
User credentials for logging into the Prometheus web interface |
— |
Service parameters |
config.file |
Path to the Prometheus server configuration file |
/etc/admprom/prometheus/prometheus.yml |
web.config.file |
Path to the web configuration file. The file is written in YAML format |
/etc/admprom/prometheus/prometheus-auth.yml |
|
storage.tsdb.path |
Path to the Prometheus server database |
/var/lib/admprom/prometheus |
|
web.listen-address |
Address to access the Prometheus web interface |
0.0.0.0:11200 |
|
web.console.libraries |
Path to console management libraries |
/usr/share/admprom/prometheus/console_libraries |
|
web.console.templates |
Path to Prometheus server console templates |
/usr/share/admprom/prometheus/consoles |
|
storage.tsdb.retention.time |
Specifies how long to retain samples in the storage.
Supported units: |
15d |
| Parameter | Description | Default value |
|---|---|---|
Grafana administrator’s password |
Password for the |
— |
Grafana listen port |
Port to access the Grafana web interface |
11210 |
| Parameter | Description | Default value |
|---|---|---|
Listen port |
Port to access ADB ES host system metrics in the Prometheus format |
11203 |
Metrics endpoint |
Endpoint to access ADB ES host system metrics in the Prometheus format |
/metrics |
| Parameter | Description | Default value |
|---|---|---|
[Prometheus] → Enable SSL |
Enables SSL encryption of incoming traffic for the Prometheus Server component |
Disabled |
[Prometheus] → Certificate file |
Path to the server SSL certificate file for the Prometheus Server component |
/etc/admprom/prometheus/server.crt |
[Prometheus] → Private key file |
Path to the file with the private key of the server SSL certificate for the Prometheus Server component |
/etc/admprom/prometheus/server.key |
[Prometheus] → Certificate authority file |
Path to the file with the CA certificate to verify Prometheus targets |
/etc/admprom/prometheus/ca.crt |
[Grafana] → Enable SSL |
Enables SSL encryption of incoming traffic for the Grafana component |
Disabled |
[Grafana] → Certificate file |
Path to the server SSL certificate file for the Grafana component |
/etc/admprom/grafana/server.crt |
[Grafana] → Private key file |
Path to the file with the private key of the server SSL certificate for the Grafana component |
/etc/admprom/grafana/server.key |
[Grafana] → Certificate authority file |
Path to the file with the CA certificate to verify the Prometheus certificate |
/etc/admprom/grafana/ca.crt |
[Node-exporter] → Enable SSL |
Enables SSL encryption of incoming traffic for the Node Exporter component |
Disabled |
[Node-exporter] → Certificate file |
Path to the server SSL certificate file for the Node Exporter component |
/etc/ssl/server.crt |
[Node-exporter] → Private key file |
Path to the file with the private key of the server SSL certificate for the Node Exporter component |
/etc/ssl/server.key |
| Parameter | Description | Default value |
|---|---|---|
Listen port |
Port to access Process Exporter metrics in the Prometheus format |
9256 |