这是原厂英文文档的翻译页面. 欢迎帮助我们 完善文档.
2022 Zabbix中国峰会
2022 Zabbix中国峰会

8 内部检查

概述

内部检查可以监控 Zabbix 的内部进程。换句话说,可以监控 Zabbix server 或者 Zabbix proxy 的运行情况。

被计算的内部检查:

  • 在 Zabbix server 上 - 主机是否被服务端监控
  • 在 Zabbix proxy 上 - 主机是否被代理端监控

内部检查在 server或者proxy上执行,无论主机是否处于维护状态。

要使用这个监控项,请选择 Zabbix internal 监控项类型。

内部检查是由 Zabbix 轮询进程(poller)处理。

性能

使用某些内部监控项可能会对性能产生负面影响。 这些监控项是:

  • · zabbix[host,,items]
  • · zabbix[host,,items_unsupported]
  • · zabbix[hosts]
  • · zabbix[items]
  • · zabbix[items_unsupported]
  • · zabbix[queue]
  • · zabbix[required_performance]
  • · zabbix[stats,,,queue]
  • · zabbix[triggers]

系统信息队列 前端部分也会受到影响。

支持的检查

  • 没有尖括号的参数是常量 - 例如, zabbix[host,<type>,available]中的'host' and 'available'. 在监控项键值中使用它们。
  • 仅当主机被服务器监控时,才能收集“代理服务器不支持”的监控项和监控项参数的值。反之亦然,“服务器不支持”的值只能在代理监视主机时收集。
键值
描述 值 注释
zabbix[boottime]
Zabbix server 或 Zabbix proxy进程启动时间(秒) 整数
zabbix[history]
存储在HISTORY表中的数量值. 整数. 如果使用MySQL nnoDB, Oracle or PostgreSQL,请勿使用!
(代理服务器不支持)
zabbix[history_log]
存储在HISTORY_LOG表中的数量值 整数. 如果使用MySQL nnoDB, Oracle or PostgreSQL,请勿使用!
从Zabbix 1.8.3 开始支持此监控项
(代理服务器不支持)
zabbix[history_str]
存储在HISTORY_STR表中的数量值 整数. 如果使用MySQL nnoDB, Oracle or PostgreSQL,请勿使用!
(代理服务器不支持)
zabbix[history_text]
存储在HISTORY_TEXT表中的数量值 整数 如果使用MySQL nnoDB, Oracle or PostgreSQL,请勿使用!
从Zabbix 1.8.3 开始支持此监控项
(代理服务器不支持)
zabbix[history_uint]
存储在HISTORY_UINT表中的值数 整数 如果使用MySQL InnoDB, Oracle or PostgreSQL,请勿使用!
从Zabbix 1.8.3 开始支持此监控项
(代理服务器不支持)
zabbix[host,,items]
主机上启用的监控项的数量(受支持和不受支持). 整数 从Zabbix 3.0.0. 开始支持 监控项
zabbix[host,,items_unsupported]
主机上启用的不受支持的监控项数量 整数 从Zabbix **3.0.0.* 开始支持此监控项
zabbix[host,,maintenance]
当前主机的维护状态 0 - 主机处于 常状态,  此监控项始终由Zabbix服务器1 - 主机处于维护状态但采集数据,  第二个参数必须为空,并保2 - 主机处于维护状态不采集数据. 此监控项从Zabbix* 理,无论主机位置如何(在服务器或代理服务器上)。 代理将不会使用配置数据接收该监控项。
供将来使用。
2.4.0.**开始支持
zabbix[host,discovery,interfaces]
Zabbix frontend中主机所有配置接口的详细信息 JSON对象 此监控项可以在 [低级发现]( manual/discovery/low_level_discovery/host_interfaces) 中使用
此监控项从Zabbix3.4.0.开始支持
(代理服务器不支持)
zabbix[host,<type>,available]
主机上特殊类型的检查。该监控项的值对应于主机列表中的可用性图标 0 - 不可用, 1 - 可用, 2 - 未知. 有效的类型是: agent, snmp, ipmi jmx.

监控项的值根据有关主机 不可达/不可用 的配置参数计算.

