Zabbix的配置文件一般有三种：

  • zabbix_server.conf：zabbix server的配置文件
  • zabbix_proxy.conf：zabbix proxy的配置文件
  • zabbix_agentd.conf：zabbix agentd的配置文件

Zabbix安装完成后，服务端默认的配置文件存在安装文件夹中的etc目录中，假设编译的参数是“--prefix=/usr/local/zabbix”，那么服务端的配置文件则保存在“/usr/loca/zabbix/etc/”目录下。zabbix_server.conf参数除了保证服务正常运行外，还会影响服务器的性能。如果参数设定不合理可能会导致zabbix添加主机不正常、代理端数据无法正常收集或是zabbix服务器性能严重下降，经常报告CPU占用过高或是IO占用过高等问题。本文说明了zabbix server的配置文件中的通用参数和大部分高级参数的具体用法，内容如下：

############ 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地址。

#

# Mandatory: no

# Default:

# SourceIP=

### Option: LogType

#       Specifies where log messages are written to://zabbix的日志类型

#               system  - syslog //写入到系统日志

#               file    - file specified with LogFile parameter //写入到指定文件

#               console - standard output //写入到标准输出

#

# Mandatory: no

# Default:

# LogType=file

### Option: LogFile

#       Log file name for LogType 'file' parameter.

//日志文件的存储路径

#

# Mandatory: no

# Default:

# LogFile=

LogFile=/tmp/zabbix_server.log

### Option: LogFileSize

#       Maximum size of log file in MB.

#       0 - disable automatic log rotation.

//指定日志文件的大小，单位MB。0表示禁用日志轮转

#

# Mandatory: no

# Range: 0-1024

# Default:

# LogFileSize=1

### Option: DebugLevel

#       Specifies debug level: //指定debug级别

#       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)

#

# 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，mysql必须用socket来连接，否则用ip来连接。若该参数为空，默认连接PostgreSQL

#

# Mandatory: no

# Default:

# DBHost=localhost

### Option: DBName

#       Database name.

#       For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.

//数据库名。对SQLite3来说，必须提供数据文件的路径，DBUser和DBPassword参数可忽略

#

# Mandatory: yes

# Default:

# DBName=

### Option: DBSchema

#       Schema name. Used for IBM DB2 and PostgreSQL.

//模式名。用于DB2或PostgreSQL数据库

#

# Mandatory: no

# Default:

# DBSchema=

### Option: DBUser

#       Database user. Ignored for SQLite.

//连接数据库的用户名，SQLite忽略该参数

#

# Mandatory: no

# Default:

# DBUser=

### Option: DBPassword

#       Database password. Ignored for SQLite.

#       Comment this line if no password is used.

//连接数据库的密码，SQLite忽略该参数

#

# Mandatory: no

# Default:

# DBPassword=

### Option: DBSocket

#       Path to MySQL socket.

//socket文件的路径

#

# Mandatory: no

# Default:

# DBSocket=/tmp/mysql.sock

### Option: DBPort

#       Database port when not using local socket. Ignored for SQLite.

//数据库监听端口，SQLite忽略该参数

#

# Mandatory: no

# Range: 1024-65535

# Default (for MySQL):

# DBPort=3306

############ ADVANCED PARAMETERS ################

### Option: StartPollers

#       Number of pre-forked instances of pollers.

//系统初始化时，预分配子进程数量。数量越多，则服务端吞吐能力越强，对系统资源消耗越大。

#

# Mandatory: no

# Range: 0-1000

# Default:

# StartPollers=5

### Option: StartIPMIPollers

#       Number of pre-forked instances of IPMI pollers.

//系统初始化时，预分配的使用ipmi协议获取主机硬件状态的进程数量。

#

# 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.

//系统初始化时，预分配用于探测某些不可达主机的（含IPMI、JAVA）的进程数量；若使用场景中含有代理端，建议保持默认；若Agent较多，可视具体情况调整。

#

# 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.

//系统初始化时，预分配的用于接收zabbix sender提交来数据的进程。

