en-us	#### Create script LLD rule  Create a simple data collection using a script LLD rule.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Script example",         "key_": "custom.script.lldrule",         "hostid": "12345",         "type": 21,         "value_type": 4,         "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));",         "parameters": [{             "name": "host",             "value": "{HOST.CONN}"         }],         "timeout": "6s",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```
zh-cn	#### 创建脚本 LLD 规则  使用脚本 LLD 规则创建一个简单的数据集合。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Script example",         "key_": "custom.script.lldrule",         "hostid": "12345",         "type": 21,         "value_type": 4,         "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));",         "parameters": [{             "name": "host",             "value": "{HOST.CONN}"         }],         "timeout": "6s",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```

en-us	#### Create script LLD rule  Create a simple data collection using a script LLD rule.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Script example",         "key_": "custom.script.lldrule",         "hostid": "12345",         "type": 21,         "value_type": 4,         "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));",         "parameters": [             {                 "name": "host",                 "value": "{HOST.CONN}"             }         ],         "timeout": "6s",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```
zh-cn	#### 创建脚本 LLD 规则  使用脚本 LLD 规则创建一个简单的数据集合。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Script example",         "key_": "custom.script.lldrule",         "hostid": "12345",         "type": 21,         "value_type": 4,         "params": "var request = new CurlHttpRequest();\nreturn request.Post(\"https://postman-echo.com/post\", JSON.parse(value));",         "parameters": [{             "name": "host",             "value": "{HOST.CONN}"         }],         "timeout": "6s",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```

en-us	#### Creating a dashboard  Create a dashboard named "My dashboard" with one Problems widget with tags and using two types of sharing (user group and user) on a single dashboard page.  Request:  ```json {     "jsonrpc": "2.0",     "method": "dashboard.create",     "params": {         "name": "My dashboard",         "display_period": 30,         "auto_start": 1,         "pages": [             {                 "widgets": [                     {                         "type": "problems",                         "x": 0,                         "y": 0,                         "width": 12,                         "height": 5,                         "view_mode": 0,                         "fields": [                             {                                 "type": 1,                                 "name": "tags.tag.0",                                 "value": "service"                             },                             {                                 "type": 0,                                 "name": "tags.operator.0",                                 "value": 1                             },                             {                                 "type": 1,                                 "name": "tags.value.0",                                 "value": "zabbix_server"                             }                         ]                     }                 ]             }         ],         "userGroups": [             {                 "usrgrpid": "7",                 "permission": 2             }         ],         "users": [             {                 "userid": "4",                 "permission": 3             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 1 } ```
zh-cn	#### 创建仪表盘  创建一个名为 “My dashboard” 的仪表盘，其中有一个带有标签的问题部件，并使用了两种类型的共享（用户组和用户）。  请求：  ```json {     "jsonrpc": "2.0",     "method": "dashboard.create",     "params": {         "name": "My dashboard",         "display_period": 30,         "auto_start": 1,         "pages": [             {                 "widgets": [                     {                         "type": "problems",                         "x": 0,                         "y": 0,                         "width": 12,                         "height": 5,                         "view_mode": 0,                         "fields": [                             {                                 "type": 1,                                 "name": "tags.tag.0",                                 "value": "service"                             },                             {                                 "type": 0,                                 "name": "tags.operator.0",                                 "value": 1                             },                             {                                 "type": 1,                                 "name": "tags.value.0",                                 "value": "zabbix_server"                             }                         ]                     }                 ]             }         ],         "userGroups": [             {                 "usrgrpid": "7",                 "permission": 2             }         ],         "users": [             {                 "userid": "4",                 "permission": 3             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 1 } ```

en-us	#### Creating a dashboard  It is possible to create a new dashboard in two ways:  -   Click on *Create dashboard*, when viewing all dashboards -   Select *Create new* from the action menu, when viewing a single     dashboard  You will be first asked to enter general dashboard parameters:  ![dashboard\_properties.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_properties.png)  |Parameter|Description| |---------|-----------| |*Owner*|Select system user that will be the dashboard owner.| |*Name*|Enter dashboard name.| |*Default page display period*|Select period for how long a dashboard page is displayed before rotating to the next page in a [slideshow](#creating_a_slideshow).| |*Start slideshow automatically*|Mark this checkbox to run a slideshow automatically one more than one dashboard page exists.|  When you click on *Apply*, an empty dashboard is opened:  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_add.png){width="600"}  To populate the dashboard, you can add widgets and pages.  Click on the *Save changes* button to save the dashboard. If you click on *Cancel*, the dashboard will not be created.
zh-cn	#### 创建仪表盘  有以下两种方式创建一个新的仪表盘：  -   在查看所有仪表盘时，点击*创建仪表盘* -   在查看单个仪表盘时，点击动作菜单的*创建新的*  您首先会被要求输入通用的仪表盘参数：  ![dashboard\_properties.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_properties.png)  |参数|描述| |---------|-----------| |*所有者*|选择成为仪表盘所有者的系统用户。| |*名称*|输入仪表盘名称。| |*默认页面显示时长*|选择仪表盘页面被轮换到[滑动显示](#creating_a_slideshow)下一页前的显示时长。| |*自动开始滑动显示*|当有多个仪表盘页面时，勾选此多选框来自动运行滑动显示。|  当你点击*应用*时，一个空仪表盘会被打开：  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_add.png){width="600"}  您可以给仪表盘添加组件和页面。  点击*保存更改*按钮来保存仪表盘。如果你点击*取消*，仪表盘不会被创建。

en-us	#### Creating a global macro  Create a global macro "{$SNMP\_COMMUNITY}" with value "public".  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.createglobal",     "params":  {         "macro": "{$SNMP_COMMUNITY}",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "6"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个全局宏  创建全局宏 "{$SNMP\_COMMUNITY}"， 值为 "public".  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.createglobal",     "params":  {         "macro": "{$SNMP_COMMUNITY}",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "6"         ]     },     "id": 1 } ```

en-us	#### Creating a graph  Create a graph with two items.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graph.create",     "params": {         "name": "MySQL bandwidth",         "width": 900,         "height": 200,         "gitems": [             {                 "itemid": "22828",                 "color": "00AA00"             },             {                 "itemid": "22829",                 "color": "3333FF"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个图表  创建一个具有两个监控项的图表。  请求：  ```json {     "jsonrpc": "2.0",     "method": "graph.create",     "params": {         "name": "MySQL bandwidth",         "width": 900,         "height": 200,         "gitems": [             {                 "itemid": "22828",                 "color": "00AA00"             },             {                 "itemid": "22829",                 "color": "3333FF"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应： ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652"         ]     },     "id": 1 } ```

en-us	#### Creating a graph prototype  Create a graph prototype with two items.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graphprototype.create",     "params": {         "name": "Disk space usage {#FSNAME}",         "width": 900,         "height": 200,         "gitems": [             {                 "itemid": "22828",                 "color": "00AA00"             },             {                 "itemid": "22829",                 "color": "3333FF"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个图表原型  创建一个有两个项目的图表原型。  请求：  ```json {     "jsonrpc": "2.0",     "method": "graphprototype.create",     "params": {         "name": "Disk space usage {#FSNAME}",         "width": 900,         "height": 200,         "gitems": [             {                 "itemid": "22828",                 "color": "00AA00"             },             {                 "itemid": "22829",                 "color": "3333FF"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652"         ]     },     "id": 1 } ```

en-us	#### Creating a host  Create a host called "Linux server" with an IP interface and tags, add it to a group, link a template to it and set the MAC addresses in the host inventory.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.create",     "params": {         "host": "Linux server",         "interfaces": [             {                 "type": 1,                 "main": 1,                 "useip": 1,                 "ip": "192.168.3.1",                 "dns": "",                 "port": "10050"             }         ],         "groups": [             {                 "groupid": "50"             }         ],         "tags": [             {                 "tag": "Host name",                 "value": "Linux server"             }         ],         "templates": [             {                 "templateid": "20045"             }         ],         "macros": [             {                 "macro": "{$USER_ID}",                 "value": "123321"             },             {                 "macro": "{$USER_LOCATION}",                 "value": "0:0:0",                 "description": "latitude, longitude and altitude coordinates"             }         ],         "inventory_mode": 0,         "inventory": {             "macaddress_a": "01234",             "macaddress_b": "56768"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "107819"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个主机  创建一个具有IP接口和标签的“Linux Server”主机，将其添加到主机组中，链接一个模板并且把MAC地址设置到主机资产清单里。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.create",     "params": {         "host": "Linux server",         "interfaces": [             {                 "type": 1,                 "main": 1,                 "useip": 1,                 "ip": "192.168.3.1",                 "dns": "",                 "port": "10050"             }         ],         "groups": [             {                 "groupid": "50"             }         ],         "tags": [             {                 "tag": "Host name",                 "value": "Linux server"             }         ],         "templates": [             {                 "templateid": "20045"             }         ],         "macros": [             {                 "macro": "{$USER_ID}",                 "value": "123321"             },             {                 "macro": "{$USER_LOCATION}",                 "value": "0:0:0",                 "description": "latitude, longitude and altitude coordinates"             }         ],         "inventory_mode": 0,         "inventory": {             "macaddress_a": "01234",             "macaddress_b": "56768"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "107819"         ]     },     "id": 1 } ```

en-us	#### Creating a host group  Create a host group called "Linux servers".  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.create",     "params": {         "name": "Linux servers"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "107819"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个主机组  创建名为"Linux servers"的主机组。  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.create",     "params": {         "name": "Linux servers"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "107819"         ]     },     "id": 1 } ```

en-us	#### Creating a host group  ::: noteimportant Only Super Admin users can create host groups. :::  To create a host group in Zabbix frontend, do the following:  -   Go to: *Configuration → Host groups* -   Click on *Create Group* in the upper right corner of the screen -   Enter parameters of the group in the form  ![](../../../../assets/en/manual/config/host_group.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Group name*|Enter a unique host group name.<br>To create a nested host group, use the '/' forward slash separator, for example `Europe/Latvia/Riga/Zabbix servers`. You can create this group even if none of the three parent host groups (`Europe/Latvia/Riga`) exist. In this case creating these parent host groups is up to the user; they will not be created automatically.<br>Leading and trailing slashes, several slashes in a row are not allowed. Escaping of '/' is not supported.<br>Nested representation of host groups is supported since Zabbix 3.2.0.| |*Apply permissions and tag filters to all subgroups*|Checkbox is available to Super Admin users only and only when editing an existing host group.<br>Mark this checkbox and click on *Update* to apply the same level of permissions/tag filters to all nested host groups. For user groups that may have had differing [permissions](/manual/config/users_and_usergroups/usergroup#configuration) assigned to nested host groups, the permission level of the parent host group will be enforced on the nested groups.<br>This is a one-time option that is not saved in the database.<br>This option is supported since Zabbix 3.4.0.|  **Permissions to nested host groups**  -   When creating a child host group to an existing parent host group,     [user group](/manual/config/users_and_usergroups/usergroup)     permissions to the child are inherited from the parent (for example,     when creating `Riga/Zabbix servers` if `Riga` already exists) -   When creating a parent host group to an existing child host group,     no permissions to the parent are set (for example, when creating     `Riga` if `Riga/Zabbix servers` already exists)
zh-cn	#### 创建主机组  ::: noteimportant 只有 Super Admin users（超级管理员用户） 可以创建主机组。 :::  要在 Zabbix 前端创建主机组，请执行以下操作：  -    点击： *Configuration（配置） → Host groups（主机群组）* -    单机屏幕右上角 *Create Group（创建主机群组）*  -    在表单中输入主机群组的相关参数  ![](../../../../assets/en/manual/config/host_group.png)  所有标有红色星号的字段为必填项。  |参数|描述| |---------|-----------| |*Group name（群组名）*|输入唯一的主机组名称。<br>要创建嵌套主机组，请使用 '/' 正斜杠分隔符，例如 `Europe/Latvia/Riga/Zabbix servers`。 即使三个父主机组  (`Europe/Latvia/Riga`)  都不存在，也可以创建此组。在这种情况下，是否创建这些父主机群组取决于用户；它们不会自动创建。<br>不允许字符串最前和最后出现斜杠、不允许连续出现多个斜杠。不支持转义 '/' 。<br>自 Zabbix 3.2.0 起支持主机组的嵌套模式。| |*Apply permissions and tag filters to all subgroups（应用权限和标签过滤器到所有子组）*|复选框仅对超级管理员用户可用且仅在编辑已存在的主机组时可用。<br>标记此复选框并单击 *Update（更新）* 以将相同级别的权限/标签过滤器应用于所有嵌套主机组。对于可能为嵌套主机组分配了不同 [权限](/manual/config/users_and_usergroups/usergroup#configuration) 的用户组，将对嵌套组强制执行父主机组的权限级别。<br>这是不保存在数据库中的一次性选项。<br>自 Zabbix 3.4.0 起支持此选项。|  **嵌套主机组的权限**  -   为已存在的父主机组创建子主机组时，子主机组的 [用户组](/manual/config/users_and_usergroups/usergroup)权限从父主机继承（例如，在父主机群组 `Riga` 已经存在的情况下创建子主机群组 `Riga/Zabbix servers`）  -   为已存在的子主机组创建父主机组时，不会设置父主机组的权限（例如，在子主机群组 `Riga/Zabbix servers` 已经存在的情况下创建父主机群组 `Riga` ）

en-us	#### Creating a host inventory item  Create a Zabbix agent item to populate the host's "OS" inventory field.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "uname",         "key_": "system.uname",         "hostid": "30021",         "type": 0,         "interfaceid": "30007",         "value_type": 1,         "delay": "10s",         "inventory_link": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 1 } ```
zh-cn	#### 创建主机资产监控项  创建 Zabbix agent 监控项，用于增添主机的 “OS” 资产字段。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "uname",         "key_": "system.uname",         "hostid": "30021",         "type": 0,         "interfaceid": "30007",         "value_type": 1,         "delay": "10s",         "inventory_link": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 1 } ```

en-us	#### Creating a host inventory item  Create a Zabbix agent item to populate the host's "OS" inventory field.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "uname",         "key_": "system.uname",         "hostid": "30021",         "type": 0,         "interfaceid": "30007",         "value_type": 1,         "delay": "10s",         "inventory_link": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 1 } ```
zh-cn	#### 创建主机资产监控项  创建 Zabbix agent 监控项，用于增添主机的 “OS” 资产字段。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "uname",         "key_": "system.uname",         "hostid": "30021",         "type": 0,         "interfaceid": "30007",         "value_type": 1,         "delay": "10s",         "inventory_link": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 1 } ```

en-us	#### Creating a host macro  Create a host macro "{$SNMP\_COMMUNITY}" with the value "public" on host "10198".  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.create",     "params": {         "hostid": "10198",         "macro": "{$SNMP_COMMUNITY}",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "11"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个主机宏  为主机"10198"创建主机宏 "{$SNMP\_COMMUNITY}" ，值为 "public" .  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.create",     "params": {         "hostid": "10198",         "macro": "{$SNMP_COMMUNITY}",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "11"         ]     },     "id": 1 } ```

en-us	#### Creating a host prototype  Create a host prototype "{\#VM.NAME}" on LLD rule "23542" with a group prototype "{\#HV.NAME}", tag pair "Datacenter": "{\#DATACENTER.NAME}" and custom SNMPv2 interface 127.0.0.1:161 with community {$SNMP\_COMMUNITY}. Link it to host group "2".  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.create",     "params": {         "host": "{#VM.NAME}",         "ruleid": "23542",         "custom_interfaces": "1",         "groupLinks": [             {                 "groupid": "2"             }         ],         "groupPrototypes": [             {                 "name": "{#HV.NAME}"             }         ],         "tags": [             {                 "tag": "Datacenter",                 "value": "{#DATACENTER.NAME}"             }         ],         "interfaces": [             {                 "main": "1",                 "type": "2",                 "useip": "1",                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": "2",                     "bulk": "1",                     "community": "{$SNMP_COMMUNITY}"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10103"         ]     },     "id": 1 } ```
zh-cn	####创建主机原型  在LLD规则“23542”上使用组原型"{\#HV.NAME}"、标签对"Datacenter": "{\#DATACENTER.NAME}"和自定义团体字为{$SNMP\_COMMUNITY}的SNMPv2接口 127.0.0.1:161,创建主机原型"{\#VM.NAME}"并将其链接到主机组"2"。  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.create",     "params": {         "host": "{#VM.NAME}",         "ruleid": "23542",         "custom_interfaces": "1",         "groupLinks": [             {                 "groupid": "2"             }         ],         "groupPrototypes": [             {                 "name": "{#HV.NAME}"             }         ],         "tags": [             {                 "tag": "Datacenter",                 "value": "{#DATACENTER.NAME}"             }         ],         "interfaces": [             {                 "main": "1",                 "type": "2",                 "useip": "1",                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": "2",                     "bulk": "1",                     "community": "{$SNMP_COMMUNITY}"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10103"         ]     },     "id": 1 } ```

en-us	#### Creating a host with SNMP interface  Create a host called "SNMP host" with an SNMPv3 interface with details.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.create",     "params": {         "host": "SNMP host",         "interfaces": [             {                 "type": 2,                 "main": 1,                 "useip": 1,                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": 3,                     "bulk": 0,                     "securityname": "mysecurityname",                     "contextname": "",                     "securitylevel": 1                 }             }         ],         "groups": [             {                 "groupid": "4"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10658"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个具有SNMP接口的主机  创建一个名为“SNMP host”的主机，并创建SNMPv3接口。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.create",     "params": {         "host": "SNMP host",         "interfaces": [             {                 "type": 2,                 "main": 1,                 "useip": 1,                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": 3,                     "bulk": 0,                     "securityname": "mysecurityname",                     "contextname": "",                     "securitylevel": 1                 }             }         ],         "groups": [             {                 "groupid": "4"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10658"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with macro paths  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "LLD rule with LLD macro paths",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.path.1"             },             {                 "lld_macro": "{#MACRO2}",                 "path": "$.path.2"             }         ]     },     "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": "LLD rule with LLD macro paths",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.path.1"             },             {                 "lld_macro": "{#MACRO2}",                 "path": "$.path.2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with macro paths  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "LLD rule with LLD macro paths",         "key_": "lld",         "hostid": "10116",         "type": 0,         "interfaceid": "13",         "delay": "30s",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.path.1"             },             {                 "lld_macro": "{#MACRO2}",                 "path": "$.path.2"             }         ]     },     "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": "LLD rule with LLD macro paths",         "key_": "lld",         "hostid": "10116",         "type": "0",         "interfaceid": "13",         "delay": "30s",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.path.1"             },             {                 "lld_macro": "{#MACRO2}",                 "path": "$.path.2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with overrides  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discover database host",         "key_": "lld.with.overrides",         "hostid": "10001",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "overrides": [             {                 "name": "Discover MySQL host",                 "step": "1",                 "stop": "1",                 "filter": {                     "evaltype": "2",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mysqld\\.service$"                         },                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mariadb\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10170"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "MySQL"                             }                         ]                     }                 ]             },             {                 "name": "Discover PostgreSQL host",                 "step": "2",                 "stop": "1",                 "filter": {                     "evaltype": "0",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^postgresql\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10263"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "PostgreSQL"                             }                         ]                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "30980"         ]     },     "id": 1 } ```
zh-cn	#### 创建具有覆盖的 LLD 规则  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discover database host",         "key_": "lld.with.overrides",         "hostid": "10001",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "overrides": [             {                 "name": "Discover MySQL host",                 "step": "1",                 "stop": "1",                 "filter": {                     "evaltype": "2",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mysqld\\.service$"                         },                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mariadb\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10170"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "MySQL"                             }                         ]                     }                 ]             },             {                 "name": "Discover PostgreSQL host",                 "step": "2",                 "stop": "1",                 "filter": {                     "evaltype": "0",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^postgresql\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10263"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "PostgreSQL"                             }                         ]                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "30980"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with overrides  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discover database host",         "key_": "lld.with.overrides",         "hostid": "10001",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "overrides": [             {                 "name": "Discover MySQL host",                 "step": "1",                 "stop": "1",                 "filter": {                     "evaltype": "2",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mysqld\\.service$"                         },                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mariadb\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10170"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "MySQL"                             }                         ]                     }                 ]             },             {                 "name": "Discover PostgreSQL host",                 "step": "2",                 "stop": "1",                 "filter": {                     "evaltype": "0",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^postgresql\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10263"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "PostgreSQL"                             }                         ]                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "30980"         ]     },     "id": 1 } ```
zh-cn	#### 创建具有覆盖的 LLD 规则  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discover database host",         "key_": "lld.with.overrides",         "hostid": "10001",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "overrides": [             {                 "name": "Discover MySQL host",                 "step": "1",                 "stop": "1",                 "filter": {                     "evaltype": "2",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mysqld\\.service$"                         },                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^mariadb\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10170"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "MySQL"                             }                         ]                     }                 ]             },             {                 "name": "Discover PostgreSQL host",                 "step": "2",                 "stop": "1",                 "filter": {                     "evaltype": "0",                     "conditions": [                         {                             "macro": "{#UNIT.NAME}",                             "operator": "8",                             "value": "^postgresql\\.service$"                         }                     ]                 },                 "operations": [                     {                         "operationobject": "3",                         "operator": "2",                         "value": "Database host",                         "opstatus": {                             "status": "0"                         },                         "optemplate": [                             {                                 "templateid": "10263"                             }                         ],                         "optag": [                             {                                 "tag": "Database",                                 "value": "PostgreSQL"                             }                         ]                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "30980"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with preprocessing  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discovery rule with preprocessing",         "key_": "lld.with.preprocessing",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "preprocessing": [             {                 "type": "20",                 "params": "20",                 "error_handler": "0",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 使用LLD 规则创建预处理   请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discovery rule with preprocessing",         "key_": "lld.with.preprocessing",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "preprocessing": [             {                 "type": "20",                 "params": "20",                 "error_handler": "0",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Creating a LLD rule with preprocessing  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discovery rule with preprocessing",         "key_": "lld.with.preprocessing",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "preprocessing": [             {                 "type": 20,                 "params": "20",                 "error_handler": 0,                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 使用LLD 规则创建预处理   请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Discovery rule with preprocessing",         "key_": "lld.with.preprocessing",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "interfaceid": "1155",         "preprocessing": [             {                 "type": "20",                 "params": "20",                 "error_handler": "0",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Creating a maintenance  Create a maintenance with data collection for host group "2" with problem tags **<service:mysqld>** and **error**. It must be active from 22.01.2013 till 22.01.2014, come in effect each Sunday at 18:00 and last for one hour.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "maintenance.create",     "params": {         "name": "Sunday maintenance",         "active_since": 1358844540,         "active_till": 1390466940,         "tags_evaltype": 0,         "groupids": [             "2"         ],         "timeperiods": [             {                 "timeperiod_type": 3,                 "every": 1,                 "dayofweek": 64,                 "start_time": 64800,                 "period": 3600             }         ],         "tags": [             {                 "tag": "service",                 "operator": "0",                 "value": "mysqld"             },             {                 "tag": "error",                 "operator": "2",                 "value": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```  
zh-cn	#### Creating a maintenance 创建一个维护模式  Create a maintenance with data collection for host group "2". It must be active from 22.01.2013 till 22.01.2014, come in effect each Sunday at 18:00 and last for one hour. 为主机组"2"以with data collection(持续收集数据)模式创建一个维护模式。该维护模式生效于22.01.2013 到 22.01.2014，每周六的18:00生效，并持续1个小时。  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "maintenance.create",     "params": {         "name": "Sunday maintenance",         "active_since": 1358844540,         "active_till": 1390466940,         "groupids": [             "2"         ],         "timeperiods": [             {                 "timeperiod_type": 3,                 "every": 1,                 "dayofweek": 64,                 "start_time": 64800,                 "period": 3600             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```  

en-us	#### Creating a maintenance  Create a maintenance with data collection for host group with ID "2" and with problem tags **service:mysqld** and **error**. It must be active from 22.01.2013 till 22.01.2014, come in effect each Sunday at 18:00 and last for one hour.  Request:  ```json {     "jsonrpc": "2.0",     "method": "maintenance.create",     "params": {         "name": "Sunday maintenance",         "active_since": 1358844540,         "active_till": 1390466940,         "tags_evaltype": 0,         "groups": [             {"groupid": "2"}         ],         "timeperiods": [             {                 "period": 3600,                 "timeperiod_type": 3,                 "start_time": 64800,                 "every": 1,                 "dayofweek": 64             }         ],         "tags": [             {                 "tag": "service",                 "operator": "0",                 "value": "mysqld"             },             {                 "tag": "error",                 "operator": "2",                 "value": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```
zh-cn	#### 创建维护模式  为 ID 为“2”的主机组创建问题标签为 **service:mysqld** 和 **error** 的数据收集维护模式。它必须从 22.01.2013 到 22.01.2014 有效，每周日 18:00 生效，持续一小时。  请求:  ```json {  · "jsonrpc": "2.0",  · "method": "maintenance.create",  · "params": {  · "name": "Sunday maintenance",  · "active_since": 1358844540,  · "active_till": 1390466940,  · "tags_evaltype": 0,  · "groups": [  · {"groupid": "2"}  · ],  · "timeperiods": [  · {  · "period": 3600,  · "timeperiod_type": 3,  · "start_time": 64800,  · "every": 1,  · "dayofweek": 64  · }  · ],  · "tags": [  · {  · "tag": "service",  · "operator": "0",  · "value": "mysqld"  · },  · {  · "tag": "error",  · "operator": "2",  · "value": ""  · }  · ]  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ```json {  · "jsonrpc": "2.0",  · "result": {  · "maintenanceids": [  · "3"  · ]  · },  · "id": 1 } ```

