Configuration parameters: Zabbix server

Overview

Configuration parameters allow customizing Zabbix server behavior.

Specify parameter values in the configuration file (zabbix_server.conf). All parameters are optional, unless explicitly stated that the parameter is mandatory.

This page is structured as:

• Parameter overview (to see full details of a parameter, click on its name)
• Parameter details

Note that:

• The default values reflect daemon defaults, not the values in the shipped configuration files.
• Values support environment variables.
• Zabbix supports configuration files only in UTF-8 encoding without BOM.
• Comments starting with # are only supported in the beginning of the line.

Such processes are data gathering by pollers, unreachable pollers, ODBC pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers together with IPMI manager, SNMP trapper, preprocessing workers, and discovery workers. Exhausting the file descriptor limit will cause Zabbix server to stop, typically shortly after startup but sometimes taking longer.

To avoid such issues, review the Zabbix server configuration file to optimize the number of concurrent checks and processes. Additionally, if necessary, ensure that the file descriptor limit is set sufficiently high by checking and adjusting system limits.

Parameter details

AlertScriptsPath

Specify the alert script location. Depends on the datadir compile-time installation variable.

Default: /usr/local/share/zabbix/alertscripts

AllowRoot

Allow server to run as root. If disabled and the server is started by root, the server will try to switch to the zabbix user instead. Has no effect if started under a regular user.

Default: 0
Values: 0 - do not allow; 1 - allow

AllowSoftwareUpdateCheck

Allow Zabbix UI receiving information about software updates from zabbix.com.

Default: 1
Values: 0 - do not allow; 1 - allow

AllowUnsupportedDBVersions

Allow server to work with unsupported database versions.

Default: 0
Values: 0 - do not allow; 1 - allow

CacheSize

Set the configuration cache size (in bytes). The shared memory size for storing host, item and trigger data.

Default: 32M
Range: 128K-64G

CacheUpdateFrequency

Set the configuration cache update frequency (in seconds). See also runtime control options.

Default: 10
Range: 1-3600

DBHost

Specify the database host (or socket directory).

For MySQL:

• localhost or an empty string uses the default UNIX-domain socket.

For PostgreSQL:

• localhost is resolved via DNS (typically to 127.0.0.1).
• An empty string uses the default UNIX-domain socket.
• A path (for example, /var/run/pgbouncer) results in using the UNIX socket at that path.
• A comma-separated list can contain multiple host:port values. Each host is tried in order until a read-write connection is established. Example: DBHost=localhost:5431,127.0.0.1:20051,zabbix.domain,[::1]:30051,[12fc::1]

Default: localhost

DBName

Specify the database name.

Mandatory: Yes

DBPassword

Specify the database password. Comment this line if no password is used.

DBPort

Specify the port of the Zabbix database host (see DBHost).
DBSocket and DBPort are mutually exclusive in server configuration. Specify only one, or leave both undefined.

Default for MySQL: 3306

Default for PostgreSQL: 5432

Range: 1024-65535

DBSchema

Specify the database schema name. Used for PostgreSQL.

DBSocket

Specify the path to the MySQL socket file.
DBSocket and DBPort are mutually exclusive in server configuration. Specify only one, or leave both undefined.

DBUser

Specify the database user.

DBTLSConnect

Specify a value to enforce a TLS connection to the database:
required - connect using TLS
verify_ca - connect using TLS and verify certificate
verify_full - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate

With MySQL, starting from 5.7.11, and PostgreSQL the follo/wing values are supported: required, verify_ca, verify_full.
With MariaDB, starting from version 10.2.6, the required and verify_full values are supported.
By default not set to any option and the behavior depends on database configuration.

DBTLSCAFile

Specify full pathname of the file containing the top-level CA(s) certificates for database certificate verification.

Mandatory: no (yes, if DBTLSConnect set to verify_ca or verify_full)

DBTLSCertFile

Specify full pathname of the file containing the Zabbix server certificate for authenticating to database.

DBTLSKeyFile

Specify full pathname of the file containing the private key for authenticating to database.