#

# Mandatory: no

# Range: 0-1000

# Default:

# StartTrappers=5

### Option: StartPingers

#       Number of pre-forked instances of ICMP pingers.

//系统初始化时，预分配的icmp ping进程的数量。若单台代理所管理机器超过500台，建议加大此数值

#

# Mandatory: no

# Range: 0-1000

# Default:

# StartPingers=1

### Option: StartDiscoverers

#       Number of pre-forked instances of discoverers.

//系统初始化时，预分配的自动发现主机的线程数量。若单台代理所管理机器超过500台，可以考虑加大此数值（仅适用于AGENT场景）

#

# Mandatory: no

# Range: 0-250

# Default:

# StartDiscoverers=1

### Option: StartHTTPPollers

#       Number of pre-forked instances of HTTP pollers.

//系统预分配的用于设置WEB监控进程数，可视具体情况增加或减少此数值。

#

# 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.

//各实例计时器数量

#

# Mandatory: no

# Range: 1-1000

# Default:

# StartTimers=1

### Option: StartEscalators

#       Number of pre-forked instances of escalators.

#

# Mandatory: no

# Range: 0-100

# Default:

# StartEscalators=1

### Option: StartVMwareCollectors

#       Number of pre-forked vmware collector instances.

//用于监控VMWARE Esxi主机实例的进程数量，为0则不启用，若要监控ESXI主机，此值最少为1 ；视监控ESXI数量设置对应数值

#

# Mandatory: no

# Range: 0-250

# Default:

# StartVMwareCollectors=0

### Option: VMwareFrequency

#       How often Zabbix will connect to VMware service to obtain a new data.

//Zabbix连接WMware service获取新数据的频率

#

# Mandatory: no

# Range: 10-86400

# Default:

# VMwareFrequency=60

### Option: VMwarePerfFrequency

#       How often Zabbix will connect to VMware service to obtain performance data.

#

# 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数据的共享内存

#

# Mandatory: no

# Range: 256K-2G

# Default:

# VMwareCacheSize=8M

### Option: VMwareTimeout

#       Specifies how many seconds vmware collector waits for response from VMware service.

#

# Mandatory: no

# Range: 1-300

# Default:

# VMwareTimeout=10

### Option: SNMPTrapperFile

#       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.

#

# Mandatory: no

# Default:

# SNMPTrapperFile=/tmp/zabbix_traps.tmp

### Option: StartSNMPTrapper

#       If 1, SNMP trapper process is started.

//是否启用snmptrapper功能 ，默认不启用=0，启用=1

#

# 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.

#

# Mandatory: no

# Default:

# ListenIP=0.0.0.0

# ListenIP=127.0.0.1

### 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!

//housekeeping一次删除的数据不能大于MaxHousekeeperDelete

#

# Mandatory: no

# Range: 0-1000000

# Default:

# MaxHousekeeperDelete=5000

### Option: SenderFrequency

#       How often Zabbix will try to send unsent alerts (in seconds).

//指定间隔多少秒后，再尝试发送为发送的报警

#

# 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.

//分配多少共享内存用于存储配置信息，HOST,ITEM,TRIGGER数据，视监控主机数量和监控项调整，建议调整到32M或者更大，2.2.3版本之前最大支持2G，目前最大支持8G，一般用不了多少。

#

# Mandatory: no

# Range: 128K-8G

# Default:

# CacheSize=8M

### Option: CacheUpdateFrequency

#       How often Zabbix will perform update of configuration cache, in seconds.

//更新系统CACHE频率，若管理页面操作不频繁，可以考虑加大参数值

#

# Mandatory: no

# Range: 1-3600

# Default:

# CacheUpdateFrequency=60

### Option: StartDBSyncers

#       Number of pre-forked instances of DB Syncers.

//将采集数据从CACHE同步到数据库线程数量，视数据库服务器I/O繁忙情况，和数据库写能力调整。数值越大，写能力越强。对数据库服务器I/O压力越大。

#

# 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.

