############ GENERAL PARAMETERS #################
### Option: ListenPort
# Listen port for trapper.# 服务端监听端口,用于接收二级代理Proxy或直连AGENT的采集数据# Mandatory: no# Range: 1024-32767# Default:# ListenPort=10051
### Option: SourceIP
# Source IP address for outgoing connections.# 对外连接的源IP地址,即使用哪个IP地址向外发起连接(zabbix_get)# Mandatory: no# Default:# SourceIP=
### Option: LogType
# Specifies where log messages are written to:# system - syslog# file - file specified with LogFile parameter# console - standard output# 日志输出类型:# file - 写入LogFile 参数指定的日志文件中,# system - 写入Windows事件日志,# console - 控制台输出.Zabbix 3.0.0后支持该参数# Mandatory: no# Default:# LogType=file
### Option: LogFile
# Log file name for LogType 'file' parameter.# zabbix服务端日志路径,LogType的类型必须是file# Mandatory: no# Default:# LogFile=LogFile=/var/log/zabbix/zabbix_server.log
### Option: LogFileSize
# Maximum size of log file in MB.# 0 - disable automatic log rotation.# 日志达到多少M就轮替;若此参数值为0时,则不轮转,日志将不断变大,建议设置成轮转(注意: 如果日志文件达到限定的大小,文件轮替失败, 不管是什么原因, 现有的日志会被截断,并重新记录日志.)# Mandatory: no# Range: 0-1024# Default:# LogFileSize=1
### Option: DebugLevel
# 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)# 指定调试等级: 0 - Zabxxi进程起停的基本信息 1 - 重要信息 2 - 错误信息 3 - 警告信息 4 - 调试 (产生大量信息) 5 - 扩展调试 (产生更多信息)# Mandatory: no# Range: 0-5# Default:# DebugLevel=3
### Option: PidFile
# Name of PID file.# PID文件保存的全路径# Mandatory: no# Default:# PidFile=/tmp/zabbix_server.pid
### Option: DBHost
# Database host name.# If set to localhost, socket is used for MySQL.# If set to empty string, socket is used for PostgreSQL.# 数据库主机名.如果是 localhost 或 空字符串会使用 socket. 如果是 PostgreSQL只有空字符串会使用 socket.# Mandatory: no# Default:DBHost=127.0.0.1
### Option: DBName
# Database name.# For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.# 数据库名称.对于 SQLite3 必须提供数据库文件路径. 数据库用户名和密码可以忽略.# Mandatory: yes# Default:# DBName=DBName=zabbix
### Option: DBSchema
# Schema name. Used for IBM DB2 and PostgreSQL.# Schema名字. IBM DB2 和 PostgreSQL使用# Mandatory: no# Default:# DBSchema=
### Option: DBUser
# Database user. Ignored for SQLite.# 数据库用户名,SQLite忽略该参数# Mandatory: no# Default:# DBUser=DBUser=zabbix
### Option: DBPassword
# Database password. Ignored for SQLite.# Comment this line if no password is used.# 与上述数据库用户对应的登录密码# Mandatory: no# Default:DBPassword=zabbix
### Option: DBSocket
# Path to MySQL socket.# MySQL socket的路径。# Mandatory: no# Default:DBSocket=/tmp/mysql.sock
### Option: DBPort
# Database port when not using local socket. Ignored for SQLite.# 当不使用本地socket时,所使用的数据库端口,SQLite忽略该参数# Mandatory: no# Range: 1024-65535# Default (for MySQL):# DBPort=3306
############ ADVANCED PARAMETERS(高级参数) ################
### Option: StartPollers
# Number of pre-forked instances of pollers.# 初始化启动时,启动子进程轮询器的数量,数量越多,则服务端吞吐能力越强,对系统资源消耗越大(在版本1.8.5之前,上限是255)# Mandatory: no# Range: 0-1000# Default:# StartPollers=5
### Option: StartIPMIPollers
# Number of pre-forked instances of IPMI pollers.# 初始化启动时,启动IPMI子进程轮询器的数量,数量越多,则服务端吞吐能力越强,对系统资源消耗越大 , 主要用于IPMI技术用于获取硬件状态场景。若无相关监控项,建议设置为0在版本1.8.5之前,上限是255)# 如果使用IPMI监控agent,这里必须至少启动一个轮询器# Mandatory: no# Range: 0-1000# Default:# StartIPMIPollers=0
### Option: StartPollersUnreachable
# 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.# 默认情况下,ZABBIX会启用指定进程用于探测某些不可到达主机(含IPMI和Java场景);若使用场景中含有代理端,建议保持默认!!!若直接agent较多,可视具体情况调整从Zabbix 2.4.0开始,如果有常规的(agent或snmp)、IPMI或Java轮询器启动,那么至少有一个针对不可访问主机的轮询器必须运行!!!!(在版本1.8.5之前,上限是255。这个参数在Zabbix 1.8.3之后得到了支持)# Mandatory: no# Range: 0-1000# Default:# StartPollersUnreachable=1
### Option: StartTrappers
# Number of pre-forked instances of trappers.# 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.# Trappers接受来自Zabbix sender、主动agents和主动proxies的传入连接。 至少要运行一个trapper进程来显示前端的服务器可用性和视图队列!!!!# Mandatory: no# Range: 0-1000# Default:# StartTrappers=5
### Option: StartPingers
# Number of pre-forked instances of ICMP pingers.# ICMP pingers进程实例数量。单台代理所管理机器超过500台,建议加大此数值!!!! 1.8.5以前最大数值为255# Mandatory: no# Range: 0-1000# Default:# StartPingers=1
### Option: StartDiscoverers
# Number of pre-forked instances of discoverers.# 设置用于自动发现主机的线程数量,若单台代理所管理机器超过500台,可以考虑加大此数值(仅适用于直接AGENT场景)!!!! 1.8.5以前最大数值为255# Mandatory: no# Range: 0-250# Default:# StartDiscoverers=1
### Option: StartHTTPPollers
# Number of pre-forked instances of HTTP pollers.# HTTP 轮询器子进程实例个数,1.8.5以前最大数值为255# Mandatory: no# Range: 0-1000# Default:# StartHTTPPollers=1
### Option: StartTimers
# 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.# 计时器子进程实例数量,计时器处理基于时间的触发器函数和维护周期 主要用于触发器,标有维护标识的主机,但只第一个计时器用于计算维护标识主机 这个参数在Zabbix 2.2.0之后得到了支持# Mandatory: no# Range: 1-1000# Default:# StartTimers=1
### Option: StartEscalators
# Number of pre-forked instances of escalators.# 检查Escalations的进程,这张表好像是告警事件表# Mandatory: no# Range: 0-100# Default:# StartEscalators=1### Option: JavaGateway# IP address (or hostname) of Zabbix Java gateway.# Only required if Java pollers are started.# Zabbix JAVA 网关的IP地址或主机名,只有当Java轮询器进程启动才需要该参数# Mandatory: no# Default:# JavaGateway=
### Option: JavaGatewayPort
# Port that Zabbix Java gateway listens on.# zabbix java网关监听的端口# Mandatory: no# Range: 1024-32767# Default:# JavaGatewayPort=10052
### Option: StartJavaPollers
# Number of pre-forked instances of Java pollers.# java轮询器预启动的进程数# Mandatory: no# Range: 0-1000# Default:# StartJavaPollers=0### Option: StartVMwareCollectors# Number of pre-forked vmware collector instances.# 用于设置监控VMWARE Esxi主机实例时使用,若为0则不启用,若要监控ESXI主机,此值最少为1 ;视监控ESXI数量设置对应数值!!!!# StartVMwareCollectors=0# Mandatory: no# Range: 0-250# Default:# StartVMwareCollectors=0
### Option: VMwareFrequency
# How often Zabbix will connect to VMware service to obtain a new data.# 代理端访问 VMWARE service的频率(官方:在单个VMware服务的数据收集之间延迟几秒)。此延迟应该设置为任一VMware监视项的最小更新间隔(单位:秒)。这个参数在Zabbix 2.2.0之后得到了支持# Mandatory: no# Range: 10-86400# Default:# VMwareFrequency=60
### Option: VMwarePerfFrequency
# How often Zabbix will connect to VMware service to obtain performance data.# 多久agent Zabbix会连接到VMware的服务来获取性能数据。该延迟应该设置为任一VMware监控的监控项(使用VMware性能计数器)最小更新间隔。 Zabbix 2.2.9, 2.4.4后支持该参数# Mandatory: no# Range: 10-86400# Default:# VMwarePerfFrequency=60
### Option: VMwareCacheSize
# Size of VMware cache, in bytes.# Shared memory size for storing VMware data.# Only used if VMware collectors are started.# 存储VMware数据的共享内存大小。 VMware内部检查[vmware,buffer,…] 可以用来监控VMware缓存使用情况,只有当VMare collector启动时才使用使用该参数 (参考:内部检查)注意:如果没有配置好启动的vmware收集器实例,那么共享内存就不会被分配。\\这个参数在Zabbix 2.2.0之后得到了支持# Mandatory: no# Range: 256K-2G# Default:# VMwareCacheSize=8M
### Option: VMwareTimeout
# Specifies how many seconds vmware collector waits for response from VMware service.# 指定VMware收集器从VMware服务等待响应的秒数。vmware采集器等等 VMware 服务(vCenter or ESX 管理程序)响应的最大时长.Zabbix 2.2.9, 2.4.4后支持该参数# Mandatory: no# Range: 1-300# Default:# VMwareTimeout=10### Option: SNMPTrapperFile# Temporary file used for passing data from SNMP trap daemon to the server.
#用户从SNMP trap守护程序传递数据到zabbix server的临时文件
# Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.#文件路径必须与zabbix_trap_receiver.pl脚本或SNMPTT配置文件中相同# Mandatory: no# Default:# SNMPTrapperFile=/tmp/zabbix_traps.tmp
### Option: StartSNMPTrapper
# If 1, SNMP trapper process is started.# 如果为1,snmp trapper进程被启动# Mandatory: no# Range: 0-1# Default:# StartSNMPTrapper=0### Option: ListenIP# List of comma delimited IP addresses that the trapper should listen on.# Trapper will listen on all network interfaces if this parameter is missing.#说明:zabbix服务监听的Ip地址,多个IP用逗号分开.如果没有该参数,会监听所有网络接口.Zabbix 1.8.3开始支持多Ip地址.即使用哪个IP对外提供服务# Mandatory: no# Default:#ListenIP=0.0.0.0
### Option: HousekeepingFrequency# How often Zabbix will perform housekeeping procedure (in hours).# Housekeeping is removing outdated information from the database.# To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency# hours of outdated information are deleted in one housekeeping cycle, for each item.# To lower load on server startup housekeeping is postponed for 30 minutes after server start.# With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.# In this case 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.# 多少小时清理一次代理端数据库的history, alert, and alarms,以保持代理端数据库轻便,建议保持默认# Mandatory: no# Range: 0-24# Default:# HousekeepingFrequency=1
### Option: MaxHousekeeperDelete
# The table "housekeeper" contains "tasks" for housekeeping procedure in the format:# [housekeeperid], [tablename], [field], [value].# No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])# will be deleted per one task in one housekeeping cycle.# SQLite3 does not use this parameter, deletes all corresponding rows without a limit.# If set to 0 then no limit is used at all. In this case you must know what you are doing!# 每次最多删除历史数据的行数# Mandatory: no# Range: 0-1000000# Default:# MaxHousekeeperDelete=5000### Option: SenderFrequency# How often Zabbix will try to send unsent alerts (in seconds).# Zabbix重新发送失败报警的频率 (单位秒).# Mandatory: no# Range: 5-3600# Default:# SenderFrequency=30
### Option: CacheSize
# Size of configuration cache, in bytes.# Shared memory size for storing host, item and trigger data.# 用于存储主机、监控项、触发器数据的共享内存大小.Zabbix2.2.3版本前最大可配置值为2GB# Mandatory: no# Range: 128K-8G# Default:CacheSize=8M
### Option: CacheUpdateFrequency
# How often Zabbix will perform update of configuration cache, in seconds.# Zabbix缓存更新频率, 单位秒.# Mandatory: no# Range: 1-3600# Default:# CacheUpdateFrequency=60
### Option: StartDBSyncers
# Number of pre-forked instances of DB Syncers.# 数据库同步实例数# Mandatory: no# Range: 1-100# Default:# StartDBSyncers=4### Option: HistoryCacheSize# Size of history cache, in bytes.# Shared memory size for storing history data.# 历史缓存大小,存储历史数据的共享缓存大小# Mandatory: no# Range: 128K-2G# Default:# HistoryCacheSize=16M
### Option: HistoryIndexCacheSize
#Size of history index cache, in bytes.#Shared memory size for indexing history cache.# 历史索引缓存大小,历史索引缓存共享内存# Mandatory: no# Range: 128K-2G# Default:# HistoryIndexCacheSize=4M
### Option: TrendCacheSize
# Size of trend cache, in bytes.# Shared memory size for storing trends data.# 趋势缓存的大小,单位字节。用于存储趋势数据的共享内存大小。# Mandatory: no# Range: 128K-2G# Default:# TrendCacheSize=4M
### Option: ValueCacheSize
# Size of history value cache, in bytes.# Shared memory size for caching item history data requests.# Setting to 0 disables value cache.# 历史值数据缓存大小, 单位bytes.缓存item历史数据请求的共享内存大小.0即禁止缓存 (不建议).当缓存大小超过共享内存时,每5分钟会向服务器日志写入一条警告信息.该参数 Zabbix 2.2.0以后的版本中都支持.# Mandatory: no# Range: 0,128K-64G# Default:# ValueCacheSize=8M
### Option: Timeout
# Specifies how long we wait for agent, SNMP device or external check (in seconds).# Agent, SNMP 设备或外部检查(External check)的超时时长(单位秒)# Mandatory: no# Range: 1-30# Default:# Timeout=3Timeout=30
### Option: TrapperTimeout
# Specifies how many seconds trapper may spend processing new data.# 捕捉器(Zabbix Trapper)处理新数据的最长时间# Mandatory: no# Range: 1-300# Default:# TrapperTimeout=300
### Option: UnreachablePeriod
# After how many seconds of unreachability treat a host as unavailable.# 在多少秒连接不到客户端,即视为客户端主机不可到达# Mandatory: no# Range: 1-3600# Default:# UnreachablePeriod=45
### Option: UnavailableDelay
# How often host is checked for availability during the unavailability period, in seconds.# 在不可用期间,主机多少秒检查一次是否可用# Mandatory: no# Range: 1-3600# Default:# UnavailableDelay=60
### Option: UnreachableDelay
# How often host is checked for availability during the unreachability period, in seconds.# 在不可达期间,主机多少秒检查一次是否可用# Mandatory: no# Range: 1-3600# Default:# UnreachableDelay=15#思考上面的两个选项UnavailableDelay和UnreachableDelay有什么区别????
### Option: AlertScriptsPath# Full path to location of custom alert scripts.# Default depends on compilation options.# 自定义报警脚本位置 (依赖编译安装时的参数设置 datadir).# Mandatory: no# Default:# AlertScriptsPath=${datadir}/zabbix/alertscripts
### Option: ExternalScripts
# Full path to location of external scripts.# Default depends on compilation options.# 外部脚本位置 (依赖编译安装时的变量datadir). 配置External check类型的监控时需要用到该脚本# Mandatory: no# Default:# ExternalScripts=${datadir}/zabbix/externalscripts
### Option: FpingLocation
# Location of fping.# Make sure that fping binary has root ownership and SUID flag set.# fping指令的路径.确保fping的属主是root用户,并且设置了SUID!# Mandatory: no# Default:# FpingLocation=/usr/sbin/fpingFpingLocation=/usr/local/fping/sbin/fping
### Option: Fping6Location
# Location of fping6.# Make sure that fping6 binary has root ownership and SUID flag set.# Make empty if your fping utility is capable to process IPv6 addresses.# fping6指令的路径.确保fping的宿主是root用户,并且设置了SUID!# Mandatory: no# Default:# Fping6Location=/usr/sbin/fping6### Option: SSHKeyLocation# Location of public and private keys for SSH checks and actions.# 用于SSH检查和操作的公钥和私钥的位置(注意,这里仅是路径,不要包含秘钥文件名)# Mandatory: no# Default:# SSHKeyLocation=
### Option: LogSlowQueries
# How long a database query may take before being logged (in milliseconds).# Only works if DebugLevel set to 3, 4 or 5.# 0 - don't log slow queries.# 在记录之前数据库查询可能需要多长时间(以毫秒为单位)。# DebugLevel设置为3,4或5时,才生效!!!!!# 0 不记录慢查询# Mandatory: no# Range: 1-3600000# Default:# LogSlowQueries=0LogSlowQueries=3000
### Option: TmpDir# Temporary directory.# 临时目录# Mandatory: no# Default:# TmpDir=/tmp
### Option: StartProxyPollers# Number of pre-forked instances of pollers for passive proxies.# 被动代理(proxy)的预分派轮询实例的数量# Mandatory: no# Range: 0-250# Default:# StartProxyPollers=1
### Option: ProxyConfigFrequency
# How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.# This parameter is used only for proxies in the passive mode.# Zabbix Server发送配置数据到Zabbix Proxy的频率,单位秒。 此参数仅用于被动模式下的Proxy代理!!!!!# Mandatory: no# Range: 1-3600*24*7# Default:# ProxyConfigFrequency=3600
### Option: ProxyDataFrequency
# How often Zabbix Server requests history data from a Zabbix Proxy in seconds.# This parameter is used only for proxies in the passive mode.# Zabbix Server向Zabbix Proxy请求历史数据的频率,单位秒。此参数仅用于被动模式下的Proxy代理!!!!!!# Mandatory: no# Range: 1-3600# Default:# ProxyDataFrequency=1
### Option: AllowRoot
# Allow the server to run as 'root'. If disabled and the server is started by 'root', the server# will try to switch to the user specified by the User configuration option instead.# Has no effect if started under a regular user.# 0 - do not allow# 1 - allow# 允许服务器以“root”身份运行。如果禁用并且服务器以“root”启动,则服务器将尝试切换到User配置选项指定的用户。如果在普通用户下启动,则不起作用!!!!!# 0 不允许# 1 允许# Mandatory: no# Default:# AllowRoot=0
### Option: User
# Drop privileges to a specific, existing user on the system.# Only has effect if run as 'root' and AllowRoot is disabled.# 降低权限为系统中存在的指定用户。仅当系统以'root'身份运行且AllowRoot=0,即禁止时,该参数才起作用。Zabbix 2.4.0后支持该参数。# Mandatory: no# Default:# User=zabbix
### Option: Include
# You may include individual files or all files in a directory in the configuration file.# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.# 您可以将单个文件或所有文件包含在配置文件的目录中。安装Zabbix将在/usr/local/etc中创建include目录,除非在编译期间进行修改。# Mandatory: no# Default:# Include=# Include=/usr/local/etc/zabbix_server.general.conf
# Include=/usr/local/etc/zabbix_server.conf.d/# Include=/usr/local/etc/zabbix_server.conf.d/*.conf### Option: SSLCertLocation# Location of SSL client certificates# This parameter is used only in web monitoring# SSL客户端证书的位置。此参数仅用于Web监控# Mandatory: no# Default:# SSLCertLocation=${datadir}/zabbix/ssl/certs
### Option: SSLKeyLocation
# Location of private keys for SSL client certificates.# This parameter is used only in web monitoring.# SSL客户端证书的私钥位置。此参数仅用于Web监控。# Mandatory: no# Default:# SSLKeyLocation=${datadir}/zabbix/ssl/keys
### Option: SSLCALocation
# Override the location of certificate authority (CA) files for SSL server certificate verification.# If not set, system-wide directory will be used.# This parameter is used only in web monitoring and SMTP authentication.# 覆盖用于SSL服务器证书验证的证书颁发机构(CA)文件的位置。如果未设置,系统范围的目录将被使用。该参数仅用于Web监控和SMTP认证。# Mandatory: no# Default:# SSLCALocation=####### LOADABLE MODULES #######
### Option: LoadModulePath
# Full path to location of server modules.# Default depends on compilation options.# 服务器模块位置的完整路径。默认取决于编译选项。# Mandatory: no# Default:# LoadModulePath=${libdir}/modules
### Option: LoadModule
# 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.# 在服务器启动时加载模块。模块用于扩展服务器的功能。格式:LoadModule = <module.so>,模块必须位于LoadModulePath指定的目录中。 #允许包含多个LoadModule参数。# Mandatory: no# Default:# LoadModule=
####### TLS-RELATED PARAMETERS #######
### Option: TLSCAFile
# Full pathname of a file containing the top-level CA(s) certificates for# peer certificate verification.# 包含对等证书验证的顶级CA(s)证书的文件的完整路径名。# Mandatory: no# Default:# TLSCAFile=
### Option: TLSCRLFile
# Full pathname of a file containing revoked certificates.# 包含吊销证书的文件的完整路径名。# Mandatory: no# Default:# TLSCRLFile=
### Option: TLSCertFile
# Full pathname of a file containing the server certificate or certificate chain.# 包含服务器证书或证书链的文件的完整路径名。# Mandatory: no# Default:# TLSCertFile=
### Option: TLSKeyFile
# Full pathname of a file containing the server private key.# 包含服务器私钥的文件的完整路径名。# Mandatory: no# Default:# TLSKeyFile=