Zabbix Documentation 3.4

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:appendix:config:zabbix_agentd

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

manual:appendix:config:zabbix_agentd [2019/09/03 07:45]
manual:appendix:config:zabbix_agentd [2019/04/03 12:19] (current)
martins-v ServerActive - spaces are allowed since 2.2
Line 1: Line 1:
 +==== 3 Zabbix agent (UNIX) ====
 +
 +<​note>​The default values reflect daemon defaults, not the values in the shipped configuration files.</​note>​
 +
 +The parameters supported in a Zabbix agent configuration file (//​zabbix_agentd.conf//​):​
 +
 +^Parameter^Mandatory^Range^Default^Description^
 +| Alias| no | | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.\\ Multiple //Alias// parameters may be present. Multiple parameters with the same //Alias// key are allowed.\\ Different //Alias// keys may reference the same item key.\\ Aliases can be used in //​HostMetadataItem//​ but not in //​HostnameItem//​ parameters.\\ \\ Examples:\\ \\ 1. Retrieving the ID of user '​zabbix'​.\\ %%Alias=zabbix.userid:​vfs.file.regexp[/​etc/​passwd,"​^zabbix:​.:​([0-9]+)",,,,​\1]%%\\ Now shorthand key **zabbix.userid** may be used to retrieve data.\\ ​ \\ 2. Getting CPU utilization with default and custom parameters.\\ Alias=cpu.util:​system.cpu.util\\ Alias=cpu.util[*]:​system.cpu.util[*]\\ This allows use **cpu.util** key to get CPU utilisation percentage with default parameters as well as use **cpu.util[all,​ idle, avg15]** to get specific data about CPU utilisation.\\ \\ 3. Running multiple [[manual/​discovery/​low_level_discovery|low-level discovery]] rules processing the same discovery items.\\ Alias=vfs.fs.discovery[*]:​vfs.fs.discovery\\ Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery[foo]**,​ **vfs.fs.discovery[bar]**,​ etc.  |
 +| AllowRoot| no | |0 |Allow the agent to run as '​root'​. If disabled and the agent is started by '​root',​ the agent will try to switch to user '​zabbix'​ instead. Has no effect if started under a regular user.\\ 0 - do not allow\\ 1 - allow|
 +| BufferSend| no | 1-3600 |5 |Do not keep data longer than N seconds in buffer. |
 +| BufferSize| no | 2-65535 |100 |Maximum number of values in a memory buffer. The agent will send\\ all collected data to Zabbix server or proxy if the buffer is full. |
 +| 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 |
 +| HostMetadata| no | 0-255 characters| | Optional parameter that defines host metadata. Host metadata is used only at host auto-registration process (active agent).\\ If not defined, the value will be acquired from HostMetadataItem.\\ An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.\\ This option is supported in version 2.2.0 and higher.|
 +| HostMetadataItem| no | | | Optional parameter that defines a //Zabbix agent// item used for getting host metadata. This option is only used when HostMetadata is not defined.\\ Supports UserParameters and aliases. Supports //​system.run[]//​ regardless of //​EnableRemoteCommands//​ value.\\ Host metadata is used only at host auto-registration process (active agent).\\ During an auto-registration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.\\ The value returned by the item must be a UTF-8 string otherwise it will be ignored.\\ This option is supported in version 2.2.0 and higher.|
 +| Hostname| no | |Set by HostnameItem |Unique, case sensitive hostname.\\ Required for active checks and must match hostname as configured on the server.\\ Allowed characters: alphanumeric,​ '​.',​ ' ', '​_'​ and '​-'​.\\ Maximum length: 64|
 +| HostnameItem| no | |system.hostname |Optional parameter that defines a //Zabbix agent// item used for getting host name. This option is only used when Hostname is not defined.\\ Does not support UserParameters or aliases, but does support //​system.run[]//​ regardless of //​EnableRemoteCommands//​ value.\\ This option is supported in version 1.8.6 and higher.|
 +| 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_include|special notes]] about limitations.|
 +| ListenIP| no | |0.0.0.0 |List of comma delimited IP addresses that the agent should listen on.\\ Multiple IP addresses are supported in version 1.8.3 and higher.|
 +| ListenPort| no | 1024-32767 |10050 |Agent will listen on this port for connections from the server. |
 +| LoadModule| no |  |  |Module to load at agent startup. Modules are used to extend functionality of the agent.\\ Format: LoadModule=<​module.so>​\\ The modules must be located in directory specified by LoadModulePath.\\ It is allowed to include multiple LoadModule parameters. ​ |
 +| LoadModulePath| no |  |  |Full path to location of agent 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. |
 +| 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. |
 +| LogRemoteCommands| no | |0 |Enable logging of executed shell commands as warnings.\\ 0 - disabled\\ 1 - enabled |
 +| MaxLinesPerSecond| no | 1-1000 |20 |Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing '​log'​ and '​eventlog'​ active checks.\\ The provided value will be overridden by the parameter '​maxlines',​\\ provided in '​log'​ or '​eventlog'​ item key.\\ //Note//: Zabbix will process 10 times more new lines than set in //​MaxLinesPerSecond//​ to seek the required string in log items. ​ |
 +| PidFile| no | |/​tmp/​zabbix_agentd.pid |Name of PID file. |
 +| RefreshActiveChecks| no | 60-3600 |120 |How often list of active checks is refreshed, in seconds.\\ Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds. |
 +| Server| yes, if StartAgents is not explicitly set to 0 | | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers and Zabbix proxies.\\ Incoming connections will be accepted only from the hosts 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.\\ Note, that "​IPv4-compatible IPv6 addresses"​ (0000::/96 prefix) are supported but deprecated by [[https://​tools.ietf.org/​html/​rfc4291#​section-2.5.5|RFC4291]].\\ Example: Server=127.0.0.1,​192.168.1.0/​24,::​1,​2001:​db8::/​32,​zabbix.domain\\ Spaces are allowed. |
 +| ServerActive| no | | |IP:port (or hostname:​port) of Zabbix server or Zabbix proxy for active checks.\\ Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.\\ If port is not specified, default port is used.\\ IPv6 addresses must be enclosed in square brackets if port for that host is specified.\\ If port is not specified, square brackets for IPv6 addresses are optional.\\ If this parameter is not specified, active checks are disabled. |
 +| SourceIP| no | | |Source IP address for outgoing connections. |
 +| StartAgents| no | 0-100 |3 |Number of pre-forked instances of zabbix_agentd that process passive checks.\\ If set to 0, disables passive checks and the agent will not listen on any TCP port.\\ The upper limit used to be 16 before version 1.8.5. |
 +| Timeout| no | 1-30 |3 |Spend no more than Timeout seconds on processing |
 +| TLSAccept| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |What incoming connections to accept. Used for a passive checks. 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 agent certificate or certificate chain, used for encrypted communications with Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 +| TLSConnect| yes, if TLS certificate or PSK parameters are defined (even for //​unencrypted//​ connection),​ otherwise no |  | |How the agent should connect to Zabbix server or proxy. Used for active checks. 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 with Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 +| TLSKeyFile| no |  | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 +| TLSPSKFile| no |  | |Full pathname of a file containing the agent pre-shared key  used for encrypted communications with Zabbix components.\\ 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 (proxy) certificate issuer.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 +| TLSServerCertSubject| no |  | |Allowed server (proxy) certificate subject.\\ This parameter is supported since Zabbix 3.0.0. ​ |
 +| UnsafeUserParameters| no | 0,1 |0 |Allow all characters to be passed in arguments to user-defined parameters. Supported since Zabbix 1.8.2.\\ The following characters are not allowed:\\ %%\ ' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @%%\\ Additionally,​ newline characters are not allowed. |
 +| 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. ​ |
 +| UserParameter| no | | |User-defined parameter to monitor. There can be several user-defined parameters.\\ Format: UserParameter=<​key>,<​shell command>​\\ Note that shell command must not return empty string or EOL only.\\ Example: UserParameter=system.test,​who%%|%%wc -l |
 +
 +<​note>​In Zabbix agent 2.0.0 version configuration parameters related to active and passive checks have been changed.\\ See the [[#​see_also|"​See also"​]] section at the bottom of this page to read more details about these changes.</​note>​
 +
 +<​note>​Zabbix supports configuration files only in UTF-8 encoding without [[https://​en.wikipedia.org/​wiki/​Byte_order_mark|BOM]].\\ \\  Comments starting with "#"​ are only supported in the beginning of the line.</​note>​
 +==== See also ====
 +  - [[http://​blog.zabbix.com/​multiple-servers-for-active-agent-sure/​858|Differences in the Zabbix agent configuration for active and passive checks starting from version 2.0.0]]