//0表示禁用，history value缓存大小，当缓存超标了，将会每隔5分钟往server日志里面记录。

#

# 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). 
//与AGNET、SNMP设备和其它外部设备通信超时设置，单位为秒；若采集数据不完整或网络繁忙，或从管理页面发现客户端状态变化频繁，可以考虑加大此数值。注意若此数值加大，应该考虑参数StartPollers 是否有相应加大的必要。

#

# Mandatory: no

# Range: 1-30

# Default:

# Timeout=3

### Option: TrapperTimeout

#       Specifies how many seconds trapper may spend processing new data.

//启用trapper功能，用于进程等待超时设置。

#

# Mandatory: no

# Range: 1-300

# Default:

# TrapperTimeout=300

### Option: UnreachablePeriod

#       After how many seconds of unreachability treat a host as unavailable.

//当Agent端处于不可用状态下，间隔多少秒后，尝试重新连接。建议根据具体情况设置。注意，若此数值过小，若Agent端业务系统繁忙时，有可能造成报警误报

#

# Mandatory: no

# Range: 1-3600

# Default:

# UnreachablePeriod=45

### Option: UnavailableDelay

#       How often host is checked for availability during the unavailability period, in seconds. 
//当Agent端处于不可用状态下，间隔多少秒后，进行状态检查。若出现可正常采集数据，但管理页面AGENT状态不正常、或在网络，端口等均通畅情况下，AGENT状态仍不正常，可以考虑加大此数值

#

# Mandatory: no

# Range: 1-3600

# Default:

# UnavailableDelay=60

### Option: UnreachableDelay

#       How often host is checked for availability during the unreachability period, in seconds.

//当Agent端处于不可达状态下，延迟多少秒后，进行重新尝试，建议保持默认，在AGENT接入调试阶段，可考虑减少此数值

#

# Mandatory: no

# Range: 1-3600

# Default:

# UnreachableDelay=15

### Option: AlertScriptsPath

#       Full path to location of custom alert scripts.

#       Default depends on compilation options.

//自定义告警脚本存放全路径

#

# Mandatory: no

# Default:

# AlertScriptsPath=${datadir}/zabbix/alertscripts

### 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.

//用于服务端数据库慢查询功能，单位是毫秒。若有服务端数据库监控慢查询的需求，可以视具体情况调整此数。

#

# Mandatory: no

# Range: 1-3600000

# Default:

# LogSlowQueries=0

### Option: TmpDir

#       Temporary directory.

//指定临时目录路径

#

# Mandatory: no

# Default:

# TmpDir=/tmp

### Option: StartProxyPollers

#       Number of pre-forked instances of pollers for passive proxies.

//启用多少子进程与代理端通信，若代理端较多可考虑加大此数值

#

# 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服务端将配置文件数据同步到代理端的频率，仅适用于代理端为被动模式情况

#

# 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服务端请求代理端采集的数据的频率，仅适用代理端为被动模式情况

#

# 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身份运行服务端

#

# 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.

//启动zabbix server的用户，在配置禁止root启动，并且当前shell用户是root得情况下有效。如果当前用户是abc，那么zabbix server的运行用户是abc

#

# 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.

//某些情况下，软件的参数配置文件很长，为了方便管理，将配置文件切割成N个配置文件，但为了主配置参数文件的简洁，便会启用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

