en-us	#### Supported checks  -   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 gathered if the host is monitored by server. And     vice versa, values "not supported on server" can only be gathered if     the host is monitored by proxy.  |Key|<|<|<|<|<| |---|-|-|-|-|-| |▲|Description|<|<|Return value|Comments| |zabbix\[boottime\]|<|<|<|<|<| |<|Startup time of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[cluster,discovery,nodes\]|<|<|<|<|<| |<|Discover [high availability cluster](/manual/concepts/server/ha) nodes.|<|<|JSON.|This item can be used in low-level discovery.| |zabbix\[history\]|<|<|<|<|<| |<|Number of values stored in the HISTORY table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_LOG table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_STR table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_TEXT table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_UINT table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported) on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|Number of enabled unsupported items on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.\*| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|Current maintenance status of a host.|<|<|0 - host in normal state,<br>1 - host in maintenance with data collection,<br>2 - host in maintenance without data collection.|This item is always processed by Zabbix server regardless of host location (on server or proxy). The proxy will not receive this item with configuration data.<br>The second parameter must be empty and is reserved for future use.| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|Details of all configured interfaces of the host in Zabbix frontend.|<|<|JSON object.|This item can be used in [low-level discovery](/manual/discovery/low_level_discovery/examples/host_interfaces).<br>This item is supported since Zabbix 3.4.0.<br>*(not supported on proxy)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|Availability of the main interface of a particular type of checks on the host.|<|<|0 - not available, 1 - available, 2 - unknown.|Valid **types** are:<br>*agent*, *snmp*, *ipmi*, *jmx*<br><br>The item value is calculated according to configuration parameters regarding host [unreachability/unavailability](/manual/appendix/items/unreachability).<br><br>This item is supported since Zabbix 2.0.0.<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|Number of monitored hosts.|<|<|Integer.|<| |zabbix\[items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported).|<|<|Integer.|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|Number of not supported items.|<|<|Integer.|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|Information about Zabbix Java gateway.|<|<|If <param> is *ping*, "1" is returned. Can be used to check Java gateway availability using nodata() trigger function.<br><br>If <param> is *version*, version of Java gateway is returned. Example: "2.0.0".|Valid values for **param** are:<br>*ping*, *version*<br><br>Second parameter must be empty and is reserved for future use.| |zabbix\[lld\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the low-level discovery processing queue.|<|<|Integer.|This item can be used to monitor the low-level discovery processing queue length.<br><br>This item is supported since Zabbix 4.2.0.| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the preprocessing queue.|<|<|Integer.|This item can be used to monitor the preprocessing queue length.<br><br>This item is supported since Zabbix 3.4.0.| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|Time a particular Zabbix process or a group of processes (identified by <type> and <mode>) spent in <state> in percentage. It is calculated for the last minute only.<br><br>If <mode> is Zabbix process number that is not running (for example, with 5 pollers running <mode> is specified to be 6), such an item will turn into unsupported state.<br>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.<br>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.<br>Currently, "busy" means "not sleeping", but in the future additional states might be introduced - waiting for locks, performing database queries, etc.<br>On Linux and most other systems, resolution is 1/100 of a second.|<|<|Percentage of time.<br>Float.|Supported **types** of [server processes](/manual/concepts/server#server_process_types):<br>*alert manager*, *alert syncer*, *alerter*, *availability manager*, *configuration syncer*, *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*<br><br>Supported **types** of [proxy processes](/manual/concepts/proxy#proxy_process_types):<br>*availability manager*, *configuration syncer*, *data sender*, *discoverer*, *heartbeat sender*, *history poller*, *history syncer*, *housekeeper*, *http poller*, *icmp pinger*, *ipmi manager*, *ipmi poller*, *java poller*, *odbs poller*, *poller*, *preprocessing manager*, *preprocessing worker*, *self-monitoring*, *snmp trapper*, *task manager*, *trapper*, *unreachable poller*, *vmware collector*<br><br>Valid **modes** are:<br>*avg* - average value for all processes of a given type (default)<br>*count* - returns number of forks for a given process type, <state> should not be specified<br>*max* - maximum value<br>*min* - minimum value<br>*<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.<br><br>Valid **states** are:<br>*busy* - process is in busy state, for example, processing request (default).<br>*idle* - process is in idle state doing nothing.<br><br>Examples:<br>=> zabbix\[process,poller,avg,busy\] → average time of poller processes spent doing something during the last minute<br>=> zabbix\[process,"icmp pinger",max,busy\] → maximum time spent doing something by any ICMP pinger process during the last minute<br>=> zabbix\[process,"history syncer",2,busy\] → time spent doing something by history syncer number 2 during the last minute<br>=> zabbix\[process,trapper,count\] → amount of currently running trapper processes| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|Information about Zabbix proxy.|<|<|Integer.|**name**: proxy name<br><br>Valid values for **param** are:<br>*lastaccess* - timestamp of last heart beat message received from proxy<br>*delay* - how long 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")<br><br>Example:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>`fuzzytime()` [function](/manual/appendix/functions/history) can be used to check availability of proxies.<br>This item is always processed by Zabbix server regardless of host location (on server or proxy).| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|Number of values in the proxy history table waiting to be sent to the server.|<|<|Integer.|*(not supported on server)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|Number of monitored items in the queue which are delayed at least by <from> seconds but less than by <to> seconds.|<|<|Integer.|**from** - default: 6 seconds<br>**to** - default: infinity<br>[Time-unit symbols](/manual/appendix/suffixes) (s,m,h,d,w) are supported for these parameters.| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix configuration cache.|<|<|Integer (for size); float (for percentage).|**cache**: *buffer*<br><br>Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*pused* mode is supported since Zabbix 4.0.0.| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Required performance of Zabbix server or Zabbix proxy, in new values per second expected.|<|<|Float.|Approximately correlates with "Required server performance, new values per second" in *Reports → [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*.| |zabbix\[stats,<ip>,<port>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal metrics.|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).<br><br>Supported since 4.2.0.| |zabbix\[stats,<ip>,<port>,queue,<from>,<to>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal queue metrics (see `zabbix[queue,<from>,<to>]`).|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>Supported since 4.2.0.| |zabbix\[tcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of the Zabbix trend function cache.|<|<|Integer (for size); float (for percentage).|Valid **parameters** are:<br>*all* - total cache requests (default)<br>*hits* - cache hits<br>*phits* - percentage of cache hits<br>*misses* - cache misses<br>*pmisses* - percentage of cache misses<br>*items* - the number of cached items<br>*requests* - the number of cached requests<br>*pitems* - percentage of cached items from cached items + requests. Low percentage most likely means that the cache size can be reduced.<br><br>Supported since 5.4.0.<br><br>*(not supported on proxy)*| |zabbix\[trends\]|<|<|<|<|<| |<|Number of values stored in the TRENDS table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|Number of values stored in the TRENDS\_UINT table.|<|<|Integer.|Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Number of enabled triggers in Zabbix database, with all items enabled on enabled hosts.|<|<|Integer.|*(not supported on proxy)*| |zabbix\[uptime\]|<|<|<|<|<| |<|Uptime of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix value cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*(not supported on proxy)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of Zabbix value cache.|<|<|Integer.<br><br>With the *mode* parameter:<br>0 - normal mode,<br>1 - low memory mode|Valid **parameter** values are:<br>*requests* - total number of requests<br>*hits* - number of cache hits (history values taken from the cache)<br>*misses* - number of cache misses (history values taken from the database)<br>*mode* - value cache operating mode<br><br>This item is supported since Zabbix 2.2.0 and the *mode* parameter since Zabbix 3.0.0.<br>*(not supported on proxy)*<br><br>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.<br><br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |zabbix\[version\]|<|<|<|<|<| |<|Version of Zabbix server or proxy.|<|<|String.|This item is supported since Zabbix 5.0.0.<br><br>Example of return value: 5.0.0beta1| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix vmware cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Statistics and availability of Zabbix write cache.|<|<|<|Specifying <cache> is mandatory.| |<|**Cache**|**Mode**|<|<|<| |^|values|all<br>*(default)*|Total number of values processed by Zabbix server or Zabbix proxy, except unsupported items.|Integer.|Counter.<br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |^|^|float|Number of processed float values.|Integer.|Counter.| |^|^|uint|Number of processed unsigned integer values.|Integer.|Counter.| |^|^|str|Number of processed character/string values.|Integer.|Counter.| |^|^|log|Number of processed log values.|Integer.|Counter.| |^|^|text|Number of processed text values.|Integer.|Counter.| |^|^|not supported|Number of times item processing resulted in item becoming unsupported or keeping that state.|Integer.|Counter.<br>| |^|history|pfree<br>*(default)*|Percentage of free history buffer.|Float.|History cache is used to store item values. A low number indicates performance problems on the database side.| |^|^|free|Size of free history buffer.|Integer.|<| |^|^|total|Total size of history buffer.|Integer.|<| |^|^|used|Size of used history buffer.|Integer.|<| |^|^|pused|Percentage of used history buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|index|pfree<br>*(default)*|Percentage of free history index buffer.|Float.|History index cache is used to index values stored in history cache.<br>*Index* cache is supported since Zabbix 3.0.0.| |^|^|free|Size of free history index history buffer.|Integer.|<| |^|^|total|Total size of history index history buffer.|Integer.|<| |^|^|used|Size of used history index history buffer.|Integer.|<| |^|^|pused|Percentage of used history index buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|trend|pfree<br>*(default)*|Percentage of free trend cache.|Float.|Trend cache stores aggregate for the current hour for all items that receive data.<br>*(not supported on proxy)*| |^|^|free|Size of free trend buffer.|Integer.|*(not supported on proxy)*| |^|^|total|Total size of trend buffer.|Integer.|*(not supported on proxy)*| |^|^|used|Size of used trend buffer.|Integer.|*(not supported on proxy)*| |^|^|pused|Percentage of used trend buffer.|Float.|*(not supported on proxy)*<br><br>*pused* mode is supported since Zabbix 4.0.0.|  
zh-cn	#### 支持的检查  -   没有尖括号的参数是常量 - 例如,     `zabbix[host,<type>,available]`中的'host' and 'available'.     在监控项键值中使用它们。 -   仅当主机被服务器监控时，才能收集“代理服务器不支持”的监控项和监控项参数的值。反之亦然，“服务器不支持”的值只能在代理监视主机时收集。  |键值|<|<|<|<|<| |------|-|-|-|-|-| |▲|描述|<|返|值                                                                                         注释|<| |zabbix\[boottime\]|<|<|<|<|<| |<|Zabbix server 或 Zabbix proxy进程启动时间（秒）|<|整数|<|<| |zabbix\[history\]|<|<|<|<|<| |<|存储在HISTORY表中的数量值.|<|整数.|如果使用MySQL|nnoDB, Oracle or PostgreSQL，请勿使用!<br>*(代理服务器不支持)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|存储在HISTORY\_LOG表中的数量值|<|整数.|如果使用MySQL|nnoDB, Oracle or PostgreSQL，请勿使用!<br>从Zabbix **1.8.3** 开始支持此监控项<br>*(代理服务器不支持)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|存储在HISTORY\_STR表中的数量值|<|整数.|如果使用MySQL|nnoDB, Oracle or PostgreSQL，请勿使用!<br>*(代理服务器不支持)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|存储在HISTORY\_TEXT表中的数量值|<|整数|如果使用MySQL|nnoDB, Oracle or PostgreSQL，请勿使用!<br>从Zabbix **1.8.3** 开始支持此监控项<br>*(代理服务器不支持)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|存储在HISTORY\_UINT表中的值数|<|整数|如果使用MySQL|InnoDB, Oracle or PostgreSQL，请勿使用!<br>从Zabbix **1.8.3** 开始支持此监控项<br>*(代理服务器不支持)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|主机上启用的监控项的数量（受支持和不受支持）.|<|整数|从Zabbix **3.0.0.** 开始支持|监控项| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|主机上启用的不受支持的监控项数量|<|整数|从Zabbix **3.0.0.*|开始支持此监控项| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|当前主机的维护状态|<|0 - 主机处于|常状态,\                                                                         此监控项始终由Zabbix服务器1 - 主机处于维护状态但采集数据,\                                                               第二个参数必须为空，并保2 - 主机处于维护状态不采集数据.                                                                此监控项从Zabbix*|理，无论主机位置如何（在服务器或代理服务器上）。 代理将不会使用配置数据接收该监控项。<br>供将来使用。<br>2.4.0.**开始支持<br>| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|Zabbix frontend中主机所有配置接口的详细信息|<|JSON对象|此监控项可以在 [低级发现](|manual/discovery/low_level_discovery/host_interfaces) 中使用<br>此监控项从Zabbix**3.4.0.**开始支持<br>*(代理服务器不支持)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|主机上特殊类型的检查。该监控项的值对应于主机列表中的可用性图标|<|0 - 不可用, 1 - 可用, 2 - 未知.|有效的类型是: **agent**, **snmp**, **ipmi**|**jmx**.<br><br>监控项的值根据有关主机 [不可达/不可用](/manual/appendix/items/unreachability) 的配置参数计算.<br><br>此监控项从Zabbix**2.0.0.**开始支持<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|已监控主机数量.|<|整数|此监控项从Zab|ix**2.2.0**开始支持.| |zabbix\[items\]|<|<|<|<|<| |<|已启用监控项的数量（受支持和不受支持的）|<|整数|<|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|不支持的监控项数量|<|整数|<|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|有关Zabbix Java网关的信息|<|如果<|aram>为 **ping**, 则返回“1”. 可以使用nodata（）触发功能来检查Java网关的可用性。\   <param>的有效值是: *ping*, *ver<br>如果<param>是 **version**, 则返回Java网关的版本。 例如: "2.0.0".                         第二个参数必须为空，并保留|ion*<br><br>将来使用。<br><br>此监控项从Zabbix**2.0.0.**开始支持| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|预处理队列中队列数量|<|整数|此监控项可用于监控预处|队列长度<br>\\\\此监控项从Zabbix**3.4.0.**开始支持| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|时间是一个特定的Zabbix进程或一组进程（由<type>和<mode>标识）,以百分比形式在<state>中使用。 仅在最后一分钟计算。<br>\\\\如果<mode>是没有运行的Zabbix进程号 (例如，运行<mode>的5个轮询器被指定为6), 则此监控项将变为不受支持的状态。<br>最小和最大值是指单个进程的使用百分比。因此，如果在一组3个轮询器中，每个进程的使用百分比为2,18和66，则min将返回2，max将返回66。\\\\进程报告它们在共享内存中所做的事情，而自我监视进程每秒都会对这些数据进行汇总。 状态改变（忙/空闲）在更改时被注册 - 因此一个进程变得繁忙，并且直到状态变为空闲时才更改或更新状态。这确保即使完全挂起的进程也被正确地注册为100％繁忙。\\\\目前，"busy"表示"not sleeping"，但在将来可能会引入额外的状态 - 等待锁、执行数据库查询等。\                                                                                                                                                                                      **alert manager**在Linux和大多数其它系统上，解析度是1/100秒。|<报警任务管理器<br>|时间百分比<br>浮点数|目前支持以下进程类型:<br>**alerter** - 发送通知的进程 *(代理服务器不支持)*<br>**configuration|<yncer** - 用于管理配置数据的内存中缓存的进程<br>**data sender** - 代理服务器数据发送者 *(不支持Zabbix server)*<br>**discoverer** - 设备发现进程<br>**escalator** - action升级进程 *(代理服务器不支持)*<br>**heartbeat sender** - 代理服务器心跳发送方 *(不支持Zabbix server)*<br>**history syncer** - 历史数据库写入者<br>**housekeeper** - 删除旧历史数据的进程<br>**http poller** - web轮询检查器<br>**icmp pinger** - icmpping轮询检查器<br>**ipmi manager** - IPMI轮询管理<br>**ipmi poller** - IPMI轮询检查器<br>**java poller** - Java检查轮询器<br>**poller** - 被动检查的通用轮询器<br>**preprocessing manager** - 预处理任务管理<br>**preprocessing worker** - 数据预处理进程<br>**proxy poller** - 被动代理服务器的轮询器 *(代理服务器不支持)*<br>**self-monitoring** - 收集内部服务器统计信息的进程<br>**snmp trapper** - SNMP陷阱捕获器<br>**task manager** - 用于远程执行其他组件请求的任务的进程(例如手动关闭, 应答, 强制检查, 远程命令功能)<br>**timer** - 处理维护的计时器 *(代理服务器不支持)*<br>**trapper** - 进行主动检查、代理通信的trapper<br>**unreachable poller** - 无法访问的设备轮询器<br>**vmware collector** - 负责VMware服务数据采集的VMware数据收集器<br><br>注意：你还可以在服务器日志文件中查看这些进程类型。<br><br>有效模式是:<br>**avg** - 给定类型的所有进程的平均值（默认）<br>**count** - 返回给定进程类型的forks数，不应指定**<state>**<br>**max** - 最大值<br>**min** - 最小值<br>**<process number>** - 进程号 (在1和预分叉实例数之间)。 例如, 如果4个trappers正在运行，则该值在1到4之间。<br><br>有效状态是:<br>**busy** - 进程处于忙状态，例如处理请求（默认）<br>**idle** - 进程处于空闲状态，什么都不做。<br><br>示例:<br>=> zabbix\[process,poller,avg,busy\] → 在最后一分钟内，轮询进程的平均花费时间<br>=> zabbix\[process,"icmp pinger",max,busy\] → 在最后一分钟内，通过ICMP pinger进程花费最多时间<br>=> zabbix\[process,"history syncer",2,busy\] → 在最后一分钟内，第2号同步器执行某些操作花费的时间<br>=> zabbix\[process,trapper,count\] → 当前运行的trapper进程的数量<br><br>此监控项从Zabbix **1.8.5.** 开始支持| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|有关Zabbix proxy的信息.|<|整数|<na|e> - 代理服务器名<br>支持的参数列表 (<param>):<br>lastaccess - 从代理服务器上收到的最后心跳消息的时间戳<br><br>示例:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>**fuzzytime()** [触发器函数](/manual/appendix/triggers/functions) 可用于检查代理的可用性。<br>此监控项从Zabbix 2.4.0开始支持，该监控项始终由Zabbix服务器处理，无论主机位置如何（在服务器或代理服务器上）。| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|代理服务器历史表中等待发送到服务器的值的数量。|<|整数|此监控项从Zabbix **2.2.0**开始支|。<br>*(不支持Zabbix server)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|队列中被监视的监控项数量至少延迟了从<from>秒，但小于<to>秒.|<|整数|<from> - 默认: 6秒<br>|<<to> - 默认: 无限<br>[Time-unit symbols](/manual/appendix/suffixes) (s,m,h,d,w) 被这些参数支持<br>参数 `from` 和 `to` 从Zabbix **1.8.3.** 开始支持| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix配置缓存的可用性统计信息|<|整数（大小）;浮点数（|分比）                                                                  缓存: **buffer**<br>|<Mode:<br>**total** - 缓冲区的总大小<br>**free** - 可用缓冲区大小<br>**pfree** - 可用缓存区百分比<br>**used** - 已用的缓存区大小| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Zabbix server或Zabbix proxy所需的性能，以每秒新增的值计算.|<|浮点数|与*Reports → [系统信息]|/manual/web_interface/frontend_sections/reports/status_of_zabbix)* 中的“所需服务器性能，每秒新值”大致相关。<br>此监控项从Zabbix **1.6.2.** 开始支持| |zabbix\[trends\]|<|<|<|<|<| |<|存储在TRENDS表中的数量值|<|整数|如果使用MySQL|nnoDB、Oracle或PostgreSQL，请勿使用！<br>*(代理服务器不支持)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|存储在TRENDS\_UINT表中的数量值|<|整数|如果使用MySQL|nnoDB、Oracle或PostgreSQL，请勿使用！<br>此监控项从Zabbix **1.8.3.** 开始支持<br>*(代理服务器不支持)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Zabbix数据库中启用的触发器数量，在启用的主机上启用所有的监控项|<|整数|*(代理服务器不支持)*|<| |zabbix\[uptime\]|<|<|<|<|<| |<|Zabbix server或zabbix proxy正常运行时间（秒）.|<|整数|<|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix值缓存的可用性统计信息|<|整数（大小）;浮点数|百分比）                                                                  模式:<br>|<**total** - 缓冲区的总大小<br>**free** - 可用缓冲区大小<br>**pfree** - 可用缓冲区百分比<br>**used** - 已用的缓冲区大小<br>**pused** - 已用的缓冲区百分比<br><br>此监控项从Zabbix **2.2.0**开始支持<br>*(代理服务器不支持)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Zabbix值缓存的有效性统计|<|整数<br>|参数:<br><br>使用**模式**参数:\                                                                             **hit0 - 正常模式,\                                                                                 **m1 - 低内存模式                                                                                 **mo|<**requests** - 总请求数量<br>** - 缓存命中数（从缓存中取出的历史值）<br>sses** - 高速缓存未命中数（从数据库获取的历史值）<br>e** - 值缓存操作模式<br>此监控项从Zabbix **2.2.0**开始支持， **模式** 参数从Zabbix **3.0.0**开始支持<br>*(代理服务器不支持)*<br><br>您可以使用这个键来进行 *每秒更改* 预处理步骤，以便获得每秒统计值。| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix vmware缓存的可用性统计信息|<|整数（大小）;浮点|（百分比）                                                                  模式:<br>|<**total** - 缓冲区的总大小<br>**free** - 可用缓冲区大小<br>**pfree** - 可用缓冲区百分比<br>**used** - 已用的缓冲区大小<br>**pused** - 已用的缓冲区百分比<br><br>此监控项从Zabbix **2.2.0**开始支持<br>| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix写缓存的统计和可用性|<|<|必须指定<c|che>| |<|**缓存**                                                                                                                                                                                                                                                                                                                                                                                                                                                               *|模式**|<|<|<| |^|values|all<br>*(默认)*|由Zabbix server或Zabbix proxy处理的值的总数（不支持的监控项除外）   整数|计数器<br>您|<以使用这个键来进行 *每秒更改* 预处理步骤，以便获得每秒统计值。| |^|^|float|处理的浮点值的数量.                                                 整数|计数器|<| |^|^|uint|处理的无符号整数值的数量.                                           整数|计数器|<| |^|^|str|处理的字符/字符串值的数量                                           整数|计数器|<| |^|^|log|处理日志值的数量                                                    整数|计数器|<| |^|^|text|已处理文本值的数量                                                  整数|计数器|<| |^|^|not supported|项目处理导致监控项不受支持或保持该状态的次数.                       整数|计数器<br>|<*Not supported* 模式从Zabbix **1.8.6.**开始支持| |^|history|pfree<br>*(默认)*|可用历史缓冲区的百分比.                                             浮点数|历史缓存用于存储监控项值。|比较低表示数据库端会有性能问题。| |^|^|free|可用历史缓冲区大小                                                  整数|<|<| |^|^|total|历史缓冲区总大小                                                    整数|<|<| |^|^|used|已用的历史缓冲区大小                                                整数|<|<| |^|index|pfree<br>*(默认)*|可用的历史索引缓冲区的百分比                                        浮点数|历史索引缓存用于索引存储在历史缓*|中的值。<br>引* 缓存从Zabbix **3.0.0**开始支持| |^|^|free|可用历史索引缓冲区的大小                                            整数|<|<| |^|^|total|历史记录索引缓冲区的总大小                                          整数|<|<| |^|^|used|已用的历史索引缓冲区的大小                                          整数|<|<| |^|trend|pfree<br>*(默认)*|可用趋势缓存的百分比                                                浮点数|趋势缓存存储接收数据的所*|监控项的当前小时的聚合。<br>代理服务器不支持)*| |^|^|free|可用趋势缓存大小                                                    整数|*(代理服务器不支|)*| |^|^|total|趋势缓存总大小                                                      整数|*(代理服务器不|持)*| |^|^|used|已用的趋势缓存大小                                                  整数|*(代理服务器不支持|*|  