此监控项从Zabbix2.0.0.开始支持
zabbix[hosts]
已监控主机数量. 整数 此监控项从Zab ix2.2.0开始支持.
zabbix[items]
已启用监控项的数量(受支持和不受支持的) 整数
zabbix[items_unsupported]
不支持的监控项数量 整数
zabbix[java,,<param>]
有关Zabbix Java网关的信息 如果< aram>为 ping, 则返回“1”. 可以使用nodata()触发功能来检查Java网关的可用性。  <param>的有效值是: ping, *ver
如果<param>是 version, 则返回Java网关的版本。 例如: "2.0.0". 第二个参数必须为空,并保留
ion*

将来使用。

此监控项从Zabbix2.0.0.开始支持
zabbix[preprocessing_queue]
预处理队列中队列数量 整数 此监控项可用于监控预处 队列长度
\\此监控项从Zabbix3.4.0.开始支持
zabbix[process,<type>,<mode>,<state>]
时间是一个特定的Zabbix进程或一组进程(由<type>和<mode>标识),以百分比形式在<state>中使用。 仅在最后一分钟计算。
\\如果<mode>是没有运行的Zabbix进程号 (例如,运行<mode>的5个轮询器被指定为6), 则此监控项将变为不受支持的状态。
最小和最大值是指单个进程的使用百分比。因此,如果在一组3个轮询器中,每个进程的使用百分比为2,18和66,则min将返回2,max将返回66。\\进程报告它们在共享内存中所做的事情,而自我监视进程每秒都会对这些数据进行汇总。 状态改变(忙/空闲)在更改时被注册 - 因此一个进程变得繁忙,并且直到状态变为空闲时才更改或更新状态。这确保即使完全挂起的进程也被正确地注册为100%繁忙。\\目前,"busy"表示"not sleeping",但在将来可能会引入额外的状态 - 等待锁、执行数据库查询等。  alert manager在Linux和大多数其它系统上,解析度是1/100秒。
<报警任务管理器
时间百分比
浮点数
目前支持以下进程类型:
alerter - 发送通知的进程 (代理服务器不支持)
**configuration
<yncer** - 用于管理配置数据的内存中缓存的进程
data sender - 代理服务器数据发送者 (不支持Zabbix server)
discoverer - 设备发现进程
escalator - action升级进程 (代理服务器不支持)
heartbeat sender - 代理服务器心跳发送方 (不支持Zabbix server)
history syncer - 历史数据库写入者
housekeeper - 删除旧历史数据的进程
http poller - web轮询检查器
icmp pinger - icmpping轮询检查器
ipmi manager - IPMI轮询管理
ipmi poller - IPMI轮询检查器
java poller - Java检查轮询器
poller - 被动检查的通用轮询器
preprocessing manager - 预处理任务管理
preprocessing worker - 数据预处理进程
proxy poller - 被动代理服务器的轮询器 (代理服务器不支持)
self-monitoring - 收集内部服务器统计信息的进程
snmp trapper - SNMP陷阱捕获器
task manager - 用于远程执行其他组件请求的任务的进程(例如手动关闭, 应答, 强制检查, 远程命令功能)
timer - 处理维护的计时器 (代理服务器不支持)
trapper - 进行主动检查、代理通信的trapper
unreachable poller - 无法访问的设备轮询器
vmware collector - 负责VMware服务数据采集的VMware数据收集器

注意:你还可以在服务器日志文件中查看这些进程类型。

有效模式是:
avg - 给定类型的所有进程的平均值(默认)
count - 返回给定进程类型的forks数,不应指定<state>
max - 最大值
min - 最小值
<process number> - 进程号 (在1和预分叉实例数之间)。 例如, 如果4个trappers正在运行,则该值在1到4之间。

有效状态是:
busy - 进程处于忙状态,例如处理请求(默认)
idle - 进程处于空闲状态,什么都不做。

示例:
=> zabbix[process,poller,avg,busy] → 在最后一分钟内,轮询进程的平均花费时间
=> zabbix[process,"icmp pinger",max,busy] → 在最后一分钟内,通过ICMP pinger进程花费最多时间
=> zabbix[process,"history syncer",2,busy] → 在最后一分钟内,第2号同步器执行某些操作花费的时间
=> zabbix[process,trapper,count] → 当前运行的trapper进程的数量

