1 Zabbix客户端

1 Zabbix客户端

概述

这些检查与Zabbix代理进行通信实现数据的采集。

有被动和主动两种agent模式. 在配置监控项时，你可以选择所需的类型：

Zabbix 客户端 - 被动模式，Zabbix Server向Agent索要数据
Zabbix 客户端 (主动式) - 主动模式，Agent主动上报数据给Zabbix Server

支持的监控项key

下表提供了可用的Zabbix代理监控项键值的详细信息。

请参考:

** 必填和可选参数 **

没有尖括号的参数是强制性的。标有尖括号 < > 的参数是可选的。

键值
	描述	返回值参数	注释
agent.hostname
	客户端主机名. Strin		从配置文件	回客户端主机名的实际值。
agent.ping
	客户端可用性检查 Nothing	- 不可用 1 - 可用	使用nodata	)触发器函数检查主机不可用性。
agent.version
	Zabbix 客户端的版本字符串		例如返回值:	<1.8.2
kernel.maxfiles
	系统支持的打开文件的最大数量整数
kernel.maxproc
	系统支持的最大进程数整数
log[file,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>]
	日志文件监控。 Log	file	- 日志文件完整路径和名称监控项必须定义为主动检查, skip - 跳过处理历史的数据（仅影响新创建的监控项）。在客户端端使用`output` 参数提取内容。 output - 可选项，输出格式模板。 \0转义序列替换为匹配的文本，而\N（其中N = 1 … 9）转义序列被替换为第N个匹配组（如果N超过捕获组的数量，则为空字符串）。 maxdelay - 最大延迟（秒）。类型：float。值：0-（默认）不忽略日志文件行; > 0.0-忽略旧行，以便在“maxdelay”秒内获取最近分析的行。使用前请阅读 maxdelay注释！示例:	/manual/appendix/items/activepassive#active_checks). 访问，则监控项不受支持。行。请注意，除“Result为TRUE”之外的所有全局正则表达式类型始终返回整个匹配行，并忽略`output` 参数。 => log[/var/log/syslog] => log[/var/log/syslog,error] => log[/home/zabbix/logs/logfile,,,100] 使用`output`参数从日志记录中提取数字的示例： 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 number 6080 to server. Because a number is being sent, the “Type of information” for this log item can be changed from “Log” to “Numeric (unsigned)” and the value can be used in graphs, triggers etc. 在发送到服务器之前使用`output`参数重写日志记录的示例： 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. `mode` 参数从Zabbix 2.0之后被支持。 `output` 从Zabbix 2.2之后被支持 `maxdelay`参数从Zabbix 3.2以后被支持。更多信息请参考日志文件监控.