en-us	#### Supported checks  -   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 gathered if the host is monitored by server. And     vice versa, values "not supported on server" can only be gathered if     the host is monitored by proxy.  |Key|<|<|<|<|<| |-|------|--|------|------|-| |▲|Description|<|<|Return value|Comments| |zabbix\[boottime\]|<|<|<|<|<| |<|Startup time of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[cluster,discovery,nodes\]|<|<|<|<|<| |<|Discover [high availability cluster](/manual/concepts/server/ha) nodes.|<|<|JSON.|This item can be used in low-level discovery.| |zabbix\[history\]|<|<|<|<|<| |<|Number of values stored in the HISTORY table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_LOG table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_STR table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_TEXT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_UINT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported) on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|Number of enabled unsupported items on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.\*| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|Current maintenance status of a host.|<|<|0 - host in normal state,<br>1 - host in maintenance with data collection,<br>2 - host in maintenance without data collection.|This item is always processed by Zabbix server regardless of host location (on server or proxy). The proxy will not receive this item with configuration data.<br>The second parameter must be empty and is reserved for future use.| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|Details of all configured interfaces of the host in Zabbix frontend.|<|<|JSON object.|This item can be used in [low-level discovery](/manual/discovery/low_level_discovery/examples/host_interfaces).<br>This item is supported since Zabbix 3.4.0.<br>*(not supported on proxy)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|Availability of the main interface of a particular type of checks on the host.|<|<|0 - not available, 1 - available, 2 - unknown.|Valid **types** are:<br>*agent*, *snmp*, *ipmi*, *jmx*<br><br>The item value is calculated according to configuration parameters regarding host [unreachability/unavailability](/manual/appendix/items/unreachability).<br><br>This item is supported since Zabbix 2.0.0.<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|Number of monitored hosts.|<|<|Integer.|<| |zabbix\[items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported).|<|<|Integer.|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|Number of not supported items.|<|<|Integer.|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|Information about Zabbix Java gateway.|<|<|If <param> is *ping*, "1" is returned. Can be used to check Java gateway availability using nodata() trigger function.<br><br>If <param> is *version*, version of Java gateway is returned. Example: "2.0.0".|Valid values for **param** are:<br>*ping*, *version*<br><br>Second parameter must be empty and is reserved for future use.| |zabbix\[lld\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the low-level discovery processing queue.|<|<|Integer.|This item can be used to monitor the low-level discovery processing queue length.<br><br>This item is supported since Zabbix 4.2.0.| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the preprocessing queue.|<|<|Integer.|This item can be used to monitor the preprocessing queue length.<br><br>This item is supported since Zabbix 3.4.0.| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|Time a particular Zabbix process or a group of processes (identified by <type> and <mode>) spent in <state> in percentage. It is calculated for the last minute only.<br><br>If <mode> is Zabbix process number that is not running (for example, with 5 pollers running <mode> is specified to be 6), such an item will turn into unsupported state.<br>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.<br>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.<br>Currently, "busy" means "not sleeping", but in the future additional states might be introduced - waiting for locks, performing database queries, etc.<br>On Linux and most other systems, resolution is 1/100 of a second.|<|<|Percentage of time.<br>Float.|Supported **types** of [server processes](/manual/concepts/server#server_process_types):<br>*alert manager*, *alert syncer*, *alerter*, *availability manager*, *configuration syncer*, *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*<br><br>Supported **types** of [proxy processes](/manual/concepts/proxy#proxy_process_types):<br>*availability manager*, *configuration syncer*, *data sender*, *discoverer*, *heartbeat sender*, *history poller*, *history syncer*, *housekeeper*, *http poller*, *icmp pinger*, *ipmi manager*, *ipmi poller*, *java poller*, *odbs poller*, *poller*, *preprocessing manager*, *preprocessing worker*, *self-monitoring*, *snmp trapper*, *task manager*, *trapper*, *unreachable poller*, *vmware collector*<br><br>Valid **modes** are:<br>*avg* - average value for all processes of a given type (default)<br>*count* - returns number of forks for a given process type, <state> should not be specified<br>*max* - maximum value<br>*min* - minimum value<br>*<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.<br><br>Valid **states** are:<br>*busy* - process is in busy state, for example, processing request (default).<br>*idle* - process is in idle state doing nothing.<br><br>Examples:<br>=> zabbix\[process,poller,avg,busy\] → average time of poller processes spent doing something during the last minute<br>=> zabbix\[process,"icmp pinger",max,busy\] → maximum time spent doing something by any ICMP pinger process during the last minute<br>=> zabbix\[process,"history syncer",2,busy\] → time spent doing something by history syncer number 2 during the last minute<br>=> zabbix\[process,trapper,count\] → amount of currently running trapper processes| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|Information about Zabbix proxy.|<|<|Integer.|**name**: proxy name<br><br>Valid values for **param** are:<br>*lastaccess* - timestamp of last heart beat message received from proxy<br>*delay* - how long 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")<br><br>Example:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>`fuzzytime()` [function](/manual/appendix/functions/history) can be used to check availability of proxies.<br>This item is always processed by Zabbix server regardless of host location (on server or proxy).| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|Number of values in the proxy history table waiting to be sent to the server.|<|<|Integer.|*(not supported on server)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|Number of monitored items in the queue which are delayed at least by <from> seconds but less than by <to> seconds.|<|<|Integer.|**from** - default: 6 seconds<br>**to** - default: infinity<br>[Time-unit symbols](/manual/appendix/suffixes) (s,m,h,d,w) are supported for these parameters.| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix configuration cache.|<|<|Integer (for size); float (for percentage).|**cache**: *buffer*<br><br>Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*pused* mode is supported since Zabbix 4.0.0.| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Required performance of Zabbix server or Zabbix proxy, in new values per second expected.|<|<|Float.|Approximately correlates with "Required server performance, new values per second" in *Reports → [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*.| |zabbix\[stats,<ip>,<port>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal metrics.|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).<br><br>Supported since 4.2.0.| |zabbix\[stats,<ip>,<port>,queue,<from>,<to>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal queue metrics (see `zabbix[queue,<from>,<to>]`).|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>Supported since 4.2.0.| |zabbix\[tcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of the Zabbix trend function cache.|<|<|Integer (for size); float (for percentage).|Valid **parameters** are:<br>*all* - total cache requests (default)<br>*hits* - cache hits<br>*phits* - percentage of cache hits<br>*misses* - cache misses<br>*pmisses* - percentage of cache misses<br>*items* - the number of cached items<br>*requests* - the number of cached requests<br>*pitems* - percentage of cached items from cached items + requests. Low percentage most likely means that the cache size can be reduced.<br><br>Supported since 5.4.0.<br><br>*(not supported on proxy)*| |zabbix\[trends\]|<|<|<|<|<| |<|Number of values stored in the TRENDS table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|Number of values stored in the TRENDS\_UINT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Number of enabled triggers in Zabbix database, with all items enabled on enabled hosts.|<|<|Integer.|*(not supported on proxy)*| |zabbix\[uptime\]|<|<|<|<|<| |<|Uptime of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix value cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*(not supported on proxy)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of Zabbix value cache.|<|<|Integer.<br><br>With the *mode* parameter:<br>0 - normal mode,<br>1 - low memory mode|Valid **parameter** values are:<br>*requests* - total number of requests<br>*hits* - number of cache hits (history values taken from the cache)<br>*misses* - number of cache misses (history values taken from the database)<br>*mode* - value cache operating mode<br><br>This item is supported since Zabbix 2.2.0 and the *mode* parameter since Zabbix 3.0.0.<br>*(not supported on proxy)*<br><br>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.<br><br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |zabbix\[version\]|<|<|<|<|<| |<|Version of Zabbix server or proxy.|<|<|String.|This item is supported since Zabbix 5.0.0.<br><br>Example of return value: 5.0.0beta1| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix vmware cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Statistics and availability of Zabbix write cache.|<|<|<|Specifying <cache> is mandatory.| |<|**Cache**|**Mode**|<|<|<| |^|values|all<br>*(default)*|Total number of values processed by Zabbix server or Zabbix proxy, except unsupported items.|Integer.|Counter.<br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |^|^|float|Number of processed float values.|Integer.|Counter.| |^|^|uint|Number of processed unsigned integer values.|Integer.|Counter.| |^|^|str|Number of processed character/string values.|Integer.|Counter.| |^|^|log|Number of processed log values.|Integer.|Counter.| |^|^|text|Number of processed text values.|Integer.|Counter.| |^|^|not supported|Number of times item processing resulted in item becoming unsupported or keeping that state.|Integer.|Counter.<br>| |^|history|pfree<br>*(default)*|Percentage of free history buffer.|Float.|History cache is used to store item values. A low number indicates performance problems on the database side.| |^|^|free|Size of free history buffer.|Integer.|<| |^|^|total|Total size of history buffer.|Integer.|<| |^|^|used|Size of used history buffer.|Integer.|<| |^|^|pused|Percentage of used history buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|index|pfree<br>*(default)*|Percentage of free history index buffer.|Float.|History index cache is used to index values stored in history cache.<br>*Index* cache is supported since Zabbix 3.0.0.| |^|^|free|Size of free history index history buffer.|Integer.|<| |^|^|total|Total size of history index history buffer.|Integer.|<| |^|^|used|Size of used history index history buffer.|Integer.|<| |^|^|pused|Percentage of used history index buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|trend|pfree<br>*(default)*|Percentage of free trend cache.|Float.|Trend cache stores aggregate for the current hour for all items that receive data.<br>*(not supported on proxy)*| |^|^|free|Size of free trend buffer.|Integer.|*(not supported on proxy)*| |^|^|total|Total size of trend buffer.|Integer.|*(not supported on proxy)*| |^|^|used|Size of used trend buffer.|Integer.|*(not supported on proxy)*| |^|^|pused|Percentage of used trend buffer.|Float.|*(not supported on proxy)*<br><br>*pused* mode is supported since Zabbix 4.0.0.|
zh-cn	#### 支持的检查  -   没有尖括号的参数为常量 - 比如,     `zabbix[host,<type>,available]` 中的'host' 和 'available'。在监控项键值 *原样* 使用它们。 -   “代理端不支持” 的监控项和监控项参数的值只能在主机被服务端监控的情况下收集。反之亦然，“服务端不支持” 的值只能在主机被代理端监控的情况下收集。  |键值|<|<|<|<|<| |---|-|-|-|-|-| |▲|描述|<|<|返回值|注释| |zabbix\[boottime\]|<|<|<|<|<| |<|Zabbix server 或者 Zabbix proxy 进程启动的时间，单位是秒.|<|<|整数.|<| |zabbix\[cluster,discovery,nodes\]|<|<|<|<|<| |<|发现 [高可用集群](/manual/concepts/server/ha) 节点.|<|<|JSON.|这个监控项可以用在 LLD.| |zabbix\[history\]|<|<|<|<|<| |<|存储在 HISTORY 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|存储在 HISTORY\_LOG 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|存储在 HISTORY\_STR 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|存储在 HISTORY\_TEXT 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|存储在 HISTORY\_UINT 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>这个监控项从 Zabbix 1.8.3 开始支持.<br>*(代理端不支持)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|主机上启用的监控项数量 (包含支持的和不支持的) .|<|<|整数.|这个监控项从 Zabbix 3.0.0 开始支持.| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|主机上启用的不支持的监控项数量.|<|<|整数.|这个监控项从 Zabbix 3.0.0 开始支持.\*| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|当前主机的维护状态.|<|<|0 - 主机处于正常状态,<br>1 - 主机处于维护状态，并且在采集数据,<br>2 - 主机处于维护状态，但是不采集数据.|这个监控项总是由 Zabbix 服务端处理，而不管主机当前所处位置(在服务端或代理端上). 代理端将不会接收这个带有配置数据的监控项.<br>第二个参数必须为空，并保留以备将来使用.| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|在 Zabbix 前端中主机所有配置接口的详细信息.|<|<|JSON object.|这个监控项可以被用在 [low-level discovery](/manual/discovery/low_level_discovery/examples/host_interfaces).<br>这个监控项从 Zabbix 3.4.0 开始支持.<br>*(代理端不支持)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|主机上特定类型检查的主接口的可用性.|<|<|0 - 不可用, 1 - 可用, 2 - 未知.|有效 **类型** 是:<br>*agent*, *snmp*, *ipmi*, *jmx*<br><br>监控项的值根据有关主机的 [不可达/不可用](/manual/appendix/items/unreachability)配置参数计算.<br><br>这个监控项从 Zabbix 2.0.0 开始支持.<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|已监控的主机数量.|<|<|整数.|<| |zabbix\[items\]|<|<|<|<|<| |<|已启用的监控项数量 (支持的和不支持的).|<|<|整数.|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|不支持的监控项数量.|<|<|整数.|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|关于Zabbix Java网关的信息.|<|<|如果 <param> 是 *ping*, 则返回 "1" . 可以使用 nodata() 触发器函数检查Java网关可用性.<br><br>如果 <param> 是 *version*, 则返回 Java 网关的版本. 例如: "2.0.0".| **param** 的有效值是:<br>*ping*, *version*<br><br>第二个参数必须为空，并保留以备将来使用.| |zabbix\[lld\_queue\]|<|<|<|<|<| |<|在 LLD 队列中排队的值.|<|<|整数.|这个监控项用来监控 LLD 的队列长度.<br><br>这个监控项从 Zabbix 4.2.0 开始支持.| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|在预处理队列中排队的值的数量.|<|<|整数.|这个监控项用来监控预处理队列的长度.<br><br>这个监控项从 Zabbix 3.4.0 开始支持.| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|一个特定Zabbix进程或一组进程(由 <type> 和 <mode> 标记)在 <state> 的时间，单位是百分比. 它只计算最后一分钟.<br><br>如果 <mode> 是未运行的Zabbix 进程号 (例如, <mode> 被指定为 6 的时候运行 5 个 poller), 这样的监控项将变成不支持的状态.<br>最小值和最大值是指单个进程的使用百分比. 因此，如果在一组3个 poller 中，每个进程的使用率分别为 2、18 和 66,最小值将返回 2,最大值将返回 66.<br>进程报告它们在共享内存中所做的事情，并且自我监控进程则每秒钟都会汇总这些数据. 状态改变(busy/idle)是在变化时记录的 - 因此，一个进程成为 busy 状态时会被记录之后不会改变或更新状态，直到它变成 idle 状态. 这将确保即使完全挂起的进程也将正确地记录为100% busy.<br>目前，"busy" 意味着 "not sleeping"，但在未来可能会引入额外的状态 - 等待锁，执行数据库查询，等等.<br>在 Linux 和大多数系统上，解析度是 1/100 秒.|<|<|时间的百分比.<br>浮点值.| [server processes](/manual/concepts/server#server_process_types)支持的 **类型**:<br>*alert manager*, *alert syncer*, *alerter*, *availability manager*, *configuration syncer*, *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*<br><br>[proxy processes](/manual/concepts/proxy#proxy_process_types)支持的 **类型**:<br>*availability manager*, *configuration syncer*, *data sender*, *discoverer*, *heartbeat sender*, *history poller*, *history syncer*, *housekeeper*, *http poller*, *icmp pinger*, *ipmi manager*, *ipmi poller*, *java poller*, *odbs poller*, *poller*, *preprocessing manager*, *preprocessing worker*, *self-monitoring*, *snmp trapper*, *task manager*, *trapper*, *unreachable poller*, *vmware collector*<br><br>有效的 **modes** 有:<br>*avg* - 给定类型的所有进程的平均值(缺省值)<br>*count* - 返回给定类型进程 fork 出来的数量, <state> 不应该被指定<br>*max* - 最大值<br>*min* - 最小值<br>*<process number>* - 进程数量 (在 1 和 pre-forked 实例之间的数量). 比如, 当有 4 个 trapper 的时候，这个值在 1 和 4 之间.<br><br>有效的 **states** 有:<br>*busy* - 进程处于繁忙状态, 比如, 处理请求(缺省值).<br>*idle* - 进程处于空闲状态什么都不做.<br><br>比如:<br>=> zabbix\[process,poller,avg,busy\] → poller 进程在最后一分钟内执行某项操作的平均时间<br>=> zabbix\[process,"icmp pinger",max,busy\] → 任何 ICMP ping 进程在最后一分钟做某件事所花费的最大时间<br>=> zabbix\[process,"history syncer",2,busy\] → history syncer 2号进程在最后一分钟所花费的时间<br>=> zabbix\[process,trapper,count\] → 当前运行的 trapper 进程的数量| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|Zabbix 代理端的信息.|<|<|整数.|**name**: 代理端名称<br><br> **param** 的有效值有:<br>*lastaccess* - 从代理端上收到的最后一次心跳消息的时间戳<br>*delay* - 采集的值多长时间未发送, 计算方式为 "代理端延迟" (当前代理端的时间与代理端上最老的未发送值的时间戳之间的差值) + ("当前服务端时间" - "代理端最后一次访问时间")<br><br>比如:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>`fuzzytime()` [函数](/manual/appendix/functions/history) 可以用来检测代理端的可用性.<br>这个监控项始终由 Zabbix 服务端处理与主机位置无关(在服务端或者代理端).| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|代理端 history 表中等待发送到服务端的值的数量.|<|<|整数.|*(服务端不支持)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|大于 <from> 的秒数但是小于 <to>秒数的延迟的队列中被监控的监控项数量.|<|<|整数.|**from** - 缺省值: 6 秒<br>**to** - default: 无穷，不限制<br>[Time-unit symbols](/manual/appendix/suffixes) 支持 s,m,h,d,w 这些参数.| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix配置缓存的可用性统计信息.|<|<|整数 (大小); float (百分比).|**cache**: *buffer*<br><br>有效的 **modes** 有:<br>*total* - 总 buffer 大小<br>*free* - 空闲 buffer大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 使用的 buffer大小<br>*pused* - 使用的buffer百分比<br><br>*pused*  模式从 Zabbix 4.0.0 开始支持.| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Zabbix 服务端或者 Zabbix 代理端所需的性能, 以每秒新增的值计算.|<|<|浮点数.|大约与 *报告中的"服务端所需性能，每秒新值"相关 → [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*.| |zabbix\[stats,<ip>,<port>\]|<|<|<|<|<| |<|远程 Zabbix 服务端或者代理端内部监控指标.|<|<|JSON 对象.|**ip** - 远程查询服务端/代理端的IP/DNS/网络掩码列表(缺省是 127.0.0.1)<br>**port** - 远程查询服务端/代理端的端口号(缺省是 10051)<br><br>注意，stats请求将只接受目标实例上'StatsAllowedIP'[server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 参数中列出的地址.<br><br>此监控项返回一组选定的内部指标. 更多信息参见 [Zabbix 远程监控的统计数据](/manual/appendix/items/remote_stats#exposed_metrics).<br><br>从 4.2.0 开始支持.| |zabbix\[stats,<ip>,<port>,queue,<from>,<to>\]|<|<|<|<|<| |<|远程 Zabbix 服务端或者代理端内部队列指标(另见 `zabbix[queue,<from>,<to>]`).|<|<|JSON 对象.|**ip** - 远程查询服务端/代理端的IP/DNS/网络掩码列表(缺省是 127.0.0.1)<br>**port** - 远程查询服务端/代理端的端口号(缺省是 10051)<br>**from** - 最少的延迟 (缺省是 6 秒)<br>**to** - 最多的延迟 (缺省是 infinity)<br><br>注意，stats请求将只接受目标实例上'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)  参数中列出的地址.<br><br>从 4.2.0 开始支持.| |zabbix\[tcache,cache,<parameter>\]|<|<|<|<|<| |<|Zabbix趋势功能缓存的有效性统计.|<|<|整数 (大小); 浮点数 (百分比).|有效 **parameters** 是:<br>*all* - 总缓存请求(缺省值)<br>*hits* - 缓存命中<br>*phits* - 缓存命中的百分比<br>*misses* - 缓存未命中<br>*pmisses* - 缓存未命中的百分比<br>*items* - 缓存的监控项数量<br>*requests* - 缓存请求的监控项数量<br>*pitems* - 缓存监控项/(缓存监控项+请求)的百分比. 较低的百分比很可能意味着可以减少缓存大小.<br><br>从 5.4.0 开始支持.<br><br>*(代理端不支持)*| |zabbix\[trends\]|<|<|<|<|<| |<|存储在 TRENDS 表中的值的数量.|<|<|整数.|该监控项自Zabbix 6.0以来已弃用.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|存储在 TRENDS\_UINT 表中的值的数量.|<|<|整数.|该监控项自Zabbix 6.0以来已弃用.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>这个监控项从 Zabbix 1.8.3 开始支持.<br>*(代理端不支持)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Zabbix 数据库中已启用触发器的数量，在已启用的主机上启用所有监控项.|<|<|整数.|*(代理端不支持)*| |zabbix\[uptime\]|<|<|<|<|<| |<|Zabbix 服务端或者 Zabbix 代理端进程启动的时间，单位是秒.|<|<|整数.|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix 值缓存的可用性统计信息.|<|<|整数 (大小); 浮点数 (百分比).|有效 **modes** 是:<br>*total* -  buffer 总大小<br>*free* - 空闲 buffer 的大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 已用的buffer<br>*pused* - 已用的buffer百分比<br><br>*(代理端不支持)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Zabbix值缓存的有效性统计.|<|<|整数.<br><br> *mode* 参数有:<br>0 - 正常模式,<br>1 - 低内存模式| **parameter** 有效值有:<br>*requests* - 请求的总数<br>*hits* - 缓存命中数量 (从缓存中获取的历史值)<br>*misses* - 缓存未命中数量 (从数据库中获取的历史值)<br>*mode* - 缓存操作模式的值<br><br>这个监控项从 Zabbix 2.2.0 开始支持，*mode* 参数从 Zabbix 3.0.0.<br>*(代理端不支持)*<br><br>一旦开启低内存模式，缓存值将保持这种状态24小时，即使触发此模式的问题被更快地解决.<br><br>您可以将此键值与 *Change per second* 预处理步骤一起使用，以便获得每秒统计值.| |zabbix\[version\]|<|<|<|<|<| |<|Zabbix 服务端或者代理端的版本.|<|<|字符串.|这个监控项从 Zabbix 5.0.0 开始支持.<br><br>比如返回这样的值: 5.0.0beta1| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix vmware 缓存可用性统计信息.|<|<| 整数(大小); 浮点数 (百分比).| **modes** 有效值:<br>*total* - buffer 的总大小<br>*free* - 空闲 buffer 的大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 已用的 buffer 大小<br>*pused* - 已用的 buffer 百分比| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix 写缓存的可用性和有效性统计.|<|<|<|<cache> 必须指定.| |<|**Cache**|**Mode**|<|<|<| |^|values|all<br>*(缺省值)*|Zabbix 服务端或者代理端处理的值的总数，不支持的监控项除外.|整数.|计数器.<br>你可以将此键值与 *Change per second* 预处理步骤一起使用，以便获得每秒统计值.| |^|^|float|处理的浮点值的数量.|整数.|计数器.| |^|^|uint|处理的无符号整数值的数量.|整数.|计数器.| |^|^|str|处理的字符/字符串的数量.|整数.|计数器.| |^|^|log|处理的日志值的数量.|整数.|计数器.| |^|^|text|处理的文本值的数量.|整数.|计数器.| |^|^|not supported|监控项处理导致监控项变得不受支持或保持该状态的次数.|整数.|计数器.<br>| |^|history|pfree<br>*(缺省值)*|可用历史 buffer 的百分比.|浮点数.|用于存储历史缓存的监控项值. 如果数值较低，则表明数据库端存在性能问题.| |^|^|free|空闲历史 buffer 大小.|整数.|<| |^|^|total|总的历史 buffer 大小.|整数.|<| |^|^|used|已用的历史 buffer 大小.|整数.|<| |^|^|pused|已用的历史 buffer 百分比.|浮点数.|*pused* 模式从 Zabbix 4.0.0 开始支持.| |^|index|pfree<br>*(缺省值)*|可用历史索引缓冲区的百分比.|浮点数.|历史索引缓存用于对存储在历史缓存中的值进行索引.<br>*Index* 缓存从 Zabbix 3.0.0 开始支持.| |^|^|free|空闲历史索引历史缓冲区的大小.|整数.|<| |^|^|total|总的历史索引历史缓冲区的大小.|整数.|<| |^|^|used|已经使用的历史索引历史缓冲区的大小.|整数.|<| |^|^|pused|已经使用的历史索引历史缓冲区的百分比.|浮点数.|*pused* 模式从 Zabbix 4.0.0 开始支持.| |^|trend|pfree<br>*(缺省值)*|可用趋势缓存的百分比.|浮点数.|趋势缓存存储当前小时内所有接收数据的监控项的聚合.<br>*(代理端不支持)*| |^|^|free|可用趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|total|总的趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|used|已用趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|pused|已用趋势缓存的百分比.|浮点数.|*(代理端不支持)*<br><br>*pused* 模式从 Zabbix 4.0.0 开始支持.|

