en-us	 |Key|<|<|<|<| |---|-|-|-|-| |<|**Description**|**Return value**|**Parameters**|**Comments**| |agent.hostmetadata|<|<|<|<| |<|Agent host metadata.|String||Returns the value of HostMetadata or HostMetadataItem parameters, or empty string if none are defined.<br><br>Supported since Zabbix 6.0.| |agent.hostname|<|<|<|<| |<|Agent host name.|String| |Returns:<br>As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file;<br>As active check - the name of the current hostname.| |agent.ping|<|<|<|<| |<|Agent availability check.|Nothing - unavailable<br><br>1 - available| |Use the **nodata()** trigger function to check for host unavailability.| |agent.variant|<|<|<|<| |<|Variant of Zabbix agent (Zabbix agent or Zabbix agent 2).|Integer| |Example of returned value:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |agent.version|<|<|<|<| |<|Version of Zabbix agent.|String| |Example of returned value:<br>6.0.3| |kernel.maxfiles|<|<|<|<| |<|Maximum number of opened files supported by OS.|Integer| | | |kernel.maxproc|<|<|<|<| |<|Maximum number of processes supported by OS.|Integer| | | |kernel.openfiles|<|<|<|<| |<|Return the number of currently open file descriptors.|Integer||This item is supported on Linux only since Zabbix 6.0.| |log\[file,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Monitoring of a log file.|Log|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0)- possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |log.count\[file,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Count of matched lines in a monitored log file.|Integer|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |logrt\[file\_regexp,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Monitoring of a log file that is rotated.|Log|**file\_regexp** - absolute path to file and the file name described by a regular [expression](/manual/regular_expressions#overview). *Note* that only the file name is a regular expression<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0) - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>Note that logrt is designed to work with one currently active log file, with several other matching inactive files rotated. If, for example, a directory has many active log files, a separate logrt item should be created for each one. Otherwise if one logrt item picks up too many files it may lead to exhausted memory and a crash of monitoring.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}$",,,100\] → will match a file like "logfile1" (will not match ".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}$","pattern\_to\_match","UTF-8",100\] → will collect data from files such "logfile\_abc\_1" or "logfile\_\_001".<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> logrt\[/app1/\^test.\*log$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |logrt.count\[file\_regexp,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Count of matched lines in a monitored log file that is rotated.|Integer|**file\_regexp** - absolute path to file and regular [expression](/manual/regular_expressions#overview) describing the file name pattern<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |modbus.get\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<|<| |<|Reads Modbus data.|JSON object|**endpoint** - endpoint defined as `protocol://connection_string`<br>**slave id** - slave ID<br>**function** - Modbus function<br>**address** - address of first registry, coil or input<br>**count** - number of records to read<br>**type** - type of data<br>**endianness** - endianness configuration<br>**offset** - number of registers, starting from 'address', the results of which will be discarded.<br><br>See a [detailed description](/manual/appendix/items/modbus) of parameters.|Supported since Zabbix 5.2.0.| |net.dns\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Checks if DNS service is up.|0 - DNS is down (server did not respond or DNS resolution failed)<br><br>1 - DNS is up|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol** (since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns*| |net.dns.record\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Performs a DNS query.|Character string with the required type of information|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol**(since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns.query*| |net.if.collisions\[if\]|<|<|<|<| |<|Number of out-of-window collisions.|Integer|**if** - network interface name| | |net.if.discovery|<|<|<|<| |<|List of network interfaces. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>On FreeBSD, OpenBSD and NetBSD supported since Zabbix 2.2.<br><br>Some Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names.| |net.if.in\[if,<mode>\]|<|<|<|<| |<|Incoming traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*frame* - the number of packet framing errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver<br>*multicast* - the number of multicast frames received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix 1.8.6.<br><br>Examples:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.out\[if,<mode>\]|<|<|<|<| |<|Outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*collisions (colls)* - the number of collisions detected on the interface<br>*carrier* - the number of carrier losses detected by the device driver<br>*compressed* - the number of compressed packets transmitted by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix agent 1.8.6 version.<br><br>Examples:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.total\[if,<mode>\]|<|<|<|<| |<|Sum of incoming and outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Examples:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.<br><br>Note that dropped packets are supported only if both net.if.in and net.if.out work for dropped packets on your platform.| |net.tcp.listen\[port\]|<|<|<|<| |<|Checks if this TCP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - TCP port number|Example:<br>=> net.tcp.listen\[80\]<br><br>On Linux supported since Zabbix 1.8.4<br><br>Since Zabbix 3.0.0, on Linux kernels 2.6.14 and above, information about listening TCP sockets is obtained from the kernel's NETLINK interface, if possible. Otherwise, the information is retrieved from /proc/net/tcp and /proc/net/tcp6 files.| |net.tcp.port\[<ip>,port\]|<|<|<|<| |<|Checks if it is possible to make TCP connection to specified port.|0 - cannot connect<br><br>1 - can connect|**ip** - IP or DNS name (default is 127.0.0.1)<br>**port** - port number|Example:<br>=> net.tcp.port\[,80\] → can be used to test availability of web server running on port 80.<br><br>For simple TCP performance testing use net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).| |net.tcp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.port for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of TCP service.|0 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,<port>\] for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.tcp.socket.count\[,80,,,established\] → check if local TCP port 80 is in "established" state<br><br>This item is supported since Zabbix 6.0.| |net.udp.listen\[port\]|<|<|<|<| |<|Checks if this UDP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - UDP port number|Example:<br>=> net.udp.listen\[68\]<br><br>On Linux supported since Zabbix 1.8.4| |net.udp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of UDP service.|0 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *unconn*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → check if any UDP socket is in "listening" state<br><br>This item is supported since Zabbix 6.0.| |proc.cpu.util\[<name>,<user>,<type>,<cmdline>,<mode>,<zone>\]|<|<|<|<| |<|Process CPU utilization percentage.|Float|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**type** - CPU utilization type:<br>*total* (default), *user*, *system*<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**mode** - data gathering mode: *avg1* (default), *avg5*, *avg15*<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.cpu.util\[,root\] → CPU utilization of all processes running under the "root" user<br>=> proc.cpu.util\[zabbix\_server,zabbix\] → CPU utilization of all zabbix\_server processes running under the zabbix user<br><br>The returned value is based on single CPU core utilization percentage. For example CPU utilization of a process fully using two cores is 200%.<br><br>The process CPU utilization data is gathered by a collector which supports the maximum of 1024 unique (by name, user and command line) queries. Queries not accessed during the last 24 hours are removed from the collector.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.<br><br>This key is supported since Zabbix 3.0.0 and is available on several platforms (see [Items supported by platform](/manual/appendix/items/supported_by_platform)).| |proc.mem\[<name>,<user>,<mode>,<cmdline>,<memtype>\]|<|<|<|<| |<|Memory used by process in bytes.|Integer - with `mode` as *max*, *min*, *sum*<br><br>Float - with `mode` as *avg*|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**mode** - possible values:<br>*avg*, *max*, *min*, *sum* (default)<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**memtype** - [type of memory](/manual/appendix/items/proc_mem_notes) used by process|Examples:<br>=> proc.mem\[,root\] → memory used by all processes running under the "root" user<br>=> proc.mem\[zabbix\_server,zabbix\] → memory used by all zabbix\_server processes running under the zabbix user<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → memory used by the most memory-hungry process running under oracle having oracleZABBIX in its command line<br><br>*Note*: When several processes use shared memory, the sum of memory used by processes may result in large, unrealistic values.<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.mem[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>The `memtype` parameter is supported on several [platforms](/manual/appendix/items/supported_by_platform) since Zabbix 3.0.0.| |proc.num\[<name>,<user>,<state>,<cmdline>,<zone>\]|<|<|<|<| |<|The number of processes.|Integer|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**state** (*disk* and *trace* options since version 3.4.0) - possible values:<br>*all* (default),<br>*disk* - uninterruptible sleep,<br>*run* - running,<br>*sleep* - interruptible sleep,<br>*trace* - stopped,<br>*zomb* - zombie<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.num\[,mysql\] → number of processes running under the mysql user<br>=> proc.num\[apache2,www-data\] → number of apache2 processes running under the www-data user<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → number of processes in sleep state running under oracle having oracleZABBIX in its command line<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>On Windows, only the `name` and `user` parameters are supported.<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.num[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.| |sensor\[device,sensor,<mode>\]|<|<|<|<| |<|Hardware sensor reading.|Float|**device** - device name<br>**sensor** - sensor name<br>**mode** - possible values:<br>*avg*, *max*, *min* (if this parameter is omitted, device and sensor are treated verbatim).|Reads /proc/sys/dev/sensors on Linux 2.4.<br><br>Example:<br>=> sensor\[w83781d-i2c-0-2d,temp1\]<br><br>Prior to Zabbix 1.8.4, the *sensor\[temp1\]* format was used.| |^|^|^|^|Reads /sys/class/hwmon on Linux 2.6+.<br><br>See a more detailed description of [sensor](/manual/appendix/items/sensor) item on Linux.| |^|^|^|^|Reads the *hw.sensors* MIB on OpenBSD.<br><br>Examples:<br>=> sensor\[cpu0,temp0\] → temperature of one CPU<br>=> sensor\["cpu\[0-2\]$",temp,avg\] → average temperature of the first three CPU's<br><br>Supported on OpenBSD since Zabbix 1.8.4.| |system.boottime|<|<|<|<| |<|System boot time.|Integer (Unix timestamp)| | | |system.cpu.discovery|<|<|<|<| |<|List of detected CPUs/CPU cores. Used for low-level discovery.|JSON object| |Supported on all platforms since 2.4.0.| |system.cpu.intr|<|<|<|<| |<|Device interrupts.|Integer| | | |system.cpu.load\[<cpu>,<mode>\]|<|<|<|<| |<|[CPU load](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - possible values:<br>*all* (default), *percpu* (since version 2.0; total load divided by online CPU count)<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |system.cpu.num\[<type>\]|<|<|<|<| |<|Number of CPUs.|Integer|**type** - possible values:<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |system.cpu.switches|<|<|<|<| |<|Count of context switches.|Integer| | | |system.cpu.util\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<|<| |<|CPU utilization percentage.|Float|**cpu** - *<CPU number>* or *all* (default)<br>**type** - possible values:<br>*user* (default), *idle*, *nice*, *system* (default for Windows), *iowait*, *interrupt*, *softirq*, *steal*, *guest* (on Linux kernels 2.6.24 and above), *guest\_nice* (on Linux kernels 2.6.33 and above).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*<br>**logical\_or\_physical** (since version 5.0.3; on AIX only) - possible values: *logical* (default), *physical*. This parameter is supported on AIX only.|Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>Old naming: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |system.hostname\[<type>, <transform>\]|<|<|<|<| |<|System host name.|String|**type** (before version 5.4.7 supported on Windows only) - possible values: *netbios* (default on Windows), *host* (default on Linux), *shorthost* (since version 5.4.7; returns part of the hostname before the first dot, a full string for names without dots).<br>**transform** (since version 5.4.7) - possible values:<br>*none* (default), *lower* (convert to lowercase)|The value is acquired by either GetComputerName() (for **netbios**) or gethostname() (for **host**) functions on Windows and by "hostname" command on other systems.<br><br>Examples of returned values:<br>*on Linux*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |system.hw.chassis\[<info>\]|<|<|<|<| |<|Chassis information.|String|**info** - one of full (default), model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>This key depends on the availability of the [SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) table.<br>Will try to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory.<br><br>**Root permissions** are required because the value is acquired by reading from sysfs or memory.<br><br>Supported since Zabbix 2.0.| |system.hw.cpu\[<cpu>,<info>\]|<|<|<|<| |<|CPU information.|String or integer|**cpu** - *<CPU number>* or *all* (default)<br>**info** - possible values:<br>*full* (default), *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>Gathers info from /proc/cpuinfo and /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq.<br><br>If a CPU number and *curfreq* or *maxfreq* is specified, a numeric value is returned (Hz).<br><br>Supported since Zabbix 2.0.| |system.hw.devices\[<type>\]|<|<|<|<| |<|Listing of PCI or USB devices.|Text|**type** (since version 2.0) - *pci* (default) or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>Returns the output of either lspci or lsusb utility (executed without any parameters).| |system.hw.macaddr\[<interface>,<format>\]|<|<|<|<| |<|Listing of MAC addresses.|String|**interface** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**format** - *full* (default) or *short*|Lists MAC addresses of the interfaces whose name matches the given `interface` regular [expression](/manual/regular_expressions#overview) (*all* lists for all interfaces).<br><br>Example:<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If `format` is specified as *short*, interface names and identical MAC addresses are not listed.<br><br>Supported since Zabbix 2.0.| |system.localtime\[<type>\]|<|<|<|<| |<|System time.|Integer - with `type` as *utc*<br><br>String - with `type` as *local*|**type** (since version 2.0) - possible values:<br>*utc* - (default) the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds.<br>*local* - the time in the 'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm' format<br>|Must be used as a [passive check](/manual/appendix/items/activepassive#passive_checks) only.<br><br>Example:<br>=> system.localtime\[local\] → create an item using this key and then use it to display host time in the *Clock* [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock).| |system.run\[command,<mode>\]|<|<|<|<| |<|Run specified command on the host.|Text result of the command<br><br>1 - with `mode` as *nowait* (regardless of command result)|**command** - command for execution<br>**mode** - possible values:<br>*wait* - wait end of execution (default),<br>*nowait* - do not wait|Up to 512KB of data can be returned, including trailing whitespace that is truncated.<br>To be processed correctly, the output of the command must be text.<br><br>Example:<br>=> system.run\[ls -l /\] → detailed file list of root directory.<br><br>*Note*: system.run items are disabled by default. Learn how to [enable them](/manual/config/items/restrict_checks).<br><br>The return value of the item is standard output together with standard error produced by command. The exit code is not checked.<br><br>Empty result is allowed starting with Zabbix 2.4.0.<br>See also: [Command execution](/manual/appendix/command_execution).| |system.stat\[resource,<type>\]|<|<|<|<| |<|System statistics.|Integer or float|**ent** - number of processor units this partition is entitled to receive (float)<br>**kthr,<type>** - information about kernel thread states:<br>*r* - average number of runnable kernel threads (float)<br>*b* - average number of kernel threads placed in the Virtual Memory Manager wait queue (float)<br>**memory,<type>** - information about the usage of virtual and real memory:<br>*avm* - active virtual pages (integer)<br>*fre* - size of the free list (integer)<br>**page,<type>** - information about page faults and paging activity:<br>*fi* - file page-ins per second (float)<br>*fo* - file page-outs per second (float)<br>*pi* - pages paged in from paging space (float)<br>*po* - pages paged out to paging space (float)<br>*fr* - pages freed (page replacement) (float)<br>*sr* - pages scanned by page-replacement algorithm (float)<br>**faults,<type>** - trap and interrupt rate:<br>*in* - device interrupts (float)<br>*sy* - system calls (float)<br>*cs* - kernel thread context switches (float)<br>**cpu,<type>** - breakdown of percentage usage of processor time:<br>*us* - user time (float)<br>*sy* - system time (float)<br>*id* - idle time (float)<br>*wa* - idle time during which the system had outstanding disk/NFS I/O request(s) (float)<br>*pc* - number of physical processors consumed (float)<br>*ec* - the percentage of entitled capacity consumed (float)<br>*lbusy* - indicates the percentage of logical processor(s) utilization that occurred while executing at the user and system level (float)<br>*app* - indicates the available physical processors in the shared pool (float)<br>**disk,<type>** - disk statistics:<br>*bps* - indicates the amount of data transferred (read or written) to the drive in bytes per second (integer)<br>*tps* - indicates the number of transfers per second that were issued to the physical disk/tape (float)|<| |<|^|^|Comments|<| |<|^|^|This item is [supported](/manual/appendix/items/supported_by_platform) on AIX only, since Zabbix 1.8.1.<br>Take note of the following limitations in these items:<br>=> system.stat\[cpu,app\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,ec\] - supported on AIX LPAR of type "Shared" and "Dedicated" ("Dedicated" always returns 100 (percent))<br>=> system.stat\[cpu,lbusy\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,pc\] - supported on AIX LPAR of type "Shared" and "Dedicated"<br>=> system.stat\[ent\] - supported on AIX LPAR of type "Shared" and "Dedicated"|<| |system.sw.arch|<|<|<|<| |<|Software architecture information.|String| |Example:<br>=> system.sw.arch → i686<br><br>Info is acquired from uname() function.<br><br>Supported since Zabbix 2.0.| |system.sw.os\[<info>\]|<|<|<|<| |<|Operating system information.|String|**info** - possible values:<br>*full* (default), *short* or *name*|Example:<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>Info is acquired from (note that not all files and options are present in all distributions):<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME parameter from /etc/os-release on systems supporting it, or /etc/issue.net (*name*)<br><br>Supported since Zabbix 2.0.| |system.sw.packages\[<package>,<manager>,<format>\]|<|<|<|<| |<|Listing of installed packages.|Text|**package** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**manager** - *all* (default) or a package manager<br>**format** - *full* (default) or *short*|Lists (alphabetically) installed packages whose name matches the given `package` regular [expression](/manual/regular_expressions#overview) (*all* lists them all).<br><br>Example:<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>Supported package managers (executed command):<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>If `format` is specified as *full*, packages are grouped by package managers (each manager on a separate line beginning with its name in square brackets).<br>If `format` is specified as *short*, packages are not grouped and are listed on a single line.<br><br>Supported since Zabbix 2.0.| |system.swap.in\[<device>,<type>\]|<|<|<|<| |<|Swap in (from device into memory) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapins), *sectors* (sectors swapped in), *pages* (pages swapped in).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.in\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.out\[<device>,<type>\]|<|<|<|<| |<|Swap out (from memory onto device) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapouts), *sectors* (sectors swapped out), *pages* (pages swapped out).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.out\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.size\[<device>,<type>\]|<|<|<|<| |<|Swap space size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*free* (free swap space, default), *pfree* (free swap space, in percent), *pused* (used swap space, in percent), *total* (total swap space), *used* (used swap space)<br>Note that *pfree*, *pused* are not supported on Windows if swap size is 0.<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.size\[,pfree\] → free swap space percentage<br><br>If *device* is not specified Zabbix agent will only take into account swap devices (files), physical memory will be ignored. For example, on Solaris systems *swap -s* command includes a portion of physical memory and swap devices (unlike *swap -l*).<br><br>Note that this key might report incorrect swap space size/percentage on virtualized (VMware ESXi, VirtualBox) Windows platforms. In this case you may use the `perf_counter[\700(_Total)\702]` key to obtain correct swap space percentage.| |system.uname|<|<|<|<| |<|Identification of the system.|String| |Example of returned value (Unix):<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>Example of returned value (Windows):<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>On Unix since Zabbix 2.2.0 the value for this item is obtained with uname() system call. Previously it was obtained by invoking "uname -a". The value of this item might differ from the output of "uname -a" and does not include additional information that "uname -a" prints based on other sources.<br><br>On Windows since Zabbix 3.0 the value for this item is obtained from Win32\_OperatingSystem and Win32\_Processor WMI classes. Previously it was obtained from volatile Windows APIs and undocumented registry keys. The OS name (including edition) might be translated to the user's display language. On some versions of Windows it contains trademark symbols and extra spaces.<br><br>Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture.| |system.uptime|<|<|<|<| |<|System uptime in seconds.|Integer| |In [item configuration](/manual/config/items/item#configuration), use **s** or **uptime** units to get readable values.| |system.users.num|<|<|<|<| |<|Number of users logged in.|Integer| |**who** command is used on the agent side to obtain the value.| |vfs.dev.discovery|<|<|<|<| |<|List of block devices and their type. Used for low-level discovery.|JSON object| |This item is supported on Linux platform only.<br><br>Supported since Zabbix 4.4.0.| |vfs.dev.read\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk read statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 devices (1023 individual and one for *all*).| |vfs.dev.write\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk write statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.write\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 (1023 individual and one for *all*).| |vfs.dir.count\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry count.|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to count, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT count. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT counted.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be counted. Smaller files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be counted. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be counted. More recent entries will not be counted. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be counted. Entries so old and older will not be counted (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never counted.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are counted only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be counted).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial count will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.count\[/dev\] - monitors number of devices in /dev (Linux)<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - monitors number of files in temporary directory (Windows)<br><br>Supported since Zabbix 4.0.0.| |vfs.dir.get\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry list.|JSON|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to list, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT list. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT listed.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be listed. Smaller files will not be listed. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be listed. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be listed. More recent entries will not be listed. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be listed. Entries so old and older will not be listed (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never listed.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are listed only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be listed).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial list will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.get\[/dev\] - retrieves device list in /dev (Linux)<br>⇒ vfs.dir.get\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - retrieves file list in temporary directory (Windows)<br><br>Supported since Zabbix 6.0.0.| |vfs.dir.size\[dir,<regex\_incl>,<regex\_excl>,<mode>,<max\_depth>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory size (in bytes).|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**mode** - possible values:<br>*apparent* (default) - gets apparent file sizes rather than disk usage (acts as `du -sb dir`), *disk* - gets disk usage (acts as `du -s -B1 dir`). Unlike du command, vfs.dir.size item takes hidden files in account when calculating directory size (acts as `du -sb .[^.]* *` within dir).<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Only directories with at least read permission for *zabbix* user are calculated.<br><br>On Windows any symlink is skipped and hard links are taken into account only once.<br><br>With large directories or slow drives this item may time out due to the Timeout setting in [agent](/manual/appendix/config/zabbix_agentd) and [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) configuration files. Increase the timeout values as necessary.<br><br>Examples:<br>⇒ vfs.dir.size\[/tmp,log\] - calculates size of all files in /tmp which contain 'log'<br>⇒ vfs.dir.size\[/tmp,log,\^.+\\.old$\] - calculates size of all files in /tmp which contain 'log', excluding files containing '.old'<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Supported since Zabbix 3.4.0.| |vfs.file.cksum\[file,<mode>\]|<|<|<|<| |<|File checksum, calculated by the UNIX cksum algorithm.|Integer - with `mode` as *crc32*<br><br>String - with `mode` as *md5*, *sha256*|**file** - full path to file<br>**mode** - *crc32* (default), *md5*, *sha256*|Example:<br>=> vfs.file.cksum\[/etc/passwd\]<br><br>Example of returned values (crc32/md5/sha256 respectively):<br>675436101<br>9845acf68b73991eb7fd7ee0ded23c44<br>ae67546e4aac995e5c921042d0cf0f1f7147703aa42bfbfb65404b30f238f2dc<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.contents\[file,<encoding>\]|<|<|<|<| |<|Retrieving contents of a file.|Text|**file** - full path to file<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)|Returns an empty string if the file is empty or contains LF/CR characters only.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Example:<br>=> vfs.file.contents\[/etc/passwd\]<br><br>This item is limited to files no larger than 64 Kbytes.<br><br>Supported since Zabbix 2.0.| |vfs.file.exists\[file,<types\_incl>,<types\_excl>\]|<|<|<|<| |<|Checks if file exists.|0 - not found<br><br>1 - file of the specified type exists|**file** - full path to file<br>**types\_incl** - list of file types to include, possible values: *file* (regular file, default (if types\_excl is not set)), *dir* (directory), *sym* (symbolic link), *sock* (socket), *bdev* (block device), *cdev* (character device), *fifo* (FIFO), *dev* (synonymous with "bdev,cdev"), *all* (all mentioned types, default if types\_excl is set).<br>**types\_excl** - list of file types to exclude, see types\_incl for possible values (by default no types are excluded)|Multiple types must be separated with a comma and the entire set enclosed in quotes "".<br>On Windows the double quotes have to be backslash '\\' escaped and the whole item key enclosed in double quotes when using the command line utility for calling zabbix\_get.exe or agent2.<br><br>If the same type is in both <types\_incl> and <types\_excl>, files of this type are excluded.<br><br>Examples:<br>=> vfs.file.exists\[/tmp/application.pid\]<br>=> vfs.file.exists\[/tmp/application.pid,"file,dir,sym"\]<br>=> vfs.file.exists\[/tmp/application\_dir,dir\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Note that the item may turn unsupported on Windows if a directory is searched within a non-existing directory, e.g. vfs.file.exists\[C:\\no\\dir,dir\] (where 'no' does not exist).| |vfs.file.get\[file\]|<|<|<|<| |<|Return information about a file.|JSON object|**file** - full path to file|Supported file types on UNIX-like systems: regular file, directory, symbolic link, socket, block device, character device, FIFO<br><br>Supported file types on Windows: regular file, directory, symbolic link<br><br>Example:<br>=> vfs.file.get\[/etc/passwd\] → return a JSON with information about the /etc/passwd file (type, user, permissions, SID, uid etc)<br><br>Supported since Zabbix 6.0.| |vfs.file.md5sum\[file\]|<|<|<|<| |<|MD5 checksum of file.|Character string (MD5 hash of the file)|**file** - full path to file|Example:<br>=> vfs.file.md5sum\[/usr/local/etc/zabbix\_agentd.conf\]<br><br>Example of returned value:<br>b5052decb577e0fffd622d6ddc017e82<br><br>The file size limit (64 MB) for this item was removed in version 1.8.6.<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.file.owner\[file,<ownertype>,<resulttype>\]|<|<|<|<| |<|Retrieve owner of a file.|Character string|**file** - full path to file<br>**ownertype** - *user* (default) or *group* (Unix only)<br>**resulttype** - *name* (default) or *id*; for id - return uid/gid on Unix, SID on Windows|Example:<br>=> vfs.file.owner\[/tmp/zabbix\_server.log\] → return file owner of /tmp/zabbix\_server.log<br>=> vfs.file.owner\[/tmp/zabbix\_server.log,,id\] → return file owner ID of /tmp/zabbix\_server.log<br><br>Supported since Zabbix 6.0.| |vfs.file.permissions\[file\]|<|<|<|<| |<|Return a 4-digit string containing the octal number with Unix permissions.|String|**file** - full path to the file|Not supported on Windows.<br><br>Example:<br>=> vfs.file.permissions\[/etc/passwd\] → return permissions of /etc/passwd, for example, '0644'<br><br>Supported since Zabbix 6.0.| |vfs.file.regexp\[file,regexp,<encoding>,<start line>,<end line>,<output>\]|<|<|<|<| |<|Find string in a file.|The line containing the matched string, or as specified by the optional `output` parameter|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|Only the first matching line is returned.<br>An empty string is returned if no line matched the expression.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `start line`, `end line` and `output` parameters are supported from version 2.2.<br><br>Examples:<br>=> vfs.file.regexp\[/etc/passwd,zabbix\]<br>=> vfs.file.regexp\[/path/to/some/file,"(\[0-9\]+)$",,3,5,\\1\]<br>=> vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\] → getting the ID of user *zabbix*| |vfs.file.regmatch\[file,regexp,<encoding>,<start line>,<end line>\]|<|<|<|<| |<|Find string in a file.|0 - match not found<br><br>1 - found|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).|Byte order mark (BOM) is ignored.<br><br>The `start line` and `end line` parameters are supported from version 2.2.<br><br>Example:<br>=> vfs.file.regmatch\[/var/log/app.log,error\]| |vfs.file.size\[file,<mode>\]|<|<|<|<| |<|File size (in bytes).|Integer|**file** - full path to file<br>**mode** - possible values:<br>*bytes* (default) or *lines* (empty lines are counted, too)|The file must have read permissions for user *zabbix*.<br><br>Example:<br>=> vfs.file.size\[/var/log/syslog\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.time\[file,<mode>\]|<|<|<|<| |<|File time information.|Integer (Unix timestamp)|**file** - full path to the file<br>**mode** - possible values:<br>*modify* (default) - last time of modifying file content,<br>*access* - last time of reading file,<br>*change* - last time of changing file properties|Example:<br>=> vfs.file.time\[/etc/passwd,modify\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.fs.discovery|<|<|<|<| |<|List of mounted filesystems and their types. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>The {\#FSDRIVETYPE} macro is supported on Windows since Zabbix 3.0.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.get|<|<|<|<| |<|List of mounted filesystems, their types, disk space and inode statistics. Can be used for low-level discovery.|JSON object| |Supported since Zabbix 4.4.5.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.inode\[fs,<mode>\]|<|<|<|<| |<|Number or percentage of inodes.|Integer - for number<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, //pfree // (free, percentage), *pused* (used, percentage)|Example:<br>=> vfs.fs.inode\[/,pfree\]| |vfs.fs.size\[fs,<mode>\]|<|<|<|<| |<|Disk space in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, *pfree* (free, percentage), *pused* (used, percentage)|In case of a mounted volume, disk space for local file system is returned.<br><br>Example:<br>=> vfs.fs.size\[/tmp,free\]<br><br>Reserved space of a file system is taken into account and not included when using the *free* mode.| |vm.memory.size\[<mode>\]|<|<|<|<| |<|Memory size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**mode** - possible values:<br>*total* (default), *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*, *used*, *pused* (used, percentage), *available*, *pavailable* (available, percentage)<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) support and [additional details](/manual/appendix/items/vm.memory.size_params) for this parameter.|This item accepts three categories of parameters:<br><br>1) *total* - total amount of memory;<br>2) platform-specific memory types: *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*;<br>3) user-level estimates on how much memory is used and available: *used*, *pused*, *available*, *pavailable*.| |web.page.get\[host,<path>,<port>\]|<|<|<|<| |<|Get content of web page.|Web page source as text (including headers)|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |web.page.perf\[host,<path>,<port>\]|<|<|<|<| |<|Loading time of full web page (in seconds).|Float|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |web.page.regexp\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<|<| |<|Find string on a web page.|The matched string, or as specified by the optional `output` parameter|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**length** - maximum number of characters to return<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `output` parameter is supported from version 2.2.<br><br>Example:<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]| |zabbix.stats\[<ip>,<port>\]|<|<|<|<| |<|Return a set of Zabbix server or proxy internal metrics remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).| |zabbix.stats\[<ip>,<port>,queue,<from>,<to>\]|<|<|<|<| |<|Return number of monitored items in the queue which are delayed on Zabbix server or proxy remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**queue** - constant (to be used as is)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.|  
zh-cn	 |键|<|<|<|<| |---|-|-|-|-| |<|**描述**|**返回值**|**参数**|**注释**| |agent.hostmetadata|<|<|<|<| |<|Agent 主机元数据|字符串||返回HostMetadata或HostMetadataItem参数的值，如果没有定义的话返回空字符串<br><br> 自Zabbix 6.0后开始支持| |agent.hostname|<|<|<|<| |<|Agent 主机名。|字符串| |返回:<br>被动模式 - Agent 配置文件中Hostname参数中的列出第一个主机名名称;<br>主动模式 - 当前主机名的名称| |agent.ping|<|<|<|<| |<|Agent 可用性检查|Nothing - 不可用<br><br>1 - 可用| |使用 **nodata()** 触发器函数检查主机不可用| |agent.variant|<|<|<|<| |<|Zabbix agent变量 (Zabbix agent 或 Zabbix agent 2)。|整型| |返回值举例:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |agent.version|<|<|<|<| |<|Zabbix agent版本。|字符串| |返回值举例:<br>6.0.3| |kernel.maxfiles|<|<|<|<| |<|系统支持的最大文件打开数量。|整型| | | |kernel.maxproc|<|<|<|<| |<|系统支持的最大的进程数量.|整型| | | |kernel.openfiles|<|<|<|<| |<|返回当前打开的文件描述符的数量。|整型||自Zabbix6.0以后，Linux才支持此项| |log\[file,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|监控日志文件。|日志|**file** - 日志文件的全路径<br>**regexp** - 正则[表达式](/manual/regular_expressions#overview) 所需要的匹配的模式<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - agent将发送到Zabbix server或proxy的每秒最大行数。此参数覆盖[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中的'MaxLinesPerSecond'值<br>**mode** (自版本 2.0以后)- 可能的值有:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的项目)。<br>**output** (自版本2.2以后) - 一个可选的输出格式模板，  **\\0** 转义序列被替换为文本的匹配部分 (匹配从开始的第一个字符到结束的字符) 而 **\\N** (其中N=1...9) 转义序列被替换为第 N 个匹配组 (或如果 N 超过捕获的组数，则为空字符串)。<br>**maxdelay** (自版本 3.2后) - 最大延迟，以秒为单位。 类型: 浮点型， 值: 0 - (默认) 从不忽略日志文件行; > 0.0 - 忽略旧行， 以便在“maxdelay”秒内分析最新行。使用前请阅读 [maxdelay](log_items#using_maxdelay_parameter) 说明！<br>**options** (自版本 4.4.7以后) - 附件选项:<br>*mtime-noreread* - 非唯一记录, 仅在文件大小更改时重读 (忽略修改时间更改). (从 5.0.2 开始不推荐使用此参数，因为现在忽略了 mtime。)<br>**persistent\_dir** (从 5.0.18、5.4.9 版本开始，仅在 Unix 系统上的 zabbix_agentd 中；在 Agent2 中不支持) - 存储持久性的目录的绝对路径名文件。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明|该项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks)。<br>如果文件丢失或权限不允许访问，监控项变为不受支持。<br><br>如果`output` 留空 - 返回包含匹配文本的整行。 请注意，除 'Result is TRUE' 之外的所有全局正则表达式类型始终返回整个匹配行，并且`output`忽略该参数。<br><br>在agent上使用`output`参数进行内容提取。<br><br>例如:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*使用`output` 参数中从日志记录中提取一个数字 :*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → 将匹配日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并只发送 '6080' 到server。 因为发送的是一个数值, 所以该项目的 "信息类型"可以设置为 "数字(无符号)" 该值可用于图形，触发器等。<br><br>*使用`output` 参数在发送到server之前重写日志记录:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → 将匹配日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并且向服务端发送修改后的记录 "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" 。<br><br>另请参阅 [日志监控](log_items)其他信息。| |log.count\[file,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|监控日志文件中匹配的行数量|整型|**file** - 含全路径的日志文件名称<br>**regexp** - 正则 [表达式](/manual/regular_expressions#overview)匹配的内容模式 <br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - agent 每秒分析新增的最大行数 (不能超过10000)。  在[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中设置的默认值是 10\*'MaxLinesPerSecond'<br>**mode** - 可能的值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的项目)。<br>**maxdelay** - 最大延迟秒数。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志行数; > 0.0 - 忽略旧行 以便在“maxdelay”秒内分析最新行。使用前请阅读[maxdelay](log_items#using_maxdelay_parameter) 说明!<br>**options** (自4.4.7版后) - 附加选项:<br>*mtime-noreread* - 非唯一记录, 仅在文件大小发生更改时重新读取 (忽略修改时间更改). (从5.0.2开始不推荐使用此参数, 因为现在忽略了mtime。)<br>**persistent\_dir** (从 5.0.18、5.4.9 版本开始，仅在 Unix 系统上的 zabbix_agentd 中；在 Agent2 中不支持) - 存储持久性的目录的绝对路径名文件。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明|该项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>如果文件缺失或权限不允许访问，则监控项不受支持。<br><br>另请参阅有关 [日志监控](log_items)的其他信息<br><br>该项不支持Windows的事件日志。<br><br>自 Zabbix 3.2.0版本后开始支持。| |logrt\[file\_regexp,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|监控轮换的日志文件。|日志|**file\_regexp** - 文件的绝对路径和正则[表达式](/manual/regular_expressions#overview)匹配的文件名模式 *请注意* 只有文件名是正则表达式<br>**regexp** - 描述正则[表达式](/manual/regular_expressions#overview)匹配的文件内容模式 <br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - agent 每秒将发送到 Zabbix server 或proxy的最大新行数。 此参数覆盖[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)的 'MaxLinesPerSecond'的值 <br>**mode** (自版本 2.0后) - 可能值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的项目)。<br>**output** (自版本2.2后) - 一个可选的输出格式模板。**\\0** 转义序列被替换文本的匹配部分 (匹配从开始的第一个字符到结束的字符) 而  **\\N** (其中 N=1...9) 转义序列被替换为第N个匹配组 (或如果N超过捕获的组数，则为空字符串)。<br>**maxdelay** (自版本 3.2后) -最大的时延，以秒为单位。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志文件行数; > 0.0 - 忽略旧行，以便在“maxdelay”秒内分析最新行。使用前请阅读 [maxdelay](log_items#using_maxdelay_parameter) 说明!<br>**options** (版本4.0和版本4.4.7后; *mtime-reread*, 和*mtime-noreread*选项 ) - 日志文件轮换类型和其他选项。可能的值:<br>*rotate* (默认),<br>*copytruncate* - 注意的是 *copytruncate* 不能和 *maxdelay*一起使用，在这种情况下 *maxdelay* 必须为0或未指定; 参阅 [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) 文档。<br>*mtime-reread* - 非唯一记录，如果修改时间或大小更改则重新读取(默认),<br>*mtime-noreread* -非唯一记录，仅在大小更改时重新读取 (忽略修改时间更改)。<br>**persistent\_dir** (从 5.0.18, 5.4.9版本开始,仅在Unix系统 zabbix\_agentd中; 不支持 Agent2) - 存储持久文件的目录的绝对路径名。另请参阅有关 [持久文件](log_items#notes-on-persistent-files-for-log-items)的附加说明。|该项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>日志轮换基于文件的最后修改时间。<br><br请注意，logrt 旨在处理一个当前活动的日志文件，并轮换几个其他匹配的非活动文件。例如，如果一个目录有许多活动日志文件，则应为每个文件创建一个单独的 logrt 项。否则，如果一个 logrt 项获取太多文件，可能会导致内存耗尽和监控崩溃。<br><br>如果 `output` 留空 - 返回包含匹配文本的整行。请注意，除 'Result is TRUE' 之外的所有全局正则表达式类型始终返回整个匹配行，并且`output` 忽略该参数.<br><br>在agent上使用`output`参数进行内容提取。<br><br>例如:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}\$",,,100\] → 将匹配文件名如"logfile1"(不会匹配".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}\$","pattern\_to\_match","UTF-8",100\] → 将从文件名如 "logfile\_abc\_1" 或 "logfile\_\_001"中采集数据<br><br>*使用 `output` 参数 从日志记录中提取数字:*<br>=> logrt\[/app1/\^test.\*log\$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] →将匹配一条日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并发送 '6080' 到服务端。 因为发送的数值， 所以此项 "信息类型" 可以设置为 "数字 (无符号)" 这个值可以用于图形，触发器等。<br><br>*使用 `output` 参数可以在发送到服务端前重写日志记录:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → 将匹配一条日志记录  "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并发送修改记录到服务端 "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" 。<br><br>另请参阅 [日志监控](log_items)其他信息。| |logrt.count\[file\_regexp,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|轮换的监控日志文件中的匹配行数|整型|**file\_regexp** - 文件绝对路径和正则 [表达式](/manual/regular_expressions#overview) 所需匹配的文件名模式<br>**regexp** - 正则 [表达式](/manual/regular_expressions#overview) 所需的内容匹配模式<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - agent 每秒分析新增的最大行数 (不能超过10000)。在 [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中设置的默认值是10\*'MaxLinesPerSecond'。<br>**mode** - 可能值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的监控项).<br>**maxdelay** - 最大时延，以秒为单位。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志文件行; > 0.0 - 以便在“maxdelay”秒内分析最新行。使用前请阅读[maxdelay](log_items#using_maxdelay_parameter)说明!<br>**options** (自版本 4.0和4.4.7后; *mtime-reread*和*mtime-noreread* 选项) - 日志文件轮换类型和其他选项， 可能的值:<br>*rotate* (默认),<br>*copytruncate* - 注意 *copytruncate* 不能与 *maxdelay*一起使用，这种情况下 *maxdelay* 必须为0或未指定; 参阅 [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) 说明,<br>*mtime-reread* - 非唯一记录, 如果修改时间或大小改变重新读 (默认),<br>*mtime-noreread* - 非唯一记录, 仅当大小改变时重新读 (忽略修改时间的改变)。<br>**persistent\_dir** (自版本 5.0.18和 5.4.9后, 仅在Unix系统上的zabbix\_agentd中;不支持 Agent2) -  存储持久文件的目录的绝对路径名。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明。|该监控项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>日志轮换基于文件的最后修改时间。<br><br>另请参阅有关[日志监控](log_items)其他信息<br><br>此监控项不支持Windows事件日志<br><br>自Zabbix 3.2.0后开始支持| |modbus.get\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<|<| |<|读取Modbus数据|JSON 对象|**endpoint** - 终端定义为 `protocol://connection_string`<br>**slave id** - 从机 ID<br>**function** - Modbus 函数<br>**address** - 第一个注册地址, 线圈 或输入<br>**count** - 读取的记录数量<br>**type** - 数据类型<br>**endianness** - 字节序配置<br>**offset** - 寄存器数, 从 '地址'开始, 其结果将被丢弃。<br><br>参阅参数的[详细描述](/manual/appendix/items/modbus) 。|自 Zabbix 5.2.0后开始支持| |net.dns\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|检查DNS服务是否启动|0 - DNS 已关闭 (服务器并没有响应或 DNS解析失败)<br><br>1 - DNS 已启动|**ip** - DNS服务器IP地址 (默认DNS服务器上的IP留空,在Windows上忽略)<br>**name** -要查询的DNS名称<br>**type** - 要查询的记录类型 (默认为 *SOA*)<br>**timeout** (在Windows上忽略) -请求超时秒数 (默认是 1 秒)<br>**count** (在在Windows上忽略) -请求的尝试次数 (默认是 2)<br>**protocol** (自版本3.0后) - 用于执行 DNS 查询的协议: *udp* (默认) 或 *tcp*|例如:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>可能的值 `type` 是:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (Windows除外), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>不支持国际化域名，请改用 IDNA 编码名称。<br><br>从 Zabbix 1.8.6 (Unix) 和 2.0.0 (Windows) 开始支持 SRV 记录类型.<br><br>Zabbix 2.0 之前的命名（仍然支持）: *net.tcp.dns*| |net.dns.record\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|执行 DNS 查询。|具有所需信息类型的字符串|**ip** - DNS 服务器的 IP 地址（默认 DNS 服务器留空，在 Windows 上忽略）<br>**name** - 要查询的 DNS 名称<br>**type** - 要查询的记录类型(默认为 *SOA*)<br>**timeout** (在 Windows 上忽略) - 请求超时秒数 (默认是 1 秒)<br>**count** (在 Windows 上忽略) - 请求的尝试次数(默认是2)<br>**protocol**(自 3.0 版起) - 用于执行 DNS 查询的协议: *udp* (默认) 或 *tcp*|例如:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>可能的值 `type` 是:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (Windows除外), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>不支持国际化域名，请改用 IDNA 编码名称。<br><br>从 Zabbix 1.8.6 (Unix) 和 2.0.0 (Windows) 开始支持 SRV 记录类型。<br><br>Zabbix 2.0 之前的命名（仍然支持）: *net.tcp.dns.query*| |net.if.collisions\[if\]|<|<|<|<| |<|Number of out-of-window collisions.|整型|**if** - 网络接口名称| | |net.if.discovery|<|<|<|<| |<|网络接口列表.用于低级别的发现。|JSON 对象| |自 Zabbix 2.0后支持<br><br>在 FreeBSD, OpenBSD 和 NetBSD 上从 Zabbix 2.2后开始支持<br><br>某些Windows版本 (如 Server 2008)可能需要安装最新更新以支持接口名称中的非ASCII 字符。| |net.if.in\[if,<mode>\]|<|<|<|<| |<|网络接口的传入流量统计|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** - 可能的值:<br>*bytes* - 字节数 (默认)<br>*packets* - 包数<br>*errors* - 错误数<br>*dropped* - 丢弃的数据包数量<br>*overruns (fifo)* - FIFO 缓冲错误数<br>*frame* - 数据包帧错误数<br>*compressed* - 设备驱动程序发送或接收的压缩数据包数<br>*multicast* - 设备驱动程序接收的多播帧数|在Windows上, 该监控项从64位计数器中获取值（如果可用），Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent 将使用 32 位计数器。 <br><br>从 Zabbix 1.8.6 开始支持 Windows 上的多字节接口名称<br><br>例如:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>您可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。| |net.if.out\[if,<mode>\]|<|<|<|<| |<|网络接口的传出流量统计|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** - 可能的值:<br>*bytes* - 字节数 (默认)<br>*packets* -包数<br>*errors* - 错误数<br>*dropped* - 丢弃的包的数量<br>*overruns (fifo)* -  FIFO 缓冲错误数 <br>*collisions (colls)* - 接口上检测到的冲突数<br>*carrier* - 在设备驱动程序检测到的载体丢失数<br>*compressed* -设备驱动程序传输的压缩数据包数|在 Windows 上，该项目从 64 位计数器中获取值（如果可用）。Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent 将使用 32 位计数器。<br><br>从 Zabbix 1.8.6 版本开始支持 Windows 上的多字节接口名称。<br><br>例如:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>您可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。| |net.if.total\[if,<mode>\]|<|<|<|<| |<|网络接口上传入和传出流量统计的总和。|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** -可能值:<br>*bytes* - 字节数 (默认)<br>*packets* - 包数<br>*errors* - 错误数<br>*dropped* - 丢弃的数据包数量<br>*overruns (fifo)* -  FIFO缓冲错误数<br>*compressed* - 设备驱动程序发送或接收的压缩数据包数|在 Windows 上，该项目从 64 位计数器中获取值（如果可用）。Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent 将使用 32 位计数器。<br><br>例如:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。<br><br>请注意，仅当 net.if.in 和 net.if.out 都在您平台上的丢弃数据包时，才支持丢弃数据包。| |net.tcp.listen\[port\]|<|<|<|<| |<|检查TCP端口是否处于监听状态|0 - 它不处于监听状态<br><br>1 - 它处于监听状态|**port** - TCP端口号|例如:<br>=> net.tcp.listen\[80\]<br><br> 自 Zabbix 1.8.4后在Linux上支持<br><br>自 Zabbix 3.0.0后, 在 Linux 内核 2.6.14及以上,如果可能，从内核的 NETLINK 接口获取有关侦听 TCP 套接字的信息. 否则，将从 /proc/net/tcp 和 /proc/net/tcp6 文件中检索信息。| |net.tcp.port\[<ip>,port\]|<|<|<|<| |<| 检查是否可以与指定端口建立 TCP 连接。|0 -不能连接<br><br>1 - 能连接|**ip** - IP 或 DNS 名称 (默认是 127.0.0.1)<br>**port** - 端口号|例如:<br>=> net.tcp.port\[,80\] → 可用于测试在端口80上运行Web 服务的可用性<br><br>对于简单的TCP性能测试，使用 net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>请注意，这些检查可能会导致增加系统守护程序日志文件中的额外信息（通常会记录SMTP和SSH会话）。| |net.tcp.service\[service,<ip>,<port>\]|<|<|<|<| |<|检查服务是否正在运行并接受 TCP 连接。|0 - 服务关闭<br><br>1 - 服务正在运行|**service** - 任意一个:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是 127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例如:<br>=> net.tcp.service\[ftp,,45\] → 用于测试在tcp端口45上的FTP服务的可用性.<br><br>请注意，这些检查可能会导致系统守护程序日志文件中出现额外消息（SMTP 和 SSH 会话正在通常记录）。<br><br>目前不支持检查加密协议（如端口 993 上的 IMAP 或端口 995 上的 POP）。作为一种解决方法，请使用 net.tcp.port 进行此类检查。<br><br>仅 Zabbix agent 2 支持在 Windows 上检查 LDAP 和 HTTPS。<br><br>请注意，telnet 检查会查找登录提示（末尾为“：”）。<br><br>请你参阅[已知问题](/manual/installation/known_issues#https_checks)用于检查HTTPS服务。<br><br>从Zabbix2.0后开始支持*https* 和 *telnet* 服务。| |net.tcp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|检查TCP服务的性能。|0 - 服务已关闭<br><br>seconds - 连接到服务花费的时间（秒）|**service** -以下任意一个:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (见 [详细](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是 127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例如:<br>=> net.tcp.service.perf\[ssh\] → 可用于测试来自 SSH 服务器的初始响应速度。<br><br>目前不支持检查加密协议（如端口 993 上的 IMAP 或端口 995 上的 POP）。作为一种解决方法，请使用 net.tcp.service.perf\[tcp,<ip>,<port>\] 进行此类检查。<br><br>仅 Zabbix agent 2 支持在 Windows 上检查 LDAP 和 HTTPS。<br><br>请注意，telnet 检查会查找登录提示（末尾为“：”）。<br><br>请你参阅[已知问题](/manual/installation/known_issues#https_checks)用于检查HTTPS服务。<br><br>从Zabbix2.0后开始支持*https* 和 *telnet* 服务。| |net.tcp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|返回与参数匹配的套接字数|整型|**laddr** - 本地 IPv4/6 地址 或 CIDR 子网<br>**lport** - 本地的端口号或服务名称<br>**raddr** - 远程 IPv4/6 地址或CIDR子网<br>**rport** - 远程端口号或服务名称<br>**state** - 连接状态(*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|Zabbix agent和Zabbix agent 2均在Linux上支持此项，64位 Windows在Zabbix agent 2上支持此项<br><br>例如:<br>=> net.tcp.socket.count\[,80,,,established\] →检查本地 TCP 端口 80 是否处于“已建立”状态<br><br>从 Zabbix 6.0后开始支持此项| |net.udp.listen\[port\]|<|<|<|<| |<|检查UDP端口是否处于监听状态|0 - 它不处于监听状态<br><br>1 -它处于监听状态|**port** - UDP端口号|例如:<br>=> net.udp.listen\[68\]<br><br>在Linux上自Zabbix 1.8.4后支持| |net.udp.service\[service,<ip>,<port>\]|<|<|<|<| |<|检查服务是否正在运行并响应 UDP 请求。|0 - 服务已关闭<br><br>1 - 服务正在运行|**service** - *ntp* (见 [详情](/manual/appendix/items/service_check_details))<br>**ip** -IP地址 (默认是 127.0.0.1)<br>**port** - 端口号(默认为标准服务使用端口号)|例:<br>=> net.udp.service\[ntp,,45\] → 可用于测试 UDP 45 端口 NTP 服务的可用性。<br><br> Zabbix 3.0.0后开始支持此项, 但*ntp* 服务可用于以前版本的 net.tcp.service\[\]监控项中| |net.udp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|检查UDP服务性能。|0 - 服务已关闭<br><br>seconds - 等待服务响应秒数|**service** - *ntp* (见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例:<br>=> net.udp.service.perf\[ntp\] → 可用于测试来自 NTP 服务的响应时间。<br><br>自 Zabbix 3.0.0后开始支持该项，但 *ntp* 服务可用于以前版本的net.tcp.service\[\]监控项中| |net.udp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|返回与参数匹配的 TCP 套接字数。|整型|**laddr** -本地IPv4/6地址或CIDR子网地址<br>**lport** -本地端口号或服务名称<br>**raddr** - 远程IPv4/6地址或CIDR子网<br>**rport** - 远程端口号或服务名称<br>**state** - 连接状态 (*established*, *unconn*)|Zabbix agent和Zabbix agent 2均在Linux上支持此项，64位 Windows在Zabbix agent 2上支持此项。<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → 检查是否有任何 UDP 套接字处于“监听”状态<br><br>从 Zabbix 6.0 开始支持此项| |proc.cpu.util\[<name>,<user>,<type>,<cmdline>,<mode>,<zone>\]|<|<|<|<| |<|进程CPU使用百分比.|浮点型|**name** -进程名 (默认是 *all processes*)<br>**user** - 用户名称 (默认是*all users*)<br>**type** -CPU使用率类型:<br>*total* (默认), *user*, *system*<br>**cmdline** - 可按命令行过滤(它是一个正则[表达式](/manual/regular_expressions#overview))<br>**mode** - 数据搜集模式: *avg1* (默认), *avg5*, *avg15*<br>**zone** - 目标区域: *current* (默认), *all*. 这个参数仅在Solaris平台上支持|例:<br>=> proc.cpu.util\[,root\] → 在root用户下运行的所有进程的CPU使用率<br>=> proc.cpu.util\[zabbix\_server,zabbix\] →在zabbix用户下运行的所有 zabbix\_server 进程的CPU使用率<br><br>T返回值基于单个 CPU 核心利用率百分比。例如，完全使用两个内核的进程的 CPU 利用率为 200%。<br><br>进程 CPU 利用率数据由支持最多 1024 个唯一（按名称、用户和命令行）查询的收集器收集。在过去 24 小时内未访问的查询将从收集器中删除。<br><br>*请注意* 将zone参数设置为*current* （或默认值）如果 agent 已在不支持区域的 Solaris 上编译，但在支持区域的较新 Solaris 上运行，则 agent 将返回 NOTSUPPORTED（ agent 不能将结果限制为仅当前区域）。但是，在这种情况下，*all*都支持。<br><br>自 Zabbix 3.0.0 起支持此键，并且可在多个平台上使用 (请参阅 [平台支持的监控项](/manual/appendix/items/supported_by_platform))。| |proc.mem\[<name>,<user>,<mode>,<cmdline>,<memtype>\]|<|<|<|<| |<|进程使用的内存（以字节为单位）|整型 - 当 `mode` 为 *max*, *min*, *sum*时<br><br>浮点数 - 当 `mode` 为 *avg*时|**name** -进程名 (默认是 *all processes*)<br>**user** - 用户名 (默认是 *all users*)<br>**mode** - 可能的值:<br>*avg*, *max*, *min*, *sum* (默认)<br>**cmdline** - 按命令行过滤(它是一个正则 [表达式](/manual/regular_expressions#overview))<br>**memtype** - 进程使用的[内存类型](/manual/appendix/items/proc_mem_notes) |例如:<br>=> proc.mem\[,root\] → 运行在root用户下的所有进程使用的内存<br>=> proc.mem\[zabbix\_server,zabbix\] → 运行在zabbix用户下的所有zabbix\_server进程使用的内存<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → 在oracle用户下，包含有oracleZABBIX命令行运行的所有内存最多的内存<br><br>*需要注意*:当多个进程使用共享内存时，进程使用的内存总和可能会导致大到不切实际。<br><br>参考 [说明](/manual/appendix/items/proc_mem_num_notes) 关于选择进程 `name` 和 `cmdline` 参数 (指定为Linux).<br><br>当此项从命令行调用并包含命令行参数时 (例如 使用 agent 测试模式: `zabbix_agentd -t proc.mem[,,,apache2]`), 一个额外的进程将被计算在内，因为 agent 将计算自己。<br><br>从Zabbix3.0.0起， `memtype` 参数开始支持多个 [平台](/manual/appendix/items/supported_by_platform) | |proc.num\[<name>,<user>,<state>,<cmdline>,<zone>\]|<|<|<|<| |<|进程数量|整型|**name** - 进程名称 (默认为 *all processes*)<br>**user** - 用户名 (默认为 *all users*)<br>**state** (*disk* 和 *trace* 选项从3.4.0起) - 可能值:<br>*all* (默认),<br>*disk* - 不间断睡眠,<br>*run* - 运行,<br>*sleep* - 可中断的睡眠,<br>*trace* - 停止,<br>*zomb* - 僵尸<br>**cmdline** - 按命令行过滤(它是一个正则[表达式](/manual/regular_expressions#overview))<br>**zone** -目标区域: *current* (默认), *all*. 此参数仅在 Solaris 上受支持。|例如:<br>=> proc.num\[,mysql\] → 在mysql用户下运行的进程数<br>=> proc.num\[apache2,www-data\] → www-data 用户下运行的 apache2 进程数<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → 在oracleZABBIX命令行下的oracle用户运行的睡眠状态进程数<br><br> [说明](/manual/appendix/items/proc_mem_num_notes) 关于选择进程 `name` 和 `cmdline` 参数 (指定于Linux)。<br><br>在Windows上仅支持`name`和`user`参数<br><br>当此项从命令行调用并包含命令行参数时 (例如 使用 agent 测试模式: `zabbix_agentd -t proc.num[,,,apache2]`), 一个额外的进程将被计算在内，因为 agent 将计算自己。<br><br>*请注意* 将zone参数设置为*current* （或默认值）如果 agent 已在不支持区域的 Solaris 上编译，但在支持区域的较新 Solaris 上运行，则 agent 将返回 NOTSUPPORTED（ agent 不能将结果限制为仅当前区域）。但是，在这种情况下，*all*都支持。| |sensor\[device,sensor,<mode>\]|<|<|<|<| |<|硬件传感器读数|浮点型|**device** - 设备名称<br>**sensor** - 传感器名称<br>**mode** - 可能的值:<br>*avg*, *max*, *min* (如果省略此参数，设备和传感器将逐字处理).|在linux2.4上读取 /proc/sys/dev/sensors <br><br>例如:<br>=> sensor\[w83781d-i2c-0-2d,temp1\]<br><br>在 Zabbix 1.8.4之前,  *sensor\[temp1\]* 格式被使用。| |^|^|^|^|在Linux2.6+上读取 /sys/class/hwmon <br><br>请参阅Linux [sensor](/manual/appendix/items/sensor)项目中 更详细的说明| |^|^|^|^|读取OpenBSD上的 *hw.sensors* MIB <br><br>例如:<br>=> sensor\[cpu0,temp0\] → 一个CPU的温度<br>=> sensor\["cpu\[0-2\]$",temp,avg\] → 前三个CPU温度的平均值<br><br>自Zabbix 1.8.4后开始支持OpenBSD| |system.boottime|<|<|<|<| |<|系统启动时间。|整型 (Unix时间戳)| | | |system.cpu.discovery|<|<|<|<| |<|检测到的CPU/CPUs的内核列表，用于低级别发现。|JSON 对象| |自2.4.0后，支持所有平台| |system.cpu.intr|<|<|<|<| |<|设备中断。|整型| | | system.cpu.load\[<cpu>,<mode>\]|<|<|<|<| |<|[CPU 负载](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - possible values:<br>*all* (default), *percpu* (从版本2.0开始; 总负载除以在线CPU数)<br>**mode** - 可能的值：<br>*avg1* (一分钟的平均值，默认), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |system.cpu.num\[<type>\]|<|<|<|<| |<|CPU数量。|Integer|**type** - 可能的值：<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |system.cpu.switches|<|<|<|<| |<|上下文切换次数。|整型| | | |system.cpu.util\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<|<| |<|CPU 利用率百分比。|浮点型|**cpu** - *<CPU number>* or *all* (default)<br>**type** - 可能的值：<br>*user* (default), *idle*, *nice*, *system* （Windows默认）, *iowait*, *interrupt*, *softirq*, *steal*, *guest* (Linux内核版本2.6.24及以上), *guest\_nice* (Linux内核版本2.6.33及以上).<br>可在[平台特性](/manual/appendix/items/supported_by_platform) 查看更多此参数的细节。<br>**mode** - 可能的值：<br>*avg1* (一分钟的平均值，默认), *avg5*, *avg15*<br>**logical\_or\_physical** (从5.0.3版本开始; 仅支持AIX) - 可能的值： *logical* （默认）, *physical*. 此参数仅支持AIX。|Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>曾用名: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |system.hostname\[<type>, <transform>\]|<|<|<|<| |<|系统主机名|字符串|**type** (在版本5.4.7前仅支持Windows) - 可能的值： *netbios* （Windows默认）, *host* (Linux默认), *shorthost* (从5.4.7版本开始; 返回第一个"."前的主机名或在没有"."时返回完整的主机名).<br>**transform** (从5.4.7版本开始) - 可能的值：<br>*none* （默认）, *lower* (转换到小写)|这个值通过Windows的函数 GetComputerName() (**netbios**)或者gethostname() (**host**) 和其他操作系统的 "hostname" 命令获取。<br><br>返回值示例：<br>*在Linux上*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>可查看[更详细的描述](/manual/appendix/install/windows_agent#configuration).| |system.hw.chassis\[<info>\]|<|<|<|<| |<|板卡信息。|字符串|**info** - one of full （默认）, model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>这个键依赖于[SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) 表的可用性。<br>会尝试从sysfs读取DMI表, 如果访问sysfs 失败，会尝试直接读取内存。<br><br>需要**Root权限**因为这个值是通过读取 sysfs 或 memory 获得的。<br><br>从Zabbix 2.0开始支持。| |system.hw.cpu\[<cpu>,<info>\]|<|<|<|<| |<|CPU 信息。|字符串或整型|**cpu** - *<CPU number>* or *all* （默认）<br>**info** - 可能的值：<br>*full* （默认）, *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>从/proc/cpuinfo 和 /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq 获取信息。<br><br>如果设置了CPU数和 *curfreq* 或 *maxfreq*，会返回数字值(Hz)。<br><br>从Zabbix 2.0开始支持。| |system.hw.devices\[<type>\]|<|<|<|<| |<|PCI或USB设备列表。|文本|**type** (从版本2.0开始) - *pci* （默认） or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>返回lspci或lsusb程序的结果（不带参数执行）。| |system.hw.macaddr\[<interface>,<format>\]|<|<|<|<| |<|MAC地址列表。|字符串|**interface** - *all* （默认）或 [正则表达式](/manual/regular_expressions#overview)<br>**format** - *full* （默认） 或 *short*|列出接口名称匹配`接口`[正则表达式](/manual/regular_expressions#overview)的MAC地址列表(*all* 列出所有接口).<br><br>示例：<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If 如果`format`被设为*short*，接口名称和重复的MAC地址将不会列出。<br><br>从Zabbix 2.0开始支持。| |system.localtime\[<type>\]|<|<|<|<| |<|系统时间。|整型 - `type`是*utc*时<br><br>字符串 - `type`是*local*时|**type** (从版本2.0开始) - 可能的值：<br>*utc* - （默认）从 (00:00:00 UTC, January 1, 1970) 开始计算的时间, 单位是秒。<br>*local* - 格式为'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm'的时间<br>|只能用于[被动检查](/manual/appendix/items/activepassive#passive_checks)。<br><br>示例：<br>=> system.localtime\[local\] → 用这个键创建一个监控项用于在*Clock* [仪表盘组件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock)展示主机时间。| |system.run\[command,<mode>\]|<|<|<|<| |<|在主机上运行特定的命令。|命令的文本结果<br><br>1 - `mode`为*nowait*时(无论命令结果如何)|**command** - 待执行的命令<br>**mode** - 可能的值：<br>*wait* - 等待执行结束（默认）,<br>*nowait* - 不等待|包括被截取的空白符，最大可以返回512KB的数据。<br>命令的输出必须是文本才能正常处理。<br><br>示例：<br>=> system.run\[ls -l /\] → 根目录的详细文件列表。<br><br>*Note*: system.run监控项默认被禁用。在[启用监控项](/[[/manual/config/items/restrict_checks)学习如何启用。<br><br>这个监控项的返回值是命令产生的标准输出和标准错误，未检查退出码。<br><br>从 Zabbix 2.4.0 开始允许空结果。<br>也可查看[命令执行](/manual/appendix/command_execution)。| |system.stat\[resource,<type>\]|<|<|<|<| |<|系统统计数据。|整型或浮点型|**ent** - 该区域可获取的处理器单元数量（浮点型）<br>**kthr,<type>** - 关于内核线程状态的信息:<br>*r* - 可运行的内核线程的平均数（浮点型）<br>*b* - 虚拟内存管理器等待队列中内核线程的平均数（浮点型）<br>**memory,<type>** - 虚拟和实际内存的使用信息：<br>*avm* - 活跃的虚拟页 (整型)<br>*fre* - 可用列表的大小 (整型)<br>**page,<type>** - 页错误和分页活动的信息：<br>*fi* - 每秒文件入页（浮点型）<br>*fo* - 每秒文件出页 （浮点型）<br>*pi* - 从分页空间入页（浮点型）<br>*po* - 向分页空间出页（浮点型）<br>*fr* - 页释放（页替换）（浮点型）<br>*sr* - 通过页替换算法扫描到的页（浮点型）<br>**faults,<type>** - 陷阱和中断率：<br>*in* - 设备中断（浮点型）<br>*sy* - 系统调用（浮点型）<br>*cs* - 内核线程上下文切换 （浮点型）<br>**cpu,<type>** - 处理器时间的分类百分比：<br>*us* - 用户时间（浮点型）<br>*sy* - 系统时间（浮点型）<br>*id* - 空闲时间（浮点型）<br>*wa* - 系统在磁盘或网络文件系统I/O请求多时的空闲时间（浮点型）<br>*pc* - 物理处理器消耗的时间（浮点型）<br>*ec* - 标称计算能力的消耗的百分比（浮点型）<br>*lbusy* - 在用户级和系统级运行时，逻辑处理器的使用百分比 （浮点型）<br>*app* - 共享池中可用物理处理器数量（浮点型）<br>**disk,<type>** - 磁盘统计信息：<br>*bps* - 磁盘驱动器传输的数据量，单位是字节/秒（整型）<br>*tps* - 发送给物理磁盘/磁带的每秒传输次数（浮点型）|<| |<|^|^|Comments|<| |<|^|^|从Zabbix 1.8.1开始，此监控项仅被AIX[支持](/manual/appendix/items/supported_by_platform)。<br>请注意这些监控项的以下限制：<br>=> system.stat\[cpu,app\] - 仅支持"Shared"类型的AIX LPAR<br>=> system.stat\[cpu,ec\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR（"Dedicated"一直返回100（百分比））<br>=> system.stat\[cpu,lbusy\] - 仅支持"Shared"类型的AIX LPAR<br>=> system.stat\[cpu,pc\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR<br>=> system.stat\[ent\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR|<| |system.sw.arch|<|<|<|<| |<|软件架构信息。|字符串| |示例：<br>=> system.sw.arch → i686<br><br>通过uname()函数获取信息。<br><br>从Zabbix 2.0开始支持。| |system.sw.os\[<info>\]|<|<|<|<| |<|操作系统信息。|字符串|**info** - 可能的值：<br>*full* （默认）, *short* or *name*|示例：<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>信息通过以下方式（请注意并非所有发行版本都存在所有文件和选项）获取：<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME 参数在支持的系统从/etc/os-release获取，或/etc/issue.net (*name*)<br><br>从Zabbix 2.0开始支持。| |system.sw.packages\[<package>,<manager>,<format>\]|<|<|<|<| |<|已安装的包列表。|文本|**package** - *all* （默认） 或[正则表达式](/manual/regular_expressions#overview)<br>**manager** - *all* （默认）或包管理器<br>**format** - *full* （默认）或*short*|按首字母顺序，列出匹配`package`[正则表达式](/manual/regular_expressions#overview)的已安装的包名 (*all* 列出全部).<br><br>示例：<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>支持的包管理器（执行的命令）：<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>如果`format`设为*full*，包按照包管理器分组（每个包管理器在单独的行，开头是方括号中的包管理器名称）。<br>如果`format`设为*short*，包不会分组，会列在一行中。<br><br>从Zabbix 2.0开始支持。| |system.swap.in\[<device>,<type>\]|<|<|<|<| |<|交换入（从设备到内存）统计|整型|**device** - 用于交换的设备（默认是*all*）<br>**type** - 可能的值：<br>*count* （交换入的数量）, *sectors* （交换入的分区）, *pages* （交换入的页）.<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.in\[,pages\]<br><br>此信息的来源是：<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.out\[<device>,<type>\]|<|<|<|<| |<|交换出（从内存到设备）统计。|整型|**device** - 用于交换的设备（默认是*all*）<br>**type** - 可能的值：<br>*count* （交换出的数量）， *sectors* （交换出的分区）, *pages* （交换出的页）。<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.out\[,pages\]<br><br>此信息的来源是：<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.size\[<device>,<type>\]|<|<|<|<| |<|交换区空间大小，字节数或总量的百分比。|Integer - 字节数的类型<br><br>Float - 百分比的类型|**device** - 用于交换的设备(默认是*all*)<br>**type** - 可能的值：<br>*free* (空闲交换空间，默认), *pfree* (空闲交换空间的百分比), *pused* (已用交换空间的百分比), *total* (总交换空间), *used* (已用交换空间)<br>请注意 *pfree*, *pused* 在交换空间为0时不支持Windows。<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.size\[,pfree\] → 空闲交换空间的百分比<br><br>如果未设置*device*的值，Zabbix agent仅会考虑账户交换设备（文件），忽略物理内存。比如，在 Solaris 系统 *swap -s* 命令包括物理内存的一部分以及交换设备（不同于*swap -l*）。<br><br>请注意此键在虚拟化（VMware ESXi, VirtualBox）Windows平台可能报告错误的交换空间大小/百分比。在这种情况下你可使用`perf_counter[\700(_Total)\702]`键来获取正确的交换空间百分比。| |system.uname|<|<|<|<| |<|系统标识|字符串| |返回值实例（Unix）：<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>返回值实例（Windows）：<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>在 Unix，从 Zabbix 2.2.0 开始，此值通过uname()系统调用获取，在此之前通过调用"uname -a"获取。此监控项的值可能和"uname -a"的输出不同，并且不包括"uname -a"打印的从其他来源获取的额外信息。<br><br>在 Windows 系统，从 Zabbix 3.0 开始，此值通过 Win32\_OperatingSystem 和 Win32\_Processor WMI 类获取。在此之前通过不稳定的 Windows APIs 和无稳定的注册表键获取。OS名（包括版本）可能被翻译到了用户的显示语言。在 Windows 的某些版本，OS 名包括商标符号和额外的空格。<br><br>请注意在Windows，此监控项返回 OS 架构，而在 Unix 返回 CPU 架构。| |system.uptime|<|<|<|<| |<|系统运行时间，单位是秒。|整型| |在[监控项配置](/manual/config/items/item#configuration)中，使用 **s** or **uptime** 单位获取可读的值。| |system.users.num|<|<|<|<| |<|用户登录数|整型| |**who** 命令是用于在agent处获取值的。| |vfs.dev.discovery|<|<|<|<| |<|块设备和类型的列表，用于低级别自动发现。|JSON 对象| |此监控项仅支持Linux平台。<br><br>从 Zabbix 4.4.0 开始支持。| |vfs.dev.read\[<device>,<type>,<mode>\]|<|<|<|<| |<|磁盘读取统计信息。|整型 - 当`type`在 *sectors*, *operations*, *bytes* 中时<br><br>浮点型 - 当`type`在 *sps*, *ops*, *bps* 中时<br><br>*注意*: 如果更新间隔在3小时及以上时^**[2](#footnotes)**^, 会一直返回 '0'|**device** - 磁盘设备（默认是 *all* ^**[3](#footnotes)**^）<br>**type** - 可能的值： *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>请注意'type'在各平台的支持和默认情况，在[平台特性](/manual/appendix/items/supported_by_platform)查看详情。<br>*sps*, *ops*, *bps* 分别代表： sectors, operations, bytes 每秒的值。<br>**mode** - 可能的值： *avg1* (一分钟的平均值，默认), *avg5*, *avg15*.<br>此参数仅支持`type` 在 sps, ops, bps中的情况。|你也可使用相关设备名称（如`sda`）加 /dev/ 前缀（如`/dev/sda`）。<br><br>支持 LVM 逻辑卷。<br><br>不同操作系统的'type'默认值：<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>示例：<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* 在支持的平台曾经支持8个设备（7个单独的和一个*all*）。从 Zabbix 2.0.1 开始这个限制是1024个设备（1023个单独的和一个*all*）。| |vfs.dev.write\[<device>,<type>,<mode>\]|<|<|<|<| |<|磁盘写入统计信息。|整型 - 当`type`在 *sectors*, *operations*, *bytes* 中时<br><br>浮点型 - 当`type`在 *sps*, *ops*, *bps* 中时<br><br>*注意*: 如果更新间隔在3小时及以上时^**[2](#footnotes)**^, 会一直返回 '0'|**device** - 磁盘设备（默认是 *all* ^**[3](#footnotes)**^）<br>**type** - 可能的值： *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>请注意'type'在各平台的支持和默认情况，在[平台特性](/manual/appendix/items/supported_by_platform)查看详情。<br>*sps*, *ops*, *bps* 分别代表： sectors, operations, bytes 每秒的值。<br>**mode** - 可能的值： *avg1* (一分钟的平均值，默认), *avg5*, *avg15*.<br>此参数仅支持`type` 在 sps, ops, bps中的情况。|你也可使用相关设备名称（如`sda`）加 /dev/ 前缀（如`/dev/sda`）。<br><br>支持 LVM 逻辑卷。<br><br>不同操作系统的'type'默认值：<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>示例：<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* 在支持的平台曾经支持8个设备（7个单独的和一个*all*）。从 Zabbix 2.0.1 开始这个限制是1024个设备（1023个单独的和一个*all*）。| |vfs.dir.count\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|目录条目计数。|整型|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号连接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**types\_incl** - 要计数的目录条目类型, 可能的值：<br>*file* - 常规文件, *dir* - 子目录, *sym* - 符号链接, *sock* - 套接字, *bdev* - 块设备, *cdev* - 字符设备, *fifo* - FIFO, *dev* - "bdev,cdev"同义词, *all* - 所有类型 （默认）, 即 "file,dir,sym,sock,bdev,cdev,fifo".多种类型时需在双引号中用逗号隔开。<br>**types\_excl** - 不需要计数的目录条目类型 (见 <types\_incl>)。 如果某些条目类型同时位于 <types\_incl> 和 <types\_excl>中, 则不计算此类型的目录条目。<br>**max\_depth** - 遍历的子目录最大深度 **-1** （默认） - 无限制, **0** -不涉及子目录。<br>**min\_size** -要计数文件的最小大小（以字节为单位）。 小于此的文件不会被计算在内，[内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用。<br>**max\_size** - 要计数文件的最大大小（以字节为单位），大于此的文件将不会被计算在内。 [内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用<br>**min\_age** - 要计数的目录条目最小创建时间（以秒为单位）。最新的条目不进行计数。 [时间后缀](/manual/appendix/suffixes#time_suffixes) 可以被使用。<br>**max\_age** - 要计数的目录条目最大创建时间（以秒为单位）。 比此旧的条目将不被计算在内 (修改时间)。 [时间后缀](/manual/appendix/suffixes#time_suffixes) can 可以被使用.<br>**regex\_excl\_dir** - 述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|不支持的环境变量, 如 %APP\_HOME%, $HOME 和 %TEMP% 。<br><br>伪目录 "." 和 ".." 不会被计算在内。<br><br>目录遍历不会跟踪符号链接。<br><br>在Windows上， 目录符号链接被跳过，硬链接只计算一次。<br><br>在计算条目大小时， `regex_incl` 和 `regex_excl` 都被应用于文件和目录， 但在选择要遍历的子目录时被忽略 (如果 regex\_incl 是 “(?i)\^.+\\.zip$” 并且 max\_depth 未设置, 那么所有子目录都将是遍历，但只会计算 zip 类型的文件)。<br><br>执行时间受限于 agent [配置](/manual/appendix/config/zabbix_agentd) (3秒)的默认时间设置，由于大目录遍历可能需要更长的时间，因此不会返回任何数据并且该监控项项将变为不受支持。 部分计数将不予返回<br><br>当按照大小过滤时，只有常规文件的大小具有意义，在Linux和BSD下 ，目录也有非零大小 (通常只有几KB)。设备大小为0 如  **/dev/sda1**的大小不反映相应分区的大小。因此，在使用 `<min_size>` 和 `<max_size>`, 建议指定 `<types_incl>` 为 "*file*",防止出现意外。<br><br>例如:<br>⇒ vfs.dir.count\[/dev\] - 监控 /dev (Linux)中的设备数量<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - 监控临时目录下的文件数量 (Windows)<br><br>自 Zabbix 4.0.0后支持。| |vfs.dir.get\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|目录条目列表|JSON|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号连接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**types\_incl** - 要计数的目录条目类型, 可能的值：<br>*file* - 常规文件, *dir* - 子目录, *sym* - 符号链接, *sock* - 套接字, *bdev* - 块设备, *cdev* - 字符设备, *fifo* - FIFO, *dev* - "bdev,cdev"同义词, *all* - 所有类型 （默认）, 即 "file,dir,sym,sock,bdev,cdev,fifo".多种类型时需在双引号中用逗号隔开。<br>**types\_excl** - 不需要计数的目录条目类型 (见 <types\_incl>)。 如果某些条目类型同时位于 <types\_incl> 和 <types\_excl>中, 则不计算此类型的目录条目。<br>**max\_depth** - 遍历的子目录最大深度 **-1** （默认） - 无限制, **0** -不涉及子目录。<br>**min\_size** -要计数文件的最小大小（以字节为单位）。 小于此的文件不会被计算在内，[内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用。<br>**max\_size** - 要计数文件的最大大小（以字节为单位），大于此的文件将不会被计算在内。 [内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用<br>**min\_age** - 要计数的目录条目最小创建时间（以秒为单位）。最新的条目不进行计数。 [时间后缀](/manual/appendix/suffixes#time_suffixes) 可以被使用。<br>**max\_age** - 要计数的目录条目最大创建时间（以秒为单位）。 比此旧的条目将不被计算在内 (修改时间)。 [时间后缀](/manual/appendix/suffixes#time_suffixes) can 可以被使用.<br>**regex\_excl\_dir** - 述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|不支持的环境变量, 如 %APP\_HOME%, $HOME 和 %TEMP% 。<br><br>伪目录 "." 和 ".." 不会被计算在内。<br><br>目录遍历不会跟踪符号链接。<br><br>在Windows上， 目录符号链接被跳过，硬链接只计算一次。<br><br>在计算条目大小时， `regex_incl` 和 `regex_excl` 都被应用于文件和目录， 但在选择要遍历的子目录时被忽略 (如果 regex\_incl 是 “(?i)\^.+\\.zip$” 并且 max\_depth 未设置, 那么所有子目录都将是遍历，但只会计算 zip 类型的文件)。<br><br>执行时间受限于 agent [配置](/manual/appendix/config/zabbix_agentd) (3秒)的默认时间设置，由于大目录遍历可能需要更长的时间，因此不会返回任何数据并且该监控项项将变为不受支持。 部分计数将不予返回<br><br>当按照大小过滤时，只有常规文件的大小具有意义，在Linux和BSD下 ，目录也有非零大小 (通常只有几KB)。设备大小为0 如  **/dev/sda1**的大小不反映相应分区的大小。因此，在使用 `<min_size>` 和 `<max_size>`, 建议指定 `<types_incl>` 为 "*file*",防止出现意外。<br><br>例如:<br>⇒ vfs.dir.count\[/dev\] - 监控 /dev (Linux)中的设备数量<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - 监控临时目录下的文件数量 (Windows)<br><br>自 Zabbix 6.0.0后支持。| |vfs.dir.size\[dir,<regex\_incl>,<regex\_excl>,<mode>,<max\_depth>,<regex\_excl\_dir>\]|<|<|<|<| |<|目录大小(以字节为单位).|整型|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号连接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**mode** - 可能的值：<br>*apparent* （默认） - 获取明确文件大小而不是磁盘使用情况( `du -sb dir`), *disk* - 获取磁盘使用情况 ( `du -s -B1 dir`)。与du 命令不同, vfs.dir.size 监控项在计算目录大小会考虑隐藏文件 (`du -sb .[^.]* *` 在目录中起作用).<br>**max\_depth** -目录遍历的最大深度。 **-1** （默认） - 无限制, **0** -不下钻到子目录<br>**regex\_excl\_dir** - 述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|只计算 *zabbix* 用户至少可读权限的目录<br><br>在Windows上任何软链接被跳过，硬链接只计算一次<br><br>对于大型目录或慢速驱动器，此监控项可能会根据 [agent](/manual/appendix/config/zabbix_agentd) 和 [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 配置文件中的超时设置而超时，可以根据需要设置超时值。<br><br>示例:<br>⇒ vfs.dir.size\[/tmp,log\] - 计算 /tmp目录中包含 'log'的所有文件大小；<br>⇒ vfs.dir.size\[/tmp,log,\^.+\\.old$\] -计算 /tmp目录中包含'log'的所有文件大小，排除文件中包含'.old'的文件。<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support)。<br><br>自Zabbix 3.4.0后开始支持| |vfs.file.cksum\[file,<mode>\]|<|<|<|<| |<|文件校验和，由 UNIX cksum 算法计算得出。|整型 -`mode` 作为 *crc32*<br><br>字符串 -  `mode` 作为 *md5*, *sha256*|**file** - 文件模式的全路径<br>**mode** - *crc32* （默认）, *md5*, *sha256*|示例：<br>=> vfs.file.cksum\[/etc/passwd\]<br><br>返回值示例 (分别为crc32/md5/sha256):<br>675436101<br>9845acf68b73991eb7fd7ee0ded23c44<br>ae67546e4aac995e5c921042d0cf0f1f7147703aa42bfbfb65404b30f238f2dc<br><br>文件大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>自 Zabbix 6.0后开始支持`mode` 参数| |vfs.file.contents\[file,<encoding>\]|<|<|<|<| |<|检索文件的内容。|文本|**file** - 文件的全路径<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)|如果文件为空或仅包含 LF/CR 字符，则返回空字符串。<br><br>字节顺序标记 (BOM) 从输出中排除。<br><br>示例：<br>=> vfs.file.contents\[/etc/passwd\]<br><br>此监控项仅限于不大于 64 KB 的文件。<br><br>从Zabbix 2.0开始支持。| |vfs.file.exists\[file,<types\_incl>,<types\_excl>\]|<|<|<|<| |<|检查文件是否存在。|0 -没有找到<br><br>1 - 指定文件类型存在|**file** - 文件的完整路径。<br>**types\_incl** - 包含的文件类型列表, 可能的值： *file* (常规文件，默认 (如果 types\_excl未设置)), *dir* (目录), *sym* (符号链接), *sock* (套接字), *bdev* (块设备), *cdev* (字符设备), *fifo* (FIFO), *dev* (与 "bdev,cdev"同义), *all* (所有提到的类型，默认为如果 types\_excl设置的值)。<br>**types\_excl** - 排除的文件类型列表, 参阅 types\_incl 获取可能的值 (默认情况下不排除任何类型)|多个类型必须用逗号分隔，整个集合用 引号""括起来.<br>在Windows上，当使用命令行调用zabbix\_get.exe或agent2时，双引号必须用反斜杠 '\\' 转义，并且整个项目键用双引号括起来。<br><br>如果 <types\_incl> 和 <types\_excl>中的类型相同,则排除此类型的文件<br><br>例如:<br>=> vfs.file.exists\[/tmp/application.pid\]<br>=> vfs.file.exists\[/tmp/application.pid,"file,dir,sym"\]<br>=> vfs.file.exists\[/tmp/application\_dir,dir\]<br><br>文件大小取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>请注意，如果在不存在的目录中搜索目录，例如vfs.file.exists\[C:\\no\\dir,dir\] (其中不存在 'no')则该监控项可能会在Windows上变为不受支持| |vfs.file.get\[file\]|<|<|<|<| |<|返回有关文件的信息。|JSON 对象|**file** - 文件的全路径|类 UNIX 系统上支持的文件类型: 常规文件,、目录、 符号链接、套接字、块设备、字符设备、FIFO<br><br>Windows 上支持的文件类型：常规文件、目录、符号链接<br><br>示例：<br>=> vfs.file.get\[/etc/passwd\] → 返回一个 JSON，其中包含有关 /etc/passwd 文件的信息(类型、用户、权限、SID、uid 等)<br><br>自Zabbix 6.0后开始支持| |vfs.file.md5sum\[file\]|<|<|<|<| |<|文件的MD5校验和。|字符串 (MD5的哈希文件)|**file** - 文件的全路径|示例：<br>=> vfs.file.md5sum\[/usr/local/etc/zabbix\_agentd.conf\]<br><br>示例的返回值:<br>b5052decb577e0fffd622d6ddc017e82<br><br>版本 1.8.6 中删除了此项目的文件大小限制 (64 MB)。<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support)。| |vfs.file.owner\[file,<ownertype>,<resulttype>\]|<|<|<|<| |<|检索文件的所有者|字符串|**file** - 文件的全路径<br>**ownertype** - *user* （默认） 或 *group* (仅Unix)<br>**resulttype** - *name* （默认） 或 *id*; 对于id - 在Unix上返回 uid/gid，Windows上返回SID|示例：<br>=> vfs.file.owner\[/tmp/zabbix\_server.log\] → 返回/tmp/zabbix\_server.log文件所有者<br>=> vfs.file.owner\[/tmp/zabbix\_server.log,,id\] → 返回 /tmp/zabbix\_server.log文件所有者id<br><br>自Zabbix 6.0后开始支持。| |vfs.file.permissions\[file\]|<|<|<|<| |<|返回一个 4 位字符串，其中包含具有 Unix 权限的八进制数。|字符串|**file** - 文件的全路径|在Windows上不支持<br><br>示例：<br>=> vfs.file.permissions\[/etc/passwd\] →返回/etc/passwd的文件权限, 例如, '0644'<br><br>自Zabbix 6.0后开始支持| |vfs.file.regexp\[file,regexp,<encoding>,<start line>,<end line>,<output>\]|<|<|<|<| |<|在文件中查找字符串。|包含匹配字符串的行，或由可选 `output` 参数指定的行|**file** - 文件的全路径<br>**regexp** - 描述所需模式编码的正则[表达式](/manual/regular_expressions#overview)<br>**encoding** - 编码[标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - 要搜索的第一行(默认为文件的第一行).<br>**end line** - 要搜索的最后一行的编号(默认为文件的最后一行)。<br>**output** - 可选的输出格式模板 **\\0** 转义序列被替换为匹配的文本部分(从匹配开始的第一个字符到匹配结束的字符) 而 **\\N** (其中 N=1...9) 转义序列被替换为第N个匹配组 (如果N超过捕获组的数量，则为空字符串)。|仅返回第一个匹配行。<br>如果没有行匹配表达式，则返回一个空字符串。<br><br>字节顺序标记 (BOM) 从输出中排除。<br><br>使用该参数的内容提取`output`发生在 agent 上。<br><br>从2.2版本开始支持 `start line`, `end line` and `output` 参数。<br><br>例如:<br>=> vfs.file.regexp\[/etc/passwd,zabbix\]<br>=> vfs.file.regexp\[/path/to/some/file,"(\[0-9\]+)$",,3,5,\\1\]<br>=> vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\] → 获取 *zabbix*用户ID| |vfs.file.regmatch\[file,regexp,<encoding>,<start line>,<end line>\]|<|<|<|<| |<|在文件中查找字符串。|0 - 未找到匹配<br><br>1 - 找到|**file** - 文件全路径<br>**regexp** - 描述所需模式编码的正则[表达式](/manual/regular_expressions#overview)<br>**encoding** - 编码[标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - 要搜索的第一行(默认为文件的第一行).<br>**end line** - 要搜索的最后一行的编号(默认为文件的最后一行)。|字节顺序标记 (BOM) 被忽略。<br><br>从2.2开始支持 `start line` 和 `end line`参数。<br><br>示例：<br>=> vfs.file.regmatch\[/var/log/app.log,error\]| |vfs.file.size\[file,<mode>\]|<|<|<|<| |<|文件大小 (以字节为单位).|整型|**file** - 文件全路径<br>**mode** - 可能的值：<br>*bytes* （默认） 或 *lines* (也计算空行)|该文件必须对用户*zabbix*具有读取权限。<br><br>示例：<br>=> vfs.file.size\[/var/log/syslog\]<br><br>文件大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>自Zabbix6.0起支持 `mode`参数。| |vfs.file.time\[file,<mode>\]|<|<|<|<| |<|文件时间信息。|整型 (Unix 时间戳)|**file** - 文件全路径<br>**mode** - 可能的值：<br>*modify* （默认） - 最后修改文件内容的时间<br>*access* - 最后读文件的时间。<br>*change* - 最后更改文件属性的时间。|示例：<br>=> vfs.file.time\[/etc/passwd,modify\]<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support).| |vfs.fs.discovery|<|<|<|<| |<|已安装文件系统及其类型的列表。用于低级别自动发现.|JSON 对象| |从Zabbix 2.0开始支持。<br><br>自Zabbix3.0起，Windows支持{\#FSDRIVETYPE}宏。<br><br>自Zabbix6.0起，Windows支持 {\#FSLABEL}宏。| |vfs.fs.get|<|<|<|<| |<|挂载的文件系统列表、它们的类型、磁盘空间和 inode 统计信息。可用于低级别自动发现.|JSON 对象| |自Zabbix 4.4.5后开始支持。<br><br>自Zabbix 6.0 起，Windows上支持 {\#FSLABEL}宏| |vfs.fs.inode\[fs,<mode>\]|<|<|<|<| |<|inode数量或百分比|整型 - 表示数量<br><br>浮点数 - 用于百分比|**fs** - 文件系统<br>**mode** - 可能的值：<br>*total* （默认）, *free*, *used*, //pfree // (空闲, 百分比), *pused* (使用, 百分比)|示例：<br>=> vfs.fs.inode\[/,pfree\]| |vfs.fs.size\[fs,<mode>\]|<|<|<|<| |<|磁盘空间（以字节为单位）或占总数的百分比。|整型 - 字节<br><br>浮点数 - 百分比|**fs** - 文件系统<br>**mode** - 可能的值：<br>*total* (默认), *free*, *used*, *pfree* (空闲, 百分比), *pused* (使用, 百分比)|如果是已挂载的卷，则返回本地文件系统的磁盘空间。<br><br>示例：<br>=> vfs.fs.size\[/tmp,free\]<br><br>当使用 *free* 模式时，文件系统的保留空间不考虑在内.| |vm.memory.size\[<mode>\]|<|<|<|<| |<|内存大小（以字节为单位）或占总数的百分比。|整型 - 字节<br><br>浮点数 -百分比|**mode** - 可能的值：<br>*total* (默认), *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*, *used*, *pused* (used, percentage), *available*, *pavailable* (available, percentage)<br>参阅[平台特性](/manual/appendix/items/supported_by_platform) 支持和此参数的 [其他详细信息](/manual/appendix/items/vm.memory.size_params)。|此监控项接受三类参数： :<br><br>1) *total* - 内存总量;<br>2)  特定于平台的内存类型: *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*;<br>3) 用户级估计有多少内存已使用和可用: *used*, *pused*, *available*, *pavailable*。| |web.page.get\[host,<path>,<port>\]|<|<|<|<| |<|获取网页内容。|作为文本的网页源（包括标题）|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent必须在启用 IPv6 支持的情况下编译。<br><br>示例：<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |web.page.perf\[host,<path>,<port>\]|<|<|<|<| |<|整个网页的加载时间（以秒为单位）。|浮点型|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent 必须在启用 IPv6 支持的情况下编译。<br><br>示例：<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |web.page.regexp\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<|<| |<|在网页上查找字符串。|匹配的字符串, 或由可选`output`参数指定。|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)<br>**regexp** - 描述了所需模式的正则 [表达式](/manual/regular_expressions#overview)<br>**length** -返回最大的字符数<br>**output** - 可选的输出格式模板， **\\0** 转义序列被替换为文本的匹配部分 (从从匹配开始的第一个字符到匹配结束的字符) ，而 **\\N** (其中 N=1...9) 转义序列被替换为第 N 个匹配组 (如果 N 超过捕获的组数，则为空字符串)。|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent 必须在启用 IPv6 支持的情况下编译。<br><br>使用该参数的内容提取 `output` 发生在 agent 上。<br><br>从2.2版本开始支持 `output`参数。<br><br>示例：<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]| |zabbix.stats\[<ip>,<port>\]|<|<|<|<| |<|远程返回一组 Zabbix Server或Proxy内部指标|JSON 对象|**ip** - 要远程查询的server/proxy的IP/DNS/网络掩码列表 (默认为127.0.0.1)<br>**port** - 要远程查询的server/proxy的端口 (默认为10051)|请注意，仅接受来自目标实例 [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)参数'StatsAllowedIP'中列出的地址统计请求<br><br>此项目返回一组选定的内部指标。有关详细信息，请参阅[Zabbix stats的远程监控](/manual/appendix/items/remote_stats#exposed_metrics).| |zabbix.stats\[<ip>,<port>,queue,<from>,<to>\]|<|<|<|<| |<|返回队列中被远程Zabbix Server或 proxy 延迟的监控项数。|JSON 对象|**ip** - 要远程查询的server/proxy的IP/DNS/网络掩码列表 (默认为127.0.0.1)<br>**port** - 要远程查询的server/proxy的端口 (默认为10051)<br>**queue** - 常量 (按原样使用)<br>**from** - 至少时延 (默认是6秒)<br>**to** - 最多延迟 (默认是无穷大)|请注意，仅接受来自目标实例[server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)参数'StatsAllowedIP'中列出的地址统计请求。|  

en-us	##### Key file authentication  To use key based authentication for SSH items, certain changes to the server configuration are required.  Open the Zabbix server configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) as `root` and look for the following line:      # SSHKeyLocation=  Uncomment it and set full path to a folder where public and private keys will be located:      SSHKeyLocation=/home/zabbix/.ssh  Save the file and restart zabbix\_server afterwards.  */home/zabbix* here is the home directory for the *zabbix* user account and *.ssh* is a directory where by default public and private keys will be generated by a [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen) command inside the home directory.  Usually installation packages of zabbix-server from different OS distributions create *zabbix* user account with a home directory in not very well-known places (as for system accounts), e. g. */var/lib/zabbix*.  Before starting to generate the keys, an approach to reallocate the home directory to a better known place (intuitively expected) could be considered. This will correspond with the *SSHKeyLocation* Zabbix server configuration parameter mentioned above.  These steps can be skipped if *zabbix* account has been added manually according to the [installation section](/manual/installation/install#create_user_account) because in this case most likely the home directory is already located at */home/zabbix*.  To change the setting for the *zabbix* user account all working processes which are using it have to be stopped:      # service zabbix-agent stop     # service zabbix-server stop  To change the home directory location with an attempt to move it (if it exists) a command should be executed:      # usermod -m -d /home/zabbix zabbix  It's absolutely possible that a home directory did not exist in the old place, so it should be created at the new place. A safe attempt to do that is:      # test -d /home/zabbix || mkdir /home/zabbix  To be sure that all is secure, additional commands could be executed to set permissions to the home directory:      # chown zabbix:zabbix /home/zabbix     # chmod 700 /home/zabbix  Previously stopped processes now can be started again:      # service zabbix-agent start     # service zabbix-server start  Now steps to generate public and private keys can be performed by a command:      # sudo -u zabbix ssh-keygen -t rsa     Generating public/private rsa key pair.     Enter file in which to save the key (/home/zabbix/.ssh/id_rsa):      Created directory '/home/zabbix/.ssh'.     Enter passphrase (empty for no passphrase):      Enter same passphrase again:      Your identification has been saved in /home/zabbix/.ssh/id_rsa.     Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub.     The key fingerprint is:     90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0     The key's randomart image is:     +--[ RSA 2048]----+     |                 |     |       .         |     |      o          |     | .     o         |     |+     . S        |     |.+   o =         |     |E .   * =        |     |=o . ..* .       |     |... oo.o+        |     +-----------------+  Note: public and private keys (*id\_rsa.pub* and *id\_rsa* respectively) have been generated by default in the */home/zabbix/.ssh* directory which corresponds to the Zabbix server *SSHKeyLocation* configuration parameter.  ::: noteimportant Key types other than "rsa" may be supported by the ssh-keygen tool and SSH servers but they may not be supported by libssh2, used by Zabbix. :::
zh-cn	##### 密钥文件认证  SSH监控项基于密钥的身份验证，需要对服务器配置进行某些更改。  使用`root`身份打开 Zabbix 服务器配置文件([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) 并查找以下行：      # SSHKeyLocation=  取消注释，配置公钥和私钥所在文件夹的完整路径，样例如下：      SSHKeyLocation=/home/zabbix/.ssh  保存文件并重启 zabbix_server 服务。  这里的 */home/zabbix* 是 *zabbix* 用户的家目录，*.ssh*是其中的一个目录。默认情况下，[ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen)命令生成的公钥和私钥将保存在这个目录中。  不同发行版操作系统的zabbix-server安装程序，会在不太明显的地方（与系统账户一样）创建一个带有主目录的zabbix用户账户。例如，*/var/lib/zabbix *。  在生成秘钥前可以考虑指定密钥保存的路径到更常见的位置，该路径需要跟 zabbix server 配置中的 *SSHKeyLocation* 保持一致.  如果已经根据[安装部分](/manual/installation/install#create_user_account)手动添加了*zabbix*账号，这些步骤可以跳过。因为在这种情况下，很可能主目录已经位于*/home/zabbix*。  要更改 *zabbix* 用户的设置，必须先停止zabbix所有的进程：     # service zabbix-agent stop    # service zabbix-server stop  要更改和移动一个已存在的目录应该执行以下命令:      # usermod -m -d /home/zabbix zabbix  在旧版本中不存在zabbix根目录，需要手动创建，可以执行以下命令:      # test -d /home/zabbix || mkdir /home/zabbix  为了保证安全，可以执行以下命令以设置跟目录的权限：      # chown zabbix:zabbix /home/zabbix     # chmod 700 /home/zabbix  当前进程如果是停止的，可以立即启动：      # service zabbix-agent start     # service zabbix-server start  生成公钥和私钥的命令和步骤如下：      # sudo -u zabbix ssh-keygen -t rsa     Generating public/private rsa key pair.     Enter file in which to save the key (/home/zabbix/.ssh/id_rsa):      Created directory '/home/zabbix/.ssh'.     Enter passphrase (empty for no passphrase):      Enter same passphrase again:      Your identification has been saved in /home/zabbix/.ssh/id_rsa.     Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub.     The key fingerprint is:     90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0     The key's randomart image is:     +--[ RSA 2048]----+     |                 |     |       .         |     |      o          |     | .     o         |     |+     . S        |     |.+   o =         |     |E .   * =        |     |=o . ..* .       |     |... oo.o+        |     +-----------------+  注意: 公钥(*id\_rsa.pub*)和私钥(*id\_rsa*)默认生成在*/home/zabbix/.ssh* 路径下，该路径对应Zabbix server的*SSHKeyLocation*配置参数  ::: noteimportant ssh-keygen命令和SSH服务可能支持“rsa”以外的密钥类型，但Zabbix使用的libssh2可能不支持.  :::

en-us	#### Key name  The key name itself has a limited range of allowed characters, which just follow each other. Allowed characters are:      0-9a-zA-Z_-.  Which means:  -   all numbers; -   all lowercase letters; -   all uppercase letters; -   underscore; -   dash; -   dot.  ![](../../../../../assets/en/manual/config/key_name.png)
zh-cn	#### 键值 名称  Key名本身具有有限的允许字符范围，允许的字符是：      0-9a-zA-Z_-.  即:  -   所有的数字; -   所有的小写字母; -   所有大写字母; -   下划线; -   减号; -   点。  ![](../../../../../assets/en/manual/config/key_name.png)

en-us	#### Kiosk mode  The kiosk mode in supported frontend pages can be activated using URL parameters. For example, in dashboards:  -   `/zabbix.php?action=dashboard.view&kiosk=1` - activate kiosk mode -   `/zabbix.php?action=dashboard.view&kiosk=0` - activate normal mode
zh-cn	#### 信息亭（Kiosk）模式  可以使用 URL 参数激活支持的前端页面中的信息亭模式。 例如，在仪表板中：  -   `/zabbix.php?action=dashboard.view&kiosk=1` - 激活信息亭模式 -   `/zabbix.php?action=dashboard.view&kiosk=0` - 激活普通模式

en-us	#### Known issues  See [known issues](/manual/installation/known_issues#graphs) for graphs.
zh-cn	#### 已知的问题  有关图表，请参阅 [已知问题](/manual/installation/known_issues#graphs)。

en-us	##### Kubernetes   - *Kubernetes nodes by HTTP*  - *Kubernetes cluster state by HTTP* - *Kubernetes API server by HTTP* - *Kubernetes Controller manager by HTTP* - *Kubernetes Scheduler by HTTP* - *Kubernetes kubelet by HTTP*  To enable Kubernetes monitoring, you need to use the new tool [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0), which installs Zabbix proxy and Zabbix agents in the Kubernetes cluster.   To learn more about configuring templates, see [HTTP template operation](/manual/config/templates_out_of_the_box/http).
zh-cn	##### Kubernetes - *基于 HTTP 的 Kubernetes 节点*  - *基于 HTTP 的 Kubernetes 集群状态* - *通过 HTTP 的 Kubernetes API 服务器* - *通过 HTTP 的 Kubernetes 控制器管理器* - *基于 HTTP 的 Kubernetes 调度程序* - *基于 HTTP 的 Kubernetes kubelet*  要启用 Kubernetes 监控，您需要使用新工具 [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0)，它会在 Kubernetes 集群中安装 Zabbix proxy 和 Zabbix agent。  要了解有关配置模板的更多信息，请参阅 [HTTP 模板操作](/manual/config/templates_out_of_the_box/http)。

en-us	##### Large file support  Zabbix has large file support for SNMP trapper files. The maximum file size that Zabbix can read is 2\^63 (8 EiB). Note that the filesystem may impose a lower limit on the file size.
zh-cn	##### 大文件支持  Zabbix为SNMP trap文件提供了“大文件支持”。Zabbix可以读取的最大文件大小为2^63（8 EiB）。请注意，文件系统可能会对文件大小添加下限。

en-us	 ### Latest data link for hosts shows numbers  The latest data link for hosts in [*Monitoring* -> *Hosts*](/manual/web_interface/frontend_sections/monitoring/hosts) now shows the number of items with latest data.
zh-cn	### 主机的最新数据链接显示数量  在 [*监控* -> *主机*](/manual/web_interface/frontend_sections/monitoring/hosts) 中主机的最新数据链接现在显示带有最新数据的项目数量。

en-us	### LDAP authentication  External LDAP authentication can be used to check user names and passwords. Note that a user must exist in Zabbix as well, however its Zabbix password will not be used.  Zabbix LDAP authentication works at least with Microsoft Active Directory and OpenLDAP.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth_ldap.png)  Configuration parameters:  |Parameter|Description| |---------|-----------| |*Enable LDAP authentication*|Mark the checkbox to enable LDAP authentication.| |*LDAP host*|Name of LDAP server. For example: ldap://ldap.zabbix.com<br>For secure LDAP server use *ldaps* protocol.<br>ldaps://ldap.zabbix.com<br>With OpenLDAP 2.x.x and later, a full LDAP URI of the form ldap://hostname:port or ldaps://hostname:port may be used.| |*Port*|Port of LDAP server. Default is 389.<br>For secure LDAP connection port number is normally 636.<br>Not used when using full LDAP URIs.| |*Base DN*|Base path to search accounts:<br>ou=Users,ou=system (for OpenLDAP),<br>DC=company,DC=com (for Microsoft Active Directory)| |*Search attribute*|LDAP account attribute used for search:<br>uid (for OpenLDAP),<br>sAMAccountName (for Microsoft Active Directory)| |*Bind DN*|LDAP account for binding and searching over the LDAP server, examples:<br>uid=ldap\_search,ou=system (for OpenLDAP),<br>CN=ldap\_search,OU=user\_group,DC=company,DC=com (for Microsoft Active Directory)<br>Anonymous binding is also supported.| |*Case-sensitive login*|Unmark the checkbox to disable case-sensitive login (enabled by default) for usernames.<br>E.g. disable case-sensitive login and log in with, for example, 'ADMIN' user even if the Zabbix user is 'Admin'.<br>*Note* that with case-sensitive login disabled the login will be denied if multiple users exist in Zabbix database with similar usernames (e.g. Admin, admin).| |*Bind password*|LDAP password of the account for binding and searching over the LDAP server.| |*Test authentication*|Header of a section for testing| |*Login*|Name of a test user (which is currently logged in the Zabbix frontend). This user name must exist in the LDAP server.<br>Zabbix will not activate LDAP authentication if it is unable to authenticate the test user.| |*User password*|LDAP password of the test user.|  ::: notewarning In case of trouble with certificates, to make a secure LDAP connection (ldaps) work you may need to add a `TLS_REQCERT allow` line to the /etc/openldap/ldap.conf configuration file. It may decrease the security of connection to the LDAP catalog. :::  ::: notetip It is recommended to create a separate LDAP account (*Bind DN*) to perform binding and searching over the LDAP server with minimal privileges in the LDAP instead of using real user accounts (used for logging in the Zabbix frontend).\ Such an approach provides more security and does not require changing the *Bind password* when the user changes his own password in the LDAP server.\ In the table above it's *ldap\_search* account name. :::
zh-cn	### LDAP 身份验证  外部 LDAP 身份验证可用于检查用户名和密码。请注意，用户也必须存在于 Zabbix 中，但不会使用其 Zabbix 密码。  Zabbix LDAP 身份验证至少适用于 Microsoft Active Directory 和 OpenLDAP。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth_ldap.png)  配置参数：  |参数|说明| |---------|------------| |*启用 LDAP 身份验证*|选中复选框以启用 LDAP 身份验证。| |*LDAP 主机*|LDAP 服务器的名称。例如：ldap://ldap.zabbix.com<br>对于安全的 LDAP 服务器，请使用 *ldaps* 协议。<br>ldaps://ldap.zabbix.com<br>对于 OpenLDAP 2.xx 及更高版本，完整的可以使用 ldap://hostname:port 或 ldaps://hostname:port 形式的 LDAP URI。| |*端口*|LDAP 服务器的端口。默认值为 389。<br>对于安全 LDAP 连接，端口号通常为 636。<br>在使用完整 LDAP URI 时不使用。| |*Base DN*|搜索帐户的基本路径：<br>ou=Users,ou=system（对于 OpenLDAP），<br>DC=company,DC=com（对于 Microsoft Active Directory）| |*搜索属性*|用于搜索的 LDAP 帐户属性：<br>uid（用于 OpenLDAP）、<br>sAMAccountName（用于 Microsoft Active Directory）| |*绑定 DN*|LDAP 帐户，用于在 LDAP 服务器上进行绑定和搜索，示例：<br>uid=ldap\_search,ou=system (for OpenLDAP),<br>CN=ldap\_search,OU=user\_group ,DC=company,DC=com（用于 Microsoft Active Directory）<br>还支持匿名绑定。| |*区分大小写的登录*|取消选中该复选框以禁用用户名的区分大小写登录（默认启用）。<br>例如禁用区分大小写的登录并使用例如“ADMIN”用户登录，即使 Zabbix 用户是“Admin”。<br>*注意*禁用区分大小写登录的情况下，如果存在多个用户，登录将被拒绝具有相似用户名的 Zabbix 数据库（例如 Admin、admin）。| |*绑定密码*|LDAP服务器上绑定和搜索帐号的LDAP密码。| |*测试认证*|测试部分的标题| |*Login*|测试用户的名称（当前登录在 Zabbix 前端）。此用户名必须存在于 LDAP 服务器中。<br>如果 Zabbix 无法对测试用户进行身份验证，它将不会激活 LDAP 身份验证。| |*用户密码*|测试用户的LDAP密码。|  ::: notewarning 如果证书出现问题，要使安全的 LDAP 连接 (ldaps) 正常工作，您可能需要在 /etc/openldap/ldap.conf 配置文件中添加 `TLS_REQCERT allow` 行。它可能会降低连接到 LDAP 目录的安全性。 :::  ::: notetip 建议创建一个单独的 LDAP 帐户 (*Bind DN*) 以在 LDAP 中以最低权限在 LDAP 服务器上执行绑定和搜索，而不是使用真实用户帐户（用于登录 Zabbix 前端）。这种方法提供了更高的安全性，并且当用户在 LDAP 服务器中更改自己的密码时，不需要更改 *Bind password*。 在上表中，它是 *ldap\_search* 帐户名。 :::

en-us	##### Limitations  -   Only same host (template) dependencies are allowed -   An item prototype can depend on another item prototype or regular     item from the same host -   Maximum count of dependent items for one master item is limited to     29999 (regardless of the number of dependency levels) -   Maximum 3 dependency levels allowed -   Dependent item on a host with master item from template will not be     exported to XML
zh-cn	##### 局限性  -   只允许相同的主机（模板）从属项 -   监控项原型可以依赖于来自同一主机的另一个监控项原型或常规监控项 -   主要监控项的从属项最大计数被限制为29999（不考虑从属级别的数量） -   最大允许3个从属级别 -   当从属监控项使用主机上来自模板的监控项作为主要监控项时，不允许导出为XML

en-us	#### Limitations  -   Private keys are stored in plain text in files readable by Zabbix     components during startup -   Pre-shared keys are entered in Zabbix frontend and stored in Zabbix     database in plain text -   Built-in encryption does not protect communications:     -   Between the web server running Zabbix frontend and user web         browser     -   Between Zabbix frontend and Zabbix server -   Currently each encrypted connection opens with a full TLS handshake,     no session caching and tickets are implemented -   Adding encryption increases the time for item checks and actions,     depending on network latency:     -   For example, if packet delay is 100ms then opening a TCP         connection and sending unencrypted request takes around 200ms.         With encryption about 1000 ms are added for establishing the TLS         connection;     -   Timeouts may need to be increased, otherwise some items and         actions running remote scripts on agents may work with         unencrypted connections, but fail with timeout with encrypted. -   Encryption is not supported by [network     discovery](/manual/discovery/network_discovery). Zabbix agent checks     performed by network discovery will be unencrypted and if Zabbix     agent is configured to reject unencrypted connections such checks     will not succeed.
zh-cn	 #### 限制因素  -   私钥以纯文本形式存储在Zabbix组件启动时可读的文件中 -   预共享密钥在Zabbix前端输入，并以明文形式存储在Zabbix数据库中 -   内置加密不能保护通信:     -   运行Zabbix前端的web服务器和用户web浏览器之间     -   Zabbix前端和Zabbix server之间 -   目前，每个加密连接都使用完整的TLS握手打开，没有实现会话缓存和票据 -   根据网络延迟，添加加密会增加监控项检查和操作的时间:     -   例如，如果包延迟100ms，那么打开TCP连接并发送未加密的请求大约需要200ms。 在建立TLS连接时，增加约1000毫秒的加密;     -   超时可能需要增加，否则在代理上运行远程脚本的某些监控项和操作可能会在未加密的连接中工作，但在加密的连接中超时则会失败。 -   不支持加密 [网络设备自动发现](/manual/discovery/network_discovery)。由网络发现执行的Zabbix agent 检查将不加密，如果Zabbix agent被配置为拒绝未加密的连接，这样的检查将不会成功。

en-us	#### - Limitations  Support of loadable modules is implemented for the Unix platform only. It means that it does not work for Windows agents.  In some cases a module may need to read module-related configuration parameters from *zabbix\_agentd.conf*. It is not supported currently. If you need your module to use some configuration parameters you should probably implement parsing of a module-specific configuration file.
zh-cn	#### - 限制  仅对类Unix平台实现了可加载模块的支持。这意味着它不适用于Windows平台的Agent。\  某些情况下，模块可能要从*zabbix\_agentd.conf*读取与模块相关的配置参数。目前不支持这么操作。如果您需要模块使用某些配置参数，则应该实现特定与模块的配置文件解析。

en-us	##### Limitations  There are some limitations associated with the algorithm of creating LLD macro names from MBean property names:  -   attribute names are changed to uppercase -   attribute names are ignored (no LLD macros are generated) if they     consist of unsupported characters for LLD macro names. Supported     characters can be described by the following regular expression:     `A-Z0-9_\.` -   if an attribute is called "obj" or "domain" they will be ignored     because of the overlap with the values of the reserved Zabbix     properties {\#JMXOBJ} and {\#JMXDOMAIN} (supported since Zabbix     3.4.3.)  Please consider this jmx.discovery (with "beans" mode) example. MBean has the following properties defined:      name=test     тип=Type     attributes []=1,2,3     Name=NameOfTheTest     domAin=some  As a result of JMX discovery, the following LLD macros will be generated:  -   {\#JMXDOMAIN} - Zabbix internal, describing the domain of MBean -   {\#JMXOBJ} - Zabbix internal, describing MBean object -   {\#JMXNAME} - created from "name" property  Ignored properties are:  -   тип : its name contains unsupported characters (non-ASCII) -   attributes\[\] : its name contains unsupported characters (square     brackets are not supported) -   Name : it's already defined (name=test) -   domAin : it's a Zabbix reserved name
zh-cn	##### 限制  从MBean属性的名称中创建LLD宏的名称时，有一些规则上的限制:  -   属性名称被改为大写 -   如果LLD宏名称中包含不支持的字符，则属性名称被忽略 (未生成LLD宏) 。支持的字符可用下面的正则表达式来表示:     `A-Z0-9_\.` -   如果属性名称是 "obj" 或 "domain" 则会被忽略     因为这与预留的Zabbix属性 {\#JMXOBJ} 和{\#JMXDOMAIN}的值重叠(从 Zabbix     3.4.3起支持此特性。)  请思考这个 jmx.discovery (使用 "beans" 模式) 的例子。MBean 中定义了下面的属性:      name=test     тип=Type     attributes []=1,2,3     Name=NameOfTheTest     domAin=some  作为JMX自动发现的结果，会产生下面的LLD宏:  -   {\#JMXDOMAIN} - Zabbix内部创建, 描述了MBean的域 -   {\#JMXOBJ} - Zabbix内部创建, 描述了MBean对象 -   {\#JMXNAME} - 从 "名称" 属性中创建  被忽略的属性有:  -   тип : 该名称包含不支持的字符 (非ASCII) -   attributes\[\] : 该名称包含不支持的字符(不支持方括号) -   Name: 已经定义过了 (name=test) -   domAin: Zabbix的保留名称

en-us	 #### Limitations  Zabbix agent for Windows does not support non-standard Windows configurations where CPUs are distributed non-uniformly across NUMA nodes. If logical CPUs are distributed non-uniformly, then CPU performance metrics may not be available for some CPUs. For example, if there are 72 logical CPUs with 2 NUMA nodes, both nodes must have 36 CPUs each.
zh-cn	#### 局限性  用于 Windows 的 Zabbix 代理不支持非标准的 Windows 配置，cpu 在 NUMA 节点上非均匀分布。如果逻辑 CPU 是非均匀分布的，那么某些 CPU 的 CPU 性能指标可能不可用。 例如, 如果有72个逻辑CPU分布在2个NUMA节点，那么每个节点必须有36个CPU。

en-us	#### Limiting access to API  Update role with ID "5", deny to call any "create", "update" or "delete" methods.  Request:  ```json {     "jsonrpc": "2.0",     "method": "role.update",     "params": [         {             "roleid": "5",             "rules": {                 "api.access": "1",                 "api.mode": "0",                 "api": ["*.create", "*.update", "*.delete"]             }         }     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "roleids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 限制对API的访问  更新ID号为5的角色，拒绝任何 "创建", "更新" 或者 "删除" 方式。  请求：  ```json {     "jsonrpc": "2.0",     "method": "role.update",     "params": [         {             "roleid": "5",             "rules": {                 "api.access": "1",                 "api.mode": "0",                 "api": ["*.create", "*.update", "*.delete"]             }         }     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "roleids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Link a group to templates  Add host group "2" to two templates.  Request:  ```json {     "jsonrpc": "2.0",     "method": "template.massadd",     "params": {         "templates": [             {                 "templateid": "10085"             },             {                 "templateid": "10086"             }         ],         "groups": [             {                 "groupid": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10085",             "10086"         ]     },     "id": 1 } ```
zh-cn	#### 将一个群组链接到模板  将主机群组“2”添加到两个模板中。  请求:  ```json {     "jsonrpc": "2.0",     "method": "template.massadd",     "params": {         "templates": [             {                 "templateid": "10085"             },             {                 "templateid": "10086"             }         ],         "groups": [             {                 "groupid": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10085",             "10086"         ]     },     "id": 1 } ```

en-us	#### Linking a template  To link a template to the host, do the following:  -   Go to *Configuration → Hosts* -   Click on the required host -   Start typing the template name in the *Templates* field. A list of     matching templates will appear; scroll down to select. -   Alternatively, you may click on *Select* next to the field and     select one or several templates from the list in a popup window -   Click on *Add/Update* in the host attributes form  The host will now have all the entities (items, triggers, graphs, etc) of the template.  ::: noteimportant Linking multiple templates to the same host will fail if in those templates there are items with the same item key. And, as triggers and graphs use items, they cannot be linked to a single host from multiple templates either, if using identical item keys. :::  When entities (items, triggers, graphs etc.) are added from the template:  -   previously existing identical entities on the host are updated as     entities of the template, and **any existing host-level customizations to the entity are lost** -   entities from the template are added -   any directly linked entities that, prior to template linkage,     existed only on the host remain untouched  In the lists, all entities from the template now are prefixed by the template name, indicating that these belong to the particular template. The template name itself (in gray text) is a link allowing to access the list of those entities on the template level.  If some entity (item, trigger, graph etc.) is not prefixed by the template name, it means that it existed on the host before and was not added by the template.
zh-cn	#### 链接模板  要将模板链接到主机，请执行以下操作：  -   转到*配置 → 主机* -   单击所需的主机 -   开始在 *模板* 字段中输入模板名称。 将出现匹配的模板列表； 向下滚动以选择。 -   或者，您可以单击旁边的 *选择* 字段，并从弹出窗口的列表中选择一个或多个模板，在弹出窗口中选择一个或多个模板 -   单击主机属性表单中的*添加/更新*  主机现在将拥有模板的所有实体（监控项，触发器，图形等）。  ::: noteimportant 如果在这些模板中具有相同监控项键的监控项，则将多个模板链接到同一主机将失败。并且作为触发器和图形使用的监控项，如果使用相同的监控项键，它们也不能从多个模板链接到单个主机。 :::  当从模板添加实体（监控项，触发器，图表等）时：  -   主机上先前存在的相同实体被更新为模板的实体，并且**任何现有实体的主机级自定义都将丢失** -   添加模板中的实体 -   在模板连接之前，只存在于主机上的任何直接链接的实体保持不变  在列表中，模板中的所有实体都以模板名称为前缀，表示这些属于特定模板。模板名称本身（灰色文本）是一个链接，允许在模板级别访问这些实体的列表。  如果某个实体（监控项，触发器，图表等）没有以模板名称为前缀，则意味着它之前存在于主机上并且不是由模板添加的。

en-us	#### Linking elements  Once you have put some elements on the map, it is time to start linking them. To link two elements you must first select them. With the elements selected, click on *Add* next to Link.  With a link created, the single element form now contains an additional *Links* section. Click on *Edit* to edit link attributes.  ![](../../../../../assets/en/manual/config/visualization/map_links.png){width="600"}  Link attributes:  |Parameter|Description| |---------|-----------| |*Label*|Label that will be rendered on top of the link.<br>Expression [macros](/manual/appendix/macros/supported_by_location) are supported in this field, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).| |*Connect to*|The element that the link connects to.| |*Type (OK)*|Default link style:<br>**Line** - single line<br>**Bold line** - bold line<br>**Dot** - dots<br>**Dashed line** - dashed line| |*Color (OK)*|Default link color.| |*[Link indicators](links)*|List of triggers linked to the link. In case a trigger has status PROBLEM, its style is applied to the link.|
zh-cn	#### 链接元素  一旦你在地图上放置了一些元素，就该开始链接了他们。要链接两个元素，您必须首先选择它们。随着元素选中，单击链接旁边的*添加*。  创建链接后，单元素表单现在包含一个附加的*链接*部分。单击 *Edit* 以编辑链接属性。  ![](../../../../../assets/en/manual/config/visualization/map_links.png){width="600"}  链接属性：  |参数|说明| |---------|------------| |*标签*|将在链接顶部呈现的标签。<br>此字段支持表达式 [宏](/manual/appendix/macros/supported_by_location)，但仅限于 `avg`、`last`、 `min` 和 `max` 函数，以时间为参数（例如，`{?avg(/host/key,1h)}`）。| |*连接到*|链接连接到的元素。| |*类型 (OK)*|默认链接样式：<br>**Line** - 单行<br>**粗线** - 粗线<br>**Dot** - 点<br>**虚线** - 虚线| |*颜色（OK）*|默认链接颜色。| |*[链接指示器](链接)*|链接到链接的触发器列表。如果触发器的状态为 PROBLEM，则其样式将应用于链接。|

en-us	##### Linking pre-defined templates to hosts  As you may have noticed, Zabbix comes with a set of predefined templates for various OS, devices and applications. To get started with monitoring very quickly, you may link the appropriate one of them to a host, but beware that these templates need to be fine-tuned for your environment. Some checks may not be needed, and polling intervals may be way too frequent.  More information about [templates](/manual/config/templates) is available.
zh-cn	##### 链接预定义模版到主机  正如您可能已经注意到的，Zabbix为各种操作系统、设备和应用程序提供了一组预定义的模板。要快速开始监控，您可以将适当的模板链接到主机，但要注意，这些模板需要根据您的环境进行微调。一些检查可能不需要，轮询间隔可能过于频繁。  可参考该链接，查看更多关于[模板](/manual/config/templates)的信息。

en-us	##### Linking templates to several hosts  To update template linkage of many hosts, in *Configuration → Hosts* select some hosts by marking their checkboxes, then click on **[Mass update](/manual/config/hosts/hostupdate)** below the list and then select *Link templates*:  ![](../../../../assets/en/manual/config/mass_link.png)  To link additional templates, start typing the template name in the auto-complete field until a dropdown appears offering the matching templates. Just scroll down to select the template to link.  The *Replace* option will allow to link a new template while unlinking any template that was linked to the hosts before. The *Unlink* option will allow to specify which templates to unlink. The *Clear when unlinking* option will allow to not only unlink any previously linked templates, but also remove all elements inherited from them (items, triggers, etc.).  ::: notetip Zabbix offers a sizable set of predefined templates. You can use these for reference, but beware of using them unchanged in production as they may contain too many items and poll for data too often. If you feel like using them, finetune them to fit you real needs. :::
zh-cn	##### 将模板链接到多个主机  要更新许多主机的模板链接，在*配置→主机*中通过标记其复选框来选择一些主机，然后单击列表下方的 **[批量更新](/manual/config/hosts/hostupdate)**，然后选择*链接模板*：  ![](../../../../assets/en/manual/config/mass_link.png)  要链接其他模板，在自动完成字段中开始输入模板名称，直到出现一个提供匹配模板的下拉列表。只需向下滚动即可选择要链接的模板。  *替换*选项将允许取消关联之前被连接到主机的任何模板的同时，链接一个新的模板。*取消链接*选项将允许取消链接指定的模板。*取消链接并清理*选项不仅允许取消链接任何以前链接的模板，也从中移除（监控项，触发器等）继承的所有元素。  ::: notetip Zabbix提供了大量预定义的模板。您可以使用这些作为参考，但请注意在生产中原封不动地使用它们，因为它们可能包含太多监控项，并且太频繁地轮询数据。如果您想使用它们，请对其进行微调以适合您的需要。 :::

en-us	#### Linking template to host  With a template ready, it only remains to add it to a host. For that, go to *Configuration → Hosts*, click on 'New host' to open its property form and find the **Templates** field.  Start typing *New template* in the *Templates* field. The name of template we have created should appear in the dropdown list. Scroll down to select. See that it appears in the *Templates* field.  ![](../../../assets/en/manual/quickstart/link_template.png)  Click *Update* in the form to save the changes. The template is now added to the host, with all entities that it holds.  As you may have guessed, this way it can be applied to any other host as well. Any changes to the items, triggers and other entities at the template level will propagate to the hosts the template is linked to.
zh-cn	#### 链接模版到主机  准备好一个模版后，将它链接到一个主机。前往*配置→ 主机*，点击“新建主机”打开其属性表单，并找到**模板**字段。  开始在*模板*字段中键入*新建模板*。我们创建的模板名称应该出现在下拉列表中。向下滚动选择。查看它是否出现在*模板*字段中。  ![](../../../assets/en/manual/quickstart/link_template.png)  单击表单中的*更新*保存更改。现在，模板和它所持有的所有对象都被添加到主机中。  正如您可能已经猜到的，这种方法也可以应用于任何其他主机。在模板级别对监控项、触发器和其他对象的任何更改都将传播到模板链接到的主机。

en-us	#### Links available  For each entry the following links are available:  -   Hosts     -   Monitoring         -   Latest data         -   Problems         -   Graphs         -   Host dashboards         -   Web scenarios     -   Configuration         -   Items         -   Triggers         -   Graphs         -   Discovery rules         -   Web scenarios  ```{=html} <!-- --> ``` -   Host groups     -   Monitoring         -   Latest data         -   Problems         -   Web scenarios     -   Configuration         -   Hosts         -   Templates  ```{=html} <!-- --> ``` -   Templates     -   Configuration         -   Items         -   Triggers         -   Graphs         -   Template dashboards         -   Discovery rules         -   Web scenarios
zh-cn	#### 可用链接  对于每个条目，以下链接可用：  -   主机     -   监控         -   最新数据         -   问题         -   图表         -   主机仪表板         -   网络场景     -   配置         -   监控项         -   触发器         -   图表         -   自动发现规则         -   网络场景  ```{=html} <!-- --> ``` -   主机组     -   监控         -   最新数据         -   问题         -   网络场景     -   配置         -   主机         -   模板  ```{=html} <!-- --> ``` -   模板     -   配置         -   监控项         -   触发器         -   图表         -   模板仪表板         -   自动发现规则         -   网络场景

en-us	##### Links  Clicking on a map element opens a menu with some available links.
zh-cn	##### 链接  点击拓扑图元素会打开一个包含一些可用链接的菜单。

en-us	#### Link two templates to a template  Link templates "10106" and "10104" to template.  Request:  ```json {     "jsonrpc": "2.0",     "method": "template.massadd",     "params": {         "templates": [             {                 "templateid": "10073"             }         ],         "templates_link": [             {                 "templateid": "10106"             },             {                 "templateid": "10104"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10073"         ]     },     "id": 1 } ```
zh-cn	#### 将两个模版链接到一个模板  将模板“10106”和“10104”链接到模板。  请求:  ```json {     "jsonrpc": "2.0",     "method": "template.massadd",     "params": {         "templates": [             {                 "templateid": "10073"             }         ],         "templates_link": [             {                 "templateid": "10106"             },             {                 "templateid": "10104"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10073"         ]     },     "id": 1 } ```

en-us	#### Linux kernel threads
zh-cn	#### Linux 内核线程

en-us	##### Linux  On Linux systems `ps` command can be used together with `watch` command for observing how Zabbix is doing. For example, to run `ps` command 5 times per second to see process activities:      watch -n 0.2 ps -fu zabbix  To show only Zabbix proxy and agent processes:      watch -tn 0.2 'ps -f -C zabbix_proxy -C zabbix_agentd'  To show only history syncer processes:      watch -tn 0.2 'ps -fC zabbix_server | grep history'  The `ps` command produces a wide output (approximately 190 columns) as some activity messages are long. If your terminal has less than 190 columns of text you can try      watch -tn 0.2 'ps -o cmd -C zabbix_server -C zabbix_proxy -C zabbix_agentd'  to display only commandlines without UID, PID, start time etc.  `top` command also can be used for observing Zabbix performance. Pressing 'c' key in `top` shows processes with their commandlines. In our tests on Linux `top` and `atop` correctly displayed changing activities of Zabbix processes, but `htop` was not displaying changing activities.
zh-cn	##### Linux  在 Linux 系统上 `ps` 命令可以与 `watch` 命令一起使用，以观察 Zabbix 的运行情况。例如，`ps` c每秒运行 5 次命令以查看进程活动：      watch -n 0.2 ps -fu zabbix  仅显示Zabbix proxy 和 agent 进程：      watch -tn 0.2 'ps -f -C zabbix_proxy -C zabbix_agentd'  仅显示历史同步器进程：      watch -tn 0.2 'ps -fC zabbix_server | grep history'  由于某些活动消息很长，因此该 `ps` 命令会产生很宽的输出（大约 190 列）。如果您的终端的文本少于 190 列，您可以尝试      watch -tn 0.2 'ps -o cmd -C zabbix_server -C zabbix_proxy -C zabbix_agentd'  仅显示没有 UID、PID、开始时间等的命令行。  `top`命令也可用于观察 Zabbix 性能。按 'c' 键 `top` 显示带有命令行的进程。在我们在 Linux 上的测试中 `top` and `atop` c正确显示了 Zabbix 进程的变化活动，但 `htop` 没有显示变化的活动。

en-us	#### Linux  See values supported for 'memtype' parameter on Linux in the table.  |Supported value|Description|Source in /proc/<pid>/status file| |--|------|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|VmSize| |pmem|Percentage of real memory|(VmRSS/total\_memory) \* 100| |rss|Resident set size|VmRSS| |data|Size of data segment|VmData| |exe|Size of code segment|VmExe| |hwm|Peak resident set size|VmHWM| |lck|Size of locked memory|VmLck| |lib|Size of shared libraries|VmLib| |peak|Peak virtual memory size|VmPeak| |pin|Size of pinned pages|VmPin| |pte|Size of page table entries|VmPTE| |size|Size of process code + data + stack segments|VmExe + VmData + VmStk| |stk|Size of stack segment|VmStk| |swap|Size of swap space used|VmSwap|  Notes for Linux:  1.  Not all 'memtype' values are supported by older Linux kernels. For     example, Linux 2.4 kernels do not support `hwm`, `pin`, `peak`,     `pte` and `swap` values. 2.  We have noticed that self-monitoring of the Zabbix agent active     check process with `proc.mem[...,...,...,...,data]` shows a value     that is 4 kB larger than reported by `VmData` line in the agent's     /proc/<pid>/status file. At the time of self-measurement the     agent's data segment increases by 4 kB and then returns to the     previous size.
zh-cn	#### Linux  请参见表中Linux上的“memtype”参数支持的值。  |支持值|描述|来源/proc/<pid>/status 文件| |---------------|-----------|---------------------------------------| |vsize ^[1](proc_mem_notes#footnotes)^|虚拟内存大小|VmSize| |pmem|实际内存百分比|(VmRSS/total\_memory) \* 100| |rss|驻留内存大小|VmRSS| |data|数据段大小|VmData| |exe|代码段大小|VmExe| |hwm|驻留集峰值大小|VmHWM| |lck|锁定内存大小|VmLck| |lib|共享库的大小|VmLib| |peak|峰值虚拟内存大小|VmPeak| |pin|固定页面的大小|VmPin| |pte|页表条目的大小|VmPTE| |size|进程代码 + 数据 + 堆栈段的大小|VmExe + VmData + VmStk| |stk|堆栈段大小|VmStk| |swap|使用的交换空间大小|VmSwap|  Linux上注意事项:  1.  一些旧版本Linux 内核并不是支持所有'memtype' 值的。例如, Linux 内核版本2.4就不支持  `hwm`,  `pin`,  `peak`,  `pte`  和  `swap`  等值。 2.  我们发现 Zabbix agent 主动检查进程参数`proc.mem[...,...,...,...,data]`  显示的值比agent 的 /proc/<pid>/status 文件中  `VmData`行的值大 4 kB。在agent自我监控管理时，agent的数据碎片增长率4 kB ，然后又返回到先前的值。

en-us	##### List of sorting fields available for each type of diagnostic information request  Following statistic fields can be used to sort and limit requested information.  |Diagnostic type|Available fields|[Type](/manual/api/reference_commentary#data_types)| |---------------|----------------|---------------------------------------------------| |historycache|values|integer| |valuecache|values|integer| |^|request.values|integer| |preprocessing|values|integer| |alerting|media.alerts|integer| |^|source.alerts|integer| |lld|values|integer|
zh-cn	##### 可用于每种诊断信息请求的排序字段列表  以下统计字段可用于排序和限制请求的信息。  |诊断类型|可用字段|[类型](/manual/api/reference_commentary#data_types)| |---------------|----------------|---------------------------------------------------| |historycache|values|integer| |valuecache|values|integer| |^|request.values|integer| |preprocessing|values|integer| |alerting|media.alerts|integer| |^|source.alerts|integer| |lld|values|integer|

en-us	##### List of statistic fields available for each type of diagnostic information request  Following statistic fields can be requested for each type of diagnostic information request property.  |Diagnostic type|Available fields|Description| |---------------|----------------|-----------| |historycache|items|Number of cached items.| |^|values|Number of cached values.| |^|memory|Shared memory statistics (free space, number of used chunks, number of free chunks, max size of free chunk).| |^|memory.data|History data cache shared memory statistics.| |^|memory.index|History index cache shared memory statistics.| |valuecache|items|Number of cached items.| |^|values|Number of cached values.| |^|memory|Shared memory statistics (free space, number of used chunks, number of free chunks, max size of free chunk).| |^|mode|Value cache mode.| |preprocessing|values|Number of queued values.| |^|preproc.values|Number of queued values with preprocessing steps.| |alerting|alerts|Number of queued alerts.| |lld|rules|Number of queued rules.| |^|values|Number of queued values.|
zh-cn	#####   每种类型的诊断信息请求可用的统计字段列表  可以为每种类型的诊断信息请求属性请求以下统计字段。  |诊断类型|可用字段|描述| |---------------|----------------|-----------| |historycache|items|监控项缓存的数量。| |^|values|值缓存的数量。| |^|memory|共享内存统计信息(空闲空间、使用的块数、空闲块数、空闲块的最大大小)。| |^|memory.data|历史数据缓存共享内存统计信息。| |^|memory.index|历史索引缓存共享内存统计信息。| |valuecache|items|缓存监控项的数量。| |^|values|缓存值的数量。| |^|memory|共享内存统计信息(空闲空间、使用的块数、空闲块数、空闲块的最大大小)。| |^|mode|值缓存模式。| |preprocessing|values|队列值的数量| |^|preproc.values|包含预处理步骤的队列值的数量。| |alerting|alerts|告警队列的数量。| |lld|rules|规则的队列数量。| |^|values|队列值的数量。|

en-us	##### List of waiting items  In this screen, each waiting item is listed.  ![](../../../../../assets/en/manual/web_interface/queue_details.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Scheduled check*|The time when the check was due is displayed.| |*Delayed by*|The length of the delay is displayed.| |*Host*|Host of the item is displayed.| |*Name*|Name of the waiting item is displayed.| |*Proxy*|The proxy name is displayed, if the host is monitored by proxy.|
zh-cn	##### 等待的监控项清单  在此屏幕中，列出了每个等待的监控项。  ![](../../../../../assets/en/manual/web_interface/queue_details.png){width="600"}  显示数据：  |栏目|说明| |--------|------------| |*定期检查*|显示检查到期的时间。| |*延迟*|显示延迟的长度。| |*主机*|显示监控项的主机名。| |*名称*|显示等待监控项的名称。| |*Proxy*|如果主机通过proxy监控，则显示proxy名称。|

en-us	### LLD macro path  The LLD macro path has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**lld\_macro**<br>(required)|string|LLD macro.| |**path**<br>(required)|string|Selector for value which will be assigned to corresponding macro.|
zh-cn	 ### LLD宏路径  LLD宏路径具有以下属性:  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**lld\_macro**<br>（必需）|string|LLD宏。| |**path**<br>（必需）|string|选择器将值分配给相应宏。|

en-us	### LLD macro path  The LLD macro path has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**lld\_macro**<br>(required)|string|LLD macro.| |**path**<br>(required)|string|Selector for value which will be assigned to corresponding macro.|
zh-cn	 ### LLD宏路径  LLD宏路径具有以下属性:  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**lld\_macro**<br>（必需）|string|LLD宏。| |**path**<br>（必需）|string|选择器将值分配给相应宏。|

en-us	#### LLD rule filter condition  The LLD rule filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [discoveryrule.get](get#retrieving_filter_conditions) and [discoveryrule.create](create#using_a_custom_expression_filter) method pages. :::
zh-cn	#### LLD 规则过滤条件  LLD 规则过滤条件对象定义了对 LLD 宏的值执行的单独检查。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|----------------------------------------------------|------------| |**macro**<br>（必需）|string|用于执行检查的 LLD 宏。| |**value**<br>（必需）|string|要比较的值。| |formulaid|string|用于从自定义表达式引用条件的任意唯一 ID。只能包含大写字母。ID 必须由用户在修改过滤条件时定义，但在以后请求时会重新生成。| |operator|integer|条件运算符。<br><br>可用值：<br>8 - *（默认值）* 匹配正则表达式；<br>9 - 不匹配正则表达式；<br>12 - 存在；<br>13 - 不存在。|  ::: notetip 为了更好地了解如何使用各种过滤器表达式的类型，参见示例[discoveryrule.get](get#检索过滤条件) 和[discoveryrule.create](create#使用自定义表达式过滤器) 方法页。 :::

en-us	#### LLD rule filter condition  The LLD rule filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [discoveryrule.get](get#retrieving_filter_conditions) and [discoveryrule.create](create#using_a_custom_expression_filter) method pages. :::
zh-cn	#### LLD 规则过滤条件  LLD 规则过滤条件对象定义了对 LLD 宏的值执行的单独检查。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|----------------------------------------------------|------------| |**macro**<br>（必需）|string|用于执行检查的 LLD 宏。| |**value**<br>（必需）|string|要比较的值。| |formulaid|string|用于从自定义表达式引用条件的任意唯一 ID。只能包含大写字母。ID 必须由用户在修改过滤条件时定义，但在以后请求时会重新生成。| |operator|integer|条件运算符。<br><br>可用值：<br>8 - *（默认值）* 匹配正则表达式；<br>9 - 不匹配正则表达式；<br>12 - 存在；<br>13 - 不存在。|  ::: notetip 为了更好地了解如何使用各种过滤器表达式的类型，参见示例[discoveryrule.get](get#检索过滤条件) 和[discoveryrule.create](create#使用自定义表达式过滤器) 方法页。 :::

en-us	### LLD rule filter  The LLD rule filter object defines a set of conditions that can be used to filter discovered objects. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.|
zh-cn	### LLD 规则过滤器  LLD 规则过滤器对象定义了一组可以使用的条件过滤发现的对象。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**conditions**<br>（必需）|array|用于过滤结果的过滤条件集。| |**evaltype**<br>（必填）|integer|过滤条件评估方法。<br><br>可用值：<br>0 - 和/或；<br>1 - 和；<br>2 -或;<br>3 - 自定义表达式。| |eval\_formula|string|*（只读）* 生成的表达式，将用于评估过滤条件。该表达式包含通过其“公式”引用特定过滤条件的 ID。`eval_formula` 的值等于具有自定义表达式的过滤器的 `formula` 的值。 |formula|string|用户定义的表达式，用于使用自定义表达式评估过滤器的条件。表达式必须包含通过其“公式”引用特定过滤条件的 ID。表达式中使用的 ID 必须与过滤条件中定义的 ID 完全匹配：任何条件都不能保持未使用或省略。<br><br>自定义表达式过滤器必需。|

en-us	### LLD rule filter  The LLD rule filter object defines a set of conditions that can be used to filter discovered objects. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.|
zh-cn	### LLD 规则过滤器  LLD 规则过滤器对象定义了一组可以使用的条件过滤发现的对象。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**conditions**<br>（必需）|array|用于过滤结果的过滤条件集。| |**evaltype**<br>（必填）|integer|过滤条件评估方法。<br><br>可用值：<br>0 - 和/或；<br>1 - 和；<br>2 -或;<br>3 - 自定义表达式。| |eval\_formula|string|*（只读）* 生成的表达式，将用于评估过滤条件。该表达式包含通过其“公式”引用特定过滤条件的 ID。`eval_formula` 的值等于具有自定义表达式的过滤器的 `formula` 的值。 |formula|string|用户定义的表达式，用于使用自定义表达式评估过滤器的条件。表达式必须包含通过其“公式”引用特定过滤条件的 ID。表达式中使用的 ID 必须与过滤条件中定义的 ID 完全匹配：任何条件都不能保持未使用或省略。<br><br>自定义表达式过滤器必需。|

en-us	# > LLD rule object  The following objects are directly related to the `discoveryrule` API.
zh-cn	# > LLD规则对象  以下对象与 `自动发现规则` API 直接相关。

en-us	#### LLD rule override filter condition  The LLD rule override filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.|
zh-cn	 #### LLD 规则覆盖过滤条件  LLD 规则覆盖过滤条件对象定义了对 LLD 宏的值执行的单独检查。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**macro**<br>（必需）|string|用于执行检查的 LLD 宏。| |**value**<br>（必需）|string|要比较的值。| |formulaid|string|用于从自定义表达式引用条件的任意唯一 ID。只能包含大写字母。 ID 必须由用户在修改过滤条件时定义，但在以后请求时会重新生成。| |operator|integer|条件运算符。<br><br>可用值：<br>8 - *（默认值）* 匹配正则表达式；<br>9 - 不匹配正则表达式；<br>12 - 存在；< br>13 - 不存在。|

en-us	#### LLD rule override filter condition  The LLD rule override filter condition object defines a separate check to perform on the value of an LLD macro. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**macro**<br>(required)|string|LLD macro to perform the check on.| |**value**<br>(required)|string|Value to compare with.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>8 - *(default)* matches regular expression;<br>9 - does not match regular expression;<br>12 - exists;<br>13 - does not exist.|
zh-cn	 #### LLD 规则覆盖过滤条件  LLD 规则覆盖过滤条件对象定义了对 LLD 宏的值执行的单独检查。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**macro**<br>（必需）|string|用于执行检查的 LLD 宏。| |**value**<br>（必需）|string|要比较的值。| |formulaid|string|用于从自定义表达式引用条件的任意唯一 ID。只能包含大写字母。 ID 必须由用户在修改过滤条件时定义，但在以后请求时会重新生成。| |operator|integer|条件运算符。<br><br>可用值：<br>8 - *（默认值）* 匹配正则表达式；<br>9 - 不匹配正则表达式；<br>12 - 存在；< br>13 - 不存在。|

en-us	#### LLD rule override filter  The LLD rule override filter object defines a set of conditions that if they match the discovered object the override is applied. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**evaltype**<br>(required)|integer|Override filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of override filter conditions to use for matching the discovered objects.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating override filter conditions. The expression contains IDs that reference specific override filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of override filters with a custom expression. The expression must contain IDs that reference specific override filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the override filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression override filters.|
zh-cn	 #### LLD 规则覆盖过滤器  LLD 规则覆盖过滤器对象定义了一组条件，如果它们与发现的对象匹配，则应用覆盖。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**evaltype**<br>（必需）|integer|覆盖过滤条件评估方法。<br><br>可能的值：<br>0 - 和/或；<br>1 - 和；<br>2 - 或;<br>3 - 自定义表达式。| |**conditions**<br>（必需）|array|用于匹配已发现对象的覆盖过滤条件集。| |eval\_formula|string|*（只读）* 生成的表达式，将用于评估覆盖过滤条件。该表达式包含通过其“公式”引用特定覆盖过滤条件的 ID。`eval_formula` 的值等于具有自定义表达式的过滤器的 `formula` 的值。 |formula|string|用户定义的表达式，用于评估具有自定义表达式的覆盖过滤器的条件。表达式必须包含通过其“公式”引用特定覆盖过滤条件的 ID。表达式中使用的 ID 必须与覆盖过滤条件中定义的 ID 完全匹配：任何条件都不能保持未使用或省略。<br><br>自定义表达式覆盖过滤器是必需的。|

en-us	#### LLD rule override filter  The LLD rule override filter object defines a set of conditions that if they match the discovered object the override is applied. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**evaltype**<br>(required)|integer|Override filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of override filter conditions to use for matching the discovered objects.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating override filter conditions. The expression contains IDs that reference specific override filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of override filters with a custom expression. The expression must contain IDs that reference specific override filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the override filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression override filters.|
zh-cn	 #### LLD 规则覆盖过滤器  LLD 规则覆盖过滤器对象定义了一组条件，如果它们与发现的对象匹配，则应用覆盖。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**evaltype**<br>（必需）|integer|覆盖过滤条件评估方法。<br><br>可能的值：<br>0 - 和/或；<br>1 - 和；<br>2 - 或;<br>3 - 自定义表达式。| |**conditions**<br>（必需）|array|用于匹配已发现对象的覆盖过滤条件集。| |eval\_formula|string|*（只读）* 生成的表达式，将用于评估覆盖过滤条件。该表达式包含通过其“公式”引用特定覆盖过滤条件的 ID。`eval_formula` 的值等于具有自定义表达式的过滤器的 `formula` 的值。 |formula|string|用户定义的表达式，用于评估具有自定义表达式的覆盖过滤器的条件。表达式必须包含通过其“公式”引用特定覆盖过滤条件的 ID。表达式中使用的 ID 必须与覆盖过滤条件中定义的 ID 完全匹配：任何条件都不能保持未使用或省略。<br><br>自定义表达式覆盖过滤器是必需的。|

en-us	##### LLD rule override operation discover  LLD rule override operation discover status that is set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**discover**<br>(required)|integer|Override the discover status for selected object.<br><br>Possible values:<br>0 - Yes, continue discovering the objects;<br>1 - No, new objects will not be discovered and existing ones will be marked as lost.|
zh-cn	##### LLD 规则覆盖操作发现  设置为已发现对象的 LLD 规则覆盖操作发现状态。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**discover**<br>（必需）|integer|覆盖选定对象的发现状态。<br><br>可用值：<br>0 - 是，持续发现对象；<br>1 - 否，不会发现新对象，现有对象将被标记为丢失。|

en-us	##### LLD rule override operation discover  LLD rule override operation discover status that is set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**discover**<br>(required)|integer|Override the discover status for selected object.<br><br>Possible values:<br>0 - Yes, continue discovering the objects;<br>1 - No, new objects will not be discovered and existing ones will be marked as lost.|
zh-cn	##### LLD 规则覆盖操作发现  设置为已发现对象的 LLD 规则覆盖操作发现状态。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**discover**<br>（必需）|integer|覆盖选定对象的发现状态。<br><br>可用值：<br>0 - 是，持续发现对象；<br>1 - 否，不会发现新对象，现有对象将被标记为丢失。|

en-us	##### LLD rule override operation history  LLD rule override operation history value that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**history**<br>(required)|string|Override the history of item prototype which is a time unit of how long the history data should be stored. Also accepts user macro and LLD macro.|
zh-cn	##### LLD 规则覆盖操作历史记录  LLD 规则覆盖设置为已发现监控项的操作历史记录值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**history**<br>（必需）|string|覆盖监控项原型的历史，这是历史数据应存储多长时间的时间单位。也接受用户宏和 LLD 宏。|

en-us	##### LLD rule override operation history  LLD rule override operation history value that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**history**<br>(required)|string|Override the history of item prototype which is a time unit of how long the history data should be stored. Also accepts user macro and LLD macro.|
zh-cn	##### LLD 规则覆盖操作历史记录  LLD 规则覆盖设置为已发现监控项的操作历史记录值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**history**<br>（必需）|string|覆盖监控项原型的历史，这是历史数据应存储多长时间的时间单位。也接受用户宏和 LLD 宏。|

en-us	##### LLD rule override operation inventory  LLD rule override operation inventory mode value that is set to discovered host. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**inventory\_mode**<br>(required)|integer|Override the host prototype inventory mode.<br><br>Possible values are:<br>-1 - disabled;<br>0 - *(default)* manual;<br>1 - automatic.|
zh-cn	##### LLD 规则覆盖操作清单  LLD 规则覆盖设置为已发现主机的操作库存模式值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**inventory\_mode**<br>（必需）|integer|覆盖主机原型库存模式。<br><br>可用值：<br>-1 - 禁用；<br>0 - *（默认值）* 手动；<br>1 - 自动。|

en-us	##### LLD rule override operation inventory  LLD rule override operation inventory mode value that is set to discovered host. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**inventory\_mode**<br>(required)|integer|Override the host prototype inventory mode.<br><br>Possible values are:<br>-1 - disabled;<br>0 - *(default)* manual;<br>1 - automatic.|
zh-cn	##### LLD 规则覆盖操作清单  LLD 规则覆盖设置为已发现主机的操作库存模式值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**inventory\_mode**<br>（必需）|integer|覆盖主机原型库存模式。<br><br>可用值：<br>-1 - 禁用；<br>0 - *（默认值）* 手动；<br>1 - 自动。|

en-us	##### LLD rule override operation period  LLD rule override operation period is an update interval value (supports custom intervals) that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**delay**<br>(required)|string|Override the update interval of the item prototype. Accepts seconds or a time unit with suffix (30s,1m,2h,1d) as well as flexible and scheduling intervals and user macros or LLD macros. Multiple intervals are separated by a semicolon.|
zh-cn	##### LLD 规则覆盖操作周期  LLD 规则覆盖操作周期是设置为已发现项目的更新间隔值（支持自定义间隔）。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**delay**<br>（必需）|string|覆盖项目原型的更新间隔。接受秒或带后缀 (30s，1m，2h，1d) 的时间单位以及灵活的调度间隔和用户宏或 LLD 宏。多个区间用分号隔开。|

en-us	##### LLD rule override operation period  LLD rule override operation period is an update interval value (supports custom intervals) that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**delay**<br>(required)|string|Override the update interval of the item prototype. Accepts seconds or a time unit with suffix (30s,1m,2h,1d) as well as flexible and scheduling intervals and user macros or LLD macros. Multiple intervals are separated by a semicolon.|
zh-cn	##### LLD 规则覆盖操作周期  LLD 规则覆盖操作周期是设置为已发现项目的更新间隔值（支持自定义间隔）。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**delay**<br>（必需）|string|覆盖项目原型的更新间隔。接受秒或带后缀 (30s，1m，2h，1d) 的时间单位以及灵活的调度间隔和用户宏或 LLD 宏。多个区间用分号隔开。|

en-us	##### LLD rule override operation severity  LLD rule override operation severity value that is set to discovered trigger. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**severity**<br>(required)|integer|Override the severity of trigger prototype.<br><br>Possible values are: 0 - *(default)* not classified;<br>1 - information;<br>2 - warning;<br>3 - average;<br>4 - high;<br>5 - disaster.|
zh-cn	##### LLD 规则覆盖操作严重性  LLD 规则覆盖设置为发现触发器的操作严重性值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**severity**<br>（必需）|integer|覆盖触发器原型的严重性。<br><br>可用值：0 - *（默认值）* 未分类；<br>1 - 信息；<br>2 - 警告；<br>3 - 一般严重；<br>4 - 比较严重；<br>5 - 灾难。|

en-us	##### LLD rule override operation severity  LLD rule override operation severity value that is set to discovered trigger. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**severity**<br>(required)|integer|Override the severity of trigger prototype.<br><br>Possible values are: 0 - *(default)* not classified;<br>1 - information;<br>2 - warning;<br>3 - average;<br>4 - high;<br>5 - disaster.|
zh-cn	##### LLD 规则覆盖操作严重性  LLD 规则覆盖设置为发现触发器的操作严重性值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**severity**<br>（必需）|integer|覆盖触发器原型的严重性。<br><br>可用值：0 - *（默认值）* 未分类；<br>1 - 信息；<br>2 - 警告；<br>3 - 一般严重；<br>4 - 比较严重；<br>5 - 灾难。|

en-us	##### LLD rule override operation status  LLD rule override operation status that is set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**status**<br>(required)|integer|Override the status for selected object.<br><br>Possible values:<br>0 - Create enabled;<br>1 - Create disabled.|
zh-cn	##### LLD 规则覆盖操作状态  LLD 规则覆盖设置为已发现对象的操作状态。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**status**<br>（必需）|integer|覆盖选定对象的状态。<br><br>可用值：<br>0 - 启用创建；<br>1 - 禁止创建。|

en-us	##### LLD rule override operation status  LLD rule override operation status that is set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**status**<br>(required)|integer|Override the status for selected object.<br><br>Possible values:<br>0 - Create enabled;<br>1 - Create disabled.|
zh-cn	##### LLD 规则覆盖操作状态  LLD 规则覆盖设置为已发现对象的操作状态。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**status**<br>（必需）|integer|覆盖选定对象的状态。<br><br>可用值：<br>0 - 启用创建；<br>1 - 禁止创建。|

en-us	##### LLD rule override operation tag  LLD rule override operation tag object contains tag name and value that are set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|New tag name.| |value|string|New tag value.|
zh-cn	##### LLD 规则覆盖操作标记  LLD 规则覆盖操作标记对象包含设置为发现对象的标记名称和值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>（必需）|string|标签名字。| |value|string|标签值。|

en-us	##### LLD rule override operation tag  LLD rule override operation tag object contains tag name and value that are set to discovered object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|New tag name.| |value|string|New tag value.|
zh-cn	##### LLD 规则覆盖操作标记  LLD 规则覆盖操作标记对象包含设置为发现对象的标记名称和值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>（必需）|string|标签名字。| |value|string|标签值。|

en-us	##### LLD rule override operation template  LLD rule override operation template object that is linked to discovered host. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**templateid**<br>(required)|string|Override the template of host prototype linked templates.|
zh-cn	##### LLD 规则覆盖操作模板   LLD 规则覆盖链接到已发现主机的操作模板对象。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**templateid**<br>（必需）|string|覆盖主机原型链接模板的模板。|

en-us	##### LLD rule override operation template  LLD rule override operation template object that is linked to discovered host. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**templateid**<br>(required)|string|Override the template of host prototype linked templates.|
zh-cn	##### LLD 规则覆盖操作模板   LLD 规则覆盖链接到已发现主机的操作模板对象。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**templateid**<br>（必需）|string|覆盖主机原型链接模板的模板。|

en-us	#### LLD rule override operation  The LLD rule override operation is combination of conditions and actions to perform on the prototype object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operationobject**<br>(required)|integer|Type of discovered object to perform the action.<br><br>Possible values:<br>0 - Item prototype;<br>1 - Trigger prototype;<br>2 - Graph prototype;<br>3 - Host prototype.| |operator|integer|Override condition operator.<br><br>Possible values:<br>0 - *(default)* equals;<br>1 - does not equal;<br>2 - contains;<br>3 - does not contain;<br>8 - matches;<br>9 - does not match.| |value|string|Pattern to match item, trigger, graph or host prototype name depending on selected object.| |opstatus|object|Override operation status object for item, trigger and host prototype objects.| |opdiscover|object|Override operation discover status object (all object types).| |opperiod|object|Override operation period (update interval) object for item prototype object.| |ophistory|object|Override operation history object for item prototype object.| |optrends|object|Override operation trends object for item prototype object.| |opseverity|object|Override operation severity object for trigger prototype object.| |optag|array|Override operation tag object for trigger and host prototype objects.| |optemplate|array|Override operation template object for host prototype object.| |opinventory|object|Override operation inventory object for host prototype object.|
zh-cn	#### LLD 规则覆盖操作  LLD 规则覆盖操作是对原型对象执行的条件和操作的组合。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**operationobject**<br>（必需）|integer|发现的执行操作的对象的类型。<br><br>可用值：<br>0 - 项目原型；<br>1 - 触发器原型；<br>2 - 图形原型；<br>3 - 主机原型。| |operator|integer|覆盖条件运算符。<br><br>可能的值：<br>0 - *（默认值）* 等于；<br>1 - 不等于；<br>2 - 包含；<br>3 - 不包含；<br>8 - 匹配；<br>9 - 不匹配。| |value|string|根据所选对象匹配项、触发器、图形或主机原型名称的模式。| |opstatus|object|覆盖项目、触发器和宿主原型对象的操作状态对象。| |opdiscover|object|覆盖操作发现状态对象（所有对象类型）。| |opperiod|object|覆盖项目原型对象的操作周期（更新间隔）对象。| |ophistory|object|覆盖项目原型对象的操作历史对象。| |optrends|object|覆盖项目原型对象的操作趋势对象。| |opseverity|object|覆盖触发器原型对象的操作严重性对象。| |optag|array|覆盖触发器和宿主原型对象的操作标记对象。| |optemplate|array|覆盖宿主原型对象的操作模板对象。| |opinventory|object|覆盖主机原型对象的操作清单对象。|

en-us	#### LLD rule override operation  The LLD rule override operation is combination of conditions and actions to perform on the prototype object. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**operationobject**<br>(required)|integer|Type of discovered object to perform the action.<br><br>Possible values:<br>0 - Item prototype;<br>1 - Trigger prototype;<br>2 - Graph prototype;<br>3 - Host prototype.| |operator|integer|Override condition operator.<br><br>Possible values:<br>0 - *(default)* equals;<br>1 - does not equal;<br>2 - contains;<br>3 - does not contain;<br>8 - matches;<br>9 - does not match.| |value|string|Pattern to match item, trigger, graph or host prototype name depending on selected object.| |opstatus|object|Override operation status object for item, trigger and host prototype objects.| |opdiscover|object|Override operation discover status object (all object types).| |opperiod|object|Override operation period (update interval) object for item prototype object.| |ophistory|object|Override operation history object for item prototype object.| |optrends|object|Override operation trends object for item prototype object.| |opseverity|object|Override operation severity object for trigger prototype object.| |optag|array|Override operation tag object for trigger and host prototype objects.| |optemplate|array|Override operation template object for host prototype object.| |opinventory|object|Override operation inventory object for host prototype object.|
zh-cn	#### LLD 规则覆盖操作  LLD 规则覆盖操作是对原型对象执行的条件和操作的组合。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**operationobject**<br>（必需）|integer|发现的执行操作的对象的类型。<br><br>可用值：<br>0 - 项目原型；<br>1 - 触发器原型；<br>2 - 图形原型；<br>3 - 主机原型。| |operator|integer|覆盖条件运算符。<br><br>可能的值：<br>0 - *（默认值）* 等于；<br>1 - 不等于；<br>2 - 包含；<br>3 - 不包含；<br>8 - 匹配；<br>9 - 不匹配。| |value|string|根据所选对象匹配项、触发器、图形或主机原型名称的模式。| |opstatus|object|覆盖项目、触发器和宿主原型对象的操作状态对象。| |opdiscover|object|覆盖操作发现状态对象（所有对象类型）。| |opperiod|object|覆盖项目原型对象的操作周期（更新间隔）对象。| |ophistory|object|覆盖项目原型对象的操作历史对象。| |optrends|object|覆盖项目原型对象的操作趋势对象。| |opseverity|object|覆盖触发器原型对象的操作严重性对象。| |optag|array|覆盖触发器和宿主原型对象的操作标记对象。| |optemplate|array|覆盖宿主原型对象的操作模板对象。| |opinventory|object|覆盖主机原型对象的操作清单对象。|

en-us	##### LLD rule override operation trends  LLD rule override operation trends value that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**trends**<br>(required)|string|Override the trends of item prototype which is a time unit of how long the trends data should be stored. Also accepts user macro and LLD macro.|
zh-cn	##### LLD 规则覆盖操作趋势  LLD 规则覆盖设置为已发现监控项的操作趋势值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**trends**<br>（必需）|string|覆盖监控项原型的趋势，这是趋势数据应存储多长时间的时间单位。也接受用户宏和 LLD 宏。|

en-us	##### LLD rule override operation trends  LLD rule override operation trends value that is set to discovered item. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**trends**<br>(required)|string|Override the trends of item prototype which is a time unit of how long the trends data should be stored. Also accepts user macro and LLD macro.|
zh-cn	##### LLD 规则覆盖操作趋势  LLD 规则覆盖设置为已发现监控项的操作趋势值。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**trends**<br>（必需）|string|覆盖监控项原型的趋势，这是趋势数据应存储多长时间的时间单位。也接受用户宏和 LLD 宏。|

en-us	### LLD rule overrides  The LLD rule overrides object defines a set of rules (filters, conditions and operations) that are used to override properties of different prototype objects. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Unique override name.| |**step**<br>(required)|integer|Unique order number of the override.| |stop|integer|Stop processing next overrides if matches.<br><br>Possible values:<br>0 - *(default)* don't stop processing overrides;<br>1 - stop processing overrides if filter matches.| |filter|object|Override filter.| |operations|array|Override operations.|
zh-cn	 ### LLD规则覆盖  LLD规则覆盖对象定义了一组规则（过滤器、条件和操作），用于覆盖不同原型对象的属性。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**name**<br>（必需）|string|唯一的覆盖名称。| |**step**<br>（必需）|integer|覆盖的唯一订单号。| |stop|integer|如果匹配，则停止处理下一个覆盖。<br><br>可用值：<br>0 - *（默认值）* 不停止处理覆盖；<br>1 - 如果过滤器匹配，则停止处理覆盖。| |filter|object|覆盖过滤器。| |operations|array|覆盖操作。|

en-us	### LLD rule overrides  The LLD rule overrides object defines a set of rules (filters, conditions and operations) that are used to override properties of different prototype objects. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**name**<br>(required)|string|Unique override name.| |**step**<br>(required)|integer|Unique order number of the override.| |stop|integer|Stop processing next overrides if matches.<br><br>Possible values:<br>0 - *(default)* don't stop processing overrides;<br>1 - stop processing overrides if filter matches.| |filter|object|Override filter.| |operations|array|Override operations.|
zh-cn	 ### LLD规则覆盖  LLD规则覆盖对象定义了一组规则（过滤器、条件和操作），用于覆盖不同原型对象的属性。它具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**name**<br>（必需）|string|唯一的覆盖名称。| |**step**<br>（必需）|integer|覆盖的唯一订单号。| |stop|integer|如果匹配，则停止处理下一个覆盖。<br><br>可用值：<br>0 - *（默认值）* 不停止处理覆盖；<br>1 - 如果过滤器匹配，则停止处理覆盖。| |filter|object|覆盖过滤器。| |operations|array|覆盖操作。|

en-us	### LLD rule  The low-level discovery rule object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the LLD rule.| |**delay**<br>(required)|string|Update interval of the LLD rule. Accepts seconds or time unit with suffix and with or without one or more [custom intervals](/manual/config/items/item/custom_intervals) that consist of either flexible intervals and scheduling intervals as serialized strings. Also accepts user macros. Flexible intervals could be written as two macros separated by a forward slash. Intervals are separated by a semicolon.<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host that the LLD rule belongs to.| |**interfaceid**<br>(required)|string|ID of the LLD rule's host interface. Used only for host LLD rules.<br><br>Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, dependent, database monitor and script LLD rules. Optional for HTTP agent LLD rules.| |**key\_**<br>(required)|string|LLD rule key.| |**name**<br>(required)|string|Name of the LLD rule.| |**type**<br>(required)|integer|Type of the LLD rule.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>10 - external check;<br>11 - database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - TELNET agent;<br>16 - JMX agent;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script.| |**url**<br>(required)|string|URL string, required for HTTP agent LLD rule. Supports user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |allow\_traps|integer|HTTP agent LLD rule field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent or HTTP agent LLD rules.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM| |description|string|Description of the LLD rule.| |error|string|*(readonly)* Error text if there are problems updating the LLD rule.| |follow\_redirects|integer|HTTP agent LLD rule field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent LLD rule field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |http\_proxy|string|HTTP agent LLD rule field. HTTP(S) proxy connection string.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI LLD rules.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lifetime|string|Time period after which items that are no longer discovered will be deleted. Accepts seconds, time unit with suffix and user macro.<br><br>Default: `30d`.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and maximum count of dependent items equal to 999 are allowed.<br>Discovery rule cannot be master item for another discovery rule.<br><br>Required for Dependent item.| |output\_format|integer|HTTP agent LLD rule field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the LLD rule:<br>- executed script for SSH and Telnet LLD rules;<br>- SQL query for database monitor LLD rules;<br>- formula for calculated LLD rules.| |parameters|array|Additional parameters for script type LLD rule. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent LLD rules.| |post\_type|integer|HTTP agent LLD rule field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent LLD rule field. HTTP(S) request body data. Used with post\_type.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent LLD rule field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent LLD rule field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent LLD rule field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent LLD rule field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent LLD rule field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent LLD rule field. Password for SSL Key file.| |state|integer|*(readonly)* State of the LLD rule.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - not supported.| |status|integer|Status of the LLD rule.<br><br>Possible values:<br>0 - *(default)* enabled LLD rule;<br>1 - disabled LLD rule.| |status\_codes|string|HTTP agent LLD rule field. Ranges of required HTTP status codes separated by commas. Also supports user macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template LLD rule.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script LLD rules. Supports user macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper LLD rules or HTTP agent LLD rules.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent LLD rules.<br><br>Required by SSH and Telnet LLD rules.| |uuid|string|Universal unique identifier, used for linking imported LLD rules to already existing ones. Used only for LLD rules on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |verify\_host|integer|HTTP agent LLD rule field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |verify\_peer|integer|HTTP agent LLD rule field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### LLD规则  底层发现规则对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |itemid|字符|*（只读）* LLD规则ID。| |**delay**<br>（必需）|字符|LLD 规则的更新间隔。接受带后缀的秒或时间单位，可以带或不带一个或多个 [自定义间隔](/manual/config/items/item/custom_intervals)，它们由灵活间隔和调度间隔组成，作为序列化字符串。还接收用户宏。灵活的间隔可以写成两个由正斜杠分隔的宏。间隔由分号分隔。<br><br>对于 Zabbix trapper、依赖项和带有 `mqtt.get` 键值的 Zabbix agent (active) 是可选的。| |**hostid**<br>（必需）|字符|LLD规则的主机ID。| |**interfaceid**<br>（必需）|字符|LLD规则的主机接口ID，只用于主机LLD规则。<br><br>Zabbix agent (主动检查)， Zabbix 内部检查， Zabbix 采集器，相关项，数据库监控和脚本LLD规则不需要。HTTP代理LLD规则可选。| |**key\_**<br>（必需）|字符|LLD规则键值。| |**name**<br>（必需）|字符|LLD规则名称。| |**type**<br>（必需）|字符|LLD规则类型。<br><br>可用值：<br>0 - Zabbix agent；<br>2 - Zabbix 采集器；<br>3 - 简单检查；<br>5 - Zabbix 内部检查；<br>7 - Zabbix agent (主动)；<br>10 - 外部检查；<br>11 - 数据库监控；<br>12 - IPMI agent；<br>13 - SSH agent；<br>14 - TELNET agent；<br>16 - JMX agent；<br>18 - 相关项；<br>19 - HTTP agent；<br>20 - SNMP agent；<br>21 - 脚本。| |**url**<br>（必需）|字符|URL字符串，HTTP代理LLD规则需要。 支持用户宏，{HOST.IP}， {HOST.CONN}，{HOST.DNS}，{HOST.HOST}，{HOST.NAME}，{ITEM.ID}，{ITEM.KEY}。| |allow\_traps|整数|HTTP代理LLD规则字段。也允许填充值作为采集器监控项类型。<br><br>0 - *（默认值）* 不允许接收传入数据；<br>1 - 允许接收传入数据。| |authtype|整数|只有SSH客户端或者HTTP代理的LLD规则能使用.<br><br>SSH客户端认证方法可用值：<br>0 - *（默认值）* 密码；<br>1 - 公钥。<br><br>HTTP客户端认证方法可用值：<br>0 - *（默认值）* none；<br>1 - basic；<br>2 - NTLM。| |description|字符|LLD规则描述。| |error|字符|*（只读）* 更新 LLD 规则时出现问题时的错误文本。| |follow\_redirects|整数|HTTP代理LLD规则字段。接收数据时进行重定向。<br><br>0 - 不重定向；<br>1 - *（默认值）* 重定向。| |headers|对象|HTTP代理LLD规则字段。带有 HTTP(S) 请求标头的对象，其中头部名称用作键，头部值用作值。<br><br>例如：<br>{ "User-Agent": "Zabbix" }| |http\_proxy|字符|HTTP代理LLD规则字段。HTTP(S)代理连接地址。| |ipmi\_sensor|字符|IPMI 传感器。只用于IPMI LLD规则。| |jmx\_endpoint|字符|JMX agent自定义的连接地址。<br><br>默认值：<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lifetime|字符|不再发现的监控项过期时间。接受秒、带后缀的时间单位和用户宏。<br><br>默认值：`30d`。| |master\_itemid|整数|主监控项ID。<br>最多允许递归 3 个依赖监控项，依赖监控项的最大计数等于 999。<br>发现规则不能是另一个发现规则的主监控项。<br><br>依赖监控项是必需的。| |output\_format|整数|HTTP代理LLD规则字段。 返回内容格式化JSON输出。<br><br>0 - *（默认值）* 不转换；<br>1 - 转JSON。| |params|字符|附加参数取决于 LLD 规则的类型：<br>- 执行SSH 和 Telnet 脚本的LLD 规则；<br>- 数据库监控SQL查询SQL的LLD规则；<br>- 可计算LLD规则。| |parameters|数组|除了LLD规则脚本类型参数之外。还有“名称”和“值”属性的对象数组，其中名称必须是唯一的。| |password|字符|密码认证。适用于简单检查、SSH、Telnet、数据库监控、JMX 和 HTTP代理LLD规则。| |post\_type|整数|HTTP代理LLD规则字段。在post属性中的数据body的类型 。<br><br>0 - *(默认值)* 行数据；<br>2 - JSON数据。<br>3 - XML数据。| |posts|字符|HTTP代理LLD规则字段。HTTP(S) 请求body数据。使用post类型。| |privatekey|字符|私钥文件的名称。| |publickey|字符|公钥文件的名称。| |query\_fields|数组|HTTP代理LLD规则字段。查询参数。具有 'key':'value' 对的对象数组，其中值可以是空字符串。| |request\_method|整数|HTTP代理LLD规则字段。请求方法的类型。<br><br>0 - *（默认值）* GET<br>1 - POST；<br>2 - PUT；<br>3 - HEAD。| |retrieve\_mode|整数|HTTP代理LLD规则字段。应该存储响应的哪些部分。<br><br>0 - *（默认值）* Body；<br>1 - Headers；<br>2 - body和headers均存储。<br><br>HEAD请求方法值只能为1。| |snmp\_oid|字符|SNMP OID。| |ssl\_cert\_file|字符|HTTP代理LLD规则字段。公钥文件路径。| |ssl\_key\_file|字符|HTTP代理LLD规则字段。 私钥文件路径。| |ssl\_key\_password|字符|HTTP代理LLD规则字段。秘钥文件的密码。| |state|整数|*（只读）* LLD规则状态。<br><br>可用值：<br>0 - *（默认值）* 支持；<br>1 - 不支持。| |status|整数|LLD规则状态。<br><br>可用值：<br>0 - *（默认值）* 激活LLD规则；<br>1 - 禁用LLD规则。| |status\_codes|字符|HTTP代理LLD规则字段。 用逗号分隔的所需 HTTP 状态代码范围。还支持用户宏作为逗号分隔列表的一部分。<br><br>例如：200，200-{$M}，{$M}，200-400。| |templateid|字符|（只读）父模板 LLD 规则的 ID。| |timeout|字符|监控项数据轮询请求超时。用于HTTP代理和LLD规则脚本。支持用户宏或LLD宏。<br><br>默认值：3s<br>最大值：60s| |trapper\_hosts|字符|允许的主机。 用于采集器监控项或者HTTP代理LLD规则。| |username|字符|验证的用户名。用于简单检查、SSH、Telnet、数据库监控、JMX和HTTP代理LLD规则。<br><br>SSH和Telnet监控项LLD规则需要。| |uuid|字符|通用唯一标识符，用于将导入的LLD规则链接到现有的LLD规则中。仅用于模板上的LLD规则。如果没有给出，则自动生成。<br><br>对于更新操作，此字段为*只读*。| |verify\_host|整数|HTTP代理LLD规则字段。 验证URL中的主机名位于主机证书的公用名字段或使用者备用名字段中。<br><br>0 - *（默认值）* 不验证；<br>1 - 验证。| |verify\_peer|整数|HTTP代理LLD规则字段。验证主机证书是否真实。<br><br>0 - *（默认值）* 不验证；<br>1 - 验证。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# LLD rule  This class is designed to work with low level discovery rules.  Object references:\  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule)  Available methods:\  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) -     copying LLD rules -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) -     creating new LLD rules -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) -     deleting LLD rules -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) -     retrieving LLD rules -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) -     updating LLD rules
zh-cn	# LLD 规则  此类用于底层发现规则。  对象引用：  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld规则)  可用方法：  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) - 复制LLD规则 -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) - 创建LLD规则 -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) - 删除LLD规则 -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) - 获取LLD规则 -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) - 更新LLD规则

en-us	## Loadable plugins  ### Encrypted MongoDB plugin connection  MongoDB plugin now supports TLS encryption when connecting to MongoDB using named sessions.   Updated plugin (MongoDB plugin 1.2.1) is included into Zabbix official packages starting from Zabbix 6.0.14. Note that MongoDB is a loadable plugin and can be installed separately either from packages or from sources. The plugin will work with any minor version of Zabbix 6.0. For more details see [MongoDB plugin](/manual/appendix/config/zabbix_agent2_plugins/mongodb_plugin).
zh-cn	## 可加载插件  ### 加密的 MongoDB 插件连接  使用命名会话连接到 MongoDB 时，MongoDB 插件现在支持 TLS 加密。  从 Zabbix 6.0.14 开始，更新的插件（MongoDB 插件 1.2.1）包含在 Zabbix 官方包中。 请注意，MongoDB 是一个可加载插件，可以从包或源中单独安装。 该插件适用于任何次要版本的 Zabbix 6.0。 有关详细信息，请参阅 [MongoDB 插件](/manual/appendix/config/zabbix_agent2_plugins/mongodb_plugin)。

en-us	##### Load on I/O  Item's persistent file is updated after successful sending of every batch of data \(containing item's data\) to server.  For example, default 'BufferSize' is 100.  If a log item has found 70 matching records then the first 50 records will be sent in one batch, persistent file will be updated, then remaining 20 records will be sent \(maybe with some delay when more data is accumulated\) in the 2nd batch, and the persistent file will be updated again.
zh-cn	##### I/O负载  每一批数据 \(包含项目的数据\)成功发送到服务器后，项目的持久文件就会更新， 例如, 默认的 'BufferSize'是100。如果一个日志项找到 70 条匹配记录， 那么前 50 条记录将分批发送，持久化文件将被更新，然后剩余 20 条记录将被发送\(可能会有一些延迟，更多数据积累\) 在第二批中，并且将再次更新持久文件。

en-us	#### Locale  Note that the agent requires a UTF-8 locale so that some textual agent items can return the expected content. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.
zh-cn	 #### 本地环境  值得注意的是，Zabbix agent 需要 UTF-8 语言环境，以便某些文本 Zabbix agent 监控项可以返回预期的内容。 大多数现代类 Unix 系统都默认使用 UTF-8 语言环境，但是，有些系统可能需要特定的设置。

en-us	#### Locale  Note that the proxy requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.
zh-cn	#### 本地环境  请注意，代理需要UTF-8语言环境，以便能够正确解释某些文本项。 大多数现代类unix系统默认使用UTF-8语言环境， 然而，有些系统可能需要专门设置。

en-us	#### Locale  Note that the server requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.
zh-cn	#### 语言环境  值得注意的是，Zabbix server 需要 UTF-8语言环境，以便可以正确解释某些文本项。 大多数现代类 Unix 系统都默认使用UTF-8 语言环境，但是，有些系统可能需要做特定的设置。

en-us	 ##### Log data  See additional information on [log monitoring](log_items).  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**log**\[file,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |Monitoring of a log file.|Log|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0)- possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server. | |**log.count**\[file,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |Count of matched lines in a monitored log file.|Integer|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br><br><br>Matching lines are counted in the new lines since the last log check by the agent, and thus depend on the item update interval.<br>If the file is missing or permissions do not allow access, item turns unsupported. <br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |**logrt**\[file\_regexp,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |Monitoring of a log file that is rotated.|Log|**file\_regexp** - absolute path to file and the file name described by a regular [expression](/manual/regular_expressions#overview). *Note* that only the file name is a regular expression<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0) - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>Note that logrt is designed to work with one currently active log file, with several other matching inactive files rotated. If, for example, a directory has many active log files, a separate logrt item should be created for each one. Otherwise if one logrt item picks up too many files it may lead to exhausted memory and a crash of monitoring.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}$",,,100\] → will match a file like "logfile1" (will not match ".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}$","pattern\_to\_match","UTF-8",100\] → will collect data from files such "logfile\_abc\_1" or "logfile\_\_001".<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> logrt\[/app1/\^test.\*log$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server. | |**logrt.count**\[file\_regexp,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |Count of matched lines in a monitored log file that is rotated.|Integer|**file\_regexp** - absolute path to file and regular [expression](/manual/regular_expressions#overview) describing the file name pattern<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br><br>Matching lines are counted in the new lines since the last log check by the agent, and thus depend on the item update interval.<br><br>Log rotation is based on the last modification time of files. <br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.|
zh-cn	##### 日志数据  更多信息参考 [日志监控](log_items).  |键值|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |**log**\[file,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |监控日志文件。|日志|**file** - 日志文件的全路径<br>**regexp** - 正则[表达式](/manual/regular_expressions#overview) 所需要的匹配的模式<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - 客户端将发送到Zabbix server或proxy的每秒最大行数。此参数覆盖[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中的'MaxLinesPerSecond'值<br>**mode** (自版本 2.0以后)- 可能的值有:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的监控项)。<br>**output** (自版本2.2以后) - 一个可选的输出格式模板，  **\\0** 转义序列被替换为文本的匹配部分 (匹配从开始的第一个字符到结束的字符) 而 **\\N** (其中N=1...9) 转义序列被替换为第 N 个匹配组 (或如果 N 超过捕获的组数，则为空字符串)。<br>**maxdelay** (自版本 3.2后) - 最大延迟，以秒为单位。 类型: 浮点型， 值: 0 - (默认) 从不忽略日志文件行; > 0.0 - 忽略旧行， 以便在“maxdelay”秒内分析最新行。使用前请阅读 [maxdelay](log_items#using_maxdelay_parameter) 说明！<br>**options** (自版本 4.4.7以后) - 附件选项:<br>*mtime-noreread* - 非唯一记录, 仅在文件大小更改时重读 (忽略修改时间更改). (从 5.0.2 开始不推荐使用此参数，因为现在忽略了 mtime。)<br>**persistent\_dir** (从 5.0.18、5.4.9 版本开始，仅在 Unix 系统上的 zabbix_agentd 中；在 Agent2 中不支持) - 存储持久性的目录的绝对路径名文件。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明|该监控项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks)。<br>如果文件丢失或权限不允许访问，监控项变为不受支持。<br><br>如果`output` 留空 - 返回包含匹配文本的整行。 请注意，除 'Result is TRUE' 之外的所有全局正则表达式类型始终返回整个匹配行，并且`output`忽略该参数。<br><br>在agent上使用`output`参数进行内容提取。<br><br>例如:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*使用`output` 参数中从日志记录中提取一个数字 :*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → 将匹配日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并只发送 '6080' 到服务器。 因为发送的是一个数值, 所以该监控项的 "信息类型"可以设置为 "数字(无符号)" 该值可用于图形，触发器等。<br><br>*使用`output` 参数在发送到服务器之前重写日志记录:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → 将匹配日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并且向服务端发送修改后的记录 "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" 。<br><br>另请参阅 [日志监控](log_items)其他信息。| |**log.count**\[file,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |监控日志文件中匹配的行数量|整型|**file** - 含全路径的日志文件名称<br>**regexp** - 正则 [表达式](/manual/regular_expressions#overview)匹配的内容模式 <br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - agent每秒分析新增的最大行数 (不能超过10000)。  在[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中设置的默认值是 10\*'MaxLinesPerSecond'<br>**mode** - 可能的值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的监控项)。<br>**maxdelay** - 最大延迟秒数。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志行数; > 0.0 - 忽略旧行 以便在“maxdelay”秒内分析最新行。使用前请阅读[maxdelay](log_items#using_maxdelay_parameter) 说明!<br>**options** (自4.4.7版后) - 附加选项:<br>*mtime-noreread* - 非唯一记录, 仅在文件大小发生更改时重新读取 (忽略修改时间更改). (从5.0.2开始不推荐使用此参数, 因为现在忽略了mtime。)<br>**persistent\_dir** (从 5.0.18、5.4.9 版本开始，仅在 Unix 系统上的 zabbix_agentd 中；在 Agent2 中不支持) - 存储持久性的目录的绝对路径名文件。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明|该监控项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>如果文件缺失或权限不允许访问，则监控项不受支持。<br><br>另请参阅有关 [日志监控](log_items)的其他信息<br><br>该监控项不支持Windows的事件日志。<br><br>自 Zabbix 3.2.0版本后开始支持。| |**logrt**\[file\_regexp,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |监控轮换的日志文件。|日志|**file\_regexp** - 文件的绝对路径和正则[表达式](/manual/regular_expressions#overview)匹配的文件名模式 *请注意* 只有文件名是正则表达式<br>**regexp** - 描述正则[表达式](/manual/regular_expressions#overview)匹配的文件内容模式 <br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - agent每秒将发送到 Zabbix 服务器或代理的最大新行数。 此参数覆盖[zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)的 'MaxLinesPerSecond'的值 <br>**mode** (自版本 2.0后) - 可能值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的监控项)。<br>**output** (自版本2.2后) - 一个可选的输出格式模板。**\\0** 转义序列被替换文本的匹配部分 (匹配从开始的第一个字符到结束的字符) 而  **\\N** (其中 N=1...9) 转义序列被替换为第N个匹配组 (或如果N超过捕获的组数，则为空字符串)。<br>**maxdelay** (自版本 3.2后) -最大的时延，以秒为单位。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志文件行数; > 0.0 - 忽略旧行，以便在“maxdelay”秒内分析最新行。使用前请阅读 [maxdelay](log_items#using_maxdelay_parameter) 说明!<br>**options** (版本4.0和版本4.4.7后; *mtime-reread*, 和*mtime-noreread*选项 ) - 日志文件轮换类型和其他选项。可能的值:<br>*rotate* (默认),<br>*copytruncate* - 注意的是 *copytruncate* 不能和 *maxdelay*一起使用，在这种情况下 *maxdelay* 必须为0或未指定; 参阅 [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) 文档。<br>*mtime-reread* - 非唯一记录，如果修改时间或大小更改则重新读取(默认),<br>*mtime-noreread* -非唯一记录，仅在大小更改时重新读取 (忽略修改时间更改)。<br>**persistent\_dir** (从 5.0.18, 5.4.9版本开始,仅在Unix系统 zabbix\_agentd中; 不支持 Agent2) - 存储持久文件的目录的绝对路径名。另请参阅有关 [持久文件](log_items#notes-on-persistent-files-for-log-items)的附加说明。|该监控项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>日志轮换基于文件的最后修改时间。<br><br请注意，logrt 旨在处理一个当前活动的日志文件，并轮换几个其他匹配的非活动文件。例如，如果一个目录有许多活动日志文件，则应为每个文件创建一个单独的 logrt 项。否则，如果一个 logrt 项获取太多文件，可能会导致内存耗尽和监控崩溃。<br><br>如果 `output` 留空 - 返回包含匹配文本的整行。请注意，除 'Result is TRUE' 之外的所有全局正则表达式类型始终返回整个匹配行，并且`output` 忽略该参数.<br><br>在代理上使用`output`参数进行内容提取。<br><br>例如:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}\$",,,100\] → 将匹配文件名如"logfile1"(不会匹配".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}\$","pattern\_to\_match","UTF-8",100\] → 将从文件名如 "logfile\_abc\_1" 或 "logfile\_\_001"中采集数据<br><br>*使用 `output` 参数 从日志记录中提取数字:*<br>=> logrt\[/app1/\^test.\*log\$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] →将匹配一条日志记录 "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并发送 '6080' 到服务端。 因为发送的数值， 所以此监控项 "信息类型" 可以设置为 "数字 (无符号)" 这个值可以用于图形，触发器等。<br><br>*使用 `output` 参数可以在发送到服务端前重写日志记录:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → 将匹配一条日志记录  "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" 并发送修改记录到服务端 "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" 。<br><br>另请参阅 [日志监控](log_items)其他信息。| |**logrt.count**\[file\_regexp,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<| |轮换的监控日志文件中的匹配行数|整型|**file\_regexp** - 文件绝对路径和正则 [表达式](/manual/regular_expressions#overview) 所需匹配的文件名模式<br>**regexp** - 正则 [表达式](/manual/regular_expressions#overview) 所需的内容匹配模式<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - agent每秒分析新增的最大行数 (不能超过10000)。在 [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)中设置的默认值是10\*'MaxLinesPerSecond'。<br>**mode** - 可能值:<br>*all* (默认), *skip* - 跳过旧数据的处理 (仅影响新创建的监控项).<br>**maxdelay** - 最大时延，以秒为单位。 类型: 浮点型。 值: 0 - (默认) 从不忽略日志文件行; > 0.0 - 以便在“maxdelay”秒内分析最新行。使用前请阅读[maxdelay](log_items#using_maxdelay_parameter)说明!<br>**options** (自版本 4.0和4.4.7后; *mtime-reread*和*mtime-noreread* 选项) - 日志文件轮换类型和其他选项， 可能的值:<br>*rotate* (默认),<br>*copytruncate* - 注意 *copytruncate* 不能与 *maxdelay*一起使用，这种情况下 *maxdelay* 必须为0或未指定; 参阅 [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) 说明,<br>*mtime-reread* - 非唯一记录, 如果修改时间或大小改变重新读 (默认),<br>*mtime-noreread* - 非唯一记录, 仅当大小改变时重新读 (忽略修改时间的改变)。<br>**persistent\_dir** (自版本 5.0.18和 5.4.9后, 仅在Unix系统上的zabbix\_agentd中;不支持 Agent2) -  存储持久文件的目录的绝对路径名。另请参阅有关[持久文件](log_items#notes-on-persistent-files-for-log-items)附加说明。|该监控项必须配置为 [主动检查](/manual/appendix/items/activepassive#active_checks).<br>日志轮换基于文件的最后修改时间。<br><br>另请参阅有关[日志监控](log_items)其他信息<br><br>此监控项不支持Windows事件日志<br><br>自Zabbix 3.2.0后开始支持|

en-us	### Log entry  The log entry object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |level|integer|Log level.| |ms|string|The time elapsed in milliseconds since the script was run before log entry was added.| |message|string|Log message.|
zh-cn	### 日志条目 日志条目对象有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |level|integer|日志等级。| |ms|string|从脚本开始运行到添加日志条目前经过时间（毫秒）。| |message|string|日志信息。|

en-us	### Log entry  The log entry object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |level|integer|Log level.| |ms|string|The time elapsed in milliseconds since the script was run before log entry was added.| |message|string|Log message.|
zh-cn	### 日志条目 日志条目对象有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |level|integer|日志等级。| |ms|string|从脚本开始运行到添加日志条目前经过时间（毫秒）。| |message|string|日志信息。|

en-us	#### Log file monitoring  `log[]` and `logrt[]` items repeatedly reread log file from the beginning if file system is 100% full and the log file is being appended (see [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) for more information).
zh-cn	#### 日志文件监控  如果文件系统达到 100% 并且日志正在追加，则 `log[]` 和 `logrt[]` 监控项会从头重读日志文件，（参阅 [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) ）获取更多。

en-us	#### Log file monitoring  `log[]` and `logrt[]` items repeatedly reread log file from the beginning if file system is 100% full and the log file is being appended (see [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) for more information).  
zh-cn	#### 日志文件监控  如果文件系统达到 100% 并且日志正在追加，则 `log[]` 和 `logrt[]` 监控项会从头重读日志文件，（参阅 [ZBX-10884](https://support.zabbix.com/browse/ZBX-10884) ）获取更多。

en-us	##### Logging  Add the "Log test" entry to the Zabbix server log and receive the item value "1" in return:  -   Create an item with type "Script".\ -   In the *Script* field, enter the following code:  ``` {.java} Zabbix.log(3, 'Log test'); return 1; ```
zh-cn	##### 记录日志  添加"Log test"到Zabbix server 日志并返回数值 "1"给监控项：  - 创建一个监控项，类型选择”脚本“。  - 在*脚本*字段填写下面的代码：  ``` {.java} Zabbix.log(3, 'Log test'); return 1; ```

en-us	#### Logging out  Log out from the API.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.logout",     "params": [],     "id": 1,     "auth": "16a46baf181ef9602e1687f3110abf8a" } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```
zh-cn	#### 注销  通过API注销.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.logout",     "params": [],     "id": 1,     "auth": "16a46baf181ef9602e1687f3110abf8a" } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```

en-us	### Log history  The log history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.|
zh-cn	 ### 日志型历史数据  日志型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |id|string|历史条目的 ID。| |clock|timestamp|收到值的时间。| |itemid|string|相关监控项的 ID。| |logeventid|integer|Windows 事件日志条目的 ID。| |ns|integer|收到值时的纳秒数。| |severity|integer|Windows 事件日志条目的级别。| |source|string|Windows 事件日志条目的来源。| |timestamp|timestamp|Windows 事件日志条目的时间。| |value|text|收到的值。|

en-us	### Log history  The log history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.|
zh-cn	 ### 日志型历史数据  日志型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |id|string|历史条目的 ID。| |clock|timestamp|收到值的时间。| |itemid|string|相关监控项的 ID。| |logeventid|integer|Windows 事件日志条目的 ID。| |ns|integer|收到值时的纳秒数。| |severity|integer|Windows 事件日志条目的级别。| |source|string|Windows 事件日志条目的来源。| |timestamp|timestamp|Windows 事件日志条目的时间。| |value|text|收到的值。|

en-us	#### Login and systemd  We recommend [creating](/manual/installation/install#create_user_account) a *zabbix* user as system user, that is, without ability to log in. Some users ignore this recommendation and use the same account to log in (e. g. using SSH) to host running Zabbix. This might crash Zabbix daemon on log out. In this case you will get something like the following in Zabbix server log:      zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument     zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument     zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument  and in Zabbix agent log:      zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument  This happens because of default systemd setting `RemoveIPC=yes` configured in `/etc/systemd/logind.conf`. When you log out of the system the semaphores created by Zabbix previously are removed which causes the crash.  A quote from systemd documentation:      RemoveIPC=      Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the     user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources     after the last of the user's sessions terminated. This covers System V semaphores, shared memory     and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the     root user and other system users are excluded from the effect of this setting. Defaults to "yes".  There are 2 solutions to this problem:  1.  (recommended) Stop using *zabbix* account for anything else than     Zabbix processes, create a dedicated account for other things. 2.  (not recommended) Set `RemoveIPC=no` in `/etc/systemd/logind.conf`     and reboot the system. Note that `RemoveIPC` is a system-wide     parameter, changing it will affect the whole system.
zh-cn	#### Login 和 systemd  我们建议[创建](/manual/installation/install#create_user_account) 一个 *zabbix*用户作为系统用户，但不允许登录。一些用户忽略此建议并使用相同的帐户登录（例如使用 SSH）来登录运行 Zabbix 的主机。这可能会使 Zabbix 守护进程在注销时崩溃。在这种情况下，您将在 Zabbix server 日志中获得类似以下内容：      zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument     zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument     zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument  并且在 Zabbix agent 日志中：      zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument  这是因为默认的 systemd 设置 `RemoveIPC=yes`在`/etc/systemd/logind.conf`中配置。 当您退出系统时，Zabbix 之前创建的信号量会被删除，这会导致崩溃。  来自 systemd 文档的引用：      RemoveIPC=      Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the     user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources     after the last of the user's sessions terminated. This covers System V semaphores, shared memory     and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the     root user and other system users are excluded from the effect of this setting. Defaults to "yes".  这个问题有2个解决方案：  1. （推荐）停止使用*zabbix* 帐户来处理除 Zabbix 进程之外的任何事情，为其他事情创建一个专用帐户。 2. （不推荐）设置`RemoveIPC=no` 在`/etc/systemd/logind.conf`中并重新启动系统。  请注意， `RemoveIPC` 是一个系统范围的参数，更改它会影响整个系统。

en-us	#### Login  ![](../../../assets/en/manual/quickstart/login.png){width="350"}  This is the Zabbix welcome screen. Enter the user name **Admin** with password **zabbix** to log in as a [Zabbix superuser](/manual/config/users_and_usergroups/permissions). Access to *Configuration* and *Administration* menus will be granted.
zh-cn	#### 登录  ![](../../../assets/en/manual/quickstart/login.png){width="350"}  这是Zabbix的“欢迎”界面。输入用户名 **Admin** 以及密码 **zabbix** 以作为 [Zabbix超级用户](/manual/config/users_and_usergroups/permissions)登录。将授予访问*配置*和*管理*菜单的权限。

en-us	#### Log in  Zabbix frontend is ready! The default user name is **Admin**, password **zabbix**.  ![](../../../assets/en/manual/quickstart/login.png){width="350"}  Proceed to [getting started with Zabbix](/manual/quickstart/login).
zh-cn	#### 登录  Zabbix 前端已准备就绪！ 默认用户名是**Admin**，密码**zabbix**。  ![](../../../assets/en/manual/quickstart/login.png){width="350"}  继续 [getting started with Zabbix](/manual/quickstart/login).

en-us	###      Log level control targets     *process-type*   All processes of specified type (active checks, collector, listener)     *process-type,N*   Process type and number (e.g., listener,3)     *pid*   Process identifier, up to 65535. For larger values specify target as "process-type,N"  ```{=html} <!-- --> ``` **-p**, **--print**   Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are:     d   Number with a decimal part.     m   Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state.     s   Text. Maximum length not limited.     t   Text. Same as **s**.     u   Unsigned integer.  **-t**, **--test** *item-key*   Test single item and exit. See **--print** for output description.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAH}
zh-cn	 ###     日志级别控制目标     *process-type*   所有指定类型的进程（活动检查、收集器、侦听器）     *process-type,N*   进程类型和编号（例如，listener,3）    *pid*   进程标识符，最多65535。对于较大的值，将目标指定为"process-type,N"  ```{=html} <!-- --> ``` **-p**, **--print**   打印已知项目并退出。对于每个项目，要么使用通用默认值，要么提供用于测试的特定默认值。这些默认值作为项目关键参数列在方括号中。返回值括在方括号中，以返回值的类型为前缀，用竖线字符分隔。对于用户参数，类型始终为 **t**，因为agent无法确定所有可能的返回值。当查询正在运行的agent守护程序时，因为权限或环境可能不同，不保证在 Zabbix 服务器或 zabbix\_get中显示为工作中的项目。返回值类型包括：     d   带有小数部分的数字。     m   不支持。这可能是由于查询仅在活动模式下工作的项目（如日志监视项目或需要多个收集值的项目）引起的。权限问题或不正确的用户参数也可能导致"不支持"状态。     s   文本。最大长度不受限制。     t   文本。和 **s** 一样。     u   无符号整数。  **-t**, **--test** *item-key*   测试单个项目并退出。查看 **--print** 部分的输出描述。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAH}

en-us	###      Log level control targets     *process-type*   All processes of specified type (configuration syncer, data sender, discoverer, heartbeat sender, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, self-monitoring, snmp trapper, task manager, trapper, unreachable poller, vmware collector)     *process-type,N*   Process type and number (e.g., poller,3)     *pid*   Process identifier, up to 65535. For larger values specify target as "process-type,N"  ```{=html} <!-- --> ``` **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAH}
zh-cn	 ###      日志级别控制目标     *process-type*   指定类型的所有进程 (configuration syncer, data sender, discoverer, heartbeat sender, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, poller, self-monitoring, snmp trapper, task manager, trapper, unreachable poller, vmware collector)     *process-type,N*   进程类型和编号（例如，poller,3）     *pid*   进程标识符，最多65535。对于较大的值，将目标指定为"process-type,N"  ```{=html} <!-- --> ``` **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAH}

en-us	##### Log rotation  Zabbix does not provide any log rotation system - that should be handled by the user. The log rotation should first rename the old file and only later delete it so that no traps are lost:\  1.  Zabbix opens the trap file at the last known location and goes to     step 3 2.  Zabbix checks if the currently opened file has been rotated by     comparing the inode number to the defined trap file's inode number.     If there is no opened file, Zabbix resets the last location and goes     to step 1. 3.  Zabbix reads the data from the currently opened file and sets the     new location. 4.  The new data are parsed. If this was the rotated file, the file is     closed and goes back to step 2. 5.  If there was no new data, Zabbix sleeps for 1 second and goes back     to step 2.
zh-cn	##### 日志轮询  Zabbix不提供任何日志轮询系统（它应由用户处理）。 日志轮询应该首先重命名旧文件，然后才能将其删除，以免丢失trap：\  1.   Zabbix在最后一个已知位置打开trap文件，并转到步骤3 2.   Zabbix通过比较inode号和定义trap文件的inode号，检查当前打开的文件是否已经轮换。如果没有打开的文件，Zabbix将重置最后一个位置并转到步骤1。 3.   Zabbix从当前打开的文件中读取数据并设置新的位置。 4.   新数据被解析。如果这是轮询的文件，文件将关闭并返回到步骤2。 5.   如果没有新的数据，Zabbix 等待1秒钟后，然后回到步骤2。

en-us	#### Low-level discovery  Configure low-level discovery rules as well as item, trigger and graph prototypes to monitor dynamic entities.  [LLD rule API](/manual/api/reference/discoveryrule) | [Item prototype API](/manual/api/reference/itemprototype) | [Trigger prototype API](/manual/api/reference/triggerprototype) | [Graph prototype API](/manual/api/reference/graphprototype) | [Host prototype API](/manual/api/reference/hostprototype)
zh-cn	#### 低级别自动发现  配置低级发现规则以及项目，触发器和图形原型来监视动态实体。  [LLD rule API](/manual/api/reference/discoveryrule) | [Item prototype API](/manual/api/reference/itemprototype) | [Trigger prototype API](/manual/api/reference/triggerprototype) | [Graph prototype API](/manual/api/reference/graphprototype) | [Host prototype API](/manual/api/reference/hostprototype)

en-us	#### Low-level discovery  In a [low-level discovery rule](/manual/discovery/low_level_discovery#configuring_low-level_discovery), user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Key parameters|<|yes| |Update interval|<|no| |Custom interval|<|no| |Keep lost resources period|<|no| |Description|<|yes| |*SNMP agent*|<|<| | |SNMP OID|yes| |*SSH agent*|<|<| | |Username|yes| |^|Public key file|yes| |^|Private key file|yes| |^|Password|yes| |^|Script|yes| |*TELNET agent*|<|<| | |Username|yes| |^|Password|yes| |^|Script|yes| |*Zabbix trapper*|<|<| | |Allowed hosts|yes| |*Database monitor*|<|<| | |Username|yes| |^|Password|yes| |^|SQL query|yes| |*JMX agent*|<|<| | |JMX endpoint|yes| |*HTTP agent*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|yes| |^|Query fields|yes| |^|Timeout|no| |^|Request body|yes| |^|Headers (names and values)|yes| |^|Required status codes|yes| |^|HTTP authentication username|yes| |^|HTTP authentication password|yes| |*Filters*|<|<| | |Regular expression|yes| |*Overrides*|<|<| | |Filters: regular expression|yes| |^|Operations: update interval (for item prototypes)|no| |^|Operations: history storage period (for item prototypes)|no| |^|Operations: trend storage period (for item prototypes)|no|
zh-cn	#### 底层自动发现  在[底层自动发现规则](/manual/discovery/low_level_discovery#configuring_low-level_discovery)中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |键参数|<|支持| |更新间隔|<|不支持| |自定义间隔|<|不支持| |保留失效资源的时间|<|不支持| |描述|<|支持| |*SNMP 代理*|<|<| | |SNMP OID|支持| |*SSH 代理*|<|<| | |用户名|支持| |^|公钥文件|支持| |^|私钥文件|支持| |^|密码|支持| |^|脚本|支持| |*TELNET 代理*|<|<| | |用户名|支持| |^|密码|支持| |^|脚本|支持| |*Zabbix采集器*|<|<| | |允许的主机|支持| |*数据库监控*|<|<| | |用户名|支持| |^|密码|支持| |^|SQL查询|支持| |*JMX 代理*|<|<| | |JMX 端点|支持| |*HTTP 代理*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|支持| |^|查询字段|支持| |^|超时时间|不支持| |^|请求正文|支持| |^|请求头部 (名字和值)|支持| |^|返回状态码|支持| |^|HTTP认证用户名|支持| |^|HTTP认证密码|支持| |*过滤器*|<|<| | |正则表达式|支持| |*覆盖*|<|<| | |过滤器：正则表达式|支持| |^|操作: 更新间隔 (对于监控项原型)|不支持| |^|操作: 历史存储周期 (对于监控项原型)|不支持| |^|操作: 趋势存储周期 (对于监控项原型)|不支持|