log.count[file,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>]
	日志文件监控中匹配行的数量。整数	file - 日志文件	整的路径和名称该监控项必须配置为[主动检查](/zh/manual/regexp - 正则表达式如果文件encoding - 编码标识符 maxproclines - Agent将分析每秒最大行数。默认值为 10‘MaxLinesPerSecond’在zabbix_agent配置文件. 查看更多信息在日志文件监控, skip - 跳过处理老数据（仅影响新创建的监控项）。从Zabbix 3.2.0开始支持maxdelay - 最大延迟秒数。类型: float. 值: 0 - (默认) 从不忽略每行日志; > 0.0 - 忽略旧行，以便在“maxdelay”秒内获取最近分析的行。在使用前请阅读maxdelay参数的注解！	ppendix/items/activepassive#active_checks). 失或权限不允许访问，则监控项不受支持。 _items).
logrt[file_regexp,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>]
	支持监控轮询的日志文件。 Log	filereg	xp - 文件名以及正则表达式定义的文件名的绝对路径。监控项必须配置为主动检查, skip - 跳过处理旧数据（仅影响新创建的监控项）。在Agent端使用输出参数提取内容。 output - 一个可选的输出格式模板。 \0 转义序列替换为匹配文本，而\N（其中N = 1 … 9）转义序列被替换为第N个匹配组（如果N超过捕获组的数量，则为空字符串）。 maxdelay - 最大延迟（秒）。类型：float。值：0-（默认）不忽略日志文件行; > 0.0-忽略旧行，以便在“maxdelay”秒内获取最近分析的行。使用前请阅读maxdelay参数注释！示例: options** - 日志文件轮换的类型. 可能的值： => logrt[轮换 (默认), copytruncate。请注意，copytruncate不能与maxdelay一起使用。在这种情况下，maxdelay必须为0或未指定。请参见copytruncate注释。 => logrt[“/home/user/^logfile.	/items/activepassive#activechecks). 改时间。 t为TRUE”之外的所有全局正则表达式类型始终返回整个匹配行，并忽略输出参数。 /home/zabbix/logs/^logfile[0-9]{1,3}$”,,,100] → 将返回一个文件类似”logfile1” (不会匹配”.logfile1”) [0-9]{1,3}$”,”patternto_match”,”UTF-8”,100] → 将从文件收集信息例如 “logfile_abc_1” 或者 “logfile__001”. 使用`output`参数从日志记录中提取数字的示例： 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 number 6080 to server. 由于正在发送一个数字，因此该日志项的“信息类型”可以从“日志”更改为“数字（无正负）”，并且该值可以用于图形，触发器等。在发送到服务器之前使用`output`参数重写日志记录的示例： 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. `mode` 参数从Zabbix 2.0以后开始支持。 `output`参数从Zabbix 2.2开始支持。 `maxdelay`参数从Zabbix 3.2开始支持。 `options` 参数从Zabbix 4.0开始支持。更多信息请参考日志文件监控.
logrt.count[file_regexp,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>]
	支持对循环日志文件监控中匹配的行数。整型	file_regexp -	件名以及正则表达式定义的文件名的绝对路径。监控项必须定义为[主动检查](/zh/manual/appendix/items/regexp - 描述匹配内容的正则表达式。日志轮询是基于文件的最后encoding - 编码标识符 maxproclines - Agent将分析每秒最大新生成行数。默认值为 4‘MaxLinesPerSecond’ 定义在 zabbix_agent配置文件. 更多信息请参考日志文件监控, skip - 跳过处理旧数据（仅影响新创建的监控项）。 `options` 参数从Zabbix 4maxdelay - 最大延迟（秒）。类型：float。值：0-（默认）不忽略日志文件行; > 0.0-忽略旧行，以便在“maxdelay”秒内获取最近分析的行。使用前请阅读maxdelay参数注释！ options - 日志文件轮换的类型. 可能的值：从Zabbix 3.2.0轮换 (默认), copytruncate。请注意，copytruncate不能与maxdelay一起使用。在这种情况下，maxdelay必须为0或未指定。请参见copytruncate注释。	ctivepassive#active_checks). 改时间。 ms)。 0开始支持。开始支持。
net.dns[<ip>,name,<type>,<timeout>,<count>,<protocol>]
	检查DNS服务是否开启。 0 - DNS宕	(服务器没有响应或DNS解析失败) ip - DNS服务器的IP地址（默 1 - DNS正在运行 t	DNS服务器为空，在Windows上被忽略）示例: name - 要查询的DNS名称 =>pe - 要查询的记录类型 (默认为 SOA) timeout (在windows上忽略) - 请求的超时秒数（默认为1秒） `type` 可选的值为: count (在windows上忽略) - 请求的尝试次数 (默认为2) ANY, A, protocol - 用于执行DNS查询的协议：udp (默认) 或者 tcp	<net.dns[8.8.8.8,zabbix.com,MX,2,1] S, CNAME, MB, MG, MR, PTR, MD, MF, MX, SOA, NULL, WKS (Windows系统除外), HINFO, MINFO, TXT, SRV 不支持国际化域名，请改用IDNA编码名称。 Zabbix 3.0支持 `protocol` 参数。 Zabbix Agent从版本1.8.6（Unix）和2.0.0（Windows）开始支持SRV记录类型。 Zabbix 2.0之前命名（仍然支持）: net.tcp.dns
net.dns.record[<ip>,name,<type>,<timeout>,<count>,<protocol>]
	执行一个DNS查询字符串与所	类型的信息 ip - DNS服务器的	P地址（默认DNS服务器为空，在Windows上被忽略）示例: name - 要查询的DNS名称 =>type - 要查询的记录类型 (默认为 SOA) timeout (在windows上忽略) - 请求的超时秒数（默认为1秒） `type` 可选的值为: count (在windows上忽略) - 请求的尝试次数 (默认为2) ANY, A, protocol - 用于执行DNS查询的协议：udp (默认) 或者 tcp	<net.dns[8.8.8.8,zabbix.com,MX,2,1] S, CNAME, MB, MG, MR, PTR, MD, MF, MX, SOA, NULL, WKS (Windows系统除外), HINFO, MINFO, TXT, SRV 不支持国际化域名，请改用IDNA编码名称。 Zabbix 3.0支持 `protocol` 参数。 Zabbix Agent从版本1.8.6（Unix）和2.0.0（Windows）开始支持SRV记录类型。 Zabbix 2.0之前命名（仍然支持）: net.tcp.dns.query
net.if.collisions[if]
	Number of out-of-window collisions.	整型	if** - 网卡名称
net.if.discovery
	网络接口列表用于低级发现。 JSON 对象		Zabbix agent从2	0之后开始支持。 Zabbix agent在FreeBSD, OpenBSD 和 NetBSD系统从2.2开始支持。某些Windows版本（例如Server 2008）可能需要安装最新的更新以支持网卡名称中的非ASCII字符。
net.if.in[if,<mode>]
	网卡流入量统计。整型	if -	卡名 (Unix); 网卡完整描述或IPv4地址（Windows）在Windows上，该选项从64位计数器获取值mode - 可用的值: bytes - 字节数(默认) 从Zabpackets - 包数量 errors - 错误数量示例:dropped - 丢包数量 =&goverruns (fifo) - FIFO缓冲区错误的数量 => nframe - 包帧错误的数量 compressed - 设备驱动程序发送或接收的压缩包数你可以使用net.if.dismulticast - 设备驱动程序接收的组播帧数	如果可用）。64位接口统计计数器在Windows Vista和Windows Server 2008中引入。如果64位计数器不可用，代理使用32位计数器。 ix Agent1.8.6版本起，支持Windows上的多字节接口名称。 ; net.if.in[eth0,errors] t.if.in[eth0] overy或net.if.list监控项在Windows上获取网卡说明。你可以使用该键与Delta（每秒速度）存储值，以获得每秒字节的统计信息。
net.if.out[if,<mode>]
	网卡流出量统计。整型	if -	卡名称 (Unix); 网卡完整描述或IPv4地址（Windows）在Windows上，该选项从64位计数器获取值（mode - 可用的值: bytes - 字节数(默认) 从Zabpackets - 包数量 errors - 错误数量示例:dropped - 丢包数量 =&goverruns (fifo) - FIFO缓冲区错误的数量 => ncollisions (colls) - 在接口上检测到的冲突数 carrier - 设备驱动程序检测到的载波丢失数你可以使用net.if.dicompressed - 设备驱动程序发送或接收的压缩包数	果可用）。64位接口统计计数器在Windows Vista和Windows Server 2008中引入。如果64位计数器不可用，代理使用32位计数器。 ix Agent1.8.6版本起，支持Windows上的多字节接口名称。 ; net.if.out[eth0,errors] t.if.out[eth0] covery或net.if.list监控项在Windows上获取网卡说明。你可以使用该键与Delta（每秒速度）存储值，以获得每秒字节的统计信息。
net.if.total[if,<mode>]
	网卡的进出流量统计信息的总和。整型	if - 网卡名称(Un	x); 网卡完整描述或IPv4地址（Windows）在Windows上，该选项从64位计数器获取值（如果可用）。6mode - 可用的值: bytes - 字节数(默认) 示例: packets - 包数量 =&errors - 错误数量 =&gdropped - 丢包数量 overruns (fifo) - FIFO缓冲区错误的数量 You maycompressed - 设备驱动程序发送或接收的压缩包数	位接口统计计数器在Windows Vista和Windows Server 2008中引入。如果64位计数器不可用，代理使用32位计数器。 t; net.if.total[eth0,errors] ; net.if.total[eth0] obtain network interface descriptions on Windows with net.if.discovery or net.if.list items. 你可以使用net.if.discovery或net.if.list监控项在Windows上获取网卡说明。你可以使用该键与Delta（每秒速度）存储值，以获得每秒字节的统计信息。请注意，只有当net.if.in和net.if.out都用于平台上丢弃的数据包时，丢弃的数据包才被支持。
net.tcp.listen[port]
	检查此TCP端口是否处于监听状态。 0 - 未监听	port - TCP端口 1 - 处于监听状态	示例:	<=> net.tcp.listen[80] 在Zabbix代理版本1.8.4之后支持Linux。从Zabbix 3.0.0之后，在Linux内核2.6.14及更高版本上从内核的NETLINK接口获取有关监听TCP套接字的信息。否则，将从/proc/net/tcp和/proc/net/tcp6文件中检索该信息。
net.tcp.port[<ip>,port]
	检查是否可以将TCP连接到指定的端口。 0 - 不能连接	ip - IP地址 (默认是 1 - 可以连接	27.0.0.1) 示例: port - 端口 =	<gt; net.tcp.port[,80] → 可用于测试在端口80上运行的Web服务器的可用性。对于简单的TCP性能测试，使用 net.tcp.service.perf[tcp,<ip>,<port>] 请注意，这些检查可能会导致增加系统守护程序日志文件中的额外信息（通常会记录SMTP和SSH会话）。旧的命名方式: check_port[]
net.tcp.service[service,<ip>,<port>]
	检查服务是否正在运行并接受TCP连接。 0 - 服务停止运行	service - 如下任一服务: 1 - 服务正在运行 ip	示例: ssh, ldap, smtp, ftp, http, pop, nntp, .imap, tcp, https, telnet (查看详细信息) =>- IP地址 (默认是 127.0.0.1) port - 端口号 (默认为标准服务端口号) 请注意，这些检测可能会导	<net.tcp.service[ftp,,45] → 可用于检测FTP服务器上TCP端口45的可用性。增加系统守护程序日志文件的信息（通常会记录SMTP和SSH会话）。目前不支持检测加密协议（如端口993上的IMAP或端口995上的POP）。一个解决方案是使用net.tcp.port来检测这些。目前不支持Windows 客户端检测LDAP和HTTPS。请注意，telnet检测查找登录提示符（’：’在结尾）。请参考HTTPS服务检测的已知问题。 https 和 telnet 服务从Zabbix 2.0开始支持。旧命名: check_service[]
net.tcp.service.perf[service,<ip>,<port>]
	检测TCP服务性能 0 - 服	停止运行。 service seconds - 连接到服务花费的时间（秒） ip - IP	如下任一服务: 示例: ssh, ldap, smtp, ftp, http, pop, nntp, imap, tcp, https, telnet (参考详细描述) =>址(默认为 127.0.0.1) port - 端口号 (默认为标准服务端口号) 目前不支持检测加密协议	<net.tcp.service.perf[ssh] → 可以用来检测SSH服务器的初始响应速度。如IMAP 上的端口993或者POP上的端口995) 。一个解决方案是使用net.tcp.service.perf[tcp,<ip>,<port>]来检测。目前不支持Windows代理检查LDAP和HTTPS。请注意，telnet检测查找登录提示符（’：’在结尾）。请参考检测HTTPS服务的已知问题 https 和 telnet 服务从Zabbix 2.0开始支持。旧名称: check_service_perf[]*
net.udp.listen[port]
	检测UDP端口是否处于监听状态。 0 - 未监听。	port - UDP端口 1 - 处在监听状态。	示例:	<=> net.udp.listen[68] 在Linux平台从Zabbix agent version 1.8.4 开始支持。
net.udp.service[service,<ip>,<port>]
	检查服务是否正在运行并能响应UDP请求。 0 - 服务停止运行。	service - ntp (参考 1 - 服务正在运行 por	详细信息) 示例: ip - IP地址 (默认是127.0.0.1) =&gt - 端口号 (默认使用标准服务端口号)	<net.udp.service[ntp,,45] → 可用于测试UDP端口45上NTP服务的可用性。此选项从Zabbix 3.0.0起支持，但ntp服务可用于以前版本中的net.tcp.service []选项。
net.udp.service.perf[service,<ip>,<port>]
	检测UDP服务的性能 0 - 服务	止运行 service seconds - 等待服务响应的秒数 port	ntp (参考详细信息) 示例: ip - IP地址 (默认为 127.0.0.1) =&gt- 端口 (默认使用标准服务端口号)	<net.udp.service.perf[ntp] → 可用于测试NTP服务的响应时间。此选项从Zabbix 3.0.0起支持，但ntp服务可用于以前版本中的net.tcp.service []选项。
proc.cpu.util[<name>,<user>,<type>,<cmdline>,<mode>,<zone>]
	进程CPU利用率百分比。浮点型	name -	程名 (默认为 all processes) 示例: user - 用户名 (默认为 all users) =>type - CPU利用率类型: =&gttotal (默认), user, system cmdline - 可按命令行过滤（支持正则表达式）返回值基于单CPU核的利用率。mode - 数据收集模式: avg1 (默认), avg5, avg15 zone - 目标区域: current (默认), all. 此参数仅在Solaris平台上受支持。从Zabbix 3.0.3开始，如果代理程序已在Solaris上编译且没有区域支持，而是在支持区域的较新Solaris上运行，并且<zone>参数为缺省值或当前值，则代理程序将返回NOTSUPPORTED（该代理程序不能将结果限制为仅当前区）。但是，在这种情况下，支持<zone>参数值all。进程CPU利用率数据由收集器收集，该收集器最多支持1024个唯一（按名称，用户和命令行）查询。过去24小时内未被访问的查询将从收集器中删除。	<proc.cpu.util[,root] → 在“root”用户下运行的所有进程的CPU利用率。 proc.cpu.util[zabbix_server,zabbix] → 在zabbix用户下运行的所有zabbix_server进程的CPU利用率。如，使用两个内核的进程的CPU利用率为200％。自Zabbix 3.0.0起支持此Key，并可在多个平台上使用 (请查看平台支持的监控项).
proc.mem[<name>,<user>,<mode>,<cmdline>,<memtype>]
	用户进程使用的内存。整型	name -	程名 (默认是全部进程) 示例: user - 用户名 (默认是全部用户) => promode - 可能的值: =&gavg, max, min, sum (默认值) =&cmdline - 按命令行过滤（它是一个正则表达式） memtype - 进程使用的内存类型注意: 当多	<.mem[,root] → “root”用户运行的所有进程使用的内存 ; proc.mem[zabbix_server,zabbix] → zabbix用户运行的所有zabbix_server进程使用的内存 t; proc.mem[,oracle,max,oracleZABBIX] → oracle用户下，包含有oracleZABBIX命令行运行的所有内存最多的内存进程使用共享内存时，进程使用的内存总和可能导致大到不切实际的值。参考说明关于选择进程`name` 和 `cmdline` 参数(指定为Linux)。 `memtype` 参数从Zabbix 3.0.0开始在多个平台支持。
proc.num[<name>,<user>,<state>,<cmdline>]
	进程数量。整型	name	* - 进程名称 (默认是 all processes) 示例: user - 用户名 (默认是 all users) =>state - 可选的值: =&g所有状态 (默认), =>disk - 不间断休眠, run - 运行中, 参考sleep - 间断休眠, trace - 停止的, 在Wzomb - 僵尸 cmdline - 按命令行过滤（它是一个正则表达式）自Zabbix 3.4.0起支持	<proc.num[,mysql] → 在mysql用户下运行的进程数 ; proc.num[apache2,www-data] → 在www-data用户下运行的apache2进程数 proc.num[,oracle,sleep,oracleZABBIX] → 在oracleZABBIX命令行下的oracle用户运行的睡眠状态进程数。说明关于选择进程 `name` 和 `cmdline` 参数(适用于Linux). ndows上，只支持`name`和`user`参数。 `state` 参数的磁盘和跟踪值。
sensor[device,sensor,<mode>]
	硬件传感器读数。浮点型	device	- 设备名称在Linux 2.4上读取sensor - 传感器名 mode - 可能的值: 示例:avg, max, min (如果省略此参数，则会对设备和传感器进行逐字处理). => sensor[w83781d-	proc/sys/dev/sensors 2c-0-2d,temp1] 在Zabbix 1.8.4之前，使用传感器[temp1]格式。
				在Linux 2.6以后的版本上读取 /sys/class/hwmon 请参阅Linux上sensor项目的更详细说明。
				在OpenBSD上读取hw.sensors MIB文件示例: => sensor[cpu0,temp0] → CPU的温度 => sensor[“cpu[0-2]$”,temp,avg] → 前三个CPU温度的平均值从Zabbix 1.8.4开始支持OpenBSD。
system.boottime
	系统启动时间整数 (U	ix时间戳)
system.cpu.discovery
	检测到的CPU/CPU内核列表。用于低级发现。 JSON对象		所有平台从2.4.0开始支持
system.cpu.intr
	设备中断数整数
system.cpu.load[<cpu>,<mode>]
	<a href=”http://en.wikipedia.org/wiki/Load(computing)”>CPU负载. 浮	数 cp	- 可能的值: 示例: all (default), percpu (总负载除以在线CPU数) => smode - 可能的值: avg1 (一分钟平均值, 默认值), avg5, avg15 percpu	<stem.cpu.load[,avg5] 从Zabbix 2.0.0开始支持旧名称: system.cpu.loadX
system.cpu.num[<type>]
	CPU的数量整数	ty	e - 可能的值: 示例: online (默认), max =	<gt; system.cpu.num
system.cpu.switches
	上下文交换的数量。整数		旧名称: syst	m[switches]
system.cpu.util[<cpu>,<type>,<mode>]
	CPU利用率。浮点型	cpu*	- <CPU数量> 或者 all (默认值) 示例: type - 可能的值: =&gidle, nice, user (默认值), system (Windows系统默认值), iowait, interrupt, softirq, steal, guest (在Linux kernels 2.6.24 以及以上支持), guest_nice (在Linux kernels 2.6.33 以及以上支持) mode - 可能的值: 旧名称avg1 (1分钟平均值, 默认值), avg5, avg15	<; system.cpu.util[0,user,avg5] system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX
system.hostname[<type>]
	系统主机名。字符串型	type	仅Windows不得在其它系统上使用) - 可能的值: netbios (默认) 或者 host 该值由Windows上的GetComputerName（	（对于 netbios）或gethostname（）（用于 host）函数以及其它系统上的“hostname”命令获取。返回值示例: Linux系统: => system.hostname → linux-w7x1 => system.hostname → www.zabbix.com Windows系统: => system.hostname → WIN-SERV2008-I6 => system.hostname[host] → Win-Serv2008-I6LonG 参数`type` Zabbix 1.8.6开始支持。请参考更详细的描述.
system.hw.chassis[<info>]
	机架信息。字符串	info	- 完整的 (默认)、型号、序列、类型或供应商之一示例: system.hw.chassis[full	] Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop] 此key取决于SMBIOS表的可用性。将尝试从sysfs读取DMI表，如果sysfs访问失败，尝试直接从内存中读取。需要Root权限，因为通过从sysfs或内存读取获取该值。 Zabbix agent从2.0开始支持。
system.hw.cpu[<cpu>,<info>]
	CPU信息字	串或者整型 cpu	<CPU数量> 或者全部 (默认) 示例: info - 可能的值： =&gtfull (默认), curfreq, maxfreq, model 或者vendor	<system.hw.cpu[0,vendor] → AuthenticAMD 从 /proc/cpuinfo 和 /sys/devices/system/cpu/[cpunum]/cpufreq/cpuinfo_max_freq 获取信息。如果指定了CPU编号和curfreq或maxfreq，则返回数值（Hz）。 Zabbix agent从版本2.0开始支持
system.hw.devices[<type>]
	列出PCI或者USB设备文本型	type	- pci (默认) 或者 usb 示例:	<=> system.hw.devices[pci] → 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge [..] 返回lspci或lsusb实用程序的输出（没有任何参数） Zabbix agent 从版本2.0开始支持
system.hw.macaddr[<interface>,<format>]
	列出MAC地址字符串	inter	ace - all (默认) 或者为一个正则表达式列出与给定 `interface` 正format - full (默认) 或者 short	表达式名称匹配的网卡的MAC地址（所有网卡的所有列表）。示例: => system.hw.macaddr[“eth0$”,full] → [eth0] 00:11:22:33:44:55 如果 `format` 被指定为short，则不会列出接口名称和相同的MAC地址。 \Zabbix agent从版本2.0开始支持。
system.localtime[<type>]
	系统时间整数	`type` 为 utc *type 字符串 - `type` 为 local*	- 可能的值: 此监控项参数从Zabutc - (默认值) 从纪元以来的时间（1970年1月1日00:00:00 UTC），以秒为单位。\ local - ‘yyyy-mm-dd，hh：mm：ss.nnn，+ hh：mm’格式的时间示例:	ix agent 版本2.0开始支持。 => system.localtime[local] → 使用该key创建一个监控项，然后使用它在时钟screen element中显示主机时间。
system.run[command,<mode>]
	在主机上运行指定的命令。命令执行的文本结果	command - 要执行的命令 1 - `mode` 为nowait（不管命令结果如何） wait - 等	最多可以返回512KB的数据，包括截断的尾随空格。 mode - 可能的值: 要被正执行结束（默认）， nowait - 不等待示例	<的处理，命令的输出必须是文本。 => system.run[ls -l /] → 根目录的详细文件列表。注意: 要启用此功能，Zabbix agent配置文件必须包含EnableRemoteCommands=1 选项。监控项的返回值是标准输出以及由命令产生的标准错误输出。如果没有使用nowait标志，则会检查执行结果。从Zabbix 2.4.0开始，空结果是允许的。同时参考: 执行指令.
system.stat[resource,<type>]
	系统信息。整型或者	点型 ent - 该	区有权接收的处理器单元数（float） kthr,<type> - 关于内核线程状态的信息: r - 平均可运行内核线程数（float） b - 虚拟内存管理器等待队列中的平均内核线程数（float） memory,<type> - 有关虚拟和真实内存使用情况的信息： avm - 活动虚拟页面（整数） fre - 自由列表的大小（整数） page,<type> - 关于页面错误和分页活动的信息： fi - 每秒文件页面输入（float） fo - 每秒文件页面输出（float） pi - 从调页空间（float）分页的页面 po - 页面分页到调页空间（float） fr - 页面被释放（页面替换）（浮点） sr - 通过页面替换算法扫描的页面 (float) faults,<type> - trap和中断率: in - 设备中断 (float) sy - 系统调用 (float) cs - 内核线程上下文切换 (float) cpu,<type> - 处理器时间使用百分比的细分: us - 用户时间 (float) sy - 系统时间 (float) id - 空闲时间 (float) wa - 系统具有未完成的磁盘/NFS I/O请求（float）的空闲请求时间(float) pc - 消耗的物理处理器数量(float) ec - 被授权的容量消耗的百分比(float) lbusy - 表示在用户和系统级执行时发生的逻辑处理器利用率的百分比(float) app - 表示共享池中的可用物理处理器(float) disk,<type> - 磁盘信息: bps - 表示以每秒字节为单位传输（读取或写入）驱动器的数据量 (integer) tps - 表示发送到物理磁盘/磁带的每秒传输次数(float) 此监控项从Zabbix 1.8.1. 开始支持
system.sw.arch
	软件架构信息。字符串型		示例:	<=> system.sw.arch → i686 信息从uname（）函数中获取。 Zabbix agent 从版本2.0开始支持
system.sw.os[<info>]
	操作系统信息字符串	info	- 可能的值: 示例: full (默认), short 或者 name =&g	<; system.sw.os[short]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11 信息获取（注意，并非所有发行版中都存在所有文件和选项）： /proc/version (full) /proc/version_signature (short) /etc/os-release中支持它的系统上的PRETTY_NAME参数，或/etc/issue.net（name） Zabbix agent从版本2.0开始支持。
system.sw.packages[<package>,<manager>,<format>]
	列出已安装的软件包。文本	package	- all (默认) 或者为正则表达式列表（按字母顺序）安装的包名称与给定的包rmanager - all (默认) 或者为包管理器 format - full (默认) 或者 short 示例:	gexp匹配的包（全部列出它们全部）。 => system.sw.packages[mini,dpkg,short] → python-minimal, python2.6-minimal, ubuntu-minimal 支持包管理器(执行命令): dpkg (dpkg —get-selections) pkgtool (ls /var/log/packages) rpm (rpm -qa) pacman (pacman -Q) 如果`format`被指定为full，则软件包由包管理器分组（每个管理器在单独的行上以其方括号开头）。如果`format` 被指定为short, 包管理器不分组，并列在一行里。 Zabbix agent从版本2.0开始支持
system.swap.in[<device>,<type>]
	交换（从设备到内存）统计。整型	device - 用	交换的设备 (默认是all) 示例: type - 可能的值: =&gcount (swapins的数量), sectors (换入的区域), pages (换入的页). 有关默认的详细信息请参考支持的平台	<; system.swap.in[,pages] 这个信息的来源是: /proc/swaps, /proc/partitions, /proc/stat (Linux 2.4) /proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)