en-us	#### Supported checks  -   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 gathered if the host is monitored by server. And     vice versa, values "not supported on server" can only be gathered if     the host is monitored by proxy.  |Key|<|<|<|<|<| |---|-|-|-|-|-| |▲|Description|<|<|Return value|Comments| |zabbix\[boottime\]|<|<|<|<|<| |<|Startup time of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[cluster,discovery,nodes\]|<|<|<|<|<| |<|Discover [high availability cluster](/manual/concepts/server/ha) nodes.|<|<|JSON.|This item can be used in low-level discovery.| |zabbix\[history\]|<|<|<|<|<| |<|Number of values stored in the HISTORY table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_LOG table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_STR table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_TEXT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|Number of values stored in the HISTORY\_UINT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported) on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|Number of enabled unsupported items on the host.|<|<|Integer.|This item is supported since Zabbix 3.0.0.\*| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|Current maintenance status of a host.|<|<|0 - host in normal state,<br>1 - host in maintenance with data collection,<br>2 - host in maintenance without data collection.|This item is always processed by Zabbix server regardless of host location (on server or proxy). The proxy will not receive this item with configuration data.<br>The second parameter must be empty and is reserved for future use.| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|Details of all configured interfaces of the host in Zabbix frontend.|<|<|JSON object.|This item can be used in [low-level discovery](/manual/discovery/low_level_discovery/examples/host_interfaces).<br>This item is supported since Zabbix 3.4.0.<br>*(not supported on proxy)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|Availability of the main interface of a particular type of checks on the host.|<|<|0 - not available, 1 - available, 2 - unknown.|Valid **types** are:<br>*agent*, *snmp*, *ipmi*, *jmx*<br><br>The item value is calculated according to configuration parameters regarding host [unreachability/unavailability](/manual/appendix/items/unreachability).<br><br>This item is supported since Zabbix 2.0.0.<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|Number of monitored hosts.|<|<|Integer.|<| |zabbix\[items\]|<|<|<|<|<| |<|Number of enabled items (supported and not supported).|<|<|Integer.|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|Number of not supported items.|<|<|Integer.|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|Information about Zabbix Java gateway.|<|<|If <param> is *ping*, "1" is returned. Can be used to check Java gateway availability using nodata() trigger function.<br><br>If <param> is *version*, version of Java gateway is returned. Example: "2.0.0".|Valid values for **param** are:<br>*ping*, *version*<br><br>Second parameter must be empty and is reserved for future use.| |zabbix\[lld\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the low-level discovery processing queue.|<|<|Integer.|This item can be used to monitor the low-level discovery processing queue length.<br><br>This item is supported since Zabbix 4.2.0.| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|Count of values enqueued in the preprocessing queue.|<|<|Integer.|This item can be used to monitor the preprocessing queue length.<br><br>This item is supported since Zabbix 3.4.0.| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|Time a particular Zabbix process or a group of processes (identified by <type> and <mode>) spent in <state> in percentage. It is calculated for the last minute only.<br><br>If <mode> is Zabbix process number that is not running (for example, with 5 pollers running <mode> is specified to be 6), such an item will turn into unsupported state.<br>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.<br>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.<br>Currently, "busy" means "not sleeping", but in the future additional states might be introduced - waiting for locks, performing database queries, etc.<br>On Linux and most other systems, resolution is 1/100 of a second.|<|<|Percentage of time.<br>Float.|Supported **types** of [server processes](/manual/concepts/server#server_process_types):<br>*alert manager*, *alert syncer*, *alerter*, *availability manager*, *configuration syncer*, *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*<br><br>Supported **types** of [proxy processes](/manual/concepts/proxy#proxy_process_types):<br>*availability manager*, *configuration syncer*, *data sender*, *discoverer*, *heartbeat sender*, *history poller*, *history syncer*, *housekeeper*, *http poller*, *icmp pinger*, *ipmi manager*, *ipmi poller*, *java poller*, *odbs poller*, *poller*, *preprocessing manager*, *preprocessing worker*, *self-monitoring*, *snmp trapper*, *task manager*, *trapper*, *unreachable poller*, *vmware collector*<br><br>Valid **modes** are:<br>*avg* - average value for all processes of a given type (default)<br>*count* - returns number of forks for a given process type, <state> should not be specified<br>*max* - maximum value<br>*min* - minimum value<br>*<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.<br><br>Valid **states** are:<br>*busy* - process is in busy state, for example, processing request (default).<br>*idle* - process is in idle state doing nothing.<br><br>Examples:<br>=> zabbix\[process,poller,avg,busy\] → average time of poller processes spent doing something during the last minute<br>=> zabbix\[process,"icmp pinger",max,busy\] → maximum time spent doing something by any ICMP pinger process during the last minute<br>=> zabbix\[process,"history syncer",2,busy\] → time spent doing something by history syncer number 2 during the last minute<br>=> zabbix\[process,trapper,count\] → amount of currently running trapper processes| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|Information about Zabbix proxy.|<|<|Integer.|**name**: proxy name<br><br>Valid values for **param** are:<br>*lastaccess* - timestamp of last heart beat message received from proxy<br>*delay* - how long 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")<br><br>Example:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>`fuzzytime()` [function](/manual/appendix/functions/history) can be used to check availability of proxies.<br>This item is always processed by Zabbix server regardless of host location (on server or proxy).| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|Number of values in the proxy history table waiting to be sent to the server.|<|<|Integer.|*(not supported on server)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|Number of monitored items in the queue which are delayed at least by <from> seconds but less than by <to> seconds.|<|<|Integer.|**from** - default: 6 seconds<br>**to** - default: infinity<br>[Time-unit symbols](/manual/appendix/suffixes) (s,m,h,d,w) are supported for these parameters.| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix configuration cache.|<|<|Integer (for size); float (for percentage).|**cache**: *buffer*<br><br>Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*pused* mode is supported since Zabbix 4.0.0.| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Required performance of Zabbix server or Zabbix proxy, in new values per second expected.|<|<|Float.|Approximately correlates with "Required server performance, new values per second" in *Reports → [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*.| |zabbix\[stats,<ip>,<port>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal metrics.|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).<br><br>Supported since 4.2.0.| |zabbix\[stats,<ip>,<port>,queue,<from>,<to>\]|<|<|<|<|<| |<|Remote Zabbix server or proxy internal queue metrics (see `zabbix[queue,<from>,<to>]`).|<|<|JSON object.|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)<br><br>Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>Supported since 4.2.0.| |zabbix\[tcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of the Zabbix trend function cache.|<|<|Integer (for size); float (for percentage).|Valid **parameters** are:<br>*all* - total cache requests (default)<br>*hits* - cache hits<br>*phits* - percentage of cache hits<br>*misses* - cache misses<br>*pmisses* - percentage of cache misses<br>*items* - the number of cached items<br>*requests* - the number of cached requests<br>*pitems* - percentage of cached items from cached items + requests. Low percentage most likely means that the cache size can be reduced.<br><br>Supported since 5.4.0.<br><br>*(not supported on proxy)*| |zabbix\[trends\]|<|<|<|<|<| |<|Number of values stored in the TRENDS table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>*(not supported on proxy)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|Number of values stored in the TRENDS\_UINT table.|<|<|Integer.|This item is deprecated since Zabbix 6.0.<br>Do not use if MySQL InnoDB, Oracle or PostgreSQL is used!<br>This item is supported since Zabbix 1.8.3.<br>*(not supported on proxy)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Number of enabled triggers in Zabbix database, with all items enabled on enabled hosts.|<|<|Integer.|*(not supported on proxy)*| |zabbix\[uptime\]|<|<|<|<|<| |<|Uptime of Zabbix server or Zabbix proxy process in seconds.|<|<|Integer.|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix value cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer<br><br>*(not supported on proxy)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Effectiveness statistics of Zabbix value cache.|<|<|Integer.<br><br>With the *mode* parameter:<br>0 - normal mode,<br>1 - low memory mode|Valid **parameter** values are:<br>*requests* - total number of requests<br>*hits* - number of cache hits (history values taken from the cache)<br>*misses* - number of cache misses (history values taken from the database)<br>*mode* - value cache operating mode<br><br>This item is supported since Zabbix 2.2.0 and the *mode* parameter since Zabbix 3.0.0.<br>*(not supported on proxy)*<br><br>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.<br><br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |zabbix\[version\]|<|<|<|<|<| |<|Version of Zabbix server or proxy.|<|<|String.|This item is supported since Zabbix 5.0.0.<br><br>Example of return value: 5.0.0beta1| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Availability statistics of Zabbix vmware cache.|<|<|Integer (for size); float (for percentage).|Valid **modes** are:<br>*total* - total size of buffer<br>*free* - size of free buffer<br>*pfree* - percentage of free buffer<br>*used* - size of used buffer<br>*pused* - percentage of used buffer| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Statistics and availability of Zabbix write cache.|<|<|<|Specifying <cache> is mandatory.| |<|**Cache**|**Mode**|<|<|<| |^|values|all<br>*(default)*|Total number of values processed by Zabbix server or Zabbix proxy, except unsupported items.|Integer.|Counter.<br>You may use this key with the *Change per second* preprocessing step in order to get values per second statistics.| |^|^|float|Number of processed float values.|Integer.|Counter.| |^|^|uint|Number of processed unsigned integer values.|Integer.|Counter.| |^|^|str|Number of processed character/string values.|Integer.|Counter.| |^|^|log|Number of processed log values.|Integer.|Counter.| |^|^|text|Number of processed text values.|Integer.|Counter.| |^|^|not supported|Number of times item processing resulted in item becoming unsupported or keeping that state.|Integer.|Counter.<br>| |^|history|pfree<br>*(default)*|Percentage of free history buffer.|Float.|History cache is used to store item values. A low number indicates performance problems on the database side.| |^|^|free|Size of free history buffer.|Integer.|<| |^|^|total|Total size of history buffer.|Integer.|<| |^|^|used|Size of used history buffer.|Integer.|<| |^|^|pused|Percentage of used history buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|index|pfree<br>*(default)*|Percentage of free history index buffer.|Float.|History index cache is used to index values stored in history cache.<br>*Index* cache is supported since Zabbix 3.0.0.| |^|^|free|Size of free history index history buffer.|Integer.|<| |^|^|total|Total size of history index history buffer.|Integer.|<| |^|^|used|Size of used history index history buffer.|Integer.|<| |^|^|pused|Percentage of used history index buffer.|Float.|*pused* mode is supported since Zabbix 4.0.0.| |^|trend|pfree<br>*(default)*|Percentage of free trend cache.|Float.|Trend cache stores aggregate for the current hour for all items that receive data.<br>*(not supported on proxy)*| |^|^|free|Size of free trend buffer.|Integer.|*(not supported on proxy)*| |^|^|total|Total size of trend buffer.|Integer.|*(not supported on proxy)*| |^|^|used|Size of used trend buffer.|Integer.|*(not supported on proxy)*| |^|^|pused|Percentage of used trend buffer.|Float.|*(not supported on proxy)*<br><br>*pused* mode is supported since Zabbix 4.0.0.|
zh-cn	#### 支持的检查  -   没有尖括号的参数为常量 - 比如,     `zabbix[host,<type>,available]` 中的'host' 和 'available'。在监控项键值 *原样* 使用它们。 -   “代理端不支持” 的监控项和监控项参数的值只能在主机被服务端监控的情况下收集。反之亦然，“服务端不支持” 的值只能在主机被代理端监控的情况下收集。  |键值|<|<|<|<|<| |---|-|-|-|-|-| |▲|描述|<|<|返回值|注释| |zabbix\[boottime\]|<|<|<|<|<| |<|Zabbix server 或者 Zabbix proxy 进程启动的时间，单位是秒.|<|<|整数.|<| |zabbix\[cluster,discovery,nodes\]|<|<|<|<|<| |<|发现 [高可用集群](/manual/concepts/server/ha) 节点.|<|<|JSON.|这个监控项可以用在 LLD.| |zabbix\[history\]|<|<|<|<|<| |<|存储在 HISTORY 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_log\]|<|<|<|<|<| |<|存储在 HISTORY\_LOG 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_str\]|<|<|<|<|<| |<|存储在 HISTORY\_STR 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_text\]|<|<|<|<|<| |<|存储在 HISTORY\_TEXT 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[history\_uint\]|<|<|<|<|<| |<|存储在 HISTORY\_UINT 表中的值的数量.|<|<|整数.|这个监控项从 Zabbix 6.0 开始已经废弃.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>这个监控项从 Zabbix 1.8.3 开始支持.<br>*(代理端不支持)*| |zabbix\[host,,items\]|<|<|<|<|<| |<|主机上启用的监控项数量 (包含支持的和不支持的) .|<|<|整数.|这个监控项从 Zabbix 3.0.0 开始支持.| |zabbix\[host,,items\_unsupported\]|<|<|<|<|<| |<|主机上启用的不支持的监控项数量.|<|<|整数.|这个监控项从 Zabbix 3.0.0 开始支持.\*| |zabbix\[host,,maintenance\]|<|<|<|<|<| |<|当前主机的维护状态.|<|<|0 - 主机处于正常状态,<br>1 - 主机处于维护状态，并且在采集数据,<br>2 - 主机处于维护状态，但是不采集数据.|这个监控项总是由 Zabbix 服务端处理，而不管主机当前所处位置(在服务端或代理端上). 代理端将不会接收这个带有配置数据的监控项.<br>第二个参数必须为空，并保留以备将来使用.| |zabbix\[host,discovery,interfaces\]|<|<|<|<|<| |<|在 Zabbix 前端中主机所有配置接口的详细信息.|<|<|JSON object.|这个监控项可以被用在 [low-level discovery](/manual/discovery/low_level_discovery/examples/host_interfaces).<br>这个监控项从 Zabbix 3.4.0 开始支持.<br>*(代理端不支持)*| |zabbix\[host,<type>,available\]|<|<|<|<|<| |<|主机上特定类型检查的主接口的可用性.|<|<|0 - 不可用, 1 - 可用, 2 - 未知.|有效 **类型** 是:<br>*agent*, *snmp*, *ipmi*, *jmx*<br><br>监控项的值根据有关主机的 [不可达/不可用](/manual/appendix/items/unreachability)配置参数计算.<br><br>这个监控项从 Zabbix 2.0.0 开始支持.<br>| |zabbix\[hosts\]|<|<|<|<|<| |<|已监控的主机数量.|<|<|整数.|<| |zabbix\[items\]|<|<|<|<|<| |<|已启用的监控项数量 (支持的和不支持的).|<|<|整数.|<| |zabbix\[items\_unsupported\]|<|<|<|<|<| |<|不支持的监控项数量.|<|<|整数.|<| |zabbix\[java,,<param>\]|<|<|<|<|<| |<|关于Zabbix Java网关的信息.|<|<|如果 <param> 是 *ping*, 则返回 "1" . 可以使用 nodata() 触发器函数检查Java网关可用性.<br><br>如果 <param> 是 *version*, 则返回 Java 网关的版本. 例如: "2.0.0".| **param** 的有效值是:<br>*ping*, *version*<br><br>第二个参数必须为空，并保留以备将来使用.| |zabbix\[lld\_queue\]|<|<|<|<|<| |<|在 LLD 队列中排队的值.|<|<|整数.|这个监控项用来监控 LLD 的队列长度.<br><br>这个监控项从 Zabbix 4.2.0 开始支持.| |zabbix\[preprocessing\_queue\]|<|<|<|<|<| |<|在预处理队列中排队的值的数量.|<|<|整数.|这个监控项用来监控预处理队列的长度.<br><br>这个监控项从 Zabbix 3.4.0 开始支持.| |zabbix\[process,<type>,<mode>,<state>\]|<|<|<|<|<| |<|一个特定Zabbix进程或一组进程(由 <type> 和 <mode> 标记)在 <state> 的时间，单位是百分比. 它只计算最后一分钟.<br><br>如果 <mode> 是未运行的Zabbix 进程号 (例如, <mode> 被指定为 6 的时候运行 5 个 poller), 这样的监控项将变成不支持的状态.<br>最小值和最大值是指单个进程的使用百分比. 因此，如果在一组3个 poller 中，每个进程的使用率分别为 2、18 和 66,最小值将返回 2,最大值将返回 66.<br>进程报告它们在共享内存中所做的事情，并且自我监控进程则每秒钟都会汇总这些数据. 状态改变(busy/idle)是在变化时记录的 - 因此，一个进程成为 busy 状态时会被记录之后不会改变或更新状态，直到它变成 idle 状态. 这将确保即使完全挂起的进程也将正确地记录为100% busy.<br>目前，"busy" 意味着 "not sleeping"，但在未来可能会引入额外的状态 - 等待锁，执行数据库查询，等等.<br>在 Linux 和大多数系统上，解析度是 1/100 秒.|<|<|时间的百分比.<br>浮点值.| [server processes](/manual/concepts/server#server_process_types)支持的 **类型**:<br>*alert manager*, *alert syncer*, *alerter*, *availability manager*, *configuration syncer*, *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*<br><br>[proxy processes](/manual/concepts/proxy#proxy_process_types)支持的 **类型**:<br>*availability manager*, *configuration syncer*, *data sender*, *discoverer*, *heartbeat sender*, *history poller*, *history syncer*, *housekeeper*, *http poller*, *icmp pinger*, *ipmi manager*, *ipmi poller*, *java poller*, *odbs poller*, *poller*, *preprocessing manager*, *preprocessing worker*, *self-monitoring*, *snmp trapper*, *task manager*, *trapper*, *unreachable poller*, *vmware collector*<br><br>有效的 **modes** 有:<br>*avg* - 给定类型的所有进程的平均值(缺省值)<br>*count* - 返回给定类型进程 fork 出来的数量, <state> 不应该被指定<br>*max* - 最大值<br>*min* - 最小值<br>*<process number>* - 进程数量 (在 1 和 pre-forked 实例之间的数量). 比如, 当有 4 个 trapper 的时候，这个值在 1 和 4 之间.<br><br>有效的 **states** 有:<br>*busy* - 进程处于繁忙状态, 比如, 处理请求(缺省值).<br>*idle* - 进程处于空闲状态什么都不做.<br><br>比如:<br>=> zabbix\[process,poller,avg,busy\] → poller 进程在最后一分钟内执行某项操作的平均时间<br>=> zabbix\[process,"icmp pinger",max,busy\] → 任何 ICMP ping 进程在最后一分钟做某件事所花费的最大时间<br>=> zabbix\[process,"history syncer",2,busy\] → history syncer 2号进程在最后一分钟所花费的时间<br>=> zabbix\[process,trapper,count\] → 当前运行的 trapper 进程的数量| |zabbix\[proxy,<name>,<param>\]|<|<|<|<|<| |<|Zabbix 代理端的信息.|<|<|整数.|**name**: 代理端名称<br><br> **param** 的有效值有:<br>*lastaccess* - 从代理端上收到的最后一次心跳消息的时间戳<br>*delay* - 采集的值多长时间未发送, 计算方式为 "代理端延迟" (当前代理端的时间与代理端上最老的未发送值的时间戳之间的差值) + ("当前服务端时间" - "代理端最后一次访问时间")<br><br>比如:<br>=> zabbix\[proxy,"Germany",lastaccess\]<br><br>`fuzzytime()` [函数](/manual/appendix/functions/history) 可以用来检测代理端的可用性.<br>这个监控项始终由 Zabbix 服务端处理与主机位置无关(在服务端或者代理端).| |zabbix\[proxy\_history\]|<|<|<|<|<| |<|代理端 history 表中等待发送到服务端的值的数量.|<|<|整数.|*(服务端不支持)*| |zabbix\[queue,<from>,<to>\]|<|<|<|<|<| |<|大于 <from> 的秒数但是小于 <to>秒数的延迟的队列中被监控的监控项数量.|<|<|整数.|**from** - 缺省值: 6 秒<br>**to** - default: 无穷，不限制<br>[Time-unit symbols](/manual/appendix/suffixes) 支持 s,m,h,d,w 这些参数.| |zabbix\[rcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix配置缓存的可用性统计信息.|<|<|整数 (大小); float (百分比).|**cache**: *buffer*<br><br>有效的 **modes** 有:<br>*total* - 总 buffer 大小<br>*free* - 空闲 buffer大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 使用的 buffer大小<br>*pused* - 使用的buffer百分比<br><br>*pused*  模式从 Zabbix 4.0.0 开始支持.| |zabbix\[requiredperformance\]|<|<|<|<|<| |<|Zabbix 服务端或者 Zabbix 代理端所需的性能, 以每秒新增的值计算.|<|<|浮点数.|大约与 *报告中的"服务端所需性能，每秒新值"相关 → [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*.| |zabbix\[stats,<ip>,<port>\]|<|<|<|<|<| |<|远程 Zabbix 服务端或者代理端内部监控指标.|<|<|JSON 对象.|**ip** - 远程查询服务端/代理端的IP/DNS/网络掩码列表(缺省是 127.0.0.1)<br>**port** - 远程查询服务端/代理端的端口号(缺省是 10051)<br><br>注意，stats请求将只接受目标实例上'StatsAllowedIP'[server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 参数中列出的地址.<br><br>此监控项返回一组选定的内部指标. 更多信息参见 [Zabbix 远程监控的统计数据](/manual/appendix/items/remote_stats#exposed_metrics).<br><br>从 4.2.0 开始支持.| |zabbix\[stats,<ip>,<port>,queue,<from>,<to>\]|<|<|<|<|<| |<|远程 Zabbix 服务端或者代理端内部队列指标(另见 `zabbix[queue,<from>,<to>]`).|<|<|JSON 对象.|**ip** - 远程查询服务端/代理端的IP/DNS/网络掩码列表(缺省是 127.0.0.1)<br>**port** - 远程查询服务端/代理端的端口号(缺省是 10051)<br>**from** - 最少的延迟 (缺省是 6 秒)<br>**to** - 最多的延迟 (缺省是 infinity)<br><br>注意，stats请求将只接受目标实例上'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)  参数中列出的地址.<br><br>从 4.2.0 开始支持.| |zabbix\[tcache,cache,<parameter>\]|<|<|<|<|<| |<|Zabbix趋势功能缓存的有效性统计.|<|<|整数 (大小); 浮点数 (百分比).|有效 **parameters** 是:<br>*all* - 总缓存请求(缺省值)<br>*hits* - 缓存命中<br>*phits* - 缓存命中的百分比<br>*misses* - 缓存未命中<br>*pmisses* - 缓存未命中的百分比<br>*items* - 缓存的监控项数量<br>*requests* - 缓存请求的监控项数量<br>*pitems* - 缓存监控项/(缓存监控项+请求)的百分比. 较低的百分比很可能意味着可以减少缓存大小.<br><br>从 5.4.0 开始支持.<br><br>*(代理端不支持)*| |zabbix\[trends\]|<|<|<|<|<| |<|存储在 TRENDS 表中的值的数量.|<|<|整数.|该监控项自Zabbix 6.0以来已弃用.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>*(代理端不支持)*| |zabbix\[trends\_uint\]|<|<|<|<|<| |<|存储在 TRENDS\_UINT 表中的值的数量.|<|<|整数.|该监控项自Zabbix 6.0以来已弃用.<br>如果使用了MySQL InnoDB, Oracle 或者 PostgreSQL 不要使用这个监控项!<br>这个监控项从 Zabbix 1.8.3 开始支持.<br>*(代理端不支持)*| |zabbix\[triggers\]|<|<|<|<|<| |<|Zabbix 数据库中已启用触发器的数量，在已启用的主机上启用所有监控项.|<|<|整数.|*(代理端不支持)*| |zabbix\[uptime\]|<|<|<|<|<| |<|Zabbix 服务端或者 Zabbix 代理端进程启动的时间，单位是秒.|<|<|整数.|<| |zabbix\[vcache,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix 值缓存的可用性统计信息.|<|<|整数 (大小); 浮点数 (百分比).|有效 **modes** 是:<br>*total* -  buffer 总大小<br>*free* - 空闲 buffer 的大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 已用的buffer<br>*pused* - 已用的buffer百分比<br><br>*(代理端不支持)*| |zabbix\[vcache,cache,<parameter>\]|<|<|<|<|<| |<|Zabbix值缓存的有效性统计.|<|<|整数.<br><br> *mode* 参数有:<br>0 - 正常模式,<br>1 - 低内存模式| **parameter** 有效值有:<br>*requests* - 请求的总数<br>*hits* - 缓存命中数量 (从缓存中获取的历史值)<br>*misses* - 缓存未命中数量 (从数据库中获取的历史值)<br>*mode* - 缓存操作模式的值<br><br>这个监控项从 Zabbix 2.2.0 开始支持，*mode* 参数从 Zabbix 3.0.0.<br>*(代理端不支持)*<br><br>一旦开启低内存模式，缓存值将保持这种状态24小时，即使触发此模式的问题被更快地解决.<br><br>您可以将此键值与 *Change per second* 预处理步骤一起使用，以便获得每秒统计值.| |zabbix\[version\]|<|<|<|<|<| |<|Zabbix 服务端或者代理端的版本.|<|<|字符串.|这个监控项从 Zabbix 5.0.0 开始支持.<br><br>比如返回这样的值: 5.0.0beta1| |zabbix\[vmware,buffer,<mode>\]|<|<|<|<|<| |<|Zabbix vmware 缓存可用性统计信息.|<|<| 整数(大小); 浮点数 (百分比).| **modes** 有效值:<br>*total* - buffer 的总大小<br>*free* - 空闲 buffer 的大小<br>*pfree* - 空闲 buffer 的百分比<br>*used* - 已用的 buffer 大小<br>*pused* - 已用的 buffer 百分比| |zabbix\[wcache,<cache>,<mode>\]|<|<|<|<|<| |<|Zabbix 写缓存的可用性和有效性统计.|<|<|<|<cache> 必须指定.| |<|**Cache**|**Mode**|<|<|<| |^|values|all<br>*(缺省值)*|Zabbix 服务端或者代理端处理的值的总数，不支持的监控项除外.|整数.|计数器.<br>你可以将此键值与 *Change per second* 预处理步骤一起使用，以便获得每秒统计值.| |^|^|float|处理的浮点值的数量.|整数.|计数器.| |^|^|uint|处理的无符号整数值的数量.|整数.|计数器.| |^|^|str|处理的字符/字符串的数量.|整数.|计数器.| |^|^|log|处理的日志值的数量.|整数.|计数器.| |^|^|text|处理的文本值的数量.|整数.|计数器.| |^|^|not supported|监控项处理导致监控项变得不受支持或保持该状态的次数.|整数.|计数器.<br>| |^|history|pfree<br>*(缺省值)*|可用历史 buffer 的百分比.|浮点数.|用于存储历史缓存的监控项值. 如果数值较低，则表明数据库端存在性能问题.| |^|^|free|空闲历史 buffer 大小.|整数.|<| |^|^|total|总的历史 buffer 大小.|整数.|<| |^|^|used|已用的历史 buffer 大小.|整数.|<| |^|^|pused|已用的历史 buffer 百分比.|浮点数.|*pused* 模式从 Zabbix 4.0.0 开始支持.| |^|index|pfree<br>*(缺省值)*|可用历史索引缓冲区的百分比.|浮点数.|历史索引缓存用于对存储在历史缓存中的值进行索引.<br>*Index* 缓存从 Zabbix 3.0.0 开始支持.| |^|^|free|空闲历史索引历史缓冲区的大小.|整数.|<| |^|^|total|总的历史索引历史缓冲区的大小.|整数.|<| |^|^|used|已经使用的历史索引历史缓冲区的大小.|整数.|<| |^|^|pused|已经使用的历史索引历史缓冲区的百分比.|浮点数.|*pused* 模式从 Zabbix 4.0.0 开始支持.| |^|trend|pfree<br>*(缺省值)*|可用趋势缓存的百分比.|浮点数.|趋势缓存存储当前小时内所有接收数据的监控项的聚合.<br>*(代理端不支持)*| |^|^|free|可用趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|total|总的趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|used|已用趋势缓存的大小.|整数.|*(代理端不支持)*| |^|^|pused|已用趋势缓存的百分比.|浮点数.|*(代理端不支持)*<br><br>*pused* 模式从 Zabbix 4.0.0 开始支持.|

en-us	##### Supported checks  The table below describes in-built items that are supported in IPMI agent checks.  |Item key|<|<|<| |--|--|------|------| |▲|Description|Return value|Comments| |ipmi.get|<|<|<| |<|IPMI-sensor related information.|JSON object|This item can be used for the [discovery of IPMI sensors](/manual/discovery/low_level_discovery/examples/ipmi_sensors#overview).<br>Supported since Zabbix 5.0.0.|
zh-cn	##### 支持的检查  下表描述了 IPMI 代理检查中支持的内置监控项。  |监控项键|<|<|<| |--|--|------|------| |▲|描述|返回值|注释| |ipmi.get|<|<|<| |<|IPMI 传感器相关信息。|JSON 对象|此监控项可用于 [IPMI 传感器的发现](/manual/discovery/low_level_discovery/examples/ipmi_sensors#overview)。<br>从 Zabbix 5.0.0 开始支持 .|

en-us	### Supported DB versions check  Zabbix [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) will now check the database version before launch and will not start if the version is out of the supported range. It is possible to turn off this check by modifying AllowUnsupportedDBVersions configuration parameter, but this approach is not recommended. The list of [officially supported database versions](/manual/installation/requirements#Software) has been updated to exclude databases that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.  
zh-cn	### Bulk processing for Prometheus metrics  Bulk processing of dependent items has been introduced in the preprocessing  queue to improve the performance of retrieving Prometheus metrics.  See [Prometheus checks](/manual/config/items/itemtypes/prometheus#bulk-processing) for more details.  

en-us	#### Supported item keys  The table provides details on the item keys that you can use with Zabbix agent items grouped by the item family.  See also:  -   [Items supported by     platform](/manual/appendix/items/supported_by_platform) -   [Item keys supported by Zabbix agent     2](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) -   [Item keys specific for Windows     agent](/manual/config/items/itemtypes/zabbix_agent/win_keys) -   [Minimum permission level for Windows agent     items](/manual/appendix/items/win_permissions)
zh-cn	#### 支持的监控项  下表提供了可用的Zabbix agent 监控项键值的详细信息。  另请参阅  -   [各平台支持的监控项](/manual/appendix/items/supported_by_platform) -   [ Zabbix agent  2支持的监控键值](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) -   [Windows 客户端指定的监控键值](/manual/config/items/itemtypes/zabbix_agent/win_keys) -   [最低权限级别Windows 客户端监控项](/manual/appendix/items/win_permissions)

en-us	#### Supported item keys  The table provides details on the item keys that you can use with Zabbix agent items.  See also:  -   [Items supported by     platform](/manual/appendix/items/supported_by_platform) -   [Item keys supported by Zabbix agent     2](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) -   [Item keys specific for Windows     agent](/manual/config/items/itemtypes/zabbix_agent/win_keys) -   [Minimum permission level for Windows agent     items](/manual/appendix/items/win_permissions)  
zh-cn	#### 支持的监控项  下表提供了可用的Zabbix agent监控项键值的详细信息。  另请参阅  -   [各平台支持的监控项](/manual/appendix/items/supported_by_platform) -   [ Zabbix agent  2支持的监控键值](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) -   [Windows agent指定的监控键值](/manual/config/items/itemtypes/zabbix_agent/win_keys) -   [最低权限级别Windows agent监控项](/manual/appendix/items/win_permissions)  

en-us	#### Supported macros  The discovery will return all instances of the specified object in the {\#INSTANCE} macro, which may be used in the prototypes of perf\_count and perf\_count\_en items.  ``` {.java} [     {"{#INSTANCE}":"0"},     {"{#INSTANCE}":"1"},     {"{#INSTANCE}":"_Total"} ] ```  For example, if the item key used in the discovery rule is:      perf_instance.discovery[Processor]  you may create an item prototype:      perf_counter["\Processor({#INSTANCE})\% Processor Time"]  Notes:  -   If the specified object is not found or does not support variable     instances then the discovery item will become NOTSUPPORTED. -   If the specified object supports variable instances, but currently     does not have any instances, then an empty JSON array will be     returned. -   In case of duplicate instances they will be skipped.
zh-cn	#### 支持的宏  自动发现会返回 {\#INSTANCE} 宏的所有对象实例 , 可用于perf\_count 和 perf\_count\_en监控项原型中。  ``` {.java} [     {"{#INSTANCE}":"0"},     {"{#INSTANCE}":"1"},     {"{#INSTANCE}":"_Total"} ] ```  例如, 假设自动发现规则中使用的监控项的键是：      perf_instance.discovery[Processor]  则可以创建这样的监控项原型：      perf_counter["\Processor({#INSTANCE})\% Processor Time"]  注意：  -   如果指定的对象找不到或者不支持可变实例，则自动发现监控项会变成NOTSUPPORTED状态。 -   如果指定的对象支持可变实例，但当前不存在任何实例，则会返回一个空的JSON数组。 -   重复的实例会被忽略。

en-us	##### Supported macros  The following macros are supported for use in the discovery rule [filter](/manual/discovery/low_level_discovery#discovery_rule_filter) and prototypes of items, triggers and graphs:  |Macro|Description| |-----|-----------| |Discovery of MBean attributes|<| |{\#JMXVALUE}|Attribute value.| |{\#JMXTYPE}|Attribute type.| |{\#JMXOBJ}|Object name.| |{\#JMXDESC}|Object name including attribute name.| |{\#JMXATTR}|Attribute name.| |Discovery of MBeans|<| |{\#JMXDOMAIN}|MBean domain. (*Zabbix reserved name*)| |{\#JMXOBJ}|Object name. (*Zabbix reserved name*)| |{\#JMX<key property>}|MBean properties (like {\#JMXTYPE}, {\#JMXNAME}) (see [Limitations](#limitations) below).|
zh-cn	##### 支持的宏  支持在自动发现规则的[过滤器](/manual/discovery/low_level_discovery#discovery_rule_filter)和监控项、触发器、图形的原型中使用下面的宏：  |宏|描述| |-----|-----------| |MBean属性的自动发现|<| |{\#JMXVALUE}|属性的值。| |{\#JMXTYPE}|属性的类型。| |{\#JMXOBJ}|对象名称。| |{\#JMXDESC}|包含属性名称的对象名称。| |{\#JMXATTR}|属性名称。| |MBean的自动发现|<| |{\#JMXDOMAIN}|MBean的域。 (*Zabbix的保留名称*)| |{\#JMXOBJ}|对象名称。 (*Zabbix的保留名称*)| |{\#JMX<key property>}|MBean属性 (类似 {\#JMXTYPE}, {\#JMXNAME}) (参考下面的[限制](#限制))。|

en-us	### Supported macros  The following macros are supported for use in the discovery rule [filter](/manual/discovery/low_level_discovery#discovery_rule_filter) and prototypes of items, triggers and graphs:  |Macro|Description| |-----|-----------| |{\#UNIT.NAME}|Primary unit name.| |{\#UNIT.DESCRIPTION}|Human readable description.| |{\#UNIT.LOADSTATE}|Load state (i.e. whether the unit file has been loaded successfully)| |{\#UNIT.ACTIVESTATE}|Active state (i.e. whether the unit is currently started or not)| |{\#UNIT.SUBSTATE}|Sub state (a more fine-grained version of the active state that is specific to the unit type, which the active state is not)| |{\#UNIT.FOLLOWED}|Unit that is being followed in its state by this unit, if there is any; otherwise an empty string.| |{\#UNIT.PATH}|Unit object path.| |{\#UNIT.JOBID}|Numeric job ID if there is a job queued for the job unit; 0 otherwise.| |{\#UNIT.JOBTYPE}|Job type.| |{\#UNIT.JOBPATH}|Job object path.| |{\#UNIT.UNITFILESTATE}|The install state of the unit file.|
zh-cn	#### 支持的宏  在自动发现规则的 [过滤器](/manual/discovery/low_level_discovery#discovery_rule_filter) 和监控项、触发器、图形的原型配置中支持的宏如下所示:  |宏|描述| |-----|-----------| |{\#UNIT.NAME}|主单元名称。| |{\#UNIT.DESCRIPTION}|通俗易懂的描述。| |{\#UNIT.LOADSTATE}|加载状态 (比如单元文件是否成功加载)| |{\#UNIT.ACTIVESTATE}|激活状态 (比如单元是否已启动)| |{\#UNIT.SUBSTATE}|子状态 (激活状态的另一个更加细致的版本，根据单元类型不同而不同, 而激活状态更加通用)| |{\#UNIT.FOLLOWED}|此单元所跟踪的单元的状态; 如果没有则显示空字符串。| |{\#UNIT.PATH}|单元对象路径。| |{\#UNIT.JOBID}|如果在任务单元中有排队的任务，则显示任务ID的数字; 否则为0。| |{\#UNIT.JOBTYPE}|任务类型。| |{\#UNIT.JOBPATH}|任务对象路径。| |{\#UNIT.UNITFILESTATE}|单元文件的安装状态。|

en-us	#### Supported macros  This discovery key returns two macros - {\#CPU.NUMBER} and {\#CPU.STATUS} identifying the CPU order number and status respectively. Note that a clear distinction cannot be made between actual, physical processors, cores and hyperthreads. {\#CPU.STATUS} on Linux, UNIX and BSD systems returns the status of the processor, which can be either "online" or "offline". On Windows systems, this same macro may represent a third value - "unknown" - which indicates that a processor has been detected, but no information has been collected for it yet.  CPU discovery relies on the agent's collector process to remain consistent with the data provided by the collector and save resources on obtaining the data. This has the effect of this item key not working with the test (-t) command line flag of the agent binary, which will return a NOT\_SUPPORTED status and an accompanying message indicating that the collector process has not been started.  Item prototypes that can be created based on CPU discovery include, for example:  -   `system.cpu.util[{#CPU.NUMBER},<type>,<mode>]` -   `system.hw.cpu[{#CPU.NUMBER},<info>]`  For detailed item key description, see [Zabbix agent item keys](/manual/config/items/itemtypes/zabbix_agent#supported_item_keys).
zh-cn	#### 支持的宏  这个键使用两个宏 - {\#CPU.NUMBER} 用于识别CPU序号， {\#CPU.STATUS} 用于识别CPU状态。 注意，没有办法清楚地区分出来实际的物理处理器、核心与超线程这三者。Linux、UNIX和BSD系统上的 {\#CPU.STATUS} 返回处理器的状态，状态可以是 "在线" 或者 "离线"。在Windows操作系统上，同样的宏可能会返回第三个取值 - "未知" - 表示已检测到处理器，但还未收集到相关信息。  为了保持与收集器提供的数据一致，CPU自动发现功能依赖agent的收集器进程，通过此方式还能在获取数据方面节省资源，但是这会导致此监控项的键不支持二进制agent的测试(-t)命令行参数，并且会返回一个NOT\_SUPPORTED状态，并附带信息，表明收集器进程未启动。  可基于CPU自动发现来创建监控项原型，比如:  -   `system.cpu.util[{#CPU.NUMBER},<type>,<mode>]` -   `system.hw.cpu[{#CPU.NUMBER},<info>]`  关于监控项的键的详细信息, 参考 [Zabbix agent 监控项的键](/manual/config/items/itemtypes/zabbix_agent#supported_item_keys)。