Zabbix Server参数文件详解的更多相关文章

  1. server.properties 文件详解

    [转载]:server.properties 文件详解 # 每一个Broker在集群中的唯标识.即使Broker的IP地址发生了变化,broker.id只要没变,则不会影响consumers的消息情况 ...

  2. server.xml文件详解

    一.server.xml文件介绍 1.server.xml作用     Server.xml配置文件用于对整个容器进行相关的配置. 2.server.xml文件的配置元素列表 <Server&g ...

  3. Tomcat 的 server.xml 文件详解

    文件内容解读 <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apac ...

  4. VSFTPD全攻略（/etc/vsftpd/vsftpd.conf文件详解）

    /etc/vsftpd/vsftpd.conf文件详解,分好类,方便大家查找与学习 #################匿名权限控制############### anonymous_enable=YE ...

  5. /etc/inittab文件详解

    /etc/inittab由/sbin/init程序解析调用,用于系统初始化,/sbin/init可参考源码busybox中init.c的实现方式. 原址如下: http://leejia.blog.5 ...

  6. Angular Npm Package.Json文件详解

    Angular7 Npm Package.Json文件详解   近期时间比较充裕,正好想了解下Angular Project相关内容.于是将Npm官网上关于Package.json的官方说明文档进行了 ...

  7. Linux下inittab文件详解

    /etc/inittab文件详解 Linux系统的启动过程为:加电自检-->根据BIOS中的设置从指定的设备启动-->找到设备MBR中的bootloader引导启动系统-->启动ke ...

  8. C#中web.config文件详解

    C#中web.config文件详解 一.认识Web.config文件 Web.config 文件是一个XML文本文件,它用来储存 ASP.NET Web 应用程序的配置信息(如最常用的设置ASP.NE ...

  9. vue-cli生成的模板各个文件详解（转）

    vue-cli脚手架中webpack配置基础文件详解 一.前言 原文:https://segmentfault.com/a/1190000014804826 vue-cli是构建vue单页应用的脚手架 ...

随机推荐

  1. 3.2.1.1 POSIX方括号表达式

        为配合非英语的环境,POSIX 标准强化其字符集范围的能力(例如,[a-z]),以匹配非英文字母字符.       POSIX 也在一般术语上作了些变动,我们早先看到的范围表达式在 UNIX  ...

  2. type="timestamp"与type="date"区别

    type="timestamp"-----数据库中保存的时间为年月日时分秒 与type="date"---------数据库中保存的时间为年月日

  3. CodeForces 220B(B. Little Elephant and Array)

    http://codeforces.com/contest/220/problem/B 题意:给出一个数组,给出m组询问,问区间中出现a[i] 次的有多少个. sl: 很显然的离线问题了. 大视野菜花 ...

  4. Ubuntu 16.04安装WPS

    1.下载 http://community.wps.cn/download/ 根据需要对应版本进行下载deb包. 2.安装 sudo dpkg -i wps-office_10.1.0.5672~a2 ...

  5. 桦仔------分享一下我研究SQLSERVER以来收集的笔记

    http://www.cnblogs.com/lyhabc/p/3219117.html

  6. mysql bin-log 设置

    mysql 的事物日至为 [root@localhost mysql]# ls -ldtr mysql-bin.* -rw-rw---- mysql mysql 4月 : mysql-bin. -rw ...

  7. Java深入浅出系列（四）——深入剖析动态代理--从静态代理到动态代理的演化

    静态代理 如上图,在程序执行之前.程序猿就要编写Proxy.然后进行编译,即在程序执行之前,代理类的字节码文件就已经生成了(Proxy类的class文件已经存在了). 静态代理尽管在增强现有的接口业务 ...

  8. vue—你必须知道的 js数据类型 前端学习 CSS 居中 事件委托和this 让js调试更简单—console AMD && CMD 模式识别课程笔记（一） web攻击 web安全之XSS JSONP && CORS css 定位 react小结

    vue—你必须知道的   目录 更多总结 猛戳这里 属性与方法 语法 计算属性 特殊属性 vue 样式绑定 vue事件处理器 表单控件绑定 父子组件通信 过渡效果 vue经验总结 javascript ...

  9. Spark SQL Catalyst源代码分析之UDF

    /** Spark SQL源代码分析系列文章*/ 在SQL的世界里,除了官方提供的经常使用的处理函数之外.一般都会提供可扩展的对外自己定义函数接口,这已经成为一种事实的标准. 在前面Spark SQL ...

  10. Android 自己定义UI圆角button

    Android实际开发中我们一般须要圆角的button,普通情况下我们能够让美工做出来对应的button图片.然后放上去就可以,另外我们能够在布局文件里直接设置,也能够达到一样的效果. 以下解说在布局 ...