system.swap.out[<device>,<type>]
	交换（从内存到设备）统计。整型	device - 用	交换的设备 (默认是all) 示例: type - 可能的值: =&gcount (swapouts的数量), sectors (换出的区域), pages (换出的页). 有关默认的详细信息请参考支持的平台	<; system.swap.out[,pages] 信息来源是: /proc/swaps, /proc/partitions, /proc/stat (Linux 2.4) /proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)
system.swap.size[<device>,<type>]
	交换空间大小（以字节为单位）或百分比（total）。 Integer - 字节	device - 用于交换的设备 ( Float - 百分比 f	认是 all) 示例: type - 可能的值: =&gee (可用的交换空间, 默认值), pfree (空闲交换空间，百分比), pused (使用交换空间，百分比), total (总交换空间), used (使用交换空间)	<; system.swap.size[,pfree] → 空闲swap空间百分比如果没有指定设备，Zabbix代理只会考虑交换设备（文件），物理内存将被忽略。例如，在Solaris系统上，swap -s命令包含一部分物理内存和交换设备（与swap -l不同）。请注意，此key可能会报告虚拟化（VMware ESXi，VirtualBox）Windows平台上的百分比不正确。在这种情况下，使用perf_counter [\700（_Total）\702]键来获取正确的交换使用数据。旧名称: system.swap.free, system.swap.total