en-us	#### Creating a map  To create a map, do the following:  -   Go to *Monitoring → Maps* -   Go to the view with all maps -   Click on *Create map*  You can also use the *Clone* and *Full clone* buttons in the configuration form of an existing map to create a new map. Clicking on *Clone* will retain general layout attributes of the original map, but no elements. *Full clone* will retain both the general layout attributes and all elements of the original map.  The **Map** tab contains general map attributes:  ![](../../../../../assets/en/manual/config/visualization/map_config.png)  All mandatory input fields are marked with a red asterisk.  General map attributes:  |Parameter|Description| |---------|-----------| |*Owner*|Name of map owner.| |*Name*|Unique map name.| |*Width*|Map width in pixels.| |*Height*|Map height in pixels.| |*Background image*|Use background image:<br>**No image** - no background image (white background)<br>**Image** - selected image to be used as a background image. No scaling is performed. You may use a geographical map or any other image to enhance your map.| |*Automatic icon mapping*|You can set to use an automatic icon mapping, configured in *Administration → General → Icon mapping*. Icon mapping allows mapping certain icons against certain host inventory fields.| |*Icon highlighting*|If you check this box, map elements will receive highlighting.<br>Elements with an active trigger will receive a round background, in the same color as the highest severity trigger. Moreover, a thick green line will be displayed around the circle, if all problems are acknowledged.<br>Elements with "disabled" or "in maintenance" status will get a square background, gray and orange respectively.<br>See also: [Viewing maps](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)| |*Mark elements on trigger status change*|A recent change of trigger status (recent problem or resolution) will be highlighted with markers (inward-pointing red triangles) on the three sides of the element icon that are free of the label. Markers are displayed for 30 minutes.| |*Display problems*|Select how problems are displayed with a map element:<br>**Expand single problem** - if there is only one problem, the problem name is displayed. Otherwise, the total number of problems is displayed.<br>**Number of problems** - the total number of problems is displayed<br>**Number of problems and expand most critical one** - the name of the most critical problem and the total number of problems is displayed.<br>'Most critical' is determined based on problem severity and, if equal, problem event ID (higher ID or later problem displayed first). For a *trigger map element* it is based on problem severity and if equal, trigger position in the trigger list. In case of multiple problems of the same trigger, the most recent one will be displayed.| |*Advanced labels*|If you check this box you will be able to define separate label types for separate element types.| |*Map element label type*|Label type used for map elements:<br>**Label** - map element label<br>**IP address** - IP address<br>**Element name** - element name (for example, host name)<br>**Status only** - status only (OK or PROBLEM)<br>**Nothing** - no labels are displayed| |*Map element label location*|Label location in relation to the map element:<br>**Bottom** - beneath the map element<br>**Left** - to the left<br>**Right** - to the right<br>**Top** - above the map element| |*Problem display*|Display problem count as:<br>**All** - full problem count will be displayed<br>**Separated** - unacknowledged problem count will be displayed separated as a number of the total problem count<br>**Unacknowledged only** - only the unacknowledged problem count will be displayed| |*Minimum trigger severity*|Problems below the selected minimum severity level will not be displayed on the map.<br>For example, with *Warning* selected, changes with *Information* and *Not classified* level triggers will not be reflected in the map.<br>This parameter is supported starting with Zabbix 2.2.| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*URLs*|URLs for each element type can be defined (with a label). These will be displayed as links when a user clicks on the element in the map viewing mode.<br>Macros can be used in map URL names and values. For a full list, see [supported macros](/manual/appendix/macros/supported_by_location) and search for 'map URL names and values'.|
zh-cn	#### 创建地图  要创建地图，请执行以下操作：  - 转到*监控 → 地图* - 转到所有地图的视图 - 点击*创建地图*  您也可以使用 *Clone* 和 *Full clone* 按钮基于现有地图的配置形式以创建新地图。点击*克隆*将保留原始地图的总体布局属性，但没有元素。 *完整克隆*将保留常规布局属性以及原始地图的所有元素。  **Map** 选项卡包含一般地图属性：  ![](../../../../../assets/en/manual/config/visualization/map_config.png)  所有标有红色星号的是必填字段。  通用地图属性：  |参数|说明| |---------|------------| |*所有者*|地图所有者的姓名。| |*名称*|唯一的地图名称。| |*宽度*|以像素为单位的地图宽度。| |*高度*|以像素为单位的地图高度。| |*背景图片*|使用背景图片：<br>**无图片** - 无背景图片（白色背景）<br>**图片** - 选择的图片用作背景图片。不执行缩放。您可以使用地理地图或任何其他图像来增强您的地图。| |*自动图标映射*|您可以设置使用自动图标映射，在 *Administration → General → Icon mapping* 中配置。图标映射允许将某些图标映射到某些主机清单字段。 |*图标突出显示*|如果您选中此框，地图元素将突出显示。<br>具有活动触发器的元素将收到圆形背景，与最严重的触发器颜色相同。此外，如果确认所有问题，圆圈周围会显示一条粗绿线。<br>“已禁用”或“维护中”状态的元素将分别获得方形背景、灰色和橙色。<br>另请参阅： [查看地图](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)| |*在触发状态更改时标记元素*|最近触发状态的更改（最近的问题或已解决的问题）将在元素图标的三个方向用没有标签标记（向内的红色三角形）突出显示。标记显示 30 分钟。| |*显示问题*|使用地图元素选择问题的显示方式：<br>**展开单个问题** - 如果只有一个问题，则显示问题名称。否则，显示问题总数。<br>**问题数** - 显示问题总数<br>**问题数并展开最关键的一个** - 最关键的名称问题并显示问题总数。<br>“最关键”是根据问题严重性确定的，如果相等，则根据问题事件 ID（ID 较高或最新的问题首先显示）确定。对于*触发地图元素*，它基于问题严重性，如果相等，则触发列表中的触发位置。如果同一个触发器出现多个问题，将显示最近的一个。| |*高级标签*|如果您选中此框，您将能够为单独的元素类型定义单独的标签类型。| |*地图元素标签类型*|用于地图元素的标签类型：<br>**标签** - 地图元素标签<br>**IP地址** - IP地址<br>**元素名称** - 元素名称（例如，主机名）<br>**仅状态** - 仅状态（OK 或 PROBLEM）<br>**Nothing** - 不显示标签| |*地图元素标签位置*|相对于地图元素的标签位置：<br>**底部** - 地图元素下方<br>**左** - 左侧<br>**右** - 右侧<br>**Top** - 地图元素上方| |*问题显示*|将问题计数显示为：<br>**全部** - 将显示完整的问题计数<br>**分隔** - 未确认的问题计数将单独显示为总问题计数的数字<br>**Unacknowledged only** - 只显示未确认的问题计数| |*最低触发严重性*|低于所选最低严重性级别的问题将不会显示在地图上。<br>例如，选择*警告*，*信息*和*未分类*级别触发器的更改将不会反映在地图中。<br>从 Zabbix 2.2 开始支持此参数。| |*显示抑制的问题*|标记复选框以显示由于主机维护而被抑制（未显示）的问题。| |*URLs*|可以定义每种元素类型的 URL（带有标签）。当用户在地图查看模式下单击元素时，这些将显示为链接。<br>宏可用于地图 URL 名称和值。有关完整列表，请参阅 [支持的宏](/manual/appendix/macros/supported_by_location) 并搜索“映射 URL 名称和值”。|

en-us	#### Creating an e-mail media type  Create a new e-mail media type with a custom SMTP port and message templates.  Request:  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": "0",         "name": "E-mail",         "smtp_server": "mail.example.com",         "smtp_helo": "example.com",         "smtp_email": "zabbix@example.com",         "smtp_port": "587",         "content_type": "1",         "message_templates": [             {                 "eventsource": "0",                 "recovery": "0",                 "subject": "Problem: {EVENT.NAME}",                 "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" started at {EVENT.TIME}."             },             {                 "eventsource": "0",                 "recovery": "1",                 "subject": "Resolved in {EVENT.DURATION}: {EVENT.NAME}",                 "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}."             },             {                 "eventsource": "0",                 "recovery": "2",                 "subject": "Updated problem in {EVENT.AGE}: {EVENT.NAME}",                 "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}."             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "7"         ]     },     "id": 1 } ```
zh-cn	#### 创建电子邮件媒介类型  使用自定义 SMTP 端口和消息模板创建新的电子邮件媒介类型。  请求：  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": "0",         "name": "E-mail",         "smtp_server": "mail.example.com",         "smtp_helo": "example.com",         "smtp_email": "zabbix@example.com",         "smtp_port": "587",         "content_type": "1",         "message_templates": [             {                 "eventsource": "0",                 "recovery": "0",                 "subject": "Problem: {EVENT.NAME}",                 "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" started at {EVENT.TIME}."             },             {                 "eventsource": "0",                 "recovery": "1",                 "subject": "Resolved in {EVENT.DURATION}: {EVENT.NAME}",                 "message": "Problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}."             },             {                 "eventsource": "0",                 "recovery": "2",                 "subject": "Updated problem in {EVENT.AGE}: {EVENT.NAME}",                 "message": "{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem \"{EVENT.NAME}\" on host \"{HOST.NAME}\" at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}."             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "7"         ]     },     "id": 1 } ```

en-us	#### Creating a new global regular expression.  Request:  ```json {     "jsonrpc": "2.0",     "method": "regexp.create",     "params": {       "name": "Storage devices for SNMP discovery",       "test_string": "/boot",       "expressions": [         {           "expression": "^(Physical memory|Virtual memory|Memory buffers|Cached memory|Swap space)$",           "expression_type": "4",           "case_sensitive": "1"         }       ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "16"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个新的全局正则表达式  请求：  ```json {     "jsonrpc": "2.0",     "method": "regexp.create",     "params": {       "name": "Storage devices for SNMP discovery",       "test_string": "/boot",       "expressions": [         {           "expression": "^(Physical memory|Virtual memory|Memory buffers|Cached memory|Swap space)$",           "expression_type": "4",           "case_sensitive": "1"         }       ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "16"         ]     },     "id": 1 } ```

en-us	#### Creating a new item  Let's create a new [item](/manual/api/reference/item/object) on "Zabbix server" using the data we've obtained from the previous `host.get` request. This can be done by using the [item.create](/manual/api/reference/item/create) method:  ```json {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Free disk space on /home/joe/",         "key_": "vfs.fs.size[/home/joe/,free]",         "hostid": "10084",         "type": 0,         "value_type": 3,         "interfaceid": "1",         "delay": 30     },     "auth": "0424bd59b807674191e7d77572075f33",     "id": 3 } ```  A successful response will contain the ID of the newly created item, which can be used to reference the item in the following requests:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 3 } ```  ::: notetip The `item.create` method as well as other create methods can also accept arrays of objects and create multiple items with one API call. :::
zh-cn	#### 创建新监控项  让我们使用从上一个请求 `host.get` 中获得的数据，在主机 “Zabbix server” 上创建一个新  [监控项](/manual/api/reference/item/object) 。这可以通过使用 [item.create](/manual/api/reference/item/create) 方法完成：  ``` {.json} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Free disk space on /home/joe/",         "key_": "vfs.fs.size[/home/joe/,free]",         "hostid": "10084",         "type": 0,         "value_type": 3,         "interfaceid": "1",         "delay": 30     },     "auth": "0424bd59b807674191e7d77572075f33",     "id": 3 } ```  成功的响应将包含新创建监控项的ID，可用于在以后请求中引用该监控项：  ``` {.json} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "24759"         ]     },     "id": 3 } ```  ::: notetip `item.create`方法和其他的 create 方法也可以接受对象数组并通过一次 API 调用创建多个监控项。 :::

en-us	#### Creating an item prototype with preprocessing  Create an item using change per second and a custom multiplier as a second step.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {         "name": "Incoming network traffic on {#IFNAME}",         "key_": "net.if.in[{#IFNAME}]",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "units": "bps",         "interfaceid": "1155",         "preprocessing": [             {                 "type": "10",                 "params": "",                 "error_handler": "0",                 "error_handler_params": ""             },             {                 "type": "1",                 "params": "8",                 "error_handler": "2",                 "error_handler_params": "10"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 创建监控项原型预处理  先创建一个监控项，第二步在预处理中使用每秒更改和自定义乘数。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "name": "Incoming network traffic on {#IFNAME}",  · "key_": "net.if.in[{#IFNAME}]",  · "hostid": "10001",  · "ruleid": "27665",  · "type": 0,  · "value_type": 3,  · "delay": "60s",  · "units": "bps",  · "interfaceid": "1155",  · "preprocessing": [  · {  · "type": "10",  · "params": "",  · "error_handler": "0",  · "error_handler_params": ""  · },  · {  · "type": "1",  · "params": "8",  · "error_handler": "2",  · "error_handler_params": "10"  · }  · ]  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44211"  · ]  · },  · "id": 1 } ```

en-us	#### Creating an item prototype with preprocessing  Create an item using change per second and a custom multiplier as a second step.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {         "name": "Incoming network traffic on {#IFNAME}",         "key_": "net.if.in[{#IFNAME}]",         "hostid": "10001",         "ruleid": "27665",         "type": 0,         "value_type": 3,         "delay": "60s",         "units": "bps",         "interfaceid": "1155",         "preprocessing": [             {                 "type": 10,                 "params": "",                 "error_handler": 0,                 "error_handler_params": ""             },             {                 "type": 1,                 "params": "8",                 "error_handler": 2,                 "error_handler_params": "10"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 创建监控项原型预处理  先创建一个监控项，第二步在预处理中使用每秒更改和自定义乘数。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "name": "Incoming network traffic on {#IFNAME}",  · "key_": "net.if.in[{#IFNAME}]",  · "hostid": "10001",  · "ruleid": "27665",  · "type": 0,  · "value_type": 3,  · "delay": "60s",  · "units": "bps",  · "interfaceid": "1155",  · "preprocessing": [  · {  · "type": "10",  · "params": "",  · "error_handler": "0",  · "error_handler_params": ""  · },  · {  · "type": "1",  · "params": "8",  · "error_handler": "2",  · "error_handler_params": "10"  · }  · ]  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44211"  · ]  · },  · "id": 1 } ```

en-us	#### Creating an item with preprocessing  Create an item using custom multiplier.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Device uptime",         "key_": "sysUpTime",         "hostid": "11312",         "type": 4,         "snmp_oid": "SNMPv2-MIB::sysUpTime.0",         "value_type": 1,         "delay": "60s",         "units": "uptime",         "interfaceid": "1156",         "preprocessing": [             {                 "type": "1",                 "params": "0.01",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44210"         ]     },     "id": 1 } ```
zh-cn	#### 创建预处理监控项  创建自定义乘数监控项。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Device uptime",         "key_": "sysUpTime",         "hostid": "11312",         "type": 4,         "snmp_oid": "SNMPv2-MIB::sysUpTime.0",         "value_type": 1,         "delay": "60s",         "units": "uptime",         "interfaceid": "1156",         "preprocessing": [             {                 "type": "1",                 "params": "0.01",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44210"         ]     },     "id": 1 } ```

en-us	#### Creating an item with preprocessing  Create an item using custom multiplier.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Device uptime",         "key_": "sysUpTime",         "hostid": "11312",         "type": 4,         "snmp_oid": "SNMPv2-MIB::sysUpTime.0",         "value_type": 1,         "delay": "60s",         "units": "uptime",         "interfaceid": "1156",         "preprocessing": [             {                 "type": 1,                 "params": "0.01",                 "error_handler": 1,                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44210"         ]     },     "id": 1 } ```
zh-cn	#### 创建预处理监控项  创建自定义乘数监控项。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "name": "Device uptime",         "key_": "sysUpTime",         "hostid": "11312",         "type": 4,         "snmp_oid": "SNMPv2-MIB::sysUpTime.0",         "value_type": 1,         "delay": "60s",         "units": "uptime",         "interfaceid": "1156",         "preprocessing": [             {                 "type": "1",                 "params": "0.01",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44210"         ]     },     "id": 1 } ```

en-us	#### Creating an LLD rule  Create a Zabbix agent LLD rule to discover mounted file systems. Discovered items will be updated every 30 seconds.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Mounted filesystem discovery",         "key_": "vfs.fs.discovery",         "hostid": "10197",         "type": "0",         "interfaceid": "112",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```
zh-cn	#### 创建 LLD 规则  创建 Zabbix agent LLD 规则以发现挂载的文件系统。 发现的监控项将每 30 秒更新一次。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Mounted filesystem discovery",         "key_": "vfs.fs.discovery",         "hostid": "10197",         "type": "0",         "interfaceid": "112",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Creating an LLD rule  Create a Zabbix agent LLD rule to discover mounted file systems. Discovered items will be updated every 30 seconds.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Mounted filesystem discovery",         "key_": "vfs.fs.discovery",         "hostid": "10197",         "type": 0,         "interfaceid": "112",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```
zh-cn	#### 创建 LLD 规则  创建 Zabbix agent LLD 规则以发现挂载的文件系统。 发现的监控项将每 30 秒更新一次。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.create",     "params": {         "name": "Mounted filesystem discovery",         "key_": "vfs.fs.discovery",         "hostid": "10197",         "type": "0",         "interfaceid": "112",         "delay": "30s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27665"         ]     },     "id": 1 } ```

en-us	#### Creating an SLA  Instruct to create an SLA entry for: * tracking uptime for SQL-engine related services; * custom schedule of all weekdays excluding last hour on Saturday; * an effective date of the last day of the year 2022; * with 1 hour and 15 minutes long planned downtime starting at midnight on the 4th of July; * SLA weekly report calculation will be on; * the minimum acceptable SLO will be 99.9995%.
zh-cn	#### 创建SLA  指示为以下对象创建 SLA 条目： * 跟踪 SQL 引擎相关服务的正常运行时间； * 除周六最后一小时外的所有工作日的自定义时间表； * 生效日期为 2022 年最后一天；¶ * 从 7 月 4 日午夜开始，计划停机时间为 1 小时 15 分钟； * SLA 周报计算将开启； * 可接受的最低 SLO 为 99.9995%。

en-us	#### Creating a role  Create a role with type "User" and denied access to two UI elements.  Request:  ```json {     "jsonrpc": "2.0",     "method": "role.create",     "params": {         "name": "Operator",         "type": "1",         "rules": {             "ui": [                 {                     "name": "monitoring.hosts",                     "status": "0"                 },                 {                     "name": "monitoring.maps",                     "status": "0"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "roleids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 创建角色  创建一个类型为“User”的角色 ，并禁止其访问两个UI元素。  请求：  ```json {     "jsonrpc": "2.0",     "method": "role.create",     "params": {         "name": "Operator",         "type": "1",         "rules": {             "ui": [                 {                     "name": "monitoring.hosts",                     "status": "0"                 },                 {                     "name": "monitoring.maps",                     "status": "0"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "roleids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Creating a scheduled report  Create a weekly report that will be prepared for the previous week every Monday-Friday at 12:00 from 2021-04-01 to 2021-08-31.  Request:  ```json {     "jsonrpc": "2.0",     "method": "report.create",     "params": {         "userid": "1",         "name": "Weekly report",         "dashboardid": "1",         "period": "1",         "cycle": "1",         "start_time": "43200",         "weekdays": "31",         "active_since": "2021-04-01",         "active_till": "2021-08-31",         "subject": "Weekly report",         "message": "Report accompanying text",         "status": "1",         "description": "Report description",         "users": [             {                 "userid": "1",                 "access_userid": "1",                 "exclude": "0"             },             {                 "userid": "2",                 "access_userid": "0",                 "exclude": "1"             }         ],         "user_groups": [             {                 "usrgrpid": "7",                 "access_userid": "0"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "reportids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 创建计划报告  创建一个周报，从2021-04-01到2021-08-31，每周一到周五12:00，发送上一周的报告。  请求：  ```json {     "jsonrpc": "2.0",     "method": "report.create",     "params": {         "userid": "1",         "name": "Weekly report",         "dashboardid": "1",         "period": "1",         "cycle": "1",         "start_time": "43200",         "weekdays": "31",         "active_since": "2021-04-01",         "active_till": "2021-08-31",         "subject": "Weekly report",         "message": "Report accompanying text",         "status": "1",         "description": "Report description",         "users": [             {                 "userid": "1",                 "access_userid": "1",                 "exclude": "0"             },             {                 "userid": "2",                 "access_userid": "0",                 "exclude": "1"             }         ],         "user_groups": [             {                 "usrgrpid": "7",                 "access_userid": "0"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "reportids": [             "1"         ]     },     "id": 1 } ```

en-us	#### Creating a script media type  Create a new script media type with a custom value for the number of attempts and the interval between them.  Request:  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": "1",         "name": "Push notifications",         "exec_path": "push-notification.sh",         "exec_params": "{ALERT.SENDTO}\n{ALERT.SUBJECT}\n{ALERT.MESSAGE}\n",         "maxattempts": "5",         "attempt_interval": "11s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "8"         ]     },     "id": 1 } ```
zh-cn	#### 创建脚本媒介类型  创建一个新的脚本媒介类型，自定义失败尝试次数和尝试间隔时间。  请求：  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": 1,         "description": "Push notifications",         "exec_path": "push-notification.sh",         "exec_params": "{ALERT.SENDTO}\n{ALERT.SUBJECT}\n{ALERT.MESSAGE}\n",         "maxattempts": "5",         "attempt_interval": "11s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "8"         ]     },     "id": 1 } ```

en-us	#### Creating a service  Create a service that will be switched to problem state, if at least one child has a problem.  Request:  ```json {     "jsonrpc": "2.0",     "method": "service.create",     "params": {         "name": "Server 1",         "algorithm": 1,         "sortorder": 1     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 创建服务  创建一个如果其至少一个子服务有问题，则会被转化为问题状态的服务。  请求：  ```json {     "jsonrpc": "2.0",     "method": "service.create",     "params": {         "name": "Server 1",         "algorithm": 1,         "sortorder": 1     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Creating a service  Create a service that will be switched to problem state, if at least one child has a problem. SLA calculation will be on and the minimum acceptable SLA will be 99.99%.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "service.create",     "params": {         "name": "Server 1",         "algorithm": 1,         "showsla": 1,         "goodsla": 99.99,         "sortorder": 1     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```  
zh-cn	#### Creating an service 创建服务  Create an service that will be switched to problem state, if at least one child has a problem. SLA calculation will be on and the minimum acceptable SLA is 99.99%. 创建一个至少有一个子服务有问题，将被切换到问题状态的服务。SLA计算将打开并且SLA最低可接受99.99%。 Request 请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "service.create",     "params": {         "name": "Server 1",         "algorithm": 1,         "showsla": 1,         "goodsla": 99.99,         "sortorder": 1     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response 响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```  

en-us	#### Creating a slideshow  A slideshow will run automatically if the dashboard contains two or more pages (see [Adding pages](#adding_pages)) and if one of the following is true:  -   The *Start slideshow automatically* option is marked in dashboard     properties -   The dashboard URL contains a `slideshow=1` parameter  The pages rotate according to the intervals given in the properties of the dashboard and individual pages. Click on:  -   *Stop slideshow* - to stop the slideshow -   *Start slideshow* - to start the slideshow  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_tabs.png)  Slideshow-related controls are also available in [kiosk mode](#viewing_and_editing_a_dashboard) (where only the page content is shown):  -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_stop_kiosk.png) -     stop slideshow -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_start_kiosk.png) -     start slideshow -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_back_kiosk.png) -     go back one page -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_next_kiosk.png) -     go to the next page
zh-cn	#### 创建一个滑动显示  一个滑动显示会在仪表盘包含两个及以上页面（查看[添加页面](#adding_pages)） 且符合以下条件时自动运行：   -   仪表盘属性中的*自动开始滑动显示*选项被选中 -   仪表盘URL包含`slideshow=1`参数  页面根据仪表盘和单个页面属性中的间隔轮换。点击：  -   *停止滑动显示* - 停止滑动显示 -   *开始滑动显示* - 开始滑动显示  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_tabs.png)  滑动显示相关的控制同样在[kiosk模式](#viewing_and_editing_a_dashboard) 中可用（当只显示页面内容是）：  -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_stop_kiosk.png) -     停止滑动显示 -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_start_kiosk.png) -     开始滑动显示 -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_back_kiosk.png) -     返回上一页 -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/slideshow_next_kiosk.png) -     进入下一页

