我的书签
添加书签
移除书签2 Zabbix proxy
2 Zabbix proxy
本节中参数的默认值只是代表守护进程的默认使用值，实际运行时应以你所使用的配置文件中定义的参数值为准。
The default values reflect daemon defaults, not the values in the shipped configuration files.
以下参数可以在Zabbix proxy配置文件中配置： The parameters supported in a Zabbix proxy configuration file:
| 参数名称 必须配 | 范围 默 | 值 描述 | 息 | |
|---|---|---|---|---|
| Parameter | Mandatory | Range | Default | Description |
| AllowRoot | 否 | 许服务以 ‘root’身份运行。 如果该参数配置为禁止，并且服务仍以root身份启动，服务会切换到使用 ‘zabbix’用户启动 。 对于以普通用户启动的，该参数没有影响。 0 - 禁止 1 - 允许 Zabbix 2.2.0。以后的版本都支持这个参数 | ||
| AllowRoot | no | 0 | Allow the proxy to run as ‘root’. If disabled and the proxy is started by ‘root’, the proxy will try to switch to the ‘zabbix’ user instead. Has no effect if started under a regular user. 0 - do not allow 1 - allow This parameter is supported since Zabbix 2.2.0. | |
| CacheSize | 否 | 28K-8G | M | 存大小, 单位为字节。 用于存储主机、监控项数据的共享内存大小。 Zabbix2.2.3以前的版本最大可配置值为2GB。 |
| CacheSize | no | 128K-8G | 8M | Size of configuration cache, in bytes. Shared memory size, for storing host and item data. Upper limit used to be 2GB before Zabbix 2.2.3. |
| ConfigFrequency | 否 | -604800 | 600 | 隔多少秒proxy从Zabbix server获取配置数据。 该参数只有主动proxy才会使用，proxy工作模式由参数ProxyMode决定。 |
| ConfigFrequency | no | 1-604800 | 3600 | How often proxy retrieves configuration data from Zabbix server in seconds. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| DBHost | 否 | ocalhost | 据库主机名。 如果是MySQL localhost或空字符串会导致使用套接字。 如果是 PostgreSQL 只有空字符串会使用套接字。 | |
| DBHost | no | localhost | Database host name. In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL only empty string results in attempt to use socket. | |
| DBName | 是 | 据库名称。 对于 SQLite3 必须提供数据库文件路径（Zabbix的多进程架构不允许使用内存数据库，例如 ：memory：，file :: memory：？cache = shared或file：memdb1？mode = memory＆cache = shared）。警告: 不要与Zabbix server使用同一个数据库。 | ||
| DBName | yes | Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use in-memory database, e.g. :memory:, file::memory:?cache=shared or file:memdb1?mode=memory&cache=shared).Warning: Do not attempt to use the same database Zabbix server is using. | ||
| DBPassword | 否 | 据库登录密码。此参数SQLite不使用。 如果数据库没有密码，请注释掉此参数。 | ||
| DBPassword | no | Database password. Ignored for SQLite. Comment this line if no password is used. | ||
| DBSchema | 否 | 据库Schema 名字。仅IBM DB2 和 PostgreSQL使用。 | ||
| DBSchema | no | Schema name. Used for IBM DB2 and PostgreSQL. | ||
| DBSocket | 否 | 306 | ySQL套接字文件的路径。 本地套接字链接时不使用数据库端口参数。 此参数SQLite不使用。 | |
| DBSocket | no | 3306 | Path to MySQL socket. Database port when not using local socket. Ignored for SQLite. | |
| DBUser | 否 | 据库用户名。此参数SQLite不使用。 | ||
| DBUser | Database user. Ignored for SQLite. | |||
| DataSenderFrequency | 否 | -3600 | roxy将采集到的数据以一定的时间间隔（单位为秒）发送给Zabbix server。 该参数只有主动proxy才会使用，proxy工作模式由参数ProxyMode决定。 | |
| DataSenderFrequency | no | 1-3600 | 1 | Proxy will send collected data to the server every N seconds. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| DebugLevel | 否 | -5 | 定调试等级: 0 - Zabbix进程的起停基本信息 1 - 重要信息 2 - 错误信息 3 - 警告信息 4 - 调试信息 (产生大量信息) 5 - 扩展调试 (产生更多信息) | |
| DebugLevel | no | 0-5 | 3 | Specifies 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) |
| EnableRemoteCommands | 否 | 否允许Zabbix server远程执行命令。 0 - 禁止 1 - 允许 从Zabbix 3.4.0开始支持该参数。 | ||
| EnableRemoteCommands | no | 0 | Whether remote commands from Zabbix server are allowed. 0 - not allowed 1 - allowed This parameter is supported since Zabbix 3.4.0. | |
| ExternalScripts | 否 | usr/local/share/zabbix/externalscripts | 部脚本位置 (依赖编译安装时的环境变量datadir)。 | |
| ExternalScripts | no | /usr/local/share/zabbix/externalscripts | Location of external scripts (depends on compile-time installation variable datadir). | |
| Fping6Location | 否 | usr/sbin/fping6 | ping6程序的路径。 确保fping6程序的所有者是root用户，并且设置了SUID标记。 如果需要fping程序处理IPv6地址，就置空(“Fping6Location=”)参数 。 | |
| Fping6Location | no | /usr/sbin/fping6 | Location of fping6. Make sure that fping6 binary has root ownership and SUID flag set. Make empty (“Fping6Location=”) if your fping utility is capable to process IPv6 addresses. | |
| FpingLocation | 否 | usr/sbin/fping | ping程序的路径。 确保fping程序的所有者是root用户，并且设置了SUID标记。 | |
| FpingLocation | no | /usr/sbin/fping | Location of fping. Make sure that fping binary has root ownership and SUID flag set! | |
| HeartbeatFrequency | 否 | -3600 | 0 | 跳信息发送频率，单位为秒。 用于监视proxy的可用性。 0 - 禁止 该参数只有主动proxy才会使用，proxy工作模式由参数ProxyMode决定。 |
| HeartbeatFrequency | no | 0-3600 | 60 | Frequency of heartbeat messages in seconds. Used for monitoring availability of proxy on server side. 0 - heartbeat messages disabled. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| HistoryCacheSize | 否 | 28K-2G | 6M | 史缓存数据大小, 单位为字节。 |
| HistoryCacheSize | no | 128K-2G | 16M | Size of history cache, in bytes. Shared memory size for storing history data. |
| HistoryIndexCacheSize | 否 | 28K-2G | M | 史索引缓存大小, 单位为字节。\缓存一个item大概需要大小为100字节的空间。 该参数从Zabbix 3.0.0开始支持。 |
| HistoryIndexCacheSize | no | 128K-2G | 4M | Size of history index cache, in bytes. Shared memory size for indexing history data stored in history cache. The index cache size needs roughly 100 bytes to cache one item. This parameter is supported since Zabbix 3.0.0. |
| Hostname | 否 | 参数HostnameItem设置 唯一的大小 | 敏感的Proxy名称。确保Server端能正确解析这个proxy名称。 允许的字符: 字母, ‘.’, ‘ ‘, ‘‘ 和 ‘-‘. 最大长度: 64 | |
| Hostname | no | Set by HostnameItem | Unique, case sensitive Proxy name. Make sure the proxy name is known to the server! Allowed characters: alphanumeric, ‘.’, ‘ ‘, ‘‘ and ‘-‘. Maximum length: 64 | |
| HostnameItem | 否 | ystem.hostname | 参数Hostname没有定义时使用这个参数设置主机名。 该参数不能用于UserParameters, performance counters or aliases, 但能用于system.run[]。 从Zabbix 1.8.6开始支持该参数。 | |
| HostnameItem | no | system.hostname | Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent). Does not support UserParameters, performance counters or aliases, but does support system.run[]. Ignored if Hostname is set. This parameter is supported since Zabbix 1.8.6. | |
| HousekeepingFrequency | 否 | -24 | abbix 执行 housekeeping 的频率 (单位为小时)。 housekeeping负责从数据库中删除过期的信息。 注意: 为了防止 housekeeper 负载过大 (例如, 当历史和趋势周期大大减小时), 对于每一个监控项，不会在一个housekeeping周期内删除超过4倍HousekeepingFrequency 的过期数据。 因此, 如果 HousekeepingFrequency 是 1小时, 一个周期内不会删除超过4小时的过期信息 (从最旧的数据开始) 。 备注: 为降低 server压力， housekeeping将在server启动以后，延迟30分钟执行。 因此, 如果 HousekeepingFrequency 是1小时,serverg启动30分后执行第一次 housekeeping , 然后按1小时为周期重复执行。从Zabbix 2.4.0以后有了这种延迟行为。 从Zabbix 3.0.0开始，可以设置HousekeepingFrequency为0来禁止自动housekeeping。 此时 housekeeping 只能通过 housekeeper_execute 启动， 在一个housuekeeping周期内删除的过期信息时长为从最后一次housekeeping以来到配置周期的4倍,不少于4小时且不大于4天。 | |
| HousekeepingFrequency | no | 0-24 | 1 | How often Zabbix will perform housekeeping procedure (in hours). Housekeeping is removing outdated information from the database. Note: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. 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 proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. This postponing behavior is in place since Zabbix 2.4.0. Since Zabbix 3.0.0 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. |
| Include | 否 | 以在配置文件中指定单个文件或者指定一个目录（所有文件在该目录中）。 只有在指定的目录中包含相关文件, 才可以使用正则匹配的通配符 。例如: /absolute/path/to/config/files/.conf. Zabbix 2.4.0以后都支持模式匹配。参看关于限制条件特例。 | ||
| Include | no | You may include individual files or all files in a directory in the configuration file. To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: /absolute/path/to/config/files/.conf. Pattern matching is supported since Zabbix 2.4.0.See special notes about limitations. | ||
| JavaGateway | 否 | abbix Java 网关的IP 地址 (或主机名) 。 Java 轮询器启动时才需要该参数。 Zabbix 2.0.0以后的所有版本都支持该参数. | ||
| JavaGateway | no | IP address (or hostname) of Zabbix Java gateway. Only required if Java pollers are started. This parameter is supported since Zabbix 2.0.0. | ||
| JavaGatewayPort | 否 | 024-32767 | 0052 | abbix Java 网关监听端口。 Zabbix 2.0.0以后的所有版本都支持该参数。 |
| JavaGatewayPort | no | 1024-32767 | 10052 | Port that Zabbix Java gateway listens on. This parameter is supported since Zabbix 2.0.0. |
| ListenIP | 否 | .0.0.0 | rapper监听的Ip地址，多个Ip用逗号分开。 如果没有设置该参数，会监听所有网络接口。 从Zabbix 1.8.3开始支持多Ip地址。 | |
| ListenIP | no | 0.0.0.0 | List of comma delimited IP addresses that the trapper should listen on. Trapper will listen on all network interfaces if this parameter is missing. Multiple IP addresses are supported since Zabbix 1.8.3. | |
| ListenPort | 否 | 024-32767 | 0051 | rapper监听端口。 |
| ListenPort | no | 1024-32767 | 10051 | Listen port for trapper. |
| LoadModule | 否 | erver端启动时加载的模块，这些模块用来扩展server的功能。 格式: LoadModule=<module.so> 这些模块必须在LoadModulePath参数指定的路径中。 允许多个 LoadModule 参数。 | ||
| LoadModule | no | Module to load at proxy startup. Modules are used to extend functionality of the proxy. Format: LoadModule=<module.so> The modules must be located in directory specified by LoadModulePath. It is allowed to include multiple LoadModule parameters. | ||
| LoadModulePath | 否 | erver 模块的绝对路径。 默认值在编译时指定。 | ||
| LoadModulePath | no | Full path to location of proxy modules. Default depends on compilation options. | ||
| LogFile | 是, 如果LogType设置为file, 否则为 日志否 | 件名 | 。 | |
| LogFile | yes, if LogType is set to file, otherwise no | Name of log file. | ||
| LogFileSize | 否 | -1024 | 志文件大小，单位 MB。 0 - 禁止日志文件自动回滚. 注意: 如果日志文件达到限定的大小，文件回滚失败, 不管是什么原因, 现有的日志会被截断，并重新记录日志。 | |
| LogFileSize | no | 0-1024 | 1 | Maximum size of log file 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. |
| LogRemoteCommands | 否 | 执行shell命令时可以记录日志。 0 - 禁止 1 - 允许 从Zabbix 3.4.0开始支持该参数。 | ||
| LogRemoteCommands | no | 0 | Enable logging of executed shell commands as warnings. 0 - disabled 1 - enabled This parameter is supported since Zabbix 3.4.0. | |
| LogType | 否 | ile | 志输出类型: file - 写入LogFile 参数指定的日志文件中, system - 写入syslog, console - 控制台输出. 从Zabbix 3.0.0开始支持该参数。 | |
| LogType | no | file | Log output type: file - write log to file specified by LogFile parameter, system - write log to syslog, console - write log to standard output. This parameter is supported since Zabbix 3.0.0. | |
| LogSlowQueries | 否 | -3600000 | 据库查询消耗时间，大于该时间将会记入日志 (毫秒)。 0 - 不记录慢查询日志。 DebugLevel=3时该选项可用。 从Zabbix 1.8.2开始支持该参数 | |
| LogSlowQueries | no | 0-3600000 | 0 | How long a database query may take before being logged (in milliseconds). 0 - don’t log slow queries. This option becomes enabled starting with DebugLevel=3. This parameter is supported since Zabbix 1.8.2. |
| PidFile | 否 | tmp/zabbix_server.pid | ID文件名称。 | |
| PidFile | no | /tmp/zabbix_proxy.pid | Name of PID file. | |
| ProxyLocalBuffer | 否 | -720 | roxy将在本地保留数据N小时，即使数据已与server同步。\如果第三方应用程序将使用本地数据，则可以使用此参数。 | |
| ProxyLocalBuffer | no | 0-720 | 0 | Proxy will keep data locally for N hours, even if the data have already been synced with the server. This parameter may be used if local data will be used by third party applications. |
| ProxyMode | 否 | -1 | roxy工作模式。 0 - 主动模式 1 - 被动模式 从Zabbix 1.8.3开始支持该参数。 注意 当使用 Active proxy 时，敏感的 proxy 配置数据可供有权访问Zabbix server trapper端口的应用使用。 因为第三方应用可以假装是活动proxy并请求配置数据而不会进行身份验证。 | |
| ProxyMode | no | 0-1 | 0 | Proxy operating mode. 0 - proxy in the active mode 1 - proxy in the passive mode This parameter is supported since Zabbix 1.8.3. Note that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place. |
| ProxyOfflineBuffer | 否 | -720 | 果无法连接Zabbix server，proxy将保留数据N小时。\旧数据将丢失。 | |
| ProxyOfflineBuffer | no | 1-720 | 1 | Proxy will keep data for N hours in case of no connectivity with Zabbix server. Older data will be lost. |
| ServerPort | 否 | 024-32767 | 0051 | abbix server上trapper使用的端口. 该参数只有主动proxy才会使用，proxy工作模式由参数ProxyMode决定。 |
| ServerPort | no | 1024-32767 | 10051 | Port of Zabbix trapper on Zabbix server. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| Server | 是 | ProxyMode参数设置为 主动模式:\可以通过Zabbix server的IP地址或DNS名称获取配置数据并将数据发送给Zabbix server。 当ProxyMode参数设置为被动模式:\逗号分隔的IP地址列表，可选以CIDR表示法或Zabbix server的DNS名称。 仅接受来自此处配置地址的传入连接。 如果启用了IPv6支持，则“127.0.0.1”，“:: 127.0.0.1”，“:: ffff：127.0.0.1”将被同等对待，“:: / 0”将允许任何IPv4或IPv6地址。 ‘0.0.0.0/0’可用于允许任何IPv4地址。 示例：Server = 127.0.0.1,192.168.1.0 / 24，:: 1,2001：db8 :: / 32，zabbix.example.com | ||
| Server | yes | If ProxyMode is set to active mode: IP address or DNS name of Zabbix server to get configuration data from and send data to. If ProxyMode is set to passive mode: List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. 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: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com | ||
| SNMPTrapperFile | 否 | tmp/zabbix_traps.tmp | 时文件， 用于传递 SNMP trap守护进程的数据给server. 必须和 zabbix_trap_receiver.pl或 SNMPTT 配置文件中的配置保持一致。 从Zabbix 2.0.0开始支持该参数。 | |
| SNMPTrapperFile | no | /tmp/zabbix_traps.tmp | Temporary file used for passing data from SNMP trap daemon to the proxy. Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file. This parameter is supported since Zabbix 2.0.0. | |
| SocketDir | 否 | tmp | abbix 内部服务使用的用于存储 IPC sockets的目录。从Zabbix 3.4.0开始支持该参数。 | |
| SocketDir | no | /tmp | Directory to store IPC sockets used by internal Zabbix services. This parameter is supported since Zabbix 3.4.0. | |
| SourceIP | 否 | 外连接的源IP地址。 | ||
| SourceIP | no | Source IP address for outgoing connections. | ||
| SSHKeyLocation | no | SSH检查和操作的公钥和私钥的位置。 | ||
| SSHKeyLocation | no | Location of public and private keys for SSH checks and actions | ||
| SSLCertLocation | 否 | 于客户端身份验证的SSL证书文件的位置。 该参数只用于web监控，从Zabbix 2.4开始支持该参数。 | ||
| SSLCertLocation | no | Location of SSL client certificate files for client authentication. This parameter is used in web monitoring only and is supported since Zabbix 2.4.0. | ||
| SSLKeyLocation | 否 | 于客户端身份验证的SSL私钥文件的位置。 该参数只用于web监控，从Zabbix 2.4开始支持该参数。 | ||
| SSLKeyLocation | no | Location of SSL private key files for client authentication. This parameter is used in web monitoring only and is supported since Zabbix 2.4.0. | ||
| SSLCALocation | 否 | SSL服务器证书验证覆盖证书颁发机构(CA)文件的位置。如果不设置，系统范围的目录将被使用。 注意，这个参数的值将被设置为libcurl选项curloptcapath， 在7.42.0之前的libcurl版本中，只有使用OpenSSL编译libcurl才会有效。 更多信息见 cURL 网页. 这个参数从Zabbix 2.4.0开始的web监控和自从Zabbix 3.0.0开始的SMTP身份验证中使用。 | ||
| SSLCALocation | no | Location of certificate authority (CA) files for SSL server certificate verification. 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 since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0. | ||
| StartDBSyncers | 否 | -100 | 据库进程的初始实例数量。 在版本1.8.5之前，上限是64。 这个参数从Zabbix 1.8.3开始得到了支持。 | |
| StartDBSyncers | no | 1-100 | 4 | Number of pre-forked instances of DB Syncers. The upper limit used to be 64 before version 1.8.5. This parameter is supported since Zabbix 1.8.3. |
| StartDiscoverers | 否 | -250 | 现进程的初始实例数量。 在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartDiscoverers | no | 0-250 | 1 | Number of pre-forked instances of discoverers. The upper limit used to be 255 before version 1.8.5. |
| StartHTTPPollers | 否 | -1000 | TTP 轮询进程的初始实例数量。 在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartHTTPPollers | no | 0-1000 | 1 | Number of pre-forked instances of HTTP pollers. |
| StartIPMIPollers | 否 | -1000 | PMI 轮询进程的初始实例数量。 在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartIPMIPollers | no | 0-1000 | 0 | Number of pre-forked instances of IPMI pollers. The upper limit used to be 255 before version 1.8.5. |
| StartJavaPollers | 否 | -1000 | ava 轮询子进程的初始实例数量。 从Zabbix 2.0.0开始支持该参数。 | |
| StartJavaPollers | no | 0-1000 | 0 | Number of pre-forked instances of Java pollers. This parameter is supported since Zabbix 2.0.0. |
| StartPingers | 否 | -1000 | CMP pingers进程的初始实例数量 在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartPingers | no | 0-1000 | 1 | Number of pre-forked instances of ICMP pingers. The upper limit used to be 255 before version 1.8.5. |
| StartPollersUnreachable | 否 | -1000 | 可达主机 (包括IPMI 和 Java)的轮询进程的初始实例数量。 从Zabbix 2.4.0开始，如果IPMI或Java轮询器启动，那么至少有一个针对不可访问主机的轮询进程必须运行。\在Zabbix 1.8.5版本之前，最大能设置为255。 这个参数从Zabbix 1.8.3开始得到了支持。 | |
| StartPollersUnreachable | no | 0-1000 | 1 | Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java). Since Zabbix 2.4.0, at least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started. The upper limit used to be 255 before version 1.8.5. This option is missing in version 1.8.3. |
| StartPollers | 否 | -1000 | 询进程的初始实例数量。\在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartPollers | no | 0-1000 | 5 | Number of pre-forked instances of pollers. The upper limit used to be 255 before version 1.8.5. |
| StartSNMPTrapper | 否 | -1 | 置为1, SNMP trapper进程将启动。 从Zabbix 2.0.0开始支持该参数。 | |
| StartSNMPTrapper | no | 0-1 | 0 | If set to 1, SNMP trapper process will be started. This parameter is supported since Zabbix 2.0.0. |
| StartTrappers | 否 | -1000 | rapper进程的初始实例数量。 Trapper接收来自Zabbix发送者、主动agent的数据。 至少要运行一个trapper进程用于在web前端展示服务器可用性和队列视图。 在Zabbix 1.8.5版本之前，最大能设置为255。 | |
| StartTrappers | no | 0-1000 | 5 | Number of pre-forked instances of trappers. Trappers accept incoming connections from Zabbix sender and active agents. The upper limit used to be 255 before version 1.8.5. |
| StartVMwareCollectors | 否 | -250 | mware采集器进程的初始实例数量。\从Zabbix 2.2.0开始支持该参数。 | |
| StartVMwareCollectors | no | 0-250 | 0 | Number of pre-forked vmware collector instances. This parameter is supported since Zabbix 2.2.0. |
| Timeout | 否 | -30 | gent, SNMP设备或外部检查的超时时长(单位为秒)。 | |
| Timeout | no | 1-30 | 3 | Specifies how long we wait for agent, SNMP device or external check (in seconds). |
| TLSAccept | 是, 如果TLS certificate 或 PSK 参数都进行了定义(即使是未加密的连接), 否则为否 Zabbix server能接受哪些 | 接方 | 。 | 参数仅用于被动proxy。 可以指定多个值，以逗号分隔： 未加密接受无加密的连接（默认） // psk// - 接受与TLS的连接和预共享密钥（PSK） //cert // - 接受与TLS和证书的连接 从Zabbix 3.0.0开始支持该参数。 |
| TLSAccept | yes, if TLS certificate or PSK parameters are defined (even for unencrypted connection), otherwise no | What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: unencrypted - accept connections without encryption (default) psk - accept connections with TLS and a pre-shared key (PSK) cert - accept connections with TLS and a certificate This parameter is supported since Zabbix 3.0.0. | ||
| TLSCAFile | 否 | 含用于对等证书验证的顶级CA（s）证书的文件的完整路径名，用于Zabbix组件之间的加密通信。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSCAFile | no | Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSCertFile | 否 | 含服务器证书或证书链文件的完整路径名，用于Zabbix组件之间的加密通信。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSCertFile | no | Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSConnect | 是, 如果TLS certificate 或 PSK 参数进行了定义(即使是未加密的连接), 否则为否 该参数仅用于主动proxy连接Za | bi | s | rver。 仅可以选择一种方式: 未加密接受无加密的连接（默认） // psk // - 接受与TLS的连接和预共享密钥（PSK） // cert // - 接受与TLS和证书的连接 从Zabbix 3.0.0开始支持该参数。 |
| TLSConnect | yes, if TLS certificate or PSK parameters are defined (even for unencrypted connection), otherwise no | How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: unencrypted - connect without encryption (default) psk - connect using TLS and a pre-shared key (PSK) cert - connect using TLS and a certificate This parameter is supported since Zabbix 3.0.0. | ||
| TLSCRLFile | 否 | 含已吊销证书文件的完整路径名， 用于Zabbix组件之间的加密通信。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSCRLFile | no | Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSKeyFile | 否 | 含私钥文件的完整路径名，用于Zabbix组件之间的加密通信。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSKeyFile | no | Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSPSKFile | 否 | 含proxy与Zabbix server加密通信所使用的预共享密钥文件的完整路径名。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSPSKFile | no | Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server. This parameter is supported since Zabbix 3.0.0. | ||
| TLSPSKIdentity | 否 | 共享密钥身份字符串，用于与Zabbix server进行加密通信。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSPSKIdentity | no | Pre-shared key identity string, used for encrypted communications with Zabbix server. This parameter is supported since Zabbix 3.0.0. | ||
| TLSServerCertIssuer | 否 | 许server证书颁发者。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSServerCertIssuer | no | Allowed server certificate issuer. This parameter is supported since Zabbix 3.0.0. | ||
| TLSServerCertSubject | 否 | 许的server证书主题。 从Zabbix 3.0.0开始支持该参数。 | ||
| TLSServerCertSubject | no | Allowed server certificate subject. This parameter is supported since Zabbix 3.0.0. | ||
| TmpDir | 否 | tmp | 时目录。 | |
| TmpDir | no | /tmp | Temporary directory. | |
| TrapperTimeout | 否 | -300 | 00 | 义trapper处理数据的超时时间。 |
| TrapperTimeout | no | 1-300 | 300 | Specifies how many seconds trapper may spend processing new data. |
| User | 否 | abbix | 了降低权限使用普通用户。 仅当以’root’身份运行且AllowRoot参数设置为禁止时，该参数才起作用。 从Zabbix 2.4.0开始支持该参数。 | |
| User | no | zabbix | Drop privileges to a specific, existing user on the system. Only has effect if run as ‘root’ and AllowRoot is disabled. This parameter is supported since Zabbix 2.4.0. | |
| UnavailableDelay | 否 | -3600 | 0 | 资源不可用期间，Zabbix多少秒检查一次资源是否可用。 |
| UnavailableDelay | no | 1-3600 | 60 | How often host is checked for availability during the unavailability period, in seconds. |
| UnreachableDelay | 否 | -3600 | 5 | 资源不可达期间 ，Zabbix多少秒检查一次资源是否可达。 |
| UnreachableDelay | no | 1-3600 | 15 | How often host is checked for availability during the unreachability period, in seconds. |
| UnreachablePeriod | 否 | -3600 | 5 | 主机 不可用多少秒后，即视为主机不可用。 |
| UnreachablePeriod | no | 1-3600 | 45 | After how many seconds of unreachability treat a host as unavailable. |
| VMwareCacheSize | 否 | 56K-2G | M | 储VMware数据的共享内存大小。 VMware内部检查[vmware,buffer,…] 可以用来监控VMware缓存使用情况 (参见 内部检查)。 注意，如果没有配置并启动vmware收集器实例，那么共享内存就不会被分配。\从Zabbix 2.2.0开始支持该参数。 |
| VMwareCacheSize | no | 256K-2G | 8M | 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. This parameter is supported since Zabbix 2.2.0. |
| VMwareFrequency | 否 | 0-86400 | 0 | 隔多少秒从单个VMware服务收集数据。\任何VMware监控项的最小更新周期都大于或等于该时间。 从Zabbix 2.2.0开始支持该参数。 |
| VMwareFrequency | no | 10-86400 | 60 | Delay in seconds between data gathering from a single VMware service. This delay should be set to the least update interval of any VMware monitoring item. This parameter is supported since Zabbix 2.2.0. |
| VMwarePerfFrequency | 否 | 0-86400 | 0 | 隔多少秒从单个VMware服务检索性能计数器统计数据。 该时间为任一VMware 监控项（使用VMware性能计数器）的最小更新间隔。 从Zabbix 2.2.9, 2.4.4开始支持该参数。 |
| VMwarePerfFrequency | no | 10-86400 | 60 | Delay in seconds between performance counter statistics retrieval from a single VMware service. This delay should be set to the least update interval of any VMware monitoring item that uses VMware performance counters. This parameter is supported since Zabbix 2.2.9, 2.4.4 |
| VMwareTimeout | 否 | -300 | 0 | mware采集器等待 VMware 服务(vCenter or ESX 管理程序)响应的最大时长。 从Zabbix 2.2.9, 2.4.4开始支持该参数。 |
| VMwareTimeout | no | 1-300 | 10 | The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor). This parameter is supported since Zabbix 2.2.9, 2.4.4 |
Zabbix配置文件仅仅支持UTF-8编码但不支持BOM。
注释信息必须在行的开头使用”#”来标识。
Zabbix supports configuration files only in UTF-8 encoding without BOM.
Comments starting with “#” are only supported in the beginning of the line.
Parameters
| Parameter | Mandatory | Range | Default | Description |
|---|---|---|---|---|
| AllowRoot | no | 0 | Allow the proxy to run as ‘root’. If disabled and the proxy is started by ‘root’, the proxy will try to switch to the ‘zabbix’ user instead. Has no effect if started under a regular user. 0 - do not allow 1 - allow | |
| CacheSize | no | 128K-64G | 8M | Size of configuration cache, in bytes. Shared memory size, for storing host and item data. |
| ConfigFrequency | no | 1-604800 | 3600 | How often proxy retrieves configuration data from Zabbix server in seconds. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| DataSenderFrequency | no | 1-3600 | 1 | Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| DBHost | no | localhost | Database host name. In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL only empty string results in attempt to use socket. In case of Oracle empty string results in using the Net Service Name connection method; in this case consider using the TNSADMIN environment variable to specify the directory of the tnsnames.ora file. | |
| DBName | yes | Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use in-memory database, e.g. :memory:, file::memory:?cache=shared or file:memdb1?mode=memory&cache=shared).Warning: Do not attempt to use the same database Zabbix server is using. In case of Oracle, if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO_TASK environment variable if DBName is set to empty string. | ||
| DBPassword | no | Database password. Ignored for SQLite. Comment this line if no password is used. | ||
| DBSchema | no | Schema name. Used for PostgreSQL. | ||
| DBSocket | no | 3306 | Path to MySQL socket. Database port when not using local socket. Ignored for SQLite. | |
| DBUser | Database user. Ignored for SQLite. | |||
| DBTLSConnect | no | Setting this option enforces to use TLS connection to 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 On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: “required”, “verify”, “verify_full”. On MariaDB starting from version 10.2.6 “required” and “verify_full” values are supported. By default not set to any option and the behavior depends on database configuration. This parameter is supported since Zabbix 5.0.0. | ||
| DBTLSCAFile | no (yes, if DBTLSConnect set to one of: verify_ca, verify_full) | Full pathname of a file containing the top-level CA(s) certificates for database certificate verification. This parameter is supported since Zabbix 5.0.0. | ||
| DBTLSCertFile | no | Full pathname of file containing Zabbix server certificate for authenticating to database. This parameter is supported since Zabbix 5.0.0. | ||
| DBTLSKeyFile | no | Full pathname of file containing the private key for authenticating to database. This parameter is supported since Zabbix 5.0.0. | ||
| DBTLSCipher | no | The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2. Supported only for MySQL. This parameter is supported since Zabbix 5.0.0. | ||
| DBTLSCipher13 | no | The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol. Supported only for MySQL, starting from version 8.0.16. This parameter is supported since Zabbix 5.0.0. | ||
| DebugLevel | no | 0-5 | 3 | Specifies 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) |
| EnableRemoteCommands | no | 0 | Whether remote commands from Zabbix server are allowed. 0 - not allowed 1 - allowed This parameter is supported since Zabbix 3.4.0. | |
| ExternalScripts | no | /usr/local/share/zabbix/externalscripts | Location of external scripts (depends on compile-time installation variable datadir). | |
| Fping6Location | no | /usr/sbin/fping6 | Location of fping6. Make sure that fping6 binary has root ownership and SUID flag set. Make empty (“Fping6Location=”) if your fping utility is capable to process IPv6 addresses. | |
| FpingLocation | no | /usr/sbin/fping | Location of fping. Make sure that fping binary has root ownership and SUID flag set! | |
| HeartbeatFrequency | no | 0-3600 | 60 | Frequency of heartbeat messages in seconds. Used for monitoring availability of proxy on server side. 0 - heartbeat messages disabled. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| HistoryCacheSize | no | 128K-2G | 16M | Size of history cache, in bytes. Shared memory size for storing history data. |
| HistoryIndexCacheSize | no | 128K-2G | 4M | Size of history index cache, in bytes. Shared memory size for indexing history data stored in history cache. The index cache size needs roughly 100 bytes to cache one item. This parameter is supported since Zabbix 3.0.0. |
| Hostname | no | Set by HostnameItem | Unique, case sensitive Proxy name. Make sure the proxy name is known to the server! Allowed characters: alphanumeric, ‘.’, ‘ ‘, ‘‘ and ‘-‘. Maximum length: 128 | |
| HostnameItem | no | system.hostname | Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent). Does not support UserParameters, performance counters or aliases, but does support system.run[]. Ignored if Hostname is set. | |
| HousekeepingFrequency | no | 0-24 | 1 | How often Zabbix will perform housekeeping procedure (in hours). Housekeeping is removing outdated information from the database. Note: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. 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 proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter. Since Zabbix 3.0.0 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. |
| Include | no | You may include individual files or all files in a directory in the configuration file. To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: /absolute/path/to/config/files/*.conf.See special notes about limitations. | ||
| JavaGateway | no | IP address (or hostname) of Zabbix Java gateway. Only required if Java pollers are started. | ||
| JavaGatewayPort | no | 1024-32767 | 10052 | Port that Zabbix Java gateway listens on. |
| ListenBacklog | no | 0 - INT_MAX | SOMAXCONN | The maximum number of pending connections in the TCP queue. Default value is a hard-coded constant, which depends on the system. Maximum supported value depends on the system, too high values may be silently truncated to the ‘implementation-specified maximum’. |
| ListenIP | no | 0.0.0.0 | List of comma delimited IP addresses that the trapper should listen on. Trapper will listen on all network interfaces if this parameter is missing. | |
| ListenPort | no | 1024-32767 | 10051 | Listen port for trapper. |
| LoadModule | no | Module to load at proxy startup. Modules are used to extend functionality of the proxy. Formats: LoadModule=<module.so> LoadModule=<path/module.so> LoadModule=</abs_path/module.so> Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with ‘/‘) then LoadModulePath is ignored. It is allowed to include multiple LoadModule parameters. | ||
| LoadModulePath | no | Full path to location of proxy modules. Default depends on compilation options. | ||
| LogFile | yes, if LogType is set to file, otherwise no | Name of log file. | ||
| LogFileSize | no | 0-1024 | 1 | Maximum size of log file 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. |
| LogRemoteCommands | no | 0 | Enable logging of executed shell commands as warnings. 0 - disabled 1 - enabled This parameter is supported since Zabbix 3.4.0. | |
| LogType | no | file | Log output type: file - write log to file specified by LogFile parameter, system - write log to syslog, console - write log to standard output. This parameter is supported since Zabbix 3.0.0. | |
| LogSlowQueries | no | 0-3600000 | 0 | How long a database query may take before being logged (in milliseconds). 0 - don’t log slow queries. This option becomes enabled starting with DebugLevel=3. |
| PidFile | no | /tmp/zabbix_proxy.pid | Name of PID file. | |
| ProxyLocalBuffer | no | 0-720 | 0 | Proxy will keep data locally for N hours, even if the data have already been synced with the server. This parameter may be used if local data will be used by third party applications. |
| ProxyMode | no | 0-1 | 0 | Proxy operating mode. 0 - proxy in the active mode 1 - proxy in the passive mode Note that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place. |
| ProxyOfflineBuffer | no | 1-720 | 1 | Proxy will keep data for N hours in case of no connectivity with Zabbix server. Older data will be lost. |
| ServerPort | no | 1024-32767 | 10051 | Port of Zabbix trapper on Zabbix server. Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter). |
| Server | yes | If ProxyMode is set to active mode: IP address or DNS name of Zabbix server to get configuration data from and send data to. If ProxyMode is set to passive mode: List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. 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: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com | ||
| SNMPTrapperFile | no | /tmp/zabbix_traps.tmp | Temporary file used for passing data from SNMP trap daemon to the proxy. Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file. | |
| SocketDir | no | /tmp | Directory to store IPC sockets used by internal Zabbix services. This parameter is supported since Zabbix 3.4.0. | |
| SourceIP | no | Source IP address for: - outgoing connections to Zabbix server; - agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks); - HTTP agent connections; - script item JavaScript HTTP requests; - preprocessing JavaScript HTTP requests; - connections to the Vault | ||
| SSHKeyLocation | no | Location of public and private keys for SSH checks and actions | ||
| SSLCertLocation | no | Location of SSL client certificate files for client authentication. This parameter is used in web monitoring only. | ||
| SSLKeyLocation | no | Location of SSL private key files for client authentication. This parameter is used in web monitoring only. | ||
| SSLCALocation | no | Location of certificate authority (CA) files for SSL server certificate verification. 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 since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0. | ||
| StartDBSyncers | no | 1-100 | 4 | Number of pre-forked instances of history syncers. Note: Be careful when changing this value, increasing it may do more harm than good. |
| StartDiscoverers | no | 0-250 | 1 | Number of pre-forked instances of discoverers. |
| StartHistoryPollers | no | 0-1000 | 1 | Number of pre-forked instances of history pollers. This parameter is supported since Zabbix 5.4.0. |
| StartHTTPPollers | no | 0-1000 | 1 | Number of pre-forked instances of HTTP pollers. |
| StartIPMIPollers | no | 0-1000 | 0 | Number of pre-forked instances of IPMI pollers. |
| StartJavaPollers | no | 0-1000 | 0 | Number of pre-forked instances of Java pollers. |
| StartPingers | no | 0-1000 | 1 | Number of pre-forked instances of ICMP pingers. |
| StartPollersUnreachable | no | 0-1000 | 1 | 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. |
| StartPollers | no | 0-1000 | 5 | Number of pre-forked instances of pollers. |
| StartPreprocessors | no | 1-1000 | 3 | Number of pre-forked instances of preprocessing workers1. The preprocessing manager process is automatically started when a preprocessor worker is started. This parameter is supported since Zabbix 4.2.0. |
| StartSNMPTrapper | no | 0-1 | 0 | If set to 1, SNMP trapper process will be started. |
| StartTrappers | no | 0-1000 | 5 | Number of pre-forked instances of trappers. Trappers accept incoming connections from Zabbix sender and active agents. |
| StartVMwareCollectors | no | 0-250 | 0 | Number of pre-forked VMware collector instances. |
| StatsAllowedIP | no | List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. 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 This parameter is supported since Zabbix 4.2.0. | ||
| Timeout | no | 1-30 | 3 | Specifies how long we wait for agent, SNMP device or external check (in seconds). |
| TLSAccept | yes for passive proxy, if TLS certificate or PSK parameters are defined (even for unencrypted connection), otherwise no | What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma: unencrypted - accept connections without encryption (default) psk - accept connections with TLS and a pre-shared key (PSK) cert - accept connections with TLS and a certificate This parameter is supported since Zabbix 3.0.0. | ||
| TLSCAFile | no | Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSCertFile | no | Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSCipherAll | no | 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 This parameter is supported since Zabbix 4.4.7. | ||
| TLSCipherAll13 | no | 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 This parameter is supported since Zabbix 4.4.7. | ||
| TLSCipherCert | no | 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 This parameter is supported since Zabbix 4.4.7. | ||
| TLSCipherCert13 | no | Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption. This parameter is supported since Zabbix 4.4.7. | ||
| TLSCipherPSK | no | 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 This parameter is supported since Zabbix 4.4.7. | ||
| TLSCipherPSK13 | no | 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 This parameter is supported since Zabbix 4.4.7. | ||
| TLSConnect | yes for active proxy, if TLS certificate or PSK parameters are defined (even for unencrypted connection), otherwise no | How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified: unencrypted - connect without encryption (default) psk - connect using TLS and a pre-shared key (PSK) cert - connect using TLS and a certificate This parameter is supported since Zabbix 3.0.0. | ||
| TLSCRLFile | no | Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSKeyFile | no | Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components. This parameter is supported since Zabbix 3.0.0. | ||
| TLSPSKFile | no | Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server. This parameter is supported since Zabbix 3.0.0. | ||
| TLSPSKIdentity | no | Pre-shared key identity string, used for encrypted communications with Zabbix server. This parameter is supported since Zabbix 3.0.0. | ||
| TLSServerCertIssuer | no | Allowed server certificate issuer. This parameter is supported since Zabbix 3.0.0. | ||
| TLSServerCertSubject | no | Allowed server certificate subject. This parameter is supported since Zabbix 3.0.0. | ||
| TmpDir | no | /tmp | Temporary directory. | |
| TrapperTimeout | no | 1-300 | 300 | Specifies how many seconds trapper may spend processing new data. |
| User | no | zabbix | Drop privileges to a specific, existing user on the system. Only has effect if run as ‘root’ and AllowRoot is disabled. | |
| UnavailableDelay | no | 1-3600 | 60 | How often host is checked for availability during the unavailability period, in seconds. |
| UnreachableDelay | no | 1-3600 | 15 | How often host is checked for availability during the unreachability period, in seconds. |
| UnreachablePeriod | no | 1-3600 | 45 | After how many seconds of unreachability treat a host as unavailable. |
| VaultDBPath | no | Vault path from where credentials for database will be retrieved by keys ‘password’ and ‘username’. Example: secret/zabbix/database This option can only be used if DBUser and DBPassword are not specified. This parameter is supported since Zabbix 5.2.0. | ||
| VaultToken | no | Vault authentication token that should have been generated exclusively for Zabbix proxy with 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. This parameter is supported since Zabbix 5.2.0. | ||
| VaultURL | no | https://127.0.0.1:8200 | Vault server HTTP[S] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified. This parameter is supported since Zabbix 5.2.0. | |
| VMwareCacheSize | no | 256K-2G | 8M | 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. |
| VMwareFrequency | no | 10-86400 | 60 | Delay in seconds between data gathering from a single VMware service. This delay should be set to the least update interval of any VMware monitoring item. |
| VMwarePerfFrequency | no | 10-86400 | 60 | Delay in seconds between performance counter statistics retrieval from a single VMware service. This delay should be set to the least update interval of any VMware monitoring item that uses VMware performance counters. |
| VMwareTimeout | no | 1-300 | 10 | The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor). |