system.uname
	系统相关信息字符串		返回值的示例(U	ix): FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov i386 返回值示例(Windows): Windows ZABBIX-WIN 6.0.6001 Microsoft? Windows Server? 2008 Standard Service Pack 1 x86 从Zabbix 2.2.0开始在Unix上，该监控项的值是通过uname（）系统调用获得的。以前它是通过调用“uname -a”获得的。此监控项的值可能与“uname -a”的输出不同，并且不包含基于其它来源输出的“uname -a”的信息。从Zabbix 3.0开始的Windows系统上，该监控项的值是从Win32_OperatingSystem和Win32_Processor WMI类获取信息。以前它是从不稳定的Windows API和未记录的注册表项获得的。操作系统名称（包括版本）可能会被翻译成用户的显示语言。在某些版本的Windows上，它包含商标符号和额外的空格。请注意，在Windows上，该项目返回操作系统架构，而在Unix上则返回CPU架构。
system.uptime
	系统正常运行时间（以秒为单位）整数		在监控项配置中, 使用 s 或者 uptime 单位来获取可读取的值。
system.users.num
	已登录用户数整数		who	命令用于代理端获取该值。
vfs.dev.read[<device>,<type>,<mode>]
	磁盘读取统计信息。整数 - `ty\|e` 为 sectors, operations, bytes device Float - `type` 为 sps, ops, bps	磁盘设备 (默认为 all) 不同操作系统的“类型”参数的默认值：type - 可能的值: sectors, operations, bytes, sps, ops, bps AIX须指定此参数，因为各种操作系统的默认值不同。 FreeBSD - bps sps, ops, bps 表示: sectors, operations, bytes per second, respectively. Lmode - 可能的值: avg1 (1分钟平均值, 默认), avg5, avg15. OpenBSD -此参数仅支持的`类型`为: sps, ops, bps. Solaris -	<- operations nux - sps perations bytes 示例: => vfs.dev.read[,operations] 在支持的平台上的sps, ops 和 bps 曾被限制为 8 个设备(7个独立的和1个 all). 从Zabbix 2.0.1 开始，这个限制提高到1024个设备(1023个独立的和1个all). 如果默认为全部用于第一个参数，那么该key将返回摘要统计信息，包括所有块设备，如sda，sbd及其分区（sda1，sda2，sdb3 …）和基于这些块设备/分区的多个设备（MD raid）和基于这些设备/分区的逻辑卷（LVM）。在这种情况下，返回值只能作为相对值（动态时间）而不是绝对值。 LVM的支持从Zabbix 1.8.6开始。直到Zabbix 1.8.6才能使用相关的设备名称（例如，sda）。从那时起，可选的 /dev/前缀（例如/dev/sda）必须被使用。旧名称: io[]
vfs.dev.write[<device>,<type>,<mode>]
	磁盘写入统计信息。整数 - `ty\|e` 为sectors, operations, bytes device 浮点型 - `type` 为 sps, ops, bps 因为各	磁盘设备 (默认为all) 不同操作系统的“类型”参数的默认值：type - 可能的值: sectors, operations, bytes, sps, ops, bps AIX操作系统的默认值有所不同，所以这个参数必须被指定。 FreeBSD - bps sps, ops, bps 代表: sectors, operations, bytes per second, respectively. Lmode - 可能的值: avg1 (1分钟平均值, 默认), avg5, avg15. OpenBSD -此参数仅支持这些`类型`: sps, ops, bps. Solaris -	<- operations nux - sps perations bytes 示例: => vfs.dev.write[,operations] sps, ops and bps在支持的平台上的sps, ops 和 bps 曾被限制为 8 个设备(7个独立的和1个 all). 从Zabbix 2.0.1 开始，这个限制提高到1024个设备(1023个独立的和1个all)。如果默认为全部用于第一个参数，那么该key将返回摘要统计信息，包括所有块设备，如sda，sbd及其分区（sda1，sda2，sdb3 …）和基于这些块设备/分区的多个设备（MD raid）和基于这些设备/分区的逻辑卷（LVM）。在这种情况下，返回值只能作为相对值（动态时间）而不是绝对值。 LVM的支持从Zabbix 1.8.6开始。直到Zabbix 1.8.6才能使用相关的设备名称（例如，sda）。从那时起，可选的 /dev/前缀（例如/dev/sda）必须被使用。旧名字: io[]