en-us	#### Supported macros  This discovery key returns two macros - {\#DEVNAME} and {\#DEVTYPE} identifying the block device name and type respectively, e.g.:  ``` {.java} [     {        "{#DEVNAME}":"loop1",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"dm-0",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda1",       "{#DEVTYPE}":"partition"    } ] ```  Block device discovery allows to use `vfs.dev.read[]` and `vfs.dev.write[]` items to create item prototypes using the {\#DEVNAME} macro, for example:  -   "vfs.dev.read\[{\#DEVNAME},sps\]" -   "vfs.dev.write\[{\#DEVNAME},sps\]"  {\#DEVTYPE} is intended for device filtering.
zh-cn	#### 支持的宏  此监控项返回两个宏 - {\#DEVNAME} 和 {\#DEVTYPE} 分别用于识别块设备名称和块设备类型, 例如:  ``` {.java} [     {        "{#DEVNAME}":"loop1",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"dm-0",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda1",       "{#DEVTYPE}":"partition"    } ] ```  块设备的自动发现允许使用 `vfs.dev.read[]` 和 `vfs.dev.write[]` 监控项和 {\#DEVNAME} 宏来创建监控项原型, 例如:  -   "vfs.dev.read\[{\#DEVNAME},sps\]" -   "vfs.dev.write\[{\#DEVNAME},sps\]"  {\#DEVTYPE} 用于设备过滤。

en-us	#### Supported macros  You may use the {\#IFNAME} macro in the discovery rule [filter](/manual/discovery/low_level_discovery#filter) and prototypes of items, triggers and graphs.  Examples of item prototypes that you might wish to create based on "net.if.discovery":  -   "net.if.in\[{\#IFNAME},bytes\]", -   "net.if.out\[{\#IFNAME},bytes\]".  Note that on Windows {\#IFGUID} is also returned.
zh-cn	#### 支持的宏  可在自动发现规则的 [过滤器](/manual/discovery/low_level_discovery#filter) 和监控项、触发器、图表的原型中用使用{\#IFNAME} 宏。  下面是基于 "net.if.discovery" 键创建的监控项原型:  -   "net.if.in\[{\#IFNAME},bytes\]", -   "net.if.out\[{\#IFNAME},bytes\]".  注意，在Windows操作系统上也可使用 {\#IFGUID} 宏获取返回值。

en-us	##### Supported parameters  The following set of parameters is supported by created MSIs:  |Number|Parameter|Description| |------|---------|-----------| |1|LOGTYPE|<| |2|LOGFILE|<| |3|SERVER|<| |4|LISTENPORT|<| |5|SERVERACTIVE|<| |6|HOSTNAME|<| |7|TIMEOUT|<| |8|TLSCONNECT|<| |9|TLSACCEPT|<| |10|TLSPSKIDENTITY|<| |11|TLSPSKFILE|<| |12|TLSPSKVALUE|<| |13|TLSCAFILE|<| |14|TLSCRLFILE|<| |15|TLSSERVERCERTISSUER|<| |16|TLSSERVERCERTSUBJECT|<| |17|TLSCERTFILE|<| |18|TLSKEYFILE|<| |19|INSTALLFOLDER|<| |20|ENABLEPATH|<| |21|SKIP|`SKIP=fw` - do not install firewall exception rule| |22|INCLUDE|Sequence of includes separated by `;`| |23|ALLOWDENYKEY|Sequence of "AllowKey" and "DenyKey" [parameters](/manual/config/items/restrict_checks) separated by `;`. Use `\\;` to escape the delimiter.|  To install you may run, for example:      SET INSTALLFOLDER=C:\Program Files\za      msiexec /l*v log.txt /i zabbix_agent-4.0.6-x86.msi /qn^      LOGTYPE=file^      LOGFILE="%INSTALLFOLDER%\za.log"^      SERVER=192.168.6.76^      LISTENPORT=12345^      SERVERACTIVE=::1^      HOSTNAME=myHost^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKFILE="%INSTALLFOLDER%\mykey.psk"^      TLSCAFILE="c:\temp\f.txt1"^      TLSCRLFILE="c:\temp\f.txt2"^      TLSSERVERCERTISSUER="My CA"^      TLSSERVERCERTSUBJECT="My Cert"^      TLSCERTFILE="c:\temp\f.txt5"^      TLSKEYFILE="c:\temp\f.txt6"^      ENABLEPATH=1^      INSTALLFOLDER="%INSTALLFOLDER%"^      SKIP=fw^      ALLOWDENYKEY="DenyKey=vfs.file.contents[/etc/passwd]"  or      msiexec /l*v log.txt /i zabbix_agent-4.4.0-x86.msi /qn^      SERVER=192.168.6.76^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKVALUE=1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952  
zh-cn	##### Supported parameters  The following set of parameters is supported by created MSIs:  |Number|Parameter|Description| |------|---------|-----------| |1|LOGTYPE|<| |2|LOGFILE|<| |3|SERVER|<| |4|LISTENPORT|<| |5|SERVERACTIVE|<| |6|HOSTNAME|<| |7|TIMEOUT|<| |8|TLSCONNECT|<| |9|TLSACCEPT|<| |10|TLSPSKIDENTITY|<| |11|TLSPSKFILE|<| |12|TLSPSKVALUE|<| |13|TLSCAFILE|<| |14|TLSCRLFILE|<| |15|TLSSERVERCERTISSUER|<| |16|TLSSERVERCERTSUBJECT|<| |17|TLSCERTFILE|<| |18|TLSKEYFILE|<| |19|INSTALLFOLDER|<| |20|ENABLEPATH|<| |21|SKIP|`SKIP=fw` - do not install firewall exception rule|  To install you may run, for example:      SET INSTALLFOLDER=C:\Program Files\za      msiexec /l*v log.txt /i zabbix_agent-4.0.6-x86.msi /qn^      LOGTYPE=file^      LOGFILE="%INSTALLFOLDER%\za.log"^      SERVER=192.168.6.76^      LISTENPORT=12345^      SERVERACTIVE=::1^      HOSTNAME=myHost^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKFILE="%INSTALLFOLDER%\mykey.psk"^      TLSCAFILE="c:\temp\f.txt1"^      TLSCRLFILE="c:\temp\f.txt2"^      TLSSERVERCERTISSUER="My CA"^      TLSSERVERCERTSUBJECT="My Cert"^      TLSCERTFILE="c:\temp\f.txt5"^      TLSKEYFILE="c:\temp\f.txt6"^      ENABLEPATH=1^      INSTALLFOLDER="%INSTALLFOLDER%"^      SKIP=fw  or      msiexec /l*v log.txt /i zabbix_agent-4.4.0-x86.msi /qn^      SERVER=192.168.6.76^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKVALUE=1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952  

en-us	##### Supported parameters  The following set of parameters is supported by created MSIs:  |Number|Parameter|Description| |------|---------|-----------| |1|LOGTYPE|<| |2|LOGFILE|<| |3|SERVER|<| |4|LISTENPORT|<| |5|SERVERACTIVE|<| |6|HOSTNAME|<| |7|TIMEOUT|<| |8|TLSCONNECT|<| |9|TLSACCEPT|<| |10|TLSPSKIDENTITY|<| |11|TLSPSKFILE|<| |12|TLSPSKVALUE|<| |13|TLSCAFILE|<| |14|TLSCRLFILE|<| |15|TLSSERVERCERTISSUER|<| |16|TLSSERVERCERTSUBJECT|<| |17|TLSCERTFILE|<| |18|TLSKEYFILE|<| |19|LISTENIP|<| |20|HOSTINTERFACE|<| |21|HOSTMETADATA|<| |22|HOSTMETADATAITEM|<| |23|STATUSPORT|Zabbix agent 2 only.| |24|ENABLEPERSISTENTBUFFER|Zabbix agent 2 only.| |25|PERSISTENTBUFFERPERIOD|Zabbix agent 2 only.| |26|PERSISTENTBUFFERFILE|Zabbix agent 2 only.| |27|INSTALLFOLDER|<| |28|ENABLEPATH|<| |29|SKIP|`SKIP=fw` - do not install firewall exception rule| |30|INCLUDE|Sequence of includes separated by `;`| |31|ALLOWDENYKEY|Sequence of "AllowKey" and "DenyKey" [parameters](/manual/config/items/restrict_checks) separated by `;`. Use `\\;` to escape the delimiter.|  To install you may run, for example:      SET INSTALLFOLDER=C:\Program Files\za      msiexec /l*v log.txt /i zabbix_agent-6.0.0-x86.msi /qn^      LOGTYPE=file^      LOGFILE="%INSTALLFOLDER%\za.log"^      SERVER=192.168.6.76^      LISTENPORT=12345^      SERVERACTIVE=::1^      HOSTNAME=myHost^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKFILE="%INSTALLFOLDER%\mykey.psk"^      TLSCAFILE="c:\temp\f.txt1"^      TLSCRLFILE="c:\temp\f.txt2"^      TLSSERVERCERTISSUER="My CA"^      TLSSERVERCERTSUBJECT="My Cert"^      TLSCERTFILE="c:\temp\f.txt5"^      TLSKEYFILE="c:\temp\f.txt6"^      ENABLEPATH=1^      INSTALLFOLDER="%INSTALLFOLDER%"^      SKIP=fw^      ALLOWDENYKEY="DenyKey=vfs.file.contents[/etc/passwd]"  or      msiexec /l*v log.txt /i zabbix_agent-6.0.0-x86.msi /qn^      SERVER=192.168.6.76^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKVALUE=1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952
zh-cn	##### 支持的参数  创建的MSI支持以下参数集：  |序号|参数|说明| |------|---------|-----------| |1|日志类型|<| |2|日志文件|<| |3|服务器|<| |4|监听|<| |5|服务器活动|<| |6|主机名|<| |7|超时|<| |8|TLS连接|<| |9|TLS接受|<| |10|TLSPSK身份|<| |11|TLSPSK文件|<| |12|TLSPSK值|<| |13|TLSCA文件|<| |14|TLSCRL文件|<| |15|TLS服务器证书颁发者|<| |16|TLS服务器证书对象|<| |17|TLS证书文件|<| |18|TLSKEY文件|<| |19|LISTENIP|<| |20|主机界面|<| |21|主机元数据|<| |22|主机元数据项|<| |23|端口状态|仅限Zabbix agent2。| |24|启用持久缓冲区|仅限Zabbix agent2。| |25|持续缓冲区|仅限Zabbix agent2。| |26|持续缓冲文件|仅限Zabbix agent2。| |27|安装文件夹|<| |28|启用路径|<| |29|跳过|`SKIP=fw` - 不安装防火墙规则| |30|包含|由 `;` 分隔的序列| |31|允许拒绝密钥|"AllowKey" 和 "DenyKey" [参数](/manual/config/items/restrict_checks) 的序列，用 `;`分隔，使用 `\\;` 转义分隔符。|  安装，可运行：      SET INSTALLFOLDER=C:\Program Files\za      msiexec /l*v log.txt /i zabbix_agent-6.0.0-x86.msi /qn^      LOGTYPE=file^      LOGFILE="%INSTALLFOLDER%\za.log"^      SERVER=192.168.6.76^      LISTENPORT=12345^      SERVERACTIVE=::1^      HOSTNAME=myHost^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKFILE="%INSTALLFOLDER%\mykey.psk"^      TLSCAFILE="c:\temp\f.txt1"^      TLSCRLFILE="c:\temp\f.txt2"^      TLSSERVERCERTISSUER="My CA"^      TLSSERVERCERTSUBJECT="My Cert"^      TLSCERTFILE="c:\temp\f.txt5"^      TLSKEYFILE="c:\temp\f.txt6"^      ENABLEPATH=1^      INSTALLFOLDER="%INSTALLFOLDER%"^      SKIP=fw^      ALLOWDENYKEY="DenyKey=vfs.file.contents[/etc/passwd]"  or      msiexec /l*v log.txt /i zabbix_agent-6.0.0-x86.msi /qn^      SERVER=192.168.6.76^      TLSCONNECT=psk^      TLSACCEPT=psk^      TLSPSKIDENTITY=MyPSKID^      TLSPSKVALUE=1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952

en-us	#### Supported platforms  Due to the security requirements and mission-critical nature of server operation, UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance and resilience. Zabbix operates on market leading versions.  Zabbix server is tested on the following platforms:  -   Linux -   Solaris -   AIX -   HP-UX -   Mac OS X -   FreeBSD -   OpenBSD -   NetBSD -   SCO Open Server -   Tru64/OSF1  ::: noteclassic Zabbix may work on other Unix-like operating systems as well. :::
zh-cn	#### 支持的平台  由于服务器操作的安全性要求和任务关键性，UNIX是唯一能够始终如一地提供必要性能、容错和弹性的操作系统。Zabbix以市场主流的操作系统版本运行。  经测试，Zabbix 可以运行在下列平台：  -   Linux -   Solaris -   AIX -   HP-UX -   Mac OS X -   FreeBSD -   OpenBSD -   NetBSD -   SCO Open Server -   Tru64/OSF1  ::: noteclassic Zabbix 可以运行在其他类 Unix 操作系统上。 :::

en-us	#### Supported platforms  Zabbix agent is [supported](https://www.zabbix.com/download_agents?version=6.0+LTS&release=6.0.12&os=Windows&os_version=Any&hardware=amd64&encryption=OpenSSL&packaging=MSI&show_legacy=0) on the following platforms:  -   Windows (all desktop and server versions since XP) -   Linux (also available in [distribution packages](https://www.zabbix.com/download?zabbix=6.0&os_distribution=alma_linux&os_version=9&components=agent&db=&ws=)) -   macOS -   IBM AIX -   FreeBSD -   OpenBSD -   Solaris
zh-cn	#### 支持的平台  Zabbix agent [支持](https://www.zabbix.com/download_agents?version=6.0+LTS&release=6.0.12&os=Windows&os_version=Any&hardware=amd64&encryption=OpenSSL&packaging=MSI&show_legacy=0) 在以下平台上：  -  Windows（自 XP 以来的所有桌面和服务器版本） -  Linux（也可在[分发包](https://www.zabbix.com/download?zabbix=6.0&os_distribution=alma_linux&os_version=9&components=agent&db=&ws=)） -  macOS -  IBM AIX -  FreeBSD -  OpenBSD -  Solaris

en-us	#### Supported platforms  Zabbix proxy runs on the same list of [server\#supported platforms](/manual/concepts/server#supported platforms) as Zabbix server.  
zh-cn	#### 支持的平台  Zabbix proxy 和Zabbix server支持运行的平台 [server#supported platforms](https://www.zabbix.com/documentation/devel/en/manual/concepts/server#supported%20platforms) 相同。

en-us	#### Supported segments  |Segment|Description| |--|--------| |`<name>`|Match object property by name.| |`*`|Match all object properties.| |`['<name>']`|Match object property by name.| |`['<name>', '<name>', ...]`|Match object property by any of the listed names.| |`[<index>]`|Match array element by the index.| |`[<number>, <number>, ...]`|Match array element by any of the listed indexes.| |`[*]`|Match all object properties or array elements.| |`[<start>:<end>]`|Match array elements by the defined range:<br>**<start>** - the first index to match (including). If not specified matches all array elements from the beginning. If negative specifies starting offset from the end of array.<br>**<end>** - the last index to match (excluding). If not specified matches all array elements to the end. If negative specifies starting offset from the end of array.| |`[?(<expression>)]`|Match objects/array elements by applying a filter expression.|  To find a matching segment ignoring its ancestry (detached segment) it must be prefixed with '..' , for example `$..name` or `$..['name']` return values of all 'name' properties.  Matched element names can be extracted by adding a `~` suffix to the JSONPath. It returns the name of the matched object or an index in string format of the matched array item. The output format follows the same rules as other JSONPath queries - definite path results are returned 'as is' and indefinite path results are returned in array. However there is not much point of extracting the name of an element matching a definite path - it's already known.
zh-cn	#### 支持的段  |段|描述| |-------|-----------| |`<name>`|按名称匹配对象属性。| |`*`|匹配所有对象属性。| |`['<name>']`|按名称匹配对象属性。| |`['<name>', '<name>', ...]`|通过任何列出的名称匹配对象属性。| |`[<index>]`|按索引匹配数组元素。| |`[<number>, <number>, ...]`|通过任何列出的索引匹配数组元素。| |`[*]`|匹配所有对象属性或数组元素。| |`[<start>:<end>]`|按定义的范围匹配数组元素：<br>**<start>** - 要匹配的第一个索引（包括）。 如果未指定，则匹配从头开始的所有数组元素。 如果为负数，则指定从数组末尾开始的偏移量。<br>**<end>** - 要匹配的最后一个索引（不包括）。 如果未指定，则匹配所有数组元素到最后。 如果为负数，则指定从数组末尾开始的偏移量。| |`[?(<表达式>)]`|通过应用过滤表达式匹配对象/数组元素。|  要查找忽略其根节点的匹配段（单独的段），它必须以 '..' 为前缀，例如 `$..name` 或 `$..['name']` 返回所有 'name' 属性的值。  可以通过在 JSONPath 中添加 `~` 后缀来提取匹配的元素名称。 它返回匹配对象的名称或匹配数组项的字符串格式的索引。 输出格式遵循与其他 JSONPath 查询相同的规则 - 确定路径结果按“原样”返回，不确定路径结果以数组形式返回。 但是，提取与明确路径匹配的元素的名称并没有多大意义——它是已知的。

en-us	#### Supported simple checks  List of supported simple checks:  See also:  -   [VMware monitoring item     keys](/manual/config/items/itemtypes/simple_checks/vmware_keys)  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |**icmpping**\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<| |Host accessibility by ICMP ping.|0 - ICMP ping fails<br><br>1 - ICMP ping successful|**target** - host IP or DNS name<br>**packets** - number of packets<br>**interval** - time between successive packets in milliseconds<br>**size** - packet size in bytes<br>**timeout** - timeout in milliseconds|Example:<br>=> icmpping\[,4\] → if at least one packet of the four is returned, the item will return 1.<br><br>See also: table of [default values](simple_checks#icmp_pings).| |**icmppingloss**\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<| |Percentage of lost packets.|Float.|**target** - host IP or DNS name<br>**packets** - number of packets<br>**interval** - time between successive packets in milliseconds<br>**size** - packet size in bytes<br>**timeout** - timeout in milliseconds|See also: table of [default values](simple_checks#icmp_pings).| |**icmppingsec**\[<target>,<packets>,<interval>,<size>,<timeout>,<mode>\]|<|<|<| |ICMP ping response time (in seconds).|Float.|**target** - host IP or DNS name<br>**packets** - number of packets<br>**interval** - time between successive packets in milliseconds<br>**size** - packet size in bytes<br>**timeout** - timeout in milliseconds<br>**mode** - possible values: *min*, *max*, *avg* (default)|Packets which are lost or timed out are not used in the calculation.<br><br>If host is not available (timeout reached), the item will return 0.<br>If the return value is less than 0.0001 seconds, the value will be set to 0.0001 seconds.<br><br>See also: table of [default values](simple_checks#icmp_pings).| |**net.tcp.service**\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - possible values: *ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address or DNS name (by default host IP/DNS is used)<br>**port** - port number (by default standard service port number is used).|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that with *tcp* service indicating the port is mandatory.<br>These checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service\[tcp,<ip>,port\] for checks like these.<br>*https* and *telnet* services are supported since Zabbix 2.0.| |**net.tcp.service.perf**\[service,<ip>,<port>\]|<|<|<| |Checks performance of TCP service.|Float.<br><br>0.000000 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - possible values: *ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address or DNS name (by default, host IP/DNS is used)<br>**port** - port number (by default standard service port number is used).|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Note that with *tcp* service indicating the port is mandatory.<br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,port\] for checks like these.<br>*https* and *telnet* services are supported since Zabbix 2.0.<br>Called tcp\_perf before Zabbix 2.0.| |net.udp.service\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - possible values: *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address or DNS name (by default host IP/DNS is used)<br>**port** - port number (by default standard service port number is used).|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0, 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.|Float.<br><br>0.000000 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - possible values: *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address or DNS name (by default, host IP/DNS is used)<br>**port** - port number (by default standard service port number is used).|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.|
zh-cn	#### 支持的简单检查  Zabbix支持的简单检查列表:  另请参考:  -   [VMware 监控项键值](/manual/config/items/itemtypes/simple_checks/vmware_keys)  |键值|<|<|<|<| |---|-|-|-|-| |<|**描述**|**返回值**|**参数**|**注释**| |icmpping\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<|<| |<|通过ICMP ping 检测主机的可访问性.|0 - ICMP ping 失败<br><br>1 - ICMP ping 成功|**target** - 主机 IP 或者域名<br>**packets** - 数据包数量<br>**interval** - 连续两个数据包之间的时间间隔，单位是毫秒<br>**size** - 数据包大小，单位是字节<br>**timeout** - 超时时间，单位是 毫秒|示例:<br>=> icmpping\[,4\] →  4 个数据包中只要一个有返回，那么该项返回值为 1.<br><br>另请参考:  [默认值](simple_checks#icmp_pings)表格。| |icmppingloss\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<|<| |<|发出的数据包丢包的百分比.|浮点数|**target** - 主机 IP 或者域名<br>**packets** - 数据包数量<br>**interval** - 连续两个数据包之间的时间间隔，单位是毫秒<br>**size** - 数据包大小，单位是字节<br>**timeout** - 超时时间，单位是毫秒|另请参考:  [默认值](simple_checks#icmp_pings)表格。| |icmppingsec\[<target>,<packets>,<interval>,<size>,<timeout>,<mode>\]|<|<|<|<| |<|ICMP ping 响应时间，单位是秒.|浮点数|**target** - 主机 IP 或者域名<br>**packets** - 数据包数量<br>**interval** - 连续两个数据包之间的时间间隔，单位是毫秒<br>**size** - 数据包大小，单位是字节<br>**timeout** - 超时时间，单位是毫秒<br>**mode** - 可能的值: *min*, *max*, *avg* (缺省值)|传输过程中丢失或者超时的数据包不会被计算在内.<br><br>如果主机不可用或者超时，这个监控项会返回 0.<br>如果返回值小于 0.0001 秒，那么这个值会被置为 0.0001 秒.<br><br>另请参考: [默认值](simple_checks#icmp_pings)表格。| |net.tcp.service\[service,<ip>,<port>\]|<|<|<|<| |<|检查服务是否在运行并且接受 TCP 连接。|0 - 服务停止<br><br>1 - 服务正在运行|**service** - 可能的值: *ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - 主机 IP 或者域名 (默认使用主机 IP/DNS<br>**port** - 端口号 (默认使用标准服务端口).|示例:<br>=> net.tcp.service\[ftp,,45\] → 通过检测 TCP 的 45 端口来检测 FTP 服务器的可用性.<br><br>请注意：使用 *tcp* 服务必须指定端口.<br>这些检测可能会在系统守护进程日志文件中产生额外的信息 (通常会记录 SMTP 和 SSH 会话).<br>目前不支持检测加密协议 (比如 993 端口的 IMAP 或者 995 端口的 POP) . 可以使用 net.tcp.service\[tcp,<ip>,port\] 作为一种检测方式进行检测 .<br>从 Zabbix 2.0 以后开始支持 *https* 和 *telnet* 服务。| |net.tcp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|检测 TCP 服务性能.|浮点数<br><br>0.000000 - 服务停止<br><br>seconds - 连接到服务花费的时间，单位是秒|**service** - 可能的值: *ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** -  IP 地址或者域名 (默认使用 IP/DNS )<br>**port** - 端口号 (默认使用标准服务端口).|示例:<br>=> net.tcp.service.perf\[ssh\] → 可以用来测试 SSH 服务器的初始响应速度.<br><br>使用 *tcp* 服务必须指定端口.<br>目前不支持检测加密协议 (比如 993 端口的 IMAP 或者 995 端口的 POP). 可以使用 net.tcp.service.perf\[tcp,<ip>,port\] 作为一种检测方式进行检测.<br>从 Zabbix 2.0 以后开始支持 *https* 和 *telnet* 服务.<br>在 Zabbix 2.0 之前调用的是 tcp\_perf 。| |net.udp.service\[service,<ip>,<port>\]|<|<|<|<| |<|检测服务是否正在运行并响应UDP请求.|0 - 服务停止<br><br>1 - 服务正在运行|**service** - 可能的值: *ntp* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP 地址或者域名 (默认使用 IP/DNS)<br>**port** - 端口号 (默认使用标准服务端口).|示例:<br>=> net.udp.service\[ntp,,45\] → 可用于测试 UDP 45 端口上 NTP 服务的可用性.<br><br>从 Zabbix 3.0以后开始支持这个监控项, 但在之前的版本中 *ntp* 服务可用 net.tcp.service\[\] 监控项来监控。| |net.udp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|检测 UDP 服务的性能.|浮点数<br><br>0.000000 - 服务停止<br><br>seconds - 等待服务响应的时间，单位是秒|**service** - 可能的值: *ntp* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP 地址或者域名 (默认使用 IP/DNS)<br>**port** - 端口号 (默认使用标准服务端口).|示例:<br>=> net.udp.service.perf\[ntp\] → 可用于测试NTP服务的响应时间.<br><br>从 Zabbix 3.0以后开始支持这个监控项, 但在之前的版本中 *ntp* 服务可用 net.tcp.service\[\] 监控项来监控。|

en-us	#### Supported XML files  XML files not older than version 1.8 are supported for import in Zabbix 6.0.  ::: noteimportant In the XML export format, trigger dependencies are stored by name only. If there are several triggers with the same name (for example, having different severities and expressions) that have a dependency defined between them, it is not possible to import them. Such dependencies must be manually removed from the XML file and re-added after import. :::
zh-cn	#### 支持的 XML 文件  Zabbix 6.0 支持导入不低于 1.8 版本的 XML 文件。  ::: noteimportant 在 XML 导出格式中，触发器依赖项仅按名称存储。如果有多个具有相同名称的触发器（例如，具有不同的严重性和表达式）并且在它们之间定义了依赖关系，则无法导入它们。此类依赖项必须从 XML 文件中手动删除，并在导入后重新添加。 :::

en-us	#### Supported Zabbix proxies  To be compatible with Zabbix 6.0, the proxy must be of the same major version; thus only Zabbix 6.0.x proxies can work with Zabbix 6.0.x server.  ::: noteimportant It is no longer possible to start the upgraded server and have older and unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. See also the [upgrade procedure](/manual/installation/upgrade). :::  Warnings about using incompatible Zabbix daemon versions are logged.
zh-cn	#### 支持的 Zabbix 代理  为了兼容Zabbix 6.0，代理必须是相同的主要版本； 因此只有 Zabbix 6.0.x 代理可以与 Zabbix 6.0.x 服务器一起工作。  ::: noteimportant 不再可能启动升级后的服务器并让旧的和未升级的代理向较新的服务器报告数据。 Zabbix 从未推荐或支持的这种方法现在已被正式禁用，因为服务器将忽略来自未升级代理的数据。 另请参阅 [升级过程](/manual/installation/upgrade)。 :::  记录有关使用不兼容的 Zabbix 守护程序版本的警告。

en-us	### SUSE  Open the `/etc/zypp/repos.d/zabbix.repo` file and set enable=1 for the `zabbix-unstable` repo.       [zabbix-unstable]     name=Zabbix Official Repository     type=rpm-md     baseurl=https://repo.zabbix.com/zabbix/5.5/sles/15/x86_64/     gpgcheck=1     gpgkey=https://repo.zabbix.com/zabbix/5.5/sles/15/x86_64/repodata/repomd.xml.key     enabled=1     update=1
zh-cn	### SUSE  打开 `/etc/zypp/repos.d/zabbix.repo` 文件并为 `zabbix-unstable` 仓库设置 enable=1。    · [zabbix-unstable]  · name=Zabbix Official Repository  · type=rpm-md  · baseurl=https://repo.zabbix.com/zabbix/5.5/sles/15/x86_64/  · gpgcheck=1  · gpgkey=https://repo.zabbix.com/zabbix/5.5/sles/15/x86_64/repodata/repomd.xml.key  · enabled=1  · update=1

en-us	##### Switching from AES128 to AES256  Zabbix uses AES128 as the built-in default for data. Let's assume you are using certificates and want to switch to AES256, on OpenSSL 1.1.1.  This can be achieved by adding the respective parameters in `zabbix_server.conf`:        TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/server.crt       TLSKeyFile=/home/zabbix/server.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384       TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256       TLSCipherPSK=kECDHEPSK+AES256:-SHA1       TLSCipherAll13=TLS_AES_256_GCM_SHA384       TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384  ::: noteimportant Although only certificate-related ciphersuites will be used, `TLSCipherPSK*` parameters are defined as well to avoid their default values which include less secure ciphers for wider interoperability. PSK ciphersuites cannot be completely disabled on server/proxy. :::  And in `zabbix_agentd.conf`:        TLSConnect=cert       TLSAccept=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384
zh-cn	##### 从AES128 到 AES256转换  Zabbix使用AES128作为数据的内置默认值。让我们假设您正在使用证书，并希望切换到OpenSSL 1.1.1上的AES256。 这可以通过添加相应的参数来实现 `zabbix_server.conf`:        TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/server.crt       TLSKeyFile=/home/zabbix/server.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384       TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256       TLSCipherPSK=kECDHEPSK+AES256:-SHA1       TLSCipherAll13=TLS_AES_256_GCM_SHA384       TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384  ::: noteimportant 虽然只使用与证书相关的密码套件，但' TLSCipherPSK* '参数也被定义得很好，以避免它们的默认值包括较不安全的密码，以实现更广泛的互操作性。 不能在server/proxy上完全禁用PSK密码套件。 :::  并且在 `zabbix_agentd.conf`:        TLSConnect=cert       TLSAccept=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384