en-us	#### Creating a task  Create a task `check now` for two items. One is an item, the other is a low-level discovery rule.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "6",             "request": {                 "itemid": "10092"             }         },         {             "type": "6",             "request": {                 "itemid": "10093"             }         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "1",             "2"         ]     },     "id": 1 } ```  Create a task `diagnostic information` task. Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "1",             "request": {                 "alerting": {                     "stats": [                         "alerts"                     ],                     "top": {                         "media.alerts": 10                     }                 },                 "lld": {                     "stats": "extend",                     "top": {                         "values": 5                     }                 }             },             "proxy_hostid": 0         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 2 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "3"         ]     },     "id": 2 } ```
zh-cn	#### 创建一个任务  为两个监控项 `check now` 创建一个任务。其一是一个监控项, 另一个是一个低级别自动发现规则。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "6",             "request": {                 "itemid": "10092"             }         },         {             "type": "6",             "request": {                 "itemid": "10093"             }         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "1",             "2"         ]     },     "id": 1 } ```  创建一个 `diagnostic information` 的任务。 请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "1",             "request": {                 "alerting": {                     "stats": [                         "alerts"                     ],                     "top": {                         "media.alerts": 10                     }                 },                 "lld": {                     "stats": "extend",                     "top": {                         "values": 5                     }                 }             },             "proxy_hostid": 0         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "3"         ]     },     "id": 2 } ```

en-us	#### Creating a task  Create a task `check now` for two items. One is an item, the other is a low-level discovery rule.  Request:  ```json {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": 6,             "request": {                 "itemid": "10092"             }         },         {             "type": "6",             "request": {                 "itemid": "10093"             }         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "taskids": [             "1",             "2"         ]     },     "id": 1 } ```  Create a task `diagnostic information` task.  Request:  ```json {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": 1,             "request": {                 "alerting": {                     "stats": [                         "alerts"                     ],                     "top": {                         "media.alerts": 10                     }                 },                 "lld": {                     "stats": "extend",                     "top": {                         "values": 5                     }                 }             },             "proxy_hostid": 0         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 2 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "taskids": [             "3"         ]     },     "id": 2 } ```
zh-cn	#### 创建一个任务  为两个监控项 `check now` 创建一个任务。其一是一个监控项, 另一个是一个低级别自动发现规则。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "6",             "request": {                 "itemid": "10092"             }         },         {             "type": "6",             "request": {                 "itemid": "10093"             }         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "1",             "2"         ]     },     "id": 1 } ```  创建一个 `diagnostic information` 的任务。 请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "task.create",     "params": [         {             "type": "1",             "request": {                 "alerting": {                     "stats": [                         "alerts"                     ],                     "top": {                         "media.alerts": 10                     }                 },                 "lld": {                     "stats": "extend",                     "top": {                         "values": 5                     }                 }             },             "proxy_hostid": 0         }     ],     "auth": "700ca65537074ec963db7efabda78259",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "taskids": [             "3"         ]     },     "id": 2 } ```

en-us	#### Creating a template  Create a template with tags and link two templates to this template.  Request:  ```json {     "jsonrpc": "2.0",     "method": "template.create",     "params": {         "host": "Linux template",         "groups": {             "groupid": 1         },         "templates": [             {                 "templateid": "11115"             },             {                 "templateid": "11116"             }         ],         "tags": [             {                 "tag": "Host name",                 "value": "{HOST.NAME}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "11117"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个模版  创建一个带有标记的模板，并将两个模板链接到此模板。  请求:  ```json {     "jsonrpc": "2.0",     "method": "template.create",     "params": {         "host": "Linux template",         "groups": {             "groupid": 1         },         "templates": [             {                 "templateid": "11115"             },             {                 "templateid": "11116"             }         ],         "tags": [             {                 "tag": "Host name",                 "value": "{HOST.NAME}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "11117"         ]     },     "id": 1 } ```

en-us	#### Creating a template dashboard  Create a template dashboard named “Graphs” with one Graph widget on a single dashboard page.  Request:  ```json {     "jsonrpc": "2.0",     "method": "templatedashboard.create",     "params": {         "templateid": "10318",         "name": "Graphs",         "pages": [             {                 "widgets": [                     {                         "type": "graph",                         "x": 0,                         "y": 0,                         "width": 12,                         "height": 5,                         "view_mode": 0,                         "fields": [                             {                                 "type": 6,                                 "name": "graphid",                                 "value": "1123"                             }                         ]                     }                 ]                              }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "32"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个模版仪表盘  在单个仪表盘页面上使用一个Graph组件创建一个名为“Graphs”的模板仪表盘。  请求：  ```json {     "jsonrpc": "2.0",     "method": "templatedashboard.create",     "params": {         "templateid": "10318",         "name": "Graphs",         "pages": [             {                 "widgets": [                     {                         "type": "graph",                         "x": 0,                         "y": 0,                         "width": 12,                         "height": 5,                         "view_mode": 0,                         "fields": [                             {                                 "type": 6,                                 "name": "graphid",                                 "value": "1123"                             }                         ]                     }                 ]                              }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "32"         ]     },     "id": 1 } ```

en-us	#### Creating a template  To create a template, do the following:  -   Go to *Configuration → Templates* -   Click on *Create template* -   Edit template attributes  The **Templates** tab contains general template attributes.  ![](../../../../assets/en/manual/config/template_a.png)  All mandatory input fields are marked with a red asterisk.  Template attributes:  |Parameter|Description| |---------|-----------| |*Template name*|Unique template name. Alphanumerics, spaces, dots, dashes, and underscores are allowed. However, leading and trailing spaces are disallowed.| |*Visible name*|If you set this name, it will be the one visible in lists, maps, etc.| |*Templates*|Link one or more "nested" templates to this template. All entities (items, triggers, graphs, etc.) will be inherited from the linked templates.<br>To link a new template, start typing the template name in the *Link new templates* field. A list of matching templates will appear; scroll down to select. Alternatively, you may click on *Select* next to the field and select templates from the list in a popup window. The templates that are selected in the *Link new templates* field will be linked to the template when the template configuration form is saved or updated.<br>To unlink a template, use one of the two options in the *Linked templates* block:<br>*Unlink* - unlink the template, but preserve its items, triggers, and graphs<br>*Unlink and clear* - unlink the template and remove all its items, triggers, and graphs| |*Groups*|Host/template groups the template belongs to.| |*Description*|Enter the template description.|  The **Tags** tab allows you to define template-level [tags](/manual/config/tagging). All problems of hosts linked to this template will be tagged with the values entered here.  ![](../../../../assets/en/manual/config/template_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.  The **Macros** tab allows you to define template-level [user macros](/manual/config/macros/user_macros) as a name-value pairs. Note that macro values can be kept as plain text, secret text, or Vault secret. Adding a description is also supported.  ![](../../../../assets/en/manual/config/template_d1.png)  You may also view here macros from linked templates and global macros if you select the *Inherited and template macros* option. That is where all defined user macros for the template are displayed with the value they resolve to as well as their origin.  ![](../../../../assets/en/manual/config/template_d2.png)  For convenience, links to respective templates and global macro configuration are provided. It is also possible to edit a nested template/global macro on the template level, effectively creating a copy of the macro on the template.  The **Value mapping** tab allows to configure human-friendly representation of item data in [value mappings](/manual/config/items/mapping).  Buttons:  |   |   | |---|---| |![](../../../../assets/en/manual/config/button_add.png)|Add the template. The added template should appear in the list.| |![](../../../../assets/en/manual/config/button_update.png)|Update the properties of an existing template.| |![](../../../../assets/en/manual/config/button_clone.png)|Create another template based on the properties of the current template, including the entities (items, triggers, etc) inherited from linked templates.| |![](../../../../assets/en/manual/config/button_full.png)|Create another template based on the properties of the current template, including the entities (items, triggers, etc) both inherited from linked templates and directly attached to the current template.| |![](../../../../assets/en/manual/config/button_delete.png)|Delete the template; entities of the template (items, triggers, etc) remain with the linked hosts.| |![](../../../../assets/en/manual/config/button_clear.png)|Delete the template and all its entities from linked hosts.| |![](../../../../assets/en/manual/config/button_cancel.png)|Cancel the editing of template properties.|  With a template created, it is time to add some entities to it.  ::: noteimportant Items have to be added to a template first. Triggers and graphs cannot be added without the corresponding item. :::
zh-cn	#### 创建模板  要创建模板，请执行以下操作：  -   转到*配置→模板* -   点击*创建模板* -   编辑模板属性  **模板**选项卡包含常规模板属性。  ![](../../../../assets/en/manual/config/template.png)  所有必填字段都标有红色星号。   模板属性：  |参数        |描述                                                    | |------------|--------------------------------------------------------| |*模板名称*  |   唯一的模板名称。 允许使用字母数字、空格、点、破折号和下划线。 但是，空格是不允许在首尾使用。 | |*可见名称*  |   如果你设置了此名称，那么它将在列表，地图等中可见的。| |*模板*      | 将一个或多个“嵌套”模板链接到此模板。 所有实体（项目、触发器、图表等）都将从链接的模板中继承。<br>要链接新模板，请开始在*链接新模板*字段中输入模板名称。 将出现匹配模板列表； 向下滚动以选择。 或者，您可以单击字段旁边的 *选择* 并从弹出窗口的列表中选择模板。 在保存或更新模板配置表单时，在 *链接新模* 字段中选择的模板将被链接。<br>要取消链接模板，请使用 *链接模板* 块中的两个选项之一 :<br>*取消链接* - 取消链接模板，但保留其监控项、触发器和图形<br>*取消链接并清除* - 取消链接模板并删除其所有监控项、触发器和图形  | |*群组*      | 模板所属的主机/模板组。| |*描述*      | 输入模板说明。|  **标签** 选项卡允许您定义模板级别[标签](/manual/config/tagging)。链接了此模板的所有主机的所有问题，将使用此处输入的标签。   ![](../../../../assets/en/manual/config/template_c.png)  标签支持用户宏、{INVENTORY.\*} 宏, {HOST.HOST}, {HOST.NAME},{HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} 和 {HOST.ID} 宏。  **宏** 选项卡允许您将模板级 [用户宏](/manual/config/macros/user_macros) 定义为`名称-值`键值对。 请注意，宏的值可以保存为纯文本、机密文本或 Vault秘钥。 还支持添加描述。   ![](../../../../assets/en/manual/config/template_d1.png)  如果选择了*继承模板的宏*选项，则还可以从链接的模板和全局宏中查看宏。在这里，模板的所有定义的用户宏都显示了它们所决定的值以及它们的起源。  ![](../../../../assets/en/manual/config/template_d2.png)  为方便起见，提供了相应模板和全局宏配置的链接。也可以在模板级别上编辑嵌套模板/全局宏，有效地创建模板上宏的副本。   **值映射**选项卡允许在 [值映射](/manual/config/items/mapping)中配置监控项数据的人性化展示。   按钮:  |   |   | |---|---| |![](../../../../assets/en/manual/config/button_add.png)|添加模板。添加的模板应该出现在列表中。| |![](../../../../assets/en/manual/config/button_update.png)|更新现有模板的属性。| |![](../../../../assets/en/manual/config/button_clone.png)|根据当前模板的属性创建另一个模板，包括从链接模板继承的实体（监控项，触发器等）| |![](../../../../assets/en/manual/config/button_full.png)|基于当前模板的属性创建另一个模板，包括从链接的模板继承并直接附加到当前模板的实体（监控项，触发器等）。| |![](../../../../assets/en/manual/config/button_delete.png)|删除模板; 模板（监控项，触发器等）的实体与链接的主机保留。| |![](../../../../assets/en/manual/config/button_clear.png)|从链接的主机中删除模板及其所有实体。| |![](../../../../assets/en/manual/config/button_cancel.png)|取消编辑模板属性。|  创建一个模板，可以开始添加一些实体。  ::: noteimportant 监控项必须首先添加到模板中。如果没有相应的监控项，则无法添加触发器和图形。 :::

en-us	#### Creating a trigger  Create a trigger with a single trigger dependency.  Request:  ```json {     "jsonrpc": "2.0",     "method": "trigger.create",     "params": [         {             "description": "Processor load is too high on {HOST.NAME}",             "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5",             "dependencies": [                 {                     "triggerid": "17367"                 }             ]         },         {             "description": "Service status",             "expression": "length(last(/Linux server/log[/var/log/system,Service .* has stopped]))<>0",             "dependencies": [                 {                     "triggerid": "17368"                 }             ],             "tags": [                 {                     "tag": "service",                     "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}"                 },                 {                     "tag": "error",                     "value": ""                 }             ]         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17369",             "17370"         ]     },     "id": 1 } ```
zh-cn	#### 创建触发器  创建具有单个触发依赖关系的触发器.  请求:  ```json {     "jsonrpc": "2.0",     "method": "trigger.create",     "params": [         {             "description": "Processor load is too high on {HOST.NAME}",             "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5",             "dependencies": [                 {                     "triggerid": "17367"                 }             ]         },         {             "description": "Service status",             "expression": "length(last(/Linux server/log[/var/log/system,Service .* has stopped]))<>0",             "dependencies": [                 {                     "triggerid": "17368"                 }             ],             "tags": [                 {                     "tag": "service",                     "value": "{{ITEM.VALUE}.regsub(\"Service (.*) has stopped\", \"\\1\")}"                 },                 {                     "tag": "error",                     "value": ""                 }             ]         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17369",             "17370"         ]     },     "id": 1 } ```

en-us	#### Creating a trigger prototype  Create a trigger prototype to detect when a file system has less than 20% free disk space.  Request:  ```json {     "jsonrpc": "2.0",     "method": "triggerprototype.create",     "params": {         "description": "Free disk space is less than 20% on volume {#FSNAME}",         "expression": "last(/Zabbix server/vfs.fs.size[{#FSNAME},pfree])<20",         "tags": [             {                 "tag": "volume",                 "value": "{#FSNAME}"             },             {                 "tag": "type",                 "value": "{#FSTYPE}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17372"         ]     },     "id": 1 } ```
zh-cn	#### 创建触发器原型  创建一个触发器原型来检测磁盘剩余空间是否小于20%.  请求:  ```json {     "jsonrpc": "2.0",     "method": "triggerprototype.create",     "params": {         "description": "Free disk space is less than 20% on volume {#FSNAME}",         "expression": "last(/Zabbix server/vfs.fs.size[{#FSNAME},pfree])<20",         "tags": [             {                 "tag": "volume",                 "value": "{#FSNAME}"             },             {                 "tag": "type",                 "value": "{#FSTYPE}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17372"         ]     },     "id": 1 } ```

en-us	#### Creating a user  Create a new user, add him to a user group and create a new media for him.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.create",     "params": {         "username": "John",         "passwd": "Doe123",         "roleid": "5",         "usrgrps": [             {                 "usrgrpid": "7"             }         ],         "medias": [             {                 "mediatypeid": "1",                 "sendto": [                     "support@company.com"                 ],                 "active": 0,                 "severity": 63,                 "period": "1-7,00:00-24:00"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "12"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个用户  创建一个新用户, 把他加入用户组同时为其添加用户媒介.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.create",     "params": {         "username": "John",         "passwd": "Doe123",         "roleid": "5",         "usrgrps": [             {                 "usrgrpid": "7"             }         ],         "medias": [             {                 "mediatypeid": "1",                 "sendto": [                     "support@company.com"                 ],                 "active": 0,                 "severity": 63,                 "period": "1-7,00:00-24:00"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "12"         ]     },     "id": 1 } ```

en-us	#### Creating a user group  Create a user group, which denies access to host group "2", and add a user to it.  Request:  ```json {     "jsonrpc": "2.0",     "method": "usergroup.create",     "params": {         "name": "Operation managers",         "rights": {             "permission": 0,             "id": "2"         },         "users": [             {"userid": "12"}         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "usrgrpids": [             "20"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个用户组  创建一个用户组, 禁止其访问主机组"2" , 并向其添加一个用户.  请求:  ```json {     "jsonrpc": "2.0",     "method": "usergroup.create",     "params": {         "name": "Operation managers",         "rights": {             "permission": 0,             "id": "2"         },         "users": [             {"userid": "12"}         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "usrgrpids": [             "20"         ]     },     "id": 1 } ```

en-us	#### Creating a value map  Create one value map with two mappings.  Request:  ```json {     "jsonrpc": "2.0",     "method": "valuemap.create",     "params": {         "hostid": "50009",         "name": "Service state",         "mappings": [             {                 "type": "1",                 "value": "1",                 "newvalue": "Up"             },             {                 "type": "5",                 "newvalue": "Down"             }         ]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个值映射  创建一个包含两个映射的值映射。  请求：  ```json {     "jsonrpc": "2.0",     "method": "valuemap.create",     "params": {         "hostid": "50009",         "name": "Service state",         "mappings": [             {                 "type": "1",                 "value": "1",                 "newvalue": "Up"             },             {                 "type": "5",                 "newvalue": "Down"             }         ]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "1"         ]     },     "id": 1 } ```

en-us	#### Creating a webhook media type  Create a new webhook media type.  Request:  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": "4",         "name": "Webhook",         "script": "var Webhook = {\r\n    token: null,\r\n    to: null,\r\n    subject: null,\r\n    message: null,\r\n\r\n    sendMessage: function() {\r\n        // some logic\r\n    }\r\n}",         "parameters": [             {                 "name": "Message",                 "value": "{ALERT.MESSAGE}"             },             {                 "name": "Subject",                 "value": "{ALERT.SUBJECT}"             },             {                 "name": "To",                 "value": "{ALERT.SENDTO}"             },             {                 "name": "Token",                 "value": "<Token>"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "9"         ]     },     "id": 1 } ```
zh-cn	#### 创建 webhook 媒介类型  创建新的 webhook 媒介类型。  请求：  ```json {     "jsonrpc": "2.0",     "method": "mediatype.create",     "params": {         "type": 1,         "description": "Push notifications",         "exec_path": "push-notification.sh",         "exec_params": "{ALERT.SENDTO}\n{ALERT.SUBJECT}\n{ALERT.MESSAGE}\n",         "maxattempts": "5",         "attempt_interval": "11s"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "mediatypeids": [             "9"         ]     },     "id": 1 } ```

en-us	#### Creating a web scenario  Create a web scenario to monitor the company home page. The scenario will have two steps, to check the home page and the "About" page and make sure they return the HTTP status code 200.  Request:  ```json {     "jsonrpc": "2.0",     "method": "httptest.create",     "params": {         "name": "Homepage check",         "hostid": "10085",         "steps": [             {                 "name": "Homepage",                 "url": "http://example.com",                 "status_codes": "200",                 "no": 1             },             {                 "name": "Homepage / About",                 "url": "http://example.com/about",                 "status_codes": "200",                 "no": 2             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "httptestids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个Web场景  创建一个Web场景用于监控公司主页。此场景具有两个步骤，检查主页和“关于”页，并保证它们返回HTTP状态码200。  请求：  ```json {     "jsonrpc": "2.0",     "method": "httptest.create",     "params": {         "name": "Homepage check",         "hostid": "10085",         "steps": [             {                 "name": "Homepage",                 "url": "http://example.com",                 "status_codes": "200",                 "no": 1             },             {                 "name": "Homepage / About",                 "url": "http://example.com/about",                 "status_codes": "200",                 "no": 2             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "httptestids": [             "5"         ]     },     "id": 1 } ```

en-us	### Creating custom LLD rules  It is also possible to create a completely custom LLD rule, discovering any type of entities - for example, databases on a database server.  To do so, a custom item should be created that returns JSON, specifying found objects and optionally - some properties of them. The amount of macros per entity is not limited - while the built-in discovery rules return either one or two macros (for example, two for filesystem discovery), it is possible to return more.  The required JSON format is best illustrated with an example. Suppose we are running an old Zabbix 1.8 agent (one that does not support "vfs.fs.discovery"), but we still need to discover file systems. Here is a simple Perl script for Linux that discovers mounted file systems and outputs JSON, which includes both file system name and type. One way to use it would be as a UserParameter with key "vfs.fs.discovery\_perl":  ``` {.perl} #!/usr/bin/perl  $first = 1;  print "[\n";  for (`cat /proc/mounts`) {     ($fsname, $fstype) = m/\S+ (\S+) (\S+)/;      print "\t,\n" if not $first;     $first = 0;      print "\t{\n";     print "\t\t\"{#FSNAME}\":\"$fsname\",\n";     print "\t\t\"{#FSTYPE}\":\"$fstype\"\n";     print "\t}\n"; }  print "]\n"; ```  ::: noteimportant Allowed symbols for LLD macro names are **0-9** , **A-Z** , **\_** , **.**\ \ Lowercase letters are not supported in the names. :::  An example of its output (reformatted for clarity) is shown below. JSON for custom discovery checks has to follow the same format.  ``` {.javascript} [     { "{#FSNAME}":"/",                           "{#FSTYPE}":"rootfs"   },     { "{#FSNAME}":"/sys",                        "{#FSTYPE}":"sysfs"    },     { "{#FSNAME}":"/proc",                       "{#FSTYPE}":"proc"     },     { "{#FSNAME}":"/dev",                        "{#FSTYPE}":"devtmpfs" },     { "{#FSNAME}":"/dev/pts",                    "{#FSTYPE}":"devpts"   },     { "{#FSNAME}":"/lib/init/rw",                "{#FSTYPE}":"tmpfs"    },     { "{#FSNAME}":"/dev/shm",                    "{#FSTYPE}":"tmpfs"    },     { "{#FSNAME}":"/home",                       "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/tmp",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/usr",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/var",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/sys/fs/fuse/connections",    "{#FSTYPE}":"fusectl"  } ] ```  In previous example it is required that the keys match the LLD macro names used in prototypes, the alternative is to extract LLD macro values using JSONPath `{#FSNAME}` → `$.fsname` and `{#FSTYPE}` → `$.fstype`, thus making such script possible:  ``` {.perl} #!/usr/bin/perl   $first = 1;   print "[\n";   for (`cat /proc/mounts`) {     ($fsname, $fstype) = m/\S+ (\S+) (\S+)/;       print "\t,\n" if not $first;     $first = 0;       print "\t{\n";     print "\t\t\"fsname\":\"$fsname\",\n";     print "\t\t\"fstype\":\"$fstype\"\n";     print "\t}\n"; }   print "]\n"; ```  An example of its output (reformatted for clarity) is shown below. JSON for custom discovery checks has to follow the same format.  ``` {.javascript} [     { "fsname":"/",                           "fstype":"rootfs"   },     { "fsname":"/sys",                        "fstype":"sysfs"    },     { "fsname":"/proc",                       "fstype":"proc"     },     { "fsname":"/dev",                        "fstype":"devtmpfs" },     { "fsname":"/dev/pts",                    "fstype":"devpts"   },     { "fsname":"/lib/init/rw",                "fstype":"tmpfs"    },     { "fsname":"/dev/shm",                    "fstype":"tmpfs"    },     { "fsname":"/home",                       "fstype":"ext3"     },     { "fsname":"/tmp",                        "fstype":"ext3"     },     { "fsname":"/usr",                        "fstype":"ext3"     },     { "fsname":"/var",                        "fstype":"ext3"     },     { "fsname":"/sys/fs/fuse/connections",    "fstype":"fusectl"  } ] ```  Then, in the discovery rule's "Filter" field, we could specify "{\#FSTYPE}" as a macro and "rootfs|ext3" as a regular expression.  ::: noteclassic You don't have to use macro names FSNAME/FSTYPE with custom LLD rules, you are free to use whatever names you like. In case JSONPath is used then LLD row will be an array element that can be an object, but it can be also another array or a value.  :::  Note that, if using a user parameter, the return value is limited to 512 KB. For more details, see [data limits for LLD return values](/manual/discovery/low_level_discovery/notes#data_limits_for_return_values).
zh-cn	### 创建自定义LLD规则  可以创建完全自定义的底层自动发现(LLD)规则，用于发现任何类型的实体 - 例如，服务器上运行的数据库。  要实现此功能，需要创建一个自定义监控项，监控项需要返回JSON数据，其中包含发现的对象以及其它可选项 - 对象的一些属性。每个实体的宏没有数量限制 - 内置的自动发现规则返回一个或两个宏(比如文件系统自动发现返回两个宏)，但自定义的LLD可以返回更多个宏。  最好用一个例子来演示所需的JSON格式比较容易理解。假设一个旧版的Zabbix 1.8的agent正在运行(该agent不支持"vfs.fs.discovery"这个监控项的键)，不过我们还需要对文件系统进行自动发现。下面是个简单的Perl脚本，运行在Linux上，用于发现挂载的文件系统并输出JSON数据，JSON数据中包含文件系统名称和类型。使用Perl脚本的其中一种方式是作为一个UserParameter，利用 "vfs.fs.discovery\_perl" 这个键：  ``` {.perl} #!/usr/bin/perl  $first = 1;  print "[\n";  for (`cat /proc/mounts`) {     ($fsname, $fstype) = m/\S+ (\S+) (\S+)/;      print "\t,\n" if not $first;     $first = 0;      print "\t{\n";     print "\t\t\"{#FSNAME}\":\"$fsname\",\n";     print "\t\t\"{#FSTYPE}\":\"$fstype\"\n";     print "\t}\n"; }  print "]\n"; ```  ::: 重要 LLD宏的名称允许使用的符号有 **0-9** ,**A-Z** , **\_** , **.**\ \ 名称中不支持小写字母。 :::  下面是一个输出(为了看的更清晰，重新排版)的例子。自定义的自动发现检查的JSON格式必须遵循相同的形式。  ``` {.javascript} [     { "{#FSNAME}":"/",                           "{#FSTYPE}":"rootfs"   },     { "{#FSNAME}":"/sys",                        "{#FSTYPE}":"sysfs"    },     { "{#FSNAME}":"/proc",                       "{#FSTYPE}":"proc"     },     { "{#FSNAME}":"/dev",                        "{#FSTYPE}":"devtmpfs" },     { "{#FSNAME}":"/dev/pts",                    "{#FSTYPE}":"devpts"   },     { "{#FSNAME}":"/lib/init/rw",                "{#FSTYPE}":"tmpfs"    },     { "{#FSNAME}":"/dev/shm",                    "{#FSTYPE}":"tmpfs"    },     { "{#FSNAME}":"/home",                       "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/tmp",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/usr",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/var",                        "{#FSTYPE}":"ext3"     },     { "{#FSNAME}":"/sys/fs/fuse/connections",    "{#FSTYPE}":"fusectl"  } ] ```  上面的例子中需要让键匹配原型中使用的LLD宏的名称，另一种方式是提取LLD宏的值，提取的方式是通过JSONPath `{#FSNAME}` → `$.fsname` 和 `{#FSTYPE}` → `$.fstype`, 于是可以使用下面的脚本来实现此功能:  ``` {.perl} #!/usr/bin/perl   $first = 1;   print "[\n";   for (`cat /proc/mounts`) {     ($fsname, $fstype) = m/\S+ (\S+) (\S+)/;       print "\t,\n" if not $first;     $first = 0;       print "\t{\n";     print "\t\t\"fsname\":\"$fsname\",\n";     print "\t\t\"fstype\":\"$fstype\"\n";     print "\t}\n"; }   print "]\n"; ```  下面是一个输出(为了看的更清晰，重新排版)的例子。自定义的自动发现检查的JSON格式必须遵循相同的形式。  ``` {.javascript} [     { "fsname":"/",                           "fstype":"rootfs"   },     { "fsname":"/sys",                        "fstype":"sysfs"    },     { "fsname":"/proc",                       "fstype":"proc"     },     { "fsname":"/dev",                        "fstype":"devtmpfs" },     { "fsname":"/dev/pts",                    "fstype":"devpts"   },     { "fsname":"/lib/init/rw",                "fstype":"tmpfs"    },     { "fsname":"/dev/shm",                    "fstype":"tmpfs"    },     { "fsname":"/home",                       "fstype":"ext3"     },     { "fsname":"/tmp",                        "fstype":"ext3"     },     { "fsname":"/usr",                        "fstype":"ext3"     },     { "fsname":"/var",                        "fstype":"ext3"     },     { "fsname":"/sys/fs/fuse/connections",    "fstype":"fusectl"  } ] ```  然后在自动发现规则的 "过滤器" 选项卡中，可以指定"{\#FSTYPE}" 作为宏 和"rootfs|ext3" 作为正则表达式。  ::: 注意 无需使用 FSNAME/FSTYPE 作为自定义LLD规则中的宏的名称，可以使用任何名称。一旦使用了JSONPath，则LLD返回的数据会是一个数组元素，该元素可以是一个对象、另一个数组或一个值。 :::  注意，如果使用一个用户参数，返回值限制在512 KB大小。更多信息请参考 [LLD返回值的数据大小限制](/manual/discovery/low_level_discovery#data_limits_for_return_values).