vfs.dir.count[dir,<regex_incl>,<regex_excl>,<types_incl>,<types_excl>,<max_depth>,<min_size>,<max_size>,<min_age>,<max_age>]
	目录条目计数. 整数	dir	- 目录的绝对路径例如%APP_HOME%,regex_incl - 正则表达式，描述包含的文件，目录和符号链接名称模式（包括所有文件，目录和符号链接，如果为空;空字符串是默认值） regex_excl - 正则表达式描述文件，目录和符号链接名称模式以排除（不排除任何如果为空;空字符串是默认值）隐藏目录 “.” and “..” 不会被计算。 types_incl - 要计算的一组目录条目类型，可能的值： file - 常规文件, dir - 子目录, sym - 符号链接, sock - 套接字, bdev - 块设备, cdev - 字符设备, fifo- FIFO, dev- “bdev,cdev”的同义词, all- 所有上述类型，即 “file,dir,sym,sock,bdev,cdev,fifo”. 如果参数为空，all为默认值。必须用逗号分隔多个类型，并用引号“”括起整个集合。目录遍历不遵循符号链接。 types_excl - 要计数的一组目录条目类型，与<types_incl>相同的值和语法。如果某些条目类型同时位于<types_incl>和<types_excl>中，则不计算此类型的目录条目。 max_depth - 遍历的子目录的最大深度。 -1 (默认) - 无限制, 0 - 不涉及子目录在Windows目录中，将跳过符号链接，并且min_size - 要计算的文件最小大小。小于此的文件将不计算在内。该值以字节为单位。内存后缀可以被使用。 max_size - 要计算的文件的最大大小。大于此的文件将不计算在内。该值以字节为单位。内存后缀可以被使用。 `regex_incl` 和 `regex_excl` 是 [Perl兼容的正则表达式min_age - 要计算的目录条目的最小创建时间。最新编辑的条目不会被计算在内。整数值以秒为单位。时间后缀可以被使用。 max_age - 要计算的目录条目的最大创建时间。很久之前编辑的条目将不计算在内（修改时间）。整数值以秒为单位。时间后缀可以被使用。执行时间将受到默认超时值3秒的限制（代理配置文件中的“超时”参数）。由于大型目录遍历可能需要更长时间，因此不会	$HOME 和 %TEMP% 子类的环境变量是不支持的。对硬链接计数一次。 (https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE). `regex_incl`和`regex_excl`在计算条目大小时都应用于文件和目录，但在选择遍历的子目录时会被忽略（如果regex_incl是“(?i)^.+.zip$”并且未设置max_depth，则将遍历所有子目录，但只会计算zip类型的文件）。如果文件名与`regex_incl`和`regex_excl`匹配，则不会计算此文件。回任何数据，并且该项目将标记为“不支持”。部分计数不会被退回。按大小过滤时，只有常规文件具有有意义的大小。在Linux和BSD下，目录也具有非零大小（通常为几Kb）。设备的大小为零，例如 /dev/sda1 的大小不反映相应的分区大小。因此，当使用`<min_size>`和`<max_size>`参数时，建议将`<types_incl>`指定为 /dev/sda1 ，以避免意外。例子： ? vfs.dir.count[/dev] - 监视/dev中的设备数量（Linux） ? vfs.dir.count[“C:\Users\ADMINI~1\AppData\Local\Temp”] - 监视临时目录中的文件数（Windows） Zabbix 4.0.0.后支持该功能
vfs.dir.size[dir,<regex_incl>,<regex_excl>,<mode>,<max_depth>]
	目录大小（以字节为单位）。整数	dir - 目录的绝	路径仅计算具有zabbix用户读取权限的目录。regex_incl - 正则表达式描述包含的文件名模式（如果为空则包括所有文件;空字符串是默认值） regex_excl - 正则表达式描述用于排除的文件名模式（如果为空不排除任何文件;空字符串是默认值）在Windows上，将跳过任何符号链接，并且仅将硬链接考虑在内。 mode - 可能的值: \ apparent (默认) - 获得明确的文件大小，而不是磁盘利用率(作为 `du -sb dir`), disk - 获取磁盘使用情况 (作为 `du -s -B1 dir`). 和du命令不同，vfs.dir.size 监控项在计算目录大小时会将隐藏的文件记录帐户 (作为 `du -sb .[^.]` 在 dir内). max_depth - 要遍历的子目录的最大深度。 -1 (默认) - 无限, 0 - 不会遍历到子目录。示例:	<对于大型目录或慢速驱动器，由于客户端和服务端/代理配置文件中的超时设置，此项可能会超时。根据需要增加超时值。 ? vfs.dir.size[/tmp,log] - 计算/tmp中包含“log”的所有文件的大小 ? vfs.dir.size[/tmp,log,^.+.old$] - 计算/tmp中包含“log”的所有文件的大小，不包括包含’.old’的文件文件大小限制取决于大文件支持。
vfs.file.cksum[file]
	文件checksum校验，由UNIX cksum算法计算实现。整型	file - 文件全	径示例:	<=> vfs.file.cksum[/etc/passwd] 返回值示例: 1938292000 旧名字: cksum 文件大小限制取决于大文件支持。
vfs.file.contents[file,<encoding>]
	检索文件的内容。文本	file	文件全路径如果文件为空或仅包含LF/Cencoding - 编码页标识符	字符，则返回空字符串。 Example: => vfs.file.contents[/etc/passwd] 此选项对文件限制是不超过64KB的文件。 Zabbix agent从版本2.0开始支持。
vfs.file.exists[file]
	检测文件是否存在。 0 - 不存在	file - 1 - 常规文件或到常规存在文件的link（符号或硬）	件的全路径示例:	<=> vfs.file.exists[/tmp/application.pid] 返回值取决于S_ISREG POSIX宏返回的值。文件大小限制取决于大文件支持。
vfs.file.md5sum[file]
	文件的MD5 checksum。字符串	文件的MD5哈希) file -	件的全路径示例:	<=> vfs.file.md5sum[/usr/local/etc/zabbix_agentd.conf] 返回值示例: b5052decb577e0fffd622d6ddc017e82 此项目的文件大小限制（64 MB）在1.8.6版中已删除。文件大小限制取决于大文件支持。
vfs.file.regexp[file,regexp,<encoding>,<start line>,<end line>,<output>]
	查找文件中的字符串。包含匹配字符串的行	或由可选输出参数指定的行。 file - 文件完整路径	只返回第一个匹配行。\如果没有行与表达式匹配，则返回空字符串。 regexp - Perl Compatible Regular Expression （PCRE）或POSIX在Zabbix 3.4之前扩展了正则表达式 encoding - 编码页标识符使用 `ostart line - 要查询的第一行的数量（默认为文件的第1行）。\ end line - 要查询的最后一行的数量（默认为文件的最后一行）。\`start line`,`end lineoutput - 一个可选的输出格式模板。 \0转义序列替换为匹配的文本，而\N（其中N = 1 … 9）转义序列被替换为第N个匹配组（如果N超过捕获组的数量，则为空字符串）。	<tput`参数的提取过程发生在代理端。和`output`参数从版本2.2开始支持。示例: => vfs.file.regexp[/etc/passwd,zabbix] => vfs.file.regexp[/path/to/some/file,”([0-9]+)$”,,3,5,\1] => vfs.file.regexp[/etc/passwd,\^zabbix:.:([0-9]+),,,,\1] → 获取用户Zabbix的ID\| \|vfs.file.regmatch[file,regexp,<encoding>,<start line>,<end line>]\|<\|<\|<\|<\| \|<\|查询文件中的字符串。 0 - 不匹配 \|file - 文 1 - 匹配 \|全路径\`start line`,`enregexp - Perl Compatible Regular Expression （PCRE）或POSIX在Zabbix 3.4之前扩展了正则表达式 encoding* - 编码页标识符示例: start line - 满足查询到的第一行的数量（默认为文件的第1行）。 => vfs.file.regmatcend line - 要查询的最后一行的数量（默认为文件的最后一行）。

一个特定于Linux的注意事项。 Zabbix Agent必须具有权限读取文件系统 proc。来自www.grsecurity.org的内核补丁限制非特权用户的访问权限。

Key
	Description	Return value	Parameters	Comments
agent.hostname
	Agent host name.	String		Returns: As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file; As active check - the name of the current hostname.
agent.ping
	Agent availability check.	Nothing - unavailable 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: 1 - Zabbix agent 2 - Zabbix agent 2 Supported since Zabbix 5.4.8.
agent.version
	Version of Zabbix agent.	String		Example of returned value: 1.8.2
kernel.maxfiles
	Maximum number of opened files supported by OS.	Integer
kernel.maxproc
	Maximum number of processes supported by OS.	Integer
log[file,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>,<persistentdir>]
	Log file monitoring.	Log	file - full path and name of log file regexp - regular expression describing the required pattern encoding - code page identifier 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 mode (since version 2.0)- possible values: all (default), skip - skip processing of older data (affects only newly created items). 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). 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 notes before using it! options (since version 4.4.7) - additional options: 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. 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.	The item must be configured as an active check. If file is missing or permissions do not allow access, item turns unsupported. 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. Content extraction using the `output` parameter takes place on the agent. Examples: => log[/var/log/syslog] => log[/var/log/syslog,error] => log[/home/zabbix/logs/logfile,,,100] Using `output` parameter for extracting a number from log record: => 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. Using `output` parameter for rewriting log record before sending to server: => 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. See also additional information on log monitoring.
log.count[file,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>,<options>,<persistent_dir>]
	Count of matched lines in log file monitoring.	Integer	file - full path and name of log file regexp - regular expression describing the required pattern encoding - code page identifier maxproclines - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10’MaxLinesPerSecond’ in zabbix_agentd.conf. mode* - possible values: all (default), skip - skip processing of older data (affects only newly created items). 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 notes before using it! options (since version 4.4.7) - additional options: 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.) 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.	The item must be configured as an active check. If file is missing or permissions do not allow access, item turns unsupported. See also additional information on log monitoring. This item is not supported for Windows Event Log. Supported since Zabbix 3.2.0.
logrt[file_regexp,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>,<persistent_dir>]
	Log file monitoring with log rotation support.	Log	file_regexp - absolute path to file and the file name described by a regular expression. Note that only the file name is a regular expression regexp - regular expression describing the required content pattern encoding - code page identifier 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 mode (since version 2.0) - possible values: all (default), skip - skip processing of older data (affects only newly created items). 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). 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 notes before using it! options (since version 4.0; mtime-reread, mtime-noreread options since 4.4.7) - type of log file rotation and other options. Possible values: rotate (default), copytruncate - note that copytruncate cannot be used together with maxdelay. In this case maxdelay must be 0 or not specified; see copytruncate notes, mtime-reread - non-unique records, reread if modification time or size changes (default), mtime-noreread - non-unique records, reread only if the size changes (ignore modification time change). 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.	The item must be configured as an active check. Log rotation is based on the last modification time of files. 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. 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. Content extraction using the `output` parameter takes place on the agent. Examples: => logrt[“/home/zabbix/logs/^logfile[0-9]{1,3}$”,,,100] → will match a file like “logfile1” (will not match “.logfile1”) => 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”. Using `output` parameter for extracting a number from log record: => 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. Using `output` parameter for rewriting log record before sending to server: => 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. See also additional information on log monitoring.
logrt.count[file_regexp,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>,<options>,<persistent_dir>]
	Count of matched lines in log file monitoring with log rotation support.	Integer	file_regexp - absolute path to file and regular expression describing the file name pattern regexp - regular expression describing the required content pattern encoding - code page identifier maxproclines - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10‘MaxLinesPerSecond’ in zabbixagentd.conf. mode - possible values: all (default), skip - skip processing of older data (affects only newly created items). 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 notes before using it! options (since version 4.0; mtime-reread, mtime-noreread options since 4.4.7) - type of log file rotation and other options. Possible values: rotate (default), copytruncate - note that copytruncate cannot be used together with maxdelay. In this case maxdelay must be 0 or not specified; see copytruncate notes, mtime-reread - non-unique records, reread if modification time or size changes (default), mtime-noreread - non-unique records, reread only if the size changes (ignore modification time change). 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.	The item must be configured as an active check. Log rotation is based on the last modification time of files. See also additional information on log monitoring. This item is not supported for Windows Event Log. 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` slave id - slave ID function - Modbus function address - address of first registry, coil or input count - number of records to read type - type of data endianness - endianness configuration offset - number of registers, starting from ‘address’, the results of which will be discarded. See a detailed description 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) 1 - DNS is up	ip - IP address of DNS server (leave empty for the default DNS server, ignored on Windows) name - DNS name to query type - record type to be queried (default is SOA) timeout (ignored on Windows) - timeout for the request in seconds (default is 1 second) count (ignored on Windows) - number of tries for the request (default is 2) protocol (since version 3.0) - the protocol used to perform DNS queries: udp (default) or tcp	Example: => net.dns[8.8.8.8,example.com,MX,2,1] The possible values for `type` are: ANY, A, NS, CNAME, MB, MG, MR, PTR, MD, MF, MX, SOA, NULL, WKS (except for Windows), HINFO, MINFO, TXT, SRV Internationalized domain names are not supported, please use IDNA encoded names instead. SRV record type is supported since Zabbix agent versions 1.8.6 (Unix) and 2.0.0 (Windows). 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) name - DNS name to query type - record type to be queried (default is SOA) timeout (ignored on Windows) - timeout for the request in seconds (default is 1 second) count (ignored on Windows) - number of tries for the request (default is 2) protocol(since version 3.0) - the protocol used to perform DNS queries: udp (default) or tcp	Example: => net.dns.record[8.8.8.8,example.com,MX,2,1] The possible values for `type` are: ANY, A, NS, CNAME, MB, MG, MR, PTR, MD, MF, MX, SOA, NULL, WKS (except for Windows), HINFO, MINFO, TXT, SRV Internationalized domain names are not supported, please use IDNA encoded names instead. SRV record type is supported since Zabbix agent versions 1.8.6 (Unix) and 2.0.0 (Windows). 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 agent version 2.0. On FreeBSD, OpenBSD and NetBSD supported since Zabbix agent version 2.2. 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) mode - possible values: bytes - number of bytes (default) packets - number of packets errors - number of errors dropped - number of dropped packets overruns (fifo) - the number of FIFO buffer errors frame - the number of packet framing errors compressed - the number of compressed packets transmitted or received by the device driver 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. Multi-byte interface names on Windows are supported. The network interface GUID as the first parameter on Windows is supported since Zabbix 5.4.5. Examples: => net.if.in[eth0,errors] => net.if.in[eth0] You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items. 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) mode - possible values: bytes - number of bytes (default) packets - number of packets errors - number of errors dropped - number of dropped packets overruns (fifo) - the number of FIFO buffer errors collisions (colls) - the number of collisions detected on the interface carrier - the number of carrier losses detected by the device driver 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. Multi-byte interface names on Windows are supported. The network interface GUID as the first parameter on Windows is supported since Zabbix 5.4.5. Examples: => net.if.out[eth0,errors] => net.if.out[eth0] You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items. 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) mode - possible values: bytes - number of bytes (default) packets - number of packets errors - number of errors dropped - number of dropped packets overruns (fifo) - the number of FIFO buffer errors 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. The network interface GUID as the first parameter on Windows is supported since Zabbix 5.4.5. Examples: => net.if.total[eth0,errors] => net.if.total[eth0] You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items. You may use this key with the Change per second preprocessing step in order to get bytes per second statistics. 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 1 - it is in LISTEN state	port - TCP port number	Example: => net.tcp.listen[80] On Linux supported since Zabbix agent version 1.8.4 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 1 - can connect	ip - IP or DNS name (default is 127.0.0.1) port - port number	Example: => net.tcp.port[,80] → can be used to test availability of web server running on port 80. For simple TCP performance testing use net.tcp.service.perf[tcp,<ip>,<port>] 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 1 - service is running	service - either of: ssh, ldap, smtp, ftp, http, pop, nntp, imap, tcp, https, telnet (see details) ip - IP address (default is 127.0.0.1) port - port number (by default standard service port number is used)	Example: => net.tcp.service[ftp,,45] → can be used to test the availability of FTP server on TCP port 45. Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually). 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. Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2. Note that the telnet check looks for a login prompt (‘:’ at the end). See also known issues of checking HTTPS service. 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 seconds - the number of seconds spent while connecting to the service	service - either of: ssh, ldap, smtp, ftp, http, pop, nntp, imap, tcp, https, telnet (see details) ip - IP address (default is 127.0.0.1) port - port number (by default standard service port number is used)	Example: => net.tcp.service.perf[ssh] → can be used to test the speed of initial response from SSH server. 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. Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2. Note that the telnet check looks for a login prompt (‘:’ at the end). See also known issues of checking HTTPS service. https and telnet services are supported since Zabbix 2.0.