en-us	##### Switching interface back to available  When the unreachability period is over, the interface is polled again, decreasing priority for item that turned the interface into unreachable state. If the unreachable interface reappears, the monitoring returns to normal automatically:      resuming Zabbix agent checks on host "New host": connection restored  ::: noteclassic Once interface becomes available, the host does not poll all its items immediately for two reasons:  -   It might overload the host. -   The interface restore time is not always matching planned item     polling schedule time.  So, after the interface becomes available, items are not polled immediately, but they are getting rescheduled to their next polling round. :::
zh-cn	 ##### 将主机接口状态切换回可用  当不可达期结束时，再次轮询接口， 降低使主机接口状态无法访问的监控项的优先级 状态。如果不可达接口再次出现，则监控自动恢复正常：      resuming Zabbix agent checks on host "New host": connection restored  ::: noteclassic 一旦接口可用，主机不会立即轮询所有监控项有两个原因：  -   它可能会使主机过载。 -   主机接口恢复时间并不总是与监控项计划轮询时间匹配。  因此，在主机接口可用后，监控项不会立即被轮询，但他们将被重新安排到下一次轮询。 :::

en-us	#### Switching to raw values  A dropdown on the upper right allows to switch from the simple graph to the *Values/500 latest values* listings. This can be useful for viewing the numeric values making up the graph.  The values represented here are raw, i.e. no units or postprocessing of values is used. Value mapping, however, is applied.
zh-cn	#### 切换到原始值  右上角的下拉菜单允许从简单图形切换到*值/500 个最新值* 列表。这对于查看组成图形的数值很有用。  这里表示的是原始值，即没有单位或使用处理后的值。但是，会显示应用了值映射。

en-us	 ### Symlink name expansion  Symlink name and full path of the symlink are now returned in `vfs.dir.get[]` and `vfs.file.get[]` items,  instead of resolving to the symlink target. 
zh-cn	### 符号链接名称扩展  符号链接名称和符号链接的完整路径现在在 `vfs.dir.get[]` 和 `vfs.file.get[]` 监控项中返回，而不是解析为符号链接目标。

en-us	## SYNOPSIS  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}
zh-cn	 ## 概要   **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_js -s** *script-file* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_js -s** *script-file* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}
zh-cn	## 概要  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}

en-us	#### Syntax  Aggregates can be retrieved by working with either:  -   history of items:  ```{=html} <!-- --> ```     aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...)  -   a [foreach function](/manual/appendix/functions/aggregate/foreach)     as the only parameter:  ```{=html} <!-- --> ```     aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod))  where:  - `aggregate_function` is one of the supported [aggregate functions](/manual/appendix/functions/aggregate#aggregate-functions-1): avg, max, min, sum, etc. - `foreach_function` is one of the supported foreach functions: avg_foreach, count_foreach, etc.   Foreach functions use an [item filter](/manual/appendix/functions/aggregate/foreach#item-filter), to work with the history of multiple items, and return an array of values - one for each item.  ::: noteclassic If the aggregate results in a float value it will be trimmed to an integer if the aggregated item type of information is *Numeric (unsigned)*. :::  An aggregate calculation may become unsupported if:  -   none of the referenced items is found (which may happen if the item     key is incorrect, none of the items exists or all included groups     are incorrect) -   no data to calculate a function
zh-cn	 -   项目历史:  ``` aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...) ``` -  一个 foreach 函数作为唯一参数:  ``` aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod)) ```         where:     -   `聚合函数`是支持的聚合函数之一: avg，max，min，sum，等等.     -    函数是受支持的 foreach 函数之一: avg _ foreach、 count _ foreach 等  Foreach 函数使用项筛选器处理多个项的历史记录，并返回一个值数组——每个项一个值。  注意: 如果聚合项类型的信息是 Numeric (无符号) ，则聚合结果生成的浮点值将被裁剪为整数。. 如果出现以下情况，则可能不支持聚合计算: -   没有找到任何引用的项(如果项目键不正确、项目不存在或所有包含的组都不正确，则可能发生这种情况) -   没有数据来计算函数

en-us	#### Syntax  Aggregates can be retrieved by working with either:  -   history of items:  ```{=html} <!-- --> ```     aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...)  -   a [foreach function](/manual/appendix/functions/aggregate/foreach)     as the only parameter:  ```{=html} <!-- --> ```     aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod))  where:  - `aggregate_function` is one of the supported [aggregate functions](/manual/appendix/functions/aggregate#aggregate-functions-1): avg, max, min, sum, etc. - `foreach_function` is one of the supported foreach functions: avg_foreach, count_foreach, etc.   Foreach functions use an item filter, to work with the history of multiple items, and return an array of values - one for each item.  ::: noteclassic If the aggregate results in a float value it will be trimmed to an integer if the aggregated item type of information is *Numeric (unsigned)*. :::  An aggregate calculation may become unsupported if:  -   none of the referenced items is found (which may happen if the item     key is incorrect, none of the items exists or all included groups     are incorrect) -   no data to calculate a function
zh-cn	 -   项目历史:  ``` aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...) ``` -  一个 foreach 函数作为唯一参数:  ``` aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod)) ```         where:     -   `聚合函数`是支持的聚合函数之一: avg，max，min，sum，等等.     -    函数是受支持的 foreach 函数之一: avg _ foreach、 count _ foreach 等  Foreach 函数使用项筛选器处理多个项的历史记录，并返回一个值数组——每个项一个值。  注意: 如果聚合项类型的信息是 Numeric (无符号) ，则聚合结果生成的浮点值将被裁剪为整数。. 如果出现以下情况，则可能不支持聚合计算: -   没有找到任何引用的项(如果项目键不正确、项目不存在或所有包含的组都不正确，则可能发生这种情况) -   没有数据来计算函数

en-us	##### System data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**system.boottime**|<|<|<| |System boot time.|Integer (Unix timestamp)| | | |**system.cpu.discovery**|<|<|<| |List of detected CPUs/CPU cores. Used for low-level discovery.|JSON object| |Supported on all platforms since 2.4.0.| |**system.cpu.intr**|<|<|<| |Device interrupts.|Integer| | | |**system.cpu.load**\[<cpu>,<mode>\]|<|<|<| |[CPU load](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - possible values:<br>*all* (default), *percpu* (since version 2.0; total load divided by online CPU count)<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |**system.cpu.num**\[<type>\]|<|<|<| |Number of CPUs.|Integer|**type** - possible values:<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |**system.cpu.switches**|<|<|<| |Count of context switches.|Integer| | | |**system.cpu.util**\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<| |CPU utilization percentage.|Float|**cpu** - *<CPU number>* or *all* (default)<br>**type** - possible values:<br>*user* (default), *idle*, *nice*, *system* (default for Windows), *iowait*, *interrupt*, *softirq*, *steal*, *guest* (on Linux kernels 2.6.24 and above), *guest\_nice* (on Linux kernels 2.6.33 and above).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*<br>**logical\_or\_physical** (since version 5.0.3; on AIX only) - possible values: *logical* (default), *physical*. This parameter is supported on AIX only.|On Windows the value is acquired using the *Processor Time* performance counter. Note that since Windows 8 its Task Manager shows CPU utilization based on the *Processor Utility* performance counter, while in previous versions it was the *Processor Time* counter.<br><br>Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>Old naming: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |**system.hostname**\[<type>, <transform>\]|<|<|<| |System host name.|String|**type** (before version 5.4.7 supported on Windows only) - possible values: *netbios* (default on Windows), *host* (default on Linux), *shorthost* (since version 5.4.7; returns part of the hostname before the first dot, a full string for names without dots).<br>**transform** (since version 5.4.7) - possible values:<br>*none* (default), *lower* (convert to lowercase)|The value is acquired by either GetComputerName() (for **netbios**) or gethostname() (for **host**) functions on Windows and by taking `nodename` from the uname() system API output on other systems.<br><br>Examples of returned values:<br>*on Linux*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |**system.hw.chassis**\[<info>\]|<|<|<| |Chassis information.|String|**info** - one of full (default), model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>This key depends on the availability of the [SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) table.<br>Will try to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory.<br><br>**Root permissions** are required because the value is acquired by reading from sysfs or memory.<br><br>Supported since Zabbix 2.0.| |**system.hw.cpu**\[<cpu>,<info>\]|<|<|<| |CPU information.|String or integer|**cpu** - *<CPU number>* or *all* (default)<br>**info** - possible values:<br>*full* (default), *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>Gathers info from /proc/cpuinfo and /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq.<br><br>If a CPU number and *curfreq* or *maxfreq* is specified, a numeric value is returned (Hz).<br><br>Supported since Zabbix 2.0.| |**system.hw.devices**\[<type>\]|<|<|<| |Listing of PCI or USB devices.|Text|**type** (since version 2.0) - *pci* (default) or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>Returns the output of either lspci or lsusb utility (executed without any parameters).| |**system.hw.macaddr**\[<interface>,<format>\]|<|<|<| |Listing of MAC addresses.|String|**interface** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**format** - *full* (default) or *short*|Lists MAC addresses of the interfaces whose name matches the given `interface` regular [expression](/manual/regular_expressions#overview) (*all* lists for all interfaces).<br><br>Example:<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If `format` is specified as *short*, interface names and identical MAC addresses are not listed.<br><br>Supported since Zabbix 2.0.| |**system.localtime**\[<type>\]|<|<|<| |System time.|Integer - with `type` as *utc*<br><br>String - with `type` as *local*|**type** (since version 2.0) - possible values:<br>*utc* - (default) the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds.<br>*local* - the time in the 'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm' format<br>|Must be used as a [passive check](/manual/appendix/items/activepassive#passive_checks) only.<br><br>Example:<br>=> system.localtime\[local\] → create an item using this key and then use it to display host time in the *Clock* [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock).| |**system.run**\[command,<mode>\]|<|<|<| |Run specified command on the host.|Text result of the command<br><br>1 - with `mode` as *nowait* (regardless of command result)|**command** - command for execution<br>**mode** - possible values:<br>*wait* - wait end of execution (default),<br>*nowait* - do not wait|Up to 512KB of data can be returned, including trailing whitespace that is truncated.<br>To be processed correctly, the output of the command must be text.<br><br>Example:<br>=> system.run\[ls -l /\] → detailed file list of root directory.<br><br>*Note*: system.run items are disabled by default. Learn how to [enable them](/manual/config/items/restrict_checks).<br><br>The return value of the item is standard output together with standard error produced by command. The exit code is not checked.<br><br>Empty result is allowed starting with Zabbix 2.4.0.<br>See also: [Command execution](/manual/appendix/command_execution).| |**system.stat**\[resource,<type>\]|<|<|<| |System statistics.|Integer or float|**ent** - number of processor units this partition is entitled to receive (float)<br>**kthr,<type>** - information about kernel thread states:<br>*r* - average number of runnable kernel threads (float)<br>*b* - average number of kernel threads placed in the Virtual Memory Manager wait queue (float)<br>**memory,<type>** - information about the usage of virtual and real memory:<br>*avm* - active virtual pages (integer)<br>*fre* - size of the free list (integer)<br>**page,<type>** - information about page faults and paging activity:<br>*fi* - file page-ins per second (float)<br>*fo* - file page-outs per second (float)<br>*pi* - pages paged in from paging space (float)<br>*po* - pages paged out to paging space (float)<br>*fr* - pages freed (page replacement) (float)<br>*sr* - pages scanned by page-replacement algorithm (float)<br>**faults,<type>** - trap and interrupt rate:<br>*in* - device interrupts (float)<br>*sy* - system calls (float)<br>*cs* - kernel thread context switches (float)<br>**cpu,<type>** - breakdown of percentage usage of processor time:<br>*us* - user time (float)<br>*sy* - system time (float)<br>*id* - idle time (float)<br>*wa* - idle time during which the system had outstanding disk/NFS I/O request(s) (float)<br>*pc* - number of physical processors consumed (float)<br>*ec* - the percentage of entitled capacity consumed (float)<br>*lbusy* - indicates the percentage of logical processor(s) utilization that occurred while executing at the user and system level (float)<br>*app* - indicates the available physical processors in the shared pool (float)<br>**disk,<type>** - disk statistics:<br>*bps* - indicates the amount of data transferred (read or written) to the drive in bytes per second (integer)<br>*tps* - indicates the number of transfers per second that were issued to the physical disk/tape (float)|This item is [supported](/manual/appendix/items/supported_by_platform) on AIX only.<br>Take note of the following limitations in these items:<br>=> system.stat\[cpu,app\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,ec\] - supported on AIX LPAR of type "Shared" and "Dedicated" ("Dedicated" always returns 100 (percent))<br>=> system.stat\[cpu,lbusy\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,pc\] - supported on AIX LPAR of type "Shared" and "Dedicated"<br>=> system.stat\[ent\] - supported on AIX LPAR of type "Shared" and "Dedicated"| |**system.sw.arch**|<|<|<| |Software architecture information.|String| |Example:<br>=> system.sw.arch → i686<br><br>Info is acquired from uname() function.<br><br>Supported since Zabbix 2.0.| |**system.sw.os**\[<info>\]|<|<|<| |Operating system information.|String|**info** - possible values:<br>*full* (default), *short* or *name*|Example:<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>Info is acquired from (note that not all files and options are present in all distributions):<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME parameter from /etc/os-release on systems supporting it, or /etc/issue.net (*name*)<br><br>Supported since Zabbix 2.0.| |**system.sw.packages**\[<regexp>,<manager>,<format>\]|<|<|<| |Listing of installed packages.|Text|**regexp** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**manager** - *all* (default) or a package manager<br>**format** - *full* (default) or *short*|Lists (alphabetically) installed packages whose name matches the given `package` regular [expression](/manual/regular_expressions#overview) (*all* lists them all).<br><br>Example:<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>Supported package managers (executed command):<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>If `format` is specified as *full*, packages are grouped by package managers (each manager on a separate line beginning with its name in square brackets).<br>If `format` is specified as *short*, packages are not grouped and are listed on a single line.<br><br>Supported since Zabbix 2.0.| |**system.swap.in**\[<device>,<type>\]|<|<|<| |Swap in (from device into memory) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapins), *sectors* (sectors swapped in), *pages* (pages swapped in).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.in\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |**system.swap.out**\[<device>,<type>\]|<|<|<| |Swap out (from memory onto device) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapouts), *sectors* (sectors swapped out), *pages* (pages swapped out).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.out\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |**system.swap.size**\[<device>,<type>\]|<|<|<| |Swap space size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*free* (free swap space, default), *pfree* (free swap space, in percent), *pused* (used swap space, in percent), *total* (total swap space), *used* (used swap space)<br>Note that *pfree*, *pused* are not supported on Windows if swap size is 0.<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.size\[,pfree\] → free swap space percentage<br><br>If *device* is not specified Zabbix agent will only take into account swap devices (files), physical memory will be ignored. For example, on Solaris systems *swap -s* command includes a portion of physical memory and swap devices (unlike *swap -l*).<br><br>Note that this key might report incorrect swap space size/percentage on virtualized (VMware ESXi, VirtualBox) Windows platforms. In this case you may use the `perf_counter[\700(_Total)\702]` key to obtain correct swap space percentage.| |**system.uname**|<|<|<| |Identification of the system.|String| |Example of returned value (Unix):<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>Example of returned value (Windows):<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>On Unix since Zabbix 2.2.0 the value for this item is obtained with uname() system call. Previously it was obtained by invoking "uname -a". The value of this item might differ from the output of "uname -a" and does not include additional information that "uname -a" prints based on other sources.<br><br>On Windows since Zabbix 3.0 the value for this item is obtained from Win32\_OperatingSystem and Win32\_Processor WMI classes. Previously it was obtained from volatile Windows APIs and undocumented registry keys. The OS name (including edition) might be translated to the user's display language. On some versions of Windows it contains trademark symbols and extra spaces.<br><br>Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture.| |**system.uptime**|<|<|<| |System uptime in seconds.|Integer| |In [item configuration](/manual/config/items/item#configuration), use **s** or **uptime** units to get readable values.| |**system.users.num**|<|<|<| |Number of users logged in.|Integer| |**who** command is used on the agent side to obtain the value.|
zh-cn	##### 系统数据  |键值|<|<|<| |---|---|---|---| |描述|返回值|参数|注释| |**system.boottime**|<|<|<| |系统启动时间。|整型 (Unix时间戳)| | | |**system.cpu.discovery**|<|<|<| |检测到的CPU/CPUs的内核列表，用于底层自动发现。|JSON 对象| |自2.4.0后，支持所有平台| |**system.cpu.intr**|<|<|<| |设备中断。|整型| | | |**system.cpu.load**\[<cpu>,<mode>\]|<|<|<| |[CPU 负载](http://en.wikipedia.org/wiki/Load_(computing)).|浮点型|**cpu** - possible values:<br>*all* (default), *percpu* (从版本2.0开始; 总负载除以在线CPU数)<br>**mode** - 可能的值：<br>*avg1* (一分钟的平均值，默认), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |**system.cpu.num**\[<type>\]|<|<|<| |CPU数量。|整型|**type** - 可能的值：<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |**system.cpu.switches**|<|<|<| |上下文切换次数。|整型| | | |**system.cpu.util**\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<| |CPU 利用率百分比。|浮点型|**cpu** - *<CPU number>* or *all* (default)<br>**type** - 可能的值：<br>*user* (default), *idle*, *nice*, *system* （Windows默认）, *iowait*, *interrupt*, *softirq*, *steal*, *guest* (Linux内核版本2.6.24及以上), *guest\_nice* (Linux内核版本2.6.33及以上).<br>可在[平台特性](/manual/appendix/items/supported_by_platform) 查看更多此参数的细节。<br>**mode** - 可能的值：<br>*avg1* (一分钟的平均值，默认), *avg5*, *avg15*<br>**logical\_or\_physical** (从5.0.3版本开始; 仅支持AIX) - 可能的值： *logical* （默认）, *physical*. 此参数仅支持AIX。|Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>曾用名: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |**system.hostname**\[<type>, <transform>\]|<|<|<| |系统主机名|字符串|**type** (在版本5.4.7前仅支持Windows) - 可能的值： *netbios* （Windows默认）, *host* (Linux默认), *shorthost* (从5.4.7版本开始; 返回第一个"."前的主机名或在没有"."时返回完整的主机名).<br>**transform** (从5.4.7版本开始) - 可能的值：<br>*none* （默认）, *lower* (转换到小写)|这个值通过Windows的函数 GetComputerName() (**netbios**)或者gethostname() (**host**) 和其他操作系统的 "hostname" 命令获取。<br><br>返回值示例：<br>*在Linux上*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>可查看[更详细的描述](/manual/appendix/install/windows_agent#configuration).| |**system.hw.chassis**\[<info>\]|<|<|<| |板卡信息。|字符串|**info** - one of full （默认）, model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>这个键依赖于[SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) 表的可用性。<br>会尝试从sysfs读取DMI表, 如果访问sysfs 失败，会尝试直接读取内存。<br><br>需要**Root权限**因为这个值是通过读取 sysfs 或 memory 获得的。<br><br>从Zabbix 2.0开始支持。| |**system.hw.cpu**\[<cpu>,<info>\]|<|<|<| |CPU 信息。|字符串或整型|**cpu** - *<CPU number>* or *all* （默认）<br>**info** - 可能的值：<br>*full* （默认）, *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>从/proc/cpuinfo 和 /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq 获取信息。<br><br>如果设置了CPU数和 *curfreq* 或 *maxfreq*，会返回数字值(Hz)。<br><br>从Zabbix 2.0开始支持。| |**system.hw.devices**\[<type>\]|<|<|<| |PCI或USB设备列表。|文本|**type** (从版本2.0开始) - *pci* （默认） or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>返回lspci或lsusb程序的结果（不带参数执行）。| |**system.hw.macaddr**\[<interface>,<format>\]|<|<|<| |MAC地址列表。|字符串|**interface** - *all* （默认）或 [正则表达式](/manual/regular_expressions#overview)<br>**format** - *full* （默认） 或 *short*|列出接口名称匹配`接口`[正则表达式](/manual/regular_expressions#overview)的MAC地址列表(*all* 列出所有接口).<br><br>示例：<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If 如果`format`被设为*short*，接口名称和重复的MAC地址将不会列出。<br><br>从Zabbix 2.0开始支持。| |**system.localtime**\[<type>\]|<|<|<| |系统时间。|整型 - `type`是*utc*时<br><br>字符串 - `type`是*local*时|**type** (从版本2.0开始) - 可能的值：<br>*utc* - （默认）从 (00:00:00 UTC, January 1, 1970) 开始计算的时间, 单位是秒。<br>*local* - 格式为'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm'的时间<br>|只能用于[被动检查](/manual/appendix/items/activepassive#passive_checks)。<br><br>示例：<br>=> system.localtime\[local\] → 用这个键创建一个监控项用于在*Clock* [仪表盘组件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock)展示主机时间。| |**system.run**\[command,<mode>\]|<|<|<| |在主机上运行特定的命令。|命令的文本结果<br><br>1 - `mode`为*nowait*时(无论命令结果如何)|**command** - 待执行的命令<br>**mode** - 可能的值：<br>*wait* - 等待执行结束（默认）,<br>*nowait* - 不等待|包括被截取的空白符，最大可以返回512KB的数据。<br>命令的输出必须是文本才能正常处理。<br><br>示例：<br>=> system.run\[ls -l /\] → 根目录的详细文件列表。<br><br>*Note*: system.run监控项默认被禁用。在[启用监控项](/[[/manual/config/items/restrict_checks)学习如何启用。<br><br>这个监控项的返回值是命令产生的标准输出和标准错误，未检查退出码。<br><br>从 Zabbix 2.4.0 开始允许空结果。<br>也可查看[命令执行](/manual/appendix/command_execution)。| |**system.stat**\[resource,<type>\]|<|<|<| |系统统计数据。|整型或浮点型|**ent** - 该区域可获取的处理器单元数量（浮点型）<br>**kthr,<type>** - 关于内核线程状态的信息:<br>*r* - 可运行的内核线程的平均数（浮点型）<br>*b* - 虚拟内存管理器等待队列中内核线程的平均数（浮点型）<br>**memory,<type>** - 虚拟和实际内存的使用信息：<br>*avm* - 活跃的虚拟页 (整型)<br>*fre* - 可用列表的大小 (整型)<br>**page,<type>** - 页错误和分页活动的信息：<br>*fi* - 每秒文件入页（浮点型）<br>*fo* - 每秒文件出页 （浮点型）<br>*pi* - 从分页空间入页（浮点型）<br>*po* - 向分页空间出页（浮点型）<br>*fr* - 页释放（页替换）（浮点型）<br>*sr* - 通过页替换算法扫描到的页（浮点型）<br>**faults,<type>** - 陷阱和中断率：<br>*in* - 设备中断（浮点型）<br>*sy* - 系统调用（浮点型）<br>*cs* - 内核线程上下文切换 （浮点型）<br>**cpu,<type>** - 处理器时间的分类百分比：<br>*us* - 用户时间（浮点型）<br>*sy* - 系统时间（浮点型）<br>*id* - 空闲时间（浮点型）<br>*wa* - 系统在磁盘或网络文件系统I/O请求多时的空闲时间（浮点型）<br>*pc* - 物理处理器消耗的时间（浮点型）<br>*ec* - 标称计算能力的消耗的百分比（浮点型）<br>*lbusy* - 在用户级和系统级运行时，逻辑处理器的使用百分比 （浮点型）<br>*app* - 共享池中可用物理处理器数量（浮点型）<br>**disk,<type>** - 磁盘统计信息：<br>*bps* - 磁盘驱动器传输的数据量，单位是字节/秒（整型）<br>*tps* - 发送给物理磁盘/磁带的每秒传输次数（浮点型），从Zabbix 1.8.1开始，此监控项仅被AIX[支持](/manual/appendix/items/supported_by_platform)。<br>请注意这些监控项的以下限制：<br>=> system.stat\[cpu,app\] - 仅支持"Shared"类型的AIX LPAR<br>=> system.stat\[cpu,ec\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR（"Dedicated"一直返回100（百分比））<br>=> system.stat\[cpu,lbusy\] - 仅支持"Shared"类型的AIX LPAR<br>=> system.stat\[cpu,pc\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR<br>=> system.stat\[ent\] - 仅支持"Shared"和"Dedicated"类型的AIX LPAR|<| |**system.sw.arch**|<|<|<| |软件架构信息。|字符串| |示例：<br>=> system.sw.arch → i686<br><br>通过uname()函数获取信息。<br><br>从Zabbix 2.0开始支持。| |**system.sw.os**\[<info>\]|<|<|<| |操作系统信息。|字符串|**info** - 可能的值：<br>*full* （默认）, *short* or *name*|示例：<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>信息通过以下方式（请注意并非所有发行版本都存在所有文件和选项）获取：<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME 参数在支持的系统从/etc/os-release获取，或/etc/issue.net (*name*)<br><br>从Zabbix 2.0开始支持。| |**system.sw.packages**\[<package>,<manager>,<format>\]|<|<|<| |已安装的包列表。|文本|**package** - *all* （默认） 或[正则表达式](/manual/regular_expressions#overview)<br>**manager** - *all* （默认）或包管理器<br>**format** - *full* （默认）或*short*|按首字母顺序，列出匹配`package`[正则表达式](/manual/regular_expressions#overview)的已安装的包名 (*all* 列出全部).<br><br>示例：<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>支持的包管理器（执行的命令）：<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>如果`format`设为*full*，包按照包管理器分组（每个包管理器在单独的行，开头是方括号中的包管理器名称）。<br>如果`format`设为*short*，包不会分组，会列在一行中。<br><br>从Zabbix 2.0开始支持。| |**system.swap.in**\[<device>,<type>\]|<|<|<| |交换入（从设备到内存）统计|整型|**device** - 用于交换的设备（默认是*all*）<br>**type** - 可能的值：<br>*count* （交换入的数量）, *sectors* （交换入的分区）, *pages* （交换入的页）.<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.in\[,pages\]<br><br>此信息的来源是：<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |**system.swap.out**\[<device>,<type>\]|<|<|<| |交换出（从内存到设备）统计。|整型|**device** - 用于交换的设备（默认是*all*）<br>**type** - 可能的值：<br>*count* （交换出的数量）， *sectors* （交换出的分区）, *pages* （交换出的页）。<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.out\[,pages\]<br><br>此信息的来源是：<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |**system.swap.size**\[<device>,<type>\]|<|<|<| |交换区空间大小，字节数或总量的百分比。|整型 - 字节数的类型<br><br>浮点型 - 百分比的类型|**device** - 用于交换的设备(默认是*all*)<br>**type** - 可能的值：<br>*free* (空闲交换空间，默认), *pfree* (空闲交换空间的百分比), *pused* (已用交换空间的百分比), *total* (总交换空间), *used* (已用交换空间)<br>请注意 *pfree*, *pused* 在交换空间为0时不支持Windows。<br>也可在[平台特性](/manual/appendix/items/supported_by_platform)查看此参数的详情。|示例：<br>=> system.swap.size\[,pfree\] → 空闲交换空间的百分比<br><br>如果未设置*device*的值，Zabbix agent仅会考虑账户交换设备（文件），忽略物理内存。比如，在 Solaris 系统 *swap -s* 命令包括物理内存的一部分以及交换设备（不同于*swap -l*）。<br><br>请注意此键在虚拟化（VMware ESXi, VirtualBox）Windows平台可能报告错误的交换空间大小/百分比。在这种情况下你可使用`perf_counter[\700(_Total)\702]`键来获取正确的交换空间百分比。| |**system.uname**|<|<|<| |系统标识|字符串| |返回值实例（Unix）：<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>返回值实例（Windows）：<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>在 Unix，从 Zabbix 2.2.0 开始，此值通过uname()系统调用获取，在此之前通过调用"uname -a"获取。此监控项的值可能和"uname -a"的输出不同，并且不包括"uname -a"打印的从其他来源获取的额外信息。<br><br>在 Windows 系统，从 Zabbix 3.0 开始，此值通过 Win32\_OperatingSystem 和 Win32\_Processor WMI 类获取。在此之前通过不稳定的 Windows APIs 和无稳定的注册表键获取。OS名（包括版本）可能被翻译到了用户的显示语言。在 Windows 的某些版本，OS 名包括商标符号和额外的空格。<br><br>请注意在Windows，此监控项返回 OS 架构，而在 Unix 返回 CPU 架构。| |**system.uptime**|<|<|<| |系统运行时间，单位是秒。|整型| |在[监控项配置](/manual/config/items/item#configuration)中，使用 **s** or **uptime** 单位获取可读的值。| |**system.users.num**|<|<|<| |登录用户数|整型| |**who** 命令是用于在agent处获取值的。|