此监控项从Zabbix 1.8.5. 开始支持
zabbix[proxy,<name>,<param>]
有关Zabbix proxy的信息. 整数 <na e> - 代理服务器名
支持的参数列表 (<param>):
lastaccess - 从代理服务器上收到的最后心跳消息的时间戳

示例:
=> zabbix[proxy,"Germany",lastaccess]

fuzzytime() 触发器函数 可用于检查代理的可用性。
此监控项从Zabbix 2.4.0开始支持,该监控项始终由Zabbix服务器处理,无论主机位置如何(在服务器或代理服务器上)。
zabbix[proxy_history]
代理服务器历史表中等待发送到服务器的值的数量。 整数 此监控项从Zabbix 2.2.0开始支
(不支持Zabbix server)
zabbix[queue,<from>,<to>]
队列中被监视的监控项数量至少延迟了从<from>秒,但小于<to>秒. 整数 <from> - 默认: 6秒
<<to> - 默认: 无限
Time-unit symbols (s,m,h,d,w) 被这些参数支持
参数 fromto 从Zabbix 1.8.3. 开始支持
zabbix[rcache,<cache>,<mode>]
Zabbix配置缓存的可用性统计信息 整数(大小);浮点数( 分比) 缓存: buffer
<Mode:
total - 缓冲区的总大小
free - 可用缓冲区大小
pfree - 可用缓存区百分比
used - 已用的缓存区大小
zabbix[requiredperformance]
Zabbix server或Zabbix proxy所需的性能,以每秒新增的值计算. 浮点数 与*Reports → [系统信息] /manual/web_interface/frontend_sections/reports/status_of_zabbix)* 中的“所需服务器性能,每秒新值”大致相关。
此监控项从Zabbix 1.6.2. 开始支持
zabbix[trends]
存储在TRENDS表中的数量值 整数 如果使用MySQL nnoDB、Oracle或PostgreSQL,请勿使用!
(代理服务器不支持)
zabbix[trends_uint]
存储在TRENDS_UINT表中的数量值 整数 如果使用MySQL nnoDB、Oracle或PostgreSQL,请勿使用!
此监控项从Zabbix 1.8.3. 开始支持
(代理服务器不支持)
zabbix[triggers]
Zabbix数据库中启用的触发器数量,在启用的主机上启用所有的监控项 整数 (代理服务器不支持)
zabbix[uptime]
Zabbix server或zabbix proxy正常运行时间(秒). 整数
zabbix[vcache,buffer,<mode>]
Zabbix值缓存的可用性统计信息 整数(大小);浮点数 百分比) 模式:
<total - 缓冲区的总大小
free - 可用缓冲区大小
pfree - 可用缓冲区百分比
used - 已用的缓冲区大小
pused - 已用的缓冲区百分比

此监控项从Zabbix 2.2.0开始支持
(代理服务器不支持)
zabbix[vcache,cache,<parameter>]
Zabbix值缓存的有效性统计 整数
参数:

使用模式参数:  hit0 - 正常模式,  m1 - 低内存模式 **mo
<requests - 总请求数量
** - 缓存命中数(从缓存中取出的历史值)
sses** - 高速缓存未命中数(从数据库获取的历史值)
e** - 值缓存操作模式
此监控项从Zabbix 2.2.0开始支持, 模式 参数从Zabbix 3.0.0开始支持
(代理服务器不支持)

您可以使用这个键来进行 每秒更改 预处理步骤,以便获得每秒统计值。
zabbix[vmware,buffer,<mode>]
Zabbix vmware缓存的可用性统计信息 整数(大小);浮点 (百分比) 模式:
<total - 缓冲区的总大小
free - 可用缓冲区大小
pfree - 可用缓冲区百分比
used - 已用的缓冲区大小
pused - 已用的缓冲区百分比