net.udp.listen[port]
	Checks if this UDP port is in LISTEN state.	0 - it is not in LISTEN state 1 - it is in LISTEN state	port - UDP port number	Example: => net.udp.listen[68] On Linux supported since Zabbix agent version 1.8.4
net.udp.service[service,<ip>,<port>]
	Checks if service is running and responding to UDP requests.	0 - service is down 1 - service is running	service - ntp (see details) ip - IP address (default is 127.0.0.1) port - port number (by default standard service port number is used)	Example: => net.udp.service[ntp,,45] → can be used to test the availability of NTP service on UDP port 45. 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 seconds - the number of seconds spent waiting for response from the service	service - ntp (see details) ip - IP address (default is 127.0.0.1) port - port number (by default standard service port number is used)	Example: => net.udp.service.perf[ntp] → can be used to test response time from NTP service. This item is supported since Zabbix 3.0.0, but ntp service was available for net.tcp.service[] item in prior versions.
proc.cpu.util[<name>,<user>,<type>,<cmdline>,<mode>,<zone>]
	Process CPU utilization percentage.	Float	name - process name (default is all processes) user - user name (default is all users) type - CPU utilization type: total (default), user, system cmdline - filter by command line (it is a regular expression) mode - data gathering mode: avg1 (default), avg5, avg15 zone - target zone: current (default), all. This parameter is supported on Solaris only.	Examples: => proc.cpu.util[,root] → CPU utilization of all processes running under the “root” user => proc.cpu.util[zabbix_server,zabbix] → CPU utilization of all zabbix_server processes running under the zabbix user The returned value is based on single CPU core utilization percentage. For example CPU utilization of a process fully using two cores is 200%. 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. 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. This key is supported since Zabbix 3.0.0 and is available on several platforms (see Items supported by platform).
proc.mem[<name>,<user>,<mode>,<cmdline>,<memtype>]
	Memory used by process in bytes.	Integer - with `mode` as max, min, sum Float - with `mode` as avg	name - process name (default is all processes) user - user name (default is all users) mode - possible values: avg, max, min, sum (default) cmdline - filter by command line (it is a regular expression) memtype - type of memory used by process	Examples: => proc.mem[,root] → memory used by all processes running under the “root” user => proc.mem[zabbix_server,zabbix] → memory used by all zabbix_server processes running under the zabbix user => proc.mem[,oracle,max,oracleZABBIX] → memory used by the most memory-hungry process running under oracle having oracleZABBIX in its command line Note: When several processes use shared memory, the sum of memory used by processes may result in large, unrealistic values. See notes on selecting processes with `name` and `cmdline` parameters (Linux-specific). 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. The `memtype` parameter is supported on several platforms since Zabbix 3.0.0.
proc.num[<name>,<user>,<state>,<cmdline>,<zone>]
	The number of processes.	Integer	name - process name (default is all processes) user - user name (default is all users) state (disk and trace options since version 3.4.0) - possible values: all (default), disk - uninterruptible sleep, run - running, sleep - interruptible sleep, trace - stopped, zomb - zombie cmdline - filter by command line (it is a regular expression) zone - target zone: current (default), all. This parameter is supported on Solaris only.	Examples: => proc.num[,mysql] → number of processes running under the mysql user => proc.num[apache2,www-data] → number of apache2 processes running under the www-data user => proc.num[,oracle,sleep,oracleZABBIX] → number of processes in sleep state running under oracle having oracleZABBIX in its command line See notes on selecting processes with `name` and `cmdline` parameters (Linux-specific). On Windows, only the `name` and `user` parameters are supported. 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. 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 sensor - sensor name mode - possible values: avg, max, min (if this parameter is omitted, device and sensor are treated verbatim).	Reads /proc/sys/dev/sensors on Linux 2.4. Example: => sensor[w83781d-i2c-0-2d,temp1] Prior to Zabbix 1.8.4, the sensor[temp1] format was used.
				Reads /sys/class/hwmon on Linux 2.6+. See a more detailed description of sensor item on Linux.
				Reads the hw.sensors MIB on OpenBSD. Examples: => sensor[cpu0,temp0] → temperature of one CPU => sensor[“cpu[0-2]$”,temp,avg] → average temperature of the first three CPU’s 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>]
	<a href=”http://en.wikipedia.org/wiki/Load(computing)”>CPU load.	Float	cpu - possible values: all (default), percpu (since version 2.0; total load divided by online CPU count) mode - possible values: avg1 (one-minute average, default), avg5, avg15	Example: => system.cpu.load[,avg5].
