This is an old revision of the document!
The parameters supported in a Zabbix agent (Windows) configuration file:
|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 not allowed.
Different Alias keys may reference the same item key.
For example, to retrieve paging file usage in percents from the server:
Alias=pg_usage:perf_counter[\Paging File(_Total)\% Usage]
Now shorthand key pg_usage may be used to retrieve data.
Aliases can be used in HostMetadataItem but not in HostnameItem or PerfCounter parameters.
|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-4||3||Specifies debug level:
0 - no debug
1 - critical information
2 - error information
3 - warnings
4 - for debugging (produces lots of 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, performance counters and aliases. Supports system.run regardless of EnableRemoteCommands value.
HostMetadataItem value is retrieved on each auto-registration attempt and 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, performance counters or aliases, but does support system.run regardless of EnableRemoteCommands value.
This option is supported in version 1.8.6 and higher.
See also a more detailed description.
|Include||no||You may include individual file in the configuration file.|
|ListenIP||no||0.0.0.0||List of comma-delimited IP addresses that the agent should listen on.
Multiple IP addresses are supported since Zabbix 1.8.3.
|ListenPort||no||1024-32767||10050||Agent will listen on this port for connections from the server.|
|LogFile||no||Name of log file.
If not set, Windows Event Log is used.
|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.
|LogRemoteCommands||no||0||Enable logging of executed shell commands as warnings.
0 - disabled
1 - enabled
|MaxLinesPerSecond||no||1-1000||100||Maximum number of new lines the agent will send per second to Zabbix server
or proxy processing 'log', 'logrt' and 'eventlog' active checks.
The provided value will be overridden by the parameter 'maxlines',
provided in 'log', 'logrt' or 'eventlog' item keys.
Defines new parameter <parameter_name> which is an average value for system performance counter <perf_counter_path> for the specified time period <period> (in seconds).
For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter “interrupts” as following:
PerfCounter = interrupts,“\Processor(0)\Interrupts/sec”,60
Please note double quotes around performance counter path.
The parameter name (interrupts) is to be used as the item key when creating an item.
Samples for calculating average value will be taken every second.
You may run “typeperf -qx” to get list of all performance counters available in Windows.
|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 0; no otherwise||List of comma delimited IP addresses (or hostnames) of Zabbix servers. Spaces are allowed since the Zabbix 2.2 version.
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.
|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.
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-63 (*)||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|
|UnsafeUserParameters||no||0-1||0||Allow all characters to be passed in arguments to user-defined parameters.
0 - do not allow
1 - allow
|UserParameter||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,echo 1