此监控项从Zabbix 2.2.0开始支持
zabbix[wcache,<cache>,<mode>]
Zabbix写缓存的统计和可用性 必须指定<c che>
缓存 * 模式**
values all
(默认)
由Zabbix server或Zabbix proxy处理的值的总数(不支持的监控项除外) 整数 计数器
<以使用这个键来进行 每秒更改 预处理步骤,以便获得每秒统计值。
float 处理的浮点值的数量. 整数 计数器
uint 处理的无符号整数值的数量. 整数 计数器
str 处理的字符/字符串值的数量 整数 计数器
log 处理日志值的数量 整数 计数器
text 已处理文本值的数量 整数 计数器
not supported 项目处理导致监控项不受支持或保持该状态的次数. 整数 计数器
<Not supported 模式从Zabbix 1.8.6.开始支持
history pfree
(默认)
可用历史缓冲区的百分比. 浮点数 历史缓存用于存储监控项值。 比较低表示数据库端会有性能问题。
free 可用历史缓冲区大小 整数
total 历史缓冲区总大小 整数
used 已用的历史缓冲区大小 整数
index pfree
(默认)
可用的历史索引缓冲区的百分比 浮点数 历史索引缓存用于索引存储在历史缓* 中的值。
引* 缓存从Zabbix 3.0.0开始支持
free 可用历史索引缓冲区的大小 整数
total 历史记录索引缓冲区的总大小 整数
used 已用的历史索引缓冲区的大小 整数
trend pfree
(默认)
可用趋势缓存的百分比 浮点数 趋势缓存存储接收数据的所* 监控项的当前小时的聚合。
代理服务器不支持)*
free 可用趋势缓存大小 整数 *(代理服务器不支 )*
total 趋势缓存总大小 整数 *(代理服务器不 持)*
used 已用的趋势缓存大小 整数 *(代理服务器不支持 *

Item key details

  • Parameters without angle brackets are constants - for example, 'host' and 'available' in zabbix[host,<type>,available]. Use them in the item key as is.
  • Values for items and item parameters that are "not supported on proxy" can only be retrieved if the host is monitored by server. And vice versa, values "not supported on server" can only be retrieved if the host is monitored by proxy.
zabbix[boottime]


The startup time of Zabbix server or Zabbix proxy process in seconds.
Return value: Integer.

zabbix[cluster,discovery,nodes]


Discovers the high availability cluster nodes.
Return value: JSON object.

This item can be used in low-level discovery.

zabbix[connector_queue]


The count of values enqueued in the connector queue.
Return value: Integer.

This item is supported since Zabbix 6.4.0.

zabbix[host,,items]


The number of enabled items (supported and not supported) on the host.
Return value: Integer.

zabbix[host,,items_unsupported]


The number of enabled unsupported items on the host.
Return value: Integer.

zabbix[host,,maintenance]


The current maintenance status of the host.
Return values: 0 - normal state; 1 - maintenance with data collection; 2 - maintenance without data collection.

Comments:

  • This item is always processed by Zabbix server regardless of the host location (on server or proxy). The proxy will not receive this item with configuration data.
  • The second parameter must be empty and is reserved for future use.
zabbix[host,active_agent,available]


The availability of active agent checks on the host.
Return values: 0 - unknown; 1 - available; 2 - not available.

zabbix[host,discovery,interfaces]


The details of all configured interfaces of the host in Zabbix frontend.
Return value: JSON object.

Comments:

zabbix[host,<type>,available]


The availability of the main interface of a particular type of checks on the host.
Return values: 0 - not available; 1 - available; 2 - unknown.

Comments:

  • Valid types are: agent, snmp, ipmi, jmx;
  • The item value is calculated according to the configuration parameters regarding host unreachability/unavailability.
zabbix[hosts]


The number of monitored hosts.
Return value: Integer.

zabbix[items]


The number of enabled items (supported and not supported).
Return value: Integer.

zabbix[items_unsupported]


The number of unsupported items.
Return value: Integer.

zabbix[java,,<param>]


The information about Zabbix Java gateway.
Return values: 1 - if <param> is ping; Java gateway version - if <param> is version (for example: "2.0.0").

Comments:

  • Valid values for param are: ping, version;
  • This item can be used to check Java gateway availability using the nodata() trigger function;
  • The second parameter must be empty and is reserved for future use.
zabbix[lld_queue]


The count of values enqueued in the low-level discovery processing queue.
Return value: Integer.

This item can be used to monitor the low-level discovery processing queue length.

zabbix[preprocessing_queue]


The count of values enqueued in the preprocessing queue.
Return value: Integer.

This item can be used to monitor the preprocessing queue length.

zabbix[process,<type>,<mode>,<state>]


The percentage of time a particular Zabbix process or a group of processes (identified by <type> and <mode>) spent in <state>. It is calculated for the last minute only.
Return value: Float.

Parameters:

  • type - for server processes: alert manager, alert syncer, alerter, availability manager, configuration syncer, connector manager, connector worker, discoverer, escalator, history poller, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, lld manager, lld worker, odbc poller, poller, preprocessing manager, preprocessing worker, proxy poller, self-monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector;
    for proxy processes: availability manager, configuration syncer, data sender, discoverer, history syncer, housekeeper, http poller, icmp pinger, ipmi manager, ipmi poller, java poller, odbc poller, poller, preprocessing manager, preprocessing worker, self-monitoring, snmp trapper, task manager, trapper, unreachable poller, vmware collector
  • mode - avg - average value for all processes of a given type (default)
    count - returns number of forks for a given process type, <state> should not be specified
    max - maximum value
    min - minimum value
    <process number> - process number (between 1 and the number of pre-forked instances). For example, if 4 trappers are running, the value is between 1 and 4.
  • state - busy - process is in busy state, for example, the processing request (default); idle - process is in idle state doing nothing.

Comments:

  • If <mode> is a Zabbix process number that is not running (for example, with 5 pollers running the <mode> is specified to be 6), such an item will turn unsupported;
  • Minimum and maximum refers to the usage percentage for a single process. So if in a group of 3 pollers usage percentages per process were 2, 18 and 66, min would return 2 and max would return 66.
  • Processes report what they are doing in shared memory and the self-monitoring process summarizes that data each second. State changes (busy/idle) are registered upon change - thus a process that becomes busy registers as such and doesn't change or update the state until it becomes idle. This ensures that even fully hung processes will be correctly registered as 100% busy.
  • Currently, "busy" means "not sleeping", but in the future additional states might be introduced - waiting for locks, performing database queries, etc.
  • On Linux and most other systems, resolution is 1/100 of a second.

Examples:

zabbix[process,poller,avg,busy] #the average time of poller processes spent doing something during the last minute
       zabbix[process,"icmp pinger",max,busy] #the maximum time spent doing something by any ICMP pinger process during the last minute
       zabbix[process,"history syncer",2,busy] #the time spent doing something by history syncer number 2 during the last minute
       zabbix[process,trapper,count] #the amount of currently running trapper processes
zabbix[proxy,<name>,<param>]


The information about Zabbix proxy.
Return value: Integer.

Parameters:

  • name - the proxy name;
  • param - delay - how long the collected values are unsent, calculated as "proxy delay" (difference between the current proxy time and the timestamp of the oldest unsent value on proxy) + ("current server time" - "proxy lastaccess").
zabbix[proxy,discovery]


The list of Zabbix proxies with name, mode, encryption, compression, version, last seen, host count, item count, required values per second (vps) and version status (current/outdated/unsupported).
Return value: JSON object.

zabbix[proxy_history]


The number of values in the proxy history table waiting to be sent to the server.
Return values: Integer.

This item is not supported on Zabbix server.

zabbix[queue,<from>,<to>]


The number of monitored items in the queue which are delayed at least by <from> seconds, but less than <to> seconds.
Return value: Integer.

Parameters:

  • from - default: 6 seconds;
  • to - default: infinity.

Time-unit symbols (s,m,h,d,w) are supported in the parameters.

zabbix[rcache,<cache>,<mode>]


The availability statistics of the Zabbix configuration cache.
Return values: Integer (for size); Float (for percentage).

Parameters:

  • cache - buffer;
  • mode - total - the total size of buffer
    free - the size of free buffer
    pfree - the percentage of free buffer
    used - the size of used buffer
    pused - the percentage of used buffer
zabbix[requiredperformance]


The required performance of Zabbix server or Zabbix proxy, in new values per second expected.
Return value: Float.

Approximately correlates with "Required server performance, new values per second" in Reports → System information.

zabbix[stats,<ip>,<port>]


The internal metrics of a remote Zabbix server or proxy.
Return values: JSON object.

Parameters:

  • ip - the IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1);
  • port - the port of server/proxy to be remotely queried (default is 10051).