en-us	 ### Systemd  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |systemd.unit.get\[unit name,<interface>\]|<|<|<| |Returns all properties of a systemd unit.|JSON object|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**interface** - unit interface type, possible values: *Unit* (default), *Service*, *Socket*, *Device*, *Mount*, *Automount*, *Swap*, *Target*, *Path*|This item is supported on Linux platform only.<br><br>LoadState, ActiveState and UnitFileState for Unit interface are returned as text and integer:<br>`"ActiveState":{"state":1,"text":"active"}`| |systemd.unit.info\[unit name,<property>,<interface>\]|<|<|<| |Systemd unit information.|String|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**property** - unit property (e.g. ActiveState (default), LoadState, Description)<br>**interface** - unit interface type (e.g. Unit (default), Socket, Service)|This item allows to retrieve a specific property from specific type of interface as described in [dbus API](https://www.freedesktop.org/wiki/Software/systemd/dbus/).<br><br>This item is supported on Linux platform only.<br><br>Examples:<br>=> systemd.unit.info\["{\#UNIT.NAME}"\] - collect active state (active, reloading, inactive, failed, activating, deactivating) info on discovered systemd units<br>=> systemd.unit.info\["{\#UNIT.NAME}",LoadState\] - collect load state info on discovered systemd units<br>=> systemd.unit.info\[mysqld.service,Id\] - retrieve service technical name (mysqld.service)<br>=> systemd.unit.info\[mysqld.service,Description\] - retrieve service description (MySQL Server)<br>=> systemd.unit.info\[mysqld.service,ActiveEnterTimestamp\] - retrieve the last time the service entered the active state (1562565036283903)<br>=> systemd.unit.info\[dbus.socket,NConnections,Socket\] - collect the number of connections from this socket unit| |systemd.unit.discovery\[<type>\]|<|<|<| |List of systemd units and their details. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**type** - possible values: *all*, *automount*, *device*, *mount*, *path*, *service* (default), *socket*, *swap*, *target*|This item is supported on Linux platform only.|
zh-cn	### Systemd  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |systemd.unit.get\[unit name,<interface>\]|<|<|<| |返回 SystemD Unit 的所有属性.|JSON 对象|**unit name** - Unit 名称 (你可能希望使用监控项原型中的 {\#UNIT.NAME} 宏来发现 Unit 名称)<br>**interface** - Unit 接口类型, 可能的值: *Unit* (缺省值), *Service*, *Socket*, *Device*, *Mount*, *Automount*, *Swap*, *Target*, *Path*|这些监控项只支持 Linux 平台.<br><br> Unit 接口 LoadState, ActiveState 和 UnitFileState 会返回 text 文本和 integer 整形:<br>`"ActiveState":{"state":1,"text":"active"}`| |systemd.unit.info\[unit name,<property>,<interface>\]|<|<|<| |SystemD unit 信息.|String|**unit name** - Unit 名称 (你可能希望使用监控项原型中的 {\#UNIT.NAME} 宏来发现 Unit 名称)<br>**property** - Unit property (比如. ActiveState (缺省值), LoadState, Description)<br>**interface** - Unit  接口类型 (比如 Unit (缺省值), Socket, Service)|这个监控项允许从特定的接口类型 [dbus API](https://www.freedesktop.org/wiki/Software/systemd/dbus/) 中检索特定的属性.<br><br>这些监控项只支持 Linux 平台.<br><br>示例:<br>=> systemd.unit.info\["{\#UNIT.NAME}"\] - 采集发现的 SystemD Uint 的活动状态信息 (active, reloading, inactive, failed, activating, deactivating) <br>=> systemd.unit.info\["{\#UNIT.NAME}",LoadState\] - 采集所发现的 SystemD Uint的负载状态信息<br>=> systemd.unit.info\[mysqld.service,Id\] - 检索指定的 Service technical 名称 (mysqld.service)<br>=> systemd.unit.info\[mysqld.service,Description\] - 检索指定的 Service 描述 (MySQL Server)<br>=> systemd.unit.info\[mysqld.service,ActiveEnterTimestamp\] - 检索 Service 最后一次进入活动状态的时间 (1562565036283903)<br>=> systemd.unit.info\[dbus.socket,NConnections,Socket\] - 从这个socket unit 采集连接数| |systemd.unit.discovery\[<type>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd) 列出 SystemD Unit 的列表及其详细信息.|JSON 对象|**type** - 可能的值: *all*, *automount*, *device*, *mount*, *path*, *service* (缺省值), *socket*, *swap*, *target*|这些监控项只支持 Linux 平台.|

en-us	#### - System requirements
zh-cn	#### - 系统要求

en-us	##### System requirements:  -   *RAM*: 1.5 GB -   *Disk space*: at least 8 GB should be allocated for the virtual     machine.  Zabbix installation CD/DVD boot menu:  ![](../../assets/en/manual/installation_cd_boot_menu1.png){width="600"}  Zabbix appliance contains a Zabbix server (configured and running on MySQL) and a frontend.  Zabbix virtual appliance is available in the following formats:  -   VMWare (.vmx) -   Open virtualization format (.ovf) -   Microsoft Hyper-V 2012 (.vhdx) -   Microsoft Hyper-V 2008 (.vhd) -   KVM, Parallels, QEMU, USB stick, VirtualBox, Xen (.raw) -   KVM, QEMU (.qcow2)  To get started, boot the appliance and point a browser at the IP the appliance has received over DHCP.  ::: noteimportant  DHCP must be enabled on the host.  :::  To get the IP address from inside the virtual machine run:      ip addr show  To access Zabbix frontend, go to **http://<host\_ip>** (for access from the host's browser bridged mode should be enabled in the VM network settings).  ::: notetip If the appliance fails to start up in Hyper-V, you may want to press `Ctrl+Alt+F2` to switch tty sessions. :::
zh-cn	##### 系统需求：  -   *RAM*: 1.5 GB -   *磁盘空间*: 应至少为虚拟机分配 8 GB。  Zabbix 安装 CD/DVD 的 boot 菜单：  ![](../../assets/en/manual/installation_cd_boot_menu1.png){width="600"}  Zabbix Appliance 包含 一个Zabbix server (已配置并在 MySQL 上运行) 及一个前端。  Zabbix Appliance 提供如下格式的虚拟机 image：  -   VMWare (.vmx) -   Open virtualization format (.ovf) -   Microsoft Hyper-V 2012 (.vhdx) -   Microsoft Hyper-V 2008 (.vhd) -   KVM, Parallels, QEMU, USB stick, VirtualBox, Xen (.raw) -   KVM, QEMU (.qcow2)  要开始使用，请 boot Appliance 并通过浏览器访问 Appliance 通过 DHCP 接收的 IP。  ::: noteimportant 必须在主机上启用 DHCP。 :::  在虚拟机内部查看 IP 地址，可以执行：      ip addr show  要访问 Zabbix 前端，可以访问 **http://<host\_ip>** （应在虚机网络设置中启用桥接模式以便从主机的浏览器访问）。  ::: notetip 如果 Appliance 在 Hyper-V 上启动失败，你可以按下 `Ctrl+Alt+F2` 以切换 tty session. :::

en-us	#### system.run and AllowKey  A hypothetical script like 'myscript.sh' may be executed on a host via Zabbix agent in several ways:  1\. As an item key in a passive or active check, for example:  -   system.run\[myscript.sh\] -   system.run\[myscript.sh,wait\] -   system.run\[myscript.sh.nowait\]  Here the user may add "wait", "nowait" or omit the 2nd argument to use its default value in system.run\[\].  2\. As a global script (initiated by user in frontend or API).  A user configures this script in *Administration* → *Scripts*, sets "Execute on: Zabbix agent" and puts "myscript.sh" into the script's "Commands" input field. When invoked from frontend or API the Zabbix server sends to agent:  -   system.run\[myscript.sh,wait\] - up to Zabbix 5.0.4 -   system.run\[myscript.sh\] - since 5.0.5  Here the user does not control the "wait"/"nowait" parameters.  3\. As a remote command from an action. The Zabbix server sends to agent:  -   system.run\[myscript.sh,nowait\]  Here again the user does not control the "wait"/"nowait" parameters.  What that means is if we set AllowKey like:      AllowKey=system.run[myscript.sh]  then  -   system.run\[myscript.sh\] - will be allowed -   system.run\[myscript.sh,wait\], system.run\[myscript.sh,nowait\]     will not be allowed - the script will not be run if invoked as a     step of action  To allow all described variants you may add:      AllowKey=system.run[myscript.sh,*]      DenyKey=system.run[*]  to the agent/agent2 parameters.
zh-cn	#### system.run 和 AllowKey  假设有一个“myscript.sh”这样脚本，它可以通过Zabbix 代理以多种方式在主机上执行：  1\.作为被动或主动检查中的项目键，例如：  - system.run\[myscript.sh\] - system.run\[myscript.sh,wait\] - system.run\[myscript.sh.nowait\]  在这里，用户可以添加“wait”、“nowait”或省略第二个参数，使用system.run\[\]的默认值 。  2\.作为全局脚本（由用户在前端或 API 中启动）。  用户在 *Administration* → *Scripts* 中配置此脚本，设置“在Zabbix agent上执行”并将“myscript.sh”放入脚本的“命令”输入字段。当从前端或 API 调用时，由Zabbix server发送到代理上：  - system.run\[myscript.sh,wait\] - 最高到 Zabbix 5.0.4 - system.run\[myscript.sh\] - 从 5.0.5 开始  这里用户不控制“wait”/“nowait”参数。  3\.作为动作的远程命令。 Zabbix server发送到agent：  - system.run\[myscript.sh,nowait\]  在这里，用户再次不控制“wait”/“nowait”参数。  这意味着如果我们将 AllowKey 设置为：      AllowKey=system.run[myscript.sh]  然后  - system.run\[myscript.sh\] - 将被允许 - system.run\[myscript.sh,wait\], system.run\[myscript.sh,nowait\]将不允许 - 如果作为行动步骤  要允许所有描述的变体，您可以添加：      AllowKey=system.run[myscript.sh,*]     DenyKey=system.run[*]  到 agent/agent2 参数。

en-us	#### - System Services  Systemd services are available:      systemctl list-units zabbix*
zh-cn	#### - 系统服务  在 Systemd 中列举 Zabbix 的 service：      systemctl list-units zabbix*

en-us	##### Tabs for favorite filters  Frequently used sets of filter parameters can be saved in tabs.  To save a new set of filter parameters, open the Home tab, and configure the filter settings, then press the *Save as* button. In a new popup window, define *Filter properties*.  ![problem\_filter0.png](../../../../../assets/en/manual/web_interface/problem_filter0.png)  |Parameter|Description| |---------|-----------| |Name|The name of the filter to display in the tab list.| |Show number of records|Check, if you want the number of problems to be displayed next to the tab name.| |Set custom time period|Check to set specific default time period for this filter set. If set, you will only be able to change the time period for this tab by updating filter settings. For tabs without a custom time period, the time range can be changed by pressing the time selector button in the top right corner (button name depends on selected time interval: This week, Last 30 minutes, Yesterday, etc.).<br>This option is available only for filters in *Monitoring→Problems*.| |From/To|[Time period](/manual/config/visualization/graphs/simple#time_period_selector) start and end in absolute (`Y-m-d H:i:s`) or relative time syntax (`now-1d`). Available, if *Set custom time period* is checked.|  To edit *Filter properties* of an existing filter, press the gear symbol next to the active tab name.  ![problem\_filter2.png](../../../../../assets/en/manual/web_interface/problem_filter2.png)  Notes:  -   To hide a filter, press on the name of the current tab. Press on the     active tab name again to open the filter. -   Filter tabs can be re-arranged by dragging and dropping. -   Keyboard navigation is supported: use arrows to switch between tabs,     press *Enter* to open. -   Pressing the arrow down icon in the upper right corner will open the     full list of saved filter tabs as a drop-down menu.  ::: noteclassic  To share filters, copy and send to others a URL of an active filter. After opening this URL, other users will be able to save this set of parameters as a permanent filter in their Zabbix account.\ See also: [Page parameters](/manual/web_interface/page_parameters). :::  
zh-cn	##### Tabs for favorite filters  Frequently used sets of filter parameters can be saved in tabs.  To save a new set of filter parameters, open the Home tab, and configure the filter settings, then press the *Save as* button. In a new popup window, define *Filter properties*.  ![problem\_filter0.png](../../../../../assets/en/manual/web_interface/problem_filter0.png)  |Parameter|Description| |---------|-----------| |Name|The name of the filter to display in the tab list.| |Show number of records|Check, if you want the number of problems to be displayed next to the tab name.| |Set custom time period|Check to set specific default time period for this filter set. If set, you will only be able to change the time period for this tab by updating filter settings. For tabs without a custom time period, the time range can be changed by pressing the time selector button in the top right corner (button name depends on selected time interval: This week, Last 30 minutes, Yesterday, etc.).<br>This option is available only for filters in *Monitoring→Problems*.| |From/To|[Time period](/manual/config/visualization/graphs/simple#time_period_selector) start and end in absolute (`Y-m-d H:i:s`) or relative time syntax (`now-1d`). Available, if *Set custom time period* is checked.|  To edit *Filter properties* of an existing filter, press the gear symbol next to the active tab name.  ![problem\_filter2.png](../../../../../assets/en/manual/web_interface/problem_filter2.png)  Notes:  -   To hide a filter, press on the name of the current tab. Press on the     active tab name again to open the filter. -   Filter tabs can be re-arranged by dragging and dropping. -   Keyboard navigation is supported: use arrows to switch between tabs,     press *Enter* to open. -   Pressing the arrow down icon in the upper right corner will open the     full list of saved filter tabs as a drop-down menu.  ::: noteclassic  To share filters, copy and send to others a URL of an active filter. After opening this URL, other users will be able to save this set of parameters as a permanent filter in their Zabbix account.\ See also: [Page parameters](/manual/web_interface/page_parameters). :::  

en-us	##### Tabs for favorite filters  Frequently used sets of filter parameters can be saved in tabs.  To save a new set of filter parameters, open the main tab, and configure the filter settings, then press the *Save as* button. In a new popup window, define *Filter properties*.  ![problem\_filter0.png](../../../../../assets/en/manual/web_interface/filter_properties.png)  |Parameter|Description| |--|--------| |*Name*|The name of the filter to display in the tab list.| |*Show number of records*|Check, if you want the number of problems to be displayed next to the tab name.| |*Set custom time period*|Check to set specific default time period for this filter set. If set, you will only be able to change the time period for this tab by updating filter settings. For tabs without a custom time period, the time range can be changed by pressing the time selector button in the top right corner (button name depends on selected time interval: This week, Last 30 minutes, Yesterday, etc.).<br>This option is available only for filters in *Monitoring→Problems*.| |*From/To*|[Time period](/manual/config/visualization/graphs/simple#time_period_selector) start and end in absolute (`Y-m-d H:i:s`) or relative time syntax (`now-1d`). Available, if *Set custom time period* is checked.|  When saved, the filter is created as a named filter tab and immediately activated.  To edit the filter properties of an existing filter, press the gear symbol next to the active tab name.  ![problem\_filter2.png](../../../../../assets/en/manual/web_interface/filter_properties_link_.png)  Notes:  -   To hide the filter area, click on the name of the current tab. Click on the     active tab name again to open the filter area again. -   Keyboard navigation is supported: use arrows to switch between tabs,     press *Enter* to open. -   The left/right buttons above the filter may be used to switch between     saved filters. Alternatively, the downward pointing button opens a drop-down      menu with all saved filters and you can click on the one you need. -   Filter tabs can be re-arranged by dragging and dropping. -   If the settings of a saved filter have been changed (but not saved), a green     dot is displayed after the filter name. To update the filter according to the new     settings, click on the *Update* button, which is displayed instead of the     *Save as* button. -   Current filter settings are remembered in the user profile. When the user     opens the page again, the filter settings will have stayed the same.  ::: noteclassic To share filters, copy and send to others a URL of an active filter. After opening this URL, other users will be able to save this set of parameters as a permanent filter in their Zabbix account.\ See also: [Page parameters](/manual/web_interface/page_parameters). :::
zh-cn	##### “收藏夹”筛选器的选项卡  常用的过滤器参数集可以保存在选项卡中。  若要存储一组新的过滤器参数， 请打开主选项卡并配置过滤器设置，然后按 *另存为* 按钮。在新的弹出窗口中，定义 *过滤器属性*。  ![problem\_filter0.png](../../../../../assets/en/manual/web_interface/problem_filter0.png)  |参数|描述| |---------|-----------| |名称|要在选项卡列表中显示的过滤器的名称。| |显示记录数|如果您希望问题的数量显示在选项卡名称旁边，请勾选。| |设置自定义时间段|检查以设置此过滤器集的特定默认时间段。如果设置了，则只能通过更新过滤器设置来更改此选项卡的时间段。对于没有自定义时间段的选项卡，时间范围可以通过按右上角的时间选择按钮来更改 (按钮名称取决于所选的时间间隔:本周、过去30分钟、昨天等).<br>此选项仅适用于 *监视→问题*中的过滤器。| |从/到|[时间段](/manual/config/visualization/graphs/simple#time_period_selector) 以绝对(`Y-m-d H:i:s`)或相对时间语法(`now-1d`)定义开始和结束, *设置自定义时间段* 选中则可用。|  保存后，过滤器将创建为命名过滤器选项卡并立即激活。  要编辑现有过滤器的*筛选属性* ，请按活动选项卡名称旁边的齿轮符号。  ![problem\_filter2.png](../../../../../assets/en/manual/web_interface/problem_filter2.png)  注意： - · 要隐藏过滤器，请按当前选项卡的名称。 再次按下活动选项卡名称打开过滤器。 - · 可以通过拖放来重新排列过滤器选项卡。 - · 支持键盘导航： 使用箭头在选项卡之间切换，按下 *Enter* 打开。 - · 按右上角的向下箭头图标将打开已保存过滤器选项卡的完整列表作为下拉菜单。 - · 可以通过拖放重新排列过滤器选项卡。 - · 如果已保存过滤器的设置已更改（但未保存），过滤器名称后会显示一个绿点。 要根据新设置更新过滤器，请单击显示的 *更新* 按钮，而不是 *另存为* 按钮。 - · 当前过滤器设置被记住在用户配置文件中。 当用户再次打开页面时，过滤器设置将保持不变。  ::: noteclassic  若要共享过滤器，请复制活动过滤器的 URL 并将其发送给其他人。打开此 URL 后，其他用户将能够将这组参数作为永久过滤器保存在其 Zabbix 帐户中。   另请参见：[页面参数](/manual/web_interface/page_parameters)。  :::

en-us	### Tag based permission  The tag based permission object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**groupid**<br>(required)|string|ID of the host group to add permission to.| |**tag**|string|Tag name.| |**value**|string|Tag value.|
zh-cn	### 基于标签的权限  基于标签的权限对象具有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**groupid**<br>(required)|string|要添加权限的主机组的ID.| |**tag**|string|标签名.| |**value**|string|标签值.|

en-us	### Tag based permission  The tag based permission object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**groupid**<br>(required)|string|ID of the host group to add permission to.| |**tag**|string|Tag name.| |**value**|string|Tag value.|
zh-cn	### 基于标签的权限  基于标签的权限对象具有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**groupid**<br>(required)|string|要添加权限的主机组的ID.| |**tag**|string|标签名.| |**value**|string|标签值.|

en-us	#### Tags  -   Performance – device family MIBs provide a way to monitor CPU and     memory items; -   Fault - device family MIBs provide a way to monitor at least one     temperature sensor; -   Inventory – device family MIBs provide a way to collect at least the     device serial number and model name; -   Certified – all three main categories above are covered.
zh-cn	 #### 标签  -   Performance – 设备系列MIB提供了一种监控CPU和内存监控项的方法; -   Fault - 设备系列MIB提供监控至少一个温度传感器的方法; -   Inventory – 设备系列MIB提供了至少收集设备序列号和型号名称的方法; -   Certified – 涵盖上述所有三个主要类别。

en-us	# task.create
zh-cn	# task.create

en-us	# task.get
zh-cn	# task.get

en-us	##### Task manager  If the 'Allow manual close' setting is enabled for trigger, then it's possible to manually close problem events generated by the trigger. This is done in the frontend when [updating a problem](/manual/acknowledges#updating_problems). The event is not closed directly – instead a 'close event' task is created, which is handled by the task manager shortly. The task manager will generate a corresponding OK event and the problem event will be closed.
zh-cn	##### 任务管理器  如果触发器启用了“允许手动关闭”的设置，就可能手动关闭触发器生成的问题事件。这在[问题升级中](/manual/acknowledges#updating_problems)由前端完成。事件不是直接关闭的——相反，会生成一个“关闭事件”的任务，很快会由任务管理器处理。问题事件会被关闭，任务管理器会生成对应的正常事件。

en-us	# > Task object  The following objects are directly related to the `task` API.  The task object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |taskid|string|*(readonly)* ID of the task.| |**type**<br>(required)|integer|Type of the task.<br><br>Possible values:<br>1 - Diagnostic information;<br>6 - Check now.| |status|integer|*(readonly)* Status of the task.<br><br>Possible values:<br>1 - new task;<br>2 - task in progress;<br>3 - task is completed;<br>4 - task is expired.| |clock|timestamp|*(readonly)* Time when the task was created.| |ttl|integer|*(readonly)* The time in seconds after which task expires.| |proxy\_hostid|string|ID of the proxy about which diagnostic information statistic is collected.<br>Ignored for 'Check now' tasks.| |**request**<br>(required)|object|Task request object according to the task type:<br>Object of 'Check now' task is [described in detail below](/manual/api/reference/task/object#check_now_request_object);<br>Object of 'Diagnostic information' task is [described in detail below](/manual/api/reference/task/object#diagnostic_information_request_object).| |result|object|*(readonly)* Result object of the diagnostic information task. May contain NULL if result is not yet ready. Result object is [described in detail below](/manual/api/reference/task/object#statistic_result_object).|
zh-cn	# > 任务对象  以下对象都是与 `task`直接相关的API。  任务对象具有以下属性:  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |taskid|string|*(只读)* 任务的ID。| |**type**<br>(必须)|integer|任务的类型.<br><br>可能的值：<br>1 - 诊断信息;<br>6 - 立即检查。| |status|integer|*(只读)* 任务状态。<br><br>可能的值：<br>1 - 新任务；<br>2 - 进行中的任务；<br>3 - 已完成的任务；<br>4 - 过期的任务。| |clock|timestamp|*(只读)* 任务创建时间。| |ttl|integer|*(只读)* 任务过期时间（秒）。| |proxy\_hostid|string|被统计诊断信息的代理ID。<br>不包含“立即检查”任务。| |**request**<br>(必须)|object|根据任务类型的任务请求对象：<br>“立即检查”任务的对象为[详细描述如下](/manual/api/reference/task/object#check_now_request_object)；<br>“诊断信息”任务的对象为[详细描述如下](/manual/api/reference/task/object#diagnostic_information_request_object)。| |result|object|*(只读)* 诊断信息任务的结果对象。如果结果还未准备好，可能会包含NULL。结果对象为[详细描述如下](/manual/api/reference/task/object#statistic_result_object)。|

en-us	# > Task object  The following objects are directly related to the `task` API.  The task object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |taskid|string|*(readonly)* ID of the task.| |**type**<br>(required)|integer|Type of the task.<br><br>Possible values:<br>1 - Diagnostic information;<br>6 - Check now.| |status|integer|*(readonly)* Status of the task.<br><br>Possible values:<br>1 - new task;<br>2 - task in progress;<br>3 - task is completed;<br>4 - task is expired.| |clock|timestamp|*(readonly)* Time when the task was created.| |ttl|integer|*(readonly)* The time in seconds after which task expires.| |proxy\_hostid|string|ID of the proxy about which diagnostic information statistic is collected.<br>Ignored for 'Check now' tasks.| |**request**<br>(required)|object|Task request object according to the task type:<br>Object of 'Check now' task is [described in detail below](/manual/api/reference/task/object#check_now_request_object);<br>Object of 'Diagnostic information' task is [described in detail below](/manual/api/reference/task/object#diagnostic_information_request_object).| |result|object|*(readonly)* Result object of the diagnostic information task. May contain NULL if result is not yet ready. Result object is [described in detail below](/manual/api/reference/task/object#statistic_result_object).|
zh-cn	# > 任务对象  以下对象都是与 `task`直接相关的API。  任务对象具有以下属性:  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |taskid|string|*(只读)* 任务的ID。| |**type**<br>(必须)|integer|任务的类型.<br><br>可能的值：<br>1 - 诊断信息;<br>6 - 立即检查。| |status|integer|*(只读)* 任务状态。<br><br>可能的值：<br>1 - 新任务；<br>2 - 进行中的任务；<br>3 - 已完成的任务；<br>4 - 过期的任务。| |clock|timestamp|*(只读)* 任务创建时间。| |ttl|integer|*(只读)* 任务过期时间（秒）。| |proxy\_hostid|string|被统计诊断信息的代理ID。<br>不包含“立即检查”任务。| |**request**<br>(必须)|object|根据任务类型的任务请求对象：<br>“立即检查”任务的对象为[详细描述如下](/manual/api/reference/task/object#check_now_request_object)；<br>“诊断信息”任务的对象为[详细描述如下](/manual/api/reference/task/object#diagnostic_information_request_object)。| |result|object|*(只读)* 诊断信息任务的结果对象。如果结果还未准备好，可能会包含NULL。结果对象为[详细描述如下](/manual/api/reference/task/object#statistic_result_object)。|

en-us	#### Tasks  Interact with Zabbix server task manager, creating tasks and retrieving response.  [Task API](/manual/api/reference/task)
zh-cn	#### 任务  与Zabbix Server task manager 交互，创建任务并检索响应。  [Task API](/manual/api/reference/task)

en-us	# Task  This class is designed to work with tasks (such as checking items or low-level discovery rules without config reload).  Object references:\  -   [Task](/manual/api/reference/task/object) -   ['Check now' request     object](/manual/api/reference/task/object#check_now_request_object) -   ['Diagnostic information' request     object](/manual/api/reference/task/object#diagnostic_information_request_object) -   [Statistic request     object](/manual/api/reference/task/object#statistic_request_object) -   [Statistic result     object](/manual/api/reference/task/object#statistic_result_object)  Available methods:\  -   [task.create](/manual/api/reference/task/create) - creating new     tasks -   [task.get](/manual/api/reference/task/get) - retrieving tasks
zh-cn	# 任务  此类用于管理任务 (例如检查监控项或不需要重新加载的低级别自动发现规则).  参考对象：  -   [任务](/manual/api/reference/task/object) -   [“立即检查”请求对象](/manual/api/reference/task/object#check_now_request_object) -   [‘诊断信息’请求对象](/manual/api/reference/task/object#diagnostic_information_request_object) -   [统计请求对象](/manual/api/reference/task/object#statistic_request_object) -   [统计结果对象](/manual/api/reference/task/object#statistic_result_object)  可用方法：  -   [task.create](/manual/api/reference/task/create) - 创建新的任务 -   [task.get](/manual/api/reference/task/get) - 检索任务

en-us	#### template  Changes:\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.create`, `template.update`, `template.delete`, `template.massadd`, `template.massupdate`, `template.massremove`: added strict validation of the methods parameters.\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.create`, `template.update`, `template.massadd`, `template.massupdate`: dropped support of parameter `hosts`.\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.massremove`: dropped support of parameter `hostids`.
zh-cn	 #### 模板  变更：\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.create`，`template.update`，`template.delete`，`template.massadd`，`template.massupdate`，`template.massremove`：添加了对方法参数的严格校验。\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.create`，`template.update`，`template.massadd`，`template.massupdate`：删除对参数`hosts`的支持。\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `template.massremove`：删除对参数`hostids`的支持。

en-us	# template.create
zh-cn	# template.create

en-us	#### templatedashboard Changes:\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) added support of new widget type `item`.\
zh-cn	 #### 模板化仪表盘  变更：\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) 添加对新控件类型`item`的支持。\

en-us	# templatedashboard.create
zh-cn	# 创建模板仪表盘

en-us	# templatedashboard.delete
zh-cn	# 删除模板仪表盘

en-us	# templatedashboard.get
zh-cn	# 检索模板仪表盘

en-us	# > Template dashboard object  The following objects are directly related to the `templatedashboard` API.
zh-cn	# > 模版仪表盘对象  以下对象与 `templatedashboard` API 直接相关。

en-us	### Template dashboard page  The template dashboard page object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboard\_pageid|string|*(readonly)* ID of the dashboard page.| |name|string|Dashboard page name.<br><br>Default: empty string.| |display\_period|integer|Dashboard page display period (in seconds).<br><br>Possible values: 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 0 (will use the default page display period).| |widgets|array|Array of the [template dashboard widget](object#template_dashboard_widget) objects.|
zh-cn	### 模版仪表盘页面  模板仪表板页面对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |dashboard\_pageid|string|*(只读)* 仪表盘页面的ID。| |name|string|仪表盘页面的名字。<br><br>默认值： 空的字符串。| |display\_period|integer|仪表盘页面显示时间（秒）。<br><br>可能的值： 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>默认值： 0 (将一直使用默认的页面显示)。| |widgets|array|[模版仪表盘组件](object#template_dashboard_widget)对象的数组。|

en-us	### Template dashboard page  The template dashboard page object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |dashboard\_pageid|string|*(readonly)* ID of the dashboard page.| |name|string|Dashboard page name.<br><br>Default: empty string.| |display\_period|integer|Dashboard page display period (in seconds).<br><br>Possible values: 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 0 (will use the default page display period).| |widgets|array|Array of the [template dashboard widget](object#template_dashboard_widget) objects.|
zh-cn	### 模版仪表盘页面  模板仪表板页面对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |dashboard\_pageid|string|*(只读)* 仪表盘页面的ID。| |name|string|仪表盘页面的名字。<br><br>默认值： 空的字符串。| |display\_period|integer|仪表盘页面显示时间（秒）。<br><br>可能的值： 0, 10, 30, 60, 120, 600, 1800, 3600.<br><br>默认值： 0 (将一直使用默认的页面显示)。| |widgets|array|[模版仪表盘组件](object#template_dashboard_widget)对象的数组。|