system.cpu.num[<type>]
	Number of CPUs.	Integer	type - possible values: online (default), max	Example: => system.cpu.num
system.cpu.switches
	Count of context switches.	Integer
system.cpu.util[<cpu>,<type>,<mode>,<logicalorphysical>]
	CPU utilization percentage.	Float	cpu - <CPU number> or all (default) type - possible values: user (default), idle, nice, system (default for Windows), iowait, interrupt, softirq, steal, guest (on Linux kernels 2.6.24 and above), guestnice (on Linux kernels 2.6.33 and above). See also platform-specific details for this parameter. mode - possible values: avg1 (one-minute average, default), avg5, avg15 logicalorphysical (since version 5.0.3; on AIX only) - possible values: logical* (default), physical. This parameter is supported on AIX only.*	Example: => system.cpu.util[0,user,avg5] 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). transform (since version 5.4.7) - possible values: 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. Examples of returned values: on Linux: => system.hostname → linux-w7x1 => system.hostname → example.com => system.hostname[shorthost] → example on Windows: => system.hostname → WIN-SERV2008-I6 => system.hostname[host] → Win-Serv2008-I6LonG => system.hostname[host,lower] → win-serv2008-i6long See also a more detailed description.
system.hw.chassis[<info>]
	Chassis information.	String	info - one of full (default), model, serial, type or vendor	Example: system.hw.chassis[full] Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop] This key depends on the availability of the SMBIOS table. Will try to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory. Root permissions are required because the value is acquired by reading from sysfs or memory. Supported since Zabbix agent version 2.0.
system.hw.cpu[<cpu>,<info>]
	CPU information.	String or integer	cpu - <CPU number> or all (default) info - possible values: full (default), curfreq, maxfreq, model or vendor	Example: => system.hw.cpu[0,vendor] → AuthenticAMD Gathers info from /proc/cpuinfo and /sys/devices/system/cpu/[cpunum]/cpufreq/cpuinfomax_freq. If a CPU number and curfreq or maxfreq is specified, a numeric value is returned (Hz). Supported since Zabbix agent version 2.0.
system.hw.devices[<type>]
	Listing of PCI or USB devices.	Text	type (since version 2.0) - pci (default) or usb	Example: => system.hw.devices[pci] → 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge [..] 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 format - full (default) or short	Lists MAC addresses of the interfaces whose name matches the given `interface` regular expression (all lists for all interfaces). Example: => system.hw.macaddr[“eth0$”,full] → [eth0] 00:11:22:33:44:55 If `format` is specified as short, interface names and identical MAC addresses are not listed. Supported since Zabbix agent version 2.0.
system.localtime[<type>]
	System time.	Integer - with `type` as utc String - with `type` as local	type (since version 2.0) - possible values: utc - (default) the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds. local - the time in the ‘yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm’ format	Must be used as a passive check only. Example: => system.localtime[local] → create an item using this key and then use it to display host time in the Clock dashboard widget.
system.run[command,<mode>]
	Run specified command on the host.	Text result of the command 1 - with `mode` as nowait (regardless of command result)	command - command for execution mode - possible values: wait - wait end of execution (default), nowait - do not wait	Up to 512KB of data can be returned, including trailing whitespace that is truncated. To be processed correctly, the output of the command must be text. Example: => system.run[ls -l /] → detailed file list of root directory. Note: system.run items are disabled by default. Learn how to enable them. The return value of the item is standard output together with standard error produced by command. The exit code is not checked. Empty result is allowed starting with Zabbix 2.4.0. See also: Command execution.
system.stat[resource,<type>]
	System statistics.	Integer or float	ent - number of processor units this partition is entitled to receive (float) kthr,<type> - information about kernel thread states: r - average number of runnable kernel threads (float) b - average number of kernel threads placed in the Virtual Memory Manager wait queue (float) memory,<type> - information about the usage of virtual and real memory: avm - active virtual pages (integer) fre - size of the free list (integer) page,<type> - information about page faults and paging activity: fi - file page-ins per second (float) fo - file page-outs per second (float) pi - pages paged in from paging space (float) po - pages paged out to paging space (float) fr - pages freed (page replacement) (float) sr - pages scanned by page-replacement algorithm (float) faults,<type> - trap and interrupt rate: in - device interrupts (float) sy - system calls (float) cs - kernel thread context switches (float) cpu,<type> - breakdown of percentage usage of processor time: us - user time (float) sy - system time (float) id - idle time (float) wa - idle time during which the system had outstanding disk/NFS I/O request(s) (float) pc - number of physical processors consumed (float) ec - the percentage of entitled capacity consumed (float) lbusy - indicates the percentage of logical processor(s) utilization that occurred while executing at the user and system level (float) app - indicates the available physical processors in the shared pool (float) disk,<type> - disk statistics: bps - indicates the amount of data transferred (read or written) to the drive in bytes per second (integer) tps - indicates the number of transfers per second that were issued to the physical disk/tape (float)
			Comments
			This item is supported on AIX only, since Zabbix 1.8.1. Take note of the following limitations in these items: => system.stat[cpu,app] - supported only on AIX LPAR of type “Shared” => system.stat[cpu,ec] - supported on AIX LPAR of type “Shared” and “Dedicated” (“Dedicated” always returns 100 (percent)) => system.stat[cpu,lbusy] - supported only on AIX LPAR of type “Shared” => system.stat[cpu,pc] - supported on AIX LPAR of type “Shared” and “Dedicated” => system.stat[ent] - supported on AIX LPAR of type “Shared” and “Dedicated”
system.sw.arch
	Software architecture information.	String		Example: => system.sw.arch → i686 Info is acquired from uname() function. Supported since Zabbix agent version 2.0.
system.sw.os[<info>]
	Operating system information.	String	info - possible values: full (default), short or name	Example: => system.sw.os[short]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11 Info is acquired from (note that not all files and options are present in all distributions): /proc/version (full) /proc/version_signature (short) PRETTY_NAME parameter from /etc/os-release on systems supporting it, or /etc/issue.net (name) Supported since Zabbix agent version 2.0.
system.sw.packages[<package>,<manager>,<format>]
	Listing of installed packages.	Text	package - all (default) or a regular expression manager - all (default) or a package manager format - full (default) or short	Lists (alphabetically) installed packages whose name matches the given `package` regular expression (all lists them all). Example: => system.sw.packages[mini,dpkg,short] → python-minimal, python2.6-minimal, ubuntu-minimal Supported package managers (executed command): dpkg (dpkg —get-selections) pkgtool (ls /var/log/packages) rpm (rpm -qa) pacman (pacman -Q) 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). If `format` is specified as short, packages are not grouped and are listed on a single line. Supported since Zabbix agent version 2.0.
system.swap.in[<device>,<type>]
	Swap in (from device into memory) statistics.	Integer	device - device used for swapping (default is all) type - possible values: count (number of swapins), sectors (sectors swapped in), pages (pages swapped in). See also platform-specific details for this parameter.	Example: => system.swap.in[,pages] The source of this information is: /proc/swaps, /proc/partitions, /proc/stat (Linux 2.4) /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) type - possible values: count (number of swapouts), sectors (sectors swapped out), pages (pages swapped out). See also platform-specific details for this parameter.	Example: => system.swap.out[,pages] The source of this information is: /proc/swaps, /proc/partitions, /proc/stat (Linux 2.4) /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 Float - for percentage	device - device used for swapping (default is all) type - possible values: 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) Note that pfree, pused are not supported on Windows if swap size is 0. See also platform-specific details for this parameter.	Example: => system.swap.size[,pfree] → free swap space percentage 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). 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): FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov i386 Example of returned value (Windows): Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86 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. 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. 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, 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. Supported since Zabbix 4.4.0.
