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.|  
ja	#### 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*, *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*, *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.|  

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.|
ja	#### サポートするチェック  -   角括弧のないパラメータは定数です。例えば、     `zabbix[host,<type>,available]` の  'host' と 'available'  これらはアイテムキーで *そのまま* 使用します。 -   プロキシでサポートされていない("not supported onproxy") アイテムおよびアイテムの引数の値は、ホストがサーバーによって     監視されている場合にのみ収集できます。逆に、サーバーでサポートされていない("not supported on server")値は、     ホストがプロキシ監視されている場合にのみ収集することができます。  |Key|<|<|<|<|<| |-|------|--|------|------|-| |▲|説明|<|<|戻り値|コメント| |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.|

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.|
ja	##### 対応チェック  次の表では、IPMIエージェントチェックでサポートされる組み込みアイテムについて説明します。  |アイテムキー|<|<|<| |--|--|------|------| |▲|説明|戻り値|コメント| |ipmi.get|<|<|<| |<|IPMI-sensor関連の情報。|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. For more details, see [databases](#databases).
ja	#### サポートされるDBバージョンの確認  Zabbix [サーバー](/manual/appendix/config/zabbix_server)と[プロキシ](/manual/appendix/config/zabbix_proxy)は、起動前にデータベースのバージョンを確認し、サポート範囲外のバージョンの場合は起動しないようになりました。詳細については、[データベース](#データベース)を参照してください。

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.  
ja	### 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)
ja	#### サポートされているアイテムキー  この表は、Zabbix agentアイテムに使用できるアイテムキーの詳細を示します。  こちらもご参照ください。  -   [プラットフォームがサポートするアイテム](/manual/appendix/items/supported_by_platform) -   [Zabbix エージェント 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)  
ja	#### 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)  \*\* Mandatory and optional parameters \*\*  Parameters without angle brackets are mandatory. Parameters marked with angle brackets **<** **>** are optional.  |Key|<|<|<|<| |---|-|-|-|-| |<|**Description**|**Return value**|**Parameters**|**Comments**| |agent.hostmetadata|<|<|<|<| |<|Agent host metadata.|String|<|Returns the value of HostMetadata or HostMetadataItem parameters, or empty string if none are defined.<br><br>Supported since Zabbix 6.0.| |agent.hostname|<|<|<|<| |<|Agent host name.|String|<|Returns:<br>As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file;<br>As active check - the name of the current hostname.| |agent.ping|<|<|<|<| |<|Agent availability check.|Nothing - unavailable<br><br>1 - available|<|Use the **nodata()** trigger function to check for host unavailability.| |agent.variant|<|<|<|<| |<|Variant of Zabbix agent (Zabbix agent or Zabbix agent 2).|Integer|<|Example of returned value:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |agent.version|<|<|<|<| |<|Version of Zabbix agent.|String|<|Example of returned value:<br>6.0.3| |kernel.maxfiles|<|<|<|<| |<|Maximum number of opened files supported by OS.|Integer|<|<| |kernel.maxproc|<|<|<|<| |<|Maximum number of processes supported by OS.|Integer|<|<| |kernel.openfiles|<|<|<|<| |<|Return the number of currently open file descriptors.|Integer|<|This item is supported on Linux only since Zabbix 6.0.| |log\[file,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>\]|<|<|<|<| |<|Monitoring of a log file.|Log|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0)- possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |log.count\[file,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>,<options>\]|<|<|<|<| |<|Count of matched lines in a monitored log file.|Integer|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |logrt\[file\_regexp,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>,<options>\]|<|<|<|<| |<|Monitoring of a log file that is rotated.|Log|**file\_regexp** - absolute path to file and the file name described by a regular [expression](/manual/regular_expressions#overview). *Note* that only the file name is a regular expression<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0) - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>Note that logrt is designed to work with one currently active log file, with several other matching inactive files rotated. If, for example, a directory has many active log files, a separate logrt item should be created for each one. Otherwise if one logrt item picks up too many files it may lead to exhausted memory and a crash of monitoring.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}$",,,100\] → will match a file like "logfile1" (will not match ".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}$","pattern\_to\_match","UTF-8",100\] → will collect data from files such "logfile\_abc\_1" or "logfile\_\_001".<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> logrt\[/app1/\^test.\*log$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |logrt.count\[file\_regexp,<regexp>,<encoding>,<maxproclines>,<mode>,<maxdelay>,<options>\]|<|<|<|<| |<|Count of matched lines in a monitored log file that is rotated.|Integer|**file\_regexp** - absolute path to file and regular [expression](/manual/regular_expressions#overview) describing the file name pattern<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |modbus.get\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<|<| |<|Reads Modbus data.|JSON object|**endpoint** - endpoint defined as `protocol://connection_string`<br>**slave id** - slave ID<br>**function** - Modbus function<br>**address** - address of first registry, coil or input<br>**count** - number of records to read<br>**type** - type of data<br>**endianness** - endianness configuration<br>**offset** - number of registers, starting from 'address', the results of which will be discarded.<br><br>See a [detailed description](/manual/appendix/items/modbus) of parameters.|Supported since Zabbix 5.2.0.| |net.dns\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Checks if DNS service is up.|0 - DNS is down (server did not respond or DNS resolution failed)<br><br>1 - DNS is up|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol** (since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns*| |net.dns.record\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Performs a DNS query.|Character string with the required type of information|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol**(since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns.query*| |net.if.collisions\[if\]|<|<|<|<| |<|Number of out-of-window collisions.|Integer|**if** - network interface name|<| |net.if.discovery|<|<|<|<| |<|List of network interfaces. Used for low-level discovery.|JSON object|<|Supported since Zabbix 2.0.<br><br>On FreeBSD, OpenBSD and NetBSD supported since Zabbix 2.2.<br><br>Some Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names.| |net.if.in\[if,<mode>\]|<|<|<|<| |<|Incoming traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*frame* - the number of packet framing errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver<br>*multicast* - the number of multicast frames received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix 1.8.6.<br><br>Examples:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.out\[if,<mode>\]|<|<|<|<| |<|Outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*collisions (colls)* - the number of collisions detected on the interface<br>*carrier* - the number of carrier losses detected by the device driver<br>*compressed* - the number of compressed packets transmitted by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix agent 1.8.6 version.<br><br>Examples:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.total\[if,<mode>\]|<|<|<|<| |<|Sum of incoming and outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Examples:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.<br><br>Note that dropped packets are supported only if both net.if.in and net.if.out work for dropped packets on your platform.| |net.tcp.listen\[port\]|<|<|<|<| |<|Checks if this TCP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - TCP port number|Example:<br>=> net.tcp.listen\[80\]<br><br>On Linux supported since Zabbix 1.8.4<br><br>Since Zabbix 3.0.0, on Linux kernels 2.6.14 and above, information about listening TCP sockets is obtained from the kernel's NETLINK interface, if possible. Otherwise, the information is retrieved from /proc/net/tcp and /proc/net/tcp6 files.| |net.tcp.port\[<ip>,port\]|<|<|<|<| |<|Checks if it is possible to make TCP connection to specified port.|0 - cannot connect<br><br>1 - can connect|**ip** - IP or DNS name (default is 127.0.0.1)<br>**port** - port number|Example:<br>=> net.tcp.port\[,80\] → can be used to test availability of web server running on port 80.<br><br>For simple TCP performance testing use net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).| |net.tcp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.port for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of TCP service.|0 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,<port>\] for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.tcp.socket.count\[,80,,,established\] → check if local TCP port 80 is in "established" state<br><br>This item is supported since Zabbix 6.0.| |net.udp.listen\[port\]|<|<|<|<| |<|Checks if this UDP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - UDP port number|Example:<br>=> net.udp.listen\[68\]<br><br>On Linux supported since Zabbix 1.8.4| |net.udp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of UDP service.|0 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *unconn*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → check if any UDP socket is in "listening" state<br><br>This item is supported since Zabbix 6.0.| |proc.cpu.util\[<name>,<user>,<type>,<cmdline>,<mode>,<zone>\]|<|<|<|<| |<|Process CPU utilization percentage.|Float|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**type** - CPU utilization type:<br>*total* (default), *user*, *system*<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**mode** - data gathering mode: *avg1* (default), *avg5*, *avg15*<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.cpu.util\[,root\] → CPU utilization of all processes running under the "root" user<br>=> proc.cpu.util\[zabbix\_server,zabbix\] → CPU utilization of all zabbix\_server processes running under the zabbix user<br><br>The returned value is based on single CPU core utilization percentage. For example CPU utilization of a process fully using two cores is 200%.<br><br>The process CPU utilization data is gathered by a collector which supports the maximum of 1024 unique (by name, user and command line) queries. Queries not accessed during the last 24 hours are removed from the collector.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.<br><br>This key is supported since Zabbix 3.0.0 and is available on several platforms (see [Items supported by platform](/manual/appendix/items/supported_by_platform)).| |proc.mem\[<name>,<user>,<mode>,<cmdline>,<memtype>\]|<|<|<|<| |<|Memory used by process in bytes.|Integer - with `mode` as *max*, *min*, *sum*<br><br>Float - with `mode` as *avg*|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**mode** - possible values:<br>*avg*, *max*, *min*, *sum* (default)<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**memtype** - [type of memory](/manual/appendix/items/proc_mem_notes) used by process|Examples:<br>=> proc.mem\[,root\] → memory used by all processes running under the "root" user<br>=> proc.mem\[zabbix\_server,zabbix\] → memory used by all zabbix\_server processes running under the zabbix user<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → memory used by the most memory-hungry process running under oracle having oracleZABBIX in its command line<br><br>*Note*: When several processes use shared memory, the sum of memory used by processes may result in large, unrealistic values.<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.mem[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>The `memtype` parameter is supported on several [platforms](/manual/appendix/items/supported_by_platform) since Zabbix 3.0.0.| |proc.num\[<name>,<user>,<state>,<cmdline>,<zone>\]|<|<|<|<| |<|The number of processes.|Integer|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**state** (*disk* and *trace* options since version 3.4.0) - possible values:<br>*all* (default),<br>*disk* - uninterruptible sleep,<br>*run* - running,<br>*sleep* - interruptible sleep,<br>*trace* - stopped,<br>*zomb* - zombie<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.num\[,mysql\] → number of processes running under the mysql user<br>=> proc.num\[apache2,www-data\] → number of apache2 processes running under the www-data user<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → number of processes in sleep state running under oracle having oracleZABBIX in its command line<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>On Windows, only the `name` and `user` parameters are supported.<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.num[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.| |sensor\[device,sensor,<mode>\]|<|<|<|<| |<|Hardware sensor reading.|Float|**device** - device name<br>**sensor** - sensor name<br>**mode** - possible values:<br>*avg*, *max*, *min* (if this parameter is omitted, device and sensor are treated verbatim).|Reads /proc/sys/dev/sensors on Linux 2.4.<br><br>Example:<br>=> sensor\[w83781d-i2c-0-2d,temp1\]<br><br>Prior to Zabbix 1.8.4, the *sensor\[temp1\]* format was used.| |^|^|^|^|Reads /sys/class/hwmon on Linux 2.6+.<br><br>See a more detailed description of [sensor](/manual/appendix/items/sensor) item on Linux.| |^|^|^|^|Reads the *hw.sensors* MIB on OpenBSD.<br><br>Examples:<br>=> sensor\[cpu0,temp0\] → temperature of one CPU<br>=> sensor\["cpu\[0-2\]$",temp,avg\] → average temperature of the first three CPU's<br><br>Supported on OpenBSD since Zabbix 1.8.4.| |system.boottime|<|<|<|<| |<|System boot time.|Integer (Unix timestamp)|<|<| |system.cpu.discovery|<|<|<|<| |<|List of detected CPUs/CPU cores. Used for low-level discovery.|JSON object|<|Supported on all platforms since 2.4.0.| |system.cpu.intr|<|<|<|<| |<|Device interrupts.|Integer|<|<| |system.cpu.load\[<cpu>,<mode>\]|<|<|<|<| |<|[CPU load](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - possible values:<br>*all* (default), *percpu* (since version 2.0; total load divided by online CPU count)<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |system.cpu.num\[<type>\]|<|<|<|<| |<|Number of CPUs.|Integer|**type** - possible values:<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |system.cpu.switches|<|<|<|<| |<|Count of context switches.|Integer|<|<| |system.cpu.util\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<|<| |<|CPU utilization percentage.|Float|**cpu** - *<CPU number>* or *all* (default)<br>**type** - possible values:<br>*user* (default), *idle*, *nice*, *system* (default for Windows), *iowait*, *interrupt*, *softirq*, *steal*, *guest* (on Linux kernels 2.6.24 and above), *guest\_nice* (on Linux kernels 2.6.33 and above).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*<br>**logical\_or\_physical** (since version 5.0.3; on AIX only) - possible values: *logical* (default), *physical*. This parameter is supported on AIX only.|Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>Old naming: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |system.hostname\[<type>, <transform>\]|<|<|<|<| |<|System host name.|String|**type** (before version 5.4.7 supported on Windows only) - possible values: *netbios* (default on Windows), *host* (default on Linux), *shorthost* (since version 5.4.7; returns part of the hostname before the first dot, a full string for names without dots).<br>**transform** (since version 5.4.7) - possible values:<br>*none* (default), *lower* (convert to lowercase)|The value is acquired by either GetComputerName() (for **netbios**) or gethostname() (for **host**) functions on Windows and by "hostname" command on other systems.<br><br>Examples of returned values:<br>*on Linux*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |system.hw.chassis\[<info>\]|<|<|<|<| |<|Chassis information.|String|**info** - one of full (default), model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>This key depends on the availability of the [SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) table.<br>Will try to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory.<br><br>**Root permissions** are required because the value is acquired by reading from sysfs or memory.<br><br>Supported since Zabbix 2.0.| |system.hw.cpu\[<cpu>,<info>\]|<|<|<|<| |<|CPU information.|String or integer|**cpu** - *<CPU number>* or *all* (default)<br>**info** - possible values:<br>*full* (default), *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>Gathers info from /proc/cpuinfo and /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq.<br><br>If a CPU number and *curfreq* or *maxfreq* is specified, a numeric value is returned (Hz).<br><br>Supported since Zabbix 2.0.| |system.hw.devices\[<type>\]|<|<|<|<| |<|Listing of PCI or USB devices.|Text|**type** (since version 2.0) - *pci* (default) or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>Returns the output of either lspci or lsusb utility (executed without any parameters).| |system.hw.macaddr\[<interface>,<format>\]|<|<|<|<| |<|Listing of MAC addresses.|String|**interface** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**format** - *full* (default) or *short*|Lists MAC addresses of the interfaces whose name matches the given `interface` regular [expression](/manual/regular_expressions#overview) (*all* lists for all interfaces).<br><br>Example:<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If `format` is specified as *short*, interface names and identical MAC addresses are not listed.<br><br>Supported since Zabbix 2.0.| |system.localtime\[<type>\]|<|<|<|<| |<|System time.|Integer - with `type` as *utc*<br><br>String - with `type` as *local*|**type** (since version 2.0) - possible values:<br>*utc* - (default) the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds.<br>*local* - the time in the 'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm' format<br>|Must be used as a [passive check](/manual/appendix/items/activepassive#passive_checks) only.<br><br>Example:<br>=> system.localtime\[local\] → create an item using this key and then use it to display host time in the *Clock* [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock).| |system.run\[command,<mode>\]|<|<|<|<| |<|Run specified command on the host.|Text result of the command<br><br>1 - with `mode` as *nowait* (regardless of command result)|**command** - command for execution<br>**mode** - possible values:<br>*wait* - wait end of execution (default),<br>*nowait* - do not wait|Up to 512KB of data can be returned, including trailing whitespace that is truncated.<br>To be processed correctly, the output of the command must be text.<br><br>Example:<br>=> system.run\[ls -l /\] → detailed file list of root directory.<br><br>*Note*: system.run items are disabled by default. Learn how to [enable them](/[[/manual/config/items/restrict_checks).<br><br>The return value of the item is standard output together with standard error produced by command. The exit code is not checked.<br><br>Empty result is allowed starting with Zabbix 2.4.0.<br>See also: [Command execution](/manual/appendix/command_execution).| |system.stat\[resource,<type>\]|<|<|<|<| |<|System statistics.|Integer or float|**ent** - number of processor units this partition is entitled to receive (float)<br>**kthr,<type>** - information about kernel thread states:<br>*r* - average number of runnable kernel threads (float)<br>*b* - average number of kernel threads placed in the Virtual Memory Manager wait queue (float)<br>**memory,<type>** - information about the usage of virtual and real memory:<br>*avm* - active virtual pages (integer)<br>*fre* - size of the free list (integer)<br>**page,<type>** - information about page faults and paging activity:<br>*fi* - file page-ins per second (float)<br>*fo* - file page-outs per second (float)<br>*pi* - pages paged in from paging space (float)<br>*po* - pages paged out to paging space (float)<br>*fr* - pages freed (page replacement) (float)<br>*sr* - pages scanned by page-replacement algorithm (float)<br>**faults,<type>** - trap and interrupt rate:<br>*in* - device interrupts (float)<br>*sy* - system calls (float)<br>*cs* - kernel thread context switches (float)<br>**cpu,<type>** - breakdown of percentage usage of processor time:<br>*us* - user time (float)<br>*sy* - system time (float)<br>*id* - idle time (float)<br>*wa* - idle time during which the system had outstanding disk/NFS I/O request(s) (float)<br>*pc* - number of physical processors consumed (float)<br>*ec* - the percentage of entitled capacity consumed (float)<br>*lbusy* - indicates the percentage of logical processor(s) utilization that occurred while executing at the user and system level (float)<br>*app* - indicates the available physical processors in the shared pool (float)<br>**disk,<type>** - disk statistics:<br>*bps* - indicates the amount of data transferred (read or written) to the drive in bytes per second (integer)<br>*tps* - indicates the number of transfers per second that were issued to the physical disk/tape (float)|<| |<|^|^|Comments|<| |<|^|^|This item is [supported](/manual/appendix/items/supported_by_platform) on AIX only, since Zabbix 1.8.1.<br>Take note of the following limitations in these items:<br>=> system.stat\[cpu,app\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,ec\] - supported on AIX LPAR of type "Shared" and "Dedicated" ("Dedicated" always returns 100 (percent))<br>=> system.stat\[cpu,lbusy\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,pc\] - supported on AIX LPAR of type "Shared" and "Dedicated"<br>=> system.stat\[ent\] - supported on AIX LPAR of type "Shared" and "Dedicated"|<| |system.sw.arch|<|<|<|<| |<|Software architecture information.|String|<|Example:<br>=> system.sw.arch → i686<br><br>Info is acquired from uname() function.<br><br>Supported since Zabbix 2.0.| |system.sw.os\[<info>\]|<|<|<|<| |<|Operating system information.|String|**info** - possible values:<br>*full* (default), *short* or *name*|Example:<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>Info is acquired from (note that not all files and options are present in all distributions):<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME parameter from /etc/os-release on systems supporting it, or /etc/issue.net (*name*)<br><br>Supported since Zabbix 2.0.| |system.sw.packages\[<package>,<manager>,<format>\]|<|<|<|<| |<|Listing of installed packages.|Text|**package** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**manager** - *all* (default) or a package manager<br>**format** - *full* (default) or *short*|Lists (alphabetically) installed packages whose name matches the given `package` regular [expression](/manual/regular_expressions#overview) (*all* lists them all).<br><br>Example:<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>Supported package managers (executed command):<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>If `format` is specified as *full*, packages are grouped by package managers (each manager on a separate line beginning with its name in square brackets).<br>If `format` is specified as *short*, packages are not grouped and are listed on a single line.<br><br>Supported since Zabbix 2.0.| |system.swap.in\[<device>,<type>\]|<|<|<|<| |<|Swap in (from device into memory) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapins), *sectors* (sectors swapped in), *pages* (pages swapped in).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.in\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.out\[<device>,<type>\]|<|<|<|<| |<|Swap out (from memory onto device) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapouts), *sectors* (sectors swapped out), *pages* (pages swapped out).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.out\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.size\[<device>,<type>\]|<|<|<|<| |<|Swap space size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*free* (free swap space, default), *pfree* (free swap space, in percent), *pused* (used swap space, in percent), *total* (total swap space), *used* (used swap space)<br>Note that *pfree*, *pused* are not supported on Windows if swap size is 0.<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.size\[,pfree\] → free swap space percentage<br><br>If *device* is not specified Zabbix agent will only take into account swap devices (files), physical memory will be ignored. For example, on Solaris systems *swap -s* command includes a portion of physical memory and swap devices (unlike *swap -l*).<br><br>Note that this key might report incorrect swap space size/percentage on virtualized (VMware ESXi, VirtualBox) Windows platforms. In this case you may use the `perf_counter[\700(_Total)\702]` key to obtain correct swap space percentage.| |system.uname|<|<|<|<| |<|Identification of the system.|String|<|Example of returned value (Unix):<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>Example of returned value (Windows):<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>On Unix since Zabbix 2.2.0 the value for this item is obtained with uname() system call. Previously it was obtained by invoking "uname -a". The value of this item might differ from the output of "uname -a" and does not include additional information that "uname -a" prints based on other sources.<br><br>On Windows since Zabbix 3.0 the value for this item is obtained from Win32\_OperatingSystem and Win32\_Processor WMI classes. Previously it was obtained from volatile Windows APIs and undocumented registry keys. The OS name (including edition) might be translated to the user's display language. On some versions of Windows it contains trademark symbols and extra spaces.<br><br>Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture.| |system.uptime|<|<|<|<| |<|System uptime in seconds.|Integer|<|In [item configuration](/manual/config/items/item#configuration), use **s** or **uptime** units to get readable values.| |system.users.num|<|<|<|<| |<|Number of users logged in.|Integer|<|**who** command is used on the agent side to obtain the value.| |vfs.dev.discovery|<|<|<|<| |<|List of block devices and their type. Used for low-level discovery.|JSON object|<|This item is supported on Linux platform only.<br><br>Supported since Zabbix 4.4.0.| |vfs.dev.read\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk read statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 devices (1023 individual and one for *all*).| |vfs.dev.write\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk write statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.write\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 (1023 individual and one for *all*).| |vfs.dir.count\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry count.|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to count, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT count. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT counted.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be counted. Smaller files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be counted. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be counted. More recent entries will not be counted. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be counted. Entries so old and older will not be counted (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never counted.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are counted only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be counted).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial count will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.count\[/dev\] - monitors number of devices in /dev (Linux)<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - monitors number of files in temporary directory (Windows)<br><br>Supported since Zabbix 4.0.0.| |vfs.dir.get\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry list.|JSON|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to list, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT list. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT listed.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be listed. Smaller files will not be listed. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be listed. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be listed. More recent entries will not be listed. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be listed. Entries so old and older will not be listed (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never listed.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are listed only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be listed).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial list will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.get\[/dev\] - retrieves device list in /dev (Linux)<br>⇒ vfs.dir.get\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - retrieves file list in temporary directory (Windows)<br><br>Supported since Zabbix 6.0.0.| |vfs.dir.size\[dir,<regex\_incl>,<regex\_excl>,<mode>,<max\_depth>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory size (in bytes).|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**mode** - possible values:<br>*apparent* (default) - gets apparent file sizes rather than disk usage (acts as `du -sb dir`), *disk* - gets disk usage (acts as `du -s -B1 dir`). Unlike du command, vfs.dir.size item takes hidden files in account when calculating directory size (acts as `du -sb .[^.]* *` within dir).<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Only directories with at least read permission for *zabbix* user are calculated.<br><br>On Windows any symlink is skipped and hard links are taken into account only once.<br><br>With large directories or slow drives this item may time out due to the Timeout setting in [agent](/manual/appendix/config/zabbix_agentd) and [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) configuration files. Increase the timeout values as necessary.<br><br>Examples:<br>⇒ vfs.dir.size\[/tmp,log\] - calculates size of all files in /tmp which contain 'log'<br>⇒ vfs.dir.size\[/tmp,log,\^.+\\.old$\] - calculates size of all files in /tmp which contain 'log', excluding files containing '.old'<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Supported since Zabbix 3.4.0.| |vfs.file.cksum\[file,<mode>\]|<|<|<|<| |<|File checksum, calculated by the UNIX cksum algorithm.|Integer - with `mode` as *crc32*<br><br>String - with `mode` as *md5*, *sha256*|**file** - full path to file<br>**mode** - *crc32* (default), *md5*, *sha256*|Example:<br>=> vfs.file.cksum\[/etc/passwd\]<br><br>Example of returned values (crc32/md5/sha256 respectively):<br>675436101<br>9845acf68b73991eb7fd7ee0ded23c44<br>ae67546e4aac995e5c921042d0cf0f1f7147703aa42bfbfb65404b30f238f2dc<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.contents\[file,<encoding>\]|<|<|<|<| |<|Retrieving contents of a file.|Text|**file** - full path to file<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)|Returns an empty string if the file is empty or contains LF/CR characters only.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Example:<br>=> vfs.file.contents\[/etc/passwd\]<br><br>This item is limited to files no larger than 64 Kbytes.<br><br>Supported since Zabbix 2.0.| |vfs.file.exists\[file,<types\_incl>,<types\_excl>\]|<|<|<|<| |<|Checks if file exists.|0 - not found<br><br>1 - file of the specified type exists|**file** - full path to file<br>**types\_incl** - list of file types to include, possible values: *file* (regular file, default (if types\_excl is not set)), *dir* (directory), *sym* (symbolic link), *sock* (socket), *bdev* (block device), *cdev* (character device), *fifo* (FIFO), *dev* (synonymous with "bdev,cdev"), *all* (all mentioned types, default if types\_excl is set).<br>**types\_excl** - list of file types to exclude, see types\_incl for possible values (by default no types are excluded)|Multiple types must be separated with a comma and the entire set enclosed in quotes "".<br>On Windows the double quotes have to be backslash '\\' escaped and the whole item key enclosed in double quotes when using the command line utility for calling zabbix\_get.exe or agent2.<br><br>If the same type is in both <types\_incl> and <types\_excl>, files of this type are excluded.<br><br>Examples:<br>=> vfs.file.exists\[/tmp/application.pid\]<br>=> vfs.file.exists\[/tmp/application.pid,"file,dir,sym"\]<br>=> vfs.file.exists\[/tmp/application\_dir,dir\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Note that the item may turn unsupported on Windows if a directory is searched within a non-existing directory, e.g. vfs.file.exists\[C:\\no\\dir,dir\] (where 'no' does not exist).| |vfs.file.get\[file\]|<|<|<|<| |<|Return information about a file.|JSON object|**file** - full path to file|Supported file types on UNIX-like systems: regular file, directory, symbolic link, socket, block device, character device, FIFO<br><br>Supported file types on Windows: regular file, directory, symbolic link<br><br>Example:<br>=> vfs.file.get\[/etc/passwd\] → return a JSON with information about the /etc/passwd file (type, user, permissions, SID, uid etc)<br><br>Supported since Zabbix 6.0.| |vfs.file.md5sum\[file\]|<|<|<|<| |<|MD5 checksum of file.|Character string (MD5 hash of the file)|**file** - full path to file|Example:<br>=> vfs.file.md5sum\[/usr/local/etc/zabbix\_agentd.conf\]<br><br>Example of returned value:<br>b5052decb577e0fffd622d6ddc017e82<br><br>The file size limit (64 MB) for this item was removed in version 1.8.6.<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.file.owner\[file,<ownertype>,<resulttype>\]|<|<|<|<| |<|Retrieve owner of a file.|Character string|**file** - full path to file<br>**ownertype** - *user* (default) or *group* (Unix only)<br>**resulttype** - *name* (default) or *id*; for id - return uid/gid on Unix, SID on Windows|Example:<br>=> vfs.file.owner\[/tmp/zabbix\_server.log\] → return file owner of /tmp/zabbix\_server.log<br>=> vfs.file.owner\[/tmp/zabbix\_server.log,,id\] → return file owner ID of /tmp/zabbix\_server.log<br><br>Supported since Zabbix 6.0.| |vfs.file.permissions\[file\]|<|<|<|<| |<|Return a 4-digit string containing the octal number with Unix permissions.|String|**file** - full path to the file|Not supported on Windows.<br><br>Example:<br>=> vfs.file.permissions\[/etc/passwd\] → return permissions of /etc/passwd, for example, '0644'<br><br>Supported since Zabbix 6.0.| |vfs.file.regexp\[file,regexp,<encoding>,<start line>,<end line>,<output>\]|<|<|<|<| |<|Find string in a file.|The line containing the matched string, or as specified by the optional `output` parameter|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|Only the first matching line is returned.<br>An empty string is returned if no line matched the expression.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `start line`, `end line` and `output` parameters are supported from version 2.2.<br><br>Examples:<br>=> vfs.file.regexp\[/etc/passwd,zabbix\]<br>=> vfs.file.regexp\[/path/to/some/file,"(\[0-9\]+)$",,3,5,\\1\]<br>=> vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\] → getting the ID of user *zabbix*| |vfs.file.regmatch\[file,regexp,<encoding>,<start line>,<end line>\]|<|<|<|<| |<|Find string in a file.|0 - match not found<br><br>1 - found|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).|Byte order mark (BOM) is ignored.<br><br>The `start line` and `end line` parameters are supported from version 2.2.<br><br>Example:<br>=> vfs.file.regmatch\[/var/log/app.log,error\]| |vfs.file.size\[file,<mode>\]|<|<|<|<| |<|File size (in bytes).|Integer|**file** - full path to file<br>**mode** - possible values:<br>*bytes* (default) or *lines* (empty lines are counted, too)|The file must have read permissions for user *zabbix*.<br><br>Example:<br>=> vfs.file.size\[/var/log/syslog\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.time\[file,<mode>\]|<|<|<|<| |<|File time information.|Integer (Unix timestamp)|**file** - full path to the file<br>**mode** - possible values:<br>*modify* (default) - last time of modifying file content,<br>*access* - last time of reading file,<br>*change* - last time of changing file properties|Example:<br>=> vfs.file.time\[/etc/passwd,modify\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.fs.discovery|<|<|<|<| |<|List of mounted filesystems and their types. Used for low-level discovery.|JSON object|<|Supported since Zabbix 2.0.<br><br>The {\#FSDRIVETYPE} macro is supported on Windows since Zabbix 3.0.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.get|<|<|<|<| |<|List of mounted filesystems, their types, disk space and inode statistics. Can be used for low-level discovery.|JSON object|<|Supported since Zabbix 4.4.5.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.inode\[fs,<mode>\]|<|<|<|<| |<|Number or percentage of inodes.|Integer - for number<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, //pfree // (free, percentage), *pused* (used, percentage)|Example:<br>=> vfs.fs.inode\[/,pfree\]| |vfs.fs.size\[fs,<mode>\]|<|<|<|<| |<|Disk space in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, *pfree* (free, percentage), *pused* (used, percentage)|In case of a mounted volume, disk space for local file system is returned.<br><br>Example:<br>=> vfs.fs.size\[/tmp,free\]<br><br>Reserved space of a file system is taken into account and not included when using the *free* mode.| |vm.memory.size\[<mode>\]|<|<|<|<| |<|Memory size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**mode** - possible values:<br>*total* (default), *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*, *used*, *pused* (used, percentage), *available*, *pavailable* (available, percentage)<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) support and [additional details](/manual/appendix/items/vm.memory.size_params) for this parameter.|This item accepts three categories of parameters:<br><br>1) *total* - total amount of memory;<br>2) platform-specific memory types: *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*;<br>3) user-level estimates on how much memory is used and available: *used*, *pused*, *available*, *pavailable*.| |web.page.get\[host,<path>,<port>\]|<|<|<|<| |<|Get content of web page.|Web page source as text (including headers)|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |web.page.perf\[host,<path>,<port>\]|<|<|<|<| |<|Loading time of full web page (in seconds).|Float|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |web.page.regexp\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<|<| |<|Find string on a web page.|The matched string, or as specified by the optional `output` parameter|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**length** - maximum number of characters to return<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `output` parameter is supported from version 2.2.<br><br>Example:<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]| |zabbix.stats\[<ip>,<port>\]|<|<|<|<| |<|Return a set of Zabbix server or proxy internal metrics remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).| |zabbix.stats\[<ip>,<port>,queue,<from>,<to>\]|<|<|<|<| |<|Return number of monitored items in the queue which are delayed on Zabbix server or proxy remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**queue** - constant (to be used as is)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.|  

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.
ja	#### サポートされているマクロ  ディスカバリは指定されたオブジェクトのすべてのインスタンスを{\#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).|
ja	##### サポートされているマクロ  次のマクロはディスカバリルール [フィルター](/manual/discovery/low_level_discovery#discovery_rule_filter) およびアイテム、トリガー、グラフのプロトタイプでの使用がサポートされています。  |マクロ|説明| |-----|-----------| |MBean 属性の検出|<| |{\#JMXVALUE}|属性値| |{\#JMXTYPE}|属性タイプ| |{\#JMXOBJ}|オブジェクト名| |{\#JMXDESC}|属性名を含むオブジェクト名| |{\#JMXATTR}|属性名| |MBean の検出|<| |{\#JMXDOMAIN}|MBean ドメイン. (*Zabbix予約名*)| |{\#JMXOBJ}|オブジェクト名. (*Zabbix予約名*)| |{\#JMX<key property>}|MBean プロパティ (like {\#JMXTYPE}, {\#JMXNAME}) (参照 [Limitations](#limitations) below).|

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.|
ja	### サポートされているマクロ  次のマクロはディスカバリルール[フィルター](/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).
ja	#### サポートされているマクロ  このディスカバリキーは、CPUモデル番号とステータスをそれぞれ識別する{\#CPU.NUMBER}と{\#CPU.STATUS}の2つのマクロを返します。 実際の物理プロセッサ、コア、ハイパースレッドを明確に判別できないことに注意してください。 Linux、UNIX、およびBSDシステムの{\#CPU.STATUS}はプロセッサのステータスを返します。これは"online"または"offline"のいずれかになります。 Windowsシステムではこの同じマクロが3番目の値（"unknown"）を表す場合があります。これは、プロセッサが検出されたもののそのプロセッサに関する情報がまだ収集されていないことを示します。  CPUディスカバリは、エージェントのコレクタープロセスに依存して、コレクターによって提供されるデータとの整合性を維持し、データの取得にかかるリソースを節約します。 これには、このアイテムキーがエージェントバイナリのテスト（-t）コマンドラインフラグで機能しないという効果があります。これにより、NOT\_SUPPORTEDステータスと、コレクタプロセスが開始されていないことを示す付随メッセージが返されます。  CPUの検出に基づいて作成できるアイテムのプロトタイプには、たとえば次のものがあります。  -   `system.cpu.util[{#CPU.NUMBER},<type>,<mode>]` -   `system.hw.cpu[{#CPU.NUMBER},<info>]`  アイテムキーの詳細な説明については、[Zabbixエージェントアイテムキー](/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.
ja	#### サポートされているマクロ  このディスカバリキーは、ブロックデバイスの名前とタイプをそれぞれ識別する{\#DEVNAME}と{\#DEVTYPE}の2つのマクロを返します。次に例を示します。  ``` {.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.
ja	#### サポートされているマクロ  ディスカバリルール[フィルター](/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  
ja	##### 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
ja	##### サポートされるパラメータ  作成されたMSIでは、以下のパラメータがサポートされています。  |番号|パラメータ|説明| |------|---------|-----------| |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.|  インストールするには、例えば、以下のように実行します。 <br>     SET INSTALLFOLDER=C:\Program Files\za <br>      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]"  または      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 security requirements and the mission-critical nature of the monitoring server, UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance, and resilience. Zabbix operates on market-leading versions.  Zabbix components are available and tested for the following platforms:  |Platform|Server|Agent|Agent2| |--------|------|-----|------| |Linux|x|x|x| |IBM AIX|x|x|\-| |FreeBSD|x|x|\-| |NetBSD|x|x|\-| |OpenBSD|x|x|\-| |HP-UX|x|x|\-| |Mac OS X|x|x|\-| |Solaris|x|x|\-| |Windows|\-|x|x|  ::: noteclassic Zabbix server/agent may work on other Unix-like operating systems as well. Zabbix agent is supported on all Windows desktop and server versions since XP.\ \ To prevent critical security vulnerabilities in Zabbix agent 2, it is compiled only with [supported Go releases](https://go.dev/doc/devel/release#policy). As of Go 1.21, the [minimum required Windows versions](https://go.dev/wiki/MinimumRequirements#windowswindows) are raised; therefore, since Zabbix 6.0.27, the minimum Windows version for Zabbix agent 2 is Windows 10/Server 2016. :::  ::: noteimportant Zabbix disables core dumps if compiled with encryption and does not start if the system does not allow disabling of core dumps. :::
ja	#### サポートするプラットフォーム  セキュリティ要件と監視サーバーのミッションクリティカルな性質から、UNIXは必要な性能と耐障害性、回復力を一貫して提供できる唯一のOSです。Zabbixは市場をリードするバージョンで動作します。  Zabbixのコンポーネントは以下のプラットフォームで動作確認されています：  |プラットフォーム|サーバー|エージェント|エージェント2| |--------|------|-----|------| |Linux|x|x|x| |IBM AIX|x|x|\-| |FreeBSD|x|x|\-| |NetBSD|x|x|\-| |OpenBSD|x|x|\-| |HP-UX|x|x|\-| |Mac OS X|x|x|\-| |Solaris|x|x|\-| |Windows|\-|x|x|  ::: noteclassic Zabbixサーバー/エージェントは他のUnix系OSでも動作する可能性があります。\ ZabbixエージェントはWindows XP以降の全てのWindowsデスクトップとサーバーのOSバージョンでサポートされています。\ \ Zabbixエージェント2の重大なセキュリティ脆弱性を防ぐために、[サポートされているGoリリース](https://go.dev/doc/devel/release#policy)のみでコンパイルされています。Go 1.21では、[Windowsバージョンの最小要件](https://go.dev/wiki/MinimumRequirements#windowswindows)が引き上げられています。したがって、Zabbix 6.0.27以降、Zabbixエージェント2におけるWindowsバージョンの最小要件はWindows 10/Server 2016です。 :::  ::: noteimportant Zabbixは、暗号化してコンパイルされている場合はコアダンプを無効にし、システムがコアダンプの無効化を許可していない場合は起動しません。 :::

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. :::
ja	#### サポートされているプラットフォーム  サーバーの処理のセキュリティ要件やミッションクリティカルな性質から、必要なパフォーマンス、フォールトトレランス、および復元力を一貫して提供できるOSはUNIXだけです。Zabbixは市場に出回っているバージョンで動作します。  Zabbixサーバーは、以下のプラットフォーム上での動作を確認済みです：  -   Linux -   Solaris -   AIX -   HP-UX -   Mac OS X -   FreeBSD -   OpenBSD -   NetBSD -   SCO Open Server -   Tru64/OSF1  ::: noteclassic Zabbixは他のUNIX系OSでも動作する可能性があります。 :::