en-us	##### Creating database  [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy.  Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
zh-cn	##### 创建数据库  为Zabbix proxy 单独[创建数据库](/manual/appendix/install/db_scripts) 。  Zabbix server和Zabbix proxy 不能使用同一个数据库。如果他们是安装在同一个主机中的，则proxy数据库需要另命名。

en-us	##### Creating database  [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy.  Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
zh-cn	##### 创建数据库  [创建](/manual/appendix/install/db_scripts) Zabbix 代理的单独数据库。  Zabbix server 和 Zabbix proxy 不能使用同一个数据库。 如果它们安装在同一台主机上，则代理数据库必须具有不同的名称。

en-us	##### Creating database  [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy.  Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
zh-cn	##### 创建数据库  为 Zabbix proxy 单独[创建数据库](/manual/appendix/install/db_scripts) 。  Zabbix server 和 Zabbix proxy 不能使用同一个数据库。如果他们是安装在同一个主机中的，则 proxy 数据库需要不同的命名。

en-us	#### Creating database  For Zabbix [server](/manual/concepts/server) and [proxy](/manual/concepts/proxy) daemons a database is required. It is not needed to run Zabbix [agent](/manual/concepts/agent).  ::: notewarning Separate databases are needed for Zabbix server and Zabbix proxy; they cannot use the same database. Therefore, if they are installed on the same host, their databases must be created with different names! :::  Create the database using the provided instructions for [MySQL](/manual/appendix/install/db_scripts#mysql) or [PostgreSQL](/manual/appendix/install/db_scripts#postgresql).
zh-cn	#### 创建数据库  Zabbix [server](/manual/concepts/server) 和[proxy](/manual/concepts/proxy) 守护进程需要数据库，运行 Zabbix [agent](/manual/concepts/agent)不需要。  ::: notewarning Zabbix server和Zabbix proxy不能使用同一个数据库，必须单独创建。因此，如果他们被安装在了同一个主机上，数据库要使用不同的名称创建！ :::  使用提供的说明来创建数据库，[MySQL](/manual/appendix/install/db_scripts#mysql) 与 [PostgreSQL](/manual/appendix/install/db_scripts#postgresql)。

en-us	#### Creating dependent item  Create a dependent item for the master item with ID 24759. Only dependencies on the same host are allowed, therefore master and the dependent item should have the same hostid.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {       "hostid": "30074",       "name": "Dependent test item",       "key_": "dependent.item",       "type": "18",       "master_itemid": "24759",       "value_type": "2"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 创建依赖监控项  创建 ID 为 24759 的主监控项的依赖监控项。仅允许依赖于同一主机，主项和依赖项要具有相同的hostid。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {       "hostid": "30074",       "name": "Dependent test item",       "key_": "dependent.item",       "type": "18",       "master_itemid": "24759",       "value_type": "2"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Creating dependent item  Create a dependent item for the master item with ID 24759. Only dependencies on the same host are allowed, therefore master and the dependent item should have the same hostid.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.create",     "params": {       "hostid": "30074",       "name": "Dependent test item",       "key_": "dependent.item",       "type": 18,       "master_itemid": "24759",       "value_type": 2     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 创建依赖监控项  创建 ID 为 24759 的主监控项的依赖监控项。仅允许依赖于同一主机，主项和依赖项要具有相同的hostid。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {       "hostid": "30074",       "name": "Dependent test item",       "key_": "dependent.item",       "type": "18",       "master_itemid": "24759",       "value_type": "2"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Creating dependent item prototype  Create Dependent item prototype for Master item prototype with ID 44211. Only dependencies on same host (template/discovery rule) are allowed, therefore Master and Dependent item should have same hostid and ruleid.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {       "hostid": "10001",       "ruleid": "27665",       "name": "Dependent test item prototype",       "key_": "dependent.prototype",       "type": "18",       "master_itemid": "44211",       "value_type": "3"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44212"         ]     },     "id": 1 } ```
zh-cn	#### 创建依赖监控项原型  创建依赖与ID 44211监控项原型的监控项原型。 只允许依赖一些主机(模板/发现规则)，因此主要监控项和依赖监控项应该具有相同的 hostid 和 ruleid。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "hostid": "10001",  · "ruleid": "27665",  · "name": "Dependent test item prototype",  · "key_": "dependent.prototype",  · "type": "18",  · "master_itemid": "44211",  · "value_type": "3"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44212"  · ]  · },  · "id": 1 } ```

en-us	#### Creating dependent item prototype  Create Dependent item prototype for Master item prototype with ID 44211. Only dependencies on same host (template/discovery rule) are allowed, therefore Master and Dependent item should have same hostid and ruleid.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {       "hostid": "10001",       "ruleid": "27665",       "name": "Dependent test item prototype",       "key_": "dependent.prototype",       "type": 18,       "master_itemid": "44211",       "value_type": 3     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44212"         ]     },     "id": 1 } ```
zh-cn	#### 创建依赖监控项原型  创建依赖与ID 44211监控项原型的监控项原型。 只允许依赖一些主机(模板/发现规则)，因此主要监控项和依赖监控项应该具有相同的 hostid 和 ruleid。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "hostid": "10001",  · "ruleid": "27665",  · "name": "Dependent test item prototype",  · "key_": "dependent.prototype",  · "type": "18",  · "master_itemid": "44211",  · "value_type": "3"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44212"  · ]  · },  · "id": 1 } ```

en-us	#### Creating interfaces  Create an interface on two hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.massadd",     "params": {         "hosts": [             {                 "hostid": "30050"             },             {                 "hostid": "30052"             }         ],         "interfaces": {             "dns": "",             "ip": "127.0.0.1",             "main": 0,             "port": "10050",             "type": 1,             "useip": 1         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30069",             "30070"         ]     },     "id": 1 } ```
zh-cn	#### 创建接口  在两个主机上创建接口  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.massadd",     "params": {         "hosts": [             {                 "hostid": "30050"             },             {                 "hostid": "30052"             }         ],         "interfaces": {             "dns": "",             "ip": "127.0.0.1",             "main": 0,             "port": "10050",             "type": 1,             "useip": 1         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30069",             "30070"         ]     },     "id": 1 } ```

en-us	#### Creating multiple triggers  So if create methods accept arrays, we can add multiple [triggers](/manual/api/reference/trigger/object) like so:  ```json {     "jsonrpc": "2.0",     "method": "trigger.create",     "params": [         {             "description": "Processor load is too high on {HOST.NAME}",             "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5",         },         {             "description": "Too many processes on {HOST.NAME}",             "expression": "avg(/Linux server/proc.num[],5m)>300",         }     ],     "auth": "0424bd59b807674191e7d77572075f33",     "id": 4 } ```  A successful response will contain the IDs of the newly created triggers:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17369",             "17370"         ]     },     "id": 4 } ```
zh-cn	#### 创建多个触发器  因此，如果create方法接受数组，我们可以添加多个 [触发器] (/manual/api/reference/trigger/object) ，像这样：  ``` {.json} {     "jsonrpc": "2.0",     "method": "trigger.create",     "params": [         {             "description": "Processor load is too high on {HOST.NAME}",             "expression": "last(/Linux server/system.cpu.load[percpu,avg1])>5",         },         {             "description": "Too many processes on {HOST.NAME}",             "expression": "avg(/Linux server/proc.num[],5m)>300",         }     ],     "auth": "0424bd59b807674191e7d77572075f33",     "id": 4 } ```  操作成功的响应将包含新创建触发器的 ID 数组：  ``` {.json} {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "17369",             "17370"         ]     },     "id": 4 } ```

en-us	##### - Credentials (login:password)  System:  -   root:zabbix  Zabbix frontend:  -   Admin:zabbix  Database:  -   root:<random> -   zabbix:<random>  ::: noteclassic Database passwords are randomly generated during the installation process.\ Root password is stored inside the /root/.my.cnf file. It is not required to input a password under the "root" account. :::  To change the database user password, changes have to be made in the following locations:  -   MySQL; -   /etc/zabbix/zabbix\_server.conf; -   /etc/zabbix/web/zabbix.conf.php.  ::: noteclassic  Separate users `zabbix_srv` and `zabbix_web` are defined for the server and the frontend respectively.  :::
zh-cn	##### - 凭证信息 (用户名:密码)  系统：  -   root:zabbix  Zabbix 前端：  -   Admin:zabbix  数据库：  -   root:<random> -   zabbix:<random>  ::: noteclassic 数据库密码是在安装过程中随机生成的。\ Root 密码存储在 /root/.my.cnf 文件中。不需要在 "root" 用户下输入密码。 :::  要更改数据库用户密码，必须在以下位置同时改变配置：  -   MySQL; -   /etc/zabbix/zabbix\_server.conf; -   /etc/zabbix/web/zabbix.conf.php.  ::: noteclassic 分别为 Zabbix Server 和 Zabbix 前端 定义了单独的用户 `zabbix_srv` 及 `zabbix_web`。 :::

en-us	### Critical
zh-cn	### 至关重要的

en-us	#### CRL expired or expires during server operation  [*OpenSSL*]{.underline}, in server log:  -   before expiration:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate revoked"  -   after expiration:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate expired"  The point here is that with valid CRL a revoked certificate is reported as "certificate revoked". When CRL expires the error message changes to "certificate expired" which is quite misleading.  [*GnuTLS*]{.underline}, in server log:  -   before and after expiration the same:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\           invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked.
zh-cn	 #### CRL 已过期或者在服务器操作期间过期  [*OpenSSL*]{.underline}, 在服务器日志中会议如下显示：  -   到期前：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate revoked"  -   到期后：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate expired"  这里需要注意的是，使用有效的 CRL，吊销的证书将报告为"证书已吊销"。当 CRL 过期时，错误消息将更改为"证书已过期"，这非常具有误导性。  [*GnuTLS*]{.underline}, 在服务器日志中会议如下显示：  -   到期前后显示相同：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\           invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked.

en-us	### Cryptography
zh-cn	### 密码学

en-us	##### Custom copyright notice  To set a custom copyright notice, add BRAND\_FOOTER to the array from the first listing. Please be aware that HTML is not supported here. Setting BRAND\_FOOTER to an empty string will hide the copyright notes completely (but the footer will stay in place).  ``` {.php} 'BRAND_FOOTER' => '{text}', ```
zh-cn	##### 自定义版权声明  要设置自定义版权声明，请将 BRAND\_FOOTER 添加到第一个列表中的数组中。 请注意，此处不支持 HTML。 将 BRAND\_FOOTER 设置为空字符串将完全隐藏版权说明（但页脚将保留在原位）。  ``` {.php} 'BRAND_FOOTER' => '{text}', ```

en-us	##### Custom help location  To replace the default Help link with a link of your choice, add BRAND\_HELP\_URL to the array from the first listing.  ``` {.php} 'BRAND_HELP_URL' => '{URL}', ```
zh-cn	##### 自定义帮助 要将默认帮助链接替换为您选择的链接，请将 BRAND\_HELP\_URL 添加到第一个列表中的数组中。  ``` {.php} 'BRAND_HELP_URL' => '{URL}', ```

en-us	### Custom interface details  The details object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**version**<br>(required)|integer|SNMP interface version.<br><br>Possible values are:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|integer|Whether to use bulk SNMP requests.<br><br>Possible values are:<br>0 - don't use bulk requests;<br>1 - *(default)* - use bulk requests.| |community|string|SNMP community. Used only by SNMPv1 and SNMPv2 interfaces.| |securityname|string|SNMPv3 security name. Used only by SNMPv3 interfaces.| |securitylevel|integer|SNMPv3 security level. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |authpassphrase|string|SNMPv3 authentication passphrase. Used only by SNMPv3 interfaces.| |privpassphrase|string|SNMPv3 privacy passphrase. Used only by SNMPv3 interfaces.| |authprotocol|integer|SNMPv3 authentication protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |privprotocol|integer|SNMPv3 privacy protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |contextname|string|SNMPv3 context name. Used only by SNMPv3 interfaces.|
zh-cn	### 自定义接口详细信息  详细信息对象有以下属性：  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**version**<br>(必选)|整型|SNMP接口版本。<br><br>可能的值有:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|整型|是否使用批量的SNMP请求<br><br>可能的值有:<br>0 - 不使用批量请求;<br>1 - *(默认)* - 使用批量请求。| |community|字符串|SNMP 团体字。仅用于SNMPv1和SNMPv2接口。| |securityname|字符串|SNMPv3安全名称。仅用于SNMPv3的接口| |securitylevel|整型|SNMPv3安全级别。仅用于SNMPv3的接口<br><br>可能的值有:<br>0 - *(默认)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv。| |authpassphrase|字符串|SNMPv3身份认证密码。仅用于SNMPv3的接口。| |privpassphrase|字符串|SNMPv3私有密码，仅用于SNMPv3的接口。| |authprotocol|整型|SNMPv3认证协议。仅用于SNMPv3的接口。<br><br>可能的值有:<br>0 - *(默认)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512。| |privprotocol|整型|SNMPv3隐私协议。仅用于SNMPv3的接口。<br><br>可能的值有:<br>0 - *(默认)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C。| |contextname|字符串|SNMPv3上下文名称。仅用于SNMPv3的接口。|

en-us	### Custom interface details  The details object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**version**<br>(required)|integer|SNMP interface version.<br><br>Possible values are:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|integer|Whether to use bulk SNMP requests.<br><br>Possible values are:<br>0 - don't use bulk requests;<br>1 - *(default)* - use bulk requests.| |community|string|SNMP community. Used only by SNMPv1 and SNMPv2 interfaces.| |securityname|string|SNMPv3 security name. Used only by SNMPv3 interfaces.| |securitylevel|integer|SNMPv3 security level. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv.| |authpassphrase|string|SNMPv3 authentication passphrase. Used only by SNMPv3 interfaces.| |privpassphrase|string|SNMPv3 privacy passphrase. Used only by SNMPv3 interfaces.| |authprotocol|integer|SNMPv3 authentication protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512.| |privprotocol|integer|SNMPv3 privacy protocol. Used only by SNMPv3 interfaces.<br><br>Possible values are:<br>0 - *(default)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C.| |contextname|string|SNMPv3 context name. Used only by SNMPv3 interfaces.|  
zh-cn	### 自定义接口详细信息  详细信息对象有以下属性：  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**version**<br>(必选)|整型|SNMP接口版本。<br><br>可能的值有:<br>1 - SNMPv1;<br>2 - SNMPv2c;<br>3 - SNMPv3| |bulk|整型|是否使用批量的SNMP请求<br><br>可能的值有:<br>0 - 不使用批量请求;<br>1 - *(默认)* - 使用批量请求。| |community|字符串|SNMP 团体字。仅用于SNMPv1和SNMPv2接口。| |securityname|字符串|SNMPv3安全名称。仅用于SNMPv3的接口| |securitylevel|整型|SNMPv3安全级别。仅用于SNMPv3的接口<br><br>可能的值有:<br>0 - *(默认)* - noAuthNoPriv;<br>1 - authNoPriv;<br>2 - authPriv。| |authpassphrase|字符串|SNMPv3身份认证密码。仅用于SNMPv3的接口。| |privpassphrase|字符串|SNMPv3私有密码，仅用于SNMPv3的接口。| |authprotocol|整型|SNMPv3认证协议。仅用于SNMPv3的接口。<br><br>可能的值有:<br>0 - *(默认)* - MD5;<br>1 - SHA1;<br>2 - SHA224;<br>3 - SHA256;<br>4 - SHA384;<br>5 - SHA512。| |privprotocol|整型|SNMPv3隐私协议。仅用于SNMPv3的接口。<br><br>可能的值有:<br>0 - *(默认)* - DES;<br>1 - AES128;<br>2 - AES192;<br>3 - AES256;<br>4 - AES192C;<br>5 - AES256C。| |contextname|字符串|SNMPv3上下文名称。仅用于SNMPv3的接口。|

en-us	### Custom interface  The custom interface object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dns|string|DNS name used by the interface.<br><br>**Required** if the connection is made via DNS. Can contain macros.| |ip|string|IP address used by the interface.<br><br>**Required** if the connection is made via IP. Can contain macros.| |**main**<br>(required)|integer|Whether the interface is used as default on the host. Only one interface of some type can be set as default on a host.<br><br>Possible values are:<br>0 - not default;<br>1 - default.| |**port**<br>(required)|string|Port number used by the interface. Can contain user and LLD macros.| |**type**<br>(required)|integer|Interface type.<br><br>Possible values are:<br>1 - agent;<br>2 - SNMP;<br>3 - IPMI;<br>4 - JMX.<br>| |**useip**<br>(required)|integer|Whether the connection should be made via IP.<br><br>Possible values are:<br>0 - connect using host DNS name;<br>1 - connect using host IP address for this host interface.| |details|array|Additional object for interface. **Required** if interface 'type' is SNMP.|
zh-cn	### 自定义接口  自定义接口对象与以下属性：  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |dns|字符串|接口使用的DNS名称。<br><br>如果直接通过DNS连接，则**必选**，可以包含宏| |ip|字符串|接口使用的IP<br><br>如果直接通过IP连接，则**必选**，可以包含宏| |**main**<br>(必选)|整型|该接口是否在主机上用作默认接口，在主机上只能将某种类型的一个接口设置为默认值。<br><br>可能的值:<br>0 - 不是默认;<br>1 - 默认。| |**port**<br>(必选)|字符串|接口使用的端口号。可以包含用户宏和LLD宏。| |**type**<br>(必选)|整型|接口类型。<br><br>可能的值:<br>1 - agent;<br>2 - SNMP;<br>3 - IPMI;<br>4 - JMX。<br>| |**useip**<br>(必选)|整型|是否通过IP进行连接。<br><br>可能的值有:<br>0 - 使用主机DNS名称进行连接;<br>1 - 使用此主机接口的IP地址进行连接| |details|数组|接口的附加对象。如果接口'类型'是SNMP则 **必须**。|

en-us	### Custom interface  The custom interface object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |dns|string|DNS name used by the interface.<br><br>**Required** if the connection is made via DNS. Can contain macros.| |ip|string|IP address used by the interface.<br><br>**Required** if the connection is made via IP. Can contain macros.| |**main**<br>(required)|integer|Whether the interface is used as default on the host. Only one interface of some type can be set as default on a host.<br><br>Possible values are:<br>0 - not default;<br>1 - default.| |**port**<br>(required)|string|Port number used by the interface. Can contain user and LLD macros.| |**type**<br>(required)|integer|Interface type.<br><br>Possible values are:<br>1 - agent;<br>2 - SNMP;<br>3 - IPMI;<br>4 - JMX.<br>| |**useip**<br>(required)|integer|Whether the connection should be made via IP.<br><br>Possible values are:<br>0 - connect using host DNS name;<br>1 - connect using host IP address for this host interface.| |details|array|Additional object for interface. **Required** if interface 'type' is SNMP.|  
zh-cn	### 自定义接口  自定义接口对象与以下属性：  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |dns|字符串|接口使用的DNS名称。<br><br>如果直接通过DNS连接，则**必选**，可以包含宏| |ip|字符串|接口使用的IP<br><br>如果直接通过IP连接，则**必选**，可以包含宏| |**main**<br>(必选)|整型|该接口是否在主机上用作默认接口，在主机上只能将某种类型的一个接口设置为默认值。<br><br>可能的值:<br>0 - 不是默认;<br>1 - 默认。| |**port**<br>(必选)|字符串|接口使用的端口号。可以包含用户宏和LLD宏。| |**type**<br>(必选)|整型|接口类型。<br><br>可能的值:<br>1 - agent;<br>2 - SNMP;<br>3 - IPMI;<br>4 - JMX。<br>| |**useip**<br>(必选)|整型|是否通过IP进行连接。<br><br>可能的值有:<br>0 - 使用主机DNS名称进行连接;<br>1 - 使用此主机接口的IP地址进行连接| |details|数组|接口的附加对象。如果接口'类型'是SNMP则 **必须**。|