Comments:

  • 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>]


The internal queue metrics (see zabbix[queue,<from>,<to>]) of a remote Zabbix server or proxy.
Return values: JSON object.

Parameters:

  • ip - the IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1);
  • port - the port of server/proxy to be remotely queried (default is 10051);
  • from - delayed by at least (default is 6 seconds);
  • to - delayed by at most (default is infinity).

Comments:

  • 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[tcache,<cache>,<parameter>]


The effectiveness statistics of the Zabbix trend function cache.
Return values: Integer (for size); Float (for percentage).

Parameters:

  • cache - buffer;
  • mode - **all* - total cache requests (default)
    hits - cache hits
    phits - percentage of cache hits
    misses - cache misses
    pmisses - percentage of cache misses
    items - the number of cached items
    requests - the number of cached requests
    pitems - percentage of cached items from cached items + requests. Low percentage most likely means that the cache size can be reduced.

This item is not supported on Zabbix proxy.

zabbix[triggers]


The number of enabled triggers in Zabbix database, with all items enabled on enabled hosts.
Return value: Integer.

This item is not supported on Zabbix proxy.

zabbix[uptime]


The uptime of the Zabbix server or proxy process in seconds.
Return value: Integer.

zabbix[vcache,buffer,<mode>]


The availability statistics of the Zabbix value cache.
Return values: Integer (for size); Float (for percentage).