en-us	### Supported platforms  Support for Debian 12 (Bookworm) has been added, and official packages are available for download on [Zabbix website](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=12&components=server_frontend_agent&db=mysql&ws=apache).
ja	### サポートされているプラットフォーム  Debian 12 (Bookworm) のサポートが追加され、公式パッケージは [Zabbix Webサイト](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=12&components=server_frontend_agent&db=mysql&ws=apache)からダウンロードできます。

en-us	#### Supported platforms  Zabbix agent 2 is supported on the following platforms:  -   Windows (all desktop and server versions [since Windows 10/Server 2016](/manual/installation/requirements#supported-platforms)) - available as a [pre-compiled binary](https://www.zabbix.com/download_agents?version=6.0+LTS&os=Windows&os_version=Any&hardware=amd64&encryption=OpenSSL&packaging=MSI&show_legacy=0) or in [Zabbix sources](https://www.zabbix.com/download_sources#60LTS) -   Linux - available in [distribution packages](https://www.zabbix.com/download?zabbix=6.0&os_distribution=alma_linux&os_version=9&components=agent_2&db=&ws=) or [Zabbix sources](https://www.zabbix.com/download_sources#60LTS)
ja	#### サポートされているプラ​​ットフォーム  Zabbixエージェント2は以下のプラットフォームでサポートされています：  -   Windows ([Windows 10/Server2016 以降](/manual/installation/requirements#supported-platforms)のすべてのバージョン - [コンパイル済み実行バイナリ](https://www.zabbix.com/download_agents?version=6.0+LTS&os=Windows&os_version=Any&hardware=amd64&encryption=OpenSSL&packaging=MSI&show_legacy=0)か[Zabbixソース](https://www.zabbix.com/download_sources#60LTS)で提供) -   Linux ([ディストリビューション用パッケージ](https://www.zabbix.com/download?zabbix=6.0&os_distribution=alma_linux&os_version=9&components=agent_2&db=&ws=)か[Zabbixソース](https://www.zabbix.com/download_sources#60LTS)で提供)

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  It is also possible to download legacy Zabbix agent binaries for [NetBSD](https://www.zabbix.com/download_agents?version=3.2&release=3.2.0&os=NetBSD&os_version=5.0&hardware=i386&encryption=No+encryption&packaging=Archive&show_legacy=1) and [HP-UX](https://www.zabbix.com/download_agents?version=2.4&release=2.4.4&os=HPUX&os_version=11.31&hardware=amd64&encryption=No+encryption&packaging=Archive&show_legacy=1), and those are compatible with current Zabbix server/proxy version.
ja	#### サポートしているプラットフォーム  Zabbixエージェントは以下のプラットフォームでの動作を[サポート](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  [NetBSD](https://www.zabbix.com/download_agents?version=3.2&release=3.2.0&os=NetBSD&os_version=5.0&hardware=i386&encryption=No+encryption&packaging=Archive&show_legacy=1)および[HP-UX](https://www.zabbix.com/download_agents?version=2.4&release=2.4.4&os=HPUX&os_version=11.31&hardware=amd64&encryption=No+encryption&packaging=Archive&show_legacy=1)用のレガシーZabbixエージェントバイナリをダウンロードすることもできます。これらは、現在のZabbixサーバー/プロキシバージョンと互換性があります。

en-us	#### Supported platforms  Zabbix proxy runs on the same list of [supported platforms](/manual/concepts/server#supported_platforms) as Zabbix server.
ja	#### サポートされているプラ​​ットフォーム  Zabbixプロキシは、Zabbixサーバーと同じ[サポートされているプラットフォーム](/manual/concepts/server#supported_platforms)のリストに記載されているプラットフォームで実行可能です。

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 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.
ja	#### 対応セグメント  |セグメント|説明| |--|--------| |`<name>`|オブジェクト プロパティを名前で照合します| |`*`|すべてのオブジェクト プロパティに一致します| |`['<name>']`|オブジェクト プロパティを名前で照合します| |`['<name>', '<name>', ...]`|リストされた名前のいずれかでオブジェクト プロパティを照合します| |`[<index>]`|配列要素をインデックスで照合します| |`[<number>, <number>, ...]`|リストされたインデックスのいずれかで配列要素を照合します| |`[*]`|すべてのオブジェクト プロパティまたは配列要素に一致します| |`[<start>:<end>]`|定義された範囲で配列要素を一致させます:<br>**<start>** - 一致する最初のインデックス (含む)。 指定しない場合は、最初からすべての配列要素に一致します。 負の場合は、配列の末尾からの開始オフセットを指定します。<br>**<end>** - 一致する最後のインデックス (除外)。 指定されていない場合は、すべての配列要素を最後まで一致させます。 負の場合、配列の末尾からの開始オフセットを指定します。| |`[?(<expression>)]`|フィルター式を適用してオブジェクト/配列要素を一致させます|  前例を無視して一致するセグメント (切り離されたセグメント) を見つけるには、接頭辞 '..' を付ける必要があります。 たとえば、`$..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.|
ja	#### サポートされているシンプルチェック  サポートされているシンプルチェックの一覧です:  参照:  -   [VMware監視アイテムキー](/manual/config/items/itemtypes/simple_checks/vmware_keys)  |Key|<|<|<| |--|--|------|------| |**説明**|**戻り値**|**パラメータ**|**コメント**| |**icmpping**\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<| |ICMP pingによるホストへのアクセス。|0 - ICMP ping 失敗<br><br>1 - ICMP ping 成功|**target** - ホストIPまたはDNS名<br>**packets** - パケット数<br>**interval** - 連続するパケット間の時間 (ミリ秒単位)<br>**size** - パケットサイズ (バイト単位)<br>**timeout** - タイムアウト (ミリ秒単位)|例:<br>=> icmpping\[,4\] → 4 つのパケットのうち少なくとも 1 つのパケットが返された場合、アイテムは 1 を返します。<br><br>参照: [デフォルト値](simple_checks#icmp_ping)の表| |**icmppingloss**\[<target>,<packets>,<interval>,<size>,<timeout>\]|<|<|<| |パケットロスの割合|浮動小数点|**target** - ホストIPまたはDNS名<br>**packets** - パケット数<br>**interval** - 連続するパケット間の時間 (ミリ秒単位)<br>**size** - パケットサイズ (バイト単位)<br>**timeout** - タイムアウト (ミリ秒単位)|参照: [デフォルト値](simple_checks#icmp_ping)の表| |**icmppingsec**\[<target>,<packets>,<interval>,<size>,<timeout>,<mode>\]|<|<|<| |ICMP ping 応答時間 (秒単位)|浮動小数点|**target** - ホスト IP または DNS 名<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_ping)の表| |**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 アドレスまたは DNS 名 (デフォルトではホスト 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>*https* および *telnet* サービスは、Zabbix 2.0 以降でサポートされています。| |**net.tcp.service.perf**\[service,<ip>,<port>\]|<|<|<| |TCP サービスのパフォーマンスをチェックします|浮動小数点<br><br>0.000000 - サービス停止<br><br>秒 - サービスへの接続にかかった秒数|**service** - 使用可能な値: *ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (参照:[詳細](/manual/appendix/items/service_check_details))<br>**ip** - IP アドレスまたは DNS 名 (デフォルトではホスト IP/DNS が使用されます)<br>**port** - ポート番号(デフォルトでは、標準のサービス ポート番号が使用されます)|例:<br>=> net.tcp.service.perf\[ssh\] → SSH サーバーの初期応答速度をテストします。<br><br>ポートを示す *tcp* サービスが必須であることに注意してください。<br>暗号化されたプロトコルのチェック (ポート 993 の IMAP またはポートの POP など) 995) は現在サポートされていません。 回避策として、これらのチェックには net.tcp.service.perf\[tcp,<ip>,port\] を使用してください。<br>*https* および *telnet* サービスは、Zabbix 2.0 以降でサポートされています。<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 アドレスまたは DNS 名 (デフォルトではホスト 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>秒 - サービスからの応答の待機にかかった秒数|**service** - 使用可能な値: *ntp* (参照[詳細](/manual/appendix/items/service_check_details))<br>**ip** - IP アドレスまたは DNS 名 (デフォルトではホスト 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. :::
ja	#### サポートされている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, yet 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.
ja	#### サポートされているZabbixプロキシ  Zabbix 6.0と互換性を持たせるには、プロキシが同じメジャーバージョンである必要があります。したがって、Zabbix6.0.xプロキシのみがZabbix6.0.xサーバーで動作できます。  ::: noteimportant アップグレードされていないプロキシがアップデート済みのサーバーにデータを報告することはできなくなりました。この方法はZabbixによって推奨もサポートもされていませんでしたが、現在は正式に無効になっています。[アップグレード手順](/manual/installation/upgrade)も参照してください。 :::  互換性のないZabbixデーモンバージョンの使用に関する警告がログに記録されます。

en-us	#### Support for ARM64/AArch64  ARM64/AArch64 installation packages are now available for Debian, RHEL 8, 9 and its derivatives, as well as SLES/OpenSUSE Leap 15.
ja	#### ARM64/AArch64 をサポート  ARM64/AArch64 インストール パッケージが、Debian、RHEL 8、9 およびその派生製品、および SLES/OpenSUSE Leap 15 で利用できるようになりました。

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
ja	### 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
ja	##### AES128からAES256への切り替え  Zabbixはデータ用のビルトインデフォルトとしてAES128を使用しています。証明書を使用していて、OpenSSL 1.1.1 の <br> 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*` パラメータも定義されています。PSK暗号スイートは、server / proxy で完全に無効に することはできません。 :::  `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. :::
ja	##### インターフェイスを到達可能に戻す  到達不能期間が終了すると、インターフェイスが再度ポーリングされ、インターフェイスを到達不能状態にしたアイテムの優先度が低下します。到達不能なインターフェイスが再び到達可能になると、監視は自動的に通常に戻ります。      resuming Zabbix agent checks on host "New host": connection restored  ::: noteclassic インターフェイスが使用可能になっても、ホストは次の2つの理由ですべてのアイテムをすぐにポーリングしません。  -   ホストが過負荷になる可能性があります。 -   インターフェイスの復元時間は、計画されたアイテムのポーリングスケジュール時間と常に一致するとは限りません。  そのため、インターフェイスが使用可能になった後、アイテムはすぐにはポーリングされず、次のポーリングラウンドに再スケジュールされます。 :::

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.
ja	#### 生の値への切り替え  右上のドロップダウンで、単純なグラフから *Values/500 latest values* のリストへ切り替えることができます。 これは、グラフを構成する数値を表示するのに便利です。  ここで表示される数値は生のものであり、単位や数値の後処理は行われていません。しかし、値のマッピングは適用されます。

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. 
ja	 ### シンボリックリンク名の展開  シンボリック リンク名とシンボリック リンクのフル パスは、シンボリック リンク ターゲットに解決される代わりに、`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}
ja	## 概要    **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}
ja	## 概要  **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}
ja	## 概要  **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}
ja	## 概要  **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}
ja	## 概要  **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}
ja	## 概要  **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}
ja	## 概要  **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}
ja	## 概要  **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
ja	#### 文法  集計は、どちらかの作業で取得することができます。:  -   history of items:  ```{=html} <!-- --> ```     aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...)  -   a [foreach function](/manual/appendix/functions/aggregate/foreach)     を唯一のパラメータとして:  ```{=html} <!-- --> ```     aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod))  where:  - aggregate_function` は、サポートされている [aggregate functions](/manual/appendix/functions/aggregate#aggregate-functions-1): avg, max, min, sum, etc のいずれかである。 - foreach_function` は、サポートされている foreach 関数 (avg_foreach, count_foreach など) のうちの 1 つです。  Foreach関数は、複数の項目の履歴を扱うために[item filter](/manual/appendix/functions/aggregate/foreach#item-filter)を使用し、各項目につき1つの値を配列で返します。  ::: noteclassic 集計結果がfloat値の場合、集計された情報の item タイプが*Numeric(unsigned)*であれば、整数に切り捨てられます。 :::  以下の場合、集計計算がサポートされなくなる可能性があります:  - 参照した項目が見つからない（item キーが正しくない、item が存在しない、含まれるグループがすべて正しくない場合に   発生する可能性があります） - 関数を計算するためのデータがない

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|The return value of the item is a standard output together with a standard error produced by the command. Exit code checking is not performed.<br>See also: [Command execution](/manual/appendix/command_execution)<br><br>To be processed correctly, the return value of the command must be of `text` data type. An empty result is also allowed.<br><br>The return value is limited to 16MB (including trailing whitespace that is truncated); [database limits](/manual/config/items/item#text-data-limits) also apply.<br><br>Note that system.run items are disabled by default. Learn how to [enable them](/manual/config/items/restrict_checks).<br><br>Example:<br>=> system.run\[ls -l /\] → detailed file list of root directory.| |**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.|
ja	##### システムデータ  |アイテムキー|<|<|<| |--|--|------|------| |説明|戻り値|パラメータ|コメント| |**system.boottime**|<|<|<| |システムの起動時間|Integer (Unix タイムスタンプ)| | | |**system.cpu.discovery**|<|<|<| |検出された CPU/CPU コアのリスト。ローレベルディスカバリに使用されます。|JSON オブジェクト| |2.4.0 以降のすべてのプラットフォームでサポートされています| |**system.cpu.intr**|<|<|<| |デバイスの割り込み|Integer| | | |**system.cpu.load**\[<cpu>,<mode>\]|<|<|<| |[CPU 負荷](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - 使用可能な値:<br>*all* (デフォルト)、*percpu* (バージョン2.0以降; 総負荷をオンライン CPU 数で割ったもの)<br>**mode** - 使用可能な値:<br>*avg1* (1 分間の平均、デフォルト)、*avg5*、*avg15*|例:<br>=> system.cpu.load\[,avg5\].| |**system.cpu.num**\[<type>\]|<|<|<| |CPU の数。|Integer|**type** - 使用可能な値:<br>*online* (デフォルト)、*max*|例:<br>=> system.cpu.num| |**system.cpu.switches**|<|<|<| |コンテキスト スイッチの数|Integer| | | |**system.cpu.util**\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<| |CPU 使用率|Float|**cpu** - *<CPU番号>* または *all* (デフォルト)<br>**type** - 使用可能な値:<br>*user*(デフォルト)、*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>**モード** - 使用可能な値:<br>*avg1* (1 分間の平均、デフォルト)、*avg5*、*avg15*<br>**logical\_or\_physical** (バージョン 5.0.3 以降、AIX のみ) - 使用可能な値: *logical* (デフォルト)、*physical*。このパラメーターは AIX でのみサポートされます。|Windows では、値は *Processor Time* パフォーマンス カウンターを使用して取得されます。 Windows 8 以降、タスク マネージャーは *Processor Utility* パフォーマンス カウンターに基づいて CPU 使用率を表示しますが、以前のバージョンでは *Processor Time* カウンターでした。<br><br>例:<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>\]|<|<|<| |システムのホスト名|String|**type** (Windows でのみサポートされるバージョン 5.4.7 より前) - 使用可能な値:*netbios* (Windows のデフォルト),*host* (Linux のデフォルト),*shorthost* (バージョン 5.4.7 以降; 最初のドットの前のホスト名の一部、ドットのない名前の完全な文字列を返します)<br>**transform** (バージョン 5.4.7 以降) - 使用可能な値:<br>*none* (デフォルト)、*lower* (小文字に変換)|この値は、Windows では GetComputerName() (**netbios** の場合) または gethostname() (**host** の場合) 関数によって取得され、他のシステムでは uname() システム API 出力から `nodename` を取得することによって取得されます。<br><br>戻り値の例:<br>*Linux* の場合:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → 例<br>*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>\]|<|<|<| |シャーシ情報|String|**情報** - フル (デフォルト)、モデル、シリアル、タイプ、ベンダーのいずれか|例: 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>sysfsやメモリから読み込んで値を取得するため、**rootパーミッション**が必要です。<br><br>Zabbix 2.0 以降でサポートされています。| |**system.hw.cpu**\[<cpu>,<info>\]|<|<|<| |CPU情報|String または integer|**cpu** - *<CPU 番号>* または *all* (デフォルト)<br>**info** - 使用可能な値:<br>*full* (デフォルト),*curfreq*, *maxfreq*, *model*, *vendor*|例:<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 デバイスのリスト|Text|**type** (バージョン 2.0 以降) - *pci* (デフォルト) または *usb*|例:<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 アドレスのリスト|String|**インターフェース** - *all* (デフォルト) または [正規表現](/manual/regular_expressions#overview)<br>**format** - *full* (デフォルト) または *short*|名前が指定された `interface` [正規表現](/manual/regular_expressions#overview) に一致するインターフェイスの MAC アドレスを一覧表示します (*all* すべてのインターフェイスのリスト)。<br><br>例:<br>=> system .hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>format が *short* と指定されている場合、インターフェース名と同一の MAC アドレスはリストされません。<br><br>Zabbix 2.0 以降でサポートされています。| |**system.localtime**\[<type>\]|<|<|<| |システム時刻|Integer - `type` を *utc* として使用<br><br>String - `type` を *local* として使用|**type** (バージョン 2.0 以降) - 使用可能な値:<br>*utc* - (デフォルト) エポック (00:00:00 UTC、1970 年 1 月 1 日) からの時間 (秒単位)<br>*local* - "yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm"形式の時刻|[パッシブ チェック](/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>*注*: system.run 項目はデフォルトで無効になっています。 [有効にする](/manual/config/items/restrict_checks)方法。<br><br>項目の戻り値は、コマンドが生成する標準エラーとともに標準出力となります。 終了コードはチェックされません。<br><br>Zabbix 2.4.0以降、空の結果が許可されます。<br>[コマンド実行](/manual/appendix/command_execution)も参照してください。| |**system.stat**\[resource,<type>\]|<|<|<| |システム統計|Integer または float|**ent** - このパーティションが受け取る資格のあるプロセッサ ユニットの数 (float)<br>**kthr,<type>** - カーネル スレッドの状態に関する情報:<br>*r* - 実行可能なカーネルの平均数スレッド (float)<br>*b* - 仮想メモリ マネージャーの待機キューに配置されたカーネル スレッドの平均数 (float)<br>**memory,<type>** - 仮想メモリと実メモリの使用に関する情報: <br>*avm* - アクティブな仮想ページ (整数)<br>*fre* - フリー リストのサイズ (整数)<br>**page,<type>** - ページ フォールトとページング アクティビティに関する情報:< br>*fi* - 1 秒あたりのファイル ページイン (float)<br>*fo* - 1 秒あたりのファイル ページアウト (float)<br>*pi* - ページング スペースからページ インされたページ (float)<br> *po* - ページング スペースにページ アウトされたページ (float)<br>*fr* - 解放されたページ (ページ置換) (float)<br>*sr* - ページ置換アルゴリズムによってスキャンされたページ (float)<br>* *faults,<type>** - トラップと割り込みレート:<br>*in* - デバイス割り込み (float)<br>*sy* - システム コール (float)<br>*cs* - カーネル スレッド コンテキスト スイッチ ( float)<b r>**cpu,<type>** - プロセッサ時間の使用率の内訳:<br>*us* - ユーザー時間 (float)<br>*sy* - システム時間 (float)<br>*id* - アイドル時間 (float)<br>*wa* - システムに未処理のディスク/NFS I/O 要求があったアイドル時間 (float)<br>*pc* - 消費された物理プロセッサの数 (float)< br>*ec* - 消費されたライセンス容量のパーセンテージ (float)<br>*lbusy* - ユーザーおよびシステム レベルで実行中に発生した論理プロセッサの使用率を示します (float)<br>*app * - 共有プールで使用可能な物理プロセッサを示します (float)<br>**disk,<type>** - ディスク統計:<br>*bps* - ドライブに転送 (読み取りまたは書き込み) されたデータの量を 1 秒あたりのバイト数 (整数) で示します。<br>*tps* - 物理ディスク/テープに発行された 1 秒あたりの転送数を示します (float)| |**system.sw.arch**|<|<|<| |ソフトウェア アーキテクチャ情報|String| |例:<br>=> system.sw.arch → i686<br><br>uname()関数から情報を取得します。<br><br>Zabbix 2.0 以降でサポートされています。| |**system.sw.os**\[<info>\]|<|<|<| |OS情報|String|**info** - 使用可能な値:<br>*full* (デフォルト)、*short* または *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>サポートしているシステムの /etc/os-release の PRETTY\_NAME パラメータ、または /etc/issue.net (*name*)<br><br>Zabbix 2.0 以降でサポートされています。| |**system.sw.packages**\[<package>,<manager>,<format>\]|<|<|<| |インストール済みパッケージのリスト|Text|**パッケージ** - *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*、パッケージはグループ化されず、1 行にリストされます。<br><br>Zabbix 2.0 以降でサポートされています。| |**system.swap.in**\[<device>,<type>\]|<|<|<| |(デバイスからメモリに) 統計情報をスワップします|Integer|**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>\]|<|<|<| |(メモリからデバイスに) 統計情報をスワップアウトします|Integer|**device** - スワップに使用されるデバイス (デフォルトは *all*)<br>**type** - 使用可能な値:<br>*count* (スワップアウトの数)、*sectors* (スワップアウトされたセクター)、 *pages* (スワップアウトされたページ)。<br>このパラメーターの詳細については、[プラットフォーム固有](/manual/appendix/items/supported_by_platform) も参照してください。|例:<br>=> system.swap.out\[,pages\]<br><br>この情報のソース:<br>/proc/swaps、/proc/partitions、/proc/stat (Linux 2.4)<br>/proc/swaps、/proc/diskstats、/proc/vmstat (Linux 2.6)| |**system.swap.size**\[<device>,<type>\]|<|<|<| |スワップ領域のサイズ (バイト単位または合計に対する割合)|Integer - バイトの場合<br><br>Float - パーセンテージの場合|**device** - スワップに使用されるデバイス (デフォルトは *all*)<br>**type** - 使用可能な値:<br>*free* (空きスワップ領域、デフォルト)、*pfree* (空きスワップ領域、パーセント)、*pused* (使用済みスワップ領域、パーセント)、*total* (合計スワップ領域)、*used* (使用済みスワップ領域)<br>スワップ サイズが 0 の場合、*pfree*、*pused* は Windows ではサポートされないことに注意してください。<br>このパラメータの詳細については、[プラットフォーム固有](/manual/appendix/items/supported_by_platform) も参照してください。|例:<br>=> system.swap.size\[,pfree\] → 空きスワップ領域の割合<br><br>*device* が指定されていない場合、Zabbix エージェントはスワップ デバイス (ファイル) のみを考慮し、物理メモリは無視されます。 たとえば、Solaris システムでは、*swap -s* コマンドには物理メモリとスワップ デバイスの一部が含まれます (*swap -l* とは異なります)<br><br>このキーは、仮想化 (VMware ESXi、VirtualBox) Windows プラットフォームで誤ったスワップ領域のサイズ/割合を報告する場合があることに注意してください。 この場合、`perf_counter[\700(_Total)\702]` キーを使用して正しいスワップ領域のパーセンテージを取得できます。| |**system.uname**|<|<|<| |システムのID|String| |戻り値の例 (Unix):<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: 月 11 月 i386<br><br>戻り値の例 (Windows):<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>Zabbix 2.2.0以降のUnixでは、このアイテムの値はuname()システムコールで取得されます。以前は"uname -a"を呼び出すことによって取得されていました。この項目の値は、"uname -a"の出力とは異なる場合があり、他のソースに基づいて"uname -a"が出力する追加情報は含まれません。<br><br>Zabbix 3.0 以降の Windows では、この項目の値は Win32\_OperatingSystem および Win32\_Processor WMI クラスから取得されます。以前は、揮発性の Windows API および文書化されていないレジストリ キーから取得されていました。 OS 名 (エディションを含む) は、ユーザーの表示言語に翻訳される場合があります。一部のバージョンの Windows では、商標記号と余分なスペースが含まれています。<br><br>Windows では OS アーキテクチャを返しますが、Unix では CPU アーキテクチャを返します。| |**system.uptime**|<|<|<| |システム稼働時間 (秒単位)|Integer| |[item configuration](/manual/config/items/item#configuration) では、**s** または **uptime** 単位を使用して読み取り可能な値を取得します。| |**system.users.num**|<|<|<| |ログインしているユーザーの数|Integer| |**who** コマンドは、エージェント側で値を取得するために使用されます|

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.|
ja	### Systemd  |キー|<|<|<| |--|--|------|------| |**説明**|**戻り値**|**パラメータ**|**コメント**| |systemd.unit.get\[unit name,<interface>\]|<|<|<| |systemd ユニットのすべてのプロパティを返します|JSONオブジェクト|**unit name** - ユニット名 (アイテム プロトタイプで {\#UNIT.NAME} マクロを使用して名前を見つけることができます)<br>**interface** - ユニット インターフェイス タイプ。使用可能な値: *Unit* (デフォルト), *Service*, *Socket*, *Device*, *Mount*, *Automount*, *Swap*, *Target*, *Path*|この項目は Linux プラットフォームでのみサポートされています。<br><br>Unit インターフェイスの LoadState、ActiveState、および UnitFileState は、テキストと整数として返されます。<br>`"ActiveState":{"state":1,"text":"active"}`| |systemd.unit.info\[unit name,<property>,<interface>\]|<|<|<| |Systemd ユニットインフォメーション|文字列|**unit name** - ユニット名 (アイテム プロトタイプで {\#UNIT.NAME} マクロを使用して名前を見つけることができます)<br>**property** - unit プロパティ (例: ActiveState (デフォルト),LoadState,Description)<br>**interface** - ユニット インターフェイス タイプ (例: 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 ユニットのアクティブ状態 (アクティブ、リロード中、非アクティブ、失敗、アクティブ化、非アクティブ化) 情報を収集します<br>=> systemd.unit.info\["{\#UNIT.NAME}",LoadState\] - 検出された systemd ユニットの負荷状態情報を収集する<br>=> systemd.unit.info\[mysqld.service,Id\] - サービス技術名の取得(mysqld.service)<br>=> systemd.unit.info\[mysqld.service,Description\] - サービスの説明を取得する(MySQL Server)<br>=> systemd.unit.info\[mysqld.service,ActiveEnterTimestamp\] - サービスが最後にアクティブ状態になった時刻を取得する(1562565036283903)<br>=> systemd.unit.info\[dbus.socket,NConnections,Socket\] - このソケット ユニットからの接続数を収集する| |systemd.unit.discovery\[<type>\]|<|<|<| |systemd ユニットとその詳細のリスト。 [ローレベルディスカバリ](/manual/discovery/low_level_discovery/examples/systemd)に使用|JSONオブジェクト|**type** - 使用可能な値: *all*, *automount*, *device*, *mount*, *path*, *service* (デフォルト), *socket*, *swap*, *target*|この項目は、Linux プラットフォームでのみサポートされています。|

en-us	#### - System requirements
ja	#### システム要件

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. :::
ja	##### システム要件：  - *RAM* : 1.5 GB - *ディスク容量* : 仮想マシンに少なくとも8GBを割り当てる必要があります  ZabbixインストールCD/DVDのブートメニュー：  ![](../../assets/en/manual/installation_cd_boot_menu1.png){width="600"}  Zabbixアプライアンスには、（MySQLで構成および実行されている）ZabbixサーバーとWebインターフェースが含まれています。  Zabbix仮想アプライアンスは次の形式で利用できます。  - VMWare（.vmx） - オープン仮想化フォーマット（.ovf） - Microsoft Hyper-V 2012（.vhdx） - Microsoft Hyper-V 2008（.vhd） - KVM、Parallels、QEMU、USBスティック、VirtualBox、Xen（.raw） - KVM、QEMU（.qcow2）  開始するには、アプライアンスを起動し、アプライアンスがDHCPで設定されたIPにブラウザーで接続します。  ::: 注意  ホストでDHCPを有効にする必要があります。 :::  仮想マシン内からIPアドレスを取得するには、次のコマンドを実行します。        ip addr show  ZabbixのWebインターフェースにアクセスするには、**http：// <host\_ip>**にアクセスします（ホストのブラウザからのアクセスについては、VMネットワーク設定でブリッジモードを有効にする必要があります）。  :::メモ アプライアンスがHyper-Vで起動しない場合は、Ctrl + Alt+F2を押してttyセッションを切り替えることができます。 :::

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.
ja	#### system.run と AllowKey  myscript.shのような仮想スクリプトは、Zabbix agent を介してホスト上でいくつかの方法で実行することができます:  1\. passive チェック や active チェックの item キーとして、例えば :  -   system.run\[myscript.sh\] -   system.run\[myscript.sh,wait\] -   system.run\[myscript.sh.nowait\]  ここで、"wait"、"nowait "を追加するか、第2引数を省略し、system.run\[ \]のデフォルト値を使用することができる。  2\. グローバルスクリプトとして（フロントエンドまたはAPIでユーザーによって開始される）  ユーザはこのスクリプトを *Administration* → *Scripts* で "Commands" 入力フィールドに "myscript.sh" を入力し、<br> "Execute on: Zabbix agent" を設定します。フロントエンドまたはAPIから呼び出されると、Zabbixサーバは agent に以下を<br> 送信します。:  -   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 / agent 2 パラメータに設定します。

en-us	#### - System Services  Systemd services are available:      systemctl list-units zabbix*
ja	#### - システムサービス  Systemdサービスが利用可能です：      systemctl list-units zabbix\*

en-us	#### System stats  ![](../../../../../assets/en/manual/web_interface/system_information1.png){width="600"}  Displayed data:  |Parameter|Value|Details| |---------|-----|-------| |*Zabbix server is running*|Status of Zabbix server:<br>**Yes** - server is running<br>**No** - server is not running<br>*Note:* To display the rest of the information the web frontend needs the server to be running and there must be at least one trapper process started on the server (StartTrappers parameter in [zabbix\_server.conf](/manual/appendix/config/zabbix_server) file > 0).|Location and port of Zabbix server.| |*Number of hosts*|Total number of hosts configured is displayed.|Number of monitored hosts/not monitored hosts.| |*Number of templates*|Total number of templates is displayed.|<| |*Number of items*|Total number of items is displayed.|Number of monitored/disabled/unsupported items.<br>Items on disabled hosts are counted as disabled.| |*Number of triggers*|Total number of triggers is displayed.|Number of enabled/disabled triggers. \[Triggers in problem/ok state.\]<br>Triggers assigned to disabled hosts or depending on disabled items are counted as disabled.| |*Number of users*|Total number of users configured is displayed.|Number of users online.| |*Required server performance, new values per second*|The expected number of new values processed by Zabbix server per second is displayed.|*Required server performance* is an estimate and can be useful as a guideline. For precise numbers of values processed, use the `zabbix[wcache,values,all]` [internal item](/manual/config/items/itemtypes/internal).<br><br>Enabled items from monitored hosts are included in the calculation. Log items are counted as one value per item update interval. Regular interval values are counted; flexible and scheduling interval values are not. The calculation is not adjusted during a "nodata" maintenance period. Trapper items are not counted.| |*Database history tables upgraded*|Database upgrade status:<br>**No** - database history tables have not been upgraded|This field is displayed if database upgrade to extended range for numeric (float) values has not been completed. See [instructions for](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values) enabling an extended range of numeric (float) values.| |*High availability cluster*|Status of [high availability cluster](/manual/concepts/server/ha) for Zabbix server:<br>**disabled** - standalone server<br>**enabled** - at least one high availability node exists|If enabled, the failover delay is displayed.|  *System information* will also display an error message if:  -   the database used does not have the required character set or     collation (UTF-8); -   the version of the database is below or above [supported     range](/manual/installation/requirements#required_software)     (available only to users with the Super admin role type).
ja	#### システム情報  ![](../../../../../assets/en/manual/web_interface/system_information1.png){width="600"}  表示情報  |パラメータ|値|詳細| |---------|-----|-------| |*Zabbix サーバーの起動*|Zabbixサーバーのステータス：<br>**はい** - サーバーは実行中です<br>**いいえ** - サーバーは実行されていません<br>*注：*残りの情報を表示するには、サーバーのStartTrappersパラメーターが[zabbix\_server.conf](/manual/appendix/config/zabbix_server) ファイルにて >0 であり、少なくとも1つのトラッパープロセスが開始されている必要があります。|Zabbixサーバーの場所とポート| |*ホスト数（有効/無効）*|構成されているホストの総数が表示されます|監視対象ホスト/監視対象外ホストの数| |*テンプレート数*|テンプレートの総数が表示されます|<| |*アイテム数（有効/無効/取得不可）*|アイテムの総数が表示されます|有効/無効/取得不可のアイテム数<br>無効なホスト上のアイテムは無効としてカウントされます| |*トリガー数（有効/無効［障害/正常］）*|トリガーの総数が表示されます|有効/無効なトリガーの数 \[障害/正常のトリガー\]<br>無効なホストに割り当てられたトリガー、または無効なアイテムに依存するトリガーは、無効としてカウントされます| |*ユーザー数（オンライン）*|ユーザーの総数が表示されます|オンラインユーザー数| |*1秒あたりの監視項目数(Zabbixサーバーの要求パフォーマンス)*|Zabbixサーバーによって1秒あたりに処理される監視項目数が表示されます|*サーバーの要求パフォーマンス*は推定値であり、ガイドラインとして役立ちます。 処理される値の正確な数については、 `zabbix[wcache,values,all]` [internal item](/manual/config/items/itemtypes/internal)を参照してください。<br><br>監視対象ホストからの有効なアイテムが値に含まれます。 ログアイテムは、アイテムの更新間隔ごとに1つの値としてカウントされます。 通常の間隔値はカウントされますが、 柔軟なスケジューリング間隔の値はカウントされません。 "nodata" メンテナンス期間中は計算されません。 トラッパーアイテムはカウントされません。| |*データベース履歴テーブルのアップグレード*|データベースのアップグレードステータス：<br> **いいえ** - データベース履歴テーブルはアップグレードされていません|このフィールドは、数値（浮動小数点）値の拡張範囲へのデータベースのアップグレードが完了していない場合に表示されます。[手順](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values)を参照して、数値（浮動小数点）の範囲を拡張できるようにします。| |*HAクラスター*|Zabbixサーバーの[高可用性クラスター](/manual/concepts/server/ha)のステータス：<br>**無効** - スタンドアロンサーバー<br>**有効** - 少なくとも1つの高可用性ノードが存在する| 有効の場合、フェイルオーバーディレイが表示されます|  *システム情報*は、次の場合にもエラーメッセージを表示します。  -   使用されているデータベースに必要な文字セットまたは照合（UTF-8）がありません。 -   データベースのバージョンが[サポートされている範囲](/manual/installation/requirements#required_software)外（スーパー管理者ユーザーのみが使用できます）

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). :::  
ja	##### 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). :::  