Overview

    There are passive and active agent checks. When configuring an item, you can select the required type:

    • Zabbix agent - for passive checks

    • Zabbix agent (active) - for active checks

    Supported item keys

    The table provides details on the item keys that you can use with Zabbix agent items.

    See also:

    Mandatory and optional parameters

    Parameters without angle brackets are mandatory. Parameters marked with angle brackets < > are optional.

    Footnotes

    1A Linux-specific note. Zabbix agent must have read-only access to filesystem /proc. Kernel patches from limit access rights of non-privileged users.

    2 vfs.dev.read[], vfs.dev.write[]: Zabbix agent will terminate “stale” device connections if the item values are not accessed for more than 3 hours. This may happen if a system has devices with dynamically changing paths or if a device gets manually removed. Note also that these items, if using an update interval of 3 hours or more, will always return ‘0’.

    4 Perl Compatible Regular Expression (PCRE) since Zabbix 3.4; POSIX-extended regular expression before that. See also: .

    5 SSL (HTTPS) is supported only if agent is compiled with cURL support. Otherwise the item will turn unsupported.

    Encoding settings

    To make sure that the acquired data are not corrupted you may specify the correct encoding for processing the check (e.g. ‘vfs.file.contents’) in the encoding parameter. The list of supported encodings (code page identifiers) may be found in documentation for (GNU Project) or in Microsoft Windows SDK documentation for “Code Page Identifiers”.

    If no encoding is specified in the parameter the following resolution strategies are applied:

    • Standard resolution - UTF-8 is used in Unix/Linux (default in newer distributions); ANSI with a system-specific extension is used in Windows;

    • BOM analysis - applicable for items ‘vfs.file.contents’, ‘vfs.file.regexp’, ‘vfs.file.regmatch’. An attempt is made to determine the correct encoding by using the byte order mark (BOM) at the beginning of the file. If BOM is not present - standard resolution (see above) is applied instead.

    Troubleshooting agent items

    • If used with the passive agent, Timeout value in server configuration may need to be higher than Timeout in the agent configuration file. Otherwise the item may not get any value because the server request to agent timed out first.