Zabbix Server parameter file

There are three types of Zabbix profiles in general:

• Zabbix_server.conf:zabbix Server's configuration file
• Configuration file for Zabbix_proxy.conf:zabbix proxy
• Zabbix_agentd.conf:zabbix configuration files for Agentd

Zabbix after the installation is complete, the default configuration file of the server is present in the ETC directory in the installation folder, assuming that the compiled parameter is "--prefix=/usr/local/zabbix", then the server configuration file is saved in the "/usr/loca/zabbix/etc /"directory. The zabbix_server.conf parameter also affects the performance of the server in addition to ensuring that the service is running correctly. If the parameter set unreasonable may cause Zabbix to add the host is not normal, the agent side data does not collect properly or the Zabbix server performance drops seriously, frequently reports the CPU is high or the IO occupies excessively high and so on problems. This article explains the general parameters and the specific usage of most advanced parameters in the configuration file for Zabbix server, as follows:

############ General PARAMETERS #################### option:listenport# Listen port for Trapper. This parameter is used to specify the listener port on the server, which is used to listen for proxy or agent connection requests. # # mandatory:no# range:1024-32767# default:# listenport=10051### option:sourceip# Source IP address for outgoing connections.//This parameter is used to specify the IP address of the server side.                # # mandatory:no# default:# sourceip=### option:logtype# Specifies where log messages is written To://zabbix log type #               System-syslog//write to System log # File-file specified with LogFile parameter//write to specified file # Console-standard output//write to standard outputs # mandatory:no# default:# logtype=file### option:logfile# Log file nam E for logtype ' file ' parameter.//log file storage path # mandatory:no# default:# logfile=logfile=/tmp/zabbix_server.log### Option: logfilesize# Maximum Size of log file in mb.# 0-disable automatic log rotation.//Specifies the size of the log file, in megabytes. 0 means disable log rotation # # mandatory:no# range:0-1024# default:# logfilesize=1### option:debuglevel# Specifies DebuG Level://Specify Debug Levels # 0-basic information about starting and stopping of Zabbix processes//Basic information about process start and stop #  1-critical Information//Key Info # 2-error information//error message # 3-warnings//Warning # 4-for Debugging (produces lots of information)//debug Info # 5-extended Debugging (produces even more information) # # Mandato ry:no# range:0-5# default:# debuglevel=3### option:pidfile# name of PID file.//pid filename # # mandatory:no# Default:#  pidfile=/tmp/zabbix_server.pid### option:dbhost# Database host name.# If set to localhost, socket was used for mysql.# if set to empty string, socket is used for postgresql.//database hostname, if set to Localhost,mysql must be connected with socket, otherwise connect with IP. If this parameter is empty, the default connection postgresql## mandatory:no# default:# dbhost=localhost### option:dbname# Database name.# for Sqlit E3 path to database file must is provided. DBUser and Dbpassword are ignored.//database names. For SQLite3, the path to the data file must be provided, and the Dbuser and Dbpassword parameters can be ignored # # mandatory:yes#default:# dbname=### option:dbschema# Schema name. Used for IBM DB2 and postgresql.//mode name. For DB2 or PostgreSQL database # # mandatory:no# default:# dbschema=### option:dbuser# db user. Ignored for sqlite.//the user name of the connection database, SQLite ignores the parameter # # mandatory:no# default:# dbuser=### option:dbpassword# database Passwo Rd. ignored for sqlite.# Comment the password for the connection database, SQLite ignores the parameter # # used.//mandatory:no# dbpassword=### option:dbsocket# path to MySQL socket.//socket file # # mandatory:no# default:# dbsocket=/tmp/mysql.s ock### option:dbport# Database Port when not using the local socket. Ignored for sqlite.//database listener port, SQLite ignores this parameter # # mandatory:no# range:1024-65535# Default (for MySQL): # dbport=3306########## # # Advanced PARAMETERS ################### option:startpollers# number of pre-forked instances of pollers.//when the system is initialized, The number of pre-allocated child processes. The higher the number, the higher the throughput capacity of the service side, the greater the system resource consumption.      # # mandatory:no# range:0-1000# default:# startpollers=5### option:startipmipollers# Number of pre-forked instances of the IPMI pollers.//system is initialized, the amount of processes that are pre-allocated using the IPMI protocol to obtain host hardware status. # # mandatory:no# range:0-1000# default:# startipmipollers=0### option:startpollersunreachable# number of Pre-fork Ed instances of Pollers for unreachable hosts (including IPMI and Java). In least one poller for unreachable hosts Must be running if regular, IPMI or Java pollers# is started.//the number of processes that are pre-allocated to probe some unreachable hosts (including IPMI, Java) when the system is initialized, and if the usage scenario contains a proxy side, It is recommended to keep the default, if the agent is more, depending on the situation. # # 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 is running to display server availability and view queue# in the frontend. When the system is initialized, the pre-allocated process is used to receive data submitted by Zabbix Sender. # # mandatory:no# range:0-1000# default:# starttrappers=5### option:startpingers# number of pre-forked instances OF ICMP pingers. The number of ICMP ping processes that were pre-allocated when the system was initialized. If the single agent to manage more than 500 machines, it is recommended to increase this value # # mandatory:no# range:0-1000# default:# startpingers=1### option:startdiscoverers# Numbe R of Pre-forked instances of discoverers. The number of threads that are pre-allocated for the Autodiscover host when the system is initialized. If the single agent manages more than 500 machines, consider increasing this value (only for agent Scenarios) # # mandatory:no# range:0-250# default:# startdiscoverers=1### Option: starthttppollers# number of pre-forked instances of HTTP pollers. The system is pre-allocated to set the number of web monitoring processes, which may increase or decrease this value in the specific case.  # # 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 T       He maintenance periods.//number of instances Timers # 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:star tvmwarecollectors# Number of pre-forked VMSWare collector instances. The number of processes used to monitor the VMware ESXi Host instance is not enabled for 0, and to monitor ESXi hosts, this value is at least 1, and the corresponding value is set according to the number of monitoring ESXi numbers # mandatory:no# range:0-250# default:# startvmwarecollectors=0### option:vmwarefrequency# How often Zabbix would connect to VMware service to obtain a new Data. Zabbix Connect WMware Service How often to get new data # mandatory:no# range:10-86400# default:# vmwarefrequency=60### Option: vmwareperffrequency# how often Zabbix would connect to VMware service to obtain performance data.## mandatory:no# Ra  nge: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 is started.//used to cache VMware data Shared Memories # # mandatory:no# range:256k-2g# default:# vmwarecachesize=8m### option:vmwaretimeout# Specifies How many seconds V Mware collector waits for response from VMware service.## mandatory:no# range:1-300# default:# vmwaretimeout=10### optio       n:snmptrapperfile#Temporary file used for passing data from SNMP Trap Daemon to the server.# must is the same as in Zabbix_trap_receiv er.pl or SNMPTT configuration file.## mandatory:no# default:# snmptrapperfile=/tmp/zabbix_traps.tmp### Option: startsnmptrapper# if 1, SNMP trapper process is started.//whether the Snmptrapper feature is enabled, = 0 is not enabled by default, enable =1## mandatory:no# range:0- # default:# startsnmptrapper=0### option:listenip# List of comma delimited IP addresses that the trapper should Li Sten on.# Trapper would listen on all network interfaces if this parameter is missing.## mandatory:no# default:# Lis tenip=0.0.0.0# listenip=127.0.0.1### option:housekeepingfrequency# How often Zabbix would perform housekeeping proce Dure (in hours). # Housekeeping are removing outdated information from the database.# to prevent housekeeper fro m being overloaded, no more than 4 times housekeepingfrequency# hours of outdated information is deleted in one Hou  Sekeeping cycle, for each item.#     To lower load on server startup housekeeping are postponed for the minutes after server start.# with housekeeping Frequency=0 The housekeeper can be is only executed using the runtime control option.# in this case the period of OUTDA Ted Information deleted in one housekeeping cycle was 4 times the# period since the last housekeeping cycle, and not Less than 4 hours and isn't greater than 4 days. How many hours to clean up the history of the database, alert, and Alarms data # # mandatory:no# range:0-24# default:# housekeepingfrequency=1### Option:max housekeeperdelete# the table "housekeeper" contains "tasks" for housekeeping procedure in the format:# [Housek Eeperid], [tablename], [Field], [value].# No more than ' maxhousekeeperdelete ' rows (corresponding to [TableName], [f  Ield], [value]) # would be deleted per one task in one housekeeping cycle.# SQLite3 does don't 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 is doing!//housekeeping once deleted data cannot be greater than maxhousekeeperdelete## mandatory:no# range:0-10000 00# default:# maxhousekeeperdelete=5000### option:senderfrequency# How often Zabbix would try to send unsent alerts       (in seconds).//Specify the interval in seconds before attempting to send an alert for send # 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. Allocate how much shared memory is used to store configuration information, Host,item,trigger data, depending on the number of monitoring hosts and monitoring items adjusted, recommended to adjust to 32M or larger, 2.2.3 before the maximum support 2G, currently the largest support 8G, generally not much. # # mandatory:no# range:128k-8g# default:# cachesize=8m### option:cacheupdatefrequency# How often Zabbix would perf ORM Update of the configuration cache, in seconds. Update the system cache frequency, if the management page operation is not frequent, you can consider increasing the parameter value # # mandatory:no# range:1-3600# default:# cacheupdatefrequency=60### Option: startdbsyncers# number of pre-forked instances of DB syncers. Synchronizes the collected data from the cache to the number of database threads, depending on the database server I/O busy situation, and database write capability tuning. The higher the value, the stronger the writing ability. The greater the pressure on the database server I/O. ## mandatory:no# range:1-100# default:# startdbsyncers=4### option:historycachesize# Size of History cache, in byte s.# Shared memory size for storing history data. Set how much shared memory is used to store the collected historical data, the larger the value, the smaller the database read pressure # mandatory:no# range:128k-2g# default:# historycachesize=16m### Option: historyindexcachesize# size of history index cache, in bytes.# GKFX memory Size for indexing history cache. Historical Data Index Cache # # mandatory:no# range:128k-2g# default:# historyindexcachesize=4m### option:trendcachesize# Size of TR End cache, in bytes.# Shared memory size for storing trends data. Used to set how much shared memory is used to store calculated trend data, which can affect the database reading pressure to a certain extent # mandatory:no# range:128k-2g# default:# trendcachesize=4m### option:valuecachesize# size of History value cache, in bytes.# Shared memory Size for caching item History DA Ta requests.# Setting to 0 disables value cache.//0 is disabled, the history value cache size, when the cache exceeded, will be logged every 5 minutes to the server log. # # mandatory:no# range:0,128k-64g# default:# Valuecachesize=8m### option:timeout# Specifies how long we wait for the agent, SNMP device or external check (in seconds). Communication time-out settings for agnet, SNMP devices, and other external devices, in seconds, or if the collection of data is incomplete or the network is busy, or if the client state changes frequently from the management page, you may consider increasing this value. Note that if this value increases, the parameter startpollers should be considered if there is a corresponding increase in the necessary.  # # mandatory:no# range:1-30# default:# timeout=3### option:trappertimeout# Specifies how many seconds trapper Spend processing new data. Enables the trapper feature for process wait timeout settings.  # # mandatory:no# range:1-300# default:# trappertimeout=300### option:unreachableperiod# after how many seconds of Unreachability treat a host as unavailable.//attempts to reconnect when the agent side is in an unusable state, after a few seconds. It is recommended to set it according to specific circumstances. Note that if this value is too small, if the agent terminal business System is busy, it is possible to cause alarm false positives # mandatory:no# range:1-3600# default:# unreachableperiod=45### Option: unavailabledelay# How often host was checked for availability during the unavailability period, in seconds. When the agent side is in an unusable state, the interval is a few seconds after the status check. If the data can be collected normally, but the Management page agent state is not normal, or in the network, port and so on, the agent state is still not normal, you can consider increasing this value # # mandatory:no# range:1-3600# default:# Unavailabledelay=60# # # option:unreachabledelay# How often host was checked for availability during the unreachability period, in second s.//when the agent side is in the unreachable state, delay how many seconds after the retry, the recommendation remains the default, in the Agent access debugging phase, you can consider reducing this value # mandatory:no# range:1-3600# default:# unreachabledelay=15### option:alertscriptspath# full path to location of the custom alert scripts. # Default depends on compilation options.//custom alarm script Store full path # # mandatory:no# default:# Alertscriptspath=${datadir}/zabbi        x/alertscripts### option:logslowqueries# How long a database query could take the before being logged (in milliseconds). # Only works if DebugLevel set to 3, 4 or 5.# 0-don ' t log slow queries. For the server-side database slow query function, in milliseconds. If you have a server-side database to monitor the requirements of slow queries, you can adjust this number as appropriate. # # mandatory:no# range:1-3600000# default:# logslowqueries=0### option:tmpdir# Temporary directory.//specify a temporary directory path # # M andatory:no# default:# tmpdir=/tmp### option:startproxypollers# Number of pre-forked instances of pollers for pass Ive proxies.//enable how many sub-processes and agent-side communication, if the agent side more consider increasing this value # Mandatory:no# range:0-250# default:# startproxypollers=1### option:proxyconfigfrequency# How often Zabbix Server se NDS configuration data to a Zabbix proxies in seconds.# This parameter are used only for proxies in the passive mode.// Zabbix server to synchronize profile data to the agent-side frequency, only for the agent-side passive mode situation # # mandatory:no# range:1-3600*24*7# default:# proxyconfigfrequency=3600### option:proxydatafrequency# how often Zabbix Server requests history data from a Zabbix proxies in seconds.# Thi s parameter is used the frequency of the data collected by the proxy side of the server for the proxies in the passive, the agent-side only applies to the passive mode situation # # Mode.//zabbix mandatory:no# 3600# default:# proxydatafrequency=1### option:allowroot # allow the server to run as ' root '. If disabled and the server is started by ' root ', the server# would try to switch to the user specified by the user Co Nfiguration option instead.# have no effect if started under a regular user.# 0-do not allow# 1-allow Allow server to run as root # # mandatory:no# default:# Allowroot=0### option:user# Drop privileges to a specific, existing User on the system.# only have effect if run a s ' Root ' and Allowroot is disabled.//the user who started the Zabbix server, is configured to disable root startup, and the current shell user is rooted in the case. If the current user is ABC, then the running user of Zabbix server is abc## mandatory:no# default:# user=zabbix### option:include# you might Include Indiv idual files or all files in a directory in the configuration file.# installing Zabbix would create include directory IN/USR/LOCAL/ETC, unless modified during the compile time.//in some cases, the software parameter profile is very long, in order to facilitate management, the configuration file is cut into n configuration files, but in order to master configuration parameters file Concise, The Include parameter is enabled to allow the program to read all configuration files under the specified directory # # 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 parameter file in a detailed