Parameter:

  • mode - total - the total size of buffer
    free - the size of free buffer
    pfree - the percentage of free buffer
    used - the size of used buffer
    pused - the percentage of used buffer

This item is not supported on Zabbix proxy.

zabbix[vcache,cache,<parameter>]


The effectiveness statistics of the Zabbix value cache.
Return values: Integer. With the mode parameter returns: 0 - normal mode; 1 - low memory mode.

Parameters:

  • parameter - requests - the total number of requests
    hits - the number of cache hits (history values taken from the cache)
    misses - the number of cache misses (history values taken from the database)
    mode - the value cache operating mode

Comments:

  • Once the low-memory mode has been switched on, the value cache will remain in this state for 24 hours, even if the problem that triggered this mode is resolved sooner;
  • You may use this key with the Change per second preprocessing step in order to get values-per-second statistics;
  • This item is not supported on Zabbix proxy.
zabbix[version]


The version of Zabbix server or proxy.
Return value: String. For example: 6.0.0beta1.

zabbix[vmware,buffer,<mode>]


The availability statistics of the Zabbix vmware cache.
Return values: Integer (for size); Float (for percentage).

Parameters:

  • mode - total - the total size of buffer
    free - the size of free buffer
    pfree - the percentage of free buffer
    used - the size of used buffer
    pused - the percentage of used buffer
zabbix[wcache,<cache>,<mode>]


The statistics and availability of the Zabbix write cache.
Return values: Integer (for number/size); Float (for percentage).

Parameters:

  • cache - values, history, index, or trend;
  • mode - (with values) all (default) - the total number of values processed by Zabbix server/proxy, except unsupported items (counter)
    float - the number of processed float values (counter)
    uint - the number of processed unsigned integer values (counter)
    str - the number of processed character/string values (counter)
    log - the number of processed log values (counter)
    text - the number of processed text values (counter)
    not supported - the number of times item processing resulted in item becoming unsupported or keeping that state (counter)
    (with history, index, trend cache) pfree (default) - the percentage of free buffer
    total - the total size of buffer
    free - the size of free buffer
    used - the size of used buffer
    pused - the percentage of used buffer

Comments:

  • Specifying <cache> is mandatory. The trend cache parameter is not supported with Zabbix proxy.
  • The history cache is used to store item values. A low number indicates performance problems on the database side.
  • The history index cache is used to index the values stored in the history cache;
  • The trend cache stores the aggregate for the current hour for all items that receive data;
  • You may use the zabbix[wcache,values] key with the Change per second preprocessing step in order to get values-per-second statistics.