en-us	##### Custom logo  To use a custom **logo**, add the following line to the array from the previous listing:  ``` {.php} 'BRAND_LOGO' => '{Path to an image on the disk or URL}', ```  With the redesign of the main menu in Zabbix 5.0, there are two additional images of the Zabbix logo that can be overridden:  -   BRAND\_LOGO\_SIDEBAR - displayed when the sidebar is expanded -   BRAND\_LOGO\_SIDEBAR\_COMPACT - displayed when the sidebar is     collapsed  To override:  ``` {.php} 'BRAND_LOGO_SIDEBAR' => '{Path to an image on the disk or URL}', 'BRAND_LOGO_SIDEBAR_COMPACT' => '{Path to an image on the disk or URL}', ```  Any image format supported by modern browsers can be used: JPG, PNG, SVG, BMP, WebP and GIF.  ::: noteclassic Custom logos will not be scaled, resized or modified in any way, and will be displayed in their original sizes and proportions, but may be cropped to fit in the corresponding place. :::
zh-cn	##### 自定义logo 要使用自定义 **logo**，请将以下行添加到上一个清单中的数组中：  ``` {.php} 'BRAND_LOGO' => '{Path to an image on the disk or URL}', ```  随着 Zabbix 5.0 中主菜单的重新设计，有两个额外的 Zabbix logo 图像可以被覆盖：  - · BRAND\_LOGO\_SIDEBAR - 侧边栏展开时显示 - · BRAND\_LOGO\_SIDEBAR\_COMPACT - 侧边栏折叠时显示 · 折叠  覆盖:  ``` {.php} 'BRAND_LOGO_SIDEBAR' => '{Path to an image on the disk or URL}', 'BRAND_LOGO_SIDEBAR_COMPACT' => '{Path to an image on the disk or URL}', ```  可以使用现代浏览器支持的任何图像格式：JPG、PNG、SVG、BMP、WebP 和 GIF。  ::: noteclassic 自定义logo不会以任何方式缩放、调整大小或修改，并将以其原始大小和比例显示，但可能会被裁剪以适合相应的位置。 :::

en-us	#### Custom macros  The **LLD macros** tab allows to specify custom low-level discovery macros.  Custom macros are useful in cases when the returned JSON does not have the required macros already defined. So, for example:  -   The native `vfs.fs.discovery` key for filesystem discovery returns a     JSON with some pre-defined LLD macros such as {\#FSNAME},     {\#FSTYPE}. These macros can be used in item, trigger prototypes     (see subsequent sections of the page) directly; defining custom     macros is not needed; -   The `vfs.fs.get` agent item also returns a JSON with [filesystem     data](/manual/discovery/low_level_discovery/examples/mounted_filesystems),     but without any pre-defined LLD macros. In this case you may define     the macros yourself, and map them to the values in the JSON using     JSONPath:  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_c.png)  The extracted values can be used in discovered items, triggers, etc. Note that values will be extracted from the result of discovery and any preprocessing steps so far.  |Parameter|Description| |--|--------| |*LLD macro*|Name of the low-level discovery macro, using the following syntax: {\#MACRO}.| |*JSONPath*|Path that is used to extract LLD macro value from a LLD row, using JSONPath syntax.<br>For example, `$.foo` will extract "bar" and "baz" from this JSON: `[{"foo":"bar"}, {"foo":"baz"}]`<br>The values extracted from the returned JSON are used to replace the LLD macros in item, trigger, etc. prototype fields.<br>JSONPath can be specified using the dot notation or the bracket notation. Bracket notation should be used in case of any special characters and Unicode, like `$['unicode + special chars #1']['unicode + special chars #2']`.|
zh-cn	#### 自定义宏   **LLD 宏** 选项卡可以自定义底层自动发现的宏。  如果返回的JSON数据不包含所需的宏时，自定义宏就派上用场了。例如:  -   用于文件系统自动发现的内置的 `vfs.fs.discovery` 键返回JSON数据，其中包含一些预定义的LLD宏，比如 {\#FSNAME},     {\#FSTYPE}。这些宏可直接用于监控项和触发器原型，(参考本页后续小节); 自定义宏不是强制的; -    `vfs.fs.get` 键同样返回JSON数据，包含 [文件系统数据](/manual/discovery/low_level_discovery/examples/mounted_filesystems),     但不包括任何预定义的LLD宏。此例中你可以自定义宏, 并把自定义的宏映射到JSONPath返回的JSON数据上:  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_c.png)  提取的值可用于已发现的监控项、触发器等实体上。 注意，值会从自动发现的结果中提取出来，也会从任何到目前为止的预处理步骤的结果中提取出来。  |参数|描述| |---------|-----------| |*LLD宏*|底层自动发现宏的名称, 使用如下的语法格式: {\#MACRO}.| |*JSONPath*|用于提取LLD宏的取值的路径, 使用JSONPath语法格式.<br>比如, `$.foo` 会从下面的JSON数据中提取 "bar" 和 "baz": `[{"foo":"bar"}, {"foo":"baz"}]`<br>从JSON数据中提取的值用于替换监控项、触发器和其它实体的原型中配置的LLD宏。<br>可以使用点标记法或括号标记法来指定JSONPath。括号标记法应该用于任何使用特殊字符和编码的场景中, 像 `$['unicode + special chars #1']['unicode + special chars #2']`。|

en-us	#### Custom script limit  Available custom script length depends on the database used:  |Database|Limit in characters|Limit in bytes| |---|---|---| |**MySQL**|65535|65535| |**Oracle Database**|2048|4000| |**PostgreSQL**|65535|not limited| |**SQLite (only Zabbix proxy)**|65535|not limited|
zh-cn	#### 自定义脚本限制  可用的自定义脚本长度取决于使用的数据库：  |数据库|字符限制|字节限制| |---|---|---| |**MySQL**|65535|65535| |**Oracle 数据库**|2048|4000| |**PostgreSQL**|65535|无限制| |**SQLite（仅Zabbix proxy）**|65535|无限制|

en-us	#### dashboard Changes:\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) added new widget type `slareport` and widget field types *(9 - Service, 10 - SLA)*.\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) added new widget type `item`.\
zh-cn	 #### 仪表盘  变更：\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) 添加对SLA和Service字段类型的支持。\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) 添加对新新控件类型`item`的支持。\

en-us	#### dashboard Changes:\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) Added support for SLA and Service field types.\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) added support of new widget type `item`.\
zh-cn	 #### 仪表盘  变更：\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) 添加对SLA和Service字段类型的支持。\ [ZBXNEXT-6966](https://support.zabbix.com/browse/ZBXNEXT-6966) 添加对新新控件类型`item`的支持。\

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

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

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

en-us	# > Dashboard object  The following objects are directly related to the `dashboard` API.
zh-cn	# > 仪表盘对象  下列对象与`dashboard（仪表盘）` API 直接相关。

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

en-us	#### Dashboards  Manage dashboards and make scheduled reports based on them.  [Dashboard API](/manual/api/reference/dashboard) | [Template dashboard API](/manual/api/reference/templatedashboard) | [Report API](/manual/api/reference/report)
zh-cn	#### 仪表盘  管理仪表板并基于它们生成定时报表。  [Dashboard API](/manual/api/reference/dashboard) | [Template dashboard API](/manual/api/reference/templatedashboard) | [Report API](/manual/api/reference/report)

en-us	### Dashboard  The dashboard object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dashboardid|string|*(readonly)* ID of the dashboard.| |**name**<br>(required)|string|Name of the dashboard.| |userid|string|Dashboard owner user ID.| |private|integer|Type of dashboard sharing.<br><br>Possible values:<br>0 - public dashboard;<br>1 - *(default)* private dashboard.| |display\_period|integer|Default page display period (in seconds).<br><br>Possible values: 10, 30, 60, 120, 600, 1800, 3600.<br><br>Default: 30.| |auto\_start|integer|Auto start slideshow.<br><br>Possible values:<br>0 - do not auto start slideshow;<br>1 - *(default)* auto start slideshow.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 仪表盘  仪表盘对象具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |dashboardid|字符|*（只读）* 仪表盘ID。| |**name**<br>（必需）|字符|仪表盘名称。| |userid|字符|仪表盘所属用户的用户ID。| |private|整数|仪表盘的共享类型。<br><br>可用值：<br>0 - 公共仪表盘；<br>1 - *（默认）* 私有仪表盘。| |display\_period|整数|默认页面显示周期（秒）。<br><br>可用值：10，30，60，120，600，1800，3600。<br><br>默认：30。| |auto\_start|整数|自动幻灯片放映。<br><br>可用值：<br>0 - 不自动开始幻灯片放映；<br>1 - *（默认）* 自动开始幻灯片放映。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Dashboard  This class is designed to work with dashboards.  Object references:\  -   [Dashboard](/manual/api/reference/dashboard/object#dashboard) -   [Dashboard     page](/manual/api/reference/dashboard/object#dashboard_page) -   [Dashboard     widget](/manual/api/reference/dashboard/object#dashboard_widget) -   [Dashboard widget     field](/manual/api/reference/dashboard/object#dashboard_widget_field) -   [Dashboard     user](/manual/api/reference/dashboard/object#dashboard_user) -   [Dashboard user     group](/manual/api/reference/dashboard/object#dashboard_user_group)  Available methods:\  -   [dashboard.create](/manual/api/reference/dashboard/create) -     creating new dashboards -   [dashboard.delete](/manual/api/reference/dashboard/delete) -     deleting dashboards -   [dashboard.get](/manual/api/reference/dashboard/get) - retrieving     dashboards -   [dashboard.update](/manual/api/reference/dashboard/update) -     updating dashboards
zh-cn	# 仪表盘  此类被设计用于仪表盘。  对象引用：  -   [仪表盘](/manual/api/reference/dashboard/object#仪表盘) -   [仪表盘页面](/manual/api/reference/dashboard/object#仪表盘页面) -   [仪表盘部件](/manual/api/reference/dashboard/object#仪表盘部件) -   [仪表盘部件字段](/manual/api/reference/dashboard/object#仪表盘部件字段) -   [仪表盘用户](/manual/api/reference/dashboard/object#仪表盘用户) -   [仪表盘用户组](/manual/api/reference/dashboard/object#仪表盘用户组)  可用方法：  -   [dashboard.create](/manual/api/reference/dashboard/create) - 创建新的仪表盘 -   [dashboard.delete](/manual/api/reference/dashboard/delete) - 删除仪表盘 -   [dashboard.get](/manual/api/reference/dashboard/get) - 获取仪表盘 -   [dashboard.update](/manual/api/reference/dashboard/update) - 更新仪表盘

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

en-us	### Dashboard user group  List of dashboard permissions based on user groups. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 仪表盘用户组  基于用户组的仪表盘权限列表。具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>（必需）|string|用户组ID。| |**permission**<br>（必需）|integer|权限级别类型。<br><br>可用值：<br>2 - 只读；<br>3 - 读写。|

en-us	### Dashboard user group  List of dashboard permissions based on user groups. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 仪表盘用户组  基于用户组的仪表盘权限列表。具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>（必需）|string|用户组ID。| |**permission**<br>（必需）|integer|权限级别类型。<br><br>可用值：<br>2 - 只读；<br>3 - 读写。|

en-us	### Dashboard user  List of dashboard permissions based on users. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 仪表盘用户  基于用户的仪表盘权限列表。其具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**userid**<br>（必需）|string|用户ID。| |**permission**<br>（必需）|integer|权限级别类型。<br><br>可用值：<br>2 - 只读；<br>3 - 读写。|

en-us	### Dashboard user  List of dashboard permissions based on users. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 仪表盘用户  基于用户的仪表盘权限列表。其具有以下属性：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**userid**<br>（必需）|string|用户ID。| |**permission**<br>（必需）|integer|权限级别类型。<br><br>可用值：<br>2 - 只读；<br>3 - 读写。|

en-us	### Dashboard widget field  The dashboard widget field object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of the widget field.<br><br>Possible values:<br>0 - Integer;<br>1 - String;<br>2 - Host group;<br>3 - Host;<br>4 - Item;<br>5 - Item prototype;<br>6 - Graph;<br>7 - Graph prototype;<br>8 - Map;<br>9 - Service;<br>10 - SLA.| |**name**<br>(required)|string|Widget field name.<br><br>Possible values: see [Dashboard widget fields](/manual/api/reference/dashboard/widget_fields).| |**value**<br>(required)|mixed|Widget field value depending on the type.<br><br>Possible values: see [Dashboard widget fields](/manual/api/reference/dashboard/widget_fields).|
zh-cn	### 仪表板小部件字段  仪表板小部件字段对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--|--|------| |**type**<br>（必填）|整数|小部件字段的类型。<br><br>可能的值：<br>0 - 整数；<br>1 - 字符串；<br>2 - 主机组;<br>3 - 主机;<br>4 - 监控项;<br>5 - 监控项原型;<br>6 - 图形;<br>7 - 图形原型;<br>8 - 映射;<br>9 - 服务；<br>10 - SLA。| |**name**<br>（必填）|string|小部件字段名称。<br><br>可能的值：参见 [仪表板小部件字段](/manual/api/reference/dashboard/widget_fields)。| |**value**<br>（必填）|mixed|小部件字段值取决于类型。<br><br>可能的值：请参阅[仪表板小部件字段](/manual/api/reference/dashboard/widget_fields) .|

en-us	### Dashboard widget  The dashboard widget object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |widgetid|string|*(readonly)* ID of the dashboard widget.| |**type**<br>(required)|string|Type of the dashboard widget.<br><br>Possible values:<br>actionlog - Action log;<br>clock - Clock;<br>dataover - Data overview;<br>discovery - Discovery status;<br>favgraphs - Favorite graphs;<br>favmaps - Favorite maps;<br>graph - Graph (classic);<br>graphprototype - Graph prototype;<br>hostavail - Host availability;<br>item - Item value;<br>map - Map;<br>navtree - Map Navigation Tree;<br>plaintext - Plain text;<br>problemhosts - Problem hosts;<br>problems - Problems;<br>problemsbysv - Problems by severity;<br>svggraph - Graph;<br>systeminfo - System information;<br>trigover - Trigger overview;<br>url - URL;<br>web - Web monitoring.| |name|string|Custom widget name.| |x|integer|A horizontal position from the left side of the dashboard.<br><br>Valid values range from 0 to 23.| |y|integer|A vertical position from the top of the dashboard.<br><br>Valid values range from 0 to 62.| |width|integer|The widget width.<br><br>Valid values range from 1 to 24.| |height|integer|The widget height.<br><br>Valid values range from 2 to 32.| |view\_mode|integer|The widget view mode.<br><br>Possible values:<br>0 - (default) default widget view;<br>1 - with hidden header;| |fields|array|Array of the [dashboard widget field](object#dashboard_widget_field) objects.|  
zh-cn	### 仪表板小部件字段  仪表板小部件字段对象具有以下属性：  |属性         类|描述|<| |------------------|------|-| |**type**<br>（需要的）|整数     小<br>|件字段的值。<br>可能的值：<br>0 - 整数；<br>1 - 字符串；<br>2 - 主机组；<br>3 - 主机；<br>4 - 监控项；<br>6 - 图形；<br>8 - 拓扑图；| |name|字符串   小部|字段的名称。| |**value**<br>（需要的）|混合型   取决|类型的小部件字段值。|  

en-us	#### Database engine  This is probably the most important part of Zabbix tuning. Zabbix heavily depends on the availability and performance of database engine.  -   use fastest database engine, i.e. MySQL or PostgreSQL -   use stable release of a database engine -   rebuild MySQL or PostgreSQL from sources to get maximum performance -   follow performance tuning instructions taken from MySQL or     PostgreSQL documentation -   for MySQL, use InnoDB table structure -   ZABBIX works at least 1.5 times faster (comparing to MyISAM) if     InnoDB is used. This is because of increased parallelism. However,     InnoDB requires more CPU power. -   tuning the database server for the best performance is highly     recommended. -   keep database tables on different hard disks -   'history', 'history\_str, 'items' 'functions', triggers', and     'trends' are most heavily used tables. -   for large installations keeping MySQL temporary files in tmpfs is:     -   MySQL >= 5.5: not recommended ([MySQL bug         \#58421](https://bugs.mysql.com/bug.php?id=58421))     -   MySQL < 5.5: recommended
zh-cn	 #### 数据库引擎  这可能是 Zabbix 调优中最重要的部分。Zabbix 很大程度上依赖于数据库引擎的可用性和性能。  -   使用最快的数据库引擎，即 MySQL 或 PostgreSQL -   使用稳定版本的数据库引擎 -  从源代码重建 MySQL 或 PostgreSQL 以获得最佳性能 -  遵循从 MySQL 或 PostgreSQL 文档中获取的性能调整说明 -  对于 MySQL，使用 InnoDB 表结构 -   如果使用 InnoDB，ZABBIX 的运行速度至少快 1.5 倍（与 MyISAM 相比）。这是因为增加了并行性。然而，InnoDB 需要更多的 CPU算力 -   强烈建议调整数据库服务器以获得最佳性能 -   将数据库表保存在不同的硬盘上 -   'history', 'history\_str, 'items' 'functions', triggers', 和'trends' 是使用最频繁的表。 -   对于将 MySQL 临时文件保存在 tmpfs 中的大型安装是：     -   MySQL >= 5.5: 不推荐 ([MySQL 错误  \#58421](https://bugs.mysql.com/bug.php?id=58421))     -   MySQL < 5.5: 推荐

en-us	##### Database management system  |Software|Supported versions|Comments| |--------|------------------|--------| |*MySQL/Percona*|8.0.X|Required if MySQL (or Percona) is used as Zabbix backend database. InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*MariaDB*|10.5.00-10.6.X|InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*Oracle*|19c - 21c|Required if Oracle is used as Zabbix backend database.| |*PostgreSQL*|13.0 - 14.X|Required if PostgreSQL is used as Zabbix backend database.| |*TimescaleDB* for PostgreSQL|2.0.1-2.3|Required if TimescaleDB is used as Zabbix backend database. Make sure to install the distribution of TimescaleDB with the compression supported.| |*SQLite*|3.3.5-3.34.X|SQLite is only supported with Zabbix proxies. Required if SQLite is used as Zabbix proxy database.|  ::: noteclassic  Although Zabbix can work with databases available in the operating systems, for the best experience, we recommend using databases installed from the official database developer repositories.  :::
zh-cn	##### 数据库管理系统  |数据库软件|支持的版本|备注| |--------|------------------|--------| |*MySQL/Percona*|8.0.X|如果需要使用 MySQL (or Percona) 作为 Zabbix 后端数据库。 需要 InnoDB engine 。 我们推荐使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 来构建 server/proxy。| |*MariaDB*|10.5.00-10.6.X|需要 InnoDB engine 。我们推荐使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 来构建 server/proxy。| |*Oracle*|19c - 21c|如果需要使用 Oracle 作为 Zabbix 后端数据库。| |*PostgreSQL*|13.0 - 14.X|如果需要使用 PostgreSQL 作为 Zabbix 后端数据库。| |*TimescaleDB* for PostgreSQL|2.0.1-2.3|如果需要使用 TimescaleDB 作为 Zabbix 后端数据库。确保安装的 TimescaleDB 发行版支持压缩。| |*SQLite*|3.3.5-3.34.X|如果需要使用 SQLite 作为 Zabbix 后端数据库。 SQLite 只支持 Zabbix proxy。|  ::: noteclassic 尽管 Zabbix 可以使用操作系统中可用的数据库，但为了获得最佳体验，我们建议使用从官方数据库开发者仓库安装的数据库。 :::

en-us	##### Database management system  |Software|Supported versions|Comments| |--------|------------------|--------| |*MySQL/Percona*|8.0.X|Required if MySQL (or Percona) is used as Zabbix backend database. InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*MariaDB*|10.5.00-10.6.X|InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*Oracle*|19c - 21c|Required if Oracle is used as Zabbix backend database.| |*PostgreSQL*|13.X|Required if PostgreSQL is used as Zabbix backend database.| |*TimescaleDB* for PostgreSQL|2.0.1-2.3|Required if TimescaleDB is used as Zabbix backend database. Make sure to install the distribution of TimescaleDB with the compression supported.| |*SQLite*|3.3.5-3.34.X|SQLite is only supported with Zabbix proxies. Required if SQLite is used as Zabbix proxy database.|  ::: noteclassic  Although Zabbix can work with databases available in the operating systems, for the best experience, we recommend using databases installed from the official database developer repositories.  :::  
zh-cn	##### 数据库管理系统  |数据库软件|支持的版本|备注| |--------|------------------|--------| |*MySQL/Percona*|8.0.X|如果需要使用 MySQL (or Percona) 作为 Zabbix 后端数据库。 需要 InnoDB engine 。 我们推荐使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 来构建 server/proxy。| |*MariaDB*|10.5.00-10.6.X|需要 InnoDB engine 。 我们推荐使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 来构建 server/proxy。| |*Oracle*|19c - 21c|如果需要使用 Oracle 作为 Zabbix 后端数据库。| |*PostgreSQL*|13.X|如果需要使用 PostgreSQL 作为 Zabbix 后端数据库。| |*TimescaleDB* for PostgreSQL|2.0.1-2.3|如果需要使用 TimescaleDB 作为 Zabbix 后端数据库。确保安装的 TimescaleDB 发行版支持压缩。| |*SQLite*|3.3.5-3.34.X| 如果需要使用 SQLite 作为 Zabbix 后端数据库。 SQLite 只支持 Zabbix proxy。|  ::: noteclassic 尽管 Zabbix 可以使用操作系统中可用的数据库，但为了获得最佳体验，我们建议使用从官方数据库开发者仓库安装的数据库。  :::  