vfs.dev.read[<device>,<type>,<mode>]
	Disk read statistics.	Integer - with `type` in sectors, operations, bytes Float - with `type` in sps, ops, bps Note: if using an update interval of three hours or more², will always return ‘0’	device - disk device (default is all ³) type - possible values: sectors, operations, bytes, sps, ops, bps Note that ‘type’ parameter support and defaults depend on the platform. See platform-specific details. sps, ops, bps stand for: sectors, operations, bytes per second, respectively. mode - possible values: avg1 (one-minute average, default), avg5, avg15. 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`). LVM logical volumes are supported. Default values of ‘type’ parameter for different OSes: AIX - operations FreeBSD - bps Linux - sps OpenBSD - operations Solaris - bytes Example: => vfs.dev.read[,operations] 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 Float - with `type` in sps, ops, bps Note: if using an update interval of three hours or more², will always return ‘0’	device - disk device (default is all ³) type - possible values: sectors, operations, bytes, sps, ops, bps Note that ‘type’ parameter support and defaults depend on the platform. See platform-specific details. sps, ops, bps stand for: sectors, operations, bytes per second, respectively. mode - possible values: avg1 (one-minute average, default), avg5, avg15. 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`). LVM logical volumes are supported. Default values of ‘type’ parameter for different OSes: AIX - operations FreeBSD - bps Linux - sps OpenBSD - operations Solaris - bytes Example: => vfs.dev.write[,operations] 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 regex_incl - regular expression describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value) regex_excl - regular expression describing the name pattern of the entity (file, directory, symbolic link) to exclude; don’t exclude any if empty (default value) types_incl - directory entry types to count, possible values: 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. 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. max_depth - maximum depth of subdirectories to traverse. -1 (default) - unlimited, 0 - no descending into subdirectories. min_size - minimum size (in bytes) for file to be counted. Smaller files will not be counted. Memory suffixes can be used. max_size - maximum size (in bytes) for file to be counted. Larger files will not be counted. Memory suffixes can be used. min_age - minimum age (in seconds) of directory entry to be counted. More recent entries will not be counted. Time suffixes can be used. 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 can be used. regex_excl_dir - regular expression 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. Pseudo-directories “.” and “..” are never counted. Symbolic links are never followed for directory traversal. On Windows, directory symlinks are skipped and hard links are counted only once. 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). Execution time is limited by the default timeout value in agent configuration (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. 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. Examples: ⇒ vfs.dir.count[/dev] - monitors number of devices in /dev (Linux) ⇒ vfs.dir.count[“C:\Users\ADMINI~1\AppData\Local\Temp”] - monitors number of files in temporary directory (Windows) Supported since Zabbix 4.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 regex_incl - regular expression describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value) regex_excl - regular expression describing the name pattern of the entity (file, directory, symbolic link) to exclude; don’t exclude any if empty (default value) mode - possible values: 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). max_depth - maximum depth of subdirectories to traverse. -1 (default) - unlimited, 0 - no descending into subdirectories. regex_excl_dir - regular expression 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. On Windows any symlink is skipped and hard links are taken into account only once. With large directories or slow drives this item may time out due to the Timeout setting in agent and server/proxy configuration files. Increase the timeout values as necessary. Examples: ⇒ vfs.dir.size[/tmp,log] - calculates size of all files in /tmp which contain ‘log’ ⇒ vfs.dir.size[/tmp,log,^.+.old$] - calculates size of all files in /tmp which contain ‘log’, excluding files containing ‘.old’ The file size limit depends on large file support. Supported since Zabbix 3.4.0.
vfs.file.cksum[file]
	File checksum, calculated by the UNIX cksum algorithm.	Integer	file - full path to file	Example: => vfs.file.cksum[/etc/passwd] Example of returned value: 1938292000 The file size limit depends on large file support.
vfs.file.contents[file,<encoding>]
	Retrieving contents of a file.	Text	file - full path to file encoding - code page identifier	Returns an empty string if the file is empty or contains LF/CR characters only. Byte order mark (BOM) is excluded from the output. Example: => vfs.file.contents[/etc/passwd] This item is limited to files no larger than 64 Kbytes. Supported since Zabbix agent version 2.0.
vfs.file.exists[file,<types_incl>,<types_excl>]
	Checks if file exists.	0 - not found 1 - file of the specified type exists	file - full path to file 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). 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 “”. 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. If the same type is in both <types_incl> and <types_excl>, files of this type are excluded. Examples: => vfs.file.exists[/tmp/application.pid] => vfs.file.exists[/tmp/application.pid,”file,dir,sym”] => vfs.file.exists[/tmp/application_dir,dir] The file size limit depends on large file support. 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.md5sum[file]
	MD5 checksum of file.	Character string (MD5 hash of the file)	file - full path to file	Example: => vfs.file.md5sum[/usr/local/etc/zabbix_agentd.conf] Example of returned value: b5052decb577e0fffd622d6ddc017e82 The file size limit (64 MB) for this item was removed in version 1.8.6. The file size limit depends on large file support.
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 regexp - regular expression describing the required pattern encoding - code page identifier start line - the number of first line to search (first line of file by default). end line - the number of last line to search (last line of file by default). 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. An empty string is returned if no line matched the expression. Byte order mark (BOM) is excluded from the output. Content extraction using the `output` parameter takes place on the agent. The `start line`, `end line` and `output` parameters are supported from version 2.2. Examples: => vfs.file.regexp[/etc/passwd,zabbix] => vfs.file.regexp[/path/to/some/file,”([0-9]+)$”,,3,5,\1] => 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 1 - found	file - full path to file regexp - regular expression describing the required pattern encoding - code page identifier start line - the number of first line to search (first line of file by default). end line - the number of last line to search (last line of file by default).	Byte order mark (BOM) is ignored. The `start line` and `end line` parameters are supported from version 2.2. Example: => vfs.file.regmatch[/var/log/app.log,error]
vfs.file.size[file]
	File size (in bytes).	Integer	file - full path to file	The file must have read permissions for user zabbix. Example: => vfs.file.size[/var/log/syslog] The file size limit depends on large file support.
vfs.file.time[file,<mode>]
	File time information.	Integer (Unix timestamp)	file - full path to the file mode - possible values: modify (default) - last time of modifying file content, access - last time of reading file, change - last time of changing file properties	Example: => vfs.file.time[/etc/passwd,modify] The file size limit depends on large file support.
vfs.fs.discovery
	List of mounted filesystems and their types. Used for low-level discovery.	JSON object		Supported since Zabbix agent version 2.0. {#FSDRIVETYPE} macro is supported on Windows since Zabbix agent version 3.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 agent version 4.4.5.
vfs.fs.inode[fs,<mode>]
	Number or percentage of inodes.	Integer - for number Float - for percentage	fs - filesystem mode - possible values: total (default), free, used, //pfree // (free, percentage), pused (used, percentage)	Example: => vfs.fs.inode[/,pfree]
vfs.fs.size[fs,<mode>]
	Disk space in bytes or in percentage from total.	Integer - for bytes Float - for percentage	fs - filesystem mode - possible values: total (default), free, used, pfree (free, percentage), pused (used, percentage)	In case of a mounted volume, disk space for local file system is returned. Example: => vfs.fs.size[/tmp,free] 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 Float - for percentage	mode - possible values: total (default), active, anon, buffers, cached, exec, file, free, inactive, pinned, shared, slab, wired, used, pused (used, percentage), available, pavailable (available, percentage) See also platform-specific support and additional details for this parameter.	This item accepts three categories of parameters: 1) total - total amount of memory; 2) platform-specific memory types: active, anon, buffers, cached, exec, file, free, inactive, pinned, shared, slab, wired; 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). Allowed URL schemes: http, https⁴. 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:<a href=”https://www.zabbix.com/cdn-cgi/l/email-protection“ class=”__cf_email“ data-cfemail=”dcacbdafafabb3aeb89cabababf2b9a4bdb1acb0b9f2bfb3b1”>[email protected]` is only possible with cURL support ⁴. Punycode is supported in hostnames. path - path to HTML document (default is /) port - port number (default is 80 for HTTP)	This item turns unsupported if the resource specified in `host` does not exist or is unavailable. `host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled. Example: => web.page.get[www.example.com,index.php,80] => web.page.get[https://www.example.com] => web.page.get[https://blog.example.com/?s=zabbix] => web.page.get[localhost:80] => 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). Allowed URL schemes: http, https⁴. 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:<a href=”https://www.zabbix.com/cdn-cgi/l/email-protection“ class=”__cf_email“ data-cfemail=”1666776565617964725661616138736e777b667a733875797b”>[email protected]` is only possible with cURL support ⁴. Punycode is supported in hostnames. path - path to HTML document (default is /) port - port number (default is 80 for HTTP)	This item turns unsupported if the resource specified in `host` does not exist or is unavailable. `host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled. Example: => web.page.perf[www.example.com,index.php,80] => 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). Allowed URL schemes: http, https⁴. 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:<a href=”https://www.zabbix.com/cdn-cgi/l/email-protection“ class=”__cf_email“ data-cfemail=”3a4a5b49494d55485e7a4d4d4d145f425b574a565f14595557”>[email protected]` is only possible with cURL support ⁴. Punycode is supported in hostnames. path - path to HTML document (default is /) port - port number (default is 80 for HTTP) regexp - regular expression describing the required pattern length - maximum number of characters to return 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. `host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled. Content extraction using the `output` parameter takes place on the agent. The `output` parameter is supported from version 2.2. Example: => web.page.regexp[www.example.com,index.php,80,OK,2] => 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) 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/proxy parameter on the target instance. A selected set of internal metrics is returned by this item. For details, see Remote monitoring of Zabbix stats.
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) port - port of server/proxy to be remotely queried (default is 10051) queue - constant (to be used as is) from - delayed by at least (default is 6 seconds) 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/proxy parameter on the target instance.

可用的编码

encoding 参数用于指定处理相应监控项检查的编码，以便获取的数据不会被破坏。有关支持的编码（代码页标识符）的列表，请参阅相应的文档，例如libiconv（GNU Project）或Microsoft Windows SDK文档“代码页标识符”的文档。

如果传递空encoding，则默认使用UTF-8（用于较新的Unix/Linux发行版的默认语言环境，请参阅系统设置）或使用具有系统特定扩展名（Windows）的ANSI。

关于监控项的一些疑难问题

如果与passive agent一起使用，服务器配置中的 超时值 可能需要高于代理配置文件中的 超时值 。否则，该监控项可能无法获取任何值，因为服务器请求代理程序首先超时。

Troubleshooting agent items

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

Mandatory and optional parameters

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

Usage with command-line utilities

Note that when testing or using item keys with zabbix_agentd or zabbix_get from the command line you should consider shell syntax too.

For example, if a certain parameter of the key has to be enclosed in double quotes you have to explicitly escape double quotes, otherwise they will be trimmed by the shell as special characters and will not be passed to the Zabbix utility.

Examples:

$ zabbix_agentd -t 'vfs.dir.count[/var/log,,,"file,dir",,0]'
       $ zabbix_agentd -t vfs.dir.count[/var/log,,,\"file,dir\",,0]