Table of Contents
1 Zabbix server
本节中参数的默认值只是代表守护进程的默认使用值，实际运行时应以你所使用的配置文件中定义的参数值为准。
The default values reflect daemon defaults, not the values in the shipped configuration files.
以下参数可以在Zabbix server配置文件中配置： The parameters supported in a Zabbix server configuration file:
| 参数名称 必须配 | 范围 默 | 值 | 描述信息 | |
|---|---|---|---|---|
| Parameter | Mandatory | Range | Default | Description |
| AlertScriptsPath | 否 | usr/local/share/zabbix/alertscripts | 定义报警脚本位置 (依赖编译安装时的参数设置 datadir)。 | |
| AlertScriptsPath | no | /usr/local/share/zabbix/alertscripts | Location of custom alert scripts (depends on compile-time installation variable datadir). | |
| AllowRoot | 否 | 许服务以 'root'身份运行。 如果该参数配置为禁止，并且服务仍以root身份启动，服务会切换到使用 'zabbix'用户启动 。 对于以普通用户启动的，该参数没有影响。 0 - 禁止 1 - 允许 Zabbix 2.2.0。以后的版本都支持这个参数 |
||
| AllowRoot | no | 0 | Allow the 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. 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, item and trigger data. Upper limit used to be 2GB before Zabbix 2.2.3. |
| CacheUpdateFrequency | 否 | -3600 | 0 | abbix 缓存更新频率, 单位为秒. 另外参考 runtime control 选项。 |
| CacheUpdateFrequency | no | 1-3600 | 60 | How often Zabbix will perform update of configuration cache, in seconds. See also runtime control options. |
| 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 | 是 | 据库名称。 | ||
| DBName | yes | Database name. | ||
| DBPassword | 否 | 据库登录密码。 如果数据库没有密码，请注释掉此参数。 |
||
| DBPassword | no | Database password. Comment this line if no password is used. |
||
| DBPort | 否 | 024-65535 | 地套接字链接时不使用该参数。 | |
| DBPort | no | 1024-65535 | Database port when not using local socket. | |
| DBSchema | 否 | 据库Schema 名字。仅IBM DB2 和 PostgreSQL使用。 | ||
| DBSchema | no | Schema name. Used for IBM DB2 and PostgreSQL. | ||
| DBSocket | 否 | ySQL套接字文件的路径。 | ||
| DBSocket | no | Path to MySQL socket file. | ||
| DBUser | 否 | 据库用户名。 | ||
| DBUser | no | Database user. | ||
| DebugLevel | 否 | -5 | 定调试等级: 0 - Zabbix进程的起停基本信息 1 - 重要信息 2 - 错误信息 3 - 警告信息 4 - 调试信息 (产生大量信息) 5 - 扩展调试 (产生更多信息) 另外可参考 runtime control 选项。 |
|
| 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) See also runtime control options. |
| ExportDir | 否 | 换行符分隔的JSON格式实时导出事件, 历史数据和趋势数据到这个目录。如果设置，则启用实时导出数据到这个目录。 此参数从Zabbix 4.0.0开始支持。 |
||
| ExportDir | no | Directory for real-time export of events, history and trends in newline-delimited JSON format. If set, enables real-time export. This parameter is supported since Zabbix 4.0.0. |
||
| ExportFileSize | 否 | M-1G | G | 个导出文件的最大限制，单位为字节。仅当ExportDir参数设置后才使用。 此参数从Zabbix 4.0.0开始支持。 |
| ExportFileSize | no | 1M-1G | 1G | Maximum size per export file in bytes. Only used for rotation if ExportDir is set. This parameter is supported since Zabbix 4.0.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! |
|
| 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. |
| HistoryStorageDateIndex | 否 | 用历史数据预处理，可以将数据存储到不同的基于时间的索引: 0 - 禁止 1 - 允许 |
||
| HistoryStorageDateIndex | no | 0 | Enable preprocessing of history values in history storage to store values in different indices based on date: 0 - disable 1 - enable |
|
| HistoryStorageURL | 否 | 史数据存储 HTTP[S] URL。 这个参数参考 Elasticsearch进行配置。 |
||
| HistoryStorageURL | no | History storage HTTP[S] URL. This parameter is used for Elasticsearch setup. |
||
| HistoryStorageTypes | 否 | int,dbl,str,log,text | 逗号分隔的列表配置哪些类型的历史数据需要存储到Elasticsearch。 这个参数参考 Elasticsearch 进行配置。 |
|
| HistoryStorageTypes | no | uint,dbl,str,log,text | Comma separated list of value types to be sent to the history storage. This parameter is used for Elasticsearch setup. |
|
| 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 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. 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. See also runtime control options. |
| 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 server startup. Modules are used to extend functionality of the server. 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 server 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. |
| 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. |
| MaxHousekeeperDelete | 否 | -1000000 | 000 | 个housekeeping周期内，一个任务删除的最大行数 （相应的表名，字段名，值）。 如果设置为0，不限制删除的行数，这种情况，你必须清楚这样做的影响! 从Zabbix 1.8.2 开始支持该参数，仅在对已经被删除的监控项进行历史和趋势数据删除操作时有效。 |
| MaxHousekeeperDelete | no | 0-1000000 | 5000 | No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value]) will be deleted per one task in one housekeeping cycle. If set to 0 then no limit is used at all. In this case you must know what you are doing! This parameter is supported since Zabbix 1.8.2 and applies only to deleting history and trends of already deleted items. |
| PidFile | 否 | tmp/zabbix_server.pid | ID文件名称。 | |
| PidFile | no | /tmp/zabbix_server.pid | Name of PID file. | |
| ProxyConfigFrequency | 否 | -604800 | 600 | abbix server 多少秒向Zabbix proxy 发送一次配置数据，用于被动模式的proxy 。 从Zabbix 1.8.3开始支持该参数。 |
| ProxyConfigFrequency | no | 1-604800 | 3600 | How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode. This parameter is supported since Zabbix 1.8.3. |
| ProxyDataFrequency | 否 | -3600 | abbix server 多少秒向Zabbix proxy请求一次历史数据， 用于被动模式的proxy。\\从Zabbix 1.8.3开始支持该参数。 | |
| ProxyDataFrequency | no | 1-3600 | 1 | How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode. This parameter is supported since Zabbix 1.8.3. |
| 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 server. 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. |
||
| 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. |
||
| SSLCALocation | 否 | SSL服务器证书验证覆盖证书颁发机构(CA)文件的位置。如果不设置，系统范围的目录将被使用。 注意，这个参数的值将被设置为libcurl选项curloptcapath， 在7.42.0之前的libcurl版本中，只有使用OpenSSL编译libcurl才会有效。 更多信息见 cURL 网页. 这个参数从Zabbix 2.4.0开始的web监控和自从Zabbix 3.0.0开始的SMTP身份验证中使用。 |
||
| SSLCALocation | no | Override 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 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. |
| StartAlerters | 否 | -100 | 警进程的初始实例数量。 从Zabbix 3.4.0开始支持该参数。 |
|
| StartAlerters | no | 1-100 | 3 | Number of pre-forked instances of alerters. This parameter is supported since Zabbix 3.4.0. |
| 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. |
| StartEscalators | 否 | -100 | scalators进程的初始实例数量。 从Zabbix 3.0.0开始支持该参数。 |
|
| StartEscalators | no | 1-100 | 1 | Number of pre-forked instances of escalators. This parameter is supported since Zabbix 3.0.0. |
| StartHTTPPollers | 否 | -1000 | TTP 轮询进程的初始实例数量。 在Zabbix 1.8.5版本之前，最大能设置为255。 |
|
| StartHTTPPollers | no | 0-1000 | 1 | Number of pre-forked instances of HTTP pollers1. The upper limit used to be 255 before version 1.8.5. |
| 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 pollers1. 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 pingers1. 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)1. 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 | 询进程的初始实例数量。\\注意如果要内部，聚合，计算的监控项能正常工作，这个参数值必须大于0。 | |
| StartPollers | no | 0-1000 | 5 | Number of pre-forked instances of pollers1. Note that a non-zero value is required for internal, aggregated and calculated items to work. |
| StartPreprocessors | 否 | -1000 | 处理工作进程的初始实例数量。\\预处理管理进程将跟随预处理工作进程启动。 从Zabbix 3.4.0开始支持该参数。 |
|
| 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 3.4.0. |
| StartProxyPollers | 否 | -250 | 动proxy的轮询进程初始实例数量。\\在Zabbix 1.8.5版本之前，最大能设置为255。 从Zabbix 1.8.3开始支持该参数。 |
|
| StartProxyPollers | no | 0-250 | 1 | Number of pre-forked instances of pollers for passive proxies1. The upper limit used to be 255 before version 1.8.5. This parameter is supported since Zabbix 1.8.3. |
| 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. |
| StartTimers | 否 | -1000 | 时器进程的初始实例数量。 计时器进程处理基于时间的触发器和维护期功能。 只有第一个计时器进程处理维护期。 从Zabbix 2.2.0开始支持该参数。 |
|
| StartTimers | no | 1-1000 | 1 | Number of pre-forked instances of timers. Timers process time-based trigger functions and maintenance periods. Only the first timer process handles the maintenance periods. This parameter is supported since Zabbix 2.2.0. |
| StartTrappers | 否 | -1000 | rapper进程的初始实例数量。 Trapper接收来自Zabbix发送者、主动agent和主动proxies的数据。 至少要运行一个trapper进程用于在web前端展示服务器可用性和队列视图。 在Zabbix 1.8.5版本之前，最大能设置为255。 |
|
| StartTrappers | no | 0-1000 | 5 | Number of pre-forked instances of trappers1. Trappers accept incoming connections from Zabbix sender, active agents and active proxies. At least one trapper process must be running to display server availability and view queue in the frontend. 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). |
| 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 server certificate or certificate chain, used for encrypted communications between Zabbix components. 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 server private key, used for encrypted communications between Zabbix components. 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. |
| TrendCacheSize | 否 | 28K-2G | M | 势数据缓存大小，单位字节。 用于存储趋势数据的共享内存大小。 |
| TrendCacheSize | no | 128K-2G | 4M | Size of trend cache, in bytes. Shared memory size for storing trends data. |
| 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. |
| 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. |
|
| ValueCacheSize | 否 | ,128K-64G | M | 史数据缓存大小, 单位为字节。 0即禁止缓存 (不建议). 当缓存大小超过共享内存时，每5分钟会向服务器日志写入一条警告信息。 从 Zabbix 2.2.0开始支持该参数。 |
| ValueCacheSize | no | 0,128K-64G | 8M | Size of history value cache, in bytes. Shared memory size for caching item history data requests. Setting to 0 disables value cache (not recommended). When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes. This parameter is supported since Zabbix 2.2.0. |
| 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 |
附注
Footnotes
(1) 请注意，大量的数据收集进程（pollers, unreachable pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers）加上IPMI管理程序，SNMP trapper和预处理程序可能使预处理管理器的进程超过其文件描述符的限制。这将会引起Zabbix server停止服务（通常启动后很快会出现，但有时候可能需要很长时间才出现）。应修改Zabbix配置文件或提高进程文件描述符限制来避免这种情况。
(1) Note that too many data gathering processes (pollers, unreachable pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers) together with IPMI manager, SNMP trapper and preprocessing workers can exhaust the per-process file descriptor limit for the preprocessing manager. This will cause Zabbix server to stop (usually shortly after the start, but sometimes it can take more time). The configuration file should be revised or the limit should be raised to avoid this situation.
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.