en-us	#### Using a custom expression filter  Create an LLD rule with a filter that will use a custom expression to evaluate the conditions. The LLD rule must only discover objects the "{\#MACRO1}" macro value of which matches both regular expression "regex1" and "regex2", and the value of "{\#MACRO2}" matches either "regex3" or "regex4". The formula IDs "A", "B", "C" and "D" have been chosen arbitrarily.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": 0,         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 3,             "formula": "(A and B) and (C or D)",             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1",                     "formulaid": "A"                 },                 {                     "macro": "{#MACRO1}",                     "value": "@regex2",                     "formulaid": "B"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex3",                     "formulaid": "C"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex4",                     "formulaid": "D"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```
zh-cn	#### 使用自定义表达式过滤器  使用将使用自定义表达式评估条件的过滤器创建 LLD 规则。 LLD 规则必须只发现“{\#MACRO1}”宏值同时匹配正则表达式“regex1”和“regex2”且“{\#MACRO2}”值匹配“regex3”或“regex4”的对象”。公式 ID“A”、“B”、“C”和“D”是任意选择的。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 3,             "formula": "(A and B) and (C or D)",             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1",                     "formulaid": "A"                 },                 {                     "macro": "{#MACRO1}",                     "value": "@regex2",                     "formulaid": "B"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex3",                     "formulaid": "C"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex4",                     "formulaid": "D"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Using a custom expression filter  Create a trigger action that will use a custom filter condition. The action must send a message for each trigger with severity higher or equal to "Warning" for hosts "10084" and "10106". The formula IDs "A", "B" and "C" have been chosen arbitrarily.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 3,             "formula": "A and (B or C)",             "conditions": [                 {                     "conditiontype": 4,                     "operator": 5,                     "value": "2",                     "formulaid": "A"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084",                     "formulaid": "B"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10106",                     "formulaid": "C"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```  
zh-cn	#### 使用自定义表达式筛选器  创建使用自定义筛选器条件的触发器动作。该动作必须为每个触发器发送一个消息，其严重程度高于或等于主机 `10084` 和 `10106` 的 `警告`。公式 ID `A`、`B`和 `C` 都是任意选择的。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "def_shortdata": "{TRIGGER.NAME}: {TRIGGER.STATUS}",         "def_longdata": "{TRIGGER.NAME}: {TRIGGER.STATUS}\r\nLast value: {ITEM.LASTVALUE}\r\n\r\n{TRIGGER.URL}",         "filter": {             "evaltype": 3,             "formula": "A and (B or C)",             "conditions": [                 {                     "conditiontype": 4,                     "operator": 5,                     "value": "2",                     "formulaid": "A"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084",                     "formulaid": "B"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10106",                     "formulaid": "C"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```  

en-us	#### Using a custom expression filter  Create a trigger action that will use a custom filter condition. The action must send a message for each trigger with severity higher or equal to "Warning" for hosts "10084" and "10106". The formula IDs "A", "B" and "C" have been chosen arbitrarily.  Request:  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 3,             "formula": "A and (B or C)",             "conditions": [                 {                     "conditiontype": 4,                     "operator": 5,                     "value": "2",                     "formulaid": "A"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084",                     "formulaid": "B"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10106",                     "formulaid": "C"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```
zh-cn	#### 使用自定义表达式过滤  创建使用自定义过滤条件的触发器动作。这个动作必须为主机 "10084" 和 "10106" 上每个严重程度等于或高于 "Warning" 的触发器发送一条消息。公式 ID 可以从 "A", "B" 和 "C" 中任选。  请求：  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 3,             "formula": "A and (B or C)",             "conditions": [                 {                     "conditiontype": 4,                     "operator": 5,                     "value": "2",                     "formulaid": "A"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084",                     "formulaid": "B"                 },                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10106",                     "formulaid": "C"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```

en-us	##### Using a custom tile service provider  The Geomap widget is capable to load raster tile images from a custom self-hosted or a third-party tile provider service. To use a custom third-party tile provider service or a self-hosted tile folder or server, select *Other* in the *Tile provider* field and specify the custom URL in the *Tile URL* field using proper placeholders.
zh-cn	##### 使用自定义瓦片服务提供者  Geomap 小部件能够从自定义的自托管或第三方切片提供商服务加载光栅切片图像。 要使用自定义第三方切片提供商服务或自托管切片文件夹或服务器，请在 *Tile provider* 字段中选择 *Other*，并在 *Tile URL* 字段中使用适当的占位符指定自定义 URL。

en-us	#### Using a filter  Create an LLD rule with a set of conditions to filter the results by. The conditions will be grouped together using the logical "and" operator.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex2",                     "operator": "9"                 },                 {                     "macro": "{#MACRO3}",                     "value": "",                     "operator": "12"                 },                 {                     "macro": "{#MACRO4}",                     "value": "",                     "operator": "13"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```
zh-cn	#### 使用过滤器  使用一组条件创建 LLD 规则以过滤结果。 条件将使用逻辑“和”运算符组合在一起。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex2",                     "operator": "9"                 },                 {                     "macro": "{#MACRO3}",                     "value": "",                     "operator": "12"                 },                 {                     "macro": "{#MACRO4}",                     "value": "",                     "operator": "13"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Using a filter  Create an LLD rule with a set of conditions to filter the results by. The conditions will be grouped together using the logical "and" operator.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": 0,         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex2",                     "operator": "9"                 },                 {                     "macro": "{#MACRO3}",                     "value": "",                     "operator": "12"                 },                 {                     "macro": "{#MACRO4}",                     "value": "",                     "operator": "13"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```
zh-cn	#### 使用过滤器  使用一组条件创建 LLD 规则以过滤结果。 条件将使用逻辑“和”运算符组合在一起。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Filtered LLD rule",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#MACRO1}",                     "value": "@regex1"                 },                 {                     "macro": "{#MACRO2}",                     "value": "@regex2",                     "operator": "9"                 },                 {                     "macro": "{#MACRO3}",                     "value": "",                     "operator": "12"                 },                 {                     "macro": "{#MACRO4}",                     "value": "",                     "operator": "13"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	##### - Using a static IP address  By default the appliance uses DHCP to obtain the IP address. To specify a static IP address:  -   Log in as root user; -   Open */etc/sysconfig/network-scripts/ifcfg-eth0* file; -   Replace *BOOTPROTO=dhcp* with *BOOTPROTO=none* -   Add the following lines:     -   *IPADDR=<IP address of the appliance>*     -   *PREFIX=<CIDR prefix>*     -   *GATEWAY=<gateway IP address>*     -   *DNS1=<DNS server IP address>* -   Run **systemctl restart network** command.  Consult the official Red Hat [documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s1-networkscripts-interfaces) if needed.
zh-cn	##### - 使用静态 IP 地址  默认情况下，Appliance 使用 DHCP 来获取 IP 地址。如果要指定一个静态 IP 地址：  -   使用 root 用户登录； -   打开 */etc/sysconfig/network-scripts/ifcfg-eth0* 文件； -   将 *BOOTPROTO=dhcp* 替换为 *BOOTPROTO=none* ； -   添加如下行：     -   *IPADDR=<Appliance 的 IP 地址>*     -   *PREFIX=<CIDR 前缀>*     -   *GATEWAY=<网关 IP 地址>*     -   *DNS1=<DNS 服务器 IP 地址>* -   执行 **systemctl restart network** 命令。  如果需要的话，查询 Red Hat 官方[文档](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s1-networkscripts-interfaces)

en-us	#### Using custom query fields and headers  Create LLD rule with custom query fields and headers.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "hostid": "10257",         "interfaceid": "5",         "type": "19",         "name": "API HTTP agent",         "key_": "api_discovery_rule",         "value_type": "3",         "delay": "5s",         "url": "http://127.0.0.1?discoverer.php",         "query_fields": [             {                 "mode": "json"             },             {                 "elements":"2"             }         ],         "headers": {             "X-Type": "api",             "Authorization": "Bearer mF_A.B5f-2.1JcM"         },         "allow_traps": "1",         "trapper_hosts": "127.0.0.1",         "id": 35,         "auth": "d678e0b85688ce578ff061bd29a20d3b",     } } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28336"         ]     },     "id": 35 } ```
zh-cn	#### 使用自定义查询字段和标题  使用自定义查询字段和标题创建 LLD 规则。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "hostid": "10257",         "interfaceid": "5",         "type": "19",         "name": "API HTTP agent",         "key_": "api_discovery_rule",         "value_type": "3",         "delay": "5s",         "url": "http://127.0.0.1?discoverer.php",         "query_fields": [             {                 "mode": "json"             },             {                 "elements":"2"             }         ],         "headers": {             "X-Type": "api",             "Authorization": "Bearer mF_A.B5f-2.1JcM"         },         "allow_traps": "1",         "trapper_hosts": "127.0.0.1",         "id": 35,         "auth": "d678e0b85688ce578ff061bd29a20d3b",     } } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28336"         ]     },     "id": 35 } ```

en-us	#### Using custom query fields and headers  Create LLD rule with custom query fields and headers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "hostid": "10257",         "interfaceid": "5",         "type": 19,         "name": "API HTTP agent",         "key_": "api_discovery_rule",         "value_type": 3,         "delay": "5s",         "url": "http://127.0.0.1?discoverer.php",         "query_fields": [             {                 "mode": "json"             },             {                 "elements": "2"             }         ],         "headers": {             "X-Type": "api",             "Authorization": "Bearer mF_A.B5f-2.1JcM"         },         "allow_traps": 1,         "trapper_hosts": "127.0.0.1"     },     "auth": "d678e0b85688ce578ff061bd29a20d3b",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28336"         ]     },     "id": 1 } ```
zh-cn	#### 使用自定义查询字段和标题  使用自定义查询字段和标题创建 LLD 规则。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "hostid": "10257",         "interfaceid": "5",         "type": "19",         "name": "API HTTP agent",         "key_": "api_discovery_rule",         "value_type": "3",         "delay": "5s",         "url": "http://127.0.0.1?discoverer.php",         "query_fields": [             {                 "mode": "json"             },             {                 "elements":"2"             }         ],         "headers": {             "X-Type": "api",             "Authorization": "Bearer mF_A.B5f-2.1JcM"         },         "allow_traps": "1",         "trapper_hosts": "127.0.0.1",         "id": 35,         "auth": "d678e0b85688ce578ff061bd29a20d3b",     } } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28336"         ]     },     "id": 35 } ```

en-us	#### Using db.odbc.discovery  As a practical example to illustrate how the SQL query is transformed into JSON, let us consider low-level discovery of Zabbix proxies by performing an ODBC query on Zabbix database. This is useful for automatic creation of "zabbix\[proxy,<name>,lastaccess\]" [internal items](/manual/config/items/itemtypes/internal) to monitor which proxies are alive.  Let us start with discovery rule configuration:  ![lld\_rule\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_odbc.png)  All mandatory input fields are marked with a red asterisk.  Here, the following direct query on Zabbix database is used to select all Zabbix proxies, together with the number of hosts they are monitoring. The number of hosts can be used, for instance, to filter out empty proxies:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  By the internal workings of "db.odbc.discovery\[,{$DSN}\]" item, the result of this query gets automatically transformed into the following JSON:  ``` {.java} [     {         "{#HOST}": "Japan 1",         "{#COUNT}": "5"     },     {         "{#HOST}": "Japan 2",         "{#COUNT}": "12"     },     {         "{#HOST}": "Latvia",         "{#COUNT}": "3"     } ] ```  It can be seen that column names become macro names and selected rows become the values of these macros.  ::: noteclassic  If it is not obvious how a column name would be transformed into a macro name, it is suggested to use column aliases like "COUNT(h2.host) AS count" in the example above.  In case a column name cannot be converted into a valid macro name, the discovery rule becomes not supported, with the error message detailing the offending column number. If additional help is desired, the obtained column names are provided under DebugLevel=4 in Zabbix server log file:      $ grep db.odbc.discovery /tmp/zabbix_server.log      ...      23876:20150114:153410.856 In db_odbc_discovery() query:'SELECT h1.host, COUNT(h2.host) FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;'      23876:20150114:153410.860 db_odbc_discovery() column[1]:'host'      23876:20150114:153410.860 db_odbc_discovery() column[2]:'COUNT(h2.host)'      23876:20150114:153410.860 End of db_odbc_discovery():NOTSUPPORTED      23876:20150114:153410.860 Item [Zabbix server:db.odbc.discovery[proxies,{$DSN}]] error: Cannot convert column #2 name to macro.   :::  Now that we understand how a SQL query is transformed into a JSON object, we can use {\#HOST} macro in item prototypes:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)  Once discovery is performed, an item will be created for each proxy:  ![discovered\_items\_odbc1.png](../../../../../assets/en/manual/discovery/low_level_discovery/discovered_items_odbc1.png)
zh-cn	#### 使用db.odbc.discovery  让我们看一个SQL查询转换为JSON数组的真实案例。思考一下如何在Zabbix数据库上使用ODBC查询对Zabbix proxy执行低级别自动发现。 此功能对于自动创建 "zabbix\[proxy,<name>,lastaccess\]" [内部监控项](/manual/config/items/itemtypes/internal) 并监控存活的proxy很有用。  下面开始配置自动发现规则：  ![lld\_rule\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_odbc.png)  所有强制输入区域均标记为红色星号。  此处Zabbix数据库上的查询用于查询所有Zabbix proxy，连同proxy所监控的主机数量. 比如，主机数量可用于过滤掉没有监控任何主机的proxy：      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  通过 "db.odbc.discovery\[,{$DSN}\]" 监控项的内部工作机制, 查询结果会自动转换为下面的JSON数组：  ``` {.java} [     {         "{#HOST}": "Japan 1",         "{#COUNT}": "5"     },     {         "{#HOST}": "Japan 2",         "{#COUNT}": "12"     },     {         "{#HOST}": "Latvia",         "{#COUNT}": "3"     } ] ```  可以看到字段名称变为宏的名称, 所选的记录变成这些宏的值。  ::: noteclassic  如果通过这种方式展示字段名称转换为宏名称不是很明显，那建议在上面的例子中使用字段别名，比如 "COUNT(h2.host) AS count"。  如果字段名称无法转换为有效的宏名称，则自动发现规则变为unsupport(不支持的)状态，其错误消息显示不合规字段的编号. 如果需要额外帮助, debug级别DebugLevel=4的Zabbix server日志文件中可找到获取的字段名称：      $ grep db.odbc.discovery /tmp/zabbix_server.log      ...      23876:20150114:153410.856 In db_odbc_discovery() query:'SELECT h1.host, COUNT(h2.host) FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;'      23876:20150114:153410.860 db_odbc_discovery() column[1]:'host'      23876:20150114:153410.860 db_odbc_discovery() column[2]:'COUNT(h2.host)'      23876:20150114:153410.860 End of db_odbc_discovery():NOTSUPPORTED      23876:20150114:153410.860 Item [Zabbix server:db.odbc.discovery[proxies,{$DSN}]] error: Cannot convert column #2 name to macro.   :::  现在理解了SQL查询如何转换成一个JSON对象后, 可以在监控项原型中使用 {\#HOST} 宏了：  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)  一旦自动发现开始执行, 会根据每个proxy创建一个对应的监控项：  ![discovered\_items\_odbc1.png](../../../../../assets/en/manual/discovery/low_level_discovery/discovered_items_odbc1.png)

en-us	#### Using db.odbc.get  Using `db.odbc.get[,{$DSN}]` and the following SQL example:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  this JSON will be returned:  ``` {.java} [     {         "host": "Japan 1",         "count": "5"     },     {         "host": "Japan 2",         "count": "12"     },     {         "host": "Latvia",         "count": "3"     } ] ```  As you can see, there are no low-level discovery macros there. However, custom low-level discovery macros can be created in the [LLD macros](/manual/discovery/low_level_discovery#custom_macros) tab of a discovery rule using JSONPath, for example:      {#HOST} → $.host  Now this {\#HOST} macro may be used in item prototypes:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)
zh-cn	#### 使用db.odbc.get  请看下面使用 `db.odbc.get[,{$DSN}]` 和相关SQL语句的例子:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  会返回这个JSON数组:  ``` {.java} [     {         "host": "Japan 1",         "count": "5"     },     {         "host": "Japan 2",         "count": "12"     },     {         "host": "Latvia",         "count": "3"     } ] ```  可以看到, 返回的JSON数组中不包含低级别自动发现的宏. 然而, 可以在自动发现规则的[LLD 宏](/manual/discovery/low_level_discovery#custom_macros) 选项卡中利用JSONPath来自定义宏, 比如:      {#HOST} → $.host  现在这个 {\#HOST} 宏可用在监控项原型中了:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)

en-us	#### Using DNS as default interface  HostInterface and HostInterfaceItem [configuration parameters](/manual/appendix/config/zabbix_agentd) allow to specify a custom value for the host interface during autoregistration.  More specifically, they are useful if the host should be autoregistered with a DNS name as the default agent interface rather than its IP address. In that case the DNS name should be specified or returned as the value of either HostInterface or HostInterfaceItem parameters. Note that if the value of one of the two parameters changes, the autoregistered host interface is updated. So it is possible to update the default interface to another DNS name or update it to an IP address. For the changes to take effect though, the agent has to be restarted.  ::: noteclassic If HostInterface or HostInterfaceItem parameters are not configured, the listen\_dns parameter is resolved from the IP address. If such resolving is configured incorrectly, it may break autoregistration because of invalid hostname. :::
zh-cn	#### 使用DNS作为默认接口  在自动注册过程中，主机接口(HostInterface)和主机接口监控项(HostInterfaceItem) [配置参数](/manual/appendix/config/zabbix_agentd)的值允许自定义。   具体来说，如果主机使用DNS名称而不是IP地址作为默认agent接口进行自动注册时，对参数的值进行自定义就发挥作用了。这种情况下，DNS名称应通过HostInterface或HostInterfaceItem参数进行设置。 注意，如果上述参数的值发生改变，自动注册的主机接口也会更新。所以可以通过更换DNS名称来更新默认接口，或给DNS名称改成IP地址来更新接口。 Zabbix agent需要重启来使变更生效。 ::: noteclassic 如果不配置HostInterface和HostInterfaceItem这两个参数，那么listen\_dns参数会从IP地址来解析。如果解析配置错误，可能会因为主机名称无效导致自动注册失败。 :::

en-us	#### Using filter  The filter can help narrow down the number of hosts and/or triggers displayed. For better search performance, data is searched with macros unresolved.  The filter is located below the *Availability report* bar. It can be opened and collapsed by clicking on the *Filter* tab on the left.
zh-cn	 #### 使用过滤器  过滤器可以帮助缩小显示的主机和/或触发器的数量。为了获得更好的搜索性能，使用未解析的宏搜索数据。  过滤器位于*可用性报表*栏下方。点击左侧的*过滤器*选项卡，可以将其打开和折叠。

en-us	##### Using filter  The item list may contain a lot of items. By using the filter, you can filter out some of them to quickly locate the items you'ŗe looking for. For better search performance, data is searched with macros unresolved.  The *Filter* icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria.  ![](../../../../../../assets/en/manual/web_interface/template_item_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Only host groups that contain at least one template can be selected.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Templates*|Filter by one or more templates.| |*Name*|Filter by item name.| |*Key*|Filter by item key.| |*Value mapping*|Filter by the value map used.<br>This parameter is not displayed if the *Templates* option is empty.| |*Type*|Filter by item type (Zabbix agent, SNMP agent, etc.).| |*Type of information*|Filter by type of information (Numeric unsigned, float, etc.).| |*History*|Filter by how long item history is kept.| |*Trends*|Filter by how long item trends are kept.| |*Update interval*|Filter by item update interval.| |*Tags*|Specify tags to limit the number of items displayed. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Status*|Filter by item status - *Enabled* or *Disabled*.| |*Triggers*|Filter items with (or without) triggers.| |*Inherited*|Filter items inherited (or not inherited) from linked templates.|  The **Subfilter** below the filter offers further filtering options (for the data already filtered). You can select groups of items with a common parameter value. Upon clicking on a group, it gets highlighted and only the items with this parameter value remain in the list.
zh-cn	##### 使用过滤器  监控项列表可能包含很多监控项。通过使用过滤器，您可以过滤掉其中的一些内容，从而快速找到您要寻找的项目。为了获得更好的搜索性能，在搜索数据时不会解析宏。  右上角有*Filter*图标。点击它将打开一个过滤器，您可以指定所需的过滤条件。 ![](../../../../../../assets/en/manual/web_interface/template_item_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|根据一个或多个主机组进行过滤。<br>主机组至少包含一个模板才能被选中。<br>选中父主机组，默认将选择所有嵌套的主机组。| |*模板*|通过一个或多个模板进行筛选。| |*名称*|通过监控项名称进行筛选。| |*键值*|按监控项的键值进行过滤| |*值映射*|根据使用的值映射过滤。<br>当“*模板*”选项为空时，此参数不显示| |*类型*|按监控项类型(Zabbix agent、SNMP agent等)进行过滤| |*信息类型*|根据信息类型(数字无符号，浮点数等)进行过滤| |*历史*|根据监控项历史记录保存的时间进行过滤| |*趋势*|根据监控项趋势保持的时间进行过滤。| |*更新间隔*|按监控项更新时间间隔进行过滤| |*标签*|通过指定标签来限制显示监控项的数量。可以包含或排除特定的标签和标签值。可以设置多个条件。标记名称匹配必须区分大小写。<br>对于每个条件都有几种操作符可用:<br>**存在** -包括指定的标签名称<br>**等于** -包括指定的标签名称和值(区分大小写)<br>**包含** -包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写）<br>**不存在** -排除指定的标签名称<br>**不等于** -排除指定的标签名称和值(区分大小写)<br>**不包含** -排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配不区分大小写）<br>条件的计算类型有两种:<br>**与/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或** -如果其中一个条件满足|就足够了| |*状态*|按监控项状态过滤- *启用*或*禁用*| |*触发器*|过滤有(或没有)触发器的监控项| |*继承*|过滤从链接模板中继承(或不继承)的监控项|  过滤器下面的**子过滤器**提供了进一步的过滤选项(对于已经过滤的数据)。可以选择几组具有公共参数值的监控项。在单击一个组时，它将突出显示，只有具有此参数值的监控项留在列表中。

en-us	##### Using filter  The page shows a list of all web scenarios of the selected host. To view web scenarios for another host or host group without returning to the *Monitoring → Hosts* page, select that host or group in the filter. You may also filter scenarios based on tags.
zh-cn	##### 使用过滤器   该页显示所选主机的所有 Web 监测的列表。若要查看其他主机或主机组的 Web 监测而不返回到 *监测  → 主机*  页面，请在筛选器中选择该主机或组。你还可以根据标签筛选方案。

en-us	##### Using filter  To view a specific graph, select it in the filter. The filter allows to specify the host, the graph name and the *Show* option (all/host graphs/simple graphs).  ![](../../../../../../assets/en/manual/web_interface/graph_filter.png){width="600"}  If no host is selected in the filter, no graphs are displayed.
zh-cn	##### 使用过滤器  为了查询特定的图像，通过使用过滤起来选中它。该过滤器允许一次指定一个主机（主机是必需的），然后通过从列表中选择或通过按图表名称模式的方法来快速搜索指定主机图表。  ![](../../../../../../assets/en/manual/web_interface/graph_filter.png){width="600"}  如果在过滤器里没有选择主机，则不会显示图形。

en-us	##### Using filter  You can filter graphs by host group and host. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  可以根据主机组和主机对图形进行过滤。为了获得更好的搜索性能，在搜索数据时不解析宏。

en-us	##### Using filter  You can filter graphs by host group and template. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  可以根据主机组和模板对图进行过滤。为了获得更好的搜索性能，在搜索数据时不解析宏。

en-us	##### Using filter  You can use the filter to display only the actions you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of actions. If you click on it, a filter becomes available where you can filter actions by name and status.  ![](../../../../../assets/en/manual/web_interface/action_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的动作。为了获得更好的搜索性能，在搜索数据时不解析宏。  *过滤器*链接可以在动作列表的上方找到。如果单击它，就会出现一个过滤器，您可以根据名称和状态过滤动作。  ![](../../../../../assets/en/manual/web_interface/action_filter.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the correlation rules you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of correlation rules. If you click on it, a filter becomes available where you can filter correlation rules by name and status.  ![](../../../../../assets/en/manual/web_interface/correlation_rules_filter1.png){width="600"}
zh-cn	#####  使用过滤器  您可以使用筛选器只显示您感兴趣的相关规则。为了获得更好的搜索性能，在搜索数据时不解析宏。  在相关规则列表的上方可以找到*过滤器*链接。如果单击它，就会出现一个过滤器，您可以根据名称和状态过滤相关规则。  ![](../../../../../assets/en/manual/web_interface/correlation_rules_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the discovery rules you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria such as template, discovery rule name, item key, item type, etc.  ![](../../../../../../assets/en/manual/web_interface/template_drule_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Only host groups that contain at least one template can be selected.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Templates*|Filter by one or more templates.| |*Name*|Filter by discovery rule name.| |*Key*|Filter by discovery item key.| |*Type*|Filter by discovery item type.| |*Update interval*|Filter by update interval.<br>Not available for Zabbix trapper and dependent items.| |*Keep lost resources period*|Filter by Keep lost resources period.| |*Status*|Filter by discovery rule status (All/Enabled/Disabled).|
zh-cn	##### 使用过滤器  您可以使用筛选器只显示感兴趣的自动发现规则。为了获得更好的搜索性能，在搜索数据时不解析宏。  右上角有*过滤器*图标。单击它将打开一个过滤器，您可以在其中指定所需的过滤条件，如模板、发现规则名称、项目键、项目类型等。  ![](../../../../../../assets/en/manual/web_interface/template_drule_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|过滤一个或多个主机组。<br>只能选择包含至少一个模板的主机组。<br>指定父主机组时，将默认选择所有嵌套的主机组| |*模板*|过滤一个或多个模板| |*名称*|根据自动发现规则名称进行过滤| |*键*|根据自动发现项键进行过滤| |*类型*|根据自动发现项类型进行过滤| |*更新间隔*|按更新间隔过滤。<br>对Zabbix捕获器和依赖项不可用| |*丢失资源保留周期*|按保留丢失资源周期过滤| |*状态*|根据发现规则状态进行过滤(全部/已启用/已禁用)|