en-us	##### Template dashboard tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |dashboards| |\-| | |Root element for template dashboards.| | |uuid|x|`string`| |Unique identifier for this dashboard.| | |name|x|`string`| |Template dashboard name.| | |display period|\-|`integer`| |Display period of dashboard pages.| | |auto\_start|\-|`string`|0 - no<br>1 - yes|Slideshow auto start.| |pages| |\-| | |Root element for template dashboard pages.| | |name|\-|`string`| |Page name.| | |display period|\-|`integer`| |Page display period.| | |sortorder|\-|`integer`| |Page sorting order.| |widgets| |\-| | |Root element for template dashboard widgets.| | |type|x|`string`| |Widget type.| | |name|\-|`string`| |Widget name.| | |x|\-|`integer`|0-23|Horizontal position from the left side of the template dashboard.| | |y|\-|`integer`|0-62|Vertical position from the top of the template dashboard.| | |width|\-|`integer`|1-24|Widget width.| | |height|\-|`integer`|2-32|Widget height.| | |hide\_header|\-|`string`|0 - no<br>1 - yes|Hide widget header.| |fields| |\-| | |Root element for the template dashboard widget fields.| | |type|x|`string`|0 - INTEGER<br>1 - STRING<br>3 - HOST<br>4 - ITEM<br>5 - ITEM\_PROTOTYPE<br>6 - GRAPH<br>7 - GRAPH\_PROTOTYPE|Widget field type.| | |name|x|`string`| |Widget field name.| | |value|x|mixed| |Widget field value, depending on the field type.|
zh-cn	##### 模板仪表盘标签  |元素|元素属性|是否必须|类型|使用范围^**[1](#footnotes)**^|描述| |-------|----------------|--------|----|--------------------------|-----------| |dashboards|<|\-|<|<|模板仪表板的根元素。| |<|uuid|x|`string`|<|此仪表板的唯一标识符。| |<|name|x|`string`|<|模板仪表盘的名字。| |<|display period|\-|`integer`|<|仪表盘页面的显示周期。| |<|auto\_start|\-|`string`|0 - no<br>1 - yes|幻灯片自动开始。| |pages|<|\-|<|<|模板仪表板页面的根元素。| |<|name|\-|`string`|<|页面名称。| |<|display period|\-|`integer`|<|页面显示。| |<|sortorder|\-|`integer`|<|页面排序顺序。| |widgets|<|\-|<|<|模板仪表板小部件的根元素。| |<|type|x|`string`|<|小部件类型。| |<|name|\-|`string`|<|小部件名称。| |<|x|\-|`integer`|0-23|模板仪表板左侧的水平位置。| |<|y|\-|`integer`|0-62|从模板仪表板顶部开始的垂直位置。| |<|width|\-|`integer`|1-24|小部件宽度。| |<|height|\-|`integer`|2-32|小部件的高度。| |<|hide\_header|\-|`string`|0 - no<br>1 - yes|隐藏小部件标题。| |fields|<|\-|<|<|模板仪表板小部件字段的根元素。| |<|type|x|`string`|0 - INTEGER<br>1 - STRING<br>3 - HOST<br>4 - ITEM<br>5 - ITEM\_PROTOTYPE<br>6 - GRAPH<br>7 - GRAPH\_PROTOTYPE|小部件字段类型。| |<|name|x|`string`|<|小部件字段名。| |<|value|x|mixed|<|小部件字段值，取决于字段类型。|

en-us	### Template dashboard  The template dashboard object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboardid|string|*(readonly)* ID of the template dashboard.| |**name**<br>(required)|string|Name of the template dashboard.| |**templateid**<br>(required)|string|ID of the template the dashboard belongs to.| |display\_period|integer|Default page display period (in seconds).<br><br>Possible values: 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 30.| |auto\_start|integer|Auto start slideshow.<br><br>Possible values:<br>0 - do not auto start slideshow;<br>1 - *(default)* auto start slideshow.| |uuid|string|Universal unique identifier, used for linking imported template dashboards to already existing ones. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 模板仪表盘  模板仪表板对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |dashboardid|string|*(只读)* 模板仪表盘的ID。| |**name**<br>(必须)|string|模板仪表盘的名字。| |**templateid**<br>(必须)|string|仪表盘所属模板的ID。| |display\_period|integer|默认页面显示时间（秒）。<br><br>可能的值： 10, 30, 60, 120, 600, 1800, 3600.<br><br>默认值： 30.| |auto\_start|integer|自动启动幻灯片放映。<br><br>可能的值：<br>0 - 不自动启动幻灯片放映；<br>1 - *(默认值)* 自动启动幻灯片放映| |uuid|string|通用唯一标识符，用于将导入的模板仪表板链接到现有的仪表板。如果没有给出则自动生成。<br><br>对于更新操作，此字段为*只读*.|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Template dashboard  This class is designed to work with template dashboards.  Object references:\  -   [Template dashboard](/manual/api/reference/templatedashboard/object) -   [Template dashboard     page](/manual/api/reference/templatedashboard/object#template_dashboard_page) -   [Template dashboard     widget](/manual/api/reference/templatedashboard/object#template_dashboard_widget) -   [Template dashboard widget     field](/manual/api/reference/templatedashboard/object#template_dashboard_widget_field)  Available methods:\  -   [templatedashboard.create](/manual/api/reference/templatedashboard/create) -     creating new template dashboards -   [templatedashboard.delete](/manual/api/reference/templatedashboard/delete) -     deleting template dashboards -   [templatedashboard.get](/manual/api/reference/templatedashboard/get) -     retrieving template dashboards -   [templatedashboard.update](/manual/api/reference/templatedashboard/update) -     updating template dashboards
zh-cn	# 模版仪表盘  此类设计用于使用模板仪表盘。  对象引用:\  -   [模版仪表盘](/manual/api/reference/templatedashboard/object) -   [模版仪表盘页面](/manual/api/reference/templatedashboard/object#template_dashboard_page) -   [模版仪表盘组件](/manual/api/reference/templatedashboard/object#template_dashboard_widget) -   [模版仪表盘组件字段](/manual/api/reference/templatedashboard/object#template_dashboard_widget_field)  可用方法:\  -   [templatedashboard.create](/manual/api/reference/templatedashboard/create) -     创建一个新的模版仪表盘 -   [templatedashboard.delete](/manual/api/reference/templatedashboard/delete) -     删除模版仪表盘 -   [templatedashboard.get](/manual/api/reference/templatedashboard/get) -     检索模版仪表盘 -   [templatedashboard.update](/manual/api/reference/templatedashboard/update) -     更新模版仪表盘

en-us	# templatedashboard.update
zh-cn	# 更新模板仪表盘

en-us	### Template dashboard widget  The template dashboard widget object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |widgetid|string|*(readonly)* ID of the dashboard widget.| |**type**<br>(required)|string|Type of the dashboard widget.<br><br>Possible values:<br>clock - Clock;<br>graph - Graph (classic);<br>graphprototype - Graph prototype;<br>item - Item value;<br>plaintext - Plain text;<br>url - URL;| |name|string|Custom widget name.| |x|integer|A horizontal position from the left side of the dashboard.<br><br>Valid values range from 0 to 23.| |y|integer|A vertical position from the top of the dashboard.<br><br>Valid values range from 0 to 62.| |width|integer|The widget width.<br><br>Valid values range from 1 to 24.| |height|integer|The widget height.<br><br>Valid values range from 2 to 32.| |view\_mode|integer|The widget view mode.<br><br>Possible values:<br>0 - (default) default widget view;<br>1 - with hidden header;| |fields|array|Array of the [template dashboard widget field](object#template_dashboard_widget_field) objects.|
zh-cn	### 模版仪表盘组件  模板仪表板组件对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |widgetid|string|*(只读)* 仪表盘组件的ID。| |**type**<br>(必须)|string|仪表盘组件的类型<br><br>可能的值：<br>clock - 时钟；<br>graph - 图形（经典）；<br>graphprototype - 图形原型；<br>item - 监控项的值；<br>plaintext - 纯文本；<br>url - URL;| |name|string|自定义组件名称。| |x|integer|仪表板左侧的水平位置。<br><br>有效值的范围为0到23。| |y|integer|仪表板顶部的垂直位置。<br><br>有效值的范围为0到62。| |width|integer|组件的宽度。<br><br>有效值的范围为1到24.| |height|integer|组件的高度。<br><br>有效值的范围为2到32。| |view\_mode|integer|组件视图模式。<br><br>可能的值：<br>0 - (默认值) 默认组件视图。<br>1 - 隐藏标题；| |fields|array|[模版仪表盘组件字段](object#template_dashboard_widget_field)对象的数组。|

en-us	### Template dashboard widget  The template dashboard widget object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |widgetid|string|*(readonly)* ID of the dashboard widget.| |**type**<br>(required)|string|Type of the dashboard widget.<br><br>Possible values:<br>clock - Clock;<br>graph - Graph (classic);<br>graphprototype - Graph prototype;<br>item - Item value;<br>plaintext - Plain text;<br>url - URL;| |name|string|Custom widget name.| |x|integer|A horizontal position from the left side of the dashboard.<br><br>Valid values range from 0 to 23.| |y|integer|A vertical position from the top of the dashboard.<br><br>Valid values range from 0 to 62.| |width|integer|The widget width.<br><br>Valid values range from 1 to 24.| |height|integer|The widget height.<br><br>Valid values range from 2 to 32.| |view\_mode|integer|The widget view mode.<br><br>Possible values:<br>0 - (default) default widget view;<br>1 - with hidden header;| |fields|array|Array of the [template dashboard widget field](object#template_dashboard_widget_field) objects.|
zh-cn	### 模版仪表盘组件  模板仪表板组件对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |widgetid|string|*(只读)* 仪表盘组件的ID。| |**type**<br>(必须)|string|仪表盘组件的类型<br><br>可能的值：<br>clock - 时钟；<br>graph - 图形（经典）；<br>graphprototype - 图形原型；<br>item - 监控项的值；<br>plaintext - 纯文本；<br>url - URL;| |name|string|自定义组件名称。| |x|integer|仪表板左侧的水平位置。<br><br>有效值的范围为0到23。| |y|integer|仪表板顶部的垂直位置。<br><br>有效值的范围为0到62。| |width|integer|组件的宽度。<br><br>有效值的范围为1到24.| |height|integer|组件的高度。<br><br>有效值的范围为2到32。| |view\_mode|integer|组件视图模式。<br><br>可能的值：<br>0 - (默认值) 默认组件视图。<br>1 - 隐藏标题；| |fields|array|[模版仪表盘组件字段](object#template_dashboard_widget_field)对象的数组。|

en-us	# template.delete
zh-cn	# template.delete

en-us	#### Template design  Templates were designed with the following in mind:  -   User macros are used as much as possible so triggers can be tuned by     the user; -   Low-level discovery is used as much as possible to minimize the     number of unsupported items; -   All templates depend on Template ICMP Ping so all devices are also     checked by ICMP; -   Items don't use any MIBs - SNMP OIDs are used in items and low-level     discoveries. So it's not necessary to load any MIBs into Zabbix for     templates to work; -   Loopback network interfaces are filtered when discovering as well as     interfaces with ifAdminStatus = down(2); -   64bit counters are used from IF-MIB::ifXTable where possible. If it     is not supported, default 32bit counters are used instead.  All discovered network interfaces have a trigger that monitors its operational status (link), for example:     ```     {$IFCONTROL:"{#IFNAME}"}=1 and last(/Alcatel Timetra TiMOS SNMP/net.if.status[ifOperStatus.{#SNMPINDEX}])=2 and (last(/Alcatel Timetra TiMOS SNMP/net.if.status[ifOperStatus.{#SNMPINDEX}],#1)<>last(/Alcatel Timetra TiMOS SNMP/net.if.status[ifOperStatus.{#SNMPINDEX}],#2))    ```  -   If you do no want to monitor this condition for a specific     interface create a user macro with context with the value 0. For example:  ![](../../../../assets/en/manual/config/template_ifcontrol.png)  where Gi0/0 is {\#IFNAME}. That way the trigger is not used any more for this specific interface.  -   You can also change the default behavior for all triggers not to fire and activate this trigger only to limited number of interfaces like uplinks:  ![](../../../../assets/en/manual/config/template_ifcontrol2.png)
zh-cn	#### 模板设计  模板的设计考虑了以下几点：  -   尽可能多的使用用户宏，以便用户可以调整触发器； -   尽可能使用底层自动发现，以尽量减少不受支持的监控项的数量； -   所有模板都依赖于模板 ICMP Ping，因此所有设备也由 ICMP 检查； -   监控项不使用任何 MIB - SNMP OID 用于监控项和底层自动发现。 因此，无需将任何 MIB 加载到 Zabbix 中即可使模板正常工作； -   环回网络接口在发现时被过滤以及ifAdminStatus = down(2)的接口; -   尽可能使用 IF-MIB::ifXTable 中的 64 位计数器。 如果不支持，则使用默认的 32 位计数器。  所有发现的网络接口都有一个触发器来监控其运行状态（链接），例如：     ```    {$IFCONTROL:"{#IFNAME}"}=1 and last(/Alcatel Timetra TiMOS SNMP/net.if.status[ifOperStatus.{#SNMPINDEX}])=2 and (last(/Alcatel Timetra TiMOS SNMP/net. if.status[ifOperStatus.{#SNMPINDEX}],#1)<>last(/Alcatel Timetra TiMOS SNMP/net.if.status[ifOperStatus.{#SNMPINDEX}],#2))    ```  -   如果您不想监控特定接口的这种情况，请创建一个上下文值为 0 的用户宏。例如：  ![](../../../../assets/en/manual/config/template_ifcontrol.png)  其中 Gi0/0 是 {\#IFNAME}。 这样触发器就不再用于此特定接口。  -   您还可以更改所有触发器的默认行为，使其不触发并仅对有限数量的接口（如上行链路）激活此触发器：  ![](../../../../assets/en/manual/config/template_ifcontrol2.png)

en-us	# template.get
zh-cn	# 检索模板

en-us	##### Template graph tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |uuid|x|`string`| |Unique identifier for this graph.| | |name|x|`string`| |Graph name.| | |width|\-|`integer`|20-65535 (default: 900)|Graph width, in pixels. Used for preview and for pie/exploded graphs.| | |height|\-|`integer`|20-65535 (default: 200)|Graph height, in pixels. Used for preview and for pie/exploded graphs.| | |yaxismin|\-|`double`|Default: 0|Value of Y axis minimum.<br><br>Used if 'ymin\_type\_1' is FIXED.| | |yaxismax|\-|`double`|Default: 0|Value of Y axis maximum.<br><br>Used if 'ymax\_type\_1' is FIXED.| | |show\_work\_period|\-|`string`|0 - NO<br>1 - YES (default)|Highlight non-working hours.<br><br>Used by normal and stacked graphs.| | |show\_triggers|\-|`string`|0 - NO<br>1 - YES (default)|Display simple trigger values as a line.<br><br>Used by normal and stacked graphs.| | |type|\-|`string`|0 - NORMAL (default)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Graph type.| | |show\_legend|\-|`string`|0 - NO<br>1 - YES (default)|Display graph legend.| | |show\_3d|\-|`string`|0 - NO (default)<br>1 - YES|Enable 3D style.<br><br>Used by pie and exploded pie graphs.| | |percent\_left|\-|`double`|Default:0|Show the percentile line for left axis.<br><br>Used only for normal graphs.| | |percent\_right|\-|`double`|Default:0|Show the percentile line for right axis.<br><br>Used only for normal graphs.| | |ymin\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Minimum value of Y axis.<br><br>Used by normal and stacked graphs.| | |ymax\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Maximum value of Y axis.<br><br>Used by normal and stacked graphs.| |ymin\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymin\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |ymax\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymax\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |graph\_items| |x| | |Root element for graph items.| | |sortorder|\-|`integer`| |Draw order. The smaller value is drawn first. Can be used to draw lines or regions behind (or in front of) another.| | |drawtype|\-|`string`|0 - SINGLE\_LINE (default)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Draw style of the graph item.<br><br>Used only by normal graphs.| | |color|\-|`string`| |Element color (6 symbols, hex).| | |yaxisside|\-|`string`|0 - LEFT (default)<br>1 - RIGHT|Side of the graph where the graph item's Y scale will be drawn.<br><br>Used by normal and stacked graphs.| | |calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG (default)<br>4 - MAX<br>7 - ALL (minimum, average and maximum; used only by simple graphs)<br>9 - LAST (used only by pie and exploded pie graphs)|Data to draw if more than one value exists for an item.| | |type|\-|`string`|0 - SIMPLE (default)<br>2 - GRAPH\_SUM (value of the item represents the whole pie; used only by pie and exploded pie graphs)|Graph item type.| |item| |x| | |Individual item.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.|
zh-cn	##### 模板图形标签  |元素|元素属性|是否必须|类型|适用范围^**[1](#footnotes)**^|描述| |-------|----------------|--------|----|--------------------------|-----------| |graphs|<|\-|<|<|图形的根元素。| |<|uuid|x|`string`|<|此图形的唯一标识符。| |<|name|x|`string`|<|图形的名称。| |<|width|\-|`integer`|20-65535 (默认: 900)|图形宽度，以像素为单位。 用于预览和饼图/分解图。| |<|height|\-|`integer`|20-65535 (默认: 200)|图形高度，以像素为单位。 用于预览和饼图/分解图。| |<|yaxismin|\-|`double`|默认: 0|Y轴最小值。 <br><br>当'ymin\_type\_1'为固定值时使用。| |<|yaxismax|\-|`double`|默认: 0|Y轴最大值。 <br><br>当'ymax\_type\_1'为固定值时使用。| |<|show\_work\_period|\-|`string`|0 - NO<br>1 - YES(默认)|突出显示非工作时间。 <br><br>用于普通图和堆叠图。| |<|show\_triggers|\-|`string`|0 - NO<br>1 - YES(默认)|将简单的触发值显示为一行。 <br><br>用于普通图和堆叠图。| |<|type|\-|`string`|0 - NORMAL(默认)<br>1 - STACKED<br>2 - PIE<br>3 - expanded |图类型。| |<|show\_legend|\-|`string`|0 - NO<br>1 - YES(默认)|显示图形图例。| |<|show\_3d|\-|`string`|0 - NO(默认)<br>1 - YES|启用3D样式。 <br><br>用于饼图和分解饼图。| |<|percent\_left|\-|`double`|默认:0|显示左轴的百分位线。 <br><br>仅用于普通图形。| |<|percent\_right|\-|`double`|默认:0|显示右轴的百分位线。 <br><br>仅用于普通图形。| |<|ymin\_type\_1|\-|`string`|0 - calculate(默认值)<br>1 - FIXED<br>2 - ITEM| Y轴的最小值。 <br><br>用于普通图和堆叠图。| |<|ymax\_type\_1|\-|`string`|0 - calculate(默认值)<br>1 - FIXED<br>2 - ITEM| Y轴的最大值。 <br><br>用于普通图和堆叠图。| |ymin\_item\_1|<|\-|<|<|个别监控项的细节。 <br><br>当'ymin\_type\_1'为ITEM时需要。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。| |ymax\_item\_1|<|\-|<|<|个别监控项的细节。 <br><br>当'ymax\_type\_1'为ITEM时需要。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。| |graph\_items|<|x|<|<|图形项的根元素。| |<|sortorder|\-|`integer`|<|画出顺序。 先画出较小的值。 可用于在另一个线或区域后面(或前面)画线或区域。| |<|drawtype|\-|`string`|0 - SINGLE\_LINE(默认)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - dot \_LINE<br>4 -虚线\_LINE<br>5 -渐变\_LINE|图形项的绘制风格。 <br><br>仅用于普通图形。| |<|color|\-|`string`|<|元素颜色(6个符号，十六进制)。| |<|yaxisside|\-|`string`|0 - LEFT(默认)<br>1 - RIGHT|图形项的Y比例将被绘制的部分。 <br><br>用于普通图和堆叠图。| |<|calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG(默认值)<br>4 - MAX<br>7 - ALL(最小值，平均值和最大值; <br>9 - LAST(仅用于饼图和分解饼图)|表示一个监控项存在多个值的数据。| |<|type|\-|`string`|0 - SIMPLE(默认)<br>2 - GRAPH\_SUM(监控项值代表整个饼图; 仅用于饼图和分解饼图)|图形监控项类型。| |item|<|x|<|<|单独监控项。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。|

en-us	### Template linking more visible  To make template linking more visible, it is now placed in the first tab of the host, host prototype and template configuration forms and host/template mass update forms.  ![](../../../assets/en/manual/introduction/template_linking_first_tab.png)  Consequently, a separate tab for template linking has been removed from all the respective forms.  In a related development, in host prototype configuration the fields for host group/host group prototype selection have also been moved from a separate tab to the first tab.
zh-cn	### 模板链接更明显  为了使模板链接更加可见，现在将其放置在主机、主机原型和模板配置表单以及主机/模板批量更新表单的第一个选项卡中。  ![](../../../assets/en/manual/introduction/template_linking_first_tab.png)  因此，已从所有相应表单中删除了用于模板链接的单独选项卡。  在相关的开发中，主机原型配置中的主机组/主机组原型选择的字段也已从单独的选项卡移动到第一个选项卡。

en-us	##### Template low-level discovery rule tags  |Element|Element property|Required|Type|Range|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Root element for low-level discovery rules.| | |*For most of the element tag values, see element tag values for a regular item. Only the tags that are specific to low-level discovery rules, are described below.*| | | | | | |type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`string`|Default: 30d|Time period after which items that are no longer discovered will be deleted. Seconds, time unit with suffix or user macro.| |filter| | | | |Individual filter.| | |evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logic to use for checking low-level discovery rule filter conditions.| | |formula|\-|`string`| |Custom calculation formula for filter conditions.| |conditions| |\-| | |Root element for filter conditions.| | |macro|x|`string`| |Low-level discovery macro name.| | |value|\-|`string`| |Filter value: regular expression or global regular expression.| | |operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|Condition operator.| | |formulaid|x|`character`| |Arbitrary unique ID that is used to reference a condition from the custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |lld\_macro\_paths| |\-| | |Root element for LLD macro paths.| | |lld\_macro|x|`string`| |Low-level discovery macro name.| | |path|x|`string`| |Selector for value which will be assigned to the corresponding macro.| |preprocessing| |\-| | |LLD rule value preprocessing.| |step| |\-| | |Individual LLD rule value preprocessing step.| | |*For most of the element tag values, see element tag values for a template item value preprocessing. Only the tags that are specific to template low-level discovery value preprocessing, are described below.*| | | | | | |type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE|Type of the item value preprocessing step.| |trigger\_prototypes| |\-| | |Root element for trigger prototypes.| | |*For trigger prototype element tag values, see regular [template trigger](/manual/xml_export_import/templates#template_trigger_tags) tags.*| | | | | |graph\_prototypes| |\-| | |Root element for graph prototypes.| | |*For graph prototype element tag values, see regular [template graph](/manual/xml_export_import/templates#template_graph_tags) tags.*| | | | | |host\_prototypes| |\-| | |Root element for host prototypes.| | |*For host prototype element tag values, see regular [host](/manual/xml_export_import/hosts#host_tags) tags.*| | | | | |item\_prototypes| |\-| | |Root element for item prototypes.| | |*For item prototype element tag values, see regular [template item](/manual/xml_export_import/templates#template_item_tags) tags.*| | | | | |master\_item| |\-| | |Individual item prototype master item/item prototype data.| | |key|x|`string`| |Dependent item prototype master item/item prototype key value.<br><br>Required for a dependent item.|
zh-cn	#####  模板LLD规则标签  |元素|元素属性|是否必须|类型|适用范围|描述| |-------|----------------|--------|----|-----|-----------| |discovery\_rules|<|\-|<|<|底层发现规则的根元素。| |<|*对于大多数元素标记值，请参阅常规项的元素标记值。 下面只描述特定于底层发现规则的标记。*|<|<|<|<| |<|type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|监控项类型。| |<|lifetime|\-|`string`|Default: 30d|删除不再被发现的监控项的时间段。 支持秒，带有后缀的时间单位或用户宏。| |filter|<|<|<|<|单独的过滤。| |<|evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|用于检查底层发现规则过滤条件的逻辑。| |<|formula|\-|`string`|<|过滤器条件的自定义计算公式。| |conditions|<|\-|<|<|过滤器条件的根元素。| |<|macro|x|`string`|<|底层发现宏名。| |<|value|\-|`string`|<|过滤值:正则表达式或全局正则表达式。| |<|operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|条件操作符。| |<|formulaid|x|`character`|<|用于从自定义表达式引用条件的任意惟一ID。 只能包含大写字母。 该ID必须由用户在修改筛选条件时定义，但在之后请求它们时将重新生成。| |lld\_macro\_paths|<|\-|<|<|LLD宏路径的根元素。| |<|lld\_macro|x|`string`|<|底层发现宏名。| |<|path|x|`string`|<|将被赋值给相应宏的选择器。| |preprocessing|<|\-|<|<|LLD规则值预处理。| |step|<|\-|<|<|单个LLD规则值预处理步骤。| |<|*对于大多数元素标记值，请参阅模板项值预处理的元素标记值。 下面只描述特定于模板底层发现值预处理的标记。*|<|<|<|<| |<|type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE|监控项值预处理步骤的类型。| |trigger\_prototypes|<|\-|<|<|触发器原型的根元素。| |<|*有关触发器原型元素标记值，请参阅regular [模板触发器](/manual/xml_export_import/templates#template_trigger_tags) 标签.*|<|<|<|<| |graph\_prototypes|<|\-|<|<|图原型的根元素。| |<|*有关图形原型元素标签值，请参阅regular [模板 图形](/manual/xml_export_import/templates#template_graph_tags) 标签.*|<|<|<|<| |host\_prototypes|<|\-|<|<|主机原型的根元素。| |<|*有关主机原型元素标签值，请参阅regular[主机](/manual/xml_export_import/hosts#host_tags) 标签.*|<|<|<|<| |item\_prototypes|<|\-|<|<|监控项原型的根元素。| |<|*有关监控项原型元素标签值，请参阅regular[模板监控项](/manual/xml_export_import/templates#template_item_tags) tags.*|<|<|<|<| |master\_item|<|\-|<|<|单个监控项原型的主监控项/监控项原型数据。| |<|key|x|`string`|<|主监控项原型键值/监控项原型键值。 <br><br>相关项监控需要使用。|

en-us	# template.massadd
zh-cn	# 批量添加模板

en-us	# template.massremove
zh-cn	# 批量删除模板

en-us	# template.massupdate
zh-cn	# 批量更新模板

en-us	# > Template object  The following objects are directly related to the `template` API.
zh-cn	# > 模版对象  以下对象都是与`template` 直接相关的API。

en-us	 ### Templates  A new template *HPE Synergy by HTTP* is available.  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).  You can get this template:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	### 模板  新模板 *HPE Synergy by HTTP* 可用。  请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http) 的设置说明。  您可以获得这些模板：  - · 在新安装的*配置* → *模板*； - · 如果您是从以前的版本升级，您可以从 Zabbix [Git 存储库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) 下载新的模板或在下载的最新 Zabbix 版本的 `templates` 目录。 然后，在 *配置* → *模板* 中，您可以手动将它们导入 Zabbix。

en-us	 ### Templates  A new [template](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense by SNMP* is available.  You can get this template:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)     or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	### 模板  一个新的[模板](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense by SNMP* 是 可用的。  你可以获得这个模板：  - · 在新安装的*配置* → *模板*； - · 如果您是从以前的版本升级，您可以从 Zabbix [Git 存储库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) 下载新模板或在` 下载的最新 Zabbix 版本的 templates` 目录。 然后，在 *配置* → *模板* 中，您可以手动将它们导入 Zabbix。

en-us	 #### Templates  A new template *OpenWeatherMap by HTTP* is now available allowing to monitor OpenWeatherMap via HTTP. See [HTTP template operation](/manual/config/templates_out_of_the_box/http) for setup instructions.  The following changes have been made in the existing templates:  - In the templates *Windows services by Zabbix agent*, *Windows services by Zabbix agent active*,  *Windows by Zabbix agent*, *Windows by Zabbix agent active*  {$SERVICE.NAME.NOT_MATCHES} macro value has been updated to filter out an extended list of services.   - The template *PostgreSQL by Zabbix agent 2* now will check the number of slow queries and generate a problem if the amount exceeds a threshold.  You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)     or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	 #### 模板  新模板 *OpenWeatherMap by HTTP* 现在可以通过 HTTP 监控 OpenWeatherMap。有关设置说明，请参阅 [HTTP 模板操作](/manual/config/templates_out_of_the_box/http)。  在现有模板中进行了以下更改：  - 在模板 *Windows services by Zabbix agent*，*Windows services by Zabbix agent active*，*Windows by Zabbix agent*，*Windows by Zabbix agent active* ，{$SERVICE.NAME.NOT_MATCHES} 宏值已更新以筛选出扩展的服务列表。  - 模板 *PostgreSQL by Zabbix agent 2* 现在将会检查慢查询的数量，如果数量超过阈值，则会产生问题。  您可以获得以下模板：  - 在新设备的 *Configuration* → *Templates*； - 如果要从以前的版本升级，可以从Zabbix [Git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)下载新模板，或在下载的最新 Zabbix 版本的`templates`目录中找到它们。然后，在 *Configuration* → *Templates* 您可以手动将模板导入Zabbix。

en-us	#### Templates  In a [template](/manual/config/templates/template) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### 模板  在 [模板](/manual/config/templates/template) 配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |*标签*^[2](supported_by_location_user#footnotes)^|<|<| | |标签名称|支持| |^|标签值|支持|