en-us	#### Database size  Zabbix configuration data require a fixed amount of disk space and do not grow much.  Zabbix database size mainly depends on these variables, which define the amount of stored historical data:  -   Number of processed values per second  This is the average number of new values Zabbix server receives every second. For example, if we have 3000 items for monitoring with a refresh rate of 60 seconds, the number of values per second is calculated as 3000/60 = **50**.  It means that 50 new values are added to Zabbix database every second.  -   Housekeeper settings for history  Zabbix keeps values for a fixed period of time, normally several weeks or months. Each new value requires a certain amount of disk space for data and index.  So, if we would like to keep 30 days of history and we receive 50 values per second, the total number of values will be around (**30**\*24\*3600)\* **50** = 129.600.000, or about 130M of values.  Depending on the database engine used, type of received values (floats, integers, strings, log files, etc), the disk space for keeping a single value may vary from 40 bytes to hundreds of bytes. Normally it is around 90 bytes per value for numeric items^**2**^. In our case, it means that 130M of values will require 130M \* 90 bytes = **10.9GB** of disk space.  ::: noteclassic The size of text/log item values is impossible to predict exactly, but you may expect around 500 bytes per value. :::  -   Housekeeper setting for trends  Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table **trends**. The data is used for trending and long period graphs. The one hour period can not be customized.  Zabbix database, depending on the database type, requires about 90 bytes per each total. Suppose we would like to keep trend data for 5 years. Values for 3000 items will require 3000\*24\*365\* **90** = **2.2GB** per year, or **11GB** for 5 years.  -   Housekeeper settings for events  Each Zabbix event requires approximately 250 bytes of disk space^**1**^. It is hard to estimate the number of events generated by Zabbix daily. In the worst-case scenario, we may assume that Zabbix generates one event per second.  For each recovered event, an event\_recovery record is created. Normally most of the events will be recovered so we can assume one event\_recovery record per event. That means additional 80 bytes per event.  Optionally events can have tags, each tag record requiring approximately 100 bytes of disk space^**1**^. The number of tags per event (\#tags) depends on configuration. So each will need an additional \#tags \* 100 bytes of disk space.  It means that if we want to keep 3 years of events, this would require 3\*365\*24\*3600\* (250+80+\#tags\*100) = **\~30GB**+\#tags\*100B disk space^**2**^.  ::: noteclassic  ^**1**^ More when having non-ASCII event names, tags and values.  ^**2**^ The size approximations are based on MySQL and might be different for other databases.  :::  The table contains formulas that can be used to calculate the disk space required for Zabbix system:  |Parameter|Formula for required disk space (in bytes)| |---------|------------------------------------------| |*Zabbix configuration*|Fixed size. Normally 10MB or less.| |*History*|days\*(items/refresh rate)\*24\*3600\*bytes<br>items : number of items<br>days : number of days to keep history<br>refresh rate : average refresh rate of items<br>bytes : number of bytes required to keep single value, depends on database engine, normally \~90 bytes.| |*Trends*|days\*(items/3600)\*24\*3600\*bytes<br>items : number of items<br>days : number of days to keep history<br>bytes : number of bytes required to keep single trend, depends on the database engine, normally \~90 bytes.| |*Events*|days\*events\*24\*3600\*bytes<br>events : number of event per second. One (1) event per second in worst-case scenario.<br>days : number of days to keep history<br>bytes : number of bytes required to keep single trend, depends on the database engine, normally \~330 + average number of tags per event \* 100 bytes.|  So, the total required disk space can be calculated as:\ **Configuration + History + Trends + Events**\ The disk space will NOT be used immediately after Zabbix installation. Database size will grow then it will stop growing at some point, which depends on housekeeper settings.
zh-cn	#### 数据库大小  Zabbix 配置文件数据需要固定数量的磁盘空间，且增长不大。  Zabbix 数据库大小主要取决于这些变量，这些变量决定了存储的历史数据量：  -   每秒处理值的数量  这是 Zabbix server 每秒接收的新值的平均数。 例如，如果有3000个监控项用于监控，取值间隔为60秒，则这个值的数量计算为 3000/60 = ** 50 **。  这意味着每秒有 50 个新值被添加到 Zabbix 数据库中。  -   Housekeeper 的历史记录设置  Zabbix 将接收到的值保存一段固定的时间，通常为几周或几个月。 每个新值都需要一定量的磁盘空间用于数据和索引。  所以，如果我们每秒收到 50 个值，且希望保留 30 天的历史数据，值的总数将大约在 (**30**\*24\*3600)\* **50** = 129.600.000，即大约 130M 个值。  根据所使用的数据库引擎，接收值的类型（浮点数、整数、字符串、日志文件等），单个值的磁盘空间可能在 40 字节到数百字节之间变化。通常，数值类型的每个值大约为 90 个字节^**2**^。在上面的例子中，这意味着 130M 个值需要占用 130M \* 90 bytes = **10.9GB** 磁盘空间。  ::: noteclassic 文本/日志类型的监控项值的大小是无法确定的，但可以以每个值大约 500 字节来计算。 :::  -   Housekeeper 的趋势记录设置  Zabbix 为表 **trends** 中的每个项目保留1小时的最大值 / 最小值 / 平均值 / 统计值。该数据用于趋势图形和历史数据图形。这一个小时的时间段是无法自定义。  Zabbix数据库，根据数据库类型，每个值总共需要大约90个字节。假设我们希望将趋势数据保持5年。3000 个监控项的值每年需要占用 3000\*24\*365\* **90** = **2.2GB**，或者5年需要占用 **11GB** 。  -   Housekeeper 的事件记录设置  每个 Zabbix 事件需要大约 250 个字节的磁盘空间^**1**^。很难估计 Zabbix 每天生成的事件数量。 在最坏的情况下，假设 Zabbix 每秒生成一个事件。  对于每个恢复的事件，将创建一个event_recovery记录。通常，大多数事件将被恢复，因此我们可以假设每个事件有一个 event_recovery 记录。这意味着每个事件额外 80 个字节。  （可选）事件可以具有标记，每个标记记录需要大约 100 字节的磁盘空间^**1**^。每个事件的标签数 (\#tags)取决于配置。因此，每个事件都需要额外的 标签数\#tags * 100 字节 的磁盘空间。  这意味着如果想要保留3年的事件，这将需要 3\*365\*24\*3600\* (250+80+ 标签数\#tags\*100) = **\~30GB**+ 标签数\#tags\*100B 的磁盘空间^**2**^。  ::: noteclassic  ^**1**^ 当具有非 ASCII 的事件名称、标记和值时，需要的空间会更多。  ^**2**^ 大小近似值基于MySQL，对于其他数据库可能有所不同。 :::  下表包含可用于计算 Zabbix 系统所需磁盘空间的公式：  |类型|所需磁盘空间的公式 (字节)| |---------|------------------------------------------| |*Zabbix 配置*|固定大小。通常为 10MB 或更少。| |*历史数据*|days\*(items/refresh rate)\*24\*3600\*bytes<br> items：监控项数量<br>days：保留历史记录的天数<br>refresh rate：监控项的平均刷新率<br>bytes：保留单个值所需要占用的字节数，依赖于数据库引擎，通常为 \~90 字节。| |*趋势数据*|days\*(items/3600)\*24\*3600\*bytes<br>items：监控项数量<br>days：保留历史记录的天数<br>bytes：保留单个趋势数据所需要占用的字节数，依赖于数据库引擎，通常为 \~90 字节。| |*事件数据*|days\*events\*24\*3600\*bytes<br>events：每秒产生的事件数量。假设最糟糕的情况下，每秒产生 1 个事件。<br>days：保留历史数据的天数。<br>bytes：保留单个趋势数据所需的字节数，取决于数据库引擎，通常为 \~330 + 每个事件的平均标签数 \* 100 字节。|  因此，所需要的磁盘总空间按下列方法计算：\ **Zabbix 配置 + 历史数据 + 趋势数据 + 事件数据**\ 在安装 Zabbix 后**不会**立即使用磁盘空间。 数据库大小取决于 housekeeper 设置，在某些时间点增长或停止增长。

en-us	### Databases  To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.  Starting from Zabbix 6.0, the following [database](/manual/installation/requirements#software) versions are officially supported:  -   *MySQL/Percona* 8.0.X -   *MariaDB* 10.5.X - 10.6.X -   *PostgreSQL* 13.X - 14.X -   *Oracle* 19c - 21c -   *TimescaleDB* 2.0.1-2.3 -   *SQLite* 3.3.5-3.34.X  By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the [server](/manual/appendix/config/zabbix_server) or [proxy](/manual/appendix/config/zabbix_proxy).
zh-cn	### 数据库  为了创造最佳的用户体验并确保在各种生产环境中获得最佳的 Zabbix 性能，已经放弃了对一些旧数据库版本的支持。这主要适用于接近使用寿命的数据库版本以及存在可能会干扰正常性能的未修复问题的版本。  从 Zabbix 6.0 开始，官方支持以下 [数据库](/manual/installation/requirements#Software) 版本：  -   *MySQL/Percona* 8.0.X -   *MariaDB* 10.5.X - 10.6.X -   *PostgreSQL* 13.X - 14.X -   *Oracle* 19c - 21c -   *TimescaleDB* 2.0.1-2.3 -   *SQLite* 3.3.5-3.34.X  默认情况下，如果检测到不支持的数据库版本，Zabbix server 和 proxy 将不会启动。虽然不推荐，但现在可以通过修改 [server](/manual/appendix/config/zabbix_server) 或 [proxy](/manual/appendix/config/zabbix_proxy) 的 AllowUnsupportedDBVersions 配置参数来关闭数据库版本检查。

en-us	### Databases  To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.  Starting from Zabbix 6.0, the following [database](/manual/installation/requirements#Software) versions are officially supported:  -   *MySQL/Percona* 8.0.X -   *MariaDB* 10.5.X - 10.6.X -   *PostgreSQL* 13.X -   *Oracle* 19c - 21c -   *TimescaleDB* 2.0.1-2.3 -   *SQLite* 3.3.5-3.34.X  By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the [server](/manual/appendix/config/zabbix_server) or [proxy](/manual/appendix/config/zabbix_proxy).  
zh-cn	### JavaScript methods  HTTP methods PATCH, HEAD, OPTIONS, TRACE, CONNECT have been added to the JavaScript engine. Also, the engine now allows sending custom HTTP method requests with the new JS method HttpRequest.customRequest.  See also: [Additional JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects).  

en-us	##### Databases  To create the optimal user experience and ensure the best Zabbix performance in various production environments, the support of some older database releases has been dropped. This primarily applies to the database versions that are nearing their end of service life point and versions with unfixed issues that may interfere with normal performance.  Starting from Zabbix 6.0, the following [database](/manual/installation/requirements#Software) versions are officially supported:  -   *MySQL/Percona* 8.0.X -   *MariaDB* 10.5.X - 10.6.X -   *PostgreSQL* 13.X -   *Oracle* 19c - 21c -   *TimescaleDB* 2.0.1-2.3 -   *SQLite* 3.3.5-3.34.X  By default, Zabbix server and proxy will not start if an unsupported database version is detected. It is now possible, though not recommended, to turn off DB version check by modifying AllowUnsupportedDBVersions configuration parameter for the [server](/manual/appendix/config/zabbix_server) or [proxy](/manual/appendix/config/zabbix_proxy).
zh-cn	##### 数据库  为了创造最佳的用户体验并确保在各种生产环境中获得最佳的 Zabbix 性能，已经放弃了对一些旧版本数据库的支持。这主要适用于接近使用寿命的数据库版本以及存在可能会干扰正常性能的未修复问题的版本。  从 Zabbix 6.0 开始，官方支持以下 [数据库](/manual/installation/requirements#Software) 版本：  -   *MySQL/Percona* 8.0.X -   *MariaDB* 10.5.X - 10.6.X -   *PostgreSQL* 13.X -   *Oracle* 19c - 21c -   *TimescaleDB* 2.0.1-2.3 -   *SQLite* 3.3.5-3.34.X  默认情况下，如果检测到不支持的数据库版本，Zabbix server 和 proxy 将不会启动。虽然不推荐，但现在可以通过修改 [server](/manual/appendix/config/zabbix_server) 或 [proxy](/manual/appendix/config/zabbix_proxy) 的 AllowUnsupportedDBVersions 配置参数来关闭数据库版本适配。

en-us	##### Database storage  All configuration information as well as the data gathered by Zabbix is stored in a database.
zh-cn	##### 数据存储  Zabbix 收集的所有配置信息以及数据都存储在数据库中。

en-us	##### Data collection with parameters  Use the {HOST.CONN} macro as parameter value and get a response with expanded macro:  -   Create an item with type "Script".\ -   Create a parameter:\     *Name:* host\     *Value:* {HOST.CONN}\ -   In the *Script* field, enter the following code:  ``` {.java} var request = new HttpRequest(); return request.post("https://postman-echo.com/post", JSON.parse(value)); ```
zh-cn	##### 带参数收集数据  使用宏{HOST.CONN} 作为参数值并获取响应：  - 创建一个监控项，类型选择”脚本“。 \ - 创建一个参数：\     *Name：* host\     *Value:* {HOST.CONN}\ - 在*脚本*字段填写下面的代码：  ``` {.java} var request = new HttpRequest(); return request.post("https://postman-echo.com/post", JSON.parse(value)); ```

en-us	#### Data flow  In addition it is important to take a step back and have a look at the overall data flow within Zabbix. In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on *Server X* you must first create a host entry for *Server X* followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.
zh-cn	#### 数据流  此外，回顾一下 Zabbix 中的整体数据流也是很重要的。为了创建一个收集数据的监控项，必须首先创建一个主机。另一方面 Zabbix 必须首先拥有一个监控项来创建触发器。必须有触发器才能创建动作。因此，如果你想收到 *服务器 X* 上的 CPU 负载过高的警报，必须首先为 *服务器 X* 创建一个主机条目，然后创建一个用于监控其 CPU 的监控项，然后是一个触发器，如果 CPU 过高则触发动作，然后通过通过动作操作向您发送电子邮件。这可能看起来像很多步骤，其实使用模板并不需要。而且，由于这种设计，可以自定义创建非常灵活的设置。

en-us	 ### DB schema update  A new column *name_upper* has been added to the database table **items**. The column contains a capitalized version of the item name or the LLD rule name. This change has been implemented to allow the use of the index with case-insensitive search for API query [optimization](#optimized-api-queries).
zh-cn	### 数据库模式更新  新列 *name_upper* 已添加到数据库表 **items**。 该列包含监控项名称或 LLD 规则名称的大写版本。 已实施此更改以允许使用不区分大小写的索引搜索 API 查询 [优化](#optimized-api-queries)。

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

en-us	### Debian/Ubuntu  Open the `/etc/apt/sources.list.d/zabbix.list` and uncomment "Zabbix unstable repository".       # Zabbix unstable repository     deb https://repo.zabbix.com/zabbix/5.5/debian bullseye main     deb-src https://repo.zabbix.com/zabbix/5.5/debian bullseye main
zh-cn	### Debian/Ubuntu  打开`/etc/apt/sources.list.d/zabbix.list`并取消注释“Zabbix unstable repository”。     · # Zabbix 不稳定的仓库  · deb https://repo.zabbix.com/zabbix/5.5/debian bullseye main  · deb-src https://repo.zabbix.com/zabbix/5.5/debian bullseye main

en-us	### Debug  Debug information of executed webhook script. The debug object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |logs|array|Array of [log entries](/manual/api/reference/script/object#Log entry).| |ms|string|Script execution duration in milliseconds.|
zh-cn	### 调试 运行的webhook脚本的调试信息。调试对象有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |logs|array|[日志条目]数组(/manual/api/reference/script/object#日志条目)。| |ms|string|脚本运行毫秒数。|

en-us	### Debug  Debug information of executed webhook script. The debug object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |logs|array|Array of [log entries](/manual/api/reference/script/object#Log entry).| |ms|string|Script execution duration in milliseconds.|
zh-cn	### 调试 运行的webhook脚本的调试信息。调试对象有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |logs|array|[日志条目]数组(/manual/api/reference/script/object#日志条目)。| |ms|string|脚本运行毫秒数。|

en-us	#### Debugging Java gateway  In case there are any problems with Java gateway or an error message that you see about an item in the frontend is not descriptive enough, you might wish to take a look at Java gateway log file.  By default, Java gateway logs its activities into /tmp/zabbix\_java.log file with log level "info". Sometimes that information is not enough and there is a need for information at log level "debug". In order to increase logging level, modify file lib/logback.xml and change the level attribute of <root> tag to "debug":      <root level="debug">       <appender-ref ref="FILE" />     </root>  Note that unlike Zabbix server or Zabbix proxy, there is no need to restart Zabbix Java gateway after changing logback.xml file - changes in logback.xml will be picked up automatically. When you are done with debugging, you can return the logging level to "info".  If you wish to log to a different file or a completely different medium like database, adjust logback.xml file to meet your needs. See [Logback Manual](http://logback.qos.ch/manual/) for more details.  Sometimes for debugging purposes it is useful to start Java gateway as a console application rather than a daemon. To do that, comment out PID\_FILE variable in settings.sh. If PID\_FILE is omitted, startup.sh script starts Java gateway as a console application and makes Logback use lib/logback-console.xml file instead, which not only logs to console, but has logging level "debug" enabled as well.  Finally, note that since Java gateway uses SLF4J for logging, you can replace Logback with the framework of your choice by placing an appropriate JAR file in lib directory. See [SLF4J Manual](http://www.slf4j.org/manual.html) for more details.
zh-cn	#### 调试Java网关  为了防止在 Java gateway 出现任何问题或在 Zabbix 前端看不到详细的报错信息的情况下，你可以通过 Java gateway 日志文件来查看。  默认情况下，Java gateway 将其活动日志记录到日志级别为 "info" 的 /tmp/zabbix_java.log 文件中。有时候，该日志信息可能不够详细，需要在日志级别为 "debug" 中获取。为了提升日志级别，需要修改 lib/logback.xml 文件，并将 <root> 标记的日志等级属性更改为 "debug"：      <root level="debug">       <appender-ref ref="FILE" />     </root>  值得注意的是，与 Zabbix server 或 Zabbix proxy 不同，更改 logback.xml 文件并不需要重启 Zabbix Java gateway，它会自动提交。当完成调试后，可以将日志级别还原成“info”。  如果希望将日志记录到其他文件或完全不同的介质，如数据库，那么只需要调整 logback.xml 文件。详见[Logback 手册](http://logback.qos.ch/manual/) 获取更多信息。  有时为了调试，将 Java 网关用作控制台应用比以守护进程来启动更方便。因此可以在 settings.sh 中注释掉 PID_FILE 变量，这时运行startup.sh 脚本启动 Java gateway 就会作为控制台应用来启动，并将 Logback 使用 lib/logback-console.xml 文件，这不仅会记录到控制台，还会启用日志级别 “debug”。  最后，请注意，由于 Java gateway 使用 SLF4J 来记录，您可以通过在 lib 目录放置合适的 JAR 文件来将 Logback 替换为您选中的框架。详见  [SLF4J 手册](http://www.slf4j.org/manual.html)  以获取更多信息。

en-us	#### Debugging Java gateway  Zabbix Java gateway log file is:      /var/log/zabbix/zabbix_java_gateway.log  If you like to increase the logging, edit the file:      /etc/zabbix/zabbix_java_gateway_logback.xml  and change `level="info"` to "debug" or even "trace" (for deep troubleshooting):      <configuration scan="true" scanPeriod="15 seconds">     [...]           <root level="info">                   <appender-ref ref="FILE" />           </root>      </configuration>
zh-cn	#### 调试 Java 网关  Zabbix Java 网关的日志路径：      /var/log/zabbix/zabbix_java_gateway.log  如果要增加日志记录，编辑以下文件：      /etc/zabbix/zabbix_java_gateway_logback.xml  并将`level="info"`更改为"debug"或"trace"（深度排错模式）      <configuration scan="true" scanPeriod="15 seconds">     [...]           <root level="info">                   <appender-ref ref="FILE" />           </root>      </configuration>

en-us	#### Debugging Java gateway  Zabbix Java gateway log file is:      /var/log/zabbix/zabbix_java_gateway.log  If you like to increase the logging, edit the file:      /etc/zabbix/zabbix_java_gateway_logback.xml  and change `level="info"` to "debug" or even "trace" (for deep troubleshooting):      <configuration scan="true" scanPeriod="15 seconds">     [...]           <root level="info">                   <appender-ref ref="FILE" />           </root>      </configuration>
zh-cn	#### 调试 Java 网关  Zabbix Java 网关的日志路径：      /var/log/zabbix/zabbix_java_gateway.log  如果要增加日志记录，编辑以下文件：      /etc/zabbix/zabbix_java_gateway_logback.xml  并将`level="info"`更改为"debug"或"trace"（深度排错模式）      <configuration scan="true" scanPeriod="15 seconds">     [...]           <root level="info">                   <appender-ref ref="FILE" />           </root>      </configuration>

en-us	### Default authentication  By default, Zabbix uses internal Zabbix authentication for all users. It is possible to change the default method to [LDAP](#ldap_authentication) system-wide or enable LDAP authentication only for specific user groups.  To set LDAP as default authentication method for all users, navigate to the *LDAP* tab and configure authentication parameters, then return to the *Authentication* tab and switch *Default authentication* selector to LDAP.  Note that the authentication method can be fine-tuned on the [user group](/manual/config/users_and_usergroups/usergroup) level. Even if LDAP authentication is set globally, some user groups can still be authenticated by Zabbix. These groups must have [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) set to Internal. Vice versa, if internal authentication is used globally, LDAP authentication details can be specified and used for specific user groups whose [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) is set to LDAP. If a user is included into at least one user group with LDAP authentication, this user will not be able to use internal authentication method.  [HTTP](#http_authentication) and [SAML 2.0](#saml_authentication) authentication methods can be used in addition to the default authentication method.
zh-cn	### 默认身份验证  默认情况下，Zabbix 对所有用户使用内部 Zabbix 身份验证。可以将默认方法更改为 [LDAP](#ldap_authentication) 系统范围或仅对特定用户组启用 LDAP 身份验证。  要将 LDAP 设置为所有用户的默认身份验证方法，请导航至*LDAP* 选项卡并配置身份验证参数，然后返回*Authentication* 选项卡并将 *Default authentication* 选择器切换到LDAP  请注意，身份验证方法可以在 [用户组](/manual/config/users_and_usergroups/usergroup) 级别。即使LDAP认证全局设置，部分用户组仍然可以 由 Zabbix 认证。这些组必须有 [前端访问](/manual/config/users_and_usergroups/usergroup#configuration) 设置到内部。反之亦然，如果全局使用内部身份验证，可以为特定用户指定和使用 LDAP 身份验证详细信息 [前端访问](/manual/config/users_and_usergroups/usergroup#configuration) 是设置为 LDAP。如果一个用户包含在至少一个用户组中LDAP 认证，此用户将无法使用内部身份验证方法。  [HTTP](#http_authentication) 和 [SAML 2.0](#saml_authentication)除了默认的身份验证方法之外，还可以使用身份验证方法身份验证方法。

en-us	### Default authentication  By default, Zabbix uses internal Zabbix authentication for all users. It is possible to change the default method to [LDAP](#ldap_authentication) system-wide or enable LDAP authentication only for specific user groups.  To set LDAP as default authentication method for all users, navigate to the *LDAP* tab and configure authentication parameters, then return to the *Authentication* tab and switch *Default authentication* selector to LDAP.  Note that the authentication method can be fine-tuned on the [user group](/manual/config/users_and_usergroups/usergroup) level. Even if LDAP authentication is set globally, some user groups can still be authenticated by Zabbix. These groups must have [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) set to Internal. Vice versa, if internal authentication is used globally, LDAP authentication details can be specified and used for specific user groups whose [frontend access](/manual/config/users_and_usergroups/usergroup#configuration) is set to LDAP. If a user is included into at least one user group with LDAP authentication, this user will not be able to use internal authentication method.  [HTTP](#HTTP_authentication) and [SAML 2.0](#SAML_authentication) authentication methods can be used in addition to the default authentication method.  
zh-cn	##### Internal  使用内部Zabbix认证。  

en-us	#### Default global regular expressions  Zabbix comes with several global regular expression in its default dataset.  |Name|Expression|Matches| |----|----------|-------| |*File systems for discovery*|`^(btrfs\|ext2\|ext3\|ext4\|jfs\|reiser\|xfs\|ffs\|ufs\|jfs\|jfs2\|vxfs\|hfs\|refs\|apfs\|ntfs\|fat32\|zfs)$`|"btrfs" or "ext2" or "ext3" or "ext4" or "jfs" or "reiser" or "xfs" or "ffs" or "ufs" or "jfs" or "jfs2" or "vxfs" or "hfs" or "refs" or "apfs" or "ntfs" or "fat32" or "zfs"| |*Network interfaces for discovery*|`^Software Loopback Interface`|Strings starting with "Software Loopback Interface".| |<|`^lo$`|"lo"| |<|`^(In)?[Ll]oop[Bb]ack[0-9._]*$`|Strings that optionally start with "In", then have "L" or "l", then "oop", then "B" or "b", then "ack", which can be optionally followed by any number of digits, dots or underscores.| |<|`^NULL[0-9.]*$`|Strings starting with "NULL" optionally followed by any number of digits or dots.| |<|`^[Ll]o[0-9.]*$`|Strings starting with "Lo" or "lo" and optionally followed by any number of digits or dots.| |<|`^[Ss]ystem$`|"System" or "system"| |<|`^Nu[0-9.]*$`|Strings starting with "Nu" optionally followed by any number of digits or dots.| |*Storage devices for SNMP discovery*|`^(Physical memory\|Virtual memory\|Memory buffers\|Cached memory\|Swap space)$`|"Physical memory" or "Virtual memory" or "Memory buffers" or "Cached memory" or "Swap space"| |*Windows service names for discovery*|`^(MMCSS\|gupdate\|SysmonLog\|clr_optimization_v2.0.50727_32\|clr_optimization_v4.0.30319_32)$`|"MMCSS" or "gupdate" or "SysmonLog" or strings like "clr\_optimization\_v2.0.50727\_32" and "clr\_optimization\_v4.0.30319\_32" where instead of dots you can put any character except newline.| |*Windows service startup states for discovery*|`^(automatic\|automatic delayed)$`|"automatic" or "automatic delayed"|
zh-cn	#### 默认全局正则表达式  Zabbix在其默认数据集中提供了几个全局正则表达式。  |名字|表达式|匹配结果| |----|----------|-------| |*用于发现的文件系统*|`^(btrfs\|ext2\|ext3\|ext4\|jfs\|reiser\|xfs\|ffs\|ufs\|jfs\|jfs2\|vxfs\|hfs\|refs\|apfs\|ntfs\|fat32\|zfs)$`|"btrfs" 或 "ext2" 或 "ext3" 或 "ext4" 或 "jfs" 或 "reiser" 或 "xfs" 或 "ffs" 或 "ufs" 或 "jfs" 或 "jfs2" 或 "vxfs" 或 "hfs" 或 "refs" 或 "apfs" 或 "ntfs" 或 "fat32" 或 "zfs"| |*用于发现的网络接口*|`^Software Loopback Interface`|以 "Software Loopback Interface（软件环回接口）" 开头的字符串。| |<|`^lo$`|"lo"| |<|`^(In)?[Ll]oop[Bb]ack[0-9._]*$`|以 "In" 为开头，接着是 "L" 或 "l"，然后是 "oop"，然后 "B" 或 "b"，再然后 "ack" 组合的字符串。可以选择后跟任意数量的数字、点或下划线。| |<|`^NULL[0-9.]*$`|以 "NULL" 开头的后可选地跟任意数量的数字或点的字符串。| |<|`^[Ll]o[0-9.]*$`|以 "Lo" 或 "lo" 开头的后跟任意数量的数字或点的字符串。| |<|`^[Ss]ystem$`|匹配 "System" 或 "system"。| |<|`^Nu[0-9.]*$`|以 "Nu" 开头的后可选地跟任意数量的数字或点的字符串。| |*用于 SNMP 发现的存储设备*|`^(Physical memory\|Virtual memory\|Memory buffers\|Cached memory\|Swap space)$`|"Physical memory" 或 "Virtual memory" 或 "Memory buffers" 或 "Cached memory" 或 "Swap space"。| |*用于发现的 Windows 服务名称*|`^(MMCSS\|gupdate\|SysmonLog\|clr_optimization_v2.0.50727_32\|clr_optimization_v4.0.30319_32)$`|"MMCSS" 或 "gupdate" 或 "SysmonLog" 或类似于 "clr\_optimization\_v2.0.50727\_32" 和 "clr\_optimization\_v4.0.30319\_32" 的除了换行符之外可以放置​​任何字符代替点的字符串。| |*用于发现的 Windows 服务启动状态*|`^(automatic\|automatic delayed)$`|"automatic（自动）" 或 "automatic delayed（自动延迟）"。|