en-us	##### Using filter  You can use the filter to display only the discovery rules you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of discovery rules. If you click on it, a filter becomes available where you can filter discovery rules by host group, host, name, item key, item type, and other parameters.  ![](../../../../../../assets/en/manual/web_interface/lld_rule_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Hosts*|Filter by one or more hosts.| |*Name*|Filter by discovery rule name.| |*Key*|Filter by discovery item key.| |*Type*|Filter by discovery item type.| |*Update interval*|Filter by update interval.<br>Not available for Zabbix trapper and dependent items.| |*Keep lost resources period*|Filter by Keep lost resources period.| |*SNMP OID*|Filter by SNMP OID.<br>Only available if *SNMP agent* is selected as type.| |*State*|Filter by discovery rule state (All/Normal/Not supported).| |*Status*|Filter by discovery rule status (All/Enabled/Disabled).|
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的发现规则。为了获得更好的搜索性能，在搜索数据时不解析宏。  在发现规则列表的上方可以找到*过滤器*链接。如果单击它，将出现一个过滤器，可以根据主机组、主机、名称、项目键、项目类型和其他参数过滤发现规则。  ![](../../../../../../assets/en/manual/web_interface/lld_rule_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|过滤一个或多个主机组。<br>指定父主机组时，将默认选择所有嵌套的主机组 |*主机*|过滤一个或多个主机 |*名称*|根据发现规则名称进行过滤 |*键*|根据发现项键进行过滤 |*类型*|根据发现项类型进行过滤 |*更新间隔*|按更新间隔过滤。<br>对Zabbix捕获器和依赖项不可用 |*丢失资源保留周期*|按丢失资源保留周期过滤| |*SNMP OID*| SNMP OID过滤。<br>仅当类型为“*SNMP agent*”时有效 |*支持状态*|根据发现规则状态进行过滤(支持全部/正常/不支持) |*状态*|根据发现规则状态进行过滤(全部/已启用/已禁用)|

en-us	##### Using filter  You can use the filter to display only the discovery rules you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of discovery rules. If you click on it, a filter becomes available where you can filter discovery rules by name and status.  ![](../../../../../assets/en/manual/web_interface/discovery_rules_filter1.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的自动发现规则。为了获得更好的搜索性能，在搜索数据时不解析宏。  在自动发现规则列表的上方可以找到*过滤器*链接。如果单击它，就会出现一个过滤器，您可以根据名称和状态过滤自动发现规则。  ![](../../../../../assets/en/manual/web_interface/discovery_rules_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the discovery rules you are interested in. For better search performance, data is searched with macros unresolved.  With nothing selected in the filter, all enabled discovery rules are displayed. To select a specific discovery rule for display, start typing its name in the filter. All matching enabled discovery rules will be listed for selection. More than one discovery rule can be selected.
zh-cn	##### 使用过滤器  可以使用筛选器显示感兴趣的发现规则。为了获得更好的搜索性能，使用未解析的宏搜索数据。如果在筛选器中未选择任何内容，则会显示所有已启用的 发现规则。  若要选择要显示的特定发现规则， 请开始在筛选器中键入其名称。将列出所有匹配的已启用发现规则以供选择。 可以选择多个发现规则。

en-us	##### Using filter  You can use the filter to display only the host groups you are interested in. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  你可以通过使用过滤器仅仅展示你感兴趣的主机组。为了更好的搜索性能，搜索数据的时候不会解析宏

en-us	#### Using filter  You can use the filter to display only the hosts you are interested in. For better search performance, data is searched with macros unresolved.  The filter is located above the table. It is possible to filter hosts by name, host group, IP or DNS, interface port, tags, problem severity, status (enabled/disabled/any); you can also select whether to display suppressed problems and hosts that are currently in maintenance.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/monitoring_hosts_filter.png){width="600"}  |Parameter|Description| |--|--------| |*Name*|Filter by visible host name.| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.| |*IP*|Filter by IP address.| |*DNS*|Filter by DNS name.| |*Port*|Filter by port number.| |*Severity*|Filter by problem severity. By default problems of all severities are displayed. Problems are displayed if not suppressed.| |*Status*|Filter by host status.| |*Tags*|Filter by host tag name and value. Hosts can be filtered by host-level tags as well as tags from all linked templates, including parent templates.<br>It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Show hosts in maintenance*|Mark the checkbox to display hosts that are in maintenance (displayed by default).| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.|  ##### Saving filter  Favorite filter settings can be saved as tabs and then quickly accessed by  clicking on the respective tab above the filter.  See more details about [saving filters](/manual/web_interface/frontend_sections/monitoring/problems#tabs_for_favorite_filters).
zh-cn	#### 使用过滤器  您可以使用过滤器仅显示您感兴趣的主机。为了获得更好的搜索性能，使用未解析的宏搜索数据。  过滤器位于表的上方。 可以按名称，主机组，IP 或 DNS，接口端口，标签，问题严重性，状态（启用/禁用/任何）过滤主机；您还可以选择是否显示被抑制的问题和当前正在维护的主机。  ![](../../../../../assets/en/manual/web_interface/monitoring_hosts_filter.png){width="600"}  |参数|描述| |---------|-----------| |*名称*|按可见主机名过滤。| |*主机组*|按一个或多个主机组进行过滤。<br>指定父主机组将隐式选择所有嵌套的主机组。| |*IP地址*|按照IP地址过滤。| |*DNS*|按 DNS 名称过滤。| |*端口*|按端口号过滤。| |*严重性*|按问题严重性过滤。 默认情况下，将显示所有严重性的问题。如果未禁止显示，则会显示问题。| |*状态*|按主机状态过滤。| |*标签*|按主机标记名称和值过滤。主机可以按主机级标签以及所有链接模板（包括父模板）中的标签进行过滤。<br>可以包含和排除特定标签和标签值。可以设置几个条件。标签名称匹配始终区分大小写。<br>每个条件都有多个运算符可用：<br>**存在** - 包括指定的标签名称<br>**等于** - 包括指定的标签名称和值（区分大小写）<br>**包含** - 包括指定的标签名称，其中标签值包含输入的字符串（子字符串匹配，不区分大小写）<br>**不存在** - 排除指定的标签名称<br>**不等于** - 排除指定的标签名称和值（区分大小写）<br>**不包含** - 排除标签值包含输入字符串的指定标签名称（子字符串匹配，不区分大小写）<br>有两种计算类型条件：<br>**与/或** -必须满足所有条件，具有相同标签名称的条件将根据或条件分组<br>**或** - 只需要满足一个条件| |*显示维护中主机*|标记该复选框以显示处于维护状态的主机（默认显示）。| |*显示处理的问题*|标记复选框以显示因主机维护而被抑制（未显示）的问题。|

en-us	#### Using filter  You can use the filter to display only the hosts you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of hosts. If you click on it, a filter becomes available where you can filter hosts by host group, linked templates, name, DNS, IP, port number, if they are monitored by server or by proxy, proxy name and tags.  ![](../../../../../assets/en/manual/web_interface/host_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Templates*|Filter by linked templates.| |*Name*|Filter by visible host name.| |*DNS*|Filter by DNS name.| |*IP*|Filter by IP address.| |*Port*|Filter by port number.| |*Monitored by*|Filter hosts that are monitored by server only, proxy only or both.| |*Proxy*|Filter hosts that are monitored by the proxy specified here.| |*Tags*|Filter by host tag name and value.<br>It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met|
zh-cn	#### 使用过滤器  您可以使用筛选器只显示您感兴趣的主机。为了获得更好的搜索性能，在搜索数据时不解析宏。  在主机列表的上方可以找到*过滤器*链接。如果单击它，可使用过滤器，根据主机组、链接模板、名称、DNS、IP、端口号(如果它们是由服务器或代理监控的)、代理名称和标签来过滤主机。  ![](../../../../../assets/en/manual/web_interface/host_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|过滤一个或多个主机组。<br>指定父主机组时，将默认选择所有嵌套的主机组 |*模板*|通过链接模板过滤| |*名称*|按可见主机名过滤| |*DNS*|按DNS名称过滤| |*IP*|按IP地址过滤| |*端口*|根据端口号进行过滤| |*被监控*|过滤只监控服务器、只监控代理或同时监控的主机| |*代理*|过滤此处指定的代理所监控的主机| |*标签*|根据主机标签名称和值过滤。<br>可以包含或排除特定的标签和标签值。可以设置多个条件。标记名称匹配必须区分大小写。<br>对于每个条件都有几种操作符可用:<br>**存在** -包括指定的标签名称<br>**等于** -包括指定的标签名称和值(区分大小写)<br>**包含** -包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写）<br>**不存在** -排除指定的标签名称<br>**不等于** -排除指定的标签名称和值(区分大小写)<br>**不包含** -排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配不区分大小写）<br>条件的计算类型有两种:<br>**与/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或** -如果其中一个条件满足|就足够了|

en-us	#### Using filter  You can use the filter to display only the items you are interested in. For better search performance, data is searched with macros unresolved.  The filter icon ![](../../../../../assets/en/manual/web_interface/icon_filter_collapsed.png){width="20"} is located above the table and the subfilter. Click on it  to expand the filter.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/latest_data_filter.png){width="600"}  The filter allows to narrow the list by host group, host, item name, tag and other settings.  Specifying a parent host group in the filter implicitly selects all nested host groups. See *Monitoring* -> *[Problems](/manual/web_interface/frontend_sections/monitoring/problems#using-filter)*  for details on filtering by tags.  *Show details* allows to extend the information displayed for the items. Such details as the refresh interval, history and trends settings, item type, and item errors (fine/unsupported) are displayed.  ##### Saving filter  Favorite filter settings can be saved as tabs and then quickly accessed by  clicking on the respective tab above the filter.  See more details about [saving filters](/manual/web_interface/frontend_sections/monitoring/problems#tabs_for_favorite_filters).  #### Using subfilter  The subfilter is useful for a quick one-click access to groups of related items.  The subfilter operates autonomously from the main filter - results are filtered  immediately, no need to click on *Apply* in the main filter.  Note that the subfilter only allows to further modify the filtering from the main filter.   Unlike the main filter, the subfilter is updated together with each table refresh request  to always get up-to-date information of available filtering options and their counter  numbers.  The subfilter shows **clickable links** allowing to filter items based on a common  entity - the host, tag name or tag value. As soon as the entity is clicked, items are  immediately filtered; the selected entity is highlighted with gray background.  To remove the filtering, click on the entity again. To add another  entity to the filtered results, click on another entity.  For each entity group (e.g. tags, hosts) up to 10 rows of entities are displayed. If there are  more entities, this list can be expanded to a maximum of 1000 entries  (the value of SUBFILTER_VALUES_PER_GROUP in [frontend definitions](/manual/web_interface/definitions))  by clicking on a three-dot icon displayed at the end. Once expanded to the maximum, the  list cannot be collapsed. (*Note* that a non-expandable maximum of 100 is the limit before Zabbix 6.0.5.)  In the list of *Tag values* up to 10 rows of tag names are displayed. If there are  more tag names with values, this list can be expanded to a maximum of 200 tag names  by clicking on a three-dot icon displayed at the bottom. Once expanded to the maximum, the  list cannot be collapsed. (*Note* that a non-expandable maximum of 20 rows is the limit before Zabbix 6.0.5.)  For each tag name up to 10 rows of values are displayed (expandable to 1000 entries  (the value of SUBFILTER_VALUES_PER_GROUP in [frontend definitions](/manual/web_interface/definitions))).  The host options in the subfilter are available only if no hosts or more than one  host is selected in the main filter.   By default, items with and without data are displayed in the item list. If only one host  is selected in the main filter, the subfilter offers the option to filter only items  with data, only without data, or both for this host.  A number next to each clickable entity indicates the number of items it has in the  results of the main filter. Entities without items are not displayed, unless they were  selected in the subfilter before.  Once one entity is selected, the numbers with other available entities are displayed  with a plus sign indicating how many items may be added to the current selection.  #### Graphs   **Ad-hoc graphs for comparing items**  You may use the checkbox in the first column to select several items and then compare their data in a simple or stacked [ad-hoc graph](/manual/config/visualization/graphs/adhoc). To do that, select items of interest, then click on the required graph button below the table.  **Links to value history/simple graph**  The last column in the latest value list offers:  -   a **History** link (for all textual items) - leading to listings     (*Values/500 latest values*) displaying the history of previous item     values.  -   a **Graph** link (for all numeric items) - leading to a [simple     graph](/manual/config/visualization/graphs/simple). However, once     the graph is displayed, a dropdown on the upper right offers a     possibility to switch to *Values/500 latest values* as well.  ![](../../../../../assets/en/manual/web_interface/latest_values.png){width="600"}  The values displayed in this list are "raw", that is, no postprocessing is applied.  ::: noteclassic The total amount of values displayed is defined by the value of *Limit for search and filter results* parameter, set in [Administration → General](/manual/web_interface/frontend_sections/administration/general). :::
zh-cn	#### 使用过滤器  您可以使用筛选器仅显示您感兴趣的项目。为了获得更好的搜索性能，搜索带有未解析的宏的数据。  过滤器图标 ![](../../../../../assets/en/manual/web_interface/icon_filter_collapsed.png){width="20"} 位于表和子过滤器的上方。单击它可以展开过滤器。  ![](../../../../../assets/en/manual/web_interface/latest_data_filter.png){width="600"}  过滤器允许按主机组、主机、项目名称、标记和其他设置缩小列表范围。在过滤器中指定父主机组将隐式选择所有嵌套主机组。有关按标记筛选的详细信息，请参阅*监测* -> *[问题](/manual/web_interface/frontend_sections/monitoring/problems#using-filter)* 。  *显示详细信息* 允许扩展为监控项显示的信息。将显示刷新间隔、历史记录和趋势设置、监控项类型和监控项错误（支持/不支持）等详细信息。  ##### 保存过滤器  最喜欢的过滤器设置可以保存为选项卡，然后通过单击过滤器上方的相应选项卡快速访问。  更多详情请参考 [保存过滤器](/manual/web_interface/frontend_sections/monitoring/problems#tabs_for_favorite_filters)。  #### 使用子过滤器  子筛选器可用于快速一键式访问相关监控项组。子过滤器从主过滤器自主运行 - 结果立即过滤，无需单击主过滤器中的“*应用*”。  请注意，子过滤器仅允许从主过滤器进一步修改筛选。  与主过滤器不同，子过滤器与每个表刷新请求一起更新，以始终获取可用过滤选项及其计数器编号的最新信息。  子过滤器显示 **可单击的链接**，允许根据公共实体（主机、标记名称或标记值）过滤监控项。单击实体后，将立即过滤监控项;所选图元将以灰色背景突出显示。若要删除过滤，请再次单击该实体。若要将其他实体添加到过滤结果中，请单击另一个实体。  对于每个实体组（例如标签、主机），最多显示 10 行实体。 如果有更多实体，可以通过单击末尾显示的三点图标将此列表扩展到最多 1000 个条目（[前端定义](/manual/web_interface/definitions) 中 SUBFILTER_VALUES_PER_GROUP 的值）。 一旦展开到最大值，列表就无法折叠。 （*注意*不可扩展的最大值 100 是 Zabbix 6.0.5 之前的限制。）  在*标签值*列表中最多显示 10 行标签名称。 如果有更多带值的标签名称，可以通过单击底部显示的三点图标将此列表扩展到最多 200 个标签名称。 一旦展开到最大值，列表就无法折叠。 （*注意* Zabbix 6.0.5 之前的限制是不可扩展的最大值 20 行。）  对于每个标记名称，最多显示 10 行值（可扩展到 1000 个条目（[前端定义](/manual/web_interface/definitions) 中 SUBFILTER_VALUES_PER_GROUP 的值））。  只有在主过滤器中未选择任何主机或选择多个主机时，子过滤器中的主机选项才可用。  默认情况下，监控项列表中会显示有数据和无数据的监控项。 如果在主过滤器中只选择了一个主机，则子过滤器会提供选项来过滤此主机的仅具有数据的监控项、仅不具有数据的监控项或两者。  每个可点击实体旁边的数字表示它在主过滤器结果中的监控项数。 没有监控项的实体不会显示，除非它们之前在子过滤器中被选中。  一旦选择了一个实体，就会显示其他可用实体的数量，并带有一个加号，表示可以将多少监控项添加到当前选择中。  #### 图表  **用于比较监控项的临时图形**  您可以使用第一列中的复选框选择多个监控项，然后在简单或堆叠的 [临时图形](/manual/config/visualization/graphs/adhoc)中比较它们的数据。为此，请选择感兴趣的监控项，然后单击表格下方的所需图表按钮。  **指向历史数据/简单图表**  最新值列表中的最后一列提供：  - ·  **历史记录** 链接（适用于所有文本项） - 指向显示以前监控项值历史记录的列表（值/500个 最新值）。  - ·  **图形** 链接 (适用于所有数字监控项) -指向一个 [简单图形](/manual/config/visualization/graphs/simple)。 然后， 一旦显示图形，右下角的的下拉列表也可以切换到 *（值/500个 最新值）*。  ![](../../../../../assets/en/manual/web_interface/latest_values.png){width="600"}  此列表中显示的值为 "原始"，即不做任何处理。  ::: noteclassic  显示的值的总量由 *搜索和过滤结果的限制* 参数的值定义，该参数在[“管理 → 一般”](/manual/web_interface/frontend_sections/administration/general)设置。  :::

en-us	##### Using filter  You can use the filter to display only the items you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria.  ![](../../../../../../assets/en/manual/web_interface/item_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host groups containing templates only cannot be selected.| |*Hosts*|Filter by one or more hosts.| |*Name*|Filter by item name.| |*Key*|Filter by item key.| |*Value mapping*|Filter by the value map used.<br>This parameter is not displayed if the *Hosts* option is empty.| |*Type*|Filter by item type (Zabbix agent, SNMP agent, etc.).| |*Type of information*|Filter by type of information (Numeric unsigned, float, etc.).| |*History*|Filter by how long item history is kept.| |*Trends*|Filter by how long item trends are kept.| |*Update interval*|Filter by item update interval.| |*Tags*|Specify tags to limit the number of items displayed. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*State*|Filter by item state - *Normal* or *Not supported*.| |*Status*|Filter by item status - *Enabled* or *Disabled*.| |*Triggers*|Filter items with (or without) triggers.| |*Inherited*|Filter items inherited (or not inherited) from a template.| |*Discovery*|Filter items discovered (or not discovered) by low-level discovery.|  The **Subfilter** below the filter offers further filtering options (for the data already filtered). You can select groups of items with a common parameter value. Upon clicking on a group, it gets highlighted and only the items with this parameter value remain in the list.
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的监控项。为了获得更好的搜索性能，在搜索数据时不解析宏。 右上角有*Filter*图标。点击它将打开一个过滤器，您可以指定所需的过滤条件。    ![](../../../../../../assets/en/manual/web_interface/item_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|过滤一个或多个主机组。<br>指定父主机组，将默认选择所有嵌套的主机组。<br>不能选择只包含模板的主机组| |*主机*|过滤一个或多个主机| |*名称*|根据项目名称进行过滤| |*键*|按项目键过滤| |*值映射*|根据使用的值映射过滤。<br>当“*Hosts*”选项为空时，此参数不显示| |*类型*|按项目类型(Zabbix agent、SNMP agent等)进行过滤| |*信息类型*|根据信息类型(数字无符号，浮点数等)进行过滤| |*历史*|根据条目历史记录保存的时间进行筛选| |*趋势*|根据项目趋势保持的时间。| |*更新时间间隔*|按项目更新时间间隔| |*标签*|指定标签限制显示条目的数量。可以包含或排除特定的标签和标签值。可以设置多个条件。标记名称匹配必须区分大小写。<br>对于每个条件都有几种操作符可用:<br>**存在** -包括指定的标签名称<br>**等于** -包括指定的标签名称和值(区分大小写)<br>**包含** -包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写）<br>**不存在** -排除指定的标签名称<br>**不等于** -排除指定的标签名称和值(区分大小写)<br>**不包含** -排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配不区分大小写）<br>条件的计算类型有两种:<br>**与/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或** -如果其中一个条件满足|就足够了| |*支持状态*|按项目状态过滤- *正常*或*不支持*| |*状态*|按项目状态过滤- *启用*或*禁用*| |*触发器*|过滤有(或没有)触发器的项目| |*继承*|从模板中继承(或不继承)的过滤项| |*发现*|过滤底层发现(或未发现)的项目|  过滤器下面的**子过滤器**提供了进一步的过滤选项(对于已经过滤的数据)。可以选择具有公共参数值的项目组。在单击一个组时，它将突出显示，只有具有此参数值的项目保留在列表中。

en-us	##### Using filter  You can use the filter to display only the items you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is located above the table to the right. You can use it to filter items by host group, host, a string in the item name and tags; you can also select to display items that have no data gathered.  Specifying a parent host group implicitly selects all nested host groups.  *Show details* allows extending displayable information on the items. Such details as refresh interval, history and trends settings, item type, and item errors (fine/unsupported) are displayed. A link to item configuration is also available.  ![](../../../../../assets/en/manual/web_interface/latest_data2.png){width="600"}  By default, items without data are shown but details are not displayed. For better page performance, the *Show items without data* option is checked and disabled if no host is selected in the filter.  **Ad-hoc graphs for comparing items**  You may use the checkbox in the first column to select several items and then compare their data in a simple or stacked [ad-hoc graph](/manual/config/visualization/graphs/adhoc). To do that, select items of interest, then click on the required graph button below the table.  **Links to value history/simple graph**  The last column in the latest value list offers:  -   a **History** link (for all textual items) - leading to listings     (*Values/500 latest values*) displaying the history of previous item     values.  ```{=html} <!-- --> ``` -   a **Graph** link (for all numeric items) - leading to a [simple     graph](/manual/config/visualization/graphs/simple). However, once     the graph is displayed, a dropdown on the upper right offers a     possibility to switch to *Values/500 latest values* as well.  ![](../../../../../assets/en/manual/web_interface/latest_values.png){width="600"}  The values displayed in this list are "raw", that is, no postprocessing is applied.  ::: noteclassic The total amount of values displayed is defined by the value of *Limit for search and filter results* parameter, set in [Administration → General](/manual/web_interface/frontend_sections/administration/general). :::  
zh-cn	##### Using filter  You can use the filter to display only the items you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is located above the table to the right. You can use it to filter items by host group, host, a string in the item name and tags; you can also select to display items that have no data gathered.  Specifying a parent host group implicitly selects all nested host groups.  *Show details* allows extending displayable information on the items. Such details as refresh interval, history and trends settings, item type, and item errors (fine/unsupported) are displayed. A link to item configuration is also available.  ![](../../../../../assets/en/manual/web_interface/latest_data2.png){width="600"}  By default, items without data are shown but details are not displayed. For better page performance, the *Show items without data* option is checked and disabled if no host is selected in the filter.  **Ad-hoc graphs for comparing items**  You may use the checkbox in the first column to select several items and then compare their data in a simple or stacked [ad-hoc graph](/manual/config/visualization/graphs/adhoc). To do that, select items of interest, then click on the required graph button below the table.  **Links to value history/simple graph**  The last column in the latest value list offers:  -   a **History** link (for all textual items) - leading to listings     (*Values/500 latest values*) displaying the history of previous item     values.  ```{=html} <!-- --> ``` -   a **Graph** link (for all numeric items) - leading to a [simple     graph](/manual/config/visualization/graphs/simple). However, once     the graph is displayed, a dropdown on the upper right offers a     possibility to switch to *Values/500 latest values* as well.  ![](../../../../../assets/en/manual/web_interface/latest_values.png){width="600"}  The values displayed in this list are "raw", that is, no postprocessing is applied.  ::: noteclassic The total amount of values displayed is defined by the value of *Limit for search and filter results* parameter, set in [Administration → General](/manual/web_interface/frontend_sections/administration/general). :::  

en-us	##### Using filter  You can use the filter to display only the maintenance periods you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of maintenance periods. If you click on it, a filter becomes available where you can filter maintenance periods by host group, name and state.  ![](../../../../../assets/en/manual/web_interface/maintenance_filter1.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的维护期。为了获得更好的搜索性能，在搜索数据时不解析宏。  在维护周期列表的上方可以找到*过滤器*链接。如果单击它，就会出现一个筛选器，可以根据主机组、名称和状态筛选维护周期。 ![](../../../../../assets/en/manual/web_interface/maintenance_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the maps you are interested in. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的地图。为了获得更好的搜索性能，使用未解析的宏搜索数据。

en-us	##### Using filter  You can use the filter to display only the media types you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of media types. If you click on it, a filter becomes available where you can filter media types by name and status.  ![](../../../../../assets/en/manual/web_interface/media_types_filter1.png){width="600"}
zh-cn	##### 使用过滤器  可以使用过滤器仅显示您感兴趣的媒介类型。为了获得更好的搜索性能，搜索数据时未解析宏。  *过滤器* 链接位于媒介类型列表上方。 如果单击它，则会出现一个过滤器，可以按名称和状态过滤媒介类型。  ![](../../../../../assets/en/manual/web_interface/media_types_filter1.png){width="600"}

en-us	#### Using filter  You can use the filter to display only the problems you are interested in. For better search performance, data is searched with macros unresolved.  The filter is located above the table. Favorite filter settings can be saved as tabs and then quickly accessed by clicking on the [tabs above the filter](/manual/web_interface/frontend_sections/monitoring/problems#tabs_for_favorite_filters).  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problem_filter.png){width="600"}  |Parameter|Description| |--|--------| |*Show*|Filter by problem status:<br>**Recent problems** - unresolved and recently resolved problems are displayed (default)<br>**Problems** - unresolved problems are displayed<br>**History** - history of all events is displayed| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Hosts*|Filter by one or more hosts.| |*Triggers*|Filter by one or more triggers.| |*Problem*|Filter by problem name.| |*Severity*|Filter by trigger (problem) severity.| |*Age less than*|Filter by how old the problem is.| |*Host inventory*|Filter by inventory type and value.| |*Tags*|Filter by [event tag](/manual/config/tagging) name and value. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met<br>When filtered, the tags specified here will be displayed first with the problem, unless overridden by the *Tag display priority* (see below) list.| |*Show tags*|Select the number of displayed tags:<br>**None** - no *Tags* column in *Monitoring → Problems*<br>**1** - *Tags* column contains one tag<br>**2** - *Tags* column contains two tags<br>**3** - *Tags* column contains three tags<br>To see all tags for the problem roll your mouse over the three dots icon.| |*Tag name*|Select tag name display mode:<br>**Full** - tag names and values are displayed in full<br>**Shortened** - tag names are shortened to 3 symbols; tag values are displayed in full<br>**None** - only tag values are displayed; no names| |*Tag display priority*|Enter tag display priority for a problem, as a comma-separated list of tags (for example: `Services,Applications,Application`). Tag names only should be used, no values. The tags of this list will always be displayed first, overriding the natural ordering by alphabet.| |*Show operational data*|Select the mode for displaying [operational data](#operational_data_of_problems):<br>**None** - no operational data is displayed<br>**Separately** - operational data is displayed in a separate column<br>**With problem name** - append operational data to the problem name, using parentheses for the operational data| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Compact view*|Mark the checkbox to enable compact view.| |*Show details*|Mark the checkbox to display underlying trigger expressions of the problems. Disabled if *Compact view* checkbox is marked.| |*Show unacknowledged only*|Mark the checkbox to display unacknowledged problems only.| |*Show timeline*|Mark the checkbox to display the visual timeline and grouping. Disabled if *Compact view* checkbox is marked.| |*Highlight whole row*|Mark the checkbox to highlight the full line for unresolved problems. The problem severity color is used for highlighting.<br>Enabled only if the *Compact view* checkbox is marked in the standard blue and dark themes. *Highlight whole row* is not available in the high-contrast themes.|
zh-cn	#### 使用过滤器  您可以使用过滤器来显示您感兴趣的问题。为了获得更好的搜索性能，使用未解析的宏搜索数据。  过滤器位于表格的上方。过滤器设置可以另存为选项卡，然后通过单击 [过滤器上方的选项卡](/manual/web_interface/frontend_sections/monitoring/problems#tabs_for_favorite_filters)快速访问。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problem_filter.png){width="600"}  |参数|描述| |---------|-----------| |*显示*|按问题状态筛选：<br>**显示最近问题** - 未解决和最近解决的问题 (默认)<br>**问题** - 显示未解决的问题<br>**历史** - 显示所有事件的历史记录| |*主机组*|筛选一个或多个主机组。<br>指定父主机组将选择所有包含的主机组。| |*主机*|筛选一个或多个主机。| |*触发器*|筛选一个或多个触发器。| |*问题*|按问题名称筛选。| |*严重性*|按触发器（问题）严重性进行筛选。| |*持续时间小于*|按问题的持续时间进行筛选。| |*主机资产记录*|按类型和值进行筛选。| |*标签*|按 [事件标签](/manual/config/tagging) 名称和值筛选。可以包含和排除特定标签和标签值。可以设置几个条件。标签名称匹配始终区分大小写。<br>每个条件都有多个运算符可用：<br>**存在** - 包括指定的标签名称<br>**等于** - 包括指定的标签名称和值（区分大小写）<br>**包含** -包含指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写)<br>**不存在** - 排除指定的标签名称<br>**不等于** - 排除指定的标签名称和值（区分大小写）<br>**不包含** - 不包含指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写)<br>条件有两种计算类型：<br>**与/或** - 必须满足所有条件，具有相同标签名称的条件将根据或条件分组<br>**或** - 只需要满足一个条件<br>过滤后，此处指定的标签将首先显示问题，除非被* *标签显示优先级* (见下文) 列表覆盖。| |*显示标签*|选择显示的标签数：<br>**没有** - 无*标签* 列在 *监控→ 问题*<br>**1** - *标签* 列包含1个标签<br>**2** - *标签* 列包含2个标签<br>**3** - *标签* 列包含3个标签<br>要查看问题的所有标签将鼠标悬停在3个点图标上。| |*标签名*|选择标签名称显示模式：<br>**完整** - 标签名称和值将完整显示<br>**缩短显示** - 标签名称被缩短为3个符号;标签值将全部显示<br>**没有** - 只显示标签值;没有名字| |*标签显示优先级*|输入问题的标签显示优先级，作为逗号分隔的标签列表 (例如: `服务、许可、申请`)。只应使用标签名称，不显示标签值。此列表的标签将始终首先显示，并覆盖按字母顺序的自然排序。| |*显示运行数据*|选择显示 [运行数据]模式(#operational_data_of_problems):<br>**无** - 不显示运行数据<br>**单独的** - 在单独的列里显示运行数据<br>**使用问题名称** - 将运行数据附加到问题名称，使用括号表示运行数据。| |*显示隐藏的问题*|标记复选框以显示由于主机维护而被隐藏（未显示）的问题。| |*紧凑视图*|标记复选框以启用精简视图。| |*显示详情*|标记该复选框以显示问题的基础触发器表达式。 如果标记了 *紧凑视图* 复选框，则禁用。| |*仅显示未确认*|标记该复选框以仅显示未确认的问题。| |*显示时间线*|标记该复选框以显示可视时间线和分组。如果标记了*紧凑视图* 复选框，则禁用。| |*整行高亮*|标记该复选框以突出显示未解决的问题的整行。问题严重性颜色用于突出显示。<br>仅当 *紧凑视图* 复选框在标准蓝色和深色主题中标记时才启用。 *整行高亮* 在高对比度主题中不可用。|

en-us	##### Using filter  You can use the filter to display only the proxies you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of proxies. If you click on it, a filter becomes available where you can filter proxies by name and mode.  ![](../../../../../assets/en/manual/web_interface/proxies_filter1.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的proxy。为了获得更好的搜索性能，使用未解析的宏搜索数据。  *Filter* 链接位于proxy列表上方。 如果单击它，将出现一个过滤器，您可以在其中按名称和模式过滤proxy。  ![](../../../../../assets/en/manual/web_interface/proxies_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the scenarios you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of web scenarios. If you click on it, a filter becomes available where you can filter scenarios by host group, host, status and tags.  ![](../../../../../../assets/en/manual/web_interface/web_scenario_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的场景。为了获得更好的搜索性能，在搜索数据时不解析宏。  *过滤器*链接在web场景列表的上方。单击后，会出现一个过滤器，可以根据主机组、模板、状态和标签对场景进行过滤。  ![](../../../../../../assets/en/manual/web_interface/web_scenario_filter.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the scenarios you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of web scenarios. If you click on it, a filter becomes available where you can filter scenarios by host group, template, status and tags.  ![](../../../../../../assets/en/manual/web_interface/template_web_scenario_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的场景。为了获得更好的搜索性能，在搜索数据时不解析宏。  *过滤器*链接在web场景列表的上方。单击后，会出现一个过滤器，可以根据主机组、模板、状态和标签对场景进行过滤。  ![](../../../../../../assets/en/manual/web_interface/template_web_scenario_filter.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the scripts you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of scripts. If you click on it, a filter becomes available where you can filter scripts by name and scope.  ![](../../../../../assets/en/manual/web_interface/script_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的脚本。为了获得更好的搜索性能，搜索数据时未解析宏。  *过滤器* 链接位于脚本列表上方。 如果您单击它，则会出现一个过滤器，您可以在其中按名称和范围过滤脚本。  ![](../../../../../assets/en/manual/web_interface/script_filter.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the services you are interested in.
zh-cn	 ##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的服务。

en-us	##### Using filter  You can use the filter to display only the templates you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available below *Create template* and *Import* buttons. If you click on it, a filter becomes available where you can filter templates by host group, linked templates, name and tags.  ![](../../../../../assets/en/manual/web_interface/template_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Linked templates*|Filter by directly linked templates.| |*Name*|Filter by template name.| |*Tags*|Filter by template tag name and value.<br>Filtering is possible only by template-level tags (not inherited ones). It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met|
zh-cn	##### 使用过滤器  你可以通过过滤器，只看你感兴趣的模板。为了更好的搜索性能，在搜索数据的时候不支持宏。  “过滤器”的连接就在*新建模板*和*导入*按钮的下面。点击之后，你可以使用主机组，连接模板，名称，标签来过滤主机组。 ![](../../../../../assets/en/manual/web_interface/template_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|通过一个或多个主机组过滤<br>指定一个父主机组，即可选中所有嵌套的主机组| |*关联模板*|过滤直接关联的模板| |*名称*|过滤模板名称| |*标签*|过滤模板标签名和标签值<br>只能通过模板标签进行过滤（集成的标签无效）。可以包含或者排除特定的标签名和标签值。可以设置几个条件。标记名称匹配必须区分大小写。<br>**存在**-包括指定的标签名<br>**等于**-包括指定的标签名称和标签值(区分大小写)<br>**包含**-包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，区分大小写）<br>**不存在**-排除指定的标签名称<br>**不等于**-排除指定的标签名称和值(区分大小写)<br>**不包含**-排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，区分大小写)<br>**与/或**-条件的计算类型有两种:<br>**和/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或**-如果其中一个条件满足就可以了|

en-us	##### Using filter  You can use the filter to display only the triggers you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria.  ![](../../../../../../assets/en/manual/web_interface/template_triggers_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Only host groups that contain at least one template can be selected.<br>Specifying a parent host group implicitly selects all nested host groups.| |*Templates*|Filter by one or more templates.<br>If host groups are already selected above, template selection is limited to those groups.| |*Name*|Filter by trigger name.| |*Severity*|Select to filter by one or several trigger severities.| |*Status*|Filter by trigger status.| |*Tags*|Filter by trigger tag name and value. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met<br>Macros and [macro functions](/manual/config/macros/macro_functions) are supported in tag name and tag value fields.| |*Inherited*|Filter triggers inherited (or not inherited) from linked templates.| |*With dependencies*|Filter triggers with (or without) dependencies.|
zh-cn	使用筛选器可以只显示您感兴趣的触发器。为了获得更好的搜索性能，在搜索数据时不解析宏。  右上角有*过滤器*图标。点击它将打开一个过滤器，您可以指定所需的过滤条件。  ![](../../../../../../assets/en/manual/web_interface/template_triggers_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|根据一个或多个主机组进行过滤。<br>主机组至少包含一个模板才能被选中。<br>选中父主机组，默认将选择所有嵌套的主机组。| |*模板*|通过一个或多个模板进行筛选。<br>如果已经选择了以上的主机组，则只能选择这些主机组的模板。| |*名称*|通过触发器名称进行筛选。| |*严重级别*|按一个或多个触发级别进行过滤| |*状态*|按触发器状态进行过滤| |*标签*|通过指定标签来限制显示监控项的数量。可以包含或排除特定的标签和标签值。可以设置多个条件。标记名称匹配必须区分大小写。<br>对于每个条件都有几种操作符可用:<br>**存在** -包括指定的标签名称<br>**等于** -包括指定的标签名称和值(区分大小写)<br>**包含** -包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写）<br>**不存在** -排除指定的标签名称<br>**不等于** -排除指定的标签名称和值(区分大小写)<br>**不包含** -排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配不区分大小写）<br>条件的计算类型有两种:<br>**与/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或** -如果其中一个条件满足|就足够了| |*继承*|过滤从链接模板中继承(或不继承)的监控项| |*依赖项*|过滤有(或没有)依赖项的触发器

en-us	#### Using filter  You can use the filter to display only the triggers you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* icon is available at the top right corner. Clicking on it will open a filter where you can specify the desired filtering criteria.  ![](../../../../../../assets/en/manual/web_interface/trigger_filter.png){width="600"}  |Parameter|Description| |---------|-----------| |*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host groups containing templates only cannot be selected.| |*Hosts*|Filter by one or more hosts.<br>If host groups are already selected above, host selection is limited to those groups.| |*Name*|Filter by trigger name.| |*Severity*|Select to filter by one or several trigger severities.| |*State*|Filter by trigger state.| |*Status*|Filter by trigger status.| |*Value*|Filter by trigger value.| |*Tags*|Filter by trigger tag name and value. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met<br>Macros and [macro functions](/manual/config/macros/macro_functions) are supported both in tag name and tag value fields.| |*Inherited*|Filter triggers inherited (or not inherited) from a template.| |*Discovered*|Filter triggers discovered (or not discovered) by low-level discovery.| |*With dependencies*|Filter triggers with (or without) dependencies.|
zh-cn	#### 使用过滤器  您可以使用筛选器只显示您感兴趣的触发器。为了获得更好的搜索性能，在搜索数据时不解析宏。  右上角有*国旅汽车*图标。点击它将打开一个过滤器，您可以指定所需的过滤条件。 ![](../../../../../../assets/en/manual/web_interface/trigger_filter.png){width="600"}  |参数|描述| |---------|-----------| |*主机组*|过滤一个或多个主机组。<br>指定父主机组时，将默认选择所有嵌套的主机组。<br>不能选择只包含模板的主机组| |*主机*|过滤一个或多个主机。<br>如果上面已经选择了主机组，则只能选择这些主机组 |*名称*|按触发器名称筛选| |*严重级别*|按一个或多个触发级别进行过滤| |*支持状态*|按触发支持状态进行过滤| |*状态*|按触发状态进行过滤| |*值*|按触发值过滤| |*标签*|按触发标记名称和值进行筛选。可以包含或排除特定的标记和标记值。可以设置几个条件。标记名称匹配总是区分大小写。<br>对于每个条件都有几种操作符可用:<br>**存在** -包括指定的标签名称<br>**等于** -包括指定的标签名称和值(区分大小写)<br>**包含** -包括指定的标签名称，其中标签值包含输入的字符串(子字符串匹配，不区分大小写）<br>**不存在** -排除指定的标签名称<br>**不等于** -排除指定的标签名称和值(区分大小写)<br>**不包含** -排除指定的标签名称，其中标签值包含输入的字符串(子字符串匹配不区分大小写）<br>条件的计算类型有两种:<br>**与/或** -如果有多个条件满足，则这些标签名相同的条件会用或拼接<br>**或** -如果其中一个条件满足|就足够了<br>宏和[宏函数](/manual/config/macros/macro_functions)在标签名和标签值字段都被支持| |*继承*|从模板中继承(或不继承)的过滤器 |*已发现*|过滤底层发现(或未发现)的触发器 |*依赖项*|过滤有(或没有)依赖项的触发器

en-us	##### Using filter  You can use the filter to display only the user groups you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of user groups. If you click on it, a filter becomes available where you can filter user groups by name and status.  ![](../../../../../assets/en/manual/web_interface/user_groups_filter1.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的用户组。为了获得更好的搜索性能，使用未解析的宏搜索数据。  *过滤器* 链接位于用户组列表上方。如果单击它，将出现一个过滤器，您可以在其中按名称和状态过滤用户组。  ![](../../../../../assets/en/manual/web_interface/user_groups_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the users you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of users. If you click on it, a filter becomes available where you can filter users by username, name, last name and user role.  ![](../../../../../assets/en/manual/web_interface/user_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的用户。为了获得更好的搜索性能，使用未解析的宏搜索数据。  *Filter* 链接位于用户列表上方。如果单击它，则会出现一个过滤器，您可以在其中按用户名、姓名、姓氏和用户角色过滤用户。  ![](../../../../../assets/en/manual/web_interface/user_filter.png){width="600"}

en-us	#### Using host metadata  When agent is sending an autoregistration request to the server it sends its hostname. In some cases (for example, Amazon cloud nodes) a hostname is not enough for Zabbix server to differentiate discovered hosts. Host metadata can be optionally used to send other information from an agent to the server.  Host metadata is configured in the agent [configuration file](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf. There are 2 ways of specifying host metadata in the configuration file:      HostMetadata     HostMetadataItem  See the description of the options in the link above.  ::: noteimportant An autoregistration attempt happens every time an active agent sends a request to refresh active checks to the server. The delay between requests is specified in the [RefreshActiveChecks](/manual/appendix/config/zabbix_agentd) parameter of the agent. The first request is sent immediately after the agent is restarted. :::
zh-cn	#### 使用主机元数据  agent会将主机名称和自动注册请求一同发送到Zabbix server上。某些情况下(比如亚马逊云主机)无法通过主机名称来区分发现的主机。 agent可以通过发送主机元数据这个可选配置来提供其它信息。  主机元数据在agent的 [配置文件](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf中定义。 有两种方式来设置主机元数据:      HostMetadata     HostMetadataItem  详情请参阅上述链接。  ::: noteimportant 每次active agent发送请求到Zabbix server刷新检查时，会尝试进行自动注册。 请求之间的延迟在agent的 [RefreshActiveChecks](/manual/appendix/config/zabbix_agentd) 参数 中定义。agent重启后会立刻发送第一个请求。 :::

en-us	#### Using jmx.discovery  This item returns a JSON object with low-level discovery macros describing MBean objects or attributes. For example, in the discovery of MBean attributes (reformatted for clarity):  ``` {.javascript} [     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionCount",         "{#JMXATTR}":"CollectionCount"     },     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionTime",         "{#JMXATTR}":"CollectionTime"     },     {         "{#JMXVALUE}":"true",         "{#JMXTYPE}":"java.lang.Boolean",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Valid",         "{#JMXATTR}":"Valid"     },     {         "{#JMXVALUE}":"PS Scavenge",         "{#JMXTYPE}":"java.lang.String",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Name",         "{#JMXATTR}":"Name"     },     {         "{#JMXVALUE}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXTYPE}":"javax.management.ObjectName",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,ObjectName",         "{#JMXATTR}":"ObjectName"     } ] ```  In the discovery of MBeans (reformatted for clarity):  ``` {.javascript} [     {         "{#JMXDOMAIN}":"java.lang",         "{#JMXTYPE}":"GarbageCollector",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXNAME}":"PS Scavenge"     } ]  ```
zh-cn	#### 使用jmx.discovery  此监控项返回一个JSON对象，其中包含低级别自动发现的宏，用于描述MBean对象或对象的属性，比如MBean属性的自动发现(为了清晰重新排版):  ``` {.javascript} [     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionCount",         "{#JMXATTR}":"CollectionCount"     },     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionTime",         "{#JMXATTR}":"CollectionTime"     },     {         "{#JMXVALUE}":"true",         "{#JMXTYPE}":"java.lang.Boolean",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Valid",         "{#JMXATTR}":"Valid"     },     {         "{#JMXVALUE}":"PS Scavenge",         "{#JMXTYPE}":"java.lang.String",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Name",         "{#JMXATTR}":"Name"     },     {         "{#JMXVALUE}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXTYPE}":"javax.management.ObjectName",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,ObjectName",         "{#JMXATTR}":"ObjectName"     } ] ```  又比如MBean的自动发现 (为了清晰重新排版):  ``` {.javascript} [     {         "{#JMXDOMAIN}":"java.lang",         "{#JMXTYPE}":"GarbageCollector",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXNAME}":"PS Scavenge"     } ]  ```

en-us	#### Using LLD macros in user macro contexts  LLD macros may be used inside user macro context, for example, [in trigger prototypes](/manual/config/macros/user_macros_context#use_cases).
zh-cn	 #### 在用户宏的上下文中使用LLD宏  LLD宏可用在用户宏的上下文中，比如 [在触发器原型中](/manual/config/macros/user_macros_context#use_cases)。

en-us	#### Using macro functions  Macro functions are supported with low-level discovery macros (except in low-level discovery rule filter), allowing to extract a certain part of the macro value using a regular expression.  For example, you may want to extract the customer name and interface number from the following LLD macro for the purposes of event tagging:      {#IFALIAS}=customername_1  To do so, the `regsub` macro function can be used with the macro in the event tag value field of a trigger prototype:  ![](../../../../assets/en/manual/config/macros/lld_macro_function.png)  Note, that commas are not allowed in unquoted item [key parameters](/manual/config/items/item/key#key_parameters), so the parameter containing a macro function has to be quoted. The backslash (`\`) character should be used to escape double quotes inside the parameter. Example:      net.if.in["{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}",bytes]  For more information on macro function syntax, see: [Macro functions](/manual/config/macros/macro_functions)  Macro functions are supported in low-level discovery macros since Zabbix 4.0.
zh-cn	#### 使用宏函数  低级发现宏支持宏功能（在低级发现规则过滤器），允许提取某个部分使用正则表达式的宏值。  例如，您可能想要提取客户名称和接口用于事件标记的以下 LLD 宏中的编号：  · {#IFALIAS}=customername_1  为此，可以将 `regsub` 宏函数与触发器原型的事件标签值字段：  ![](../../../../assets/en/manual/config/macros/lld_macro_function.png)  请注意，未引用的项目中不允许使用逗号 [key参数](/manual/config/items/item/key#key_parameters)，所以必须引用包含宏函数的参数。反斜杠(`\`) 字符应用于转义范围。例子：      net.if.in["{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}",bytes]  有关宏函数语法的更多信息，请参阅：[宏函数](/manual/config/macros/macro_functions)  自 Zabbix 以来，低级发现宏支持宏功能4.0。

en-us	##### Using macros in scripts  It is possible to use user macros in JavaScript code. If a script contains user macros, these macros are resolved by server/proxy before executing specific preprocessing steps. Note, that when testing preprocessing steps in the frontend, macro values will not be pulled and need to be entered manually.  ::: noteclassic  Context is ignored when a macro is replaced with its value. Macro value is inserted in the code as is, it is not possible to add additional escaping before placing the value in the JavaScript code. Please be advised, that this can cause JavaScript errors in some cases.  :::  In an example below, if received value exceeds a {$THRESHOLD} macro value, the threshold value (if present) will be returned instead:  ``` {.java} var threshold = '{$THRESHOLD}'; return (!isNaN(threshold) && value > threshold) ? threshold : value; ```
zh-cn	 ##### 在脚本中使用宏  可以在 JavaScript 代码中使用用户宏。 如果脚本包含用户宏，则这些宏在执行特定预处理步骤之前由服务器/代理解析。 注意，在前端测试预处理步骤时，宏值不会被拉取，需要手动输入。  ::: noteclassic 将宏替换为其值时将忽略上下文。宏值按原样插入代码中，在将值放入 JavaScript 代码之前无法添加额外的转义。请注意，这可能在某些情况下会导致 JavaScript 错误 。  :::  在下面的示例中，如果接收到的值超过 {$THRESHOLD} 宏值，则将返回阈值（如果存在）：  ``` {.java} var threshold = '{$THRESHOLD}'; return (!isNaN(threshold) && value > threshold) ? threshold : value; ```

en-us	#### Using mass update  To mass-update some hosts, do the following:  -   Mark the checkboxes before the hosts you want to update in the [host     list](/manual/web_interface/frontend_sections/configuration/hosts) -   Click on *Mass update* below the list -   Navigate to the tab with required attributes (*Host*, *IPMI*,     *Tags*, *Macros*, *Inventory*, *Encryption* or *Value mapping*) -   Mark the checkboxes of any attribute to update and enter a new value     for them  ![](../../../../assets/en/manual/config/hosts/host_mass.png)  The following options are available when selecting the respective button for **template** linkage update:  -   *Link* - specify which additional templates to link -   *Replace* - specify which templates to link while unlinking any     template that was linked to the hosts before -   *Unlink* - specify which templates to unlink  To specify the templates to link/unlink start typing the template name in the auto-complete field until a dropdown appears offering the matching templates. Just scroll down to select the required template.  The *Clear when unlinking* option will allow to not only unlink any previously linked templates, but also remove all elements inherited from them (items, triggers, etc.).  The following options are available when selecting the respective button for **host group** update:  -   *Add* - allows to specify additional host groups from the existing     ones or enter completely new host groups for the hosts -   *Replace* - will remove the host from any existing host groups and     replace them with the one(s) specified in this field (existing or     new host groups) -   *Remove* - will remove specific host groups from hosts  These fields are auto-complete - starting to type in them offers a dropdown of matching host groups. If the host group is new, it also appears in the dropdown and it is indicated by *(new)* after the string. Just scroll down to select.  ![](../../../../assets/en/manual/config/hosts/host_mass_c.png)  ![](../../../../assets/en/manual/config/hosts/host_mass_d.png)  User macros, {INVENTORY.\*} macros, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros are supported in tags. Note, that tags with the same name, but different values are not considered 'duplicates' and can be added to the same host.  ![](../../../../assets/en/manual/config/hosts/host_mass_e.png)  The following options are available when selecting the respective button for macros update:  -   *Add* - allows to specify additional user macros for the hosts. If     *Update existing* checkbox is checked, value, type and description     for the specified macro name will be updated. If unchecked, if a     macro with that name already exist on the host(s), it will not be     updated. -   *Update* - will replace values, types and descriptions of macros     specified in this list. If *Add missing* checkbox is checked, macro     that didn't previously exist on a host will be added as new macro.     If unchecked, only macros that already exist on a host will be     updated. -   *Remove* - will remove specified macros from hosts. If *Except     selected* box is checked, all macros except specified in the list     will be removed. If unchecked, only macros specified in the list     will be removed. -   *Remove all* - will remove all user macros from hosts. If *I confirm     to remove all macros* checkbox is not checked, a new popup window     will open asking to confirm removal of all macros.  ![](../../../../assets/en/manual/config/hosts/host_mass_f.png)  To be able to mass update inventory fields, the *Inventory mode* should be set to 'Manual' or 'Automatic'.  ![](../../../../assets/en/manual/config/hosts/host_mass_g.png)  ![](../../../../assets/en/manual/config/hosts/host_mass_h.png)  Buttons with the following options are available for value map update:  -   *Add* - add value maps to the hosts. If you mark *Update existing*,     all properties of the value map with this name will be updated.     Otherwise, if a value map with that name already exists, it will not     be updated. -   *Update* - update existing value maps. If you mark *Add missing*, a     value map that didn't previously exist on a host will be added as a     new value map. Otherwise only the value maps that already exist on a     host will be updated. -   *Rename* - give new name to an existing value map -   *Remove* - remove the specified value maps from the hosts. If you     mark *Except selected*, all value maps will be removed **except**     the ones that are specified. -   *Remove all* - remove all value maps from the hosts. If the *I     confirm to remove all value maps* checkbox is not marked, a new     popup window will open asking to confirm the removal.  When done with all required changes, click on *Update*. The attributes will be updated accordingly for all the selected hosts.
zh-cn	#### 使用批量更新  要批量更新某些主机，请按以下操作执行:  -   [主机列表](/zh/manual/web_interface/frontend_sections/configuration/hosts)中，在要更新的主机之前选中复选框 -   点击下方的 *Mass update（批量更新）* 按钮 -   跳转到属性所属的选项卡（*Host（主机）*、*IPMI*、*Tags（标签）*、*Macros（宏）*、*Inventory（资产记录）*、*Encryption（加密）* 或 *Value mapping（值映射）*） -   选中要更新的任何属性的复选框，并输入新值  ![](../../../../assets/en/manual/config/hosts/host_mass.png)  在选择 **template（模板）** 链接更新按钮时，如下选项可供选择：  -   *Link（链接）* - 指定需要链接的模板 -   *Replace（替换）* - 指定需要链接的模板，并取消任意之前已经链接到该主机且不需要的模板链接 -   *Unlink（取消链接）* - 指定需要取消链接的模板  要指定链接/取消链接的模板，请在搜索框（在此输入搜索）字段中输入模板名，直到出现一个提供匹配模板的下拉菜单。只需向下滚动即可选择所需的模板。  在选中 *Clear when unlinking（取消链接时清除）* 选项时，在取消与任何以前链接的模板的关联的同时还会删除所有继承自该模板的元素（监控项、触发器等）。  在选择**主机组**更新对应的按钮时，如下选项可供选择：  -   *Add（添加）*- 从现有主机组指定要添加的主机组，或为所选主机输入全新的主机组 -   *Replace（替换）*- 从任何现有主机组中删除所选主机，并替换为此字段中指定的主机组（现有的或新的主机组） -   *Remove（移除）*- 从所选主机中移除特定主机组  这些字段都是可以自动填充的 - 开始输入时会提供匹配的主机组的下拉列表。新的主机组也会出现在下拉列表中，并在字符串后用*(new)*表示。 只需向下滚动即可选择。  ![](../../../../assets/en/manual/config/hosts/host_mass_c.png)  ![](../../../../assets/en/manual/config/hosts/host_mass_d.png)  标签支持以下宏：用户宏、{INVENTORY.\*}宏、{HOST.HOST}、{HOST.NAME}、{HOST.CONN}、{HOST.DNS}、{HOST.IP}、{HOST.PORT}和{HOST.ID}宏。 注意：名称相同但值不同的标签是不被当成重复标签的，可以添加到同一个主机。  ![](../../../../assets/en/manual/config/hosts/host_mass_e.png)  在选择宏更新按钮时，如下选项可供选择：  -   *Add（添加）*- 允许为主机指定额外的用户宏。如果选中了 *Update existing（更新现有的）* 复选框，则将更新指定宏名称的值、类型和描述。不选的话，如果主机上已存在具有该名称的宏，则不会对其进行更新。 -   *Update（更新）*- 将替换此列表中指定的宏的值、类型和描述。如果选中 *Add missing（添加所缺的）* 复选框，则主机上以前不存在的宏将被添加为新宏。如果不选，则仅更新主机上已存在的宏。 -   *Remove（移除）*- 从主机中删除指定的宏。如果选中了 *Except selected（除选定对象之外）* 复选框，则除列表中指定的宏之外的所有宏将被删除。如果不选，则仅删除列表中指定的宏。 -   *Remove all（全部删除）*- 从主机上删除所有用户宏。如果没选中 *I confirm to remove all macros（我确认删除所有的宏）* 复选框，将弹出一个要求确认删除所有宏的窗口。  ![](../../../../assets/en/manual/config/hosts/host_mass_f.png)  为了能够批量更新资产记录，*Inventory mode（资产记录模式）* 应该设置为'手动'或'自动'。  ![](../../../../assets/en/manual/config/hosts/host_mass_g.png)  ![](../../../../assets/en/manual/config/hosts/host_mass_h.png)  在选择值映射按钮时，如下选项可供选择：  -   *Add（增加）*- 增加主机的值映射。如果选中了 *Update existing（更新已有的）*，该名称的值映射下的所有属性都会被更新。否则，若该名称的值映射已存在，则不会被更新。 -   *Update（更新）*- 更新已有的值映射。如果选中了 *Add missing（添加所缺的）*，则原来主机中不存在的值映射会被加入到主机中。否则仅已经存在的值映射会被更新。 -   *Rename（重命名）*- 重命名已存在的值映射。 -   *Remove（移除）*- 从主机中删除指定的值映射。如果选中了 *Except selected（除选定对象之外）*，则**除了**选定的值映射外都会被删除。 -   *Remove all（全部删除）*- 删除主机的全部值映射配置。如果没选中 *I confirm to remove all value maps（我确认删除所有的值映射）* 复选框，将弹出一个要求确认删除所有值映射的窗口。  完成所有必要的更改后，单击 *Update（更新）*。所有选定主机的属性将相应更新。

en-us	#### Using mass update  To mass-update some templates, do the following:  -   Mark the checkboxes before the templates you want to update in the     [template     list](/manual/web_interface/frontend_sections/configuration/templates) -   Click on *Mass update* below the list -   Navigate to the tab with required attributes (*Template*, *Tags*,     *Macros* or *Value mapping*) -   Mark the checkboxes of any attribute to update and enter a new value     for them  ![](../../../../assets/en/manual/config/templates/templ_mass.png)  The following options are available when selecting the respective button for **template** linkage update:  -   *Link* - specify which additional templates to link -   *Replace* - specify which templates to link while unlinking any     template that was linked to the templates before -   *Unlink* - specify which templates to unlink  To specify the templates to link/unlink start typing the template name in the auto-complete field until a dropdown appears offering the matching templates. Just scroll down to select the required template.  The *Clear when unlinking* option will allow to not only unlink any previously linked templates, but also remove all elements inherited from them (items, triggers, etc.).  The following options are available when selecting the respective button for **host group** update:  -   *Add* - allows to specify additional host groups from the existing     ones or enter completely new host groups for the templates -   *Replace* - will remove the template from any existing host groups     and replace them with the one(s) specified in this field (existing     or new host groups) -   *Remove* - will remove specific host groups from templates  These fields are auto-complete - starting to type in them offers a dropdown of matching host groups. If the host group is new, it also appears in the dropdown and it is indicated by *(new)* after the string. Just scroll down to select.  ![](../../../../assets/en/manual/config/templates/templ_mass_c.png)  User macros, {INVENTORY.\*} macros, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros are supported in tags. Note, that tags with the same name, but different values are not considered 'duplicates' and can be added to the same template.  ![](../../../../assets/en/manual/config/templates/templ_mass_d.png)  The following options are available when selecting the respective button for macros update:  -   *Add* - allows to specify additional user macros for the templates.     If *Update existing* checkbox is checked, value, type and     description for the specified macro name will be updated. If     unchecked, if a macro with that name already exist on the     template(s), it will not be updated. -   *Update* - will replace values, types and descriptions of macros     specified in this list. If *Add missing* checkbox is checked, macro     that didn't previously exist on a template will be added as new     macro. If unchecked, only macros that already exist on a template     will be updated. -   *Remove* - will remove specified macros from templates. If *Except     selected* box is checked, all macros except specified in the list     will be removed. If unchecked, only macros specified in the list     will be removed. -   *Remove all* - will remove all user macros from templates. If *I     confirm to remove all macros* checkbox is not checked, a new popup     window will open asking to confirm removal of all macros.  ![](../../../../assets/en/manual/config/templates/templ_mass_e.png)  Buttons with the following options are available for value map update:  -   *Add* - add value maps to the templates. If you mark *Update     existing*, all properties of the value map with this name will be     updated. Otherwise, if a value map with that name already exists, it     will not be updated. -   *Update* - update existing value maps. If you mark *Add missing*, a     value map that didn't previously exist on a template will be added     as a new value map. Otherwise only the value maps that already exist     on a template will be updated. -   *Rename* - give new name to an existing value map -   *Remove* - remove the specified value maps from the templates. If     you mark *Except selected*, all value maps will be removed     **except** the ones that are specified. -   *Remove all* - remove all value maps from the templates. If the *I     confirm to remove all value maps* checkbox is not marked, a new     popup window will open asking to confirm the removal.  When done with all required changes, click on *Update*. The attributes will be updated accordingly for all the selected templates.
zh-cn	#### 使用批量更新  批量更新一些模板，操作如下:  - 在 [模板列表](/manual/web_interface/frontend_sections/configuration/templates) 中，标记要更新模板前的复选框 - 点击下方 *更新* 按钮 - 页面跳转到带有所需属性 (*模板*, *标记*,     *宏* 或 *值映射*)的选项卡 - 标记要更新的任何属性的复选框，并为它们输入一个新值  ![](../../../../assets/en/manual/config/templates/templ_mass.png)  当选择更新 **模板链接** 复选框时，将有以下选项可以选择:  - *链接* - 指定要链接的附加模板。 - *替换* - 指定要链接的模板，同时取消链接之前链接到模板的任何模板。 - *取消链接* - 指定要取消链接的模板。  快捷搜索 -在搜索框输入模板名关键字后，将出现一个提供匹配模板的下拉菜单。只需向下滚动选择要_链接/取消链接_的模板即可。  *当无链接时清除*选项不仅允许取消任何先前关联的模板的关联，而且还可以删除从它们继承的所有元素(监控项、触发器等)。  当选择更新 **主机群组** 复选框时，将有以下选项可以选择:  - *添加* - 允许从现有的主机组中指定额外的主机组或为模板输入全新的主机组。 - *替换* - 将从任何现有主机组中删除模板，并将它们替换为在此字段中指定的模板(现有或新的主机组)。 - *移除* - 将从模板中删除特定的主机组。  这些字段是自动完成的 - 在搜索框输入关键字后，会自动提供一个匹配主机组的下拉列表。如果主机组是新创建的，它也会出现在下拉列表中，并且在字符串后面用*新(new)*表示。数量较多时，只需向下滚动选择即可。  ![](../../../../assets/en/manual/config/templates/templ_mass_c.png)  用户宏， {INVENTORY.\*} , {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} 和{HOST.ID}在标签中被支持。具有相同名称但不同值的标签不被认为是“重复”，可以添加到相同的模板中。  ![](../../../../assets/en/manual/config/templates/templ_mass_d.png)  当选择更新 **宏** 复选框时，将有以下选项可以选择:  - *添加*- 允许为模板指定额外的用户宏。如果选中*更新现有的*复选框，则只更新指定宏名称的值、类型和描述。反之，如果模板中已经存在同名的宏，则不会更新该宏。 - *更新* - 将替换列表中指定的宏的值、类型和描述。如果选中*添加缺失*复选框，则模板上先前不存在的宏将被添加为新的宏。反之，则只有模板中已经存在的宏才会被更新。 - *移除* - 将从模板中删除指定的宏。如果选中*除选中*复选框，则除列表中指定的宏之外的所有宏都将被删除。如果未选中，则只删除列表中指定的宏。 - *全部移除* - 将从模板中删除所有的宏。 如果未选中*我确认移除所有宏*复选框，将弹出需要选择该选项的警告提示框。   ![](../../../../assets/en/manual/config/templates/templ_mass_e.png)  当选择更新 **值映射** 复选框时，将有以下选项可以选择:  -  *添加* - 添加值映射到模板。如果选中*更新现有的*复选框，只更新指定值映射中的所有属性。反之，如果值映射已存在，将不会更新。 - *更新* - 更新已存在值映射。如果选中*添加缺失*复选框，则模板上先前不存在的值映射将被添加为新的值映射。反之，则只有模板中已经存在的值映射才会被更新。 - *重命名* - 为已存在的值映射更换新的名称。 - *移除* - 将从模板中删除指定的值映射。如果选中*除选中*复选框，则**除**列表中指定的值映射**之外**的所有宏都将被删除。 - *全部移除* - 将从模板中删除所有的值映射。 如果未选中*我确认移除所有值映射*复选框，将弹出需要选择该选项的警告提示框。  完成所有需要的更改后，点击*更新*按钮。所有选择模板的属性都会相应地更新。

en-us	#### Using mass update  To mass-update some triggers, do the following:  -   Mark the checkboxes of the triggers you want to update in the list -   Click on *Mass update* below the list -   Navigate to the tab with required attributes (*Trigger*, *Tags* or     *Dependencies*) -   Mark the checkboxes of any attribute to update  ![](../../../../assets/en/manual/config/triggers/trigger_mass.png)  ![](../../../../assets/en/manual/config/triggers/trigger_mass_b.png)  The following options are available when selecting the respective button for tag update:  -   *Add* - allows to add new tags for the triggers; -   *Replace* - will remove any existing tags from the trigger and     replace them with the one(s) specified below; -   *Remove* - will remove specified tags from triggers.  Note, that tags with the same name, but different values are not considered 'duplicates' and can be added to the same trigger.  ![](../../../../assets/en/manual/config/triggers/trigger_mass_c.png)  *Replace dependencies* - will remove any existing dependencies from the trigger and replace them with the one(s) specified.  Click on *Update* to apply the changes.
zh-cn	#### 使用批量更新  要批量更新某些触发器，请执行以下操作：  -  在列表中标记要更新的触发器的复选框 -  点击列表下方的*批量更新*  -   导航到具有所需属性 (*触发器*, *标签* or *依赖项*)的选项卡 -   标记要更新的任何属性的复选框  ![](../../../../assets/en/manual/config/triggers/trigger_mass.png)  ![](../../../../assets/en/manual/config/triggers/trigger_mass_b.png)  选择相应的标签更新按钮时，可以使用以下选项：  -   *添加* - 允许为触发器添加新标签; -   *替换* - 将从触发器中删除任何现有标签，并用下面指定的标签替换它们； -   *删除* - 将从触发器中删除指定的标签。  请注意，具有相同名称但不同值的标签不被视为 '重复' ，可以添加到同一个触发器中。  ![](../../../../assets/en/manual/config/triggers/trigger_mass_c.png)  *替换依赖项* - 将从触发器中删除任何现有依赖项并将它们替换为指定的依赖项。  单击 *更新*  来应用更改。

en-us	#### Using maxdelay parameter  The 'maxdelay' parameter in log items allows ignoring some older lines from log files in order to get the most recent lines analyzed within the 'maxdelay' seconds.  ::: notewarning Specifying 'maxdelay' > 0 may lead to **ignoring important log file records and missed alerts**. Use it carefully at your own risk only when necessary. :::  By default items for log monitoring follow all new lines appearing in the log files. However, there are applications which in some situations start writing an enormous number of messages in their log files. For example, if a database or a DNS server is unavailable, such applications flood log files with thousands of nearly identical error messages until normal operation is restored. By default, all those messages will be dutifully analyzed and matching lines sent to server as configured in `log` and `logrt` items.  Built-in protection against overload consists of a configurable 'maxlines' parameter (protects server from too many incoming matching log lines) and a 10\*'maxlines' limit (protects host CPU and I/O from overloading by agent in one check). Still, there are 2 problems with the built-in protection. First, a large number of potentially not-so-informative messages are reported to server and consume space in the database. Second, due to the limited number of lines analyzed per second the agent may lag behind the newest log records for hours. Quite likely, you might prefer to be sooner informed about the current situation in the log files instead of crawling through old records for hours.  The solution to both problems is using the 'maxdelay' parameter. If 'maxdelay' > 0 is specified, during each check the number of processed bytes, the number of remaining bytes and processing time is measured. From these numbers the agent calculates an estimated delay - how many seconds it would take to analyze all remaining records in a log file.  If the delay does not exceed 'maxdelay' then the agent proceeds with analyzing the log file as usual.  If the delay is greater than 'maxdelay' then the agent **ignores a chunk of a log file by "jumping" over it** to a new estimated position so that the remaining lines could be analyzed within 'maxdelay' seconds.  Note that agent does not even read ignored lines into buffer, but calculates an approximate position to jump to in a file.  The fact of skipping log file lines is logged in the agent log file like this:      14287:20160602:174344.206 item:"logrt["/home/zabbix32/test[0-9].log",ERROR,,1000,,,120.0]"     logfile:"/home/zabbix32/test1.log" skipping 679858 bytes     (from byte 75653115 to byte 76332973) to meet maxdelay  The "to byte" number is approximate because after the "jump" the agent adjusts the position in the file to the beginning of a log line which may be further in the file or earlier.  Depending on how the speed of growing compares with the speed of analyzing the log file you may see no "jumps", rare or often "jumps", large or small "jumps", or even a small "jump" in every check. Fluctuations in the system load and network latency also affect the calculation of delay and hence, "jumping" ahead to keep up with the "maxdelay" parameter.  Setting 'maxdelay' < 'update interval' is not recommended (it may result in frequent small "jumps").
zh-cn	#### 使用maxdelay参数  日志监控项中的“maxdelay”参数允许忽略日志文件中的一些较旧的行，以便在“maxdelay”秒内获取最近分析的行。  ::: notewarning 指定'maxdelay'>0可能导致**忽略重要的日志文件记录和错过的报警**，只有在必要时才使用否则后果自负。 :::  默认情况下，日志监控项将跟踪出现在日志文件中的所有新行。 但是，有些应用程序在某些情况下开始在其日志文件中写入大量的消息。例如，如果数据库或DNS服务器不可用，则此类应用程序会向日志文件中注入数千条几乎相同错误消息，直到恢复正常为止。默认情况下，所有这些消息将被完全分析，并将匹配的行发送到配置为`log` 和`logrt`监控项的服务器上。  内置的过载保护包括一个可配置的“maxlines”参数（保护服务器免受过多传入匹配日志行的影响）和 10\*“maxlines”限制（保护主机 CPU 和 I/O 免于agent在一次检查中过载） . 尽管如此，内置保护仍存在两个问题。 首先，大量可能不那么有用的消息被报告给服务器并占用数据库空间。 其次，由于每秒分析的行数有限，agent可能会落后于最新的日志记录数小时。 很可能，您可能更愿意尽快了解日志文件中的当前情况，而不是花几个小时在旧记录中爬行。  这两个问题的解决方案是使用“maxdelay”参数。 如果指定 'maxdelay' > 0，则在每次检查处理的字节数时，测量剩余字节数和处理时间。 agent根据这些数字计算估计的延迟——分析日志文件中所有剩余记录需要多少秒。  如果延迟不超过“maxdelay”，那么agent将像往常一样继续分析日志文件。  如果延迟大于“maxdelay”，那么agent将**通过“跳转”到一个新的估计位置来忽略日志文件的一个块**，以便在“maxdelay”秒内分析剩下的行。  请注意，agent甚至不会将忽略的行读入缓冲区，而是计算要在文件中跳转的大致位置。  跳过日志文件行的事实记录在代理日志文件中，如下所示：      14287:20160602:174344.206 item:"logrt["/home/zabbix32/test[0-9].log",ERROR,,1000,,,120.0]"     logfile:"/home/zabbix32/test1.log" skipping 679858 bytes     (from byte 75653115 to byte 76332973) to meet maxdelay  “to byte”数字是近似的，因为在“跳转”之后，agent将文件中的位置调整到日志行开头，日志行可能在文件中更远或更早。  根据增长速度与分析日志文件的速度的不同，你可能会看到没有"跳转"、少有或经常"跳转"、大或小的"跳转"，甚至每次检查中的"跳转"都很小。系统负载和网络延迟的波动也会影响延迟的计算，因此"跳转"可以跟上“maxdelay”参数。  不推荐设置 'maxdelay' <'update interval'（这可能会导致频繁的"jumps"）

en-us	#### Using subfilter  The subfilter is useful for a quick one-click access to related graphs.  The subfilter operates autonomously from the main filter - results are filtered  immediately, no need to click on *Apply* in the main filter.  Note that the subfilter only allows to further modify the filtering from the main filter.   Unlike the main filter, the subfilter is updated together with each table refresh request  to always get up-to-date information of available filtering options and their counter  numbers.  The subfilter shows **clickable links** allowing to filter graphs based on a common  entity - the tag name or tag value. As soon as the entity is clicked, graphs are  immediately filtered; the selected entity is highlighted with gray background.  To remove the filtering, click on the entity again. To add another  entity to the filtered results, click on another entity.  The number of entities displayed is limited to 100 horizontally. If there are more,  a three-dot icon is displayed at the end; it is not clickable. Vertical lists  (such as tags with their values) are limited to 20 entries. If there are more,  a three-dot icon is displayed; it is not clickable.  A number next to each clickable entity indicates the number of graphs it has in the  results of the main filter.  Once one entity is selected, the numbers with other available entities are displayed  with a plus sign indicating how many graphs may be added to the current selection.
zh-cn	#### 使用子筛选器  子筛选器可用于快速一键访问相关图形。子过滤器从主过滤器自主运行- 结果立即过滤， 无需单击主过滤器中的 *应用* 。  请注意，子筛选器仅允许从主筛选器进一步修改筛选。   与主筛选器不同，子筛选器与每个表 刷新请求一起更新，以始终获取可用筛选选项及其计数器 编号的最新信息。  子筛选器显示 **可单击的链接** 允许根据公共实体（标记名称或标记值）筛选图形。一旦单击实体，图形就会立即被过滤；所选图元将以灰色背景突出显示。若要删除筛选，请再次单击该实体。若要将其他实体添加到筛选结果中，请单击另一个实体。  水平方向显示的实体数限制为 100 个。如果还有更多，则在末尾显示一个三点图标；它是可点击的。垂直列表  （比如带值的标签）限制为 20 个。如果有更多，将显示一个三点图标：它是可点击的。  每个可单击实体旁边的数字表示它在主筛选器结果中的图形数。  选择一个图元后，将显示具有其他可用图元的数字，并带有加号，指示可以添加到当前选定内容中的图形数。

en-us	#### Using Zabbix frontend behind proxy  If Zabbix frontend runs behind proxy server, the cookie path in the proxy configuration file needs to be rewritten in order to match the reverse-proxied path. See examples below. If the cookie path is not rewritten, users may experience authorization issues, when trying to login to Zabbix frontend.
zh-cn	####  在代理后面使用 Zabbix 前端  如果 Zabbix 前端在代理服务器后面运行，则需要重写代理配置文件中的 cookie 路径以匹配反向代理路径。请参阅下面的示例。如果不重写 cookie 路径，用户在尝试登录 Zabbix 前端时可能会遇到授权问题。

en-us	#### UTF-8 encoding  UTF-8 is the only encoding supported by Zabbix. It is known to work without any security flaws. Users should be aware that there are known security issues if using some of the other encodings.
zh-cn	#### UTF-8 编码  UTF-8 是 Zabbix 唯一支持的编码类型。众所周知，应用该类型编码可使Zabbix正常运转且没有任何安全漏洞。请用户注意，如果使用其它一些编码类型，我们发现会出现许多安全问题。

en-us	##### utf8mb4 support for MySQL  utf8mb4 encoding with utf8mb4\_bin collation is now supported for Zabbix installations with the MySQL/MariaDB database.  Previously only utf8 encoding was supported, which with MySQL stands for utf8mb3 encoding and thus supports only a subset of proper UTF-8 characters. In the new version utf8mb4 support has been added with support for the [full](https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb4.html) UTF-8 character set. Old installations using utf8mb3 are kept intact and may continue using that encoding.
zh-cn	##### 对 MySQL 的 utf8mb4 支持  使用 MySQL/MariaDB 数据库的 Zabbix 安装现在支持使用 utf8mb4\_bin 排序规则的 utf8mb4 编码。  以前只支持 utf8 编码，MySQL 代表 utf8mb3 编码，因此只支持正确 UTF-8 字符的子集。在新版本中，增加了对 utf8mb4 的支持，并支持 [完整的](https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb4.html) UTF-8 字符集。使用 utf8mb3 的旧安装保持不变，并且可以继续使用该编码。

en-us	#### Value caching  Values required for trigger evaluation are cached by Zabbix server. Because of this trigger evaluation causes a higher database load for some time after the server restarts. The value cache is not cleared when item history values are removed (either manually or by housekeeper), so the server will use the cached values until they are older than the time periods defined in trigger functions or server is restarted.
zh-cn	####  缓存值  触发器评估所需的值由Zabbix server缓存。由于此触发器评估在服务器重新启动后一段时间导致较高的数据库负载。当监控项历史数据被移除（手动或housekeeper）时，缓存值不会被清除，因此服务器将使用缓存的值，直到它们比触发器函数中定义的时间段或服务器重启的时间长。

en-us	# valuemap.create
zh-cn	# 创建

en-us	# valuemap.delete
zh-cn	# 删除

en-us	# valuemap.get
zh-cn	# 获取

en-us	# > Value map object  The following objects are directly related to the `valuemap` API.
zh-cn	# > 值映射对象  以下对象都是与valuemap直接相关的API。

en-us	### Value mappings  The value mappings object defines value mappings of the value map. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |type|integer|Mapping match type. For type equal 0,1,2,3,4 `value` field cannot be empty, for type 5 `value` field should be empty.<br><br>Possible values:<br>0 - (default) exact match ;<br>1 - mapping will be applied if value is greater or equal^1^;<br>2 - mapping will be applied if value is less or equal^1^;<br>3 - mapping will be applied if value is in range (ranges are inclusive), allow to define multiple ranges separated by comma character^1^;<br>4 - mapping will be applied if value match regular expression^2^;<br>5 - default value, mapping will be applied if no other match were found.| |**value**<br>(required)|string|Original value.<br><br>Is not required for mapping of type "default".| |**newvalue**<br>(required)|string|Value to which the original value is mapped to.|  ^1^ supported only for items having value type "numeric unsigned", "numeric float".\ ^2^ supported only for items having value type "character".\
zh-cn	 ### 值映射关系  值映射关系对象定义了值映射的值映射关系。 它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |type|integer|映射匹配类型。等于 0,1,2,3,4 类型的 `value` 字段不能为空，类型 5 的`value` 字段必须为空。<br><br>可用值：<br>0 - (默认) 精确匹配 ;<br>1 - 如果值大于或者等于，映射将会被应用^1^；<br>2 - 如果值小于或者等于，映射将会被应用^1^；<br>3 - 如果值在一个范围（包含范围边界），允许定义用逗号符号分隔的多个范围，映射将会被应用^1^；<br>4 - 如果值和正真表达式匹配，映射将会被应用^2^；<br>5 - 默认值，如果没有找到其他的匹配，映射将会被应用。| |**value**<br>(必填)|string|原始值。<br><br>“默认”类型的映射不是必填的。| |**newvalue**<br>(必填)|string|原始值的映射值。|  ^1^ 仅支持具有“无符号数”，“浮点数”值类型的监控项。\ ^2^ 仅支持具有“字符”值类型的监控项。\

en-us	### Value mappings  The value mappings object defines value mappings of the value map. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |type|integer|Mapping match type. For type equal 0,1,2,3,4 `value` field cannot be empty, for type 5 `value` field should be empty.<br><br>Possible values:<br>0 - (default) exact match ;<br>1 - mapping will be applied if value is greater or equal^1^;<br>2 - mapping will be applied if value is less or equal^1^;<br>3 - mapping will be applied if value is in range (ranges are inclusive), allow to define multiple ranges separated by comma character^1^;<br>4 - mapping will be applied if value match regular expression^2^;<br>5 - default value, mapping will be applied if no other match were found.| |**value**<br>(required)|string|Original value.<br><br>Is not required for mapping of type "default".| |**newvalue**<br>(required)|string|Value to which the original value is mapped to.|  ^1^ supported only for items having value type "numeric unsigned", "numeric float".\ ^2^ supported only for items having value type "character".\
zh-cn	 ### 值映射关系  值映射关系对象定义了值映射的值映射关系。 它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |type|integer|映射匹配类型。等于 0,1,2,3,4 类型的 `value` 字段不能为空，类型 5 的`value` 字段必须为空。<br><br>可用值：<br>0 - (默认) 精确匹配 ;<br>1 - 如果值大于或者等于，映射将会被应用^1^；<br>2 - 如果值小于或者等于，映射将会被应用^1^；<br>3 - 如果值在一个范围（包含范围边界），允许定义用逗号符号分隔的多个范围，映射将会被应用^1^；<br>4 - 如果值和正真表达式匹配，映射将会被应用^2^；<br>5 - 默认值，如果没有找到其他的匹配，映射将会被应用。| |**value**<br>(必填)|string|原始值。<br><br>“默认”类型的映射不是必填的。| |**newvalue**<br>(必填)|string|原始值的映射值。|  ^1^ 仅支持具有“无符号数”，“浮点数”值类型的监控项。\ ^2^ 仅支持具有“字符”值类型的监控项。\

en-us	##### Value mapping  The **Value mapping** tab allows to configure human-friendly representation of item data in [value mappings](/manual/config/items/mapping).
zh-cn	##### 值映射   **Value mapping（值映射）** 选项卡允许在 [value mappings（值映射）](/manual/config/items/mapping) 中配置监控项数据的人性化展示。

en-us	### Value map  The value map object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |valuemapid|string|*(readonly)* ID of the value map.| |**hostid**<br>(required)|id|Value map host ID.| |**name**<br>(required)|string|Name of the value map.| |**mappings**<br>(required)|array|Value mappings for current value map. The mapping object is [described in detail below](object#value_mappings).| |uuid|string|Universal unique identifier, used for linking imported value maps to already existing ones. Used only for value maps on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 值映射  值映射对象具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |valuemapid|string|*(只读)* 值映射的ID。| |**hostid**<br>(必填)|id|值映射的主机ID。| |**name**<br>(必填)|string|值映射的名称。| |**mappings**<br>(必填)|array|当前值映射的值映射关系。映射对象 [described in detail below](object#值映射关系)。| |uuid|string|通用唯一标识，用于将引入的值映射关联已经存在的对象。仅用于模板上的值映射。如果没有提供，则自动生成。<br><br>用于更新操作，这个字段是*只读*。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Value map  This class is designed to work with value maps.  Object references:\  -   [Value map](/manual/api/reference/valuemap/object#value_map)  Available methods:\  -   [valuemap.create](/manual/api/reference/valuemap/create) - creating     new value maps -   [valuemap.delete](/manual/api/reference/valuemap/delete) - deleting     value maps -   [valuemap.get](/manual/api/reference/valuemap/get) - retrieving     value maps -   [valuemap.update](/manual/api/reference/valuemap/update) - updating     value maps
zh-cn	# 值映射  此类用于值映射。  对象引用：  -   [Value map](/manual/api/reference/valuemap/object#值映射)  可用方法：  -   [valuemap.create](/manual/api/reference/valuemap/create) - 创建新的值映射 -   [valuemap.delete](/manual/api/reference/valuemap/delete) - 删除值映射 -   [valuemap.get](/manual/api/reference/valuemap/get) - 获取值映射 -   [valuemap.update](/manual/api/reference/valuemap/update) - 更新值映射

en-us	# valuemap.update
zh-cn	# 更新

en-us	##### Value processing pipeline  Item value processing is executed in multiple steps (or phases) by multiple processes. This can cause:  -   Dependent item can receive values, while THE master value cannot.     This can be achieved by using the following use case:     -   Master item has value type `UINT`, (trapper item can be used),         dependent item has value type `TEXT`.     -   No preprocessing steps are required for both master and         dependent items.     -   Textual value (like, "abc") should be passed to master item.     -   As there are no preprocessing steps to execute, preprocessing         manager checks if master item is not in NOT SUPPORTED state and         if value is set (both are true) and enqueues dependent item with         the same value as master item (as there are no preprocessing         steps).     -   When both master and dependent items reach history         synchronization phase, master item becomes NOT SUPPORTED,         because of the value conversion error (textual data cannot be         converted to unsigned integer).  As a result, dependent item receives a value, while master item changes its state to NOT SUPPORTED.  -   Dependent item receives value that is not present in master item     history. The use case is very similar to the previous one, except     for the master item type. For example, if `CHAR` type is used for     master item, then master item value will be truncated at the history     synchronization phase, while dependent items will receive their     value from the initial (not truncated) value of master item.
zh-cn	#####  监控项值处理流水线  监控项值处理分多个步骤（或阶段）在多个进程中执行。 这可能导致：  -    依赖项可以接收值，而主要监控项不能。 这可以通过使用以下用例来实现：      - 主要监控项具有值类型`UINT`，（可以使用陷阱监控项），依赖项具有值类型`TEXT`。      - 主要监控项和依赖项都不需要预处理步骤。      - 文本值（如“abc”）应传递给主要监控项。      -  由于没有要执行的预处理步骤，预处理管理器检查主项是否处于不支持状态以及是否设置了值（两者都为真）并将具有与主要监控项相同的值的依赖项排入队列（因为没有预处理步骤 ）。      -  当主要监控项和依赖项都达到历史同步阶段时，主要监控项变为不支持，因为值转换错误（文本数据无法转换为无符号整数）。  因此，依赖项收到一个值，而主要监控项状态将变为不支持。  - 依赖项接收主要监控项历史记录中不存在的值。 用例与前一个非常相似，除了主要监控项类型。 例如，如果主要监控项使用 `CHAR` 类型，则主要监控项值将在历史同步阶段被截断，而依赖项将从主要监控项的初始（未截断）值接收它们的值。

en-us	#### Verification  It can be verified that a problem has been closed manually:  -   in event details, available through *Monitoring* → *Problems*; -   by using the {EVENT.UPDATE.HISTORY} macro in notification messages     that will provide this information.
zh-cn	#### 验证  可以通过以下方式确认一个问题已经被手动关闭了：  -   在事件详细信息里，通过*监控* → *问题*可以查看； -   在通知消息里使用宏{EVENT.UPDATE.HISTORY}会提供该信息。

en-us	##### Verify agent parameters  Make sure that in the [agent configuration file](/manual/appendix/config/zabbix_agentd):  -   'Hostname' parameter matches the host name in the frontend -   Servers in the 'ServerActive' parameter are specified for the     processing of active checks
zh-cn	##### 验证代理参数  确保在 [代理配置文件](/manual/appendix/config/zabbix_agentd) 中已设置：  -   'Hostname'参数与前端的主机名一致 -   'ServerActive'参数中的服务器被指定用于处理主动检查

en-us	### Verify CA mode
zh-cn	### 验证 CA 模式

en-us	### Verify CA mode  Copy required MySQL CA to the Zabbix frontend server, assign proper permissions to allow the webserver to read this file.  ::: noteclassic  *Verify CA* mode doesn't work on SLES 12 and RHEL 7 due to older MySQL libraries.  :::
zh-cn	### 验证 CA 模式  将所需的MySQL CA复制到Zabbix前端服务器，分配适当的权限以允许Web服务器读取此文件。  ::: noteclassic  *Verify CA* 模式在 SLES 12 and RHEL 7 不会生效，因为所在系统的 MySQL 库过老.  :::

en-us	### Verify full mode
zh-cn	### 完整验证模式

en-us	### Verify Full mode
zh-cn	### 验证完整模式

en-us	#### Versions  Each repository of Zabbix components contains the following tags:  -   `latest` - latest stable version of a Zabbix component based on     Alpine Linux image -   `alpine-latest` - latest stable version of a Zabbix component based     on Alpine Linux image -   `ubuntu-latest` - latest stable version of a Zabbix component based     on Ubuntu image -   `alpine-5.4-latest` - latest minor version of a Zabbix 5.4 component     based on Alpine Linux image -   `ubuntu-5.4-latest` - latest minor version of a Zabbix 5.4 component     based on Ubuntu image -   `alpine-5.4.*` - different minor versions of a Zabbix 5.4 component     based on Alpine Linux image, where `*` is the minor version of     Zabbix component -   `ubuntu-5.4.*` - different minor versions of a Zabbix 5.4 component     based on Ubuntu image, where `*` is the minor version of Zabbix     component
zh-cn	#### 版本  Zabbix 组件的每个镜像仓库都包含了下列标签：  -   `latest` - 基于 Alpine Linux 镜像的最新稳定版的 Zabbix 组件 -   `alpine-latest` - 基于 Alpine Linux 镜像的最新稳定版的 Zabbix 组件 -   `ubuntu-latest` - 基于 Ubuntu 镜像的最新稳定版的 Zabbix 组件 -   `alpine-5.4-latest` - 基于 Alpine Linux 镜像的最新次要版本的 Zabbix 5.4 组件 -   `ubuntu-5.4-latest` - 基于 Unbuntu 镜像的最新次要版本的 Zabbix 5.4 组件 -   `alpine-5.4.*` - 基于 Alpine Linux 镜像的不同次要版本的 Zabbix 5.4 组件，其中 * 代表 Zabbix 组件的次要版本 -   `ubuntu-5.4.*` - 基于 Ubuntu 镜像的不同次要版本的 Zabbix 5.4 组件，其中 * 代表 Zabbix 组件的次要版本

en-us	#### Viewing and editing a dashboard  To view a single dashboard, click on its name in the list of dashboards.  When **viewing** a dashboard, the following options are available:  |   |   |   | |---|---|---| |![](../../../../../assets/en/manual/web_interface/dashboard_edit_button.png){width="107"}|<|Switch to the dashboard **editing** mode.<br>The editing mode is also opened when a new dashboard is being created and when you click on the ![](../../../../../assets/en/manual/web_interface/widget_edit.png) edit button of a widget.| |![](../../../../../assets/en/manual/web_interface/dashboard_action_menu2.png)|<|Open the action menu (see action descriptions below).| |<|![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_view_actions.png){width="208"}|*Sharing* - edit sharing preferences for the dashboard. Dashboards can be made public or private. Public dashboards are visible to all users. Private dashboards are visible only to their owner.<br>Private dashboards can be shared by the owner with other users and user groups. For details on configuring sharing, see the map [configuration](/manual/config/visualization/maps/map#sharing) section.<br>*Create new* - [create](#creating_a_dashboard) a new dashboard.<br>*Clone* - create a new dashboard by copying properties of the existing one. First you are prompted to enter dashboard parameters. Then, the new dashboard opens in editing mode with all the widgets of the original dashboard.<br>*Delete* - delete the dashboard.<br>*Create new report* - open a pop-up window with report [configuration form](/manual/config/reports). Disabled if the user does not have permission to manage scheduled reports.<br>*View related reports* - open a pop-up window with a list of existing reports based on the current dashboard. Disabled if there are no related reports or the user does not have permission to view scheduled reports.| |![](../../../../../assets/en/manual/web_interface/button_kiosk.png)|<|Display only page content ([kiosk mode](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)).<br>Kiosk mode can also be accessed with the following URL parameters: `/zabbix.php?action=dashboard.view&kiosk=1`.<br>To exit to normal mode: `/zabbix.php?action=dashboard.view&kiosk=0`|  When **editing** a dashboard, the following options are available:  |   |   |   | |---|---|---| |![](../../../../../assets/en/manual/web_interface/dashboard_properties.png)|<|Edit general dashboard [parameters](#creating_a_dashboard).| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_add_button.png)|<|Add a new widget.<br>Clicking on the arrow button will open the action menu (see action descriptions below).| |<|![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_edit_actions.png)|*Add widget* - add a new widget<br>*Add page* - add a new page<br>*Paste widget* - paste a copied widget. This option is grayed out if no widget has been copied. Only one entity (widget or page) can be copied at one time.<br>*Paste page* - paste a copied page. This option is grayed out if no page has been copied.| |![](../../../../../assets/en/manual/web_interface/dashboard_save.png)|<|Save dashboard changes.| |![](../../../../../assets/en/manual/web_interface/dashboard_cancel.png)|<|Cancel dashboard changes.|
zh-cn	#### 查看和编辑仪表盘  要查看一个仪表盘，需在仪表盘列表中点击它的名称。  当**查看**一个仪表盘时，下列选项是可选的：  |   |   |   | |---|---|---| |![](../../../../../assets/en/manual/web_interface/dashboard_edit_button.png){width="107"}|<|切换到仪表盘**编辑**模式。<br>新建仪表盘和点击组件的![](../../../../../assets/en/manual/web_interface/widget_edit.png)编辑按钮时也会进入编辑模式| |![](../../../../../assets/en/manual/web_interface/dashboard_action_menu2.png)|<|打开动作菜单（查看下方的动作描述）。| |<|![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_view_actions.png){width="208"}|*分享* - 编辑仪表盘的分享偏好。仪表盘可以被设为公有或私有。公有仪表盘对所有用户可见。私有仪表盘仅对所有者可见。<br>私有仪表盘可被所有者向其他用户和用户组分享。查看分享配置的详细情况，可查看拓扑图 [configuration](/manual/config/visualization/maps/map#sharing) 组件。<br>*创建新的* - [创建](#creating_a_dashboard)一个新的仪表盘。<br>*克隆* - 通过复制已有仪表盘的属性来创建一个新的仪表盘。首先你会被提示输入仪表盘参数。然后，新仪表盘将在编辑模式打开，包含原仪表盘的所有组件。<br>*删除* - 删除仪表盘。<br>*创建新的报告* - 打开报告[configuration form](/manual/config/reports)弹窗。如果该用户无管理定期报告的权限，此选项会被禁用。<br>*查看相关报告* - 打开基于该仪表盘的已有报告的弹窗。 如果没有相关报告或该用户无管理定期报告的权限，此选项会被禁用。| |![](../../../../../assets/en/manual/web_interface/button_kiosk.png)|<|显示仅页面内容([kiosk模式](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)).<br>Kiosk模式也可通过下列URL参数访问：`/zabbix.php?action=dashboard.view&kiosk=1`.<br>要退回到普通模式：`/zabbix.php?action=dashboard.view&kiosk=0`|  当 **编辑** 一个仪表盘时，下列选项是可选的：  |   |   |   | |---|---|---| |![](../../../../../assets/en/manual/web_interface/dashboard_properties.png)|<|编辑通用仪表盘[参数](#creating_a_dashboard).| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_add_button.png)|<|添加一个新组件。<br>点击箭头按钮会打开动作菜单（查看下方的动作描述）。| |<|![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_edit_actions.png)|*添加组件* - 添加一个新组件<br>*添加页面* - 添加一个新页面<br>*粘贴组件* - 粘贴一个被复制的组件。如果没有被复制的组件，此选项是禁用的。一次只有一个实体（组件或页面）可以被复制。<br>*粘贴页面* - 粘贴一个被复制的页面。如果没有被复制的页面，此选项是禁用的。| |![](../../../../../assets/en/manual/web_interface/dashboard_save.png)|<|保存仪表盘的更改。| |![](../../../../../assets/en/manual/web_interface/dashboard_cancel.png)|<|取消仪表盘的更改。|

en-us	#### Viewing dashboards  To view all configured dashboards, click on *All dashboards* just below the section title.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboards.png)  Dashboards are displayed with a sharing tag:  -   *My* - indicates a private dashboard -   *Shared* - indicates a public dashboard or a private dashboard     shared with any user or user group  The filter located to the right above the list allows to filter dashboards by name and by those created by the current user.  To delete one or several dashboards, mark the checkboxes of the respective dashboards and click on *Delete* below the list.
zh-cn	#### 查看仪表盘  可点击组件标题下方的*所有仪表盘*来查看所有配置的仪表盘。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboards.png)  仪表盘和一个分享标签一起显示：  -   *我的* - 表示一个私有仪表盘 -   *分享* - 表示一个公有仪表盘或分享给某用户或用户组的私有仪表盘  列表右上方的过滤器允许通过名称和当前用户创建来过滤仪表盘。  要删除一个或多个仪表盘，勾选对应仪表盘的多选框，并点击列表下方的*删除*。

en-us	#### Viewing details  The times for problem start and recovery in *Monitoring → Problems* are links. Clicking on them opens more details of the event.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/event_details.png){width="600"}  Note how the problem severity differs for the trigger and the problem event - for the problem event it has been updated using the *Update problem* [screen](/manual/acknowledges#updating_problems).  In the action list, the following icons are used to denote the activity type:  -   ![icon\_generated.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_generated.png) -     problem event generated -   ![icon\_message.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_message.png) -     message has been sent -   ![icon\_acknowledged.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_acknowledged.png) -     problem event acknowledged -   ![icon\_unacknowledged.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_unacknowledged.png) -     problem event unacknowledged -   ![icon\_comment2.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_comment2.png) -     a comment has been added -   ![icon\_sev\_up1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_up1.png) -     problem severity has been increased (e.g. Information → Warning) -   ![icon\_sev\_down1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_down1.png) -     problem severity has been decreased (e.g. Warning → Information) -   ![icon\_severity\_back.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_severity_back.png) -     problem severity has been changed, but returned to the original     level (e.g. Warning → Information → Warning) -   ![icon\_remote.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_remote.png) -     a remote command has been executed -   ![icon\_recovery.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_recovery.png) -     problem event has recovered -   ![icon\_closed.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_closed.png) -     the problem has been closed manually
zh-cn	#### 查看详细信息  在 _监视 → 问题_ 异常开始和恢复的时间都有链接，单击链接可以打开更多事件细节。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/event_details.png){width="600"}  请注意触发器和问题时间的严重性是有区别的。 对于问题事件，它已使用_“更新问题”_[屏幕](/manual/acknowledges#updating_problems)进行了更新。  在操作列表中，以下图标用于表示活动类型：  - · ![icon\_generated.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_generated.png) -生成的问题事件 - · ![icon\_message.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_message.png) -消息已发送 - · ![icon\_acknowledged.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_acknowledged.png) - 确认问题事件 - · ![icon\_unacknowledged.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_unacknowledged.png) -未确认的问题事件 - · ![icon\_comment2.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_comment2.png) -添加了注释 - · ![icon\_sev\_up1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_up1.png) -问题严重性已增加（例如：信息→警告） - · ![icon\_sev\_down1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_down1.png) -问题严重性已降低（例如：警告→信息） - · ![icon\_severity\_back.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_severity_back.png) - 问题严重性已更改，但已恢复到原始级别（例如：警告→信息→警告） - · ![icon\_remote.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_remote.png) - 已执行远程命令 - · ![icon\_recovery.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_recovery.png) -问题事件已恢复 - · ![icon\_closed.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_closed.png) - 问题已手动关闭

en-us	#### Viewing event tags  Tagging, if defined, can be seen with new events in:  -   *Monitoring* → *Problems* -   *Monitoring* → *Problems* → *Event details* -   *Monitoring* → *Dashboard* → *Problems* widget (in popup window that     opens when rolling the mouse over problem name|  ![](../../../assets/en/manual/config/triggers/event_tags_view.png){width="600"}  Only the first three tag entries are displayed. If there are more than three tag entries, it is indicated by three dots. If you roll your mouse over these three dots, all tag entries are displayed in a pop-up window.  Note that the order in which tags are displayed is affected by tag filtering and the *Tag display priority* option in the filter of *Monitoring* → *Problems* or the *Problems* dashboard widget.
zh-cn	#### 查看事件标签  标记（如果已定义）可以在以下新事件中看到：  - *监控* → *问题* - *监控* → *问题* → *事件详情* - *监控* → *仪表板* → *问题*小部件（在弹出窗口中将鼠标悬停在问题名称上时打开|  ![](../../../assets/en/manual/config/triggers/event_tags_view.png){width="600"}  仅显示前三个标签对。如果有超过三个标签对，由三个点表示。如果你把鼠标移动到这三个点上，所有标签对都会显示在弹出窗口中。  请注意，在*监控* → *问题*或*问题*仪表板小部件中，标签的显示顺序受标签过滤器和过滤器中的*标签显示优先级*影响。

en-us	#### Viewing host group elements  This option is available if the "Host group elements" show option is chosen. When selecting "Host group elements" as the *show* option, you will at first see only one icon for the host group. However, when you save the map and then go to the map view, you will see that the map includes all the elements (hosts) of the certain host group:  |Map editing view|Map view| |----------------|--------| |![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_conf.png){width="450"}|![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_view.png){width="450"}|  Notice how the {HOST.NAME} macro is used. In map editing, the macro name is unresolved, while in map view all the unique names of the hosts are displayed.
zh-cn	#### 查看主机组元素  如果“主机组元素”显示选项为选择。选择“主机组元素”作为* show *选项时，您起初只会看到主机组的一个图标。然而，当你保存地图，然后转到地图视图，你会看到地图包括特定主机组的所有元素（主机）：  |地图编辑视图|地图视图| |----------------|--------| |![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_conf.png){width="450"}|![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_view.png){width="450"}|  请注意如何使用 {HOST.NAME} 宏。在地图编辑中，宏名称是不解析的，而在查看地图时，所有唯一名称的主机都被显示。

en-us	#### Viewing maps  To view a map, click on its name in the list of all maps.  ![](../../../../../assets/en/manual/web_interface/maps.png){width="600"}  You can use the drop-down in the map title bar to select the lowest severity level of the problem triggers to display. The severity marked as *default* is the level set in the map configuration. If the map contains a sub-map, navigating to the sub-map will retain the higher-level map severity (except if it is *Not classified*, in this case, it will not be passed to the sub-map).
zh-cn	#### 查看拓扑图  要查看某个拓扑图，单击所有拓扑图列表中对应的名称。  ![](../../../../../assets/en/manual/web_interface/maps.png){width="600"}  您可以使用拓扑图标题栏中的下拉列表来选择要显示问题触发器的最低严重性级别。默认严重性是在拓扑图配置中设置的级别。如果拓扑图包含子拓扑图，则导航到子拓扑图将保留上层级别拓扑图严重性。

en-us	### Viewing services  ![](../../../../../assets/en/manual/web_interface/services_view.png){width="600"}  A list of the existing services is displayed.  Displayed data:  |Parameter|Description| |---------|-----------| |*Name*|Service name.<br>The service name is a link to [service details](#service-details).<br>The number after the name indicates how many [child services](#service-details) the service has.| |*Status*|Service status:<br>**OK** - no problems<br>**(trigger color and severity)** - indicates a problem and its severity. If there are multiple problems, the color and severity of the problem with highest severity is displayed.| |*Root cause*|Underlying problems that directly or indirectly affect the service status are listed.<br>The same problems are listed as returned by the {SERVICE.ROOTCAUSE} [macro](/manual/appendix/macros/supported_by_location).<br>Click on the problem name to see more details about it in *Monitoring* → *Problems*.<br>Problems that do not affect the service status are not in the list.| |*Created at*|The time when the service was created is displayed.| |*Tags*|Tags of the service are displayed. Tags are used to identify a service.<br>Tags can be used in configuring service [actions](/manual/config/notifications/action).|
zh-cn	 ### 查看服务  ![](../../../../../assets/en/manual/web_interface/services_view.png){width="600"}  显示现有服务的列表。  显示的数据：  |参数|描述| |---------|-----------| |*Name*|服务名称。<br>该服务名称链接到[服务详情](#服务详情)。<br>名称后的数字表示该服务有多少[子服务](#服务详情)。| |*Status*|服务状态：<br>**OK** - 没问题<br>**(trigger color and severity)** - 表示问题及其严重性。如果存在多个问题，将显示严重性最高的问题的颜色和严重性。| |*Root cause*|列出了直接或间接影响服务状态的基本问题。<br>与{SERVICE.ROOTCAUSE} [宏](/manual/appendix/macros/supported_by_location)返回的问题相同。<br>点击问题名称，在 *监测* → *问题* 中查看有关该问题的更多详细信息。<br>不影响服务状态的问题不在列表中。| |*Created at*|显示创建服务的时间。| |*Tags*|显示服务的[标签](/manual/web_interface/frontend_sections/services/service)。标签用于识别服务中的服务[动作](/manual/web_interface/frontend_sections/services/service_actions) 和 [SLA](/manual/web_interface/frontend_sections/services/sla)。|

en-us	#### Viewing Zabbix process performance with "ps" and "top"  Since Zabbix 2.2 processes change their commandlines to display current activity and meaningful statistics, like:      UID        PID  PPID  C STIME TTY      TIME CMD     zabbix22  4584     1  0 14:55 ?    00:00:00 zabbix_server -c /home/zabbix22/zabbix_server.conf     zabbix22  4587  4584  0 14:55 ?    00:00:00 zabbix_server: configuration syncer [synced configuration in 0.041169 sec, idle 60 sec]     zabbix22  4588  4584  0 14:55 ?    00:00:00 zabbix_server: db watchdog [synced alerts config in 0.018748 sec, idle 60 sec]     zabbix22  4608  4584  0 14:55 ?    00:00:00 zabbix_server: timer #1 [updated 0 hosts, suppressed 0 events in 0.000472 sec, idle 59 sec]     zabbix22  4637  4584  0 14:55 ?    00:00:01 zabbix_server: history syncer #3 [processed 0 values, 0 triggers in 0.000036 sec, idle 1 sec]     zabbix22  4657  4584  0 14:55 ?    00:00:00 zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000004 sec, idle 5 sec]     zabbix22  4670     1  0 14:55 ?    00:00:00 zabbix_proxy -c /home/zabbix22/zabbix_proxy.conf     zabbix22  4673  4670  0 14:55 ?    00:00:00 zabbix_proxy: configuration syncer [synced config 15251 bytes in 0.111861 sec, idle 60 sec]     zabbix22  4674  4670  0 14:55 ?    00:00:00 zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.013643 sec, idle 30 sec]     zabbix22  4688  4670  0 14:55 ?    00:00:00 zabbix_proxy: icmp pinger #1 [got 1 values in 1.811128 sec, idle 5 sec]     zabbix22  4690  4670  0 14:55 ?    00:00:00 zabbix_proxy: housekeeper [deleted 9870 records in 0.233491 sec, idle 3599 sec]     zabbix22  4701  4670  0 14:55 ?    00:00:08 zabbix_proxy: http poller #2 [got 1 values in 0.024105 sec, idle 1 sec]     zabbix22  4707  4670  0 14:55 ?    00:00:00 zabbix_proxy: history syncer #4 [processed 0 values, 0 triggers in 0.000039 sec, idle 1 sec]     zabbix22  4738     1  0 14:55 ?    00:00:00 zabbix_agentd -c /home/zabbix22/zabbix_agentd.conf     zabbix22  4739  4738  0 14:55 ?    00:00:00 zabbix_agentd: collector [idle 1 sec]     zabbix22  4740  4738  0 14:55 ?    00:00:00 zabbix_agentd: listener #1 [waiting for connection]     zabbix22  4741  4738  0 14:55 ?    00:00:00 zabbix_agentd: listener #2 [processing request]  The main process is an exception. Instead of current activity the original commandline is shown. This helps to distinguish processes on systems with multiple Zabbix instances.  This feature is not implemented for Microsoft Windows.  If logging level is set to **DebugLevel=4** these activity and statistics messages are also written into log file.
zh-cn	#### 用“ps”和“top”查看Zabbix进程性能  从Zabbix 2.2 开始进程更改了它们的命令行以显示当前活动和有意义的统计信息，例如：      UID        PID  PPID  C STIME TTY      TIME CMD     zabbix22  4584     1  0 14:55 ?    00:00:00 zabbix_server -c /home/zabbix22/zabbix_server.conf     zabbix22  4587  4584  0 14:55 ?    00:00:00 zabbix_server: configuration syncer [synced configuration in 0.041169 sec, idle 60 sec]     zabbix22  4588  4584  0 14:55 ?    00:00:00 zabbix_server: db watchdog [synced alerts config in 0.018748 sec, idle 60 sec]     zabbix22  4608  4584  0 14:55 ?    00:00:00 zabbix_server: timer #1 [updated 0 hosts, suppressed 0 events in 0.000472 sec, idle 59 sec]     zabbix22  4637  4584  0 14:55 ?    00:00:01 zabbix_server: history syncer #3 [processed 0 values, 0 triggers in 0.000036 sec, idle 1 sec]     zabbix22  4657  4584  0 14:55 ?    00:00:00 zabbix_server: vmware collector #1 [updated 0, removed 0 VMware services in 0.000004 sec, idle 5 sec]     zabbix22  4670     1  0 14:55 ?    00:00:00 zabbix_proxy -c /home/zabbix22/zabbix_proxy.conf     zabbix22  4673  4670  0 14:55 ?    00:00:00 zabbix_proxy: configuration syncer [synced config 15251 bytes in 0.111861 sec, idle 60 sec]     zabbix22  4674  4670  0 14:55 ?    00:00:00 zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.013643 sec, idle 30 sec]     zabbix22  4688  4670  0 14:55 ?    00:00:00 zabbix_proxy: icmp pinger #1 [got 1 values in 1.811128 sec, idle 5 sec]     zabbix22  4690  4670  0 14:55 ?    00:00:00 zabbix_proxy: housekeeper [deleted 9870 records in 0.233491 sec, idle 3599 sec]     zabbix22  4701  4670  0 14:55 ?    00:00:08 zabbix_proxy: http poller #2 [got 1 values in 0.024105 sec, idle 1 sec]     zabbix22  4707  4670  0 14:55 ?    00:00:00 zabbix_proxy: history syncer #4 [processed 0 values, 0 triggers in 0.000039 sec, idle 1 sec]     zabbix22  4738     1  0 14:55 ?    00:00:00 zabbix_agentd -c /home/zabbix22/zabbix_agentd.conf     zabbix22  4739  4738  0 14:55 ?    00:00:00 zabbix_agentd: collector [idle 1 sec]     zabbix22  4740  4738  0 14:55 ?    00:00:00 zabbix_agentd: listener #1 [waiting for connection]     zabbix22  4741  4738  0 14:55 ?    00:00:00 zabbix_agentd: listener #2 [processing request]  主进程例外。显示的是原始命令行，而不是当前活动。这有助于区分具有多个 Zabbix 实例的系统上的进程。  此功能不支持 Microsoft Windows 。  如果日志级别设置为 **DebugLevel=4**这些活动和统计信息也会写入日志文件。

en-us	#### View mode buttons  The following buttons located in the top right corner are common for every section:  |   |   | |---|---| |![](../../../../assets/en/manual/web_interface/button_kiosk.png)|Display page in kiosk mode. In this mode only page content is displayed.<br>To exit kiosk mode, move the mouse cursor until the ![](../../../../assets/en/manual/web_interface/button_kiosk_leave.png) exit button appears and click on it. You will be taken back to normal mode.|
zh-cn	#### 查看模式按钮  位于右上角的下列按钮在每个组件中都是常见的：  |   |   | |---|---| |![](../../../../assets/en/manual/web_interface/button_kiosk.png)|在kiosk模式显示页面。在此模式仅显示页面内容。<br>要退出kiosk模式，移动鼠标直到![](../../../../assets/en/manual/web_interface/button_kiosk_leave.png) 退出按钮出现并点击它。你会返回普通模式。|

en-us	##### Virtual file system data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**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.<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.<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| |The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.<br><br>Since Zabbix 6.0.11, this item is capable of reporting file systems with the inode count equal to zero, which can be the case for file systems with dynamic inodes (e.g. btrfs).| |**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)|Since Zabbix 6.0.11, this item will not become unsupported in pfree/pused modes if the inode count equals to zero, which can be the case for file systems with dynamic inodes (e.g. btrfs). Instead the pfree/pused values for such file systems will be reported as "100" and "0" respectively.<br><br>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.|
zh-cn	##### 虚拟文件系统数据  |键值|<|<|<| |---|---|---|---| |描述|返回值|参数|注释| |**vfs.dev.discovery**|<|<|<| |块设备和类型的列表，用于底层自动发现。|JSON 对象| |此监控项仅支持Linux平台。<br><br>从 Zabbix 4.4.0 开始支持。| |**vfs.dev.read**\[<device>,<type>,<mode>\]|<|<|<| |磁盘读取统计信息。|整型 - 当`type`在 *sectors*, *operations*, *bytes* 中时<br><br>浮点型 - 当`type`在 *sps*, *ops*, *bps* 中时<br><br>*注意*: 如果更新间隔在3小时及以上时^**[2](#footnotes)**^, 会一直返回 '0'|**device** - 磁盘设备（默认是 *all* ^**[3](#footnotes)**^）<br>**type** - 可能的值： *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>请注意'type'在各平台的支持和默认情况，在[平台特性](/manual/appendix/items/supported_by_platform)查看详情。<br>*sps*, *ops*, *bps* 分别代表： sectors, operations, bytes 每秒的值。<br>**mode** - 可能的值： *avg1* (一分钟的平均值，默认), *avg5*, *avg15*.<br>此参数仅支持`type` 在 sps, ops, bps中的情况。|你也可使用相关设备名称（如`sda`）加 /dev/ 前缀（如`/dev/sda`）。<br><br>支持 LVM 逻辑卷。<br><br>不同操作系统的'type'默认值：<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>示例：<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* 在支持的平台曾经支持8个设备（7个单独的和一个*all*）。从 Zabbix 2.0.1 开始这个限制是1024个设备（1023个单独的和一个*all*）。| |**vfs.dev.write**\[<device>,<type>,<mode>\]|<|<|<| |磁盘写入统计信息。|整型 - 当`type`在 *sectors*, *operations*, *bytes* 中时<br><br>浮点型 - 当`type`在 *sps*, *ops*, *bps* 中时<br><br>*注意*: 如果更新间隔在3小时及以上时^**[2](#footnotes)**^, 会一直返回 '0'|**device** - 磁盘设备（默认是 *all* ^**[3](#footnotes)**^）<br>**type** - 可能的值： *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>请注意'type'在各平台的支持和默认情况，在[平台特性](/manual/appendix/items/supported_by_platform)查看详情。<br>*sps*, *ops*, *bps* 分别代表： sectors, operations, bytes 每秒的值。<br>**mode** - 可能的值： *avg1* (一分钟的平均值，默认), *avg5*, *avg15*.<br>此参数仅支持`type` 在 sps, ops, bps中的情况。|你也可使用相关设备名称（如`sda`）加 /dev/ 前缀（如`/dev/sda`）。<br><br>支持 LVM 逻辑卷。<br><br>不同操作系统的'type'默认值：<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>示例：<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* 在支持的平台曾经支持8个设备（7个单独的和一个*all*）。从 Zabbix 2.0.1 开始这个限制是1024个设备（1023个单独的和一个*all*）。| |**vfs.dir.count**\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |目录条目计数。|整型|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号链接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**types\_incl** - 要计数的目录条目类型, 可能的值：<br>*file* - 常规文件, *dir* - 子目录, *sym* - 符号链接, *sock* - 套接字, *bdev* - 块设备, *cdev* - 字符设备, *fifo* - FIFO, *dev* - "bdev,cdev"同义词, *all* - 所有类型 （默认）, 即 "file,dir,sym,sock,bdev,cdev,fifo".多种类型时需在双引号中用逗号隔开。<br>**types\_excl** - 不需要计数的目录条目类型 (见 <types\_incl>)。 如果某些条目类型同时位于 <types\_incl> 和 <types\_excl>中, 则不计算此类型的目录条目。<br>**max\_depth** - 遍历的子目录最大深度 **-1** （默认） - 无限制, **0** -不涉及子目录。<br>**min\_size** -要计数文件的最小大小（以字节为单位）。 小于此的文件不会被计算在内，[内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用。<br>**max\_size** - 要计数文件的最大大小（以字节为单位），大于此的文件将不会被计算在内。 [内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用<br>**min\_age** - 要计数的目录条目最小创建时间（以秒为单位）。最新的条目不进行计数。 [时间后缀](/manual/appendix/suffixes#time_suffixes) 可以被使用。<br>**max\_age** - 要计数的目录条目最大创建时间（以秒为单位）。 比此旧的条目将不被计算在内 (修改时间)。 [时间后缀](/manual/appendix/suffixes#time_suffixes) can 可以被使用.<br>**regex\_excl\_dir** - 描述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|不支持的环境变量, 如 %APP\_HOME%, $HOME 和 %TEMP% 。<br><br>伪目录 "." 和 ".." 不会被计算在内。<br><br>目录遍历不会跟踪符号链接。<br><br>在Windows上， 目录符号链接被跳过，硬链接只计算一次。<br><br>在计算条目大小时， `regex_incl` 和 `regex_excl` 都被应用于文件和目录， 但在选择要遍历的子目录时被忽略 (如果 regex\_incl 是 “(?i)\^.+\\.zip$” 并且 max\_depth 未设置, 那么所有子目录都将是遍历，但只会计算 zip 类型的文件)。<br><br>执行时间受限于代理 [配置](/manual/appendix/config/zabbix_agentd) (3秒)的默认时间设置，由于大目录遍历可能需要更长的时间，因此不会返回任何数据并且该监控项项将变为不受支持。 部分计数将不予返回<br><br>当按照大小过滤时，只有常规文件的大小具有意义，在Linux和BSD下 ，目录也有非零大小 (通常只有几KB)。设备大小为0 如  **/dev/sda1**的大小不反映相应分区的大小。因此，在使用 `<min_size>` 和 `<max_size>`, 建议指定 `<types_incl>` 为 "*file*",防止出现意外。<br><br>例如:<br>⇒ vfs.dir.count\[/dev\] - 监控 /dev (Linux)中的设备数量<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - 监控临时目录下的文件数量 (Windows)<br><br>自 Zabbix 4.0.0后支持。| |**vfs.dir.get**\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<| |目录条目列表|JSON|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号链接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**types\_incl** - 要计数的目录条目类型, 可能的值：<br>*file* - 常规文件, *dir* - 子目录, *sym* - 符号链接, *sock* - 套接字, *bdev* - 块设备, *cdev* - 字符设备, *fifo* - FIFO, *dev* - "bdev,cdev"同义词, *all* - 所有类型 （默认）, 即 "file,dir,sym,sock,bdev,cdev,fifo".多种类型时需在双引号中用逗号隔开。<br>**types\_excl** - 不需要计数的目录条目类型 (见 <types\_incl>)。 如果某些条目类型同时位于 <types\_incl> 和 <types\_excl>中, 则不计算此类型的目录条目。<br>**max\_depth** - 遍历的子目录最大深度 **-1** （默认） - 无限制, **0** -不涉及子目录。<br>**min\_size** -要计数文件的最小大小（以字节为单位）。 小于此的文件不会被计算在内，[内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用。<br>**max\_size** - 要计数文件的最大大小（以字节为单位），大于此的文件将不会被计算在内。 [内存后缀](/manual/appendix/suffixes#memory_suffixes) 可以被使用<br>**min\_age** - 要计数的目录条目最小创建时间（以秒为单位）。最新的条目不进行计数。 [时间后缀](/manual/appendix/suffixes#time_suffixes) 可以被使用。<br>**max\_age** - 要计数的目录条目最大创建时间（以秒为单位）。 比此旧的条目将不被计算在内 (修改时间)。 [时间后缀](/manual/appendix/suffixes#time_suffixes) can 可以被使用.<br>**regex\_excl\_dir** - 描述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|不支持的环境变量, 如 %APP\_HOME%, $HOME 和 %TEMP% 。<br><br>伪目录 "." 和 ".." 不会被计算在内。<br><br>目录遍历不会跟踪符号链接。<br><br>在Windows上， 目录符号链接被跳过，硬链接只计算一次。<br><br>在计算条目大小时， `regex_incl` 和 `regex_excl` 都被应用于文件和目录， 但在选择要遍历的子目录时被忽略 (如果 regex\_incl 是 “(?i)\^.+\\.zip$” 并且 max\_depth 未设置, 那么所有子目录都将是遍历，但只会计算 zip 类型的文件)。<br><br>执行时间受限于代理 [配置](/manual/appendix/config/zabbix_agentd) (3秒)的默认时间设置，由于大目录遍历可能需要更长的时间，因此不会返回任何数据并且该监控项项将变为不受支持。 部分计数将不予返回<br><br>当按照大小过滤时，只有常规文件的大小具有意义，在Linux和BSD下 ，目录也有非零大小 (通常只有几KB)。设备大小为0 如  **/dev/sda1**的大小不反映相应分区的大小。因此，在使用 `<min_size>` 和 `<max_size>`, 建议指定 `<types_incl>` 为 "*file*",防止出现意外。<br><br>例如:<br>⇒ vfs.dir.count\[/dev\] - 监控 /dev (Linux)中的设备数量<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - 监控临时目录下的文件数量 (Windows)<br><br>自 Zabbix 6.0.0后支持。| |**vfs.dir.size**\[dir,<regex\_incl>,<regex\_excl>,<mode>,<max\_depth>,<regex\_excl\_dir>\]|<|<|<| |目录大小(以字节为单位).|整型|**dir** - 目录的绝对路径<br>**regex\_incl** - 描述包含的 (文件, 目录, 符号链接 )的名称模式的正则 [表达式](/manual/regular_expressions#overview) ;如果为空，则包含所有 (默认值)<br>**regex\_excl** - 描述了排除 (文件, 目录, 符号链接) 的名称模式正则 [表达式](/manual/regular_expressions#overview) ; 如果为空，不排除任何实体 (默认)<br>**mode** - 可能的值：<br>*apparent* （默认） - 获取明确文件大小而不是磁盘使用情况( `du -sb dir`), *disk* - 获取磁盘使用情况 ( `du -s -B1 dir`)。与du 命令不同, vfs.dir.size 监控项在计算目录大小会考虑隐藏文件 (`du -sb .[^.]* *` 在目录中起作用).<br>**max\_depth** -目录遍历的最大深度。 **-1** （默认） - 无限制, **0** -不下钻到子目录<br>**regex\_excl\_dir** - 描述要排除的目录的名称模式的正则[表达式](/manual/regular_expressions#overview)，目录的所有内容都将被排除 (与 regex\_excl相比)|只计算 *zabbix* 用户至少可读权限的目录<br><br>在Windows上任何软链接被跳过，硬链接只计算一次<br><br>对于大型目录或慢速驱动器，此监控项可能会根据 [agent](/manual/appendix/config/zabbix_agentd) 和 [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 配置文件中的超时设置而超时，可以根据需要设置超时值。<br><br>示例:<br>⇒ vfs.dir.size\[/tmp,log\] - 计算 /tmp目录中包含 'log'的所有文件大小；<br>⇒ vfs.dir.size\[/tmp,log,\^.+\\.old$\] -计算 /tmp目录中包含'log'的所有文件大小，排除文件中包含'.old'的文件。<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support)。<br><br>自Zabbix 3.4.0后开始支持| |**vfs.file.cksum**\[file,<mode>\]|<|<|<| |文件校验和，由 UNIX cksum 算法计算得出。|整型 -`mode` 作为 *crc32*<br><br>字符串 -  `mode` 作为 *md5*, *sha256*|**file** - 文件模式的全路径<br>**mode** - *crc32* （默认）, *md5*, *sha256*|示例：<br>=> vfs.file.cksum\[/etc/passwd\]<br><br>返回值示例 (分别为crc32/md5/sha256):<br>675436101<br>9845acf68b73991eb7fd7ee0ded23c44<br>ae67546e4aac995e5c921042d0cf0f1f7147703aa42bfbfb65404b30f238f2dc<br><br>文件大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>自 Zabbix 6.0后开始支持`mode` 参数| |**vfs.file.contents**\[file,<encoding>\]|<|<|<| |检索文件的内容。|文本|**file** - 文件的全路径<br>**encoding** - 编码 [标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)|如果文件为空或仅包含 LF/CR 字符，则返回空字符串。<br><br>字节顺序标记 (BOM) 从输出中排除。<br><br>示例：<br>=> vfs.file.contents\[/etc/passwd\]<br><br>此监控项仅限于不大于 64 KB 的文件。<br><br>从Zabbix 2.0开始支持。| |**vfs.file.exists**\[file,<types\_incl>,<types\_excl>\]|<|<|<| |检查文件是否存在。|0 -没有找到<br><br>1 - 指定文件类型存在|**file** - 文件的完整路径。<br>**types\_incl** - 包含的文件类型列表, 可能的值： *file* (常规文件，默认 (如果 types\_excl未设置)), *dir* (目录), *sym* (符号链接), *sock* (套接字), *bdev* (块设备), *cdev* (字符设备), *fifo* (FIFO), *dev* (与 "bdev,cdev"同义), *all* (所有提到的类型，默认为如果 types\_excl设置的值)。<br>**types\_excl** - 排除的文件类型列表, 参阅 types\_incl 获取可能的值 (默认情况下不排除任何类型)|多个类型必须用逗号分隔，整个集合用 引号""括起来.<br>在Windows上，当使用命令行调用zabbix\_get.exe或agent2时，双引号必须用反斜杠 '\\' 转义，并且整个项目键用双引号括起来。<br><br>如果 <types\_incl> 和 <types\_excl>中的类型相同,则排除此类型的文件<br><br>例如:<br>=> vfs.file.exists\[/tmp/application.pid\]<br>=> vfs.file.exists\[/tmp/application.pid,"file,dir,sym"\]<br>=> vfs.file.exists\[/tmp/application\_dir,dir\]<br><br>文件大小取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>请注意，如果在不存在的目录中搜索目录，例如vfs.file.exists\[C:\\no\\dir,dir\] (其中不存在 'no')则该监控项可能会在Windows上变为不受支持| |**vfs.file.get**\[file\]|<|<|<| |返回有关文件的信息。|JSON 对象|**file** - 文件的全路径|类 UNIX 系统上支持的文件类型: 常规文件、目录、 符号链接、套接字、块设备、字符设备、FIFO<br><br>Windows 上支持的文件类型：常规文件、目录、符号链接<br><br>示例：<br>=> vfs.file.get\[/etc/passwd\] → 返回一个 JSON，其中包含有关 /etc/passwd 文件的信息(类型、用户、权限、SID、uid 等)<br><br>自Zabbix 6.0后开始支持| |**vfs.file.md5sum**\[file\]|<|<|<| |文件的MD5校验和。|字符串 (MD5的哈希文件)|**file** - 文件的全路径|示例：<br>=> vfs.file.md5sum\[/usr/local/etc/zabbix\_agentd.conf\]<br><br>示例的返回值:<br>b5052decb577e0fffd622d6ddc017e82<br><br>版本 1.8.6 中删除了此项目的文件大小限制 (64 MB)。<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support)。| |**vfs.file.owner**\[file,<ownertype>,<resulttype>\]|<|<|<| |检索文件的所有者|字符串|**file** - 文件的全路径<br>**ownertype** - *user* （默认） 或 *group* (仅Unix)<br>**resulttype** - *name* （默认） 或 *id*; 对于id - 在Unix上返回 uid/gid，Windows上返回SID|示例：<br>=> vfs.file.owner\[/tmp/zabbix\_server.log\] → 返回/tmp/zabbix\_server.log文件所有者<br>=> vfs.file.owner\[/tmp/zabbix\_server.log,,id\] → 返回 /tmp/zabbix\_server.log文件所有者id<br><br>自Zabbix 6.0后开始支持。| |**vfs.file.permissions**\[file\]|<|<|<| |返回一个 4 位字符串，其中包含具有 Unix 权限的八进制数。|字符串|**file** - 文件的全路径|在Windows上不支持<br><br>示例：<br>=> vfs.file.permissions\[/etc/passwd\] →返回/etc/passwd的文件权限, 例如, '0644'<br><br>自Zabbix 6.0后开始支持| |**vfs.file.regexp**\[file,regexp,<encoding>,<start line>,<end line>,<output>\]|<|<|<| |在文件中查找字符串。|包含匹配字符串的行，或由可选 `output` 参数指定的行|**file** - 文件的全路径<br>**regexp** - 描述所需模式编码的正则[表达式](/manual/regular_expressions#overview)<br>**encoding** - 编码[标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - 要搜索的第一行(默认为文件的第一行).<br>**end line** - 要搜索的最后一行的编号(默认为文件的最后一行)。<br>**output** - 可选的输出格式模板 **\\0** 转义序列被替换为匹配的文本部分(从匹配开始的第一个字符到匹配结束的字符) 而 **\\N** (其中 N=1...9) 转义序列被替换为第N个匹配组 (如果N超过捕获组的数量，则为空字符串)。|仅返回第一个匹配行。<br>如果没有行匹配表达式，则返回一个空字符串。<br><br>字节顺序标记 (BOM) 从输出中排除。<br><br>使用该参数的内容提取`output`发生在代理上。<br><br>从2.2版本开始支持 `start line`, `end line` and `output` 参数。<br><br>例如:<br>=> vfs.file.regexp\[/etc/passwd,zabbix\]<br>=> vfs.file.regexp\[/path/to/some/file,"(\[0-9\]+)$",,3,5,\\1\]<br>=> vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\] → 获取 *zabbix*用户ID| |**vfs.file.regmatch**\[file,regexp,<encoding>,<start line>,<end line>\]|<|<|<| |在文件中查找字符串。|0 - 未找到匹配<br><br>1 - 找到|**file** - 文件全路径<br>**regexp** - 描述所需模式编码的正则[表达式](/manual/regular_expressions#overview)<br>**encoding** - 编码[标识符](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - 要搜索的第一行(默认为文件的第一行).<br>**end line** - 要搜索的最后一行的编号(默认为文件的最后一行)。|字节顺序标记 (BOM) 被忽略。<br><br>从2.2开始支持 `start line` 和 `end line`参数。<br><br>示例：<br>=> vfs.file.regmatch\[/var/log/app.log,error\]| |**vfs.file.size**\[file,<mode>\]|<|<|<| |文件大小 (以字节为单位).|整型|**file** - 文件全路径<br>**mode** - 可能的值：<br>*bytes* （默认） 或 *lines* (也计算空行)|该文件必须对用户*zabbix*具有读取权限。<br><br>示例：<br>=> vfs.file.size\[/var/log/syslog\]<br><br>文件大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。<br><br>自Zabbix6.0起支持 `mode`参数。| |**vfs.file.time**\[file,<mode>\]|<|<|<| |文件时间信息。|整型 (Unix 时间戳)|**file** - 文件全路径<br>**mode** - 可能的值：<br>*modify* （默认） - 最后修改文件内容的时间<br>*access* - 最后读文件的时间。<br>*change* - 最后更改文件属性的时间。|示例：<br>=> vfs.file.time\[/etc/passwd,modify\]<br><br>文件大小限制取决于 [大文件支持](/manual/appendix/items/large_file_support).| |**vfs.fs.discovery**|<|<|<| |已安装文件系统及其类型的列表。用于底层自动发现.|JSON 对象| |从Zabbix 2.0开始支持。<br><br>自Zabbix3.0起，Windows支持{\#FSDRIVETYPE}宏。<br><br>自Zabbix6.0起，Windows支持 {\#FSLABEL}宏。| |**vfs.fs.get**|<|<|<| |挂载的文件系统列表、它们的类型、磁盘空间和 inode 统计信息。可用于底层自动发现.|JSON 对象| |自Zabbix 4.4.5后开始支持。<br><br>自Zabbix 6.0 起，Windows上支持 {\#FSLABEL}宏| |**vfs.fs.inode**\[fs,<mode>\]|<|<|<| |inode数量或百分比|整型 - 表示数量<br><br>浮点型 - 用于百分比|**fs** - 文件系统<br>**mode** - 可能的值：<br>*total* （默认）, *free*, *used*, //pfree // (空闲, 百分比), *pused* (使用, 百分比)|示例：<br>=> vfs.fs.inode\[/,pfree\]| |**vfs.fs.size**\[fs,<mode>\]|<|<|<| |磁盘空间（以字节为单位）或占总数的百分比。|整型 - 字节<br><br>浮点型 - 百分比|**fs** - 文件系统<br>**mode** - 可能的值：<br>*total* (默认), *free*, *used*, *pfree* (空闲, 百分比), *pused* (使用, 百分比)|如果是已挂载的卷，则返回本地文件系统的磁盘空间。<br><br>示例：<br>=> vfs.fs.size\[/tmp,free\]<br><br>当使用 *free* 模式时，文件系统的保留空间不考虑在内.|

en-us	 ##### Virtual memory data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**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*.|
zh-cn	##### 虚拟机数据  |键值|<|<|<| |---|---|---|---| |描述|返回值|参数|注释| |**vm.memory.size**\[<mode>\]|<|<|<| |内存大小（以字节为单位）或占总数的百分比。|整型 - 字节<br><br>浮点型 -百分比|**mode** - 可能的值：<br>*total* (默认), *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*, *used*, *pused* (used, percentage), *available*, *pavailable* (available, percentage)<br>参阅[平台特性](/manual/appendix/items/supported_by_platform) 支持和此参数的 [其他详细信息](/manual/appendix/items/vm.memory.size_params)。|此监控项接受三类参数：<br><br>1) *total* - 内存总量;<br>2)  特定于平台的内存类型: *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*;<br>3) 用户级估计有多少内存已使用和可用: *used*, *pused*, *available*, *pavailable*。|

en-us	##### Volumes  The images allow to use some mount points. These mount points are different and depend on Zabbix component type:  |   |   | |---|---| |**Volume**|**Description**| |**Zabbix agent**|<| |*/etc/zabbix/zabbix\_agentd.d*|The volume allows to include *\*.conf* files and extend Zabbix agent using the `UserParameter` feature| |*/var/lib/zabbix/modules*|The volume allows to load additional modules and extend Zabbix agent using the [LoadModule](/manual/config/items/loadablemodules) feature| |*/var/lib/zabbix/enc*|The volume is used to store TLS-related files. These file names are specified using `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` and `ZBX_TLSPSKFILE` environment variables| |**Zabbix server**|<| |*/usr/lib/zabbix/alertscripts*|The volume is used for custom alert scripts. It is the `AlertScriptsPath` parameter in [zabbix\_server.conf](/manual/appendix/config/zabbix_server)| |*/usr/lib/zabbix/externalscripts*|The volume is used by [external checks](/manual/config/items/itemtypes/external). It is the `ExternalScripts` parameter in [zabbix\_server.conf](/manual/appendix/config/zabbix_server)| |*/var/lib/zabbix/modules*|The volume allows to load additional modules and extend Zabbix server using the [LoadModule](/manual/config/items/loadablemodules) feature| |*/var/lib/zabbix/enc*|The volume is used to store TLS related files. These file names are specified using `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` and `ZBX_TLSPSKFILE` environment variables| |*/var/lib/zabbix/ssl/certs*|The volume is used as location of SSL client certificate files for client authentication. It is the `SSLCertLocation` parameter in zabbix\_server.conf| |*/var/lib/zabbix/ssl/keys*|The volume is used as location of SSL private key files for client authentication. It is the `SSLKeyLocation` parameter in [zabbix\_server.conf](/manual/appendix/config/zabbix_server)| |*/var/lib/zabbix/ssl/ssl\_ca*|The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is the `SSLCALocation` parameter in [zabbix\_server.conf](/manual/appendix/config/zabbix_server)| |*/var/lib/zabbix/snmptraps*|The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using the volumes\_from Docker option while creating a new instance of Zabbix server. SNMP trap processing feature could be enabled by using shared volume and switching the `ZBX_ENABLE_SNMP_TRAPS` environment variable to 'true'| |*/var/lib/zabbix/mibs*|The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in `/var/lib/zabbix/mibs`| |**Zabbix proxy**|<| |*/usr/lib/zabbix/externalscripts*|The volume is used by [external checks](/manual/config/items/itemtypes/external). It is the `ExternalScripts` parameter in [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)| |*/var/lib/zabbix/modules*|The volume allows to load additional modules and extend Zabbix server using the [LoadModule](/manual/config/items/loadablemodules) feature| |*/var/lib/zabbix/enc*|The volume is used to store TLS related files. These file names are specified using `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` and `ZBX_TLSPSKFILE` environment variables| |*/var/lib/zabbix/ssl/certs*|The volume is used as location of SSL client certificate files for client authentication. It is the `SSLCertLocation` parameter in [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)| |*/var/lib/zabbix/ssl/keys*|The volume is used as location of SSL private key files for client authentication. It is the `SSLKeyLocation` parameter in [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)| |*/var/lib/zabbix/ssl/ssl\_ca*|The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is the `SSLCALocation` parameter in [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)| |*/var/lib/zabbix/snmptraps*|The volume is used as location of snmptraps.log file. It could be shared by the zabbix-snmptraps container and inherited using the volumes\_from Docker option while creating a new instance of Zabbix server. SNMP trap processing feature could be enabled by using shared volume and switching the `ZBX_ENABLE_SNMP_TRAPS` environment variable to 'true'| |*/var/lib/zabbix/mibs*|The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in `/var/lib/zabbix/mibs`| |**Zabbix web interface based on Apache2 web server**|<| |*/etc/ssl/apache2*|The volume allows to enable HTTPS for Zabbix web interface. The volume must contain the two `ssl.crt` and `ssl.key` files prepared for Apache2 SSL connections| |**Zabbix web interface based on Nginx web server**|<| |*/etc/ssl/nginx*|The volume allows to enable HTTPS for Zabbix web interface. The volume must contain the two `ssl.crt`, `ssl.key` files and `dhparam.pem` prepared for Nginx SSL connections| |**Zabbix snmptraps**|<| |*/var/lib/zabbix/snmptraps*|The volume contains the `snmptraps.log` log file named with received SNMP traps| |*/var/lib/zabbix/mibs*|The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in `/var/lib/zabbix/mibs`|  For additional information use Zabbix official repositories in Docker Hub.
zh-cn	##### Volumes  Image 中允许使用一些挂载点。根据 Zabbix 组件类型，这些挂载点各不相同：  |   |   | |---|---| |**Volume**|**描述**| |**Zabbix agent**|<| |*/etc/zabbix/zabbix\_agentd.d*| 这个 volume 允许包含 *\*.conf* 文件并使用 `UserParameter` 扩展 Zabbix agent。| |*/var/lib/zabbix/modules*| 这个 volume 允许加载其它 module 并使用 [LoadModule](/manual/config/items/loadablemodules) 功能扩展 Zabbix agent。| |*/var/lib/zabbix/enc*|这个 volume 用于存放 TLS 相关的文件。这些文件名使用 `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` ，`ZBX_TLSPSKFILE` 等环境变量指定。| |**Zabbix server**|<| |*/usr/lib/zabbix/alertscripts*|这个 volume 用于自定义告警脚本。即 [zabbix\_server.conf](/manual/appendix/config/zabbix_server) 中的 `AlertScriptsPath` 参数。 | |*/usr/lib/zabbix/externalscripts*| 这个 volume 用于 [外部检查](/manual/config/items/itemtypes/external)。即 [zabbix\_server.conf](/manual/appendix/config/zabbix_server) 中的 `ExternalScripts` 参数。| |*/var/lib/zabbix/modules*|这个 volume 允许通过 [LoadModule](/manual/config/items/loadablemodules) 功能加载额外的模块以扩展 Zabbix server。| |*/var/lib/zabbix/enc*|这个 volume 用于存放 TLS 相关的文件。这些文件名使用 `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` ，`ZBX_TLSPSKFILE` 等环境变量指定。| |*/var/lib/zabbix/ssl/certs*|这个 volume 用于存放客户端认证的 SSL 客户端认证文件。即 [zabbix\_server.conf] 中的 `SSLCertLocation` 参数。| |*/var/lib/zabbix/ssl/keys*|这个 volume 用于存放客户端认证的 SSL 私钥文件。即 [zabbix\_server.conf](/manual/appendix/config/zabbix_server) 中的 `SSLKeyLocation` 参数。| |*/var/lib/zabbix/ssl/ssl\_ca*|这个 volume 用于存放 SSL 服务器证书认证的证书颁发机构(CA)文件。即 [zabbix\_server.conf](/manual/appendix/config/zabbix_server) 中的 `SSLCALocation` 参数。| |*/var/lib/zabbix/snmptraps*|这个 volume 用于存放 snmptraps.log 文件。它可由 zabbix-snmptraps 容器共享，并在创建 Zabbix server 新实例时使用 Docker 的 `--volumes-from` 选项继承。可以通过共享 volume ，并将 ZBX_ENABLE_SNMP_TRAPS 环境变量切换为 'true' 以启用 SNMP trap 处理功能。| |*/var/lib/zabbix/mibs*| 这个 volume 允许添加新的 MIB 文件。它不支持子目录，所有的 MIB 文件必须位于 `/var/lib/zabbix/mibs` 下。| |**Zabbix proxy**|<| |*/usr/lib/zabbix/externalscripts*|这个 volume 用于 [外部检查](/manual/config/items/itemtypes/external)。即 [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy) 中的 `ExternalScripts` 参数。| |*/var/lib/zabbix/modules*|这个 volume 允许通过 [LoadModule](/manual/config/items/loadablemodules) 功能加载额外的模块以扩展 Zabbix server。| |*/var/lib/zabbix/enc*|这个 volume 用于存放 TLS 相关的文件。这些文件名使用 `ZBX_TLSCAFILE`, `ZBX_TLSCRLFILE`, `ZBX_TLSKEY_FILE` ，`ZBX_TLSPSKFILE` 等环境变量指定。| |*/var/lib/zabbix/ssl/certs*|这个 volume 用于存放客户端认证的 SSL 客户端认证文件。即 [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy) 中的  `SSLCertLocation` 参数。| |*/var/lib/zabbix/ssl/keys*|这个 volume 用于存放客户端认证的 SSL 私钥文件。即 [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy) 中的 `SSLKeyLocation` 参数。| |*/var/lib/zabbix/ssl/ssl\_ca*|这个 volume 用于存放 SSL 服务器证书认证的证书颁发机构(CA)文件。即[zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy) 中的 `SSLCALocation` 参数。 | |*/var/lib/zabbix/snmptraps*|这个 volume 用于存放 snmptraps.log 文件。它可由 zabbix-snmptraps 容器共享，并在创建 Zabbix server 新实例时使用 Docker 的 `--volumes-from` 选项继承。可以通过共享 volume ，并将 ZBX_ENABLE_SNMP_TRAPS 环境变量切换为 'true' 以启用 SNMP trap 处理功能。| |*/var/lib/zabbix/mibs*|这个 volume 允许添加新的 MIB 文件。它不支持子目录，所有的 MIB 文件必须位于 `/var/lib/zabbix/mibs` 下。| |**基于 Apache2 web 服务器的 Zabbix web 界面**|<| |*/etc/ssl/apache2*| 这个 volume 允许为 Zabbix Web 界面启用 HTTPS。这个 volume 必须包含为 Apache2 SSL 连接准备的 `ssl.crt` 和 `ssl.key` 两个文件。| |**基于 Nginx web 服务器的 Zabbix web 界面**|<| |*/etc/ssl/nginx*| 这个 volume 允许为 Zabbix Web 接口启用 HTTPS。这个 volume 必须包含为 Nginx SSL 连接装备的 `ssl.crt` 和 `ssl.key` 两个文件。| |**Zabbix snmptraps**|<| |*/var/lib/zabbix/snmptraps*|这个 volume 包含了已接收到的 SNMP traps 命名的 `snmptraps.log`日志文件。| |*/var/lib/zabbix/mibs*|这个 volume 允许添加新的 MIB 文件。它不支持子目录，所有的 MIB 文件必须位于 `/var/lib/zabbix/mibs` 下。|  关于更多的信息请在 Docker Hub 的 Zabbix 官方仓库查看。

en-us	##### Web browser on client side  Cookies and JavaScript must be enabled.  The latest stable versions of Google Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari, and Opera are supported.  ::: notewarning The same-origin policy for IFrames is implemented, which means that Zabbix cannot be placed in frames on a different domain.\ \ Still, pages placed into a Zabbix frame will have access to Zabbix frontend (through JavaScript) if the page that is placed in the frame and Zabbix frontend are on the same domain. A page like `http://secure-zabbix.com/cms/page.html`, if placed into dashboards on `http://secure-zabbix.com/zabbix/`, will have full JS access to Zabbix. :::
zh-cn	##### 客户端浏览器  浏览器必须启用 Cookies 和 Java Script 。  支持Google Chrome，Mozilla Firefox，Microsoft Edge，Apple Safari和Opera的最新稳定版本。  ::: notewarning 为了执行 IFrame 的“同源政策”，意味着 Zabbix 不能放在不同域的 frames 中。\ \ 但是，如果放置在 frames 中的页面和 Zabbix 前端位于同一个域中，则置于 Zabbix frames 中的页面将可以访问 Zabbix 前端（通过JavaScript）。像 `http://secure-zabbix.com/cms/page.html` 这样的页面，如果置于 `http://secure-zabbix.com/zabbix/` 的聚合图形或仪表盘上，将拥有对 Zabbix 的完整 JS 访问权限。 :::

en-us	 ### Web certificate  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |web.certificate.get\[hostname,<port>,<address>\]|<|<|<| |Validates certificates and returns certificate details.|JSON object|**hostname** - can be either IP or DNS.<br>May contain the URL scheme (*https* only), path (it will be ignored), and port.<br>If a port is provided in both the first and the second parameters, their values must match.<br>If address (the 3rd parameter) is specified, the hostname is only used for SNI and hostname verification.<br>**port** - port number (default is 443 for HTTPS).<br>**address** - can be either IP or DNS. If specified, it will be used for connection, and hostname (the 1st parameter) will be used for SNI, and host verification.<br>In case, the 1st parameter is an IP and the 3rd parameter is DNS, the 1st parameter will be used for connection, and the 3rd parameter will be used for SNI and host verification.|This item turns unsupported if the resource specified in `host` does not exist or is unavailable or if TLS handshake fails with any error except an invalid certificate.<br><br>Currently, AIA (Authority Information Access) X.509 extension, CRLs and OCSP (including OCSP stapling), Certificate Transparency, and custom CA trust store are not supported.|
zh-cn	### Web certificate  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |web.certificate.get\[hostname,<port>,<address>\]|<|<|<| |验证证书并返回证书详细信息。|JSON 对象|**hostname** - 可以是IP或者DNS.<br>可能包含 URL scheme (只有*https* 的时候), path (可能会被忽略), 端口.<br>如果第一个和第二个参数都提供了端口，则它们的值必须匹配.<br>如果第三个参数指定了address，主机名仅用于SNI和主机名验证.<br>**port** - 端口 (HTTPS 缺省是 443 端口).<br>**address** - 可以是IP或者DNS. 如果指定了 address 参数，它将被用于连接，第一个参数的主机名将被用于SNI和主机验证.<br>如果第1个参数是IP，第3个参数是DNS，第1个参数用于连接，第3个参数用于SNI和主机验证.|这个监控项不支持这几种情况，在`host`中指定的资源不存在或不可用，或者TLS握手失败，除了无效的证书之外还有其他错误.<br><br>目前不支持 AIA (Authority Information Access) X.509 扩展, CRLs 和 OCSP (包括 OCSP stapling), 证书透明度, 自定义 CA 信任库.|

en-us	### Webhook integrations  A new integration is available allowing to use the [webhook](/manual/config/notifications/media/webhook) media type for creating [Github issues](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/github/README.md) from Zabbix notifications.
zh-cn	### Webhook 集成  Webhook 集成允许使用 [webhook](/manual/config/notifications/media/webhook) 媒体类型从 Zabbix 通知创建 [Github事件](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/github/README.md)。

en-us	### Webhook integrations  A new media type *LINE* is now available allowing to use the [webhook](/manual/config/notifications/media/webhook) feature for sending notifications about Zabbix events to *LINE* messenger.
zh-cn	### Webhook 集成  一种新的媒介类型 *LINE* 现在可用，允许使用 [webhook](/manual/config/notifications/media/webhook) 功能将有关 Zabbix 事件的通知发送到 *LINE* messenger。

en-us	### Webhook parameters  Parameters passed to webhook script when it is called, have the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Parameter name.| |value|string|Parameter value, supports macros.<br>Supported macros are described on the [Supported macros](/manual/appendix/macros/supported_by_location) page.|
zh-cn	### Webhook 参数  调用 webhook 脚本时传递的参数，具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**name**<br>（必需）|string|参数名称。| |value|string|参数值，支持宏。<br>支持的宏在[支持的宏](/manual/appendix/macros/supported_by_location)页面中描述。|

en-us	### Webhook parameters  Parameters passed to webhook script when it is called have the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Parameter name.| |value|string|Parameter value. Supports [macros](/manual/appendix/macros/supported_by_location).|
zh-cn	### Webhook参数 webhook脚本运行时被传入的参数有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |**name**<br>(必需)|string|参数名称。| |value|string|参数值。 支持[宏](/manual/appendix/macros/supported_by_location)。|

en-us	### Webhook parameters  Parameters passed to webhook script when it is called have the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**name**<br>(required)|string|Parameter name.| |value|string|Parameter value. Supports [macros](/manual/appendix/macros/supported_by_location).|
zh-cn	### Webhook参数 webhook脚本运行时被传入的参数有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |**name**<br>(必需)|string|参数名称。| |value|string|参数值。 支持[宏](/manual/appendix/macros/supported_by_location)。|

en-us	##### Web interface  For an easy access to Zabbix from anywhere and from any platform, the web-based interface is provided. The interface is part of Zabbix server, and usually (but not necessarily) runs on the same physical machine as the one running the server.
zh-cn	##### Web 界面  为了从任何地方和任何平台轻松访问，Zabbix 提供了基于 Web 的界面。该接口是 Zabbix server 的一部分，通常（但不一定）与 server 运行在同一台设备上。

en-us	#### Web monitoring and HTTP agent  Zabbix server leaks memory on CentOS 6, CentOS 7 and possibly other related Linux distributions due to an [upstream bug](https://bugzilla.redhat.com/show_bug.cgi?id=1057388) when "SSL verify peer" is enabled in web scenarios or HTTP agent. Please see [ZBX-10486](https://support.zabbix.com/browse/ZBX-10486) for more information and available workarounds.
zh-cn	#### Web 监控和 HTTP agent  由于 [上游 bug](https://bugzilla.redhat.com/show_bug.cgi?id=1057388)，在 Web 场景或 HTTP agent 中启用 “SSL  verify peer” 时，Zabbix server 在 CentOS 6、CentOS 7 或其他 Linux 发行版上可能存在内存泄漏（leaks memory）的问题。参考 [ZBX-10486](https://support.zabbix.com/browse/ZBX-10486)  获取更多信息和解决方案 。

en-us	#### Web monitoring and HTTP agent  Zabbix server leaks memory on CentOS 6, CentOS 7 and possibly other related Linux distributions due to an [upstream bug](https://bugzilla.redhat.com/show_bug.cgi?id=1057388) when "SSL verify peer" is enabled in web scenarios or HTTP agent. Please see [ZBX-10486](https://support.zabbix.com/browse/ZBX-10486) for more information and available workarounds.  
zh-cn	#### Web 监控和 HTTP agent  由于 [上游 bug](https://bugzilla.redhat.com/show_bug.cgi?id=1057388)，在 Web 场景或 HTTP agent 中启用 “SSL  verify peer” 时，Zabbix server 在 CentOS 6、CentOS 7 或其他 Linux 发行版上可能存在内存泄漏（leaks memory）的问题。参考 [ZBX-10486](https://support.zabbix.com/browse/ZBX-10486)  获取更多信息和解决方案 。

en-us	#### Web monitoring  Configure web scenarios to monitor your web applications and services.  [Web scenario API](/manual/api/reference/httptest)
zh-cn	#### Web 监控  配置 Web 场景以监控 Web 应用程序和服务。  [Web scenario API](/manual/api/reference/httptest)

en-us	 ##### Web monitoring data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**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\]|
zh-cn	##### 网页监控数据  |键值|<|<|<| |---|---|---|---| |描述|返回值|参数|注释| |**web.page.get**\[host,<path>,<port>\]|<|<|<| |获取网页内容。|作为文本的网页源（包括标题）|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent必须在启用 IPv6 支持的情况下编译。<br><br>示例：<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |**web.page.perf**\[host,<path>,<port>\]|<|<|<| |整个网页的加载时间（以秒为单位）。|浮点型|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent必须在启用 IPv6 支持的情况下编译。<br><br>示例：<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |**web.page.regexp**\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<| |在网页上查找字符串。|匹配的字符串, 或由可选`output`参数指定。|**host** - 主机名或URL (如  `scheme://host:port/path`, 只有 *host*是强制的).<br>允许的URL方案: *http*, *https*^**[4](#footnotes)**^. 缺少的方案将被使用 *http*。如果URL 指定了 `path` 和 `port`必须为空。 连接服务需要验证时需指定用户名和密码，示例： `http://user:password@www.example.com` 只有curl^**[4](#footnotes)**^才有可能。<br>主机名支持Punycode。<br>**path** - HTML文档路径(默认为 /)<br>**port** - 端口号(默认是 http 80)<br>**regexp** - 描述了所需模式的正则 [表达式](/manual/regular_expressions#overview)<br>**length** -返回最大的字符数<br>**output** - 可选的输出格式模板， **\\0** 转义序列被替换为文本的匹配部分 (从从匹配开始的第一个字符到匹配结束的字符) ，而 **\\N** (其中 N=1...9) 转义序列被替换为第 N 个匹配组 (如果 N 超过捕获的组数，则为空字符串)。|如果指定的资源在 `host`中不存在或不可用，则此监控项将不受支持。<br><br>`host` 可以是主机名、域名、IPv4 或 IPv6 地址。但是对于 IPv6 地址，Zabbix agent必须在启用 IPv6 支持的情况下编译。<br><br>使用该参数的内容提取 `output` 发生在agent上。<br><br>从2.2版本开始支持 `output`参数。<br><br>示例：<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]|

en-us	#### Web scenario  In a [web scenario](/manual/web_monitoring) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Name|<|yes| |Update interval|<|no| |Agent|<|yes| |HTTP proxy|<|yes| |Variables (values only)|<|yes| |Headers (names and values)|<|yes| |*Steps*|<|<| | |Name|yes| |^|URL^[3](supported_by_location_user#footnotes)^|yes| |^|Variables (values only)|yes| |^|Headers (names and values)|yes| |^|Timeout|no| |^|Required string|yes| |^|Required status codes|no| |*Authentication*|<|<| | |User|yes| |^|Password|yes| |^|SSL certificate|yes| |^|SSL key file|yes| |^|SSL key password|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### Web 场景  在 [web 场景](/manual/web_monitoring)配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |名称|<|支持| |更新间隔|<|不支持| |Agent|<|支持| |HTTP 代理|<|支持| |变量 (只允许值)|<|支持| |请求头部 (名称和值)|<|支持| |*步骤*|<|<| | |名称|支持| |^|URL^[3](supported_by_location_user#footnotes)^|支持| |^|变量 (只允许值)|支持| |^|请求头部 (名称和值)|支持| |^|超时时间|不支持| |^|返回字符串|支持| |^|返回状态码|不支持| |*认证*|<|<| | |用户|支持| |^|密码|支持| |^|SSL 证书|支持| |^|SSL 密钥文件|支持| |^|SSL 密钥密码|支持| |*标签*|<|<| | |标签名称|支持| |^|标签值|支持|

en-us	# > Web scenario object  The following objects are directly related to the `webcheck` API.
zh-cn	 # > Web场景对象  以下对象都是与`webcheck` 直接相关的API。

en-us	### Web scenario tag  The web scenario tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Web scenario tag name.| |value|string|Web scenario tag value.|
zh-cn	### Web场景标签  Web场景标签对象具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必填)|string|Web场景标签的名称。| |value|string|Web场景标签的值。|

en-us	### Web scenario tag  The web scenario tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Web scenario tag name.| |value|string|Web scenario tag value.|
zh-cn	### Web场景标签  Web场景标签对象具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必填)|string|Web场景标签的名称。| |value|string|Web场景标签的值。|

en-us	### Web scenario  The web scenario object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |httptestid|string|*(readonly)* ID of the web scenario.| |**hostid**<br>(required)|string|ID of the host that the web scenario belongs to.| |**name**<br>(required)|string|Name of the web scenario.| |agent|string|User agent string that will be used by the web scenario.<br><br>Default: Zabbix| |authentication|integer|Authentication method that will be used by the web scenario.<br><br>Possible values:<br>0 - *(default)* none;<br>1 - basic HTTP authentication;<br>2 - NTLM authentication.| |delay|string|Execution interval of the web scenario. Accepts seconds, time unit with suffix and user macro.<br><br>Default: 1m.| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP headers that will be sent when performing a request.| |http\_password|string|Password used for basic HTTP or NTLM authentication.| |http\_proxy|string|Proxy that will be used by the web scenario given as *http://\[username\[:password\]@\]proxy.example.com\[:port\]*.| |http\_user|string|User name used for basic HTTP or NTLM authentication.| |nextcheck|timestamp|*(readonly)* Time of the next web scenario execution.| |retries|integer|Number of times a web scenario will try to execute each step before failing.<br><br>Default: 1.| |ssl\_cert\_file|string|Name of the SSL certificate file used for client authentication (must be in PEM format).| |ssl\_key\_file|string|Name of the SSL private key file used for client authentication (must be in PEM format).| |ssl\_key\_password|string|SSL private key password.| |status|integer|Whether the web scenario is enabled.<br><br>Possible values are:<br>0 - *(default)* enabled;<br>1 - disabled.| |templateid|string|*(readonly)* ID of the parent template web scenario.| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Web scenario variables.| |verify\_host|integer|Whether to verify that the host name specified in the SSL certificate matches the one used in the scenario.<br><br>Possible values are:<br>0 - *(default)* skip host verification;<br>1 - verify host.| |verify\_peer|integer|Whether to verify the SSL certificate of the web server.<br><br>Possible values are:<br>0 - *(default)* skip peer verification;<br>1 - verify peer.| |uuid|string|*(readonly on already existing web scenarios)*<br>Global unique identifier, used for linking imported web scenarios to already existing ones. Used only for web scenarios on templates.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### Web场景  Web场景对象具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |httptestid|字符串|*(只读)* Web场景的ID。| |**hostid**<br>(必填)|字符串|Web场景所属主机的ID。| |**name**<br>(必填)|字符串|Web场景的名称。| |agent|字符串|Web场景将使用的用户代理字符串。<br><br>默认： Zabbix| |authentication|整数|Web场景将使用的身份认证方法。<br><br>可用值：<br>0 - *(默认)* none；<br>1 - 基本的HTTP身份认证；<br>2 - NTLM身份认证。| |delay|字符串|Web场景的执行间隔。接受秒，带后缀的时间单位和用户宏。<br><br>默认： 1m。| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|执行请求时将发送的HTTP请求头。| |http\_password|字符串|用于基本的HTTP或NTLM身份认证的密码。| |http\_proxy|字符串|Web场景将使用的代理，如下所示： *http://\[username\[:password\]@\]proxy.example.com\[:port\]*。| |http\_user|字符串|用于基本的HTTP或NTLM身份认证的用户名。| |nextcheck|时间戳|*(只读)*下一个Web场景执行的时间。| |retries|整数|Web场景在失败之前尝试执行每个步骤的次数。<br><br>默认： 1。| |ssl\_cert\_file|字符串|用于客户端身份认证的SSL证书文件的名称(必须是PEM格式)。| |ssl\_key\_file|字符串|用于客户端身份认证的SSL私钥文件的名称(必须是PEM格式)。| |ssl\_key\_password|字符串|SSL私钥密码。| |status|整数|Web场景是否可用。<br><br>可用值：<br>0 - *(默认)* 可用；<br>1 - 不可用。| |templateid|字符串|*(只读)* 父模板Web场景的ID。| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|Web场景变量。| |verify\_host|整数|是否验证SSL证书里指定的主机名与Web场景中使用的主机名匹配。<br><br>可能的值：<br>0 - *(默认)* 跳过主机验证；<br>1 - 验证主机。| |verify\_peer|整数|是否验证Web服务器的SSL证书。<br><br>可用值：<br>0 - *(默认)* 跳过对等验证；<br>1 - 验证对等。| |uuid|字符串|*(在现有的Web场景上只读)*<br>全局唯一标识符，用于将导入的Web场景连接到现有场景。仅用于模板上的web场景。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Web scenario  This class is designed to work with web scenarios.  Object references:\  -   [Web scenario](/manual/api/reference/httptest/object#web_scenario) -   [Scenario step](/manual/api/reference/httptest/object#scenario_step)  Available methods:\  -   [httptest.create](/manual/api/reference/httptest/create) - creating     new web scenarios -   [httptest.delete](/manual/api/reference/httptest/delete) - deleting     web scenarios -   [httptest.get](/manual/api/reference/httptest/get) - retrieving web     scenarios -   [httptest.update](/manual/api/reference/httptest/update) - updating     web scenarios
zh-cn	 # Web场景  此类用于Web场景。  对象引用：\  -   [Web scenario](/manual/api/reference/httptest/object#Web场景) -   [Scenario step](/manual/api/reference/httptest/object#场景步骤)  可用方法：\  -   [httptest.create](/manual/api/reference/httptest/create) - 创建新的Web场景 -   [httptest.delete](/manual/api/reference/httptest/delete) - 删除Web场景 -   [httptest.get](/manual/api/reference/httptest/get) - 获取Web场景 -   [httptest.update](/manual/api/reference/httptest/update) - 更新Web场景

en-us	### Web server hardening
zh-cn	### Web 服务器加固

en-us	#### Welcome screen  Open Zabbix frontend URL in the browser. If you have installed Zabbix from packages, the URL is:  -   for Apache: *http://<server\_ip\_or\_name>/zabbix* -   for Nginx: *http://<server\_ip\_or\_name>*  You should see the first screen of the frontend installation wizard.  Use the *Default language* drop-down menu to change system default language and continue the installation process in the selected language (optional). For more information, see [Installation of additional frontend languages](/manual/appendix/install/locales).  ![](../../../assets/en/manual/installation/install_1.png){width="550"}
zh-cn	#### 欢迎主界面  在浏览器中输入Zabbix 前端的URL来进入主界面。通过依赖包的方式对Zabbix进行安装，其URL的输入格式会略有不同，相关格式如下所示：  -   对于 Apache: *http://<server\_ip\_or\_name>/zabbix* -   对于 Nginx: *http://<server\_ip\_or\_name>*  根据安装方式输入正确的URL后，您将会进入到前端安装的向导程序。  使用*系统默认语言*下拉菜单，更改系统默认语言，并以所选语言继续安装过程（非必选）。详细信息，请参考 [Installation of additional frontend languages](/manual/appendix/install/locales).  ![](../../../assets/en/manual/installation/install_1.png){width="550"}

en-us	##### What can be exported/imported  Objects that can be exported/imported are:  -   [host groups](/manual/xml_export_import/groups) (*through Zabbix API     only*) -   [templates](/manual/xml_export_import/templates) -   [hosts](/manual/xml_export_import/hosts) -   [network maps](/manual/xml_export_import/maps) -   [media types](/manual/xml_export_import/media) -   images
zh-cn	#####  可以导出/导入什么  可以导出/导入的对象有:  -   [主机群组](/manual/xml_export_import/groups) (*只能通过Zabbix API*) -   [模板](/manual/xml_export_import/templates) -   [主机](/manual/xml_export_import/hosts) -   [网络设备拓扑图](/manual/xml_export_import/maps) -   [媒介类型](/manual/xml_export_import/media) -   图片

en-us	#### Whitespace  Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`.  
zh-cn	#### 空格  空格（空格、制表符）可以在括号符号段和表达式中自由使用，例如，`$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`.

en-us	#### Widget menu  The widget menu contains different options based on whether the dashboard is in the edit or view mode:  |Widget menu|Options| |-----------|-------| |In dashboard edit mode:<br>![widget\_menu\_edit.png](../../../../../assets/en/manual/web_interface/widget_menu_edit.png)|*Copy* - copy the widget<br>*Paste* - paste a copied widget over this widget<br>This option is grayed out if no widget has been copied.<br>*Delete* - delete the widget| |In dashboard view mode:<br>![widget\_menu\_view.png](../../../../../assets/en/manual/web_interface/widget_menu_view.png)|*Copy* - copy the widget<br>*Download image* - download the widget as a PNG image<br>(only available for [graph](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph)/[classic graph](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic) widgets)<br>*Refresh interval* - select the frequency of refreshing<br>the widget contents|
zh-cn	#### 组件菜单  组件菜单在仪表盘编辑或查看模式包括不同的选项：  |组件菜单|选项| |-----------|-------| |在仪表盘编辑模式：<br>![widget\_menu\_edit.png](../../../../../assets/en/manual/web_interface/widget_menu_edit.png)|*复制* - 复制组件<br>*粘贴* - 粘贴一个复制的组件来覆盖当前组件<br>当没有复制的组件时，此选项被禁用。<br>*删除* - 删除组件| |在仪表盘查看模式：<br>![widget\_menu\_view.png](../../../../../assets/en/manual/web_interface/widget_menu_view.png)|*复制* - 复制组件<br>*下载图片* - 将组件下载为PNG图片<br>(只对[图表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph)/[传统图表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic)组件可用)<br>*刷新间隔* - 选择刷新间隔<br>组件内容|

en-us	### Windows installer paths When using Windows installers, it is recommended to use default paths provided by the installer as using custom paths without proper permissions could compromise the security of the installation.
zh-cn	### Windows 安装程序路径 使用 Windows 安装程序时，建议使用安装程序提供的默认路径，因为使用没有适当权限的自定义路径可能会危及安装的安全性。

en-us	#### Windows-specific item keys  |Item key|User group|<| |--------|----------|-| | |Recommended|Minimum technically acceptable (functionality is limited)| |eventlog|Event Log Readers|Guests| |net.if.list|Guests|Guests| |perf\_counter|Performance Monitor Users|Performance Monitor Users| |proc\_info|Administrators|Guests| |service.discovery|Guests|Guests| |service.info|Guests|Guests| |services|Guests|Guests| |wmi.get|Administrators|Guests| |vm.vmemory.size|Guests|Guests|
zh-cn	 #### Windows特定的监控项键  |监控项 key|用户组|<| |--------|----------|-| | |推荐的|技术上可接受的最低权限组 (功能有限)| |eventlog|Event Log Readers|Guests| |net.if.list|Guests|Guests| |perf\_counter|Performance Monitor Users|Performance Monitor Users| |proc\_info|Administrators|Guests| |service.discovery|Guests|Guests| |service.info|Guests|Guests| |services|Guests|Guests| |wmi.get|Administrators|Guests| |vm.vmemory.size|Guests|Guests|

en-us	##### Windows  Use Zabbix Windows agent included (pre-compiled) into Zabbix distribution.
zh-cn	##### Windows  使用包含（预编译）到 Zabbix 发行版中的 Zabbix Windows 代理。

en-us	#### Working with the menu  A [global search](/manual/web_interface/global_search) box is located below the Zabbix logo.  The menu can be collapsed or hidden completely:  -   To collapse, click on     ![](../../../assets/en/manual/web_interface/button_collapse.png)     next to Zabbix logo -   To hide, click on     ![](../../../assets/en/manual/web_interface/button_hide.png) next to     Zabbix logo  |   |   | |---|---| |![](../../../assets/en/manual/web_interface/collapsed_menu.png)|![](../../../assets/en/manual/web_interface/hidden_menu.png)| |Collapsed menu with only the icons visible.|Hidden menu.|
zh-cn	#### 使用菜单  [全局搜索](/manual/web_interface/global_search) 框位于 Zabbix logo 的下方。  此菜单可以折叠或完全隐藏：  -   要折叠，请点击 Zabbix logo 旁边的     ![](../../../assets/en/manual/web_interface/button_collapse.png) -   要隐藏，请点击 Zabbix logo 旁边的     ![](../../../assets/en/manual/web_interface/button_hide.png)   |   |   | |---|---| |![](../../../assets/en/manual/web_interface/collapsed_menu.png)|![](../../../assets/en/manual/web_interface/hidden_menu.png)| |只有图标可见的折叠菜单。|隐藏菜单。|

en-us	#### Wrong conversion of services in Zabbix 6.0.0-6.0.2  In Zabbix 6.0, new more flexible service status calculation algorithms were introduced.   After an upgrade from Zabbix <6.0 to Zabbix 6.0.0, 6.0.1, 6.0.2, the service status calculation rules 'Most critical if all children have problems' and 'Most critical of child nodes' will become swapped. Services created in Zabbix 6.0.0 and newer will have correct status calculation rules.   When upgrading from versions <6.0 to Zabbix 6.0.3 or newer, Zabbix will correctly update service status calculation rules. Upgrading from 6.0.x to 6.0.3 will have no effect on service status calculation rules.
zh-cn	#### Zabbix 6.0.0-6.0.2 中服务转换错误  在 Zabbix 6.0 中，引入了新的更灵活的服务状态计算算法。  从 Zabbix <6.0 版本升级到 Zabbix 6.0.0，6.0.1，6.0.2 版本，服务状态计算规则 “Most critical if all children have problems” 和 “Most critical of child nodes” 将被交换。在 Zabbix 6.0.0 及更高版本中创建的服务将具有正确的状态计算规则。  从  <6.0 版本升级到  Zabbix 6.0.3 或更高版本时，Zabbix  将正确更新服务状态计算规则。从 6.0.x 版本升级到 6.0.3 版本不会影响服务状态计算规则。

en-us	#### XML  The XML object allows the processing of XML data in the item and low-level discovery preprocessing and webhooks.  ::: noteimportant  In order to use XML object, server/proxy must be compiled with libxml2 support. :::  |Method|Description| |--|--------| |`XML.query(data, expression)`|Retrieves node content using XPath. Returns null if node is not found.<br>**expression** - an XPath expression;<br>**data** - XML data as a string.| |`XML.toJson(data)`|Converts data in XML format to JSON.| |`XML.fromJson(object)`|Converts data in JSON format to XML.|  Example:  *Input:*      <menu>         <food type = "breakfast">             <name>Chocolate</name>             <price>$5.95</price>             <description></description>             <calories>650</calories>         </food>     </menu>  *Output:*  ``` {.java} {     "menu": {         "food": {             "@type": "breakfast",             "name": "Chocolate",             "price": "$5.95",             "description": null,             "calories": "650"         }     } } ```
zh-cn	#### XML  XML 对象允许处理监控项中的 XML 数据以及底层自动发现预处理和 Webhook。  ::: noteimportant 要使用 XML 对象，必须使用支持 libxml2 编译的Server或proxy。 :::  |方法|描述| |------|-----------| |`XML.query(expression, data)`|使用 XPath 检索节点内容。 如果未找到节点，则返回 null。<br>**expression** - XPath 表达式；<br>**data** - XML 数据作为字符串。| |`XML.toJson(data)`|将 XML 格式的数据转换为 JSON。| |`XML.fromJson(object)`|将 JSON 格式的数据转换为 XML。|  示例:  *输入:*      <menu>         <food type = "breakfast">             <name>Chocolate</name>             <price>$5.95</price>             <description></description>             <calories>650</calories>         </food>     </menu>  *输出:*  ``` {.java} {     "menu": {         "food": {             "@type": "breakfast",             "name": "Chocolate",             "price": "$5.95",             "description": null,             "calories": "650"         }     } } ```

en-us	#### YAML export/import  There are some known issues with YAML [export/import](/manual/xml_export_import):  -   Error messages are not translatable; -   Valid JSON with a .yaml file extension sometimes cannot be imported; -   Unquoted human-readable dates are automatically converted to Unix     timestamps.
zh-cn	#### YAML 导出/导入  YAML [导出/导入](/manual/xml_export_import) 存在一些已知问题：  -   错误消息不会被翻译； -   有时会无法导入带有 .yaml 文件扩展名的有效 JSON 文件； -   日期如果不加引号会自动转换为 Unix 时间戳。

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

en-us	You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   When upgrading from previous versions, the latest templates can be     downloaded from the [Zabbix Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)     and manually imported into Zabbix in the *Configuration* →     *Templates* section. If a template with the same name already     exists, check the *Delete missing* option before importing to     achieve a clean import. This way the items that have been excluded     from the updated template will be removed (note, that history of the     deleted items will be lost).
zh-cn	可以获得以下模板：  -   在新装环境的 *Configuration* → *Templates* 中； -   从以前的版本升级时，可以从 [Zabbix Git 存储库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates) 下载最新的模板，并在 *Configuration* → *Templates* 部分手动导入 Zabbix 。如果已存在同名模板，请在导入前选中删除缺失选项以实现干净导入。这样，已从更新模板中排除的监控项将被删除（请注意，已删除监控项的历史记录将丢失）。

en-us	# Zabbix agent 2  
zh-cn	# Zabbix agent 2  

en-us	 #### Zabbix agent 2 active check configuration  A new optional [configuration parameter](/manual/appendix/config/zabbix_agent2) *ForceActiveChecksOnStart* has been added to Zabbix agent 2.  Setting the parameter to  `ForceActiveChecksOnStart=1` will ensure item data for active checks is collected immediately upon Zabbix agent restart, except for items with *Scheduling* [update interval](/manual/config/items/item/custom_intervals#scheduling-intervals). Otherwise, the first data collection after an agent restart will happen at random time, which is less than item update interval, to prevent spikes in resource usage.   It is also possible to set this option only for a specific plugin by using *Plugins.\<PluginName>.System.ForceActiveChecksOnStart* (for example, `Plugins.Uptime.System.ForceActiveChecksOnStart=1`). If set, a plugin-level parameter will override the global setting. 
zh-cn	 #### Zabbix agent 2 主动检查配置  Zabbix agent 2 中添加了一个新的可选[配置参数](/manual/appendix/config/zabbix_agent2) *ForceActiveChecksOnStart* 。将参数设置为 `ForceActiveChecksOnStart=1` 将确保在 Zabbix agent 重新启动时立即收集主动检查的监控项数据，具有 *调度* [update interval](/manual/config/items/item/custom_intervals#调度)的监控项除外。否则，agent 重新启动后的第一次数据收集将在随机时间发生，该时间小于监控项更新间隔，以防止资源使用高峰。  通过使用 *Plugins.\<PluginName>.System.ForceActiveChecksOnStart*，也可以仅为特定插件设置此选项（例如，`Plugins.Uptime.System.ForceActiveChecksOnStart=1`）。如果设置，插件级参数将覆盖全局设置。

en-us	 ### Zabbix agent 2 items  - Native support for the [items](/manual/config/items/itemtypes/zabbix_agent) **net.dns** and **net.dns.record** has been added. These items, used with Zabbix agent 2, now support concurrent check processing. On Windows, custom DNS IP addresses are allowed in the `ip` parameter, `timeout` and `count` parameters are no longer ignored.  - *smart.disk.discovery* and *smart.attribute.discovery* [items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#s.m.a.r.t.), supported for S.M.A.R.T. plugin, have been updated and now return {#DISKTYPE} macro value in the lower case.
zh-cn	 ### Zabbix agent 2 监控项  - 添加了对[监控项](/manual/config/items/itemtypes/zabbix_agent) **net.dns** 和 **net.dns.record** 的原生支持。这些监控项与 Zabbix agent 2 一起使用，现在支持并发检查处理。在 Windows 上，`ip` 参数中允许自定义DNS IP地址，`timeout` 和 `count` 参数不再被忽略。 - S.M.A.R.T. 插件支持的 *smart.disk.discovery* 和 *smart.attribute.discovery* [监控项](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#s.m.a.r.t.)已更新，现在以小写形式返回 {#DISKTYPE} 宏值。

en-us	### Zabbix agent 2 plugins  Each Zabbix agent 2 plugin now has a separate [configuration file](/manual/appendix/config/zabbix_agent2_plugins). By default, these files are located in the `./zabbix_agent2.d/plugins.d/` directory. The path is specified in the `Include` parameter of the agent 2 configuration file and can be relative to the [zabbix\_agent2.conf](/manual/appendix/config/zabbix_agent2) or [zabbix\_agent2.win.conf](/manual/appendix/config/zabbix_agent2_win) file location.  
zh-cn	### Web monitoring  The ability to handle compressed content has been added to Zabbix web monitoring. All encoding formats supported by **libcurl** are supported.  

en-us	##### Zabbix agent 2 plugins  Each Zabbix agent 2 plugin now has a separate [configuration file](/manual/appendix/config/zabbix_agent2_plugins). By default, these files are located in the `./zabbix_agent2.d/plugins.d/` directory. The path is specified in the `Include` parameter of the agent 2 configuration file and can be relative to the [zabbix\_agent2.conf](/manual/appendix/config/zabbix_agent2) or [zabbix\_agent2.win.conf](/manual/appendix/config/zabbix_agent2_win) file location.
zh-cn	##### Zabbix agent 2 插件  每个 Zabbix agent 2 插件都有独立的 [配置文件](/manual/appendix/config/zabbix_agent2_plugins)。默认这些文件位于 `./zabbix_agent2.d/plugins.d/` 路径下。也可以由agent 2配置文件的参数 `Include` 来指定。配置文件参见 [zabbix\_agent2.conf](/manual/appendix/config/zabbix_agent2) 或 [zabbix\_agent2.win.conf](/manual/appendix/config/zabbix_agent2_win)。

en-us	 Zabbix agent 2 supports all item keys supported for Zabbix agent on [Unix](/manual/config/items/itemtypes/zabbix_agent) and [Windows](manual/config/items/itemtypes/zabbix_agent/win_keys). This page provides details on the additional item keys, which you can use with Zabbix agent 2 only, grouped by the plugin they belong to.  See also: [Plugins supplied out-of-the-box](/manual/config/items/plugins#plugins_supplied_out-of-the-box)  ::: noteclassic  Parameters without angle brackets are mandatory. Parameters marked with angle brackets **<** **>** are optional. :::
zh-cn	 Zabbix agent 2 支持 Zabbix agent 在 [Unix](/manual/config/items/itemtypes/zabbix_agent) and [Windows](manual/config/items/itemtypes/zabbix_agent/win_keys) 上支持的所有监控项键值。这个页面提供了额外的监控项键值的详细信息，或者你也可以按它们所属的插件分组只使用 Zabbix agent 2。  可以查看: [Plugins supplied out-of-the-box](/manual/config/items/plugins#开箱即用的插件) ::: noteclassic  使用尖括号**<** **>** 标记的参数是可选参数，没有使用尖括号标记的参数是必选参数。 :::