en-us	#### Templates  Manage templates and link them to hosts or other templates.  [Template API](/manual/api/reference/template) | [Value map API](/manual/api/reference/valuemap)
zh-cn	#### 模板  管理模板并将其链接到主机或其他模板。  [Template API](/manual/api/reference/template) | [Value map API](/manual/api/reference/valuemap)

en-us	 ### Templates  New templates are available:  - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).  You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	### 模板  新模板可用：  - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP  请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http) 的设置说明。  您可以获得这些模板：  - · 在新安装的*配置* → *模板*； - · 如果您是从以前的版本升级，您可以从 Zabbix [Git 存储库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) 下载新的模板或在下载的最新 Zabbix 版本的 `templates` 目录。 然后，在 *Configuration* → *Templates* 中，您可以手动将它们导入 Zabbix。

en-us	 ### Templates  New templates are available:  - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).  You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	### 模板  新的模板已经可以使用:  - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP  有关设置说明，请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http).  你可以使用如下方式获取到新的模板:  -   在新安装的 *配置* → *模板* 中; -   如果要从以前的版本升级，可以从Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      下载新模板，或在下载的最新 Zabbix 版本的`templates`目录中找到它们。然后，在 *配置* → *模板* 您可以手动将模板导入 Zabbix 。

en-us	 ### Templates  New templates are available:  - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).  You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	### 模板  新的模板已经可以使用:  - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP  有关设置说明，请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http)。  你可以使用如下方式获取到新的模板:  -   在新安装的 *配置* → *模板* ; -   如果要从以前的版本升级，可以从Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      下载新模板，或在下载的最新 Zabbix 版本的`templates`目录中找到它们。然后，在 *配置* → *模板* 您可以手动将模板导入 Zabbix 。

en-us	 ### Templates  New templates are available: - *TrueNAS SNMP* - monitoring of TrueNAS storage OS by SNMP - *Proxmox VE by HTTP* - see setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http)  New macros allowing to define warning and critical thresholds of the filesystem utilization for virtual file system monitoring have been added to the templates *HOST-RESOURCES-MIB storage SNMP*,  *Linux by Prom*,  *Linux filesystems SNMP*,  *Linux filesystems by Zabbix agent active*,  *Linux filesystems by Zabbix agent*,  *Mellanox SNMP*,  *PFSense SNMP*,  *Windows filesystems by Zabbix agent active*, *Windows filesystems by Zabbix agent*. Filesystem utilization triggers have been updated to use these macros.   You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   If you are upgrading from previous versions, you can download new     templates from Zabbix [Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)      or find them in the `templates` directory of the downloaded latest     Zabbix version. Then, while in *Configuration* → *Templates* you can     import them manually into Zabbix.
zh-cn	 ### 模板  新模板可用： - *TrueNAS SNMP* - 通过SNMP监控TrueNAS存储操作系统 - *Proxmox VE by HTTP* - 请参阅[HTTP 模板](/manual/config/templates_out_of_the_box/http)的设置说明  以下模板中添加了新宏，新宏定义用于虚拟文件系统监控文件系统利用率的告警和关键阈值，*HOST-RESOURCES-MIB storage SNMP*，*Linux by Prom*，*Linux filesystems SNMP*，*Linux filesystems by Zabbix agent active*，*Linux filesystems by Zabbix agent*，*Mellanox SNMP*，*PFSense SNMP*，*Windows filesystems by Zabbix agent active*，*Windows filesystems by Zabbix agent*。文件系统利用率触发器已更新为使用这些宏。  您可以获得以下模板：  - 在新设备的 *Configuration* → *Templates* ； - 如果要从以前的版本升级，可以从Zabbix  [Git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)下载新模板，或在下载的最新 Zabbix 版本的`templates`目录中找到它们。然后，在 *Configuration* → *Templates* 您可以手动将模板导入Zabbix。

en-us	#### Templates  Templates are available for [remote monitoring](/manual/appendix/items/remote_stats) of Zabbix server or proxy internal metrics from an external instance:  -   Remote Zabbix server -   Remote Zabbix proxy  Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring.
zh-cn	#### 模版  Zabbix server和Zabbix proxy  [远程监控](/manual/appendix/items/remote_stats) 模板:  -   Template App Remote Zabbix server -   Template App Remote Zabbix proxy  请注意，为了使用模板远程监视多个外部实例，每个外部实例监视都需要一个单独的主机。

en-us	##### Template tags  |Element|Element property|Required|Type|Range|Description| |--|--|-|--|----|--------| |templates| |\-| | |Root element for templates.| | |uuid|x|`string`| |Unique identifier for this template.| | |template|x|`string`| |Unique template name.| | |name|\-|`string`| |Visible template name.| | |description|\-|`text`| |Template description.| |groups| |x| | |Root element for template host groups.| | |uuid|x|`string`| |Unique identifier for this host group.| | |name|x|`string`| |Host group name.| |templates| |\-| | |Root element for linked templates.| | |name|x|`string`| |Template name.| |tags| |\-| | |Root element for template tags.| | |tag|x|`string`| |Tag name.| | |value|\-|`string`| |Tag value.| |macros| |\-| | |Root element for template user macros.| | |macro|x|`string`| |User macro name.| | |type|\-|`string`|0 - TEXT (default)<br>1 - SECRET\_TEXT<br>2 - VAULT|Type of the macro.| | |value|\-|`string`| |User macro value.| | |description|\-|`string`| |User macro description.| |valuemaps| |\-| | |Root element for template value maps.| | |uuid|x|`string`| |Unique identifier for this value map.| | |name|x|`string`| |Value map name.| | |mapping|\-| | |Root element for mappings.| | |value|x|`string`| |Value of a mapping.| | |newvalue|x|`string`| |New value of a mapping.|
zh-cn	##### 模板标签  |元素|元素属性|是否必须的|类型|范围|描述| |-------|----------------|--------|----|-----|-----------| |templates|<|\-|<|<|模板的根元素。| |<|uuid|x|`string`|<|此模板的唯一标识符。| |<|template|x|`string`|<|此模板的唯一模板名称。| |<|name|\-|`string`|<|模板别名。| |<|description|\-|`text`|<|模板描述。| |groups|<|x|<|<|模板主机组的根元素。| |<|uuid|x|`string`|<|主机组的唯一标识。| |<|name|x|`string`|<|主机组名称| |templates|<|\-|<|<|链接模板的根元素。| |<|name|x|`string`|<|模板名称。| |tags|<|\-|<|<|模板标签的根元素。| |<|tag|x|`string`|<|标签名。| |<|value|\-|`string`|<|标签值。| |macros|<|\-|<|<|模板用户宏的根元素。| |<|macro|x|`string`|<|用户宏名称。| |<|type|\-|`string`|0 - TEXT (default)<br>1 - SECRET\_TEXT<br>2 - VAULT|宏类型。| |<|value|\-|`string`|<|用户宏值。| |<|description|\-|`string`|<|用户宏描述。| |valuemaps|<|\-|<|<|模板值映射的根元素。| |<|uuid|x|`string`|<|-此值映射的唯一标识符。| |<|name|x|`string`|<|值映射名称。| |<|mapping|\-|<|<|映射的根元素。| |<|value|x|`string`|<|值映射的值。| |<|newvalue|x|`string`|<|值映射的新值。|

en-us	### Template tag  The template tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Template tag name.| |value|string|Template tag value.|
zh-cn	### 模版标签  模版标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必须)|string|模版标签名字。| |value|string|模版标签值。|

en-us	### Template tag  The template tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Template tag name.| |value|string|Template tag value.|
zh-cn	### 模版标签  模版标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必须)|string|模版标签名字。| |value|string|模版标签值。|

en-us	### Template  The template object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |templateid|string|*(readonly)* ID of the template.| |**host**<br>(required)|string|Technical name of the template.| |description|text|Description of the template.| |name|string|Visible name of the template.<br><br>Default: `host` property value.| |uuid|string|Universal unique identifier, used for linking imported templates to already existing ones. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 模版  模板对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |templateid|string|*(只读)* 模版的ID。| |**host**<br>(必需)|string|-   模板的技术名称。| |description|text|模版的描述。| |name|string|模版的可见名称。<br><br>默认值： `host` 属性值。| |uuid|string|通用唯一标识符，用于将导入的模板链接到现有模板。如果没有给出则自动生成。<br><br>对于更新操作，此字段为*只读*。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Template  This class is designed to work with templates.  Object references:  -   [Template](/manual/api/reference/template/object#template)  Available methods:  -   [template.create](/manual/api/reference/template/create) - creating new templates -   [template.delete](/manual/api/reference/template/delete) - deleting templates -   [template.get](/manual/api/reference/template/get) - retrieving templates -   [template.massadd](/manual/api/reference/template/massadd) - adding related objects to templates -   [template.massremove](/manual/api/reference/template/massremove) - removing related objects from templates -   [template.massupdate](/manual/api/reference/template/massupdate) - replacing or removing related objects from templates -   [template.update](/manual/api/reference/template/update) - updating templates
zh-cn	# 模版  这个类是为使用模板而设计的。  对象引用:  -   [模版](/manual/api/reference/template/object#template)  可用方法:  -   [template.create](/manual/api/reference/template/create) - 创建一个新模版 -   [template.delete](/manual/api/reference/template/delete) - 删除模版 -   [template.get](/manual/api/reference/template/get) - 检索模版 -   [template.massadd](/manual/api/reference/template/massadd) - 向模板添加相关对象 -   [template.massremove](/manual/api/reference/template/massremove) - 从模板中删除相关对象 -   [template.massupdate](/manual/api/reference/template/massupdate) - 从模板中替换或删除相关对象 -   [template.update](/manual/api/reference/template/update) - 更新模版

en-us	# template.update
zh-cn	# 更新模板

en-us	##### Terminology  Setting this option enforces to use TLS connection to database from Zabbix server/proxy and frontend to database:  -   required - connect using TLS as transport mode without identity     checks; -   verify\_ca - connect using TLS and verify certificate; -   verify\_full - connect using TLS, verify certificate and verify that     database identity (CN) specified by DBHost matches its certificate;
zh-cn	##### 术语  通过设置此选项强制Zabbix Server/proxy/前端使用TLS连接数据库:  - required - 使用无需身份检查的TLS作为数据传输的连接; - verify\_ca - 使用TLS连接并验证证书; - verify\_full - 使用TLS连接，验证证书及DBHost指定的数据库身份(CN)匹配的证书;

en-us	#### Testing expressions  It is possible to test the configured trigger expression as to what the expression result would be depending on the received value.  The following expression from an official template is taken as an example:      avg(/Cisco IOS SNMPv2/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_WARN}     or     last(/Cisco IOS SNMPv2/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_WARN_STATUS}  To test the expression, click on *Expression constructor* under the expression field.  ![](../../../../assets/en/manual/config/triggers/trigger_test.png)  In the Expression constructor, all individual expressions are listed. To open the testing window, click on *Test* below the expression list.  ![](../../../../assets/en/manual/config/triggers/expr_test_button.png){width="600"}  In the testing window you can enter sample values ('80', '70', '0', '1' in this example) and then see the expression result, by clicking on the *Test* button.  ![](../../../../assets/en/manual/config/triggers/expr_test.png){width="600"}  The result of the individual expressions as well as the whole expression can be seen.  "TRUE" means that the specified expression is correct. In this particular case A, "80" is greater than the {$TEMP\_WARN} specified value, "70" in this example. As expected, a "TRUE" result appears.  "FALSE" means that the specified expression is incorrect. In this particular case B, {$TEMP\_WARN\_STATUS} "1" needs to be equal with specified value, "0" in this example. As expected, a "FALSE" result appears.  The chosen expression type is "OR". If at least one of the specified conditions (A or B in this case) is TRUE, the overall result will be TRUE as well. Meaning that the current value exceeds the warning value and a problem has occurred.
zh-cn	 #### 测试表达式  可以根据接收的值测试配置的触发器表达式，以确定表达式结果。  以官方模板的表达为例：      avg(/Cisco IOS SNMPv2/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_WARN}     or     last(/Cisco IOS SNMPv2/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_WARN_STATUS}  若要测试表达式，请点击表达式字段下的 *Expression constructor（表达式构造器）*。  ![](../../../../assets/en/manual/config/triggers/trigger_test.png)  在表达式构造器列出了所有单个表达式。打开测试窗口，点击在表达式列表下方*Test(测试)*。  ![](../../../../assets/en/manual/config/triggers/expr_test_button.png){width="600"}  在测试窗口中，您可以输入示例值（在这个示例中为“80, 70, 0，1”），然后点击 *测试* 按钮查看表达式结果。  ![](../../../../assets/en/manual/config/triggers/expr_test.png){width="600"}  可以看到每个表达式的结果以及整个表达式的结果。  “TRUE”结果意味着指定的表达式是正确的。在这个特定的情况A下，“80”大于{$TEMP\_WARN}指定值“70”，出现“TRUE”结果。  “FALSE”结果表示指定的表达式不正确。在这个特定的情况B下，在这个例子中{$TEMP\_WARN\_STATUS}是“1”，需要与指定的“0”值相等，这是错误的。出现“FALSE”结果。  选择的表达式类型是“OR”。如果指定条件中的至少一个（在这种情况下为A或B）是真的，那么最终结果也是TRUE。意味着，当前值超过了警告值，出现了异常。

en-us	##### Testing hypothetical value  ![](../../../../assets/en/manual/config/items/test_item_p.png){width="600"}  |Parameter|Description| |--|--------| |*Get value from host*|If you want to test a hypothetical value, leave this checkbox unmarked.<br>See also: [Testing real value](#testing_real_value).| |*Value*|Enter the input value to test.<br>Clicking in the parameter field or on the view/edit button will open a text area window for entering the value or code block.| |*Not supported*|Mark this checkbox to test an unsupported value.<br>This option is useful to test the *Check for not supported value* preprocessing step.| |*Time*|Time of the input value is displayed: `now` (read-only).| |*Previous value*|Enter a previous input value to compare to.<br>Only for *Change* and *Throttling* preprocessing steps.| |*Previous time*|Enter the previous input value time to compare to.<br>Only for *Change* and *Throttling* preprocessing steps.<br>The default value is based on the 'Update interval' field value of the item (if '1m', then this field is filled with `now-1m`). If nothing is specified or the user has no access to the host, the default is `now-30s`.| |*Macros*|If any macros are used, they are listed along with their values. The values are editable for testing purposes, but the changes will only be saved within the testing context.| |*End of line sequence*|Select the end of line sequence for multiline input values:<br>**LF** - LF (line feed) sequence<br>**CRLF** - CRLF (carriage-return line-feed) sequence.| |*Preprocessing steps*|Preprocessing steps are listed; the testing result is displayed for each step after the *Test* button is clicked.<br>If the step failed in testing, an error icon is displayed. The error description is displayed on mouseover.<br>In case "Custom on fail" is specified for the step and that action is performed, a new line appears right after the preprocessing test step row, showing what action was done and what outcome it produced (error or value).| |*Result*|The final result of testing preprocessing steps is displayed in all cases when all steps are tested together (when you click on the *Test all steps* button).<br>The type of conversion to the value type of the item is also displayed, for example `Result converted to Numeric (unsigned)`.|  Click on *Test* to see the result after each preprocessing step.  Test values are stored between test sessions for either individual steps or all steps, allowing the user to change preprocessing steps or item configuration and then return to the testing window without having to re-enter information. Values are lost on a page refresh though.  The testing is done by Zabbix server. The frontend sends a corresponding request to the server and waits for the result. The request contains the input value and preprocessing steps (with expanded user macros). For *Change* and *Throttling* steps, an optional previous value and time can be specified. The server responds with results for each preprocessing step.  All technical errors or input validation errors are displayed in the error box at the top of the testing window.
zh-cn	##### 检验假设值  ![](../../../../assets/en/manual/config/items/test_item_p.png){width="600"}  |参数|描述| |---------|-----------| |*从主机获取值*|如果您想测试假设值，请不要选中此复选框。<br>另请参阅：[测试真实值](#testing_real_value).| |*值*|输入要测试的输入值。<br>单击参数字段或查看/编辑按钮将打开一个文本区域窗口，用于输入值或代码块。| |*不支持的*|选中此复选框可测试不受支持的值。<br>此选项可用于测试 *检查不受支持的值* 预处理步骤。| |*时间*|显示输入值的时间：`now`（只读）。| |*以前的值*|输入之前的输入值进行比较。<br>仅适用于 *更改* 和 *节流* 预处理步骤。| |*以前的时间点*|输入之前的输入值时间进行比较。<br>仅适用于*更改* 和 *节流* 预处理步骤。<br>默认值基于监控项的“更新间隔”字段值（如果为“1m”， 然后这个字段用`now-1m`填充）。 如果未指定任何内容或用户无权访问主机，则默认为 `now-30s`。| |*宏*|如果使用了任何宏，它们将与它们的值一起列出。 出于测试目的，这些值是可编辑的，但更改只会保存在测试上下文中。| |*行尾序列*|为多行输入值选择行尾序列：<br>**LF** - LF（换行）序列<br>**CRLF** - CRLF（回车换行）序列。| |*预处理步骤*|列出了预处理步骤； 单击 *Test* 按钮后，将显示每个步骤的测试结果。<br>如果该步骤测试失败，则会显示错误图标。 鼠标悬停时会显示错误描述。<br>如果为步骤指定了“失败时自定义”并执行了该操作，则会在预处理测试步骤行之后立即出现一个新行，显示已执行的操作和结果 产生（错误或值）。| |*结果*|测试预处理步骤的最终结果在所有步骤一起测试时显示在所有情况下（当您单击*测试所有步骤*按钮时）。<br>还显示转换为监控项的值类型的类型， 例如“结果转换为数字（无符号）”。|  单击 *测试* 以查看每个预处理步骤后的结果。  测试值存储在单个步骤或所有步骤的测试会话之间，允许用户更改预处理步骤或监控项配置，然后返回到测试窗口，而无需重新输入信息。 但是，页面刷新时值会丢失。  测试由 Zabbix server 完成。 前端向服务器发送相应的请求并等待结果。 该请求包含输入值和预处理步骤（带有扩展的用户宏）。 对于 *更改* 和 *节流* 步骤，可以指定可选的先前值和时间。 服务器响应每个预处理步骤的结果。  所有技术错误或输入验证错误都显示在测试窗口顶部的错误框中。

en-us	#### Testing  It is possible to test an item and, if configured correctly, get a real value in return. Testing can occur even before an item is saved.  Testing is available for host and template items, item prototypes and low-level discovery rules. Testing is not available for active items.  Item testing is available for the following passive item types:  -   Zabbix agent -   SNMP agent (v1, v2, v3) -   IPMI agent -   SSH checks -   Telnet checks -   JMX agent -   Simple checks (except `icmpping*`, `vmware.*` items) -   Zabbix internal -   Calculated items -   External checks -   Database monitor -   HTTP agent -   Script  To test an item, click on the *Test* button at the bottom of the item configuration form. Note that the *Test* button will be disabled for items that cannot be tested (like active checks, excluded simple checks).  ![](../../../../assets/en/manual/config/items/item_test_button.png)  The item testing form has fields for the required host parameters (host address, port, proxy name/no proxy) and item-specific details (such as SNMPv2 community or SNMPv3 security credentials). These fields are context aware:  -   The values are pre-filled when possible, i.e. for items requiring an     agent, by taking the information from the selected agent interface     of the host -   The values have to be filled manually for template items -   Plain-text macro values are resolved -   Fields where the value (or part of the value) is a secret or Vault     macro are empty and have to be entered manually. If any item     parameter contains a secret macro value, the following warning     message is displayed: "Item contains user-defined macros with secret     values. Values of these macros should be entered manually." -   The fields are disabled when not needed in the context of the item     type (e.g. the host address field and the proxy field are disabled     for calculated items)  To test the item, click on *Get value*. If the value is retrieved successfully, it will fill the *Value* field, moving the current value (if any) to the *Previous value* field while also calculating the *Prev. time* field, i.e. the time difference between the two values (clicks) and trying to detect an EOL sequence and switch to CRLF if detecting "\\n\\r" in retrieved value.  ![](../../../../assets/en/manual/config/items/item_test.png){width="600"}  If the configuration is incorrect, an error message is displayed describing the possible cause.  ![](../../../../assets/en/manual/config/items/item_test_error.png)  A successfully retrieved value from host can also be used to test [preprocessing steps](/manual/config/items/preprocessing#testing).
zh-cn	#### 测试  可以对监控项进行测试，如果配置正确，则可以返回实际值。测试甚至可以在保存监控项之前进行。  可以对主机和模板的监控项、监控项原型和低级别自动发现规则进行测试。agent（主动式）类型的监控项不能被测试。  监控项测试可用于以下被动式监控项：  -   Zabbix agent -   SNMP agent (v1, v2, v3) -   IPMI agent -   SSH checks -   Telnet checks -   JMX agent -   Simple checks（除了监控项 `icmpping*`, `vmware.*`） -   Zabbix internal -   Calculated items -   External checks -   Database monitor -   HTTP agent -   Script  要测试监控项，请单击监控项配置表单底部的*测试*按钮。请注意，对于无法测试的监控项（例如简单检查之外的其它主动检查），*测试*按钮将被禁用。  ![](../../../../assets/en/manual/config/items/item_test_button.png)  监控项测试表单包含主机参数（主机IP地址、端口、proxy名称/无proxy）和监控项相关的详情（如SNMPv2的团体名或SNMPv3的安全凭据）所需的字段。这些字段是上下文相关的：  -   所需的参数值会尽可能预填充，例如，对于需要agent的监控项，所需信息就会从主机下所选的agent接口传递过来 -   模板内的监控项的相关参数需要手动填充 -   纯文本宏的值会被解析 -   值（或部分值）为密码或Vault宏的字段为空，必须手动输入。如果监控项参数中存在加密宏值，则会显示如下警告信息：“监控项包含用户定义的带有密码的宏。这些宏的值应该手动输入。” -   在特定的监控项类型上下文中，不需要的字段会被禁用（例如，在可计算类型的监控项中主机地址字段和proxy字段被禁用）  要测试监控项，点击 *获取值*。如果成功获取到值，它会自动填充进对应的 *Value（值）*字段，将当前值（如果有的话）移动到 *Previous value（前一次值）*字段，同时计算*Prev. time（前一次）*字段，即两个值（两次测试）之间的时间差，并尝试检测EOL序列，若在接收到的值中检测到“\\n\\r”时切换到CRLF。  ![](../../../../assets/en/manual/config/items/item_test.png){width="600"}  如果配置不正确，则返回错误提示，并描述可能的原因。  ![](../../../../assets/en/manual/config/items/item_test_error.png)  从主机接收成功的值也可以用于测试[预处理步骤](/zh/manual/config/items/preprocessing#testing)。

en-us	#### Testing MIB files  Testing snmp MIBs can be done using `snmpwalk` utility. If you don't have it installed, use the following instructions.  On Debian-based systems:      # apt install snmp  On RedHat-based systems:      # dnf install net-snmp-utils  After that, the following command must not give error when you query a network device:      $ snmpwalk -v 2c -c public <NETWORK DEVICE IP> ifInOctets     IF-MIB::ifInOctets.1 = Counter32: 176137634     IF-MIB::ifInOctets.2 = Counter32: 0     IF-MIB::ifInOctets.3 = Counter32: 240375057     IF-MIB::ifInOctets.4 = Counter32: 220893420     [...]
zh-cn	#### 测试 MIB 文件  可以使用 `snmpwalk` 实用程序来测试 snmp MIB。如果你没有安装，请使用以下说明。  在基于 Debian 的系统上：      # apt install snmp  在基于 RedHat 的系统上：      # dnf install net-snmp-utils  之后，当您查询网络设备时，以下命令一定不会出错：      $ snmpwalk -v 2c -c public <NETWORK DEVICE IP> ifInOctets     IF-MIB::ifInOctets.1 = Counter32: 176137634     IF-MIB::ifInOctets.2 = Counter32: 0     IF-MIB::ifInOctets.3 = Counter32: 240375057     IF-MIB::ifInOctets.4 = Counter32: 220893420     [...]

en-us	##### Testing real value  To test preprocessing against a real value:  -   Mark the *Get value from host* checkbox -   Enter or verify host parameters (host address, port, proxy name/no     proxy) and item-specific details (such as SNMPv2 community or SNMPv3     security credentials). These fields are context-aware:     -   The values are pre-filled when possible, i.e. for items         requiring an agent, by taking the information from the selected         agent interface of the host     -   The values have to be filled manually for template items     -   Plain-text macro values are resolved     -   Fields where the value (or part of the value) is a secret or         Vault macro are empty and have to be entered manually. If any         item parameter contains a secret macro value, the following         warning message is displayed: "Item contains user-defined macros         with secret values. Values of these macros should be entered         manually."     -   The fields are disabled when not needed in the context of the         item type (e.g. the host address and the proxy fields are         disabled for calculated items) -   Click on *Get value and test* to test the preprocessing  ![](../../../../assets/en/manual/config/items/test_item_p2.png){width="600"}  If you have specified a value mapping in the item configuration form ('Show value' field), the item test dialog will show another line after the final result, named 'Result with value map applied'.  Parameters that are specific to getting a real value from a host:  |Parameter|Description| |--|--------| |*Get value from host*|Mark this checkbox to get a real value from the host.| |*Host address*|Enter the host address.<br>This field is automatically filled by the address of the item host interface.| |*Port*|Enter the host port.<br>This field is automatically filled by the port of item host interface.| |*Additional fields for SNMP interfaces<br>(SNMP version, SNMP community, Context name, etc)*|See [Configuring SNMP monitoring](/manual/config/items/itemtypes/snmp#step_2) for additional details on configuring an SNMP interface (v1, v2 and v3).<br>These fields are automatically filled from the item host interface.| |*Proxy*|Specify the proxy if the host is monitored by a proxy.<br>This field is automatically filled by the proxy of the host (if any).|  For the rest of the parameters, see [Testing hypothetical value](#testing_hypothetical_value) above.
zh-cn	##### 测试真实值  根据实际值测试预处理:  - 标记 *从主机获取值* 复选框 - 输入或验证主机参数（主机地址、端口、代理名称/无代理）和监控项特定的详细信息（例如 SNMPv2 社区或 SNMPv3 安全凭证）。这些字段是上下文感知的：     - 这些值在可能的情况下预先填写，即对于需要agent的监控项，通过从主机的选定agent接口获取信息     - 模板监控项的值必须手动填写     - 解析纯文本宏值     - 值（或部分值）为机密或 Vault 宏的字段为空，必须手动输入。如果任何监控项参数包含秘密宏值，则会显示以下警告消息：“监控项包含具有秘密值的用户定义的宏。应手动输入这些宏的值。”     - 在监控项类型的上下文中不需要时禁用这些字段（例如，计算监控项的主机地址和代理字段被禁用） - 点击 *获取值并测试* 来测试预处理  ![](../../../../assets/en/manual/config/items/test_item_p2.png){width="600"}  如果您在监控项配置表单（“显示值”字段）中指定了值映射，监控项测试对话框将在最终结果之后显示另一行，名为“应用了值映射的结果”。  特定于从主机获取实际值的参数:  |参数|描述| |---------|-----------| |*从主机获取值*|标记此复选框以从主机获取实际值。| |*主机地址*|输入主机地址。<br>此字段由监控项主机接口的地址自动填充。| |*端口*|输入主机端口。<br>此字段由监控项主机接口的端口自动填充。| |*SNMP 接口的附加字段<br>(SNMP 版本、SNMP 社区、上下文名称等)*|有关配置 SNMP 接口（v1、v2 和 v3）的更多详细信息。请查看[配置 SNMP 监控](/manual/config/items/itemtypes/snmp#step_2)。 <br>这些字段会从监控项主机接口自动填充。| |*代理*|如果主机由代理监控，请指定代理。<br>此字段由主机的代理（如果有）自动填充。|  有关其余参数，请参考 [Testing hypothetical value](#testing_hypothetical_value) 。

en-us	#### Testing  Testing preprocessing steps is useful to make sure that complex preprocessing pipelines yield the results that are expected from them, without waiting for the item value to be received and preprocessed.  ![](../../../../assets/en/manual/config/items/test_item_steps.png){width="600"}  It is possible to test:  -   against a hypothetical value -   against a real value from a host  Each preprocessing step can be tested individually as well as all steps can be tested together. When you click on the *Test* or *Test all steps* button respectively in the Actions block, a testing window is opened.
zh-cn	#### Testing  测试预处理步骤有助于确保复杂的预处理管道产生预期的结果，而无需等待接收和预处理监控项值。  ![](../../../../assets/en/manual/config/items/test_item_steps.png){width="600"}  可以测试：  -   与假设值相比 -   与主机的实际值相比较  每个预处理步骤都可以单独测试，也可以一起测试所有步骤。 当您分别单击 动作块中的 *Test* 或 *Test all steps* 按钮时，将打开一个测试窗口。

en-us	 ### Text data for Top hosts widget  It is now possible to select items with any type of information (including *Character*, *Text*, and *Log*)  in the [Top hosts](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts) widget.  For example, it is now possible to use this widget to display the versions of Zabbix agents  running on each host.
zh-cn	 ### Top hosts 组件的文本数据  现在可以在 [Top hosts](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts) 组件中选择包含任何信息类型（包括*字符*、*文本* 和 *日志*）的监控项。例如，现在可以使用此组件显示每台主机上运行的 Zabbix agent 版本。

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