DBTLSCipher

Specify the list of encryption ciphers that Zabbix server permits for TLS protocols up through TLS v1.2. Supported only for MySQL.

DBTLSCipher13

Specify the list of encryption ciphersuites that Zabbix server permits for the TLS v1.3 protocol. Supported only for MySQL, starting from version 8.0.16.

DebugLevel

Set the debug level:
0 - basic information about starting and stopping of Zabbix processes
1 - critical information;
2 - error information;
3 - warnings;
4 - for debugging (produces lots of information);
5 - extended debugging (produces even more information).
See also runtime control options.

Default: 3
Range: 0-5

EnableGlobalScripts

Enable global scripts on Zabbix server.
Note: Global script execution is enabled by default. However, for new installations starting with Zabbix 7.0, EnableGlobalScripts is explicitly set to 0 (disabled).

Default: 1
Values: 0 - disable; 1 - enable

ExportDir

Specify a directory to enable real-time export of events, history and trends.

ExportFileSize

Set the maximum export file size (in bytes). Used for rotation if ExportDir is set.

Default: 1G
Range: 1M-1G

ExportType

Specify entity types for real-time export (events, history, trends). A comma-delimited list. All types are exported by default. Valid only if ExportDir is set.
Note that if ExportType is specified, but ExportDir is not, then this is a configuration error and the server will not start.

Example for history and trends export:

ExportType=history,trends

Example for event export only:

ExportType=events

ExternalScripts

Specify the external script location. Depends on the datadir compile-time installation variable.

Default: /usr/local/share/zabbix/externalscripts

Fping6Location

Specify the fping6 location. Make sure that the fping6 binary has root ownership and the SUID flag set. Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.

Default: /usr/sbin/fping6

FpingLocation

Specify the fping location. Make sure that the fping binary has root ownership and the SUID flag set.

Default: /usr/sbin/fping

FrontendAllowedIP

Specify IP addresses or CIDR ranges that are permitted to connect from the frontend. A comma-separated list. By default all connections are accepted for frontend requests. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.

Example:

FrontendAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com

HANodeName

Specify the node name in a high-availability cluster. When empty the server is working in standalone mode and a node with empty name is created.

HistoryCacheSize

Set the history cache size (in bytes). The shared memory size for storing history data.

Default: 16M
Range: 128K-16G

HistoryIndexCacheSize

Set the history-index cache size (in bytes). The shared memory size for indexing the history data stored in history cache. The index cache size needs roughly 100 bytes to cache one item.

Default: 4M
Range: 128K-16G

HistoryStorageDateIndex

Enable storing history values in different indices based on date.

Default: 0
Values: 0 - disable; 1 - enable

HistoryStorageURL

Specify the history storage URL. This parameter is used for Elasticsearch setup.

HistoryStorageTypes

Specify value types to be sent to history storage. A comma-delimited list. This parameter is used for Elasticsearch setup.

Default: uint,dbl,str,log,text,json

HousekeepingFrequency

Set the housekeeping procedure frequency (in hours). Housekeeping is removing outdated information from the database.
Note: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.
Note: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter.
It is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by housekeeper_execute runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
See also runtime control options and details on the housekeeping procedure.

Default: 1
Range: 0-24

Include

Specify a directory or individual files to be included in the configuration file. To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. See special notes about limitations.

Example:

Include=/absolute/path/to/config/files/*.conf

JavaGateway

Specify the IP address or hostname of Zabbix Java gateway. Only required if Java pollers are started.

JavaGatewayPort

Specify the Zabbix Java gateway port.

Default: 10052
Range: 1024-32767

ListenBacklog

Set the maximum number of pending connections in the TCP queue.
The default value is a hard-coded constant, which depends on the system.
The maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.

Default: SOMAXCONN
Range: 0 - INT_MAX

ListenIP

Specify the trapper listen IP address. A comma-delimited list.
Trapper will listen on all network interfaces if this parameter is not specified.

Default: 0.0.0.0

ListenPort

Specify the trapper listen port.

Default: 10051
Range: 1024-32767

LoadModule

Specify the module to load at server startup. Modules are used to extend the functionality of the server. The module must be located in the directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.
Formats:
LoadModule=<module.so>
LoadModule=<path/module.so>
LoadModule=</abs_path/module.so>
It is allowed to include multiple LoadModule parameters.

LoadModulePath

Specify full path to the location of server modules. The default depends on compilation options.

LogFile

Specify the server log file.

Mandatory: Yes, if LogType is set to file; otherwise no

LogFileSize

Set the maximum log file size (in MB).
0 - disable automatic log rotation.
Note: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.

Default: 1
Range: 0-1024
Mandatory: Yes, if LogType is set to file; otherwise no

LogSlowQueries

Set the maximum duration a database query may take before being logged (in milliseconds).
0 - don't log slow queries.
This option becomes enabled starting with DebugLevel=3.

Default: 0
Range: 0-3600000

LogType

Specify the log output type:
file - write log to file specified by LogFile parameter;
system - write log to syslog;
console - write log to standard output.

Default: file

MaxConcurrentChecksPerPoller

Set the maximum number of asynchronous checks that can be executed at once by each HTTP agent poller, agent poller or SNMP poller. See StartHTTPAgentPollers, StartAgentPollers, and StartSNMPPollers.

Default: 1000
Range: 1-1000

MaxHousekeeperDelete

Set the maximum number of rows to be deleted per task in one housekeeping cycle from history, history_str, history_log, history_uint, history_text, history_bin, history_json, trends, trends_uint and problem tables.
Housekeeping tasks exist in the housekeeper table in the format: [housekeeperid], [object], [objectid].
This parameter applies only to deleting data left behind by already deleted items.
If set to 0 then no limit is used at all.
In this case you must know what you are doing, so as not to overload the database.
When a lot of items are deleted it increases the load to the database, because the housekeeper will need to remove all the history data that these items had.
For example, if we only have to remove 1 item prototype from the template, but this template is linked to 50 hosts and for every host the prototype is expanded to 100 real items, 5000 items in total have to be removed (1*50*100).
If 500 is set for MaxHousekeeperDelete (MaxHousekeeperDelete=500), the housekeeper process will have to remove up to 2500000 values (5000*500) for the deleted items from history and trends tables in one cycle.

See also details on the housekeeping procedure.

Default: 5000
Range: 0-1000000

NodeAddress

Specify IP or hostname with optional port to override how the frontend connects to the server.
Format: <address>[:<port>]

If IP or hostname is not set, the value of ListenIP will be used. If ListenIP is not set, the value localhost will be used.
If port is not set, the value of ListenPort will be used. If ListenPort is not set, the value 10051 will be used.

This option can be overridden by the address specified in the frontend configuration.

See also: HANodeName parameter; Enabling high availability.

Default: localhost:10051

PidFile

Specify the PID file.

Default: /tmp/zabbix_server.pid

ProblemHousekeepingFrequency

Set the frequency of deleting problems for deleted triggers (in seconds).
See also details on the housekeeping procedure.

Default: 60
Range: 1-3600

ProxyConfigFrequency

Set the frequency of sending configuration data to Zabbix proxy by the server. Used only for proxies in the passive mode.

Default: 10
Range: 1-604800

ProxyDataFrequency

Set the frequency of requesting history data from Zabbix proxy by the server. Used only for proxies in the passive mode.

Default: 1
Range: 1-3600

ServiceManagerSyncFrequency

Set the frequency of synchronizing the configuration of a service manager (in seconds).

Default: 60
Range: 1-3600

SMSDevices

Specify modem files that are allowed to use Zabbix server. A comma-delimited list.
SMS sending is not possible if this parameter is not set.

Example:

SMSDevices=/dev/ttyUSB0,/dev/ttyUSB1

SNMPTrapperFile

Specify the temporary file used for passing data from the SNMP trap daemon to the server.
Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.

Default: /tmp/zabbix_traps.tmp

SocketDir

Specify the directory for storing IPC sockets used by internal Zabbix services.

Default: /tmp

SourceIP

Specify the source IP address for:

• outgoing connections to Zabbix proxy and Zabbix agent
• agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks)
• HTTP agent connections
• script item JavaScript HTTP requests
• preprocessing JavaScript HTTP requests
• sending notification emails (connections to SMTP server)
• webhook notifications (JavaScript HTTP connections)
• connections to the Vault

SSHKeyLocation

Specify the location of public and private keys for SSH checks and actions.

SSLCertLocation

Specify the location of SSL-client certificate files for client authentication.
This parameter is used in web monitoring only.

SSLKeyLocation

Specify the location of SSL private key files for client authentication.
This parameter is used in web monitoring only.

SSLCALocation

Specify the location of certificate authority (CA) files for SSL-server certificate verification. If not set, system-wide directory will be used.
Note that the value of this parameter will be set as libcurl option CURLOPT_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see cURL web page.
This parameter is used in web monitoring and in SMTP authentication.

StartAgentPollers

Set the number of pre-forked instances of Zabbix agent pollers. See MaxConcurrentChecksPerPoller.

Default: 1
Range: 0-1000

StartAlerters

Set the number of pre-forked instances of alerters.

Default: 3
Range: 1-100

StartBrowserPollers

Set the number of pre-forked instances of browser item pollers.

Default: 1
Range: 0-1000

StartConnectors

Set the number of pre-forked instances of connector workers. The connector manager process is started automatically when a connector worker is started.

Default: 0
Range: 0-1000

StartDBSyncers

Set the number of pre-forked instances of history syncers.
Note: Be careful when changing this value, increasing it may do more harm than good. Roughly, the default value should be enough to handle up to 4000 NVPS.

Default: 4
Range: 1-100

StartDiscoverers

Set the number of pre-forked instances of discovery workers¹.

Default: 5
Range: 0-1000

StartEscalators

Set the number of pre-forked instances of escalators.

Default: 1
Range: 1-100

StartHistoryPollers

Set the number of pre-forked instances of history pollers.
Only required for calculated checks.

Default: 5
Range: 0-1000

StartHTTPAgentPollers

Set the number of pre-forked instances of HTTP agent pollers. See MaxConcurrentChecksPerPoller.

Default: 1
Range: 0-1000

StartHTTPPollers

Set the number of pre-forked instances of HTTP pollers¹.

Default: 1
Range: 0-1000

StartIPMIPollers

Set the number of pre-forked instances of IPMI pollers.

Default: 0
Range: 0-1000

StartJavaPollers

Set the number of pre-forked instances of Java pollers¹.

Default: 0
Range: 0-1000

StartLLDProcessors

Set the number of pre-forked instances of low-level discovery (LLD) workers¹.
The LLD manager process is automatically started when an LLD worker is started.

Default: 2
Range: 1-100

StartODBCPollers

Set the number of pre-forked instances of ODBC pollers¹.

Default: 1
Range: 0-1000

StartPingers

Set the number of pre-forked instances of ICMP pingers¹.

Default: 1
Range: 0-1000

StartPollersUnreachable

Set the number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java)¹.
At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.

Default: 1
Range: 0-1000

StartPollers

Set the number of pre-forked instances of pollers¹.

Default: 5
Range: 0-1000

StartPreprocessors

Set the number of pre-started instances of preprocessing worker¹ threads should be set to no less than the available CPU core count. More workers should be set if preprocessing is not CPU-bound and has lots of network requests.

Default: 16
Range: 1-1000

StartProxyPollers

Set the number of pre-forked instances of pollers for passive proxies¹.

Default: 1
Range: 0-250

StartReportWriters

Set the number of pre-forked instances of report writers.
If set to 0, scheduled report generation is disabled.
The report manager process is automatically started when a report writer is started.

Default: 0
Range: 0-100

StartSNMPPollers

Set the number of pre-forked instances of SNMP pollers. See MaxConcurrentChecksPerPoller.

Default: 1
Range: 0-1000

StartSNMPTrapper

Set to 1 to start an SNMP trapper process.

Default: 0
Range: 0-1

StartTimers

Set the number of pre-forked instances of timers.
Timers process maintenance periods.

Default: 1
Range: 1-1000

StartTrappers

Set the number of pre-forked instances of trappers¹.
Trappers accept incoming connections from Zabbix sender, active agents and active proxies.

Default: 5
Range: 0-1000

StartVMwareCollectors

Set the number of pre-forked VMware collector instances.

Default: 0
Range: 0-250

StatsAllowedIP

Specify IP addresses (optionally in CIDR notation) or DNS names of external Zabbix instances that are allowed to request stats. A comma-delimited list.
If this parameter is not set no stats requests will be accepted.
If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.

Example:

StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com

Timeout

Specify how long to wait (in seconds) for establishing connection and exchanging data with Zabbix proxy, agent, web service, and legacy SNMP checks (single OID number or string).

This parameter defines the duration for various communication operations:

• remote command execution on Zabbix agent
• SSH/Telnet command execution
• requests to Zabbix web service
• communication timeout for mediatype test request and the history.push method
• rescheduling of items when an IPMI interface becomes unavailable
• sending response to Zabbix proxy when failing to exchange data due to rights or encryption issues
• deadline for IPC asynchronous sockets and runtime control options
• JMX connections
• fetching statistics from a remote Zabbix proxy or server
• sending responses to Zabbix frontend
• asynchronous poller DNS requests
• response for active check heartbeat
• retrieval of Zabbix agent data (values) from active agents
• retrieval of data from Zabbix sender
• response when trapper fails to process a request
• sending active check list to Zabbix agent

This timeout will not be used for those checks that have flexible timeout settings configured in the frontend (on global, proxy, or per-item level). For example, SNMP walk[OID] and get[OID] items use the configured timeout from the frontend; legacy SNMP checks still use the server timeout value.

Default: 3
Range: 1-30

TLSCAFile

Specify full pathname of the file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.

TLSCertFile

Specify full pathname of the file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.

TLSCipherAll

Specify the GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.

Example:

TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256

TLSCipherAll13

Specify the cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.

Example for GnuTLS:

NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509

Example for OpenSSL:

EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128

TLSCipherCert

Specify the GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.

Example for GnuTLS:

NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509

Example for OpenSSL:

EECDH+aRSA+AES128:RSA+aRSA+AES128

TLSCipherCert13

Specify the cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.

TLSCipherPSK

Specify the GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.

Example for GnuTLS:

NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL

Example for OpenSSL:

kECDHEPSK+AES128:kPSK+AES128

TLSCipherPSK13

Specify the cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.

Example:

TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256

TLSCRLFile

Specify full pathname of the file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.

TLSFrontendAccept

Specify encryption level for incoming connections from the frontend.

Multiple values can be specified, separated by comma:

• unencrypted - accept connections without encryption.
• cert - accept connections secured with TLS and a certificate.

Default: unencrypted

TLSFrontendCertIssuer

Specify the allowed frontend certificate issuer.

TLSFrontendCertSubject

Specify the allowed frontend certificate subject.

TLSKeyFile

Specify full pathname of the file containing the server private key, used for encrypted communications between Zabbix components.

TLSListen

Require TLS-only connections on the trapper socket.

Supported values:

• required - accept only TLS connections

TmpDir

Specify the temporary directory.

Default: /tmp

TrapperTimeout

Specify trapper timeout in seconds for:

• retrieval of historical data from Zabbix proxy
• sending configuration data to Zabbix proxy
• global script execution or remote command execution on Zabbix server

Default: 300
Range: 1-300

TrendCacheSize

Set the trend cache size, in bytes.
The shared memory size for storing trends.

Default: 4M
Range: 128K-16G

TrendFunctionCacheSize

Set the trend-function cache size, in bytes.
The shared memory size for caching calculated trend function data.

Default: 4M
Range: 128K-2G

UnavailableDelay

Set the frequency of checking host availability during the unavailability period in seconds.

Default: 60
Range: 1-3600

UnreachableDelay

Set the frequency of checking host availability during the unreachability period in seconds.

Default: 15
Range: 1-3600

UnreachablePeriod

Set after how many seconds of unreachability treat host as unavailable.

Default: 45
Range: 1-3600

User

Drop privileges to a specific, existing user on the system.
Only has effect if run as 'root' and AllowRoot is disabled.

Default: zabbix

ValueCacheSize

Set the size of the history value cache (in bytes).
The shared memory size for caching item history data requests.
Setting to 0 disables the value cache (not recommended).
When the value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.

Default: 8M
Range: 0,128K-64G

Vault

Specify the vault provider:
HashiCorp - HashiCorp KV Secrets Engine version 2
CyberArk - CyberArk Central Credential Provider
Must match the vault provider set in the frontend.

Default: HashiCorp

VaultDBPath

Specify the location for retrieving database credentials by keys. It is a Vault path or query, depending on the Vault.

The keys used for HashiCorp are 'password' and 'username'.

Example path with VaultPrefix=/v1/secret/data/zabbix/:

database

Example path without VaultPrefix:

secret/zabbix/database

The keys used for CyberArk are 'Content' and 'UserName'.

Example:

AppID=zabbix_server&Query=Safe=passwordSafe;Object=zabbix_server_database

This option can only be used if DBUser and DBPassword are not specified.

VaultPrefix

Specify custom prefix for the vault path or query, depending on the Vault. The most suitable defaults will be used if not specified.
Note that 'data' is automatically appended after mountpoint for HashiCorp if VaultPrefix is not specified.

Example prefix for Hashicorp:

v1/secret/data/zabbix/

Example prefix for Cyberark:

/AIMWebService/api/Accounts?

VaultTLSCertFile

Specify the name of the SSL certificate file used for client authentication. The certificate file must be in PEM1 format.
If the certificate file contains also the private key, leave the SSL key file field empty.
The directory containing this file is specified by the configuration parameter SSLCertLocation.
This option can be omitted but is recommended for CyberArkCCP vault.

VaultTLSKeyFile

Specify the name of the SSL private key file used for client authentication. The private key file must be in PEM1 format.
The directory containing this file is specified by the configuration parameter SSLKeyLocation.
This option can be omitted but is recommended for CyberArkCCP vault.

VaultToken

Specify the HashiCorp vault authentication token. The HashiCorp Vault authentication token should have been generated exclusively for Zabbix server with read-only permission to the paths specified in Vault macros and read-only permission to the path specified in the optional VaultDBPath configuration parameter.
It is an error if VaultToken and VAULT_TOKEN environment variable are defined at the same time.

Mandatory: Yes, if Vault is set to HashiCorp; otherwise no

VaultURL

Specify the vault server URL. The system-wide CA certificates directory will be used if SSLCALocation is not specified.

Default: https://127.0.0.1:8200

VMwareCacheSize

Set the shared memory size for storing VMware data. A VMware internal check zabbix[vmware,buffer,...] can be used to monitor the VMware cache usage (see Internal checks).
Note that shared memory is not allocated if there are no vmware collector instances configured to start.

Default: 8M
Range: 256K-2G

VMwareFrequency

Set the frequency of data gathering from a single VMware service (in seconds). This frequency should be set to the least update interval of any VMware monitoring item.

Default: 60
Range: 10-86400

VMwarePerfFrequency

Set the frequency of retrieving performance counter statistics from a single VMware service (in seconds).
This frequency should be set to the least update interval of any VMware monitoring item that uses VMware performance counters.

Default: 60
Range: 10-86400

VMwareTimeout

Set the maximum number of seconds a vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).

Default: 10
Range: 1-300

WebDriverURL

Specify the WebDriver interface URL.

Example (used with Selenium WebDriver standalone server):

WebDriverURL=http://localhost:4444

WebServiceURL

Specify the web service URL in the format http[s]://host:port/report.

Example:

WebServiceURL=http://localhost:10053/report

The http:// scheme may be omitted for non-TLS (HTTP) connections only; with TLS configured, https:// must be used.