en-us	 #### Default port numbers  The following list of open ports per component is applicable for default configuration:  |Zabbix component|Port number|Protocol|Type of connection| |-------|-------|-------|-------| |Zabbix agent|10050|TCP|on demand| |Zabbix agent 2|10050|TCP|on demand| |Zabbix server|10051|TCP|on demand| |Zabbix proxy|10051|TCP|on demand| |Zabbix Java gateway|10052|TCP|on demand| |Zabbix web service|10053|TCP|on demand| |Zabbix frontend|80|HTTP|on demand| |^|443|HTTPS|on demand| |Zabbix trapper|10051 |TCP| on demand|  ::: noteclassic The port numbers should be open in firewall to enable Zabbix communications. Outgoing TCP connections usually do not require explicit firewall settings. ::: 
zh-cn	#### 默认端口号  以下每个组件的开放端口列表适用于默认配置：  |Zabbix 组件|端口号|协议|连接类型| |--------|--------|--------|--------| |Zabbix agent|10050|TCP|on demand| |Zabbix agent 2|10050|TCP|on demand| |Zabbix server|10051|TCP|on demand| |Zabbix proxy|10051|TCP|on demand| |Zabbix Java gateway|10052|TCP|on demand| |Zabbix web service|10053|TCP|on demand| |Zabbix frontend|80|HTTP|on demand| |^|443|HTTPS|on demand| |Zabbix trapper|10051 |TCP| on demand|  ::: noteclassic 端口号应在防火墙中打开以启用 Zabbix 通信。 向外访问的TCP连接通常不需要明确的防火墙设置。 ::::

en-us	#### Default user roles  By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions:  -   Admin role -   Guest role -   Super admin role -   User role  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  Default *Super admin role* cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix.  :::  Zabbix users with type Super admins and proper permissions can modify or delete existing roles or create new custom roles.  To create a new role, click on the *Create user role* button at the top right corner. To update an existing role, press on the role name to open the configuration form.  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Available permission options along with default permission sets for pre-existing user roles in Zabbix are described below.  |Parameter|Description|Default user roles|<|<|<| |---------|-----------|------------------|-|-|-| | | |Super admin role|Admin role|User role|Guest role| |Name|Role visible name.|Super admin role|Admin role|User role|Guest role| |User type|Selected user type determines the list of available permissions.<br>Upon selecting a user type, all available permissions for this user type are granted by default.<br>Uncheck the checkbox(es) to revoke certain permissions for the user role.<br>Checkboxes for permissions not available for this user type are grayed out.|Super admin|Admin|User|User| |Access to UI elements|<|<|<|<|<| |*Monitoring*|<|<|<|<|<| |Dashboard|Enable/disable access to a specific Monitoring menu section and underlying pages.|Yes|Yes|Yes|Yes| |Problems|^|^|^|^|^| |Hosts|^|^|^|^|^| |Latest data|^|^|^|^|^| |Maps|^|^|^|^|^| |Discovery|^|^|^|No|No| |*Services*|<|<|<|<|<| |Services|Enable/disable access to a specific Services menu section and underlying pages.|Yes|Yes|Yes|Yes| |Service actions|^|^|^|^|^| |SLA|^|^|^|^|^| |SLA report|^|^|^|^|^| |*Inventory*|<|<|<|<|<| |Overview|Enable/disable access to a specific Inventory menu section and underlying pages.|Yes|Yes|Yes|Yes| |Hosts|^|^|^|^|^| |*Reports*|<|<|<|<|<| |System information|Enable/disable access to a specific Reports menu section and underlying pages.|Yes|No|No|No| |Availability report|^|^|Yes|Yes|Yes| |Triggers top 100|^|^|^|^|^| |Audit|^|^|No|No|No| |Action log|^|^|^|^|^| |Notifications|^|^|Yes|^|^| |Scheduled reports|^|^|^|^|^| |*Configuration*|<|<|<|<|<| |Host groups|Enable/disable access to a specific *Configuration* menu section and underlying pages.|Yes|Yes|No|No| |Templates|^|^|^|^|^| |Hosts|^|^|^|^|^| |Maintenance|^|^|^|^|^| |Actions|^|^|^|^|^| |Event correlation|^|^|No|^|^| |Discovery|^|^|Yes|^|^| |*Administration*|<|<|<|<|<| |General|Enable/disable access to a specific *Administration* menu section and underlying pages.|Yes|No|No|No| |Proxies|^|^|^|^|^| |Authentication|^|^|^|^|^| |User groups|^|^|^|^|^| |User roles|^|^|^|^|^| |Users|^|^|^|^|^| |Media types|^|^|^|^|^| |Scripts|^|^|^|^|^| |Queue|^|^|^|^|^| |*Default access to new UI elements*|Enable/disable access to the custom UI elements. Modules, if present, will be listed below.|Yes|Yes|Yes|Yes| |Access to services|<|<|<|<|<| |Read-write access to services|Select read-write access to services:<br>**None** - no access at all<br>**All** - access to all services is read-write<br>**Service list** - select services for read-write access<br><br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|Yes|Yes|No|No| |Read-write access to services with tag|Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-write access to services* parameter.<br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services|Select read-only access to services:<br>**None** - no access at all<br>**All** - access to all services is read-only<br>**Service list** - select services for read-only access<br><br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services with tag|Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-only access to services* parameter.<br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Access to modules|<|<|<|<|<| |<Module name>|Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.|Yes|Yes|Yes|Yes| |*Default access to new modules*|Enable/disable access to modules that may be added in the future.|^|^|^|^| |Access to API|<|<|<|<|<| |*Enabled*|Enable/disable access to API.|Yes|Yes|Yes|No| |*API methods*|Select *Allow list* to allow only specified API methods or *Deny list* to restrict only specified API methods.<br><br>In the search field, start typing the method name, then select the method from the auto-complete list.<br>You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action.<br><br>Wildcards are supported. Examples: `dashboard.*` (all methods of 'dashboard.' API service) `*` (any method), `*.export` (methods with '.export' name from all API services).<br><br>If no methods have been specified the Allow/Deny list rule will be ignored.|^|^|^|^| |Access to actions|<|<|<|<|<| |Create and edit dashboards|Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.|Yes|Yes|Yes|No| |Create and edit maps|^|^|^|^|^| |Create and edit maintenance|^|^|^|No|^| |Add problem comments|Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.|^|^|Yes|^| |Change severity|^|^|^|^|^| |Acknowledge problems|^|^|^|^|^| |Close problems|^|^|^|^|^| |Execute scripts|Clearing this checkbox will also revoke the rights to use the `script.execute` API method.|^|^|^|^| |Manage API tokens|Clearing this checkbox will also revoke the rights to use all `token.` API methods.|^|^|^|^| |Manage scheduled reports|Clearing this checkbox will also revoke the rights to use all `report.` API methods.|^|^|No|^| |Manage SLA|Enable/disable the rights to manage [SLA](/manual/web_interface/frontend_sections/services/sla).|^|^|^|^| |Default access to new actions|Enable/disable access to new actions.|^|^|Yes|^|  Notes:  -   Each user may have only one role assigned. -   If an element is restricted, users will not be able to access it     even by entering a direct URL to this element into the browser. -   Users of type *User* or *Admin* cannot change their own role     settings. -   Users of type *Super admin* can modify settings of their own role     (not available for the default *Super admin role*), but not the user     type. -   Users of all levels cannot change their own user type.  See also:  -   [Configuring a user](/manual/config/users_and_usergroups/user)
zh-cn	#### 默认用户角色  默认情况下，Zabbix 配置了四个用户角色，它们具有一组预定义的权限：  - · 管理员角色 - · 嘉宾角色 - · 超级管理员角色 - · 用户角色  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  默认 *超级管理员角色* 不能修改或删除，因为 Zabbix 中必须至少存在一个具有无限权限的超级管理员。 :::  具有超级管理员类型和适当权限的 Zabbix 用户可以修改或删除现有角色或创建新的自定义角色。  要创建新角色，请单击右上角的*创建用户角色*按钮。要更新现有角色，请按角色名称以打开配置表单。  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Zabbix 中预先存在的用户角色的可用权限选项以及默认权限集如下所述。  |参数|说明|默认用户角色|<|<|<| |---------|-----------|------|-|-|-| | | |超级管理员角色|管理员角色|用户角色|访客角色| |名称|角色可见名称。|超级管理员角色|管理员角色|用户角色|访客角色| |用户类型|选定的用户类型决定了可用权限的列表。<br>选择用户类型后，默认情况下会授予此用户类型的所有可用权限。<br>取消选中该复选框可撤消该用户的某些权限用户角色。<br>此用户类型不可用的权限复选框呈灰色显示。|超级管理员|管理员|用户|用户| |访问 UI 元素|<|<|<|<|<| |*监控*|<|<|<|<|<| |仪表板|启用/禁用对特定监控菜单部分和基础页面的访问。|是|是|是|是| |问题|^|^|^|^|^| |主机|^|^|^|^|^| |最新数据|^|^|^|^|^| |地图|^|^|^|^|^| |发现|^|^|^|否|否| |*服务*|<|<|<|<|<| |服务|启用/禁用对特定服务菜单部分和基础页面的访问。|是|是|是|是| |服务行动|^|^|^|^|^| |SLA|^|^|^|^|^| |SLA 报告|^|^|^|^|^| |*资产管理*|<|<|<|<|<| |概览|启用/禁用对特定库存菜单部分和基础页面的访问。|是|是|是|是| |主机|^|^|^|^|^| |*报告*|<|<|<|<|<| |系统信息|启用/禁用对特定报告菜单部分和基础页面的访问。|是|否|否|否| |可用性报告|^|^|是|是|是| |触发前 100 名|^|^|^|^|^| |审核|^|^|否|否|否| |动作日志|^|^|^|^|^| |通知|^|^|是|^|^| |预定报告|^|^|^|^|^| |*配置*|<|<|<|<|<| |主机组|启用/禁用对特定*配置*菜单部分和基础页面的访问。|是|是|否|否| |模板|^|^|^|^|^| |主机|^|^|^|^|^| |维护|^|^|^|^|^| |动作|^|^|^|^|^| |事件关联|^|^|否|^|^| |发现|^|^|是|^|^| |*管理*|<|<|<|<|<| |常规|启用/禁用对特定*管理*菜单部分和基础页面的访问。|是|否|否|否| |proxies|^|^|^|^|^| |认证|^|^|^|^|^| |用户组|^|^|^|^|^| |用户角色|^|^|^|^|^| |用户|^|^|^|^|^| |媒介类型|^|^|^|^|^| |脚本|^|^|^|^|^| |队列|^|^|^|^|^| |*对新 UI 元素的默认访问*|启用/禁用对自定义 UI 元素的访问。模块，如果存在，将在下面列出。|是|是|是|是| |访问服务|<|<|<|<|<| |对服务的读写访问权限|选择对服务的读写访问权限：<br>**无** - 完全没有访问权限<br>**全部** - 对所有服务的访问权限为读写权限<br>* *服务列表** - 为读写访问选择服务<br><br>读写访问优先于只读访问，并由子服务动态继承。|是|是|否|否| |使用标签对服务进行读写访问|指定标签名称和可选的值，以额外授予对匹配标签的服务的读写访问权限。<br>如果在 *Read- 中选择了“服务列表”，则此选项可用对 services* 参数的写访问。<br>读写访问优先于只读访问，并由子服务动态继承。|^|^|^|^| |对服务的只读访问权限|选择对服务的只读访问权限：<br>**无** - 根本没有访问权限<br>**全部** - 对所有服务的访问权限都是只读的<br>* *服务列表** - 选择服务进行只读访问<br><br>只读访问不优先于读写访问，由子服务动态继承。|^|^|^| ^| |对带有标签的服务的只读访问权限|指定标签名称和（可选）值以额外授予对匹配标签的服务的只读访问权限。<br>如果在 *Read- 中选择了“服务列表”，则此选项可用仅访问 services* 参数。<br>只读访问不优先于读写访问，由子服务动态继承。|^|^|^|^| |访问模块|<|<|<|<|<| |<模块名称>|允许/拒绝对特定模块的访问。本节仅显示启用的模块。无法授予或限制对当前禁用的模块的访问权限。|是|是|是|是| |*对新模块的默认访问*|启用/禁用对将来可能添加的模块的访问。|^|^|^|^| |访问API|<|<|<|<|<| |*启用*|启用/禁用对 API 的访问。|是|是|是|否| |*API 方法*|选择*允许列表* 仅允许指定的 API 方法或选择*拒绝列表* 仅限制指定的 API 方法。<br><br>在搜索字段中，开始输入方法名称，然后选择方法从自动完成列表中。<br>您还可以按“选择”按钮并从可用于此用户类型的完整列表中选择方法。请注意，如果未选中“访问操作”块中的某些操作，用户将无法使用与该操作相关的 API 方法。<br><br>支持通配符。示例：`dashboard.*`（'dashboard.' API 服务的所有方法）`*`（任何方法）、`*.export`（来自所有 API 服务的具有 '.export' 名称的方法）。<br><br >如果没有指定方法，允许/拒绝列表规则将被忽略。|^|^|^|^| |访问操作|<|<|<|<|<| |创建和编辑仪表板|清除此复选框还将撤销对相应元素使用 `.create`、`.update` 和 `.delete` API 方法的权限。|是|是|是|否| |创建和编辑地图|^|^|^|^|^| |创建和编辑维护|^|^|^|否|^| |添加问题评论|清除此复选框还将撤销通过`event.acknowledge` API方法执行相应操作的权限。|^|^|是|^| |更改严重性|^|^|^|^|^| |确认问题|^|^|^|^|^| |关闭问题|^|^|^|^|^| |执行脚本|清除此复选框也将撤销使用 `script.execute` API 方法的权限。|^|^|^|^| |管理 API 令牌|清除此复选框还将撤销使用所有 `token.` API 方法的权利。|^|^|^|^| |管理预定报告|清除此复选框还将撤销使用所有“报告”API 方法的权利。|^|^|否|^| |管理 SLA|启用/禁用管理 [SLA](/manual/web_interface/frontend_sections/services/sla) 的权限。|^|^|^|^| |默认访问新操作|启用/禁用访问新操作。|^|^|是|^|  备注：  - · 每个用户只能分配一个角色。 - · 如果某个元素受到限制，即使在浏览器中输入指向该元素的直接 URL，用户也无法访问它。 - · *User* 或*Admin* 类型的用户不能更改他们自己的角色设置。 - · *超级管理员*类型的用户可以修改他们自己角色的设置（不适用于默认的*超级管理员角色*），但不能修改用户类型。 - · 各级用户不能更改自己的用户类型。  参阅：  - · [配置用户](/manual/config/users_and_usergroups/user)

en-us	#### Default user roles  By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions:  -   Admin role -   Guest role -   Super admin role -   User role  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  Default *Super admin role* cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix.  :::  Zabbix users with type Super admins and proper permissions can modify or delete existing roles or create new custom roles.  To create a new role, click on the *Create user role* button at the top right corner. To update an existing role, press on the role name to open the configuration form.  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Available permission options along with default permission sets for pre-existing user roles in Zabbix are described below.  |Parameter|Description|Default user roles|<|<|<| |---------|-----------|------------------|-|-|-| | | |Super admin role|Admin role|User role|Guest role| |Name|Role visible name.|Super admin role|Admin role|User role|Guest role| |User type|Selected user type determines the list of available permissions.<br>Upon selecting a user type, all available permissions for this user type are granted by default.<br>Uncheck the checkbox(es) to revoke certain permissions for the user role.<br>Checkboxes for permissions not available for this user type are grayed out.|Super admin|Admin|User|User| |Access to UI elements|<|<|<|<|<| |*Monitoring*|<|<|<|<|<| |Dashboard|Enable/disable access to a specific Monitoring menu section and underlying pages.|Yes|Yes|Yes|Yes| |Problems|^|^|^|^|^| |Hosts|^|^|^|^|^| |Latest data|^|^|^|^|^| |Maps|^|^|^|^|^| |Discovery|^|^|^|No|No| |Services|^|^|^|Yes|Yes| |*Inventory*|<|<|<|<|<| |Overview|Enable/disable access to a specific Inventory menu section and underlying pages.|Yes|Yes|Yes|Yes| |Hosts|^|^|^|^|^| |*Reports*|<|<|<|<|<| |System information|Enable/disable access to a specific Reports menu section and underlying pages.|Yes|No|No|No| |Availability report|^|^|Yes|Yes|Yes| |Triggers top 100|^|^|^|^|^| |Audit|^|^|No|No|No| |Action log|^|^|^|^|^| |Notifications|^|^|Yes|^|^| |Scheduled reports|^|^|^|^|^| |*Configuration*|<|<|<|<|<| |Host groups|Enable/disable access to a specific *Configuration* menu section and underlying pages.|Yes|Yes|No|No| |Templates|^|^|^|^|^| |Hosts|^|^|^|^|^| |Maintenance|^|^|^|^|^| |Actions|^|^|^|^|^| |Event correlation|^|^|No|^|^| |Discovery|^|^|Yes|^|^| |*Administration*|<|<|<|<|<| |General|Enable/disable access to a specific *Administration* menu section and underlying pages.|Yes|No|No|No| |Proxies|^|^|^|^|^| |Authentication|^|^|^|^|^| |User groups|^|^|^|^|^| |User roles|^|^|^|^|^| |Users|^|^|^|^|^| |Media types|^|^|^|^|^| |Scripts|^|^|^|^|^| |Queue|^|^|^|^|^| |*Default access to new UI elements*|Enable/disable access to the custom UI elements. Modules, if present, will be listed below.|Yes|Yes|Yes|Yes| |Access to services|<|<|<|<|<| |Read-write access to services|Select read-write access to services:<br>**None** - no access at all<br>**All** - access to all services is read-write<br>**Service list** - select services for read-write access<br><br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|Yes|Yes|No|No| |Read-write access to services with tag|Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-write access to services* parameter.<br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services|Select read-only access to services:<br>**None** - no access at all<br>**All** - access to all services is read-only<br>**Service list** - select services for read-only access<br><br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services with tag|Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-only access to services* parameter.<br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Access to modules|<|<|<|<|<| |<Module name>|Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.|Yes|Yes|Yes|Yes| |*Default access to new modules*|Enable/disable access to modules that may be added in the future.|^|^|^|^| |Access to API|<|<|<|<|<| |*Enabled*|Enable/disable access to API.|Yes|Yes|Yes|No| |*API methods*|Select *Allow list* to allow only specified API methods or *Deny list* to restrict only specified API methods.<br><br>In the search field, start typing the method name, then select the method from the auto-complete list.<br>You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action.<br><br>Wildcards are supported. Examples: `dashboard.*` (all methods of 'dashboard.' API service) `*` (any method), `*.export` (methods with '.export' name from all API services).<br><br>If no methods have been specified the Allow/Deny list rule will be ignored.|^|^|^|^| |Access to actions|<|<|<|<|<| |Create and edit dashboards|Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.|Yes|Yes|Yes|No| |Create and edit maps|^|^|^|^|^| |Create and edit maintenance|^|^|^|No|^| |Add problem comments|Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.|^|^|Yes|^| |Change severity|^|^|^|^|^| |Acknowledge problems|^|^|^|^|^| |Close problems|^|^|^|^|^| |Execute scripts|Clearing this checkbox will also revoke the rights to use the `script.execute` API method.|^|^|^|^| |Manage API tokens|Clearing this checkbox will also revoke the rights to use all `token.` API methods.|^|^|^|^| |Manage scheduled reports|Clearing this checkbox will also revoke the rights to use all `report.` API methods.|^|^|No|^| |Default access to new actions|Enable/disable access to new actions.|^|^|Yes|^|  Notes:  -   Each user may have only one role assigned. -   If an element is restricted, users will not be able to access it     even by entering a direct URL to this element into the browser. -   Users of type *User* or *Admin* cannot change their own role     settings. -   Users of type *Super admin* can modify settings of their own role     (not available for the default *Super admin role*), but not the user     type. -   Users of all levels cannot change their own user type.  See also:  -   [Configuring a user](/manual/config/users_and_usergroups/user)  
zh-cn	#### Default user roles  By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions:  -   Admin role -   Guest role -   Super admin role -   User role  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  Default *Super admin role* cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix.  :::  Zabbix users with type Super admins and proper permissions can modify or delete existing roles or create new custom roles.  To create a new role, click on the *Create user role* button at the top right corner. To update an existing role, press on the role name to open the configuration form.  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Available permission options along with default permission sets for pre-existing user roles in Zabbix are described below.  |Parameter|Description|Default user roles|<|<|<| |---------|-----------|------------------|-|-|-| |^|^|Super admin role|Admin role|User role|Guest role| |Name|Role visible name.|Super admin role|Admin role|User role|Guest role| |User type|Selected user type determines the list of available permissions.<br>Upon selecting a user type, all available permissions for this user type are granted by default.<br>Uncheck the checkbox(es) to revoke certain permissions for the user role.<br>Checkboxes for permissions not available for this user type are grayed out.|Super admin|Admin|User|User| |Access to UI elements|<|<|<|<|<| |*Monitoring*|<|<|<|<|<| |Dashboard|Enable/disable access to a specific Monitoring menu section and underlying pages.|Yes|Yes|Yes|Yes| |Problems|^|^|^|^|^| |Hosts|^|^|^|^|^| |Latest data|^|^|^|^|^| |Maps|^|^|^|^|^| |Discovery|^|^|^|No|No| |Services|^|^|^|Yes|Yes| |*Inventory*|<|<|<|<|<| |Overview|Enable/disable access to a specific Inventory menu section and underlying pages.|Yes|Yes|Yes|Yes| |Hosts|^|^|^|^|^| |*Reports*|<|<|<|<|<| |System information|Enable/disable access to a specific Reports menu section and underlying pages.|Yes|No|No|No| |Availability report|^|^|Yes|Yes|Yes| |Triggers top 100|^|^|^|^|^| |Audit|^|^|No|No|No| |Action log|^|^|^|^|^| |Notifications|^|^|Yes|^|^| |Scheduled reports|^|^|^|^|^| |*Configuration*|<|<|<|<|<| |Host groups|Enable/disable access to a specific *Configuration* menu section and underlying pages.|Yes|Yes|No|No| |Templates|^|^|^|^|^| |Hosts|^|^|^|^|^| |Maintenance|^|^|^|^|^| |Actions|^|^|^|^|^| |Event correlation|^|^|No|^|^| |Discovery|^|^|Yes|^|^| |*Administration*|<|<|<|<|<| |General|Enable/disable access to a specific *Administration* menu section and underlying pages.|Yes|No|No|No| |Proxies|^|^|^|^|^| |Authentication|^|^|^|^|^| |User groups|^|^|^|^|^| |User roles|^|^|^|^|^| |Users|^|^|^|^|^| |Media types|^|^|^|^|^| |Scripts|^|^|^|^|^| |Queue|^|^|^|^|^| |*Default access to new UI elements*|Enable/disable access to the custom UI elements. Modules, if present, will be listed below.|Yes|Yes|Yes|Yes| |Access to services|<|<|<|<|<| |Read-write access to services|Select read-write access to services:<br>**None** - no access at all<br>**All** - access to all services is read-write<br>**Service list** - select services for read-write access<br><br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|Yes|Yes|No|No| |Read-write access to services with tag|Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-write access to services* parameter.<br>The read-write access takes precedence over the read-only access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services|Select read-only access to services:<br>**None** - no access at all<br>**All** - access to all services is read-only<br>**Service list** - select services for read-only access<br><br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services with tag|Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-only access to services* parameter.<br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Access to modules|<|<|<|<|<| |<Module name>|Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.|Yes|Yes|Yes|Yes| |*Default access to new modules*|Enable/disable access to modules that may be added in the future.|^|^|^|^| |Access to API|<|<|<|<|<| |*Enabled*|Enable/disable access to API.|Yes|Yes|Yes|No| |*API methods*|Select *Allow list* to allow only specified API methods or *Deny list* to restrict only specified API methods.<br><br>In the search field, start typing the method name, then select the method from the auto-complete list.<br>You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action.<br><br>Wildcards are supported. Examples: `dashboard.*` (all methods of 'dashboard.' API service) `*` (any method), `*.export` (methods with '.export' name from all API services).<br><br>If no methods have been specified the Allow/Deny list rule will be ignored.|^|^|^|^| |Access to actions|<|<|<|<|<| |Create and edit dashboards|Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.|Yes|Yes|Yes|No| |Create and edit maps|^|^|^|^|^| |Create and edit maintenance|^|^|^|No|^| |Add problem comments|Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.|^|^|Yes|^| |Change severity|^|^|^|^|^| |Acknowledge problems|^|^|^|^|^| |Close problems|^|^|^|^|^| |Execute scripts|Clearing this checkbox will also revoke the rights to use the `script.execute` API method.|^|^|^|^| |Manage API tokens|Clearing this checkbox will also revoke the rights to use all `token.` API methods.|^|^|^|^| |Manage scheduled reports|Clearing this checkbox will also revoke the rights to use all `report.` API methods.|^|^|No|^| |Default access to new actions|Enable/disable access to new actions.|^|^|Yes|^|  Notes:  -   Each user may have only one role assigned. -   If an element is restricted, users will not be able to access it     even by entering a direct URL to this element into the browser. -   Users of type *User* or *Admin* cannot change their own role     settings. -   Users of type *Super admin* can modify settings of their own role     (not available for the default *Super admin role*), but not the user     type. -   Users of all levels cannot change their own user type.  See also:  -   [Configuring a user](/manual/config/users_and_usergroups/user)  

en-us	##### - Defining items  Each item is defined in a ZBX\_METRIC structure:  ``` {.c} typedef struct {     char        *key;     unsigned    flags;     int     (*function)();     char        *test_param; } ZBX_METRIC; ```  Here, **key** is the item key (e.g., "dummy.random"), **flags** is either CF\_HAVEPARAMS or 0 (depending on whether the item accepts parameters or not), **function** is a C function that implements the item (e.g., "zbx\_module\_dummy\_random"), and **test\_param** is the parameter list to be used when Zabbix agent is started with the "-p" flag (e.g., "1,1000", can be NULL). An example definition may look like this:  ``` {.c} static ZBX_METRIC keys[] = {     { "dummy.random", CF_HAVEPARAMS, zbx_module_dummy_random, "1,1000" },     { NULL } } ```  Each function that implements an item should accept two pointer parameters, the first one of type AGENT\_REQUEST and the second one of type AGENT\_RESULT:  ``` {.c} int zbx_module_dummy_random(AGENT_REQUEST *request, AGENT_RESULT *result) {     ...      SET_UI64_RESULT(result, from + rand() % (to - from + 1));      return SYSINFO_RET_OK; } ```  These functions should return SYSINFO\_RET\_OK, if the item value was successfully obtained. Otherwise, they should return SYSINFO\_RET\_FAIL. See example "dummy" module below for details on how to obtain information from AGENT\_REQUEST and how to set information in AGENT\_RESULT.
zh-cn	##### - 定义监控项  每个监控项都应当被定义在 ZBX\_METRIC 结构中：  ``` {.c} typedef struct {     char        *key;     unsigned    flags;     int     (*function)();     char        *test_param; } ZBX_METRIC; ```  这里的**key**指的时监控项的key（例如：“ dummy.random”），**flags**可以是 CF\_HAVEPARAMS 或 0 (取决于监控项是否接受参数)，**function** 是实现该监控项的 C函数（例如："zbx\_module\_dummy\_random"），最后 **test\_param** 是使用'' -P '' 标志启动 ZABBIX Agent 时使用的参数里列表（例如："1,1000",可以是 NULL）。下面是一个具体示例：\  ``` {.c} static ZBX_METRIC keys[] = {     { "dummy.random", CF_HAVEPARAMS, zbx_module_dummy_random, "1,1000" },     { NULL } } ```  每个实现一个监控项的函数应该接受俩哥哥指针参数函数，第一个是一种AGENT\_REQUEST类型，第二个是一种AGENT\_RESULT类型：\  ``` {.c} int zbx_module_dummy_random(AGENT_REQUEST *request, AGENT_RESULT *result) {     ...      SET_UI64_RESULT(result, from + rand() % (to - from + 1));      return SYSINFO_RET_OK; } ```  如果这个监控项的值被成功获取，这些函数应当返回 SYSINFO\_RET\_OK。否则，应当返回 SYSINFO\_RET\_FAIL。关于如何从 AGENT\_REQUEST获取信息以及如何设定 AGENT\_RESULT 的详情，请参阅示例“dummy”模块。\

en-us	#### Definitions  ***[host](/manual/config/hosts)***  \- *a networked device that you want to monitor, with IP/DNS.*  ***[host group](/manual/config/hosts)***  \- *a logical grouping of hosts; it may contain hosts and templates. Hosts and templates within a host group are not in any way linked to each other. Host groups are used when assigning access rights to hosts for different user groups.*  ***[item](/manual/config/items)***  \- *a particular piece of data that you want to receive off of a host, a metric of data.*  ***[value preprocessing](/manual/config/items/item#item_value_preprocessing)***  \- *a transformation of received metric value* before saving it to the database.  ***[trigger](/manual/config/triggers)***  \- *a logical expression that defines a problem threshold and is used to "evaluate" data received in items.*  When received data are above the threshold, triggers go from 'Ok' into a 'Problem' state. When received data are below the threshold, triggers stay in/return to an 'Ok' state.  ***[event](/manual/config/events)***  \- *a single occurrence of something that deserves attention such as a trigger changing state or a discovery/agent autoregistration taking place.*  ***[event tag](/manual/config/event_correlation/trigger/event_tags)***  \- *a pre-defined marker for the event.* It may be used in event correlation, permission granulation, etc.  ***[event correlation](/manual/config/event_correlation)***  \- *a method of correlating problems to their resolution flexibly and precisely.*  For example, you may define that a problem reported by one trigger may be resolved by another trigger, which may even use a different data collection method.  ***[problem](/manual/web_interface/frontend_sections/monitoring/problems)***  \- *a trigger that is in "Problem" state.*  ***[problem update](/manual/acknowledges#updating_problems)***  \- *problem management options provided by Zabbix, such as adding comment, acknowledging, changing severity or closing manually.*  ***[action](/manual/config/notifications/action)***  \- *a predefined means of reacting to an event.*  An action consists of operations (e.g. sending a notification) and conditions (*when* the operation is carried out)  ***[escalation](/manual/config/notifications/action/escalations)***  \- *a custom scenario for executing operations within an action; a sequence of sending notifications/executing remote commands.*  ***[media](/manual/config/notifications/media)***  \- *a means of delivering notifications; delivery channel.*  ***[notification](/manual/config/notifications/action/operation/message)***  \- *a message about some event sent to a user via the chosen media channel.*  ***[remote command](/manual/config/notifications/action/operation/remote_command)***  \- *a pre-defined command that is automatically executed on a monitored host upon some condition.*  ***[template](/manual/config/templates)***  \- *a set of entities (items, triggers, graphs, low-level discovery rules, web scenarios) ready to be applied to one or several hosts.*  The job of templates is to speed up the deployment of monitoring tasks on a host; also to make it easier to apply mass changes to monitoring tasks. Templates are linked directly to individual hosts.  ***[web scenario](/manual/web_monitoring)***  \- *one or several HTTP requests to check the availability of a web site.*  ***[frontend](/manual/introduction/overview#architecture)***  \- *the web interface provided with Zabbix.*  ***[dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard)***  \- *customizable section of the web interface displaying summaries and vizualizations* of important information in visual units called widgets.  ***[widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets)***  \- *visual unit displaying information of a certain kind and source* (a summary, a map, a graph, the clock, etc), used in the dashboard.  ***[Zabbix API](/manual/api)***  \- *Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any other custom tasks.*  ***[Zabbix server](/manual/concepts/server)***  \- *a central process of Zabbix software that performs monitoring, interacts with Zabbix proxies and agents, calculates triggers, sends notifications; a central repository of data.*  ***[Zabbix proxy](/manual/concepts/proxy)***  \- *a process that may collect data on behalf of Zabbix server, taking some processing load off of the server.*  ***[Zabbix agent](/manual/concepts/agent)***  \- *a process deployed on monitoring targets to actively monitor local resources and applications.*  ***[Zabbix agent 2](/manual/concepts/agent2)***  \- *a new generation of Zabbix agent to actively monitor local resources and applications, allowing to use custom plugins for monitoring.*  ::: noteimportant Because Zabbix agent 2 shares much functionality with Zabbix agent, the term "Zabbix agent" in documentation stands for both - Zabbix agent and Zabbix agent 2, if the functional behavior is the same. Zabbix agent 2 is only specifically named where its functionality differs. :::  ***[encryption](/manual/encryption)***  \- *support of encrypted communications between Zabbix components (server, proxy, agent, zabbix\_sender and zabbix\_get utilities)* using Transport Layer Security (TLS) protocol.  ***[network discovery](/manual/discovery/network_discovery)***  \- *automated discovery of network devices*.  ***[low-level discovery](/manual/discovery/low_level_discovery)***  \- *automated discovery of low-level entities on a particular device* (e.g. file systems, network interfaces, etc).  ***[low-level discovery rule](/manual/discovery/low_level_discovery#discovery_rule)***  \- *set of definitions for automated discovery of low-level entities* on a device.  ***[item prototype](/manual/discovery/low_level_discovery#item_prototypes)***  \- *a metric with certain parameters as variables, ready for low-level discovery*. After low-level discovery the variables are automatically substituted with the real discovered parameters and the metric automatically starts gathering data.  ***[trigger prototype](/manual/discovery/low_level_discovery#trigger_prototypes)***  \- *a trigger with certain parameters as variables, ready for low-level discovery*. After low-level discovery the variables are automatically substituted with the real discovered parameters and the trigger automatically starts evaluating data.  *Prototypes* of some other Zabbix entities are also in use in low-level discovery - graph prototypes, host prototypes, host group prototypes.  ***[agent autoregistration](/manual/discovery/auto_registration)***  \- *automated process whereby a Zabbix agent itself is registered* as a host and started to monitor.
zh-cn	#### 定义  ***[host（主机）](/manual/config/hosts)*** \- *要通过 IP/DNS 监控的联网设备。*  ***[host group（主机组）](/manual/config/hosts)*** \- *主机的逻辑分组；它可能包含主机和模板。主机组中的主机和模板没有以任何方式相互链接。在为不同用户组分配主机访问权限时使用主机组。 *  ***[item（监控项）](/manual/config/items)*** \- *你想要接收的主机的特定数据，一个度量/指标数据。*  ***[value preprocessing（值预处理）](/manual/config/items/item#item_value_preprocessing)*** \- *在数据存入数据库之前* 转化/预处理接收到的指标数据。*   ***[trigger（触发器）](/manual/config/triggers)*** \- *一个被用于定义问题阈值和 "评估" 控项接收到的数据的逻辑表达式。* 当接收到的数据高于阈值时，触发器从 'Ok' 变成 'Problem' 状态。当接收到的数据低于阈值时，触发器保留/返回 'Ok' 的状态。  ***[event（事件）](/manual/config/events)*** \- *一次发生的需要注意的事情，例如 触发器状态改变、自动发现/agent 自动注册。*  ***[event tag（事件标签）](/manual/config/event_correlation/trigger/event_tags)*** \- *预设的事件标记* 可以被用于事件关联，权限细化设置等。  ***[event correlation（事件关联）](/manual/config/event_correlation)*** \- *一种灵活而精确地将问题与其解决方法联系起来的方法* 比如说，你可以定义触发器A告警的异常可以由触发器B解决，触发器B可能采用完全不同的数据采集方式。  ***[problem（问题）](/manual/web_interface/frontend_sections/monitoring/problems)*** \- *一个处在 "问题" 状态的触发器。*  ***[problem update（问题更新）](/manual/acknowledges#updating_problems)*** \- *Zabbix 提供的问题管理选项，例如添加评论、确认、更改严重性或手动关闭。*  ***[action（动作）](/manual/config/notifications/action)*** \- *对事件作出反应的预先定义的方法。* 一个动作由多个操作（例如发送通知)）和条件（*什么情况下* 执行操作）组成。  ***[escalation（升级）](/manual/config/notifications/action/escalations)*** \- *用于在动作中执行操作的自定义场景；发送通知/执行远程命令的序列。*  ***[media（媒体）](/manual/config/notifications/media)*** \- *发送告警通知的渠道；传输媒介。*  ***[notification（通知）](/manual/config/notifications/action/operation/message)*** \- *通过选定的媒体通道发送给用户的关于某个事件的消息。*  ***[remote command（远程命令）](/manual/config/notifications/action/operation/remote_command)*** \- *在某些条件下在受监控主机上自动执行的预定义命令。*  ***[template（模板）](/manual/config/templates)*** \- *可以应用于一个或多个主机的一组实体集 （包含监控项、触发器、图表、低级别自动发现规则、web场景等）。* 模版的应用使得主机上的监控任务部署快捷方便；也可以使监控任务的批量修改更加简单。模版是直接关联到每台单独的主机上。  ***[web scenario（web 场景）](/manual/web_monitoring)*** \- *检查一个网站的可用性的一个或多个HTTP请求。*  ***[frontend（前端）](/manual/introduction/overview#architecture)*** \- *Zabbix的web界面。*  ***[dashboard（仪表盘）](/manual/web_interface/frontend_sections/monitoring/dashboard)*** \- *web界面的可定制部分，以可视化的单元（又叫小部件）显示重要信息的摘要和可视化。*  ***[widget（小部件）](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets)*** \- *在仪表板中使用的显示某种类型和来源的信息*（摘要、地图、图表、时钟等）的可视化单元。  ***[Zabbix API](/manual/api)*** \- *Zabbix API 允许您使用 JSON RPC 协议来创建、更新和获取 Zabbix 对象（如主机、监控项、图表等）或执行任何其他自定义任务。*  ***[Zabbix server](/manual/concepts/server)*** \- *Zabbix 软件的中央进程，执行监控、与 Zabbix proxy 和 agent 交互、计算触发器、发送通知；数据的中央存储库。 *  ***[Zabbix proxy](/manual/concepts/proxy)*** \- *一个可以代表 Zabbix server 收集数据的进程，减轻 server 的一些处理负载。*  ***[Zabbix agent](/manual/concepts/agent)*** \- *部署在被监控目标上以主动监控本地资源和应用程序的进程。*  ***[Zabbix agent 2](/manual/concepts/agent2)*** \- *新一代 Zabbix agent，主动监控本地资源和应用程序，允许使用自定义插件进行监控。*  ::: noteimportant 因为 Zabbix agent 2 与 Zabbix agent 共享许多功能，所以如果功能行为相同，文档中的术语 "Zabbix agent" 同时代表 Zabbix agent 和 Zabbix agent 2。Zabbix agent 2 仅在其功能不同的地方特别命名。 :::  ***[encryption（加密）](/manual/encryption)*** \- 使用传输层安全 (TLS) 协议 *支持Zabbix组件（server，proxy，agent，zabbix\_sender 和 zabbix\_get 实用程序）之间的加密通信 。*   ***[network discovery（网络发现）](/manual/discovery/network_discovery)*** \- *网络设备的自动发现。*  ***[low-level discovery（低级别自动发现）](/manual/discovery/low_level_discovery)*** \- *自动发现特定设备上的底层实体*（例如：文件系统、网络接口等)   ***[low-level discovery rule（自动别自动发现规则）](/manual/discovery/low_level_discovery#discovery_rule)*** \- *用于在设备上自动发现低级别实体的一组定义。*   ***[item prototype（监控项原型）](/manual/discovery/low_level_discovery#item_prototypes)*** \- *带有某些参数作为变量的度量，为低级别自动发现做好了准备。* 在低级别自动发现之后，变量被自动替换为实际发现的参数，度量标准自动开始收集数据。  ***[trigger prototype（触发器原型）](/manual/discovery/low_level_discovery#trigger_prototypes)*** \- *以某些参数作为变量的触发器，为低级别自动发现做好准备。* 在低级别自动发现之后，变量被自动替换为实际发现的参数，触发器自动开始计算数据。  其他一些 Zabbix 实体的 *原型* 也在低级别自动发现中使用 - 图形原型、主机原型、主机组原型。  ***[agent autoregistration（agent 自动注册）](/manual/discovery/auto_registration)*** \- *Zabbix agent 自动注册为主机* 并开始监控的自动化过程。

en-us	#### Delete a host interface  Delete the host interface with ID 30062.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.delete",     "params": [         "30062"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30062"         ]     },     "id": 1 } ```
zh-cn	#### 删除一个主机接口  删除ID为30062的主机接口.  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.delete",     "params": [         "30062"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30062"         ]     },     "id": 1 } ```

en-us	#### Delete multiple actions  Delete two actions.  Request:  ```json {     "jsonrpc": "2.0",     "method": "action.delete",     "params": [         "17",         "18"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17",             "18"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个动作  删除两个动作。  请求：  ``` json {     "jsonrpc": "2.0",     "method": "action.delete",     "params": [         "17",         "18"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ``` json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17",             "18"         ]     },     "id": 1 } ```

en-us	#### Delete multiple correlations  Delete two correlations.  Request:  ```json {     "jsonrpc": "2.0",     "method": "correlation.delete",     "params": [         "1",         "2"     ],     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "correlationids": [             "1",             "2"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个关联  删除两个关联。  请求:  ```json {     "jsonrpc": "2.0",     "method": "correlation.delete",     "params": [         "1",         "2"     ],     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "correlaionids": [             "1",             "2"         ]     },     "id": 1 } ```

en-us	#### Delete multiple discovery rules  Delete two discovery rules.  Request:  ```json {     "jsonrpc": "2.0",     "method": "drule.delete",     "params": [         "4",         "6"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "4",             "6"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个发现规则  删除两个发现规则。  请求：  ```json {     "jsonrpc": "2.0",     "method": "drule.delete",     "params": [         "4",         "6"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "4",             "6"         ]     },     "id": 1 } ```

en-us	#### Delete multiple icon maps  Delete two icon maps.  Request:  ```json {     "jsonrpc": "2.0",     "method": "iconmap.delete",     "params": [         "2",         "5"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "iconmapids": [             "2",             "5"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个图标映射  删除两个图标映射。  请求：  ```json {     "jsonrpc": "2.0",     "method": "iconmap.delete",     "params": [         "2",         "5"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "iconmapids": [             "2",             "5"         ]     },     "id": 1 } ```

en-us	#### Delete multiple images  Delete two images.  Request:  ```json {     "jsonrpc": "2.0",     "method": "image.delete",     "params": [         "188",         "192"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "imageids": [             "188",             "192"         ]     },     "id": 1 } ```
zh-cn	#### 批量删除图像  删除两个图像。  请求：  ```json {     "jsonrpc": "2.0",     "method": "image.delete",     "params": [         "188",         "192"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "imageids": [             "188",             "192"         ]     },     "id": 1 } ```

en-us	#### Delete multiple maps  Delete two maps.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.delete",     "params": [         "12",         "34"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "12",             "34"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个拓扑图  删除2个拓扑  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.delete",     "params": [         "12",         "34"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "12",             "34"         ]     },     "id": 1 } ```

en-us	#### Delete multiple proxies  Delete two proxies.  Request:  ```json {     "jsonrpc": "2.0",     "method": "proxy.delete",     "params": [         "10286",         "10285"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10286",             "10285"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个proxy  删除两个proxy。  请求：  ```json {     "jsonrpc": "2.0",     "method": "proxy.delete",     "params": [         "10286",         "10285"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10286",             "10285"         ]     },     "id": 1 } ```

en-us	#### Delete multiple scripts  Delete two scripts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.delete",     "params": [         "3",         "4"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "3",             "4"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个脚本  删除两个脚本  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.delete",     "params": [         "3",         "4"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "3",             "4"         ]     },     "id": 1 } ```

en-us	#### Delete multiple tokens  Delete two tokens.  Request:  ```json {     "jsonrpc": "2.0",     "method": "token.delete",     "params": [         "188",         "192"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "188",             "192"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个令牌  删除两个令牌。  请求：  ```json {     "jsonrpc": "2.0",     "method": "token.delete",     "params": [         "188",         "192"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "188",             "192"         ]     },     "id": 1 } ```

en-us	#### Delete multiple triggers  Delete two triggers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "trigger.delete",     "params": [         "12002",         "12003"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "12002",             "12003"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个触发器  删除两个触发器.  请求:  ```json {     "jsonrpc": "2.0",     "method": "trigger.delete",     "params": [         "12002",         "12003"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "12002",             "12003"         ]     },     "id": 1 } ```

en-us	#### Deleting dependencies from multiple triggers  Delete all dependencies from two triggers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "trigger.deleteDependencies",     "params": [         {             "triggerid": "14544"         },         {             "triggerid": "14545"         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "14544",             "14545"         ]     },     "id": 1 } ```
zh-cn	#### 从多个触发器中删除依赖关系  从两个触发器中删除所有依赖关系.  请求:  ```json {     "jsonrpc": "2.0",     "method": "trigger.deleteDependencies",     "params": [         {             "triggerid": "14544"         },         {             "triggerid": "14545"         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "14544",             "14545"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple dashboards  Delete two dashboards.  Request:  ```json {     "jsonrpc": "2.0",     "method": "dashboard.delete",     "params": [         "2",         "3"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2",             "3"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个仪表盘  删除两个仪表盘  请求:  ```json {     "jsonrpc": "2.0",     "method": "dashboard.delete",     "params": [         "2",         "3"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2",             "3"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple global macros  Delete two global macros.  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.deleteglobal",     "params": [         "32",         "11"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "32",             "11"         ]     },     "id": 1 } ```
zh-cn	#### 批量删除全局宏  删除两个全局宏.  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.deleteglobal",     "params": [         "32",         "11"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "32",             "11"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple global regular expressions.  Request:  ```json {     "jsonrpc": "2.0",     "method": "regexp.delete",     "params": [         "16",         "17"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "16",             "17"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个全局正则表达式。  请求：  ```json {     "jsonrpc": "2.0",     "method": "regexp.delete",     "params": [         "16",         "17"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "16",             "17"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple graph prototypes  Delete two graph prototypes.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graphprototype.delete",     "params": [         "652",         "653"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652",             "653"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个图表原型  删除两个图表原型。  请求： ```json {     "jsonrpc": "2.0",     "method": "graphprototype.delete",     "params": [         "652",         "653"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应： ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652",             "653"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple graphs  Delete two graphs.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graph.delete",     "params": [         "652",         "653"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652",             "653"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个图表 删除两个图表。  请求：  ```json {     "jsonrpc": "2.0",     "method": "graph.delete",     "params": [         "652",         "653"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "652",             "653"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple host groups  Delete two host groups.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.delete",     "params": [         "107824",         "107825"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "107824",             "107825"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个主机组  删除两个主机组。  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.delete",     "params": [         "107824",         "107825"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "107824",             "107825"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple host macros  Delete two host macros.  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.delete",     "params": [         "32",         "11"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "32",             "11"         ]     },     "id": 1 } ```
zh-cn	#### 批量删除主机宏  删除两个主机宏.  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.delete",     "params": [         "32",         "11"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "32",             "11"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple host prototypes  Delete two host prototypes.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.delete",     "params": [         "10103",         "10105"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10103",             "10105"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个主机原型  删除两个主机原型:  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.delete",     "params": [         "10103",         "10105"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10103",             "10105"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple hosts  Delete two hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.delete",     "params": [         "13",         "32"     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "13",             "32"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个主机  删除两个主机。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.delete",     "params": [         "13",         "32"     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "13",             "32"         ]     },     "id": 1 } ```

en-us	#### Deleting multiple item prototypes  Delete two item prototypes.\ Dependent item prototypes are removed automatically if master item or item prototype is deleted.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.delete",     "params": [         "27352",         "27356"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "prototypeids": [             "27352",             "27356"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个监控项原型  删除2个监控项原型。\ 如果主监控项或者监控项原型被删除，依赖监控项原型的监控项将被自动删除。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.delete",  · "params": [  · "27352",  · "27356"  · ],  · "auth": "3a57200802b24cda67c4e4010b50c065",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "prototypeids": [  · "27352",  · "27356"  · ]  · },  · "id": 1 } ```

en-us	#### Deleting multiple item prototypes  Delete two item prototypes.\ Dependent item prototypes are removed automatically if master item or item prototype is deleted.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.delete",     "params": [         "27352",         "27356"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "prototypeids": [             "27352",             "27356"         ]     },     "id": 1 } ```
zh-cn	#### 删除多个监控项原型  删除2个监控项原型。\ 如果主监控项或者监控项原型被删除，依赖监控项原型的监控项将被自动删除。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.delete",  · "params": [  · "27352",  · "27356"  · ],  · "auth": "3a57200802b24cda67c4e4010b50c065",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "prototypeids": [  · "27352",  · "27356"  · ]  · },  · "id": 1 } ```