en-us	#### Retrieving trigger events  Retrieve the latest events from trigger "13926."  Request:  ```json {     "jsonrpc": "2.0",     "method": "event.get",     "params": {         "output": "extend",         "select_acknowledges": "extend",         "selectTags": "extend",         "selectSuppressionData": "extend",         "objectids": "13926",         "sortfield": ["clock", "eventid"],         "sortorder": "DESC"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "eventid": "9695",             "source": "0",             "object": "0",             "objectid": "13926",             "clock": "1347970410",             "value": "1",             "acknowledged": "1",             "ns": "413316245",             "name": "MySQL is down",             "severity": "5",             "r_eventid": "0",             "c_eventid": "0",             "correlationid": "0",             "userid": "0",             "opdata": "",             "acknowledges": [                 {                     "acknowledgeid": "1",                     "userid": "1",                     "eventid": "9695",                     "clock": "1350640590",                     "message": "Problem resolved.\n\r----[BULK ACKNOWLEDGE]----",                     "action": "6",                     "old_severity": "0",                     "new_severity": "0",                     "username": "Admin",                     "name": "Zabbix",                     "surname": "Administrator"                 }             ],             "suppression_data": [                 {                     "maintenanceid": "15",                     "suppress_until": "1472511600"                 }             ],             "suppressed": "1",             "tags": [                 {                     "tag": "service",                     "value": "mysqld"                 },                 {                     "tag": "error",                     "value": ""                 }             ]         },         {             "eventid": "9671",             "source": "0",             "object": "0",             "objectid": "13926",             "clock": "1347970347",             "value": "0",             "acknowledged": "0",             "ns": "0",             "name": "Unavailable by ICMP ping",             "severity": "4",             "r_eventid": "0",             "c_eventid": "0",             "correlationid": "0",             "userid": "0",             "opdata": "",             "acknowledges": [],             "suppression_data": [],             "suppressed": "0",             "tags": []         }     ],     "id": 1 } ```
zh-cn	#### 检索触发器事件  检索ID为 "13926"  的触发器的最新事件。  请求：  ```json {     "jsonrpc": "2.0",     "method": "event.get",     "params": {     "output": "extend",     "select_acknowledges": "extend",     "selectTags": "extend",     "selectSuppressionData": "extend",     "objectids": "13926",     "sortfield": ["clock", "eventid"],     "sortorder": "DESC"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": [     {     "eventid": "9695",     "source": "0",     "object": "0",     "objectid": "13926",     "clock": "1347970410",     "value": "1",     "acknowledged": "1",     "ns": "413316245",     "name": "MySQL is down",     "severity": "5",     "r_eventid": "0",     "c_eventid": "0",     "correlationid": "0",     "userid": "0",     "opdata": "",     "acknowledges": [     {     "acknowledgeid": "1",     "userid": "1",     "eventid": "9695",     "clock": "1350640590",     "message": "Problem resolved.\n\r----[BULK ACKNOWLEDGE]----",     "action": "6",     "old_severity": "0",     "new_severity": "0",     "username": "Admin",     "name": "Zabbix",     "surname": "Administrator"     }     ],     "suppression_data": [     {     "maintenanceid": "15",     "suppress_until": "1472511600"     }     ],     "suppressed": "1",     "tags": [     {     "tag": "service",     "value": "mysqld"     },     {     "tag": "error",     "value": ""     }     ]     },     {     "eventid": "9671",     "source": "0",     "object": "0",     "objectid": "13926",     "clock": "1347970347",     "value": "0",     "acknowledged": "0",     "ns": "0",     "name": "Unavailable by ICMP ping",     "severity": "4",     "r_eventid": "0",     "c_eventid": "0",     "correlationid": "0",     "userid": "0",     "opdata": "",     "acknowledges": [],     "suppression_data": [],     "suppressed": "0",     "tags": []     }     ],     "id": 1 } ```

en-us	#### Retrieving trigger problem events  Retrieve recent events from trigger "15112."  Request:  ```json {     "jsonrpc": "2.0",     "method": "problem.get",     "params": {         "output": "extend",         "selectAcknowledges": "extend",         "selectTags": "extend",         "selectSuppressionData": "extend",         "objectids": "15112",         "recent": "true",         "sortfield": ["eventid"],         "sortorder": "DESC"     },     "auth": "67f45d3eb1173338e1b1647c4bdc1916",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "eventid": "1245463",             "source": "0",             "object": "0",             "objectid": "15112",             "clock": "1472457242",             "ns": "209442442",             "r_eventid": "1245468",             "r_clock": "1472457285",             "r_ns": "125644870",             "correlationid": "0",             "userid": "1",             "name": "Zabbix agent on localhost is unreachable for 5 minutes",             "acknowledged": "1",             "severity": "3",             "opdata": "",             "acknowledges": [                 {                     "acknowledgeid": "14443",                     "userid": "1",                     "eventid": "1245463",                     "clock": "1472457281",                     "message": "problem solved",                     "action": "6",                     "old_severity": "0",                     "new_severity": "0"                 }             ],             "suppression_data": [                 {                     "maintenanceid": "15",                     "suppress_until": "1472511600"                 }             ],             "suppressed": "1",             "tags": [                 {                     "tag": "test tag",                     "value": "test value"                 }             ]         }     ],     "id": 1 } ```
zh-cn	#### 检索触发问题事件  从触发器"15112"中检索最近的事件。  请求：  ```json {     "jsonrpc": "2.0",     "method": "problem.get",     "params": {         "output": "extend",         "selectAcknowledges": "extend",         "selectTags": "extend",         "selectSuppressionData": "extend",         "objectids": "15112",         "recent": "true",         "sortfield": ["eventid"],         "sortorder": "DESC"     },     "auth": "67f45d3eb1173338e1b1647c4bdc1916",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": [         {             "eventid": "1245463",             "source": "0",             "object": "0",             "objectid": "15112",             "clock": "1472457242",             "ns": "209442442",             "r_eventid": "1245468",             "r_clock": "1472457285",             "r_ns": "125644870",             "correlationid": "0",             "userid": "1",             "name": "Zabbix agent on localhost is unreachable for 5 minutes",             "acknowledged": "1",             "severity": "3",             "opdata": "",             "acknowledges": [                 {                     "acknowledgeid": "14443",                     "userid": "1",                     "eventid": "1245463",                     "clock": "1472457281",                     "message": "problem solved",                     "action": "6",                     "old_severity": "0",                     "new_severity": "0"                 }             ],             "suppression_data": [                 {                     "maintenanceid": "15",                     "suppress_until": "1472511600"                 }             ],             "suppressed": "1",             "tags": [                 {                     "tag": "test tag",                     "value": "test value"                 }             ]         }     ],     "id": 1 } ```

en-us	#### Retrieving triggers in problem state  Retrieve the ID, name and severity of all triggers in problem state and sort them by severity in descending order.  Request:  ```json {     "jsonrpc": "2.0",     "method": "trigger.get",     "params": {         "output": [             "triggerid",             "description",             "priority"         ],         "filter": {             "value": 1         },         "sortfield": "priority",         "sortorder": "DESC"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "triggerid": "13907",             "description": "Zabbix self-monitoring processes < 100% busy",             "priority": "4"         },         {             "triggerid": "13824",             "description": "Zabbix discoverer processes more than 75% busy",             "priority": "3"         }     ],     "id": 1 } ```
zh-cn	#### 检索在问题状态的触发器  检索在问题状态下的所有触发器的ID，名称和严重性，并按严重性级别按降序分类。  请求:  ```json {     "jsonrpc": "2.0",     "method": "trigger.get",     "params": {         "output": [             "triggerid",             "description",             "priority"         ],         "filter": {             "value": 1         },         "sortfield": "priority",         "sortorder": "DESC"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": [         {             "triggerid": "13907",             "description": "Zabbix self-monitoring processes < 100% busy",             "priority": "4"         },         {             "triggerid": "13824",             "description": "Zabbix discoverer processes more than 75% busy",             "priority": "3"         }     ],     "id": 1 } ```

en-us	#### Retrieving user data  Retrieve data of a user with ID "12".  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.get",     "params": {         "output": ["userid", "username"],         "selectRole": "extend",         "userids": "12"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {   "jsonrpc": "2.0",   "result": [       {           "userid": "12",           "username": "John",           "role": {               "roleid": "5",               "name": "Operator",               "type": "1",               "readonly": "0"           }       }   ],   "id": 1 } ```
zh-cn	#### 查询用户数据  查询用户ID是 “12”  的用户数据.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.get",     "params": {         "output": ["userid", "username"],         "selectRole": "extend",         "userids": "12"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {   "jsonrpc": "2.0",   "result": [       {           "userid": "12",           "username": "John",           "role": {               "roleid": "5",               "name": "Operator",               "type": "1",               "readonly": "0"           }       }   ],   "id": 1 } ```

en-us	#### Retrieving users  Retrieve all of the configured users.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.get",     "params": {         "output": "extend"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "userid": "1",             "username": "Admin",             "name": "Zabbix",             "surname": "Administrator",             "url": "",             "autologin": "1",             "autologout": "0",             "lang": "en_GB",             "refresh": "0s",             "theme": "default",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "50",             "timezone": "default",             "roleid": "3"         },         {             "userid": "2",             "username": "guest",             "name": "",             "surname": "",             "url": "",             "autologin": "0",             "autologout": "15m",             "lang": "default",             "refresh": "30s",             "theme": "default",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "50",             "timezone": "default",             "roleid": "4"         },         {             "userid": "3",             "username": "user",             "name": "Zabbix",             "surname": "User",             "url": "",             "autologin": "0",             "autologout": "0",             "lang": "ru_RU",             "refresh": "15s",             "theme": "dark-theme",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "100",             "timezone": "default",             "roleid": "1"         }     ],     "id": 1 } ```
zh-cn	#### 多用户查询  查询所有已配置的用户.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.get",     "params": {         "output": "extend"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": [         {             "userid": "1",             "username": "Admin",             "name": "Zabbix",             "surname": "Administrator",             "url": "",             "autologin": "1",             "autologout": "0",             "lang": "en_GB",             "refresh": "0s",             "theme": "default",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "50",             "timezone": "default",             "roleid": "3"         },         {             "userid": "2",             "username": "guest",             "name": "",             "surname": "",             "url": "",             "autologin": "0",             "autologout": "15m",             "lang": "default",             "refresh": "30s",             "theme": "default",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "50",             "timezone": "default",             "roleid": "4"         },         {             "userid": "3",             "username": "user",             "name": "Zabbix",             "surname": "User",             "url": "",             "autologin": "0",             "autologout": "0",             "lang": "ru_RU",             "refresh": "15s",             "theme": "dark-theme",             "attempt_failed": "0",             "attempt_ip": "",             "attempt_clock": "0",             "rows_per_page": "100",             "timezone": "default",             "roleid": "1"         }     ],     "id": 1 } ```

en-us	#### Retrieving value maps  Retrieve all configured value maps.  Request:  ```json {     "jsonrpc": "2.0",     "method": "valuemap.get",     "params": {         "output": "extend"     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "valuemapid": "4",             "name": "APC Battery Replacement Status"         },         {             "valuemapid": "5",             "name": "APC Battery Status"         },         {             "valuemapid": "7",             "name": "Dell Open Manage System Status"         }     ],     "id": 1 } ```  Retrieve one value map with its mappings.  Request:  ```json {     "jsonrpc": "2.0",     "method": "valuemap.get",     "params": {         "output": "extend",         "selectMappings": "extend",         "valuemapids": ["4"]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "valuemapid": "4",             "name": "APC Battery Replacement Status",             "mappings": [                 {                     "type": "0",                     "value": "1",                     "newvalue": "unknown"                 },                 {                     "type": "0",                     "value": "2",                     "newvalue": "notInstalled"                 },                 {                     "type": "0",                     "value": "3",                     "newvalue": "ok"                 },                 {                     "type": "0",                     "value": "4",                     "newvalue": "failed"                 },                 {                     "type": "0",                     "value": "5",                     "newvalue": "highTemperature"                 },                 {                     "type": "0",                     "value": "6",                     "newvalue": "replaceImmediately"                 },                 {                     "type": "0",                     "value": "7",                     "newvalue": "lowCapacity"                 }             ]         }     ],     "id": 1 } ```
zh-cn	#### 检索值映射  检索所有配置的值映射。  请求：  ```json {     "jsonrpc": "2.0",     "method": "valuemap.get",     "params": {         "output": "extend"     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": [         {             "valuemapid": "4",             "name": "APC Battery Replacement Status"         },         {             "valuemapid": "5",             "name": "APC Battery Status"         },         {             "valuemapid": "7",             "name": "Dell Open Manage System Status"         }     ],     "id": 1 } ```  根据映射关系，检索一个值映射。  请求：  ```json {     "jsonrpc": "2.0",     "method": "valuemap.get",     "params": {         "output": "extend",         "selectMappings": "extend",         "valuemapids": ["4"]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": [         {             "valuemapid": "4",             "name": "APC Battery Replacement Status",             "mappings": [                 {                     "type": "0",                     "value": "1",                     "newvalue": "unknown"                 },                 {                     "type": "0",                     "value": "2",                     "newvalue": "notInstalled"                 },                 {                     "type": "0",                     "value": "3",                     "newvalue": "ok"                 },                 {                     "type": "0",                     "value": "4",                     "newvalue": "failed"                 },                 {                     "type": "0",                     "value": "5",                     "newvalue": "highTemperature"                 },                 {                     "type": "0",                     "value": "6",                     "newvalue": "replaceImmediately"                 },                 {                     "type": "0",                     "value": "7",                     "newvalue": "lowCapacity"                 }             ]         }     ],     "id": 1 } ```

en-us	### Return values  `(array)` Returns an array of objects containing the ID of the generated token under the `tokenid` property and generated authorization string under `token` property.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tokenid|string|ID of the token.| |token|string|The generated authorization string for this token.|
zh-cn	### 返回值  `(array)` 返回一个对象数组，其中包含 `tokenid` 属性下生成的令牌的 ID 和 `token` 属性下生成的授权字符串。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tokenid|string|令牌ID。| |token|string|为此令牌生成的授权字符串。|

en-us	### Return values  `(array)` Returns an array of objects containing the ID of the generated token under the `tokenid` property and generated authorization string under `token` property.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |tokenid|string|ID of the token.| |token|string|The generated authorization string for this token.|
zh-cn	### 返回值  `(array)` 返回一个对象数组，其中包含 `tokenid` 属性下生成的令牌的 ID 和 `token` 属性下生成的授权字符串。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tokenid|string|令牌ID。| |token|string|为此令牌生成的授权字符串。|

en-us	### Return values  `(array)` Returns an array with changes in configuration, that will be made.
zh-cn	### 返回值  `(array)` 以数组形式返回配置中的变更内容

en-us	### Return values  `(array)` Returns array with the names of updated parameters.
zh-cn	### 返回值  `(array)` 返回更新参数的名称数组

en-us	### Return values  `(array)` Returns array with the names of updated parameters.
zh-cn	 ### 返回值  `(数组)` 返回被更新参数名字的数组。

en-us	### Return values  `(array)` Returns array with the names of updated parameters.
zh-cn	### 返回值  `(array)` 返回包含已更新参数名称的数组。

en-us	### Return values  `(boolean )` Returns boolean true as result on successful update.
zh-cn	### 返回值  `(boolean )` 成功更新后返回布尔值true。

en-us	### Return values  `(boolean)` Returns `true` if importing has been successful.
zh-cn	### 返回值  `(boolean)`如果导入成功将返回 `true` 

en-us	### Return values  `(boolean)` Returns `true` if the copying was successful.
zh-cn	### 返回值  `(boolean)` 如果复制成功，则返回 `true`。

en-us	### Return values  `(boolean)` Returns `true` if the user has been logged out successfully.
zh-cn	### 返回值  `(boolean)` 如果用户成功注销，返回 `true`.

en-us	### Return values  `(integer/array)` Returns an array of objects.
zh-cn	### 返回值  `(integer/array)` 返回一个对象的数组。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has been used.
zh-cn	###返回值  `(integer/array)` 返回以下任一选项  -  对象数组; -   如果使用`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回任一值:  - 对象数组； - 检索到的对象的计数，如果使用了 `countOutput` 参数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回值是 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了`countOutput`参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，返回被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回以下其中一种结果：  -   一个数组对象； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(整型/数组)` 返回其中之一： -   一组对象; -   如果用到`countOutput`参数，被检索到的对象数,。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了`countOutput`参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中一个：  -   一个对象数组； -   如果使用了`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整数/数组)` 返回其中之一:  -   一组对象; -   如果使用了 `countOutput` 参数,返回对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整数/数组)` 返回任一：  -   对象数组； -   如果已使用countOutput参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整型/数组)` 返回其中之一： -   一个对象数组； -   如果使用`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，返回被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回以下其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中一个：  -   一个对象数组； -   如果使用了 countOutput 参数，将返回获取对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   对象数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回二者之一:  -   一个对象列表; -   查询结果数量, 如果使用了 `countOutput` 参数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  (integer/array) 返回其中之一：  -   对象数组；  -   如果使用了 countOutput 参数，则检索到对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回数值  `(integer/array)`将返回以下两种数值中的任意一种：  -   一组有关对象的数组； -   若在使用`countOutput`参数的前提下，那么将会返回检索对象的总数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(integer/array)`返回以下:  -   一组对象; -   如果`countOutput` 参数被使用，返回对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -   如果使用了 `countOutput` 参数，则返回检索到的对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一组对象； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一组对象； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回:  -   一个对象数组; -   检索对象的计数, 如果, 如果 `countOutput` 参数被使用.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回下列两种数值之一：  -   一组对象； -   在`countOutput`参数应用的情况下，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(integer/array)` 返回两者其一：  -   一个对象数组； -   如果使用了'countOutput'参数，则对检索对象进行计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回:  -   一组对象; -   如果使用了 `countOutput` 参数，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -  如果使用了 countOutput 参数，将返回获取对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整数/数组)` 返回其中之一:  -   一组对象; -   如果使用了 `countOutput` 参数，则返回获取的对象数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一：  -   一组对象数组; -   如果已经使用了`countOutput`参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一:  -    一个对象数组 -   如果已经使用了`countOutput`参数，则统计对象的数量.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一:  -   一组对象数组; -   如果已经使用了`countOutput`参数，则检索对象的计数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回下列两种之一：  -   一组对象； -   在`countOutput`参数应用的情况下，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一:  -   一组对象. -   如果已经使用了`countOutput`参数，则检索对象的计数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回结果二选一:  -   一个对象数组; -   如果使用 `countOutput` 参数，返回检索到的对象总数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数,查询对象的数量.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回:  -   一组对象; -  如果设置了`countOutput`参数,则返回获取到的对象数量。

en-us	### Return values  `(object)` Returns an object containing information about user.
zh-cn	### 返回值  `(object)` 返回一个包含用户信息的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the affected triggers under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含在`triggerids`属性中已受影响触发器的ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含 `itemids` 属性（其中包含成功删除历史数据的监控项ID）的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created actions under the `actionids` property. The order of the returned IDs matches the order of the passed actions.
zh-cn	### 返回值  `(object)` 返回一个对象，其中 `actionids` 属性下包含已创建 动作 的 ID。 返回的 ID 的顺序与传递的 动作 顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created correlations under the `correlationids` property. The order of the returned IDs matches the order of the passed correlations.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含`correlationids` 属性下创建的关联的 ID。返回的 ID 的顺序与所传递的关联的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed dashboards.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 `dashboardids` 属性下创建的仪表盘的 ID。返回的 ID 的顺序与所传递的仪表盘的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created discovery rules under the `druleids` property. The order of the returned IDs matches the order of the passed discovery rules.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下创建的发现规则的ID。返回 ID 的顺序与传递的发现规则的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created global macros under the `globalmacroids` property. The order of the returned IDs matches the order of the passed global macros.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被创建全局宏的ID）的对象. 返回的主机宏ID顺序与传入的主机宏顺序相同.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graph prototypes under the `graphids` property. The order of the returned IDs matches the order of the passed graph prototypes.
zh-cn	 ### 返回值  `(object)`返回一个对象，包含在`graphids`属性下创建的图表原型的ID。返回的ID的顺序与传递的图表原型的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graphs under the `graphids` property. The order of the returned IDs matches the order of the passed graphs.
zh-cn	### 返回值  `(object)`返回一个对象，包含在`graphids`属性下创建的图表的ID。返回的ID的顺序与传递的图表的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host groups under the `groupids` property. The order of the returned IDs matches the order of the passed host groups.
zh-cn	 ### 返回值  `(对象)` 在`groupids`属性下返回包含已创建主机组ID的对象.返回主机组ID的顺序与传入的主机组顺序一致.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)`  在`interfaceids`属性中返回已创建主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`iterfaceids`属性中返回包含已创建主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. The order of the returned IDs matches the order of the passed host interfaces.
zh-cn	### 返回值  `(object)` 在 `interfaceids` 属性中返回已创建主机接口ID对象。 返回的ID顺序与传入的主机接口顺序保持一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host macros under the `hostmacroids` property. The order of the returned IDs matches the order of the passed host macros.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被创建主机宏的ID）的对象. 返回的主机宏ID顺序与传入的主机宏顺序相同.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host prototypes under the `hostids` property. The order of the returned IDs matches the order of the passed host prototypes.
zh-cn	### 返回值  `(object)` 在`hostids`属性中返回包含创建主机原型的ID对象， 返回的ID顺序和传入的主机原型的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts.
zh-cn	 ### 返回值  `(对象)` 返回包含已创建主机ID的属性 `hostids` ，返回ID的顺序与传入主机的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created icon maps under the `iconmapids` property. The order of the returned IDs matches the order of the passed icon maps.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所创建图标映射的 ID。返回的多个 ID 的顺序与传参里多个图标映射的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created images under the `imageids` property. The order of the returned IDs matches the order of the passed images.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下创建的图像的 ID。返回 ID 的顺序与传递图像的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created item prototypes under the `itemids` property. The order of the returned IDs matches the order of the passed item prototypes.
zh-cn	### 返回值  返回一个对象`(object)` ，该对象包含在 `itemids` 属性下创建的监控项原型的 IDs。返回的 IDs 的顺序与传递的项目原型的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created items under the `itemids` property. The order of the returned IDs matches the order of the passed items.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `itemids` 属性下创建的监控项的 ID。返回 ID 的顺序与传递监控项的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created LLD rules under the `itemids` property. The order of the returned IDs matches the order of the passed LLD rules.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含在 `itemids` 属性下创建的 LLD 规则的 ID。返回 ID 的顺序与传递的 LLD 规则的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created maintenances under the `maintenanceids` property. The order of the returned IDs matches the order of the passed maintenances.
zh-cn	### 返回值   `(object)`在`maintenanceids`属性中返回一个包含所有已被创建的维护模式的对象的ID。返回的IDs的排序与传递的维护模式的IDs顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created maps under the `sysmapids` property. The order of the returned IDs matches the order of the passed maps.
zh-cn	### 返回值  `(对象)`返回一个对象，该对象包含在"sysmapid"属性下创建的拓扑图的id。返回id的顺序与传递的拓扑图的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created media types under the `mediatypeids` property. The order of the returned IDs matches the order of the passed media types.
zh-cn	### 返回值   `(object)`返回一个包含在"mediatypeids"属性下创建的媒介类型的IDs的对象，返回的顺序与传递的媒介类型的ID顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created proxies under the `proxyids` property. The order of the returned IDs matches the order of the passed proxies.
zh-cn	### 返回值  `(object)`返回一个对象,该对象包含在`proxyids`属性下创建的proxy的ids，返回的Ids的顺序与所传递的代理的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created regular expressions under the `regexpids` property.
zh-cn	### 返回值  根据`regexpids` 的特性`(object)`会反馈一个包含新创建的正则表达式ID的对象

en-us	### Return values  `(object)` Returns an object containing the IDs of the created roles under the `roleids` property. The order of the returned IDs matches the order of the passed roles.
zh-cn	### 返回值  根据`roleids`特性，`(object)` 会返回一个对象，包含创建的角色用户的ID号。返回的ID号顺序对应查询的角色用户次序。 

en-us	### Return values  `(object)` Returns an object containing the IDs of the created scheduled reports under the `reportids` property. The order of the returned IDs matches the order of the passed scheduled reports.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`会返回一个对象，包含已创建的规划报告ID。 返回的ID顺序与发送的规划报告顺序保持一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created scripts under the `scriptids` property. The order of the returned IDs matches the order of the passed scripts.
zh-cn	### 返回值  `(对象)` 返回一个`scriptids`属性包含被创建脚本ID的对象。返回的ID顺序与传入脚本的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created services under the `serviceids` property. The order of the returned IDs matches the order of the passed services.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids`属性包含被创建服务ID的对象。返回的ID顺序与传入服务的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created SLAs under the `slaids` property. The order of the returned IDs matches the order of the passed SLAs.
zh-cn	### 返回值  `(object)` 返回一个包含已创建 SLA 的 ID 的对象，在`slaids`属性下。返回的 ID 的顺序匹配通过的 SLA 的顺序。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created tasks under the `taskids` property. One task is created for each item and low-level discovery rule. The order of the returned IDs matches the order of the passed `itemids`.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`taskids` 属性下创建的任务的ID。为每个监控项和低级别自动发现规则创建一个任务。返回的ID的顺序与传递的`itemids`的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created template dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed template dashboards.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids` 属性下创建的模板仪表盘的ID。返回ID的顺序与传递的模板仪表盘的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created templates under the `templateids` property. The order of the returned IDs matches the order of the passed templates.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下创建的模板的ID。返回ID的顺序与传递模板的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created tokens under the `tokenids` property. The order of the returned IDs matches the order of the passed tokens.
zh-cn	### 返回值  `(object)` 返回一个对象其中包含在 `tokenids` 属性下创建的令牌的 ID。返回的 ID 的顺序与传递的令牌的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created trigger prototypes under the `triggerids` property. The order of the returned IDs matches the order of the passed trigger prototypes.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含在`triggerids`属性中已创建触发器原型的ID，返回ID的顺序与传递触发器原型的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created triggers under the `triggerids` property. The order of the returned IDs matches the order of the passed triggers.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含在 `triggerids` 属性下创建的触发器 ID，返回 的ID 顺序与传递的触发器的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created user groups under the `usrgrpids` property. The order of the returned IDs matches the order of the passed user groups.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被创建用户组ID）的对象.  返回的ID的顺序与传递的用户组的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created users under the `userids` property. The order of the returned IDs matches the order of the passed users.
zh-cn	### 返回值  `(object)` 返回一个包含创建值的ID的对象映射 `userids` 属性. 返回的ID的顺序与传入的用户的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created value maps the `valuemapids` property. The order of the returned IDs matches the order of the passed value maps.
zh-cn	### 返回值  `(object)` 返回一个包含已创建值映射的ID的对象，ID在`valuemapids` 属性下。返回的IDs的顺序和传递的值映射的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created web scenarios under the `httptestids` property. The order of the returned IDs matches the order of the passed web scenarios.
zh-cn	 ### 返回值  `(object)` 返回一个包含已创建Web场景ID的对象，ID在`httptestids`属性下。返回的IDs的顺序和传递的Web场景的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted actions under the `actionids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象在 `actionids` 属性下包含要删除动作的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted correlations under the `correlationids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`correlationids`属性下删除的关联 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids`属性下删除的仪表盘 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted discovery rules under the `druleids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下已删除的发现规则的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted global macros under the `globalmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被删除全局宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graph prototypes under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个包含在`graphids`属性下被删除图表原型的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个对象，包含在`graphids`属性下删除的图表的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 在`groupids`属性中返回包含已删主机组ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已删除主机接口ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已删除主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host macros under the `hostmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被删除主机宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host prototypes under the `hostids` property.
zh-cn	### 返回值 `(object)` 在`hostids`属性中返回已删除主机原型的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted hosts under the `hostids` property.
zh-cn	 ### 返回值  `(object)` 返回一个具有`hostids`属性（其中包含被删除主机的ID）的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted icon maps under the `iconmapids` property.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所删除的多个图标映射的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted images under the `imageids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下已删除图像的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted item prototypes under the `prototypeids` property.
zh-cn	### 返回值  `（object）`返回一个对象，该对象包含`prototypeids`属性下已删除监控项原型的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted items under the `itemids` property.
zh-cn	### 返回值  返回一个对象，该对象包含 `itemids` 属性下已删除项目的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted maintenance periods under the `maintenanceids` property.
zh-cn	### 返回值  `(object)`在`maintenanceids`属性下返回包含已被删除的维护周期的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted maps under the `sysmapids` property.
zh-cn	### 返回值  返回包含"sysmapid"属性下的已删除拓扑图的IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted media types under the `mediatypeids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `mediatypeids` 属性下已删除媒介类型的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted proxies under the `proxyids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 proxyids 属性下已删除proxy的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted regular expressions under the `regexpids` property.
zh-cn	### 返回数值  根据`regexpids` 的特性`(object)`会反馈一个包含已删除正则表达式的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted roles under the `roleids` property.
zh-cn	### 返回值  根据`roleids`特性，`(object)` 会返回一个对象，包含删除的角色用户的ID号。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted scheduled reports under the `reportids` property.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`返回一个包含已删除的规划报告ID的对象。 

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted scripts under the `scriptids` property.
zh-cn	### 返回值  `(对象)` 返回一个`scriptids`属性包含被删除脚本ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted services under the `serviceids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids` 属性包含被删除服务ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted SLAs under the `slaids` property.
zh-cn	###返回值 `(object)` 返回一个包含已删除 SLA 的 ID 的对象¶ 在`slaids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted template dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids`属性下已删除模板仪表盘的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已删除模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted tokens under the `tokenids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `tokenids` 属性下已删除令牌的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted trigger prototypes under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含在`triggerids`属性中已删除触发器原型的ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted triggers under the `triggerids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含在 `triggerids` 属性下已删除触发器 ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted user groups under the `usrgrpids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被创建用户组ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被删除用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted value maps under the `valuemapids` property.
zh-cn	### 返回值  `(object)` 返回一个包含被删除的值映射ID的对象，ID在`valuemapids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted web scenarios under the `httptestids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含被删除的Web场景的ID的对象，ID在`httptestids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the dependent triggers under the `triggerids` property.
zh-cn	### 返回值  `(对象)` 返回一个对象，该对象包含 `triggerids` 属性下的触发器 ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the unblocked users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被解锁用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated actions under the `actionids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象在 `actionids` 属性下包含更新的动作的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated correlations under the `correlationids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 “correlationids” 属性下更新的关联的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `dashboardids`属性下更新的仪表盘 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated discovery rules under the `druleids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下更新的发现规则的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated events under the `eventids` property.
zh-cn	### 返回值  `(object)` 返回一个对象， 该对象包含 `eventids` 属性下更新的事件 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated global macros under the `globalmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被更新全局宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个包含`graphids'属性下更新的图表原型的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含 `graphids` 属性下的更新图表的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值 `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已更新主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host macros under the `hostmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被更新主机宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property.
zh-cn	### 返回值  `(object)` 在`hostids`属性中返回包含已更新主机原型ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated icon maps under the `iconmapids` property.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所更新的多个图标映射的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated images under the `imageids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下更新的图像的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated item prototypes under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `itemids` 属性下更新的监控项原型的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated items under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `itemids` 属性下更新的监控项的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated LLD rules under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `itemids` 属性下更新的 LLD 规则的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated maintenances under the `maintenanceids` property.
zh-cn	### 返回值   `(object)`在`maintenanceids`属性中返回一个包含已被更新的维护模式的IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated maps under the `sysmapids` property.
zh-cn	### 返回值  返回一个对象，该对象包含"sysmapid"属性下更新的映射的id.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated media types under the `mediatypeids` property.
zh-cn	### 返回值  `(object)` 返回包含`mediatypeids`属性下所更新IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated proxies under the `proxyids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含`proxyids`属性下更新的proxy的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated regular expressions under the `regexpids` property.
zh-cn	### 返回值  根据`regexpids`的特性，`(object)` 会返回一个对象，其包含已升级的正则表达式ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated roles under the `roleids` property.
zh-cn	### 返回值  根据`roleids`的特性，`(object)`返回一个包含已更新职责用户ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated scheduled reports under the `reportids` property.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`返回一个包含已更新定时报表ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated scripts under the `scriptids` property.
zh-cn	### 返回值 `(对象)` 返回一个`scriptids`属性包含被更新脚本ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated services under the `serviceids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids`属性包含了被更新服务ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated SLAs under the `slaids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含 `slaids` 属性下更新的 SLA 的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated template dashboards under the `dashboardids` property.
zh-cn	### 返回值 `(object)` 返回一个对象，该对象包含`dashboardids`属性下更新的模板仪表盘的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated tokens under the `tokenids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `tokenids` 属性下已被更新的令牌的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated trigger prototypes under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象是包含在`triggerids`属性中已更新触发器原型的ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated triggers under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，其中包含 triggerids 属性下已更新的触发器的 ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated user groups under the `usrgrpids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被更新用户组ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被更新用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated value maps under the `valuemapids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，包含被更新的值映射的ID，ID在`valuemapids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含被更新Web场景的ID的对象，ID在`httptestid`属性下。

en-us	### Return values  `(object)` Returns an object with host IDs as properties and arrays of available scripts as values.  ::: notetip The method will automatically expand macros in the `confirmation` text. :::
zh-cn	### 返回值 `(对象)` 返回一个以主机ID为属性、以可用脚本数组为值的对象。 ::: notetip 此方法会自动拓展`confirmation` 中的宏. :::

en-us	### Return values  `(object)` Returns authentication object.
zh-cn	### 返回值  `(object)` 返回认证对象。

en-us	### Return values  `(object)` Returns autoregistration object.
zh-cn	### 返回值  `(object)` 返回自动注册对象

en-us	### Return values  `(object)` Returns housekeeping object.  
zh-cn	### 返回值  `(object)` 返回管家对象

en-us	### Return values  `(object)` Returns settings object.
zh-cn	 ### 返回值  `(对象)`返回设置对象。

en-us	### Return values  `(object)` Returns the result of script execution.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |response|string|Whether the script was run successfully.<br><br>Possible value - `success`.| |value|string|Script output.| |debug|object|Contains a [debug object](/manual/api/reference/script/object#Debug) if a webhook script is executed. For other script types, it contains empty object.|
zh-cn	### 返回值  `(object)` 返回脚本执行的结果。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--|--|------| |response|string|脚本是否成功运行。<br><br>可能的值 - `success`或 `failed`。| |值|字符串|脚本输出。| |debug|object|如果执行 webhook 脚本，则包含 [调试对象](/manual/api/reference/script/object#Debug)。对于其他脚本类型，它包含空对象。|

en-us	### Return values  `(object)` Returns the results of the calculation.  | Property   | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                                                                                                                                                                  | |------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | periods    | array                                               | List of the reported periods.<br><br>Each reported period is represented as an object consisting of:<br>- _period\_from_ - Starting date of the reported period (timestamp).<br>- _period\_to_ - Ending date of the reported period (timestamp).<br><br>Periods are sorted by `period_from` field ascending. | | serviceids | array                                               | List of service IDs in the reported periods.<br><br>The sorting order of the list is not defined. Even if `serviceids` parameter was passed to the `sla.getsli` method.                                                                                                                                      | | sli        | array                                               | SLI data (as a **two-dimensional array**) for each reported period and service.<br><br>The index of the `periods` property is used as the **first** dimension of the `sli` property.<br><br>The index of the `serviceids` property is used as the **second** dimension of the `sli` property.                |
zh-cn	### 返回值  `(object)` 返回计算的结果  | 属性| [类型](/manual/api/reference_commentary#data_types) | 描述| |------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | periods    | 数组| 报告期间的列表。<br><br>每个报告期间都表示为一个对象，包括：<br>- _period\_from_ - 报告期间的开始日期（时间戳）。<br>- _period\_to_ - 结束报告期间的日期（时间戳）。<br><br>期间按 `period_from` 字段升序排序。  | | serviceids | 数组|报告期间的服务 ID 列表。<br><br>未定义列表的排序顺序。即使 `serviceids` 参数被传递给 `sla.getsli` 方法。                                                                                                                                      | | sli        | 数组| 每个报告的期间和服务的 SLI 数据（作为**二维数组**）。<br><br>`periods` 属性的索引用作`sli` 的**第一个** 维度<br><br>`serviceids` 属性的索引用作`sli` 属性的**second**维度。         |

en-us	### Return values  `(string)` Returns a serialized string containing the requested configuration data.
zh-cn	### 返回值  `(string)` 返回一个包含请求配置数据的序列化字符串

en-us	### Return values  `(string)` Returns the version of the Zabbix API.  ::: notetip Starting from Zabbix 2.0.4 the version of the API matches the version of Zabbix. :::
zh-cn	### 返回值  `(string)` 返回 Zabbix API 的版本。  ::: notetip 从 Zabbix 2.0.4 版本开始，API 的版本与 Zabbix 的版本相匹配。 :::

en-us	 ### RHEL packages renamed  RHEL packages have been renamed by adding a "release" word in the name:  |Naming|Package name| |--|--------| |Old|`zabbix-agent-6.0.7-1.el9.x86_64.rpm`| |New|`zabbix-agent-6.0.8-release1.el9.x86_64.rpm`|  There is no functional change associated with this change.   This is necessary as preparation for providing packages of minor version (i.e. 6.0.x) release candidates, expected to start with 6.0.9. The naming change will ensure that for someone who has both stable and unstable repositories enabled on their system, repository updates will be received in the correct order. This naming change is for RHEL packages only.
zh-cn	### RHEL 包重命名  RHEL 软件包已通过在名称中添加“release”一词进行重命名：  |命名|包名| |--|--------| |旧|`zabbix-agent-6.0.7-1.el9.x86_64.rpm`| |新|`zabbix-agent-6.0.8-release1.el9.x86_64.rpm`|  没有与此更改相关的功能更改。  这是准备提供次要版本（即 6.0.x）候选发布包的准备，预计从 6.0.9 开始。 命名更改将确保对于在其系统上同时启用了稳定和不稳定存储库的人，将以正确的顺序接收存储库更新。 此命名更改仅适用于 RHEL 包。

en-us	#### role  Changes:\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) Action object: added support of name value `manage_services`.\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) Role rules object: added support of new properties `services.read.mode`, `services.read.list`, `services.read.tag`, `services.write.mode`, `services.write.list` and `services.write.tag`.\
zh-cn	 #### 角色  变更：\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) 动作对象：添加对名称值为`manage_services`的支持。\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 角色规则对象：添加对新属性`services.read.mode`，`services.read.list`，`services.read.tag`，`services.write.mode`，`services.write.list`和`services.write.tag`的支持。\

en-us	#### role  Changes:\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) Action object: dropped support of value `manage_services` for `name` property.\
zh-cn	 #### 角色  变更：\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 动作对象：删除对`name`属性值为`manage_services`的支持。\

en-us	#### role  Changes:\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) added support of new properties `services.read.mode`, `services.read.list`, `services.read.tag`, `services.write.mode`, `services.write.list` and `services.write.tag`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) added support of name value `manage_services`.\
zh-cn	 #### 角色  变更：\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) 动作对象：添加对名称值为`manage_services`的支持。\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 角色规则对象：添加对新属性`services.read.mode`，`services.read.list`，`services.read.tag`，`services.write.mode`，`services.write.list`和`services.write.tag`的支持。\

en-us	#### role  Changes:\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) dropped support of value `manage_services` for `name` property in `action` object.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) dropped support of value `configuration.services` for `name` property in UI object.\
zh-cn	 #### 角色  变更：\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 动作对象：删除对`name`属性值为`manage_services`的支持。\

en-us	# role.create
zh-cn	# 角色.创建

en-us	# role.delete
zh-cn	# 角色.删除

en-us	# role.get
zh-cn	# 角色.获取

en-us	# > Role object  The following objects are directly related to the `role` API.
zh-cn	# > 角色 对象  以下内容将详细介绍有关 `角色` API的相关功能。

en-us	### Role rules  The role rules object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |ui|array|Array of the [UI element](object#ui_element) objects.| |ui.default\_access|integer|Whether access to new UI elements is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |services.read.mode|integer|Read-only access to services.<br><br>Possible values:<br><br>0 - Read-only access to the services, specified by the `services.read.list` or matched by the `services.read.tag` properties.<br>1 - *(default)* Read-only access to all services.| |services.read.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.read.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.write.mode|integer|Read-write access to services.<br><br>Possible values:<br><br>0 - (default) Read-write access to the services, specified by the `services.write.list` or matched by the `services.write.tag` properties.<br>1 - Read-write access to all services.| |services.write.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |services.write.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |modules|array|Array of the [module](object#module) objects.| |modules.default\_access|integer|Whether access to new modules is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.access|integer|Whether access to API is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.mode|integer|Mode for treating API methods listed in the `api` property.<br><br>Possible values:<br>0 - *(default)* Deny list;<br>1 - Allow list.| |api|array|Array of API methods.| |actions|array|Array of the [action](object#action) objects.| |actions.default\_access|integer|Whether access to new actions is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	 ### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标角色用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|

en-us	### Role rules  The role rules object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |ui|array|Array of the [UI element](object#ui_element) objects.| |ui.default\_access|integer|Whether access to new UI elements is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |services.read.mode|integer|Read-only access to services.<br><br>Possible values:<br><br>0 - Read-only access to the services, specified by the `services.read.list` or matched by the `services.read.tag` properties.<br>1 - *(default)* Read-only access to all services.| |services.read.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.read.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-only access to the user role. Read-only access will not override read-write access to the services.<br><br>Only used if `services.read.mode` is set to 0.| |services.write.mode|integer|Read-write access to services.<br><br>Possible values:<br><br>0 - (default) Read-write access to the services, specified by the `services.write.list` or matched by the `services.write.tag` properties.<br>1 - Read-write access to all services.| |services.write.list|array|Array of [Service](object#service) objects.<br><br>The specified services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |services.write.tag|object|Array of [Service tag](object#service_tag) object.<br><br>The tag matched services, including child services, will be granted a read-write access to the user role. Read-write access will override read-only access to the services.<br><br>Only used if `services.write.mode` is set to 0.| |modules|array|Array of the [module](object#module) objects.| |modules.default\_access|integer|Whether access to new modules is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.access|integer|Whether access to API is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.| |api.mode|integer|Mode for treating API methods listed in the `api` property.<br><br>Possible values:<br>0 - *(default)* Deny list;<br>1 - Allow list.| |api|array|Array of API methods.| |actions|array|Array of the [action](object#action) objects.| |actions.default\_access|integer|Whether access to new actions is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	 ### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标### 角色规则  角色规则拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |ui|数组|一组包含[UI元素](object#ui_element) 对象的数组。| |ui.default\_access|整数|表示新的UI元素状态为启动与否。<br>可配置的参数包括：<br><br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |services.read.mode|整数|只允许只读性质的业务访问。<br>可配置的参数包括：<br><br>0 - 启动只读模式，通过`services.read.list`来限定只读的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - *（缺省值）* 对所有业务均采用只读访问。| |services.read.list|数字|该数组包含所有[业务](object#service) 对象。<br>列表中的业务，包含其子业务，会对目标角色用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|用户开启只读访问。对业务来说，只读访问并不会覆盖读写访问。 <br>只有将`services.read.mode`设定为0才会开应用属性。| |services.read.tag|对象|包含一组[业务标签](object#service_tag)对象的参数。<br><br>标签所对应的业务，包含其子业务，会对目标角色用户开启对业务的只读访问。对用户来说，只读访问并不会覆盖读写访问。<br><br>只有将`services.read.mode`设定为0才会开启该功能。| |services.write.mode|整数|对业务开启读写访问。<br><br>可配置的参数包括：<br><br>0 - （缺省值） 设定业务的读写访问，通过`services.read.list`来限定读写的业务，或者通过与`services.read.tag`匹配对对应业务进行访问。<br>1 - 对所有业务开启读写访问。| |services.write.list|数组|包含一组[业务](object#service)对象。<br><br>列表中的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |services.write.tag|对象|包含一组[业务标签](object#service_tag)对象。<br><br>标签对应的业务，包含其子业务，会对目标角色用户开启对业务的读写访问。对用户来讲，读写访问权限会覆盖只读访问权限。<br><br>只有将`services.write.mode`设定为0才会开启该功能。| |modules|数组|包含一组[模块](object#module)对象。| |modules.default\_access|整数|表示对新模块开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.access|证书|表示对API开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。| |api.mode|整数|对罗列在`api`属性中的API的方式进行模式设定。<br><br>可配置的参数包括：<br>0 - *（缺省值）* 拒绝列表；<br>1 - 允许列表。| |api|数组|包含一组API的方式。| |actions|数组|包含一组[动作](object#action)对象。| |actions.default\_access|整数|表示对新的动作是否开启访问。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *（缺省值）* 开启。|

en-us	### Role  The role object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |roleid|string|*(readonly)* ID of the role.| |**name**<br>(required)|string|Name of the role.| |**type**<br>(required)|integer|User type.<br><br>Possible values:<br>1 - *(default)* User;<br>2 - Admin;<br>3 - Super admin.| |readonly|integer|*(readonly)* Whether the role is readonly.<br><br>Possible values:<br>0 - *(default)* No;<br>1 - Yes.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 角色  一个角色对象拥有以下属性：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |roleid|字符串|*（只读）* 角色ID号。| |**name**<br>（必要）|字符串|角色名称。| |**type**<br>(必需)|整数|用户类型。<br><br>可选值：<br>1 - *（缺省值）* 普通用户；<br>2 - 管理员；<br>3 - 超级管理员。| |readonly|整数|*（只读）* 设定角色是否为只读。<br><br>可选值：<br>0 - *（缺省值）* 否；<br>1 - 是。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Role  This class is designed to work with user roles.  Object references:\  -   [Role](/manual/api/reference/role/object#role) -   [Role rules](/manual/api/reference/role/object#role_rules) -   [UI element](/manual/api/reference/role/object#ui_element) -   [Service](/manual/api/reference/role/object#service) -   [Service tag](/manual/api/reference/role/object#service_tag) -   [Module](/manual/api/reference/role/object#module) -   [Action](/manual/api/reference/role/object#action)  Available methods:\  -   [role.create](/manual/api/reference/role/create) - create new user     roles -   [role.delete](/manual/api/reference/role/delete) - delete user roles -   [role.get](/manual/api/reference/role/get) - retrieve user roles -   [role.update](/manual/api/reference/role/update) - update user roles
zh-cn	# 角色  该章节介绍如何使用有关角色的功能。  参照资料：\  -   [角色](zh/manual/api/reference/role/object#role) -   [角色规则](zh/manual/api/reference/role/object#role_rules) -   [UI 元素](zh/manual/api/reference/role/object#ui_element) -   [业务](zh/manual/api/reference/role/object#service) -   [业务标签](zh/manual/api/reference/role/object#service_tag) -   [模块](zh/manual/api/reference/role/object#module) -   [动作](zh/manual/api/reference/role/object#action)  支持使用的功能包括：\  -   [role.create](zh/manual/api/reference/role/create) - 创建新的用户角色 -   [role.delete](zh/manual/api/reference/role/delete) - 删除用户角色 -   [role.get](zh/manual/api/reference/role/get) - 检索用户角色 -   [role.update](zh/manual/api/reference/role/update) - 升级用户角色

en-us	# role.update
zh-cn	# 角色.更新

en-us	##### Root cause analysis  A new *Root cause* column lists the underlying problems that directly or indirectly affect the service status.  ![](../../../assets/en/manual/introduction/root_cause.png)  If you click on the problem name you can see more details about it in *Monitoring* → *Problems*.
zh-cn	##### 根本原因分析  一个新的 *根本原因（Root cause）* 列显示了直接或间接影响服务状态的潜在问题。  ![](../../../assets/en/manual/introduction/root_cause.png)  如果您单击问题名称，您可以在*Monitoring* → *Problems*中查看有关它的更多详细信息。

en-us	#### Rule attributes  ![](../../../../assets/en/manual/discovery/network_discovery/d_rule.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Name*|Unique name of the rule. For example, "Local network".| |*Discovery by proxy*|What performs discovery:<br>**no proxy** - Zabbix server is doing discovery<br>**<proxy name>** - this proxy performs discovery| |*IP range*|The range of IP addresses for discovery. It may have the following formats:<br>Single IP: 192.168.1.33<br>Range of IP addresses: 192.168.1-10.1-255. The range is limited by the total number of covered addresses (less than 64K).<br>IP mask: 192.168.4.0/24<br>supported IP masks:<br>/16 - /30 for IPv4 addresses<br>/112 - /128 for IPv6 addresses<br>List: 192.168.1.1-255, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>Since Zabbix 3.0.0 this field supports spaces, tabulation and multiple lines.| |*Update interval*|This parameter defines how often Zabbix will execute the rule.<br>The interval is measured after the execution of previous discovery instance ends so there is no overlap.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d, since Zabbix 3.4.0.<br>[User macros](/manual/config/macros/user_macros) are supported, since Zabbix 3.4.0.<br>*Note* that if a user macro is used and its value is changed (e.g. 1w → 1h), the next check will be executed according to the previous value (far in the future with the example values).| |*Checks*|Zabbix will use this list of checks for discovery. Click on ![](../../../../assets/en/manual/discovery/network_discovery/add_link.png) to configure a new check in a popup window.<br>Supported checks: SSH, LDAP, SMTP, FTP, HTTP, HTTPS, POP, NNTP, IMAP, TCP, Telnet, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping.<br>A protocol-based discovery uses the **net.tcp.service\[\]** functionality to test each host, except for SNMP which queries an SNMP OID. Zabbix agent is tested by querying an item in unencrypted mode. Please see [agent items](/manual/config/items/itemtypes/zabbix_agent) for more details.<br>The 'Ports' parameter may be one of following:<br>Single port: 22<br>Range of ports: 22-45<br>List: 22-45,55,60-70| |*Device uniqueness criteria*|Uniqueness criteria may be:<br>**IP address** - no processing of multiple single-IP devices. If a device with the same IP already exists it will be considered already discovered and a new host will not be added.<br>**<discovery check>** - either Zabbix agent or SNMP agent check.| |*Host name*|Set the technical host name of a created host using:<br>**DNS name** - DNS name (default)<br>**IP address** - IP address<br>**<discovery check>** - received string value of the discovery check (e.g. Zabbix agent, SNMP agent check)<br>See also: [Host naming](/manual/discovery/network_discovery#host_naming).<br>This option is supported since 4.2.0.| |*Visible name*|Set the visible host name of a created host using:<br>**Host name** - technical host name (default)<br>**DNS name** - DNS name<br>**IP address** - IP address<br>**<discovery check>** - received string value of the discovery check (e.g. Zabbix agent, SNMP agent check)<br>See also: [Host naming](/manual/discovery/network_discovery#host_naming).<br>This option is supported since 4.2.0.| |*Enabled*|With the check-box marked the rule is active and will be executed by Zabbix server.<br>If unmarked, the rule is not active. It won't be executed.|
zh-cn	#### 规则属性  ![](../../../../assets/en/manual/discovery/network_discovery/d_rule.png)  所有强制输入区域会标记为红色星号。  |参数|描述| |---------|-----------| |*名称*|唯一的规则名称。比如，"Local network"。| |*执行发现的proxy*|哪个组件执行网络发现:<br>**没有proxy** - Zabbix server执行网络发现<br>**<proxy 名称>** - 此proxy执行网络发现| |*IP地址范围*|需要发现的IP地址范围。包括下列格式:<br>单IP: 192.168.1.33<br>IP地址范围: 192.168.1-10.1-255。IP地址范围取决于包含的所有地址数量(小于64K)。<br>IP子网掩码: 192.168.4.0/24<br>支持的IP掩码:<br>/16 - /30 用于 IPv4地址<br>/112 - /128用于IPv6地址<br>列表: 192.168.1.1-255, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>从Zabbix 3.0.0起支持空格、制表符和多行。| |*更新间隔*|此参数定义了规则执行的时间间隔。<br>前一次发现任务执行完毕才会开始时间间隔计时，所以不会有重叠。<br>从Zabbix 3.4.0开始支持[时间后缀](/manual/appendix/suffixes)，例如30s, 1m, 2h, 1d。<br>从Zabbix 3.4.0开始支持[用户宏](/manual/config/macros/user_macros)。<br>*注意* 如果使用了用户宏并且其值改变(比如 1w → 1h)，下次检查会基于上一个值进行计算。(如果时间拉到很远的未来，会以示例值计算)。| |*检查*|Zabbix会使用此检查列表来执行网络发现。点击 ![](../../../../assets/en/manual/discovery/network_discovery/add_link.png) 在弹窗中配置一个新检查。<br>支持的检查: SSH, LDAP, SMTP, FTP, HTTP, HTTPS, POP, NNTP, IMAP, TCP, Telnet, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping.<br>基于协议的自动发现使用**net.tcp.service\[\]** 功能来检测每台主机，查询SNMP OID的SNMP服务不在此列。通过查询未加密模式的监控项来探测Zabbix agent的存在。请查阅[agent监控项](/manual/config/items/itemtypes/zabbix_agent)获取更多信息。<br>'端口'参数的格式如下：<br>单一端口: 22<br>端口范围: 22-45<br>列表: 22-45,55,60-70| |*设备唯一标识*|唯一标识可以设置为：<br>**IP地址** - 不对多台相同IP的设备做处理。如果一台相同IP的设备已经存在，则该设备视为已经发现并且不会添加新设备。<br>**<发现检查>** - 选择Zabbix agent或SNMP agent检查。| |*主机名称*|设置主机的技术名称：<br>**DNS名称** - DNS名称 (默认)<br>**IP地址** - IP地址<br>**<发现检查>** - 通过发现检查收到的字符串值 (比如 Zabbix agent, SNMP agent 检查)<br>另请参阅: [主机命名](/manual/discovery/network_discovery#host_naming).<br>从4.2.0版本起支持此选项。| |*可见名称*|设置主机的可见名称:<br>**Host name** - 技术主机名称 (默认)<br>**DNS名称** - DNS名称<br>**IP地址** - IP地址<br>**<发现检查>** - 通过发现检查收到的字符串值 (比如 Zabbix agent, SNMP agent check)<br>另请参阅: [主机命名](/manual/discovery/network_discovery#host_naming).<br>从4.2.0版本起支持此选项。| |*启用*|勾选检查框启用规则。<br>如果取消勾选，则规则变成未启用状态且不会执行。|

en-us	#### Run a custom script  Run a "ping" script on a host.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.execute",     "params": {         "scriptid": "1",         "hostid": "30079"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "response": "success",         "value": "PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.\n64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.074 ms\n64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.030 ms\n64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.030 ms\n\n--- 127.0.0.1 ping statistics ---\n3 packets transmitted, 3 received, 0% packet loss, time 1998ms\nrtt min/avg/max/mdev = 0.030/0.044/0.074/0.022 ms\n",         "debug": []     },     "id": 1 } ```
zh-cn	#### 运行自定义脚本  在主机上运行“ping”脚本。  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.execute",     "params": {         "scriptid": "1",         "hostid": "30079"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "response": "success",         "value": "PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.\n64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.074 ms\n64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.030 ms\n64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.030 ms\n\n--- 127.0.0.1 ping statistics ---\n3 packets transmitted, 3 received, 0% packet loss, time 1998ms\nrtt min/avg/max/mdev = 0.030/0.044/0.074/0.022 ms\n",         "debug": []     },     "id": 1 } ```

en-us	#### Run a webhook script  Run a webhook script that sends HTTP request to external service.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.execute",     "params": {         "scriptid": "4",         "hostid": "30079"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "response": "success",         "value": "{\"status\":\"sent\",\"timestamp\":\"1611235391\"}",         "debug": {             "logs": [                  {                      "level": 3,                      "ms": 480,                      "message": "[Webhook Script] HTTP status: 200."                  }              ],              "ms": 495         }     },     "id": 1 } ```
zh-cn	#### 运行 webhook 脚本  运行一个向外部服务发送HTTP请求的webhook脚本。  请求： ```json {     "jsonrpc": "2.0",     "method": "script.execute",     "params": {         "scriptid": "4",         "hostid": "30079"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ``` 响应： ```json {     "jsonrpc": "2.0",     "result": {         "response": "success",         "value": "{\"status\":\"sent\",\"timestamp\":\"1611235391\"}",         "debug": {             "logs": [                  {                      "level": 3,                      "ms": 480,                      "message": "[Webhook Script] HTTP status: 200."                  }              ],              "ms": 495         }     },     "id": 1 } ```

en-us	#### Running agent  The agent will start automatically after installation or restart.  You may edit the configuration file at `/usr/local/etc/zabbix/zabbix_agentd.conf` if necessary.  To start the agent manually, you may run:      sudo launchctl start com.zabbix.zabbix_agentd  To stop the agent manually:      sudo launchctl stop com.zabbix.zabbix_agentd  During upgrade, the existing configuration file is not overwritten. Instead a new `zabbix_agentd.conf.NEW` file is created to be used for reviewing and updating the existing configuration file, if necessary. Remember to restart the agent after manual changes to the configuration file.
zh-cn	#### 运行 Agent  Agent将在安装或重新启动后自动启动。  如有需要，你可以编辑位于`/usr/local/etc/zabbix/zabbix_agentd.conf` 的配置文件。  手动启动 agent，你可以执行:      sudo launchctl start com.zabbix.zabbix_agentd  手动停止 agent，你可以执行:      sudo launchctl stop com.zabbix.zabbix_agentd  在升级过程中，现有配置文件不会被覆盖。 如有需要，它将被替换为一个新的 `zabbix_agentd.conf.NEW` 文件，用于查看和更新现有配置文件。 请记得在手动更改配置文件后重新启动 agent 。

en-us	#### Running proxy
zh-cn	#### 运行Proxy

en-us	#### Running server
zh-cn	#### 服务进程

en-us	### Runtime commands for profiling  Runtime commands for profiling have been added to Zabbix server and Zabbix proxy.   -    `prof_enable` - enable profiling -    `prof_disable` - disable profiling  Profiling can be enabled per server/proxy process. Enabled profiling provides details of all rwlocks/mutexes by function name.  See also:  -   [Zabbix server runtime commands](/manual/concepts/server#runtime-control) -   [Zabbix proxy runtime commands](/manual/concepts/proxy#runtime-control)
zh-cn	### 用于分析的运行时命令  用于分析的运行时命令已添加到 Zabbix 服务器和 Zabbix 代理。  - · `prof_enable` - 启用分析 - · `prof_disable` - 禁用分析  可以为每个服务器/代理进程启用分析。 启用的分析按函数名称提供所有 rwlocks/mutexes 的详细信息。  也可以看看：  - · [Zabbix 服务器运行时命令](/manual/concepts/server#runtime-control) - · [Zabbix 代理运行时命令](/manual/concepts/proxy#runtime-control)

en-us	 ### Runtime command transfer Zabbix server and proxy runtime commands are now sent via socket instead of Unix signals. This change allowed to improve user experience working with runtime control options:  - Results of the command execution are now printed to the console. - It is possible to send longer input parameters, such as HA node name instead of node number.
zh-cn	### 运行时命令传输  Zabbix server 和 proxy 运行时命令现在通过套接字而不是 Unix 信号发送。此更改可以改善使用运行时控制选项的用户体验：  - 命令执行的结果会打印到控制台。 - 可以发送更长的输入参数，例如 HA 节点名称而不是节点编号。

en-us	##### Runtime command transfer  Zabbix server and proxy runtime commands are now sent via socket instead of Unix signals. This  change allows to improve user experience working with runtime control options:  -   Results of the command execution are now printed to the console. -   It is possible to send longer input parameters, such as HA node name instead of node number.
zh-cn	##### 运行时命令的传输  Zabbix server 和 proxy 运行时命令现在通过套接字而不是 Unix 信号发送。此更改可以改善使用运行时控制选项的用户体验：  -   命令执行的结果会打印到控制台。 -   可以发送更长的输入参数，例如 HA 节点名称而不是节点编号。

en-us	###      Runtime control options     **config\_cache\_reload**   Reload configuration cache. Ignored if cache is being currently loaded. Active Zabbix proxy will connect to the Zabbix server and request configuration data. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file.     **snmp\_cache\_reload**   Reload SNMP cache.     **housekeeper\_execute**   Execute the housekeeper. Ignored if housekeeper is being currently executed.     **diaginfo**\[=*section*\]   Log internal diagnostic information of the specified section. Section can be *historycache*, *preprocessing*. By default diagnostic information of all sections is logged.     **log\_level\_increase**\[=*target*\]   Increase log level, affects all processes if target is not specified.     **log\_level\_decrease**\[=*target*\]   Decrease log level, affects all processes if target is not specified.  [ ]{#lbAG}
zh-cn	 ###      运行时控制选项     **config\_cache\_reload**   重新加载配置缓存。如果当前正在加载缓存，则忽略。活动的Zabbix proxy将连接到Zabbix server并请求配置数据。默认配置文件（除非指定了**-c**选项）将用于查找PID文件，并将信号发送到进程，在PID文件中列出。     **snmp\_cache\_reload**   重新加载 SNMP 缓存。     **housekeeper\_execute**   执行housekeeper。如果当前housekeeper正在被执行则忽略。     **diaginfo**\[=*section*\]   记录指定部分的内部诊断信息。节可以是*historycache*，*preprocessing*。默认情况下，记录所有部分的诊断信息。     **log\_level\_increase**\[=*target*\]   提升日志级别，如果未指定目标，则会影响所有进程。     **log\_level\_decrease**\[=*target*\]   降低日志级别，如果未指定目标，则会影响所有进程。  [ ]{#lbAG}

en-us	##### Runtime control  Runtime control options:  |Option|Description|Target| |------|-----------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.<br>Active Zabbix proxy will connect to the Zabbix server and request configuration data.|<| |diaginfo\[=<**target**>\]|Gather diagnostic information in the proxy log file.|**historycache** - history cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**locks** - list of mutexes| |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.|<| |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.|<| |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)<br>See all [proxy process types](#proxy_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.|^|  Example of using runtime control to reload the proxy configuration cache:      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R config_cache_reload  Examples of using runtime control to gather diagnostic information:      Gather all available diagnostic information in the proxy log file:     shell> zabbix_proxy -R diaginfo      Gather history cache statistics in the proxy log file:     shell> zabbix_proxy -R diaginfo=historycache  Example of using runtime control to reload the SNMP cache:      shell> zabbix_proxy -R snmp_cache_reload    Example of using runtime control to trigger execution of housekeeper      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R housekeeper_execute  Examples of using runtime control to change log level:      Increase log level of all processes:     shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase      Increase log level of second poller process:     shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=poller,2      Increase log level of process with PID 1234:     shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=1234      Decrease log level of all http poller processes:     shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_decrease="http poller"  
zh-cn	##### 进程用户  Zabbix proxy 允许使用非 root 用户运行。它将以任何非 root 用户的身份运行。因此，使用非 root 用户运行 proxy 是没有任何问题的.  如果你试图以“root”身份运行它，它将会切换到一个已经“写死”的“zabbix”用户，该用户必须存在于您的系统上。如果您只想以“root”用户运行 proxy，您必须在 proxy 配置文件里修改‘AllowRoot‘参数。  

en-us	##### Runtime control  Runtime control options:  |Option|Description|Target| |------|-----------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.|<| |diaginfo\[=<**target**>\]|Gather diagnostic information in the server log file.|**historycache** - history cache statistics<br>**valuecache** - value cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**alerting** - alert manager statistics<br>**lld** - LLD manager statistics<br>**locks** - list of mutexes| |ha\_status|Log high availability (HA) cluster status.|<| |ha\_remove\_node=target|Remove the high availability (HA) node specified by its listed number.<br>Note that active/standby nodes cannot be removed.|**target** - number of the node in the list (can be obtained by running ha\_status)| |ha\_set\_failover\_delay=delay|Set high availability (HA) failover delay.<br>Time suffixes are supported, e.g. 10s, 1m.|<| |secrets\_reload|Reload secrets from Vault.|<| |service\_cache\_reload|Reload the service manager cache.|<| |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.|<| |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.|<| |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)<br>See all [server process types](#server_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.|^|  Example of using runtime control to reload the server configuration cache:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload  Examples of using runtime control to gather diagnostic information:      Gather all available diagnostic information in the server log file:     shell> zabbix_server -R diaginfo      Gather history cache statistics in the server log file:     shell> zabbix_server -R diaginfo=historycache  Example of using runtime control to reload the SNMP cache:      shell> zabbix_server -R snmp_cache_reload    Example of using runtime control to trigger execution of housekeeper:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute  Examples of using runtime control to change log level:      Increase log level of all processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase      Increase log level of second poller process:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2      Increase log level of process with PID 1234:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234      Decrease log level of all http poller processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller"  Example of setting the HA failover delay to the minimum of 10 seconds:      shell> zabbix_server -R ha_set_failover_delay=10s  
zh-cn	##### 运行时控制  运行时控制包含的选项：  |选项                                          描|目标|<| |---------------------------------------------------|------|-| |config\_cache\_reload|重新加载配置缓存。如果当前正在加载缓存，则忽略。|<| |housekeeper\_execute|启动管家程序。忽略当前正在进行中的管家程序。|<| |log\_level\_increase\[=<**target**>\]|增加日志级别，如果未指定目标，将影响所有进程。     **pid** - 进程标识符 (1 to|5535)<br>**process type** - 指定进程的所有类型 (例如，poller)<br>**process type,N** - 进程类型和编号 (例如，poller,3)| |log\_level\_decrease\[=<**target**>\]|降低日志级别，如果未指定目标，则会影响所有进程。   :::|<|  单一 Zabbix 进程的日志级别改变后，进程的 PIDs 的值也会改变，允许的范围为1\~65535。在具有大 PIDs <process type,N> 目标选项可更改单个进程的日志级别。  例如，使用 config\_cache\_reload 选项重新加载 server 的配置缓存：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload  例如，使用 housekeeper\_execute 选项来触发管家服务执行：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute  例如，使用 log\_level\_increase 选项来改变日志级别：      增加所有进程的日志级别：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase      增加第二个 Poller 进程的日志级别：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2      增加 PID 为 1234 进程的日志级别：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234      降低 http poller 进程的日志级别：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller"  

en-us	##### Runtime control  Runtime control options:  |Option|Description|Target| |------|-----------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.| | |diaginfo\[=<**target**>\]|Gather diagnostic information in the server log file.|**historycache** - history cache statistics<br>**valuecache** - value cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**alerting** - alert manager statistics<br>**lld** - LLD manager statistics<br>**locks** - list of mutexes| |ha\_status|Log high availability (HA) cluster status.| | |ha\_remove\_node=target|Remove the high availability (HA) node specified by its listed number.<br>Note that active/standby nodes cannot be removed.|**target** - number of the node in the list (can be obtained by running ha\_status)| |ha\_set\_failover\_delay=delay|Set high availability (HA) failover delay.<br>Time suffixes are supported, e.g. 10s, 1m.| | |secrets\_reload|Reload secrets from Vault.| | |service\_cache\_reload|Reload the service manager cache.| | |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.| | |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified.|**process type** - All processes of specified type (e.g., poller)<br>See all [server process types](#server_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.|^|  Example of using runtime control to reload the server configuration cache:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload  Examples of using runtime control to gather diagnostic information:      Gather all available diagnostic information in the server log file:     shell> zabbix_server -R diaginfo      Gather history cache statistics in the server log file:     shell> zabbix_server -R diaginfo=historycache  Example of using runtime control to reload the SNMP cache:      shell> zabbix_server -R snmp_cache_reload    Example of using runtime control to trigger execution of housekeeper:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute  Examples of using runtime control to change log level:      Increase log level of all processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase      Increase log level of second poller process:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2      Increase log level of process with PID 1234:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234      Decrease log level of all http poller processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller"  Example of setting the HA failover delay to the minimum of 10 seconds:      shell> zabbix_server -R ha_set_failover_delay=10s  
zh-cn	##### 运行时控制  运行时控制包含的选项：  |选项|描述|目标| |------|-----------|------| |config\_cache\_reload|重新加载配置缓存。如果当前正在加载缓存，则忽略。| | |diaginfo\[=<**target**>\]|在服务器日志文件中收集诊断信息。|**historycache** - 历史缓存统计<br>**valuecache** - 值缓存统计<br>**preprocessing** -预处理管理器统计<br>**alerting** - 警报管理器统计<br>**lld** - LLD 管理器统计<br>**locks** - 互斥锁列表| |ha\_status|记录高可用性 (HA) 集群状态。| | |ha\_remove\_node=target| 删除由其列出的编号指定的高可用性 (HA) 节点。<br>请注意，不能移除主备节点。|**target** - 列表中节点的编号（可以通过运行 ha_status 获得）| |ha\_set\_failover\_delay=delay|设置高可用性 (HA) 故障转移延迟。<br>支持时间后缀，例如 10s、1m。| | |secrets\_reload|从 Vault 重新加载秘钥。| | |service\_cache\_reload|重新加载服务管理器缓存。| | |snmp\_cache\_reload|重新加载 SNMP 缓存，清除所有主机的 SNMP 属性（引擎时间、引擎启动、引擎 ID、凭据）。| | |housekeeper\_execute|开始管家处理程序。如果当前正在进行管家处理程序，则忽略。| | |log\_level\_increase\[=<**target**>\]|增加日志级别，如果未指定目标，则影响所有进程。|**process type** - 指定类型的所有进程（例如，轮询器）<br>查看所有 [服务器进程类型](#server_process_types)。<br>**process type,N** -进程类型和编号（例如，轮询器,3）<br>**pid** - 进程标识符（1 到 65535）。对于较大的值，将目标指定为“进程类型，N”。| |log\_level\_decrease\[=<**target**>\]|降低日志级别，如果未指定目标，则影响所有进程。|^|  使用运行时控制重新加载服务器配置缓存的示例：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R config_cache_reload  使用运行时控制收集诊断信息的示例：      Gather all available diagnostic information in the server log file:     shell> zabbix_server -R diaginfo      Gather history cache statistics in the server log file:     shell> zabbix_server -R diaginfo=historycache  使用运行时控制重新加载 SNMP 缓存的示例：      shell> zabbix_server -R snmp_cache_reload    使用运行时控制触发管家执行的示例：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R housekeeper_execute  使用运行时控制更改日志级别的示例：      Increase log level of all processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase      Increase log level of second poller process:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=poller,2      Increase log level of process with PID 1234:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase=1234      Decrease log level of all http poller processes:     shell> zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_decrease="http poller"  将 HA 故障转移延迟设置为最短 10 秒的示例：      shell> zabbix_server -R ha_set_failover_delay=10s

en-us	##### Runtime control  Runtime control options:  |Option|Description|Target| |------|-----------|------| |config\_cache\_reload|Reload configuration cache. Ignored if cache is being currently loaded.| | |diaginfo\[=<**target**>\]|Gather diagnostic information in the server log file.|**historycache** - history cache statistics<br>**valuecache** - value cache statistics<br>**preprocessing** - preprocessing manager statistics<br>**alerting** - alert manager statistics<br>**lld** - LLD manager statistics<br>**locks** - list of mutexes (is empty on **BSD* systems)| |ha\_status|Log high availability (HA) cluster status.| | |ha\_remove\_node=target|Remove the high availability (HA) node specified by its listed number.<br>Note that active/standby nodes cannot be removed.|**target** - number of the node in the list (can be obtained by running ha\_status)| |ha\_set\_failover\_delay=delay|Set high availability (HA) failover delay.<br>Time suffixes are supported, e.g. 10s, 1m.| | |secrets\_reload|Reload secrets from Vault.| | |service\_cache\_reload|Reload the service manager cache.| | |snmp\_cache\_reload|Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts.| | |housekeeper\_execute|Start the housekeeping procedure. Ignored if the housekeeping procedure is currently in progress.| | |log\_level\_increase\[=<**target**>\]|Increase log level, affects all processes if target is not specified.<br>Not supported on **BSD* systems.|**process type** - All processes of specified type (e.g., poller)<br>See all [server process types](#server_process_types).<br>**process type,N** - Process type and number (e.g., poller,3)<br>**pid** - Process identifier (1 to 65535). For larger values specify target as 'process type,N'.| |log\_level\_decrease\[=<**target**>\]|Decrease log level, affects all processes if target is not specified.<br>Not supported on **BSD* systems.|^|  
zh-cn	##### 运行时控制  运行时控制选项：  |选项|描述|目标| |--------|------------|------| |config\_cache\_reload|重新加载配置缓存。如果当前正在加载缓存，则忽略。| | |diaginfo\[=<**target**>\]|在服务器日志文件中收集诊断信息。|**historycache** - 历史缓存统计<br>**valuecache** - 值缓存统计<br>* *preprocessing** - 预处理管理器统计信息<br>**alerting** - 警报管理器统计信息<br>**lld** - LLD 管理器统计信息<br>**locks** - 互斥锁列表（在 ** 上为空BSD* 系统）| |ha\_status|记录高可用性 (HA) 集群状态。| | |ha\_remove\_node=target|删除由其列出的编号指定的高可用性 (HA) 节点。<br>请注意，无法删除活动/备用节点。|**target** - 列表中的节点编号（可以通过运行 ha\_status 获得）| |ha\_set\_failover\_delay=delay|设置高可用性 (HA) 故障转移延迟。<br>支持时间后缀，例如10 秒，1 分钟。| | |secrets\_reload|从 Vault 重新加载秘钥。| | |service\_cache\_reload|重新加载服务管理器缓存。| | |snmp\_cache\_reload|重新加载 SNMP 缓存，清除所有主机的 SNMP 属性（引擎时间、引擎启动、引擎 ID、凭据）。| | |housekeeper\_execute|启动管家程序。如果当前正在进行管家处理程序，则忽略。| | |log\_level\_increase\[=<**target**>\]|增加日志级别，如果未指定 target，则影响所有进程。<br>在 **BSD* 系统上不受支持。|**进程类型* * - 指定类型的所有进程（例如，轮询器）<br>查看所有 [服务器进程类型](#server_process_types)。<br>**进程类型，N** - 进程类型和编号（例如，轮询器，3） <br>**pid** - 进程标识符（1 到 65535）。对于较大的值，请将目标指定为“进程类型，N”。| |log\_level\_decrease\[=<**target**>\]|降低日志级别，如果未指定 target，则影响所有进程。<br>在 **BSD* 系统上不支持。|^|  

en-us	### Runtime controls on BSD-based OS Previously, Zabbix server and Zabbix proxy runtime control options were not supported on BSD-based systems. Changing the runtime command transfer method has allowed to withdraw this limitation. Now the majority of the commands are supported on *FreeBSD*, *NetBSD*, *OpenBSD*, and other operating systems from the **BSD* family. For the exact list, see *Runtime control* for Zabbix [server](/manual/concepts/server#runtime_control) or [proxy](/manual/concepts/proxy#runtime_control). 
zh-cn	### 基于 BSD 的操作系统上的运行时控制  以前，基于 BSD 的系统不支持 Zabbix server 和 Zabbix proxy 运行时控制选项。更改运行时命令传输方法已允许取消此限制。现在*FreeBSD*、*NetBSD*、*OpenBSD* 和 **BSD* 系列的其他操作系统都支持大多数命令。有关确切列表，请参阅 Zabbix [server](/manual/concepts/server#runtime_control)  或 [proxy](/manual/concepts/proxy#runtime_control) 的 *运行时控制* 。

en-us	### SAML authentication  SAML 2.0 authentication can be used to sign in to Zabbix. Note that a user must exist in Zabbix, however, its Zabbix password will not be used. If authentication is successful, then Zabbix will match a local username with the username attribute returned by SAML.  ::: noteclassic  If SAML authentication is enabled, users will be able to choose between logging in locally or via SAML Single Sign-On.  :::
zh-cn	### SAML 身份验证  SAML 2.0 身份验证可用于登录 Zabbix。 请注意，用户必须存在于 Zabbix 中，但不会使用其 Zabbix 密码。 如果身份验证成功，则 Zabbix 会将本地用户名与 SAML 返回的用户名属性进行匹配。  ::: noteclass   如果启用 SAML 身份验证，用户将能够在本地登录或通过 SAML 单点登录之间进行选择。 :::

en-us	#### Scenario
zh-cn	#### 场景

en-us	#### Scenario items  As soon as a scenario is created, Zabbix automatically adds the following items for monitoring.  |Item|Description| |----|-----------| |*Download speed for scenario <Scenario>*|This item will collect information about the download speed (bytes per second) of the whole scenario, i.e. average for all steps.<br>Item key: web.test.in\[Scenario,,bps\]<br>Type: *Numeric(float)*| |*Failed step of scenario <Scenario>*|This item will display the number of the step that failed on the scenario. If all steps are executed successfully, 0 is returned.<br>Item key: web.test.fail\[Scenario\]<br>Type: *Numeric(unsigned)*| |*Last error message of scenario <Scenario>*|This item returns the last error message text of the scenario. A new value is stored only if the scenario has a failed step. If all steps are ok, no new value is collected.<br>Item key: web.test.error\[Scenario\]<br>Type: *Character*|  The actual scenario name will be used instead of "Scenario".  ::: noteclassic Web monitoring items are added with a 30 day history and a 90 day trend retention period. :::  ::: noteclassic If scenario name starts with a doublequote or contains comma or square bracket, it will be properly quoted in item keys. In other cases no additional quoting will be performed. :::  These items can be used to create triggers and define notification conditions.
zh-cn	#### 场景监控项  一旦创建了一个场景，Zabbix 就会自动添加以下监控项。  |监控项|描述| |----|-----------| |*Download speed for scenario <Scenario>*|该监控项将收集有关整个场景的下载速度（每秒字节数）的信息，即所有步骤的平均值。<br>监控项键值： web.test.in\[Scenario,,bps\]<br>类型： *Numeric(float)*| |*Failed step of scenario <Scenario>*|该监控项将显示场景中失败的步骤数。如果所有步骤都成功执行，则返回 0。<br>监控项键值： web.test.fail\[Scenario\]<br>类型： *Numeric(unsigned)*| |*Last error message of scenario <Scenario>*|该监控项返回场景的最后一条错误消息文本。仅当场景具有失败的步骤时才存储新值。如果所有步骤都正常，则不会收集新值。<br>监控项键值： web.test.error\[Scenario\]<br>类型： *Character*|  将使用实际场景名称而不是 "Scenario（场景）"。  ::: noteclassic Web 监控项添加了 30 天的历史记录和 90 天的趋势数据保留时长。 :::  ::: noteclassic 如果场景名称以双引号开头或包含逗号或方括号，它将在监控项键值中被正确引用。在其他情况下，将不执行额外的引用。 :::  这些监控项可用于创建触发器和定义通知条件。

en-us	#### Scenario step items  As soon as a step is created, Zabbix automatically adds the following items for monitoring.  |Item|Description| |----|-----------| |*Download speed for step <Step> of scenario <Scenario>*|This item will collect information about the download speed (bytes per second) of the step.<br>Item key: web.test.in\[Scenario,Step,bps\]<br>Type: *Numeric(float)*| |*Response time for step <Step> of scenario <Scenario>*|This item will collect information about the response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred.<br>Item key: web.test.time\[Scenario,Step,resp\]<br>Type: *Numeric(float)*| |*Response code for step <Step> of scenario <Scenario>*|This item will collect response codes of the step.<br>Item key: web.test.rspcode\[Scenario,Step\]<br>Type: *Numeric(unsigned)*|  Actual scenario and step names will be used instead of "Scenario" and "Step" respectively.  ::: noteclassic Web monitoring items are added with a 30 day history and a 90 day trend retention period. :::  ::: noteclassic If scenario name starts with a doublequote or contains comma or square bracket, it will be properly quoted in item keys. In other cases no additional quoting will be performed. :::  These items can be used to create triggers and define notification conditions. For example, to create a "Zabbix GUI login is too slow" trigger, you can define a trigger expression:      last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3
zh-cn	#### 场景步骤监控项  一旦创建了一个步骤，Zabbix 就会自动添加以下监控项。  |监控项|描述| |----|-----------| |*Download speed for step <Step> of scenario <Scenario>*|该监控项收集有关该步骤的下载速度（每秒字节数）的信息。<br>监控项键值：web.test.in\[Scenario,Step,bps\]<br>类型：*Numeric(float)*| |*Response time for step <Step> of scenario <Scenario>*|该监控项收集有关步骤响应时间的信息（以秒为单位）。响应时间是从请求开始到所有信息传输完毕的时间。<br>监控项键值： web.test.time\[Scenario,Step,resp\]<br>类型： *Numeric(float)*| |*Response code for step <Step> of scenario <Scenario>*|该监控项收集步骤的响应代码。<br>监控项键值： web.test.rspcode\[Scenario,Step\]<br>类型： *Numeric(unsigned)*|  将分别使用实际场景和步骤名称代替 "Scenario" 和 "Step"。  ::: noteclassic Web 监控项添加了 30 天的历史记录和 90 天的趋势数据保留时长。 :::  ::: noteclassic 如果场景名称以双引号开头或包含逗号或方括号，它将在监控项键值中正确引用。在其他情况下，将不执行额外的引用。 :::  这些监控项可用于创建触发器和定义通知条件。例如，要创建一个 "Zabbix GUI login is too slow"的触发器，可以定义一个触发器表达式：      last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3

en-us	### Scenario step  The scenario step object defines a specific web scenario check. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |httpstepid|string|*(readonly)* ID of the scenario step.| |**name**<br>(required)|string|Name of the scenario step.| |**no**<br>(required)|integer|Sequence number of the step in a web scenario.| |**url**<br>(required)|string|URL to be checked.| |follow\_redirects|integer|Whether to follow HTTP redirects.<br><br>Possible values are:<br>0 - don't follow redirects;<br>1 - *(default)* follow redirects.| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP headers that will be sent when performing a request. Scenario step headers will overwrite headers specified for the web scenario.| |httptestid|string|*(readonly)* ID of the web scenario that the step belongs to.| |posts|string<br>array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP POST variables as a string (raw post data) or as an array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) (form field data).| |required|string|Text that must be present in the response.| |retrieve\_mode|integer|Part of the HTTP response that the scenario step must retrieve.<br><br>Possible values are:<br>0 - *(default)* only body;<br>1 - only headers;<br>2 - headers and body.| |status\_codes|string|Ranges of required HTTP status codes separated by commas.| |timeout|string|Request timeout in seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Default: 15s. Maximum: 1h. Minimum: 1s.| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Scenario step variables.| |query\_fields|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Query fields - array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) that will be added to URL when performing a request|
zh-cn	 ### 场景步骤  场景步骤对象定义了一个特定的Web场景检查。具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |httpstepid|string|*(只读)* Web场景步骤ID。| |**name**<br>(必填)|string|Web场景的名称。| |**no**<br>(必填)|integer|一个Web场景步骤的序列号。| |**url**<br>(必填)|string|待检查的URL。| |follow\_redirects|integer|是否遵循HTTP重定向。<br><br>可用值：<br>0 - 不遵循重定向；<br>1 - *(默认)* 遵循重定向。| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|执行请求时将发送的HTTP请求头。场景步骤请求头将被重写为Web场景指定的请求头。| |httptestid|string|*(只读)* 步骤所属Web场景的ID。| |posts|string<br>array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|HTTP POST变量作为一个字符串（原始的post数据）或一个[HTTP fields](/manual/api/reference/httptest/object#HTTP字段) (表单字段数据)的数组。| |required|string|响应中必须出现的文本。| |retrieve\_mode|integer|场景步骤必须获取的一部分HTTP响应。<br><br>可用值：<br>0 - *(默认)* 仅返回内容；<br>1 - 仅请求头；<br>2 - 请求头和内容。| |status\_codes|string|用逗号隔开的所需HTTP状态码的范围。| |timeout|string|请求超时时间（秒）。接受秒，带后缀的时间单位和用户宏。<br><br>默认： 15s。 最大值： 1h。 最小值: 1s。| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|场景步骤的变量。| |query\_fields|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|查询字段 - 执行请求时将被添加到URL中的[HTTP fields](/manual/api/reference/httptest/object#HTTP字段)数组。|

en-us	### Scenario step  The scenario step object defines a specific web scenario check. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |httpstepid|string|*(readonly)* ID of the scenario step.| |**name**<br>(required)|string|Name of the scenario step.| |**no**<br>(required)|integer|Sequence number of the step in a web scenario.| |**url**<br>(required)|string|URL to be checked.| |follow\_redirects|integer|Whether to follow HTTP redirects.<br><br>Possible values are:<br>0 - don't follow redirects;<br>1 - *(default)* follow redirects.| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP headers that will be sent when performing a request. Scenario step headers will overwrite headers specified for the web scenario.| |httptestid|string|*(readonly)* ID of the web scenario that the step belongs to.| |posts|string<br>array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|HTTP POST variables as a string (raw post data) or as an array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) (form field data).| |required|string|Text that must be present in the response.| |retrieve\_mode|integer|Part of the HTTP response that the scenario step must retrieve.<br><br>Possible values are:<br>0 - *(default)* only body;<br>1 - only headers;<br>2 - headers and body.| |status\_codes|string|Ranges of required HTTP status codes separated by commas.| |timeout|string|Request timeout in seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Default: 15s. Maximum: 1h. Minimum: 1s.| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Scenario step variables.| |query\_fields|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field)|Query fields - array of [HTTP fields](/manual/api/reference/httptest/object#HTTP field) that will be added to URL when performing a request|
zh-cn	 ### 场景步骤  场景步骤对象定义了一个特定的Web场景检查。具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |httpstepid|string|*(只读)* Web场景步骤ID。| |**name**<br>(必填)|string|Web场景的名称。| |**no**<br>(必填)|integer|一个Web场景步骤的序列号。| |**url**<br>(必填)|string|待检查的URL。| |follow\_redirects|integer|是否遵循HTTP重定向。<br><br>可用值：<br>0 - 不遵循重定向；<br>1 - *(默认)* 遵循重定向。| |headers|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|执行请求时将发送的HTTP请求头。场景步骤请求头将被重写为Web场景指定的请求头。| |httptestid|string|*(只读)* 步骤所属Web场景的ID。| |posts|string<br>array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|HTTP POST变量作为一个字符串（原始的post数据）或一个[HTTP fields](/manual/api/reference/httptest/object#HTTP字段) (表单字段数据)的数组。| |required|string|响应中必须出现的文本。| |retrieve\_mode|integer|场景步骤必须获取的一部分HTTP响应。<br><br>可用值：<br>0 - *(默认)* 仅返回内容；<br>1 - 仅请求头；<br>2 - 请求头和内容。| |status\_codes|string|用逗号隔开的所需HTTP状态码的范围。| |timeout|string|请求超时时间（秒）。接受秒，带后缀的时间单位和用户宏。<br><br>默认： 15s。 最大值： 1h。 最小值: 1s。| |variables|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|场景步骤的变量。| |query\_fields|array of [HTTP fields](/manual/api/reference/httptest/object#HTTP字段)|查询字段 - 执行请求时将被添加到URL中的[HTTP fields](/manual/api/reference/httptest/object#HTTP字段)数组。|

en-us	#### Scheduling intervals  Scheduling intervals are used to check items at specific times. While flexible intervals are designed to redefine the default item update interval, the scheduling intervals are used to specify an independent checking schedule, which is executed in parallel.  A scheduling interval is defined as: `md<filter>wd<filter>h<filter>m<filter>s<filter>` where:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` is used to specify values for its prefix (days, hours, minutes, seconds) and is defined as: `[<from>[-<to>]][/<step>][,<filter>]` where:  -   `<from>` and `<to>` define the range of matching values (included).     If `<to>` is omitted then the filter matches a `<from> - <from>`     range. If `<from>` is also omitted then the filter matches all     possible values. -   `<step>` defines the skips of the number value through the range. By     default `<step>` has the value of 1, which means that all values of     the defined range are matched.  While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the *<step>* value defined.  An empty filter matches either '0' if no lower-level filter is defined or all possible values otherwise. For example, if the hour filter is omitted then only '0' hour will match, provided minute and seconds filters are omitted too, otherwise an empty hour filter will match all hour values.  Valid `<from>` and `<to>` values for their respective filter prefix are:  |Prefix|Description|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  The `<from>` value must be less or equal to `<to>` value. The `<step>` value must be greater or equal to 1 and less or equal to `<to>` - `<from>`.  Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example `md01-31` and `h/02` are valid intervals, but `md01-031` and `wd01-07` are not.  In Zabbix frontend, multiple ​scheduling intervals ​are entered in separate rows. In Zabbix API, they are concatenated into a single string ​with a semicolon `;` ​as a separator.  If a time is matched by several intervals it is executed only once. For example, `wd1h9;h9` will be executed only once on Monday at 9am.  Examples:  |Interval|Will be executed| |--------|----------------| |m0-59|every minute| |h9-17/2|every 2 hours starting with 9:00 (9:00, 11:00 ...)| |m0,30 or m/30|hourly at hh:00 and hh:30| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|every five minutes| |wd1-5h9|every Monday till Friday at 9:00| |wd1-5h9-18|every Monday till Friday at 9:00,10:00,...,18:00| |h9,10,11 or h9-11|every day at 9:00, 10:00 and 11:00| |md1h9m30|every 1st day of each month at 9:30| |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday| |h9m/30|every day at 9:00, 9:30| |h9m0-59/30|every day at 9:00, 9:30| |h9,10m/30|every day at 9:00, 9:30, 10:00, 10:30| |h9-10m30|every day at 9:30, 10:30| |h9m10-40/30|every day at 9:10, 9:40| |h9,10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9-10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9m10-40|every day at 9:10, 9:11, 9:12, ... 9:40| |h9m10-40/1|every day at 9:10, 9:11, 9:12, ... 9:40| |h9-12,15|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0s30|every day at 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30| |h9-12s30|every day at 9:00:30, 9:01:30, 9:02:30 ... 12:58:30, 12:59:30| |h9m/30;h10 (*API-specific syntax*)|every day at 9:00, 9:30, 10:00| |h9m/30<br>h10 (*add this as another row in frontend*)|every day at 9:00, 9:30, 10:00|  
zh-cn	#### 调度间隔  调度间隔用于在特定时间检查监控项。虽然灵活间隔被设计为重新定义默认监控项的更新间隔，但是调度间隔用于指定并行执行的检查计划。  调度间隔定义为: `md<filter>wd<filter>h<filter>m<filter>s<filter>` 其中:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` 用于指定其前缀的值(日, 时, 分, 秒) 并被定义为: `[<from>[-<to>]][/<step>][,<filter>]` 其中:  -   `<from>` 和 `<to>` 定义匹配值的范围（包括）。 如果忽略 `<to>`     ，则过滤器匹配 `<from> - <from>` 范围。 如果 `<from>`     也被省略，则过滤器匹配所有可能的值。 -   `<step>` 通过该范围定义数字值的跳过。默认情况下， `<step>`     的值为1，这意味着所有定义范围的值都匹配。  虽然过滤器定义是可选的，但必须至少使用一个过滤器。过滤器必须有一个范围或定义的*<step>*值。  如果没有定义低级过滤器，则一个空的filter既与“0”匹配，又匹配所有可能的值。例如，如果省略小时过滤器，仅当分钟和秒的过滤器也被省略则只有“0”小时将匹配，否则空的小时过滤器将匹配所有小时值。  它们各自的过滤器前缀的有效 `<from>` 和 `<to>` 值分别为：  |前缀   |描述|*<from>*  |*<to>*| |------------|---|----------------|--------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  `<from>` 值必须小于或等于 `<to>` 值。 `<step>` 值必须大于或等于1且小于或等于 `<to>` - `<from>`。  单个数字月份、小时、分钟和秒值可以前缀为0.例如 `md01-31` 和 `h/02` 是有效间隔，但 `md01-031` 和 `wd01-07` 无效。  在Zabbix管理前端，多个调度间隔以单独的行输入。在Zabbix API中，它们连接成单个字符串，以分号 `;` 作为分隔符。  如果时间匹配了几个间隔，则只执行一次。例如， `wd1h9;h9` 将在星期一上午9点执行一次。  示例:  |间隔                                        |执行方式| |-------------------------------------------------|-| |m0-59|每分钟执行一次| |h9-17/2|从9:00开始每2小时执行一次（9:00，11:00 ...）| |m0,30 or m/30|在每小时的hh:00 和 hh:30执行| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|每5分钟执行| |wd1-5h9|每周一至周五9:00| |wd1-5h9-18|每个星期一到星期五在9：00,10：00，...，18:00| |h9,10,11 or h9-11|每天上午9:00，10:00和11:00| |md1h9m30|每个月的第一天在9:30| |md1wd1h9m30|如果是星期一，每个月的第一天在9:30执行| |h9m/30|在9:00，9:30执行| |h9m0-59/30|在9:00，9:30执行| |h9,10m/30|在9:00，9:30，10:00，10:30执行| |h9-10m30|在9:30，10:30执行| |h9m10-40/30|在9:10，9:40执行| |h9,10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9-10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9m10-40|在9:10，9:11，9:12，... 9:40执行| |h9m10-40/1|在9:10，9:11，9:12，... 9:40执行| |h9-12,15|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0s30|在上午9时30分，上午10时30分，11时30分，12时30分，15时30分执行| |h9-12s30|在9:00:30，9:01:30，9:02:30 ... 12:58:30，12:59:30执行| |h9m/30;h10 (*指定API的语法*)|在每天 9:00, 9:30, 10:00执行| |h9m/30<br>h10（*在前端添加至另一行*）|在每天9:00，9:30，10:00执行|  

en-us	#### Scheduling intervals  Scheduling intervals are used to check items at specific times. While flexible intervals are designed to redefine the default item update interval, the scheduling intervals are used to specify an independent checking schedule, which is executed in parallel.  A scheduling interval is defined as: `md<filter>wd<filter>h<filter>m<filter>s<filter>` where:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` is used to specify values for its prefix (days, hours, minutes, seconds) and is defined as: `[<from>[-<to>]][/<step>][,<filter>]` where:  -   `<from>` and `<to>` define the range of matching values (included).     If `<to>` is omitted then the filter matches a `<from> - <from>`     range. If `<from>` is also omitted then the filter matches all     possible values. -   `<step>` defines the skips of the number value through the range. By     default `<step>` has the value of 1, which means that all values of     the defined range are matched.  While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the *<step>* value defined.  An empty filter matches either '0' if no lower-level filter is defined or all possible values otherwise. For example, if the hour filter is omitted then only '0' hour will match, provided minute and seconds filters are omitted too, otherwise an empty hour filter will match all hour values.  Valid `<from>` and `<to>` values for their respective filter prefix are:  |Prefix|Description|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  The `<from>` value must be less or equal to `<to>` value. The `<step>` value must be greater or equal to 1 and less or equal to `<to>` - `<from>`.  Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example `md01-31` and `h/02` are valid intervals, but `md01-031` and `wd01-07` are not.  In Zabbix frontend, multiple scheduling intervals are entered in separate rows. In Zabbix API, they are concatenated into a single string with a semicolon `;` as a separator.  If a time is matched by several intervals it is executed only once. For example, `wd1h9;h9` will be executed only once on Monday at 9am.  Examples:  |Interval|Will be executed| |--------|----------------| |m0-59|every minute| |h9-17/2|every 2 hours starting with 9:00 (9:00, 11:00 ...)| |m0,30 or m/30|hourly at hh:00 and hh:30| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|every five minutes| |wd1-5h9|every Monday till Friday at 9:00| |wd1-5h9-18|every Monday till Friday at 9:00,10:00,...,18:00| |h9,10,11 or h9-11|every day at 9:00, 10:00 and 11:00| |md1h9m30|every 1st day of each month at 9:30| |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday| |h9m/30|every day at 9:00, 9:30| |h9m0-59/30|every day at 9:00, 9:30| |h9,10m/30|every day at 9:00, 9:30, 10:00, 10:30| |h9-10m30|every day at 9:30, 10:30| |h9m10-40/30|every day at 9:10, 9:40| |h9,10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9-10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9m10-40|every day at 9:10, 9:11, 9:12, ... 9:40| |h9m10-40/1|every day at 9:10, 9:11, 9:12, ... 9:40| |h9-12,15|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0s30|every day at 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30| |h9-12s30|every day at 9:00:30, 9:01:30, 9:02:30 ... 12:58:30, 12:59:30| |h9m/30;h10 (*API-specific syntax*)|every day at 9:00, 9:30, 10:00| |h9m/30<br>h10 (*add this as another row in frontend*)|every day at 9:00, 9:30, 10:00|
zh-cn	#### 调度  调度用于在特定时间检查监控项。虽然默认的自定义时间间隔是灵活，但是调度常用于指定独立执行的检查计划。  调度定义为: `md<filter>wd<filter>h<filter>m<filter>s<filter>` 其中:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` 用于指定其前缀的值(日, 时, 分, 秒) 并被定义为:: `[<from>[-<to>]][/<step>][,<filter>]` 其中:  -   `<from>` 和`<to>` 定义匹配值的范围（包括）。     如果忽略 `<to>` 则过滤器匹配 `<from> - <from>`     范围。 如果 `<from>` 也被省略，则过滤器匹配所有可能的值。 -   `<step>` 通过该范围定义数字值的跳过。默认情况下，`<step>` 的值为1，这意味着所有定义范围的值都匹配。  <step> 通过该范围定义数字值的跳过。默认情况下， <step> 的值为1，这意味着所有定义范围的值都匹配。 虽然过滤器定义是可选的，但必须至少使用一个过滤器。过滤器必须有一个范围或定义的<step>值。  如果没有定义低级别过滤器，则一个空的filter既与“0”匹配，又匹配所有可能的值。例如，如果省略小时过滤器，仅当分钟和秒的过滤器也被省略则只有“0”小时将匹配，否则空的小时过滤器将匹配所有小时值。  过滤器前缀的有效 <from> 和 <to> 值分别为：  |前缀|描述|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  <from> 值必须小于或等于 <to> 值。<step> 值必须大于或等于1且小于或等于 <to> - <from>。  单个数字月份、小时、分钟和秒值可以前缀为0。例如 md01-31 和 h/02 是有效间隔，但 md01-031 和 wd01-07 无效。  在Zabbix前端，多个调度间隔以单独的行输入。在Zabbix API中，它们连接成单个字符串，以分号 ; 作为分隔符。  如果同一个时间匹配了几个间隔，则只执行一次。例如， wd1h9;h9 将在星期一上午9点执行一次。  示例:  |间隔|描述| |--------|----------------| |m0-59|每分钟执行一次| |h9-17/2|从9:00开始每2小时执行一次（9:00，11:00 ...）| |m0,30 or m/30|在每小时的hh:00 和 hh:30执行| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|每5分钟执行| |wd1-5h9|每周一至周五9:00| |wd1-5h9-18|每个星期一到星期五在9：00,10：00，...，18:00| |h9,10,11 or h9-11|每天上午9:00，10:00和11:00| |md1h9m30|每个月的第一天在9:30| |md1wd1h9m30|如果是星期一，每个月的第一天在9:30执行| |h9m/30|在9:00，9:30执行| |h9m0-59/30|在9:00，9:30执行| |h9,10m/30|在9:00，9:30，10:00，10:30执行| |h9-10m30|在9:30，10:30执行| |h9m10-40/30|在9:10，9:40执行| |h9,10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9-10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9m10-40|在9:10，9:11，9:12，... 9:40执行| |h9m10-40/1|在9:10，9:11，9:12，... 9:40执行| |h9-12,15|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0s30|在上午9时30分，上午10时30分，11时30分，12时30分，15时30分执行| |h9-12s30|在9:00:30，9:01:30，9:02:30 ... 12:58:30，12:59:30执行| |h9m/30;h10 (*API-指定语法*)|在9:00，9:30，10:00执行| |h9m/30<br>h10 (*在前端的另一行添加*)|在9:00，9:30，10:00执行|

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

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

en-us	# script.execute
zh-cn	# 执行

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

en-us	# script.getscriptsbyhosts
zh-cn	# 通过主机获取脚本

en-us	# > Script object  The following objects are directly related to the `script` API.
zh-cn	# > 脚本对象  以下对象与 `脚本` API直接相关。

en-us	#### Scripts  Configure and execute scripts to help you with your daily tasks.  [Script API](/manual/api/reference/script)
zh-cn	#### 脚本  配置和执行脚本以帮助您完成日常任务。  [Script API](/manual/api/reference/script)

en-us	### Script  The script object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |scriptid|string|*(readonly)* ID of the script.| |**name**<br>(required)|string|Name of the script.| |**type**<br>(required)|integer|Script type.<br><br>Possible values:<br>0 - Script;<br>1 - IPMI;<br>2 - SSH;<br>3 - Telnet;<br>5 - *(default)* Webhook.| |**command**<br>(required)|string|Command to run.| |scope|integer|Script scope.<br><br>Possible values:<br>1 - *default* action operation;<br>2 - manual host action;<br>4 - manual event action.| |execute\_on|integer|Where to run the script.<br>Used if `type` is `0` (script).<br><br>Possible values:<br>0 - run on Zabbix agent;<br>1 - run on Zabbix server;<br>2 - *(default)* run on Zabbix server (proxy).| |menu\_path|string|Folders separated by slash that form a menu like navigation in frontend when clicked on host or event.<br>Used if `scope` is `2` or `4`.| |authtype|integer|Authentication method used for SSH script type.<br>Used if `type` is `2`.<br><br>Possible values:<br>0 - password;<br>1 - public key.| |username|string|User name used for authentication.<br>Required if `type` is `2` or `3`.| |password|string|Password used for SSH scripts with password authentication and Telnet scripts.<br>Used if `type` is `2` and `authtype` is `0` or `type` is `3`.| |publickey|string|Name of the public key file used for SSH scripts with public key authentication.<br>Required if type is `2` and `authtype` is `1`.| |privatekey|string|Name of the private key file used for SSH scripts with public key authentication.<br>Required if type is `2` and `authtype` is `1`.| |port|string|Port number used for SSH and Telnet scripts.<br>Used if type is `2` or `3`.| |groupid|string|ID of the host group that the script can be run on. If set to 0, the script will be available on all host groups.<br><br>Default: 0.| |usrgrpid|string|ID of the user group that will be allowed to run the script. If set to 0, the script will be available for all user groups.<br>Used if `scope` is `2` or `4`.<br><br>Default: 0.| |host\_access|integer|Host permissions needed to run the script.<br>Used if `scope` is `2` or `4`.<br><br>Possible values:<br>2 - *(default)* read;<br>3 - write.| |confirmation|string|Confirmation pop up text. The pop up will appear when trying to run the script from the Zabbix frontend.<br>Used if `scope` is `2` or `4`.| |timeout|string|Webhook script execution timeout in seconds. Time suffixes are supported, e.g. 30s, 1m.<br>Required if `type` is `5`.<br><br>Possible values:<br>1-60s<br><br>Default value:<br>30s| |parameters|array|Array of [webhook input parameters](/manual/api/reference/script/object#Webhook parameters).<br>Used if `type` is `5`.| |description|string|Description of the script.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 脚本  脚本对象有以下参数。  |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |scriptid|string|*(只读)* 脚本ID。| |**name**<br>(必需)|string|脚本名称。| |**type**<br>(必需)|integer|脚本类型。<br><br>可能的值：<br>0 - 脚本；<br>1 - IPMI；<br>2 - SSH；<br>3 - Telnet；<br>5 - *(默认)* Webhook。| |**command**<br>(必需)|string|运行的命令。| |scope|integer|脚本范围。<br><br>可能的值：<br>1 - *默认* 动作操作；<br>2 - 手动主机动作；<br>4 - 手动事件动作。| |execute\_on|integer|在哪里运行脚本。<br>当 `type` 为 `0`时使用 （脚本）。<br><br>可能的值：<br>0 - 在 Zabbix agent上运行；<br>1 - 在 Zabbix server上运行;<br>2 - *(默认)* 在 Zabbix server (proxy)上运行。| |menu\_path|string|当点击主机或事件时，由斜杠分隔的文件夹所组成的类似于前端导航的菜单。<br>当 `scope` 为 `2` 或 `4`时使用。| |authtype|integer|SSH脚本类型使用的身份验证方法。<br>当 `type` 为 `2`时使用。<br><br>可能的值：<br>0 - 密码；<br>1 - 公钥。| |username|string|身份验证使用的用户名<br>当 `type` 为 `2` 或 `3`时需要。| |password|string|通过密码进行身份验证的SSH脚本和Telnet脚本使用的密码。<br>当`type` 为 `2` 且 `authtype` 为 `0` 或 `type` 为 `3`时使用。| |publickey|string|通过公钥进行身份验证的SSH脚本使用的公钥文件名。<br>当`type` 为 `2` 且 `authtype` 为 `1`时需要。| |privatekey|string|通过公钥进行身份验证的SSH脚本使用的私钥文件名。<br>当`type` 为 `2` 且 `authtype` 为 `1`时需要。| |port|string|SSH 和 Telnet 脚本使用的端口号。<br>当`type` 为 `2` 或 `3`时使用。| |groupid|string|可以运行脚本的主机群组ID。如果设置为 0， 脚本将可以在所有主机群组运行。<br><br>默认值： 0。| |usrgrpid|string|允许运行脚本的用户群组ID。如果设置为 0, 脚本将可以在所有用户群组运行。<br>当`scope` 为 `2` 或 `4`时使用。<br><br>默认值: 0.| |host\_access|integer|运行脚本所需的主机权限。<br>当`scope`为 `2` 或 `4`时使用。<br><br>可能的值：<br>2 - *(默认)* 读;<br>3 - 写.| |confirmation|string|弹出窗口的确认文本。如果尝试在zabbix前端运行脚本，将会弹出窗口。<br>当`scope` 为 `2` 或 `4`时使用。| |timeout|string|Webhook脚本执行超时秒数。 支持时间后缀, 例如 30s，1m。<br>当`type` 为 `5`时需要。<br><br>可能的值：<br>1-60s<br><br>默认值：<br>30s| |parameters|array|[webhook入参数组](/manual/api/reference/script/object#Webhook parameters).<br>当`type` 为 `5`时使用。| |description|string|脚本描述。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Script  This class is designed to work with scripts.  Object references:\  -   [Script](/manual/api/reference/script/object#script) -   [Webhook     parameters](/manual/api/reference/script/object#webhook_parameters) -   [Debug](/manual/api/reference/script/object#debug) -   [Log entry](/manual/api/reference/script/object#log_entry)  Available methods:\  -   [script.create](/manual/api/reference/script/create) - create new     scripts -   [script.delete](/manual/api/reference/script/delete) - delete     scripts -   [script.execute](/manual/api/reference/script/execute) - run scripts -   [script.get](/manual/api/reference/script/get) - retrieve scripts -   [script.getscriptsbyhosts](/manual/api/reference/script/getscriptsbyhosts) -     retrieve scripts for hosts -   [script.update](/manual/api/reference/script/update) - update     scripts
zh-cn	 # 脚本  此类为使用脚本而设计。 参考对象:\  -   [脚本](/manual/api/reference/script/object#脚本) -   [Webhook参数](/manual/api/reference/script/object#Webhook_参数) -   [调试](/manual/api/reference/script/object#调试) -   [日志条目](/manual/api/reference/script/object#日志_条目)  可用方法:\  -   [script.create](/manual/api/reference/script/create) - 创建新脚本 -   [script.delete](/manual/api/reference/script/delete) - 删除脚本 -   [script.execute](/manual/api/reference/script/execute) - 运行脚本 -   [script.get](/manual/api/reference/script/get) - 检索脚本 -   [script.getscriptsbyhosts](/manual/api/reference/script/getscriptsbyhosts) -     通过主机检索脚本 -   [script.update](/manual/api/reference/script/update) - 更新脚本

en-us	#### Script timeout
zh-cn	#### 脚本超时

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

en-us	#### Searchable attributes  Hosts can be searched by the following properties:  -   Host name -   Visible name -   IP address -   DNS name  Host groups can be searched by name. Specifying a parent host group implicitly selects all nested host groups.  Templates can be searched by name or visible name. If you search by a name that is different from the visible name (of a template/host), in the search results it is displayed below the visible name in parentheses.
zh-cn	#### 可搜索的属性  可以通过以下属性搜索主机：  - 主机名 - 可见的名字 - IP地址 - DNS 名称  可以按名称搜索主机组。指定父主机组会隐式选择所有嵌套主机组。  可以按名称或可见名称搜索模板。如果您按与（模板/主机的）可见名称不同的名称进行搜索，则在搜索结果中，它会显示在括号中可见名称的下方。

en-us	#### Searching by host inventory data  Retrieve hosts that contain "Linux" in the host inventory "OS" field.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": [             "host"         ],         "selectInventory": [             "os"         ],         "searchInventory": {             "os": "Linux"         }     },     "id": 2,     "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10084",             "host": "Zabbix server",             "inventory": {                 "os": "Linux Ubuntu"             }         },         {             "hostid": "10107",             "host": "Linux server",             "inventory": {                 "os": "Linux Mint"             }         }     ],     "id": 1 } ```
zh-cn	#### 按主机资产数据进行搜索  检索主机资产“OS”字段中包含“Linux”的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": [             "host"         ],         "selectInventory": [             "os"         ],         "searchInventory": {             "os": "Linux"         }     },     "id": 2,     "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10084",             "host": "Zabbix server",             "inventory": {                 "os": "Linux Ubuntu"             }         },         {             "hostid": "10107",             "host": "Linux server",             "inventory": {                 "os": "Linux Mint"             }         }     ],     "id": 1 } ```

en-us	#### Searching by host inventory data  Retrieve hosts that contain "Linux" in the host inventory "OS" field.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": [             "host"         ],         "selectInventory": [             "os"         ],         "searchInventory": {             "os": "Linux"         }     },     "id": 2,     "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10084",             "host": "Zabbix server",             "inventory": {                 "os": "Linux Ubuntu"             }         },         {             "hostid": "10107",             "host": "Linux server",             "inventory": {                 "os": "Linux Mint"             }         }     ],     "id": 1 } ```
zh-cn	#### 按主机资产数据进行搜索  检索主机资产“OS”字段中包含“Linux”的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": [             "host"         ],         "selectInventory": [             "os"         ],         "searchInventory": {             "os": "Linux"         }     },     "id": 2,     "auth": "7f9e00124c75e8f25facd5c093f3e9a0" } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10084",             "host": "Zabbix server",             "inventory": {                 "os": "Linux Ubuntu"             }         },         {             "hostid": "10107",             "host": "Linux server",             "inventory": {                 "os": "Linux Mint"             }         }     ],     "id": 1 } ```

en-us	#### Searching by host tags  Retrieve hosts that have tag "Host name" equal to "Linux server".  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "Linux server",                 "operator": 1             }         ]     },     "auth": "7f9e00124c75e8f25facd5c093f3e9a0",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10085",             "tags": [                 {                     "tag": "Host name",                     "value": "Linux server"                 },                 {                     "tag": "OS",                     "value": "RHEL 7"                 }             ]         }     ],     "id": 1 } ```  Retrieve hosts that have these tags not only on host level but also in their linked parent templates.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "tags": [{"tag": "A", "value": "1", "operator": "0"}],         "inheritedTags": true     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10623",             "name": "PC room 1"         },         {             "hostid": "10601",             "name": "Office"         }     ],     "id": 1 } ```
zh-cn	 #### 按主机标记搜索  检索标记为“主机名”等于“Linux服务器”的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "Linux server",                 "operator": 1             }         ]     },     "auth": "7f9e00124c75e8f25facd5c093f3e9a0",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10085",             "tags": [                 {                     "tag": "Host name",                     "value": "Linux server"                 },                 {                     "tag": "OS",                     "value": "RHEL 7"                 }             ]         }     ],     "id": 1 } ```  检索不仅在主机级而且在其链接的父模板中具有这些标记的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "tags": [{"tag": "A", "value": "1", "operator": "0"}],         "inheritedTags": true     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10623",             "name": "PC room 1"         },         {             "hostid": "10601",             "name": "Office"         }     ],     "id": 1 } ```

en-us	#### Searching by host tags  Retrieve hosts that have tag "Host name" equal to "Linux server".  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "Linux server",                 "operator": 1             }         ]     },     "auth": "7f9e00124c75e8f25facd5c093f3e9a0",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10085",             "tags": [                 {                     "tag": "Host name",                     "value": "Linux server"                 },                 {                     "tag": "OS",                     "value": "RHEL 7"                 }             ]         }     ],     "id": 1 } ```  Retrieve hosts that have these tags not only on host level but also in their linked parent templates.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "tags": [{"tag": "A", "value": "1", "operator": "0"}],         "inheritedTags": true     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10623",             "name": "PC room 1"         },         {             "hostid": "10601",             "name": "Office"         }     ],     "id": 1 } ```
zh-cn	 #### 按主机标记搜索  检索标记为“主机名”等于“Linux服务器”的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "Linux server",                 "operator": 1             }         ]     },     "auth": "7f9e00124c75e8f25facd5c093f3e9a0",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10085",             "tags": [                 {                     "tag": "Host name",                     "value": "Linux server"                 },                 {                     "tag": "OS",                     "value": "RHEL 7"                 }             ]         }     ],     "id": 1 } ```  检索不仅在主机级而且在其链接的父模板中具有这些标记的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "tags": [{"tag": "A", "value": "1", "operator": "0"}],         "inheritedTags": true     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10623",             "name": "PC room 1"         },         {             "hostid": "10601",             "name": "Office"         }     ],     "id": 1 } ```

en-us	#### Searching by template tags  Retrieve templates that have tag "Host name" equal to "{HOST.NAME}".  Request:  ```json {     "jsonrpc": "2.0",     "method": "template.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "{HOST.NAME}",                 "operator": 1             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10402",             "tags": [                 {                     "tag": "Host name",                     "value": "{HOST.NAME}"                 }             ]         }     ],     "id": 1 } ```
zh-cn	#### 按模板标签搜索  检索标签“主机名称”等于“{HOST.NAME}”的模板。  请求:  ```json {     "jsonrpc": "2.0",     "method": "template.get",     "params": {         "output": ["hostid"],         "selectTags": "extend",         "evaltype": 0,         "tags": [             {                 "tag": "Host name",                 "value": "{HOST.NAME}",                 "operator": 1             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10402",             "tags": [                 {                     "tag": "Host name",                     "value": "{HOST.NAME}"                 }             ]         }     ],     "id": 1 } ```

en-us	#### Searching for hosts using wildcards  Find hosts whose name contains word "server" and have interface ports "10050" or "10071". Sort the result by host name in descending order and limit it to 5 hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid", "host"],         "selectInterfaces": ["port"],         "filter": {             "port": ["10050", "10071"]         },         "search": {             "host": "*server*"         },         "searchWildcardsEnabled": true,         "searchByAny": true,         "sortfield": "host",         "sortorder": "DESC",         "limit": 5     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "50003",             "host": "WebServer-Tomcat02",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "50005",             "host": "WebServer-Tomcat01",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "50004",             "host": "WebServer-Nginx",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "99032",             "host": "MySQL server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         },         {             "hostid": "99061",             "host": "Linux server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         }     ],     "id": 1 } ```
zh-cn	#### 使用通配符搜索主机  查找名称中包含单词“server”，并且接口端口是“10050”或“10071”的主机。结果按照主机名称倒序排序，并且限制返回5台主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid", "host"],         "selectInterfaces": ["port"],         "filter": {             "port": ["10050", "10071"]         },         "search": {             "host": "*server*"         },         "searchWildcardsEnabled": true,         "searchByAny": true,         "sortfield": "host",         "sortorder": "DESC",         "limit": 5     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "50003",             "host": "WebServer-Tomcat02",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "50005",             "host": "WebServer-Tomcat01",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "50004",             "host": "WebServer-Nginx",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         {             "hostid": "99032",             "host": "MySQL server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         },         {             "hostid": "99061",             "host": "Linux server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         }     ],     "id": 1 } ```

en-us	#### Searching for hosts using wildcards with "preservekeys"  If you add the parameter "preservekeys" to the previous request, the result is returned as an associative array, where the keys are the id of the objects.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid", "host"],         "selectInterfaces": ["port"],         "filter": {             "port": ["10050", "10071"]         },         "search": {             "host": "*server*"         },         "searchWildcardsEnabled": true,         "searchByAny": true,         "sortfield": "host",         "sortorder": "DESC",         "limit": 5,         "preservekeys": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "50003": {             "hostid": "50003",             "host": "WebServer-Tomcat02",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         "50005": {             "hostid": "50005",             "host": "WebServer-Tomcat01",             "interfaces": [                 {                     "port": "10071"                 }             ]         },                 "50004": {             "hostid": "50004",             "host": "WebServer-Nginx",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         "99032": {             "hostid": "99032",             "host": "MySQL server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         },         "99061": {             "hostid": "99061",             "host": "Linux server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         }     },     "id": 1 } ```
zh-cn	#### 加上 "preservekeys"参数使用通配符搜索主机  如果将参数“preservekeys”添加到上一个请求中，结果会返回一个关联数组，键是对象的id。  请求：  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["hostid", "host"],         "selectInterfaces": ["port"],         "filter": {             "port": ["10050", "10071"]         },         "search": {             "host": "*server*"         },         "searchWildcardsEnabled": true,         "searchByAny": true,         "sortfield": "host",         "sortorder": "DESC",         "limit": 5,         "preservekeys": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "50003": {             "hostid": "50003",             "host": "WebServer-Tomcat02",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         "50005": {             "hostid": "50005",             "host": "WebServer-Tomcat01",             "interfaces": [                 {                     "port": "10071"                 }             ]         },                 "50004": {             "hostid": "50004",             "host": "WebServer-Nginx",             "interfaces": [                 {                     "port": "10071"                 }             ]         },         "99032": {             "hostid": "99032",             "host": "MySQL server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         },         "99061": {             "hostid": "99061",             "host": "Linux server 01",             "interfaces": [                 {                     "port": "10050"                 }             ]         }     },     "id": 1 } ```

en-us	#### Searching hosts by problem severity  Retrieve hosts that have "Disaster" problems.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10160",             "name": "Zabbix server"         }     ],     "id": 1 } ```  Retrieve hosts that have "Average" and "High" problems.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": [3, 4]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "20170",             "name": "Database"         },         {             "hostid": "20183",             "name": "workstation"         }     ],     "id": 1 } ```
zh-cn	 #### 根据问题严重程度搜索主机  检索有“灾难”问题的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10160",             "name": "Zabbix server"         }     ],     "id": 1 } ```  检索具有“一般严重”和“严重”问题的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": [3, 4]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "20170",             "name": "Database"         },         {             "hostid": "20183",             "name": "workstation"         }     ],     "id": 1 } ```

en-us	#### Searching hosts by problem severity  Retrieve hosts that have "Disaster" problems.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10160",             "name": "Zabbix server"         }     ],     "id": 1 } ```  Retrieve hosts that have "Average" and "High" problems.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": [3, 4]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "20170",             "name": "Database"         },         {             "hostid": "20183",             "name": "workstation"         }     ],     "id": 1 } ```
zh-cn	 #### 根据问题严重程度搜索主机  检索有“灾难”问题的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": 5     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10160",             "name": "Zabbix server"         }     ],     "id": 1 } ```  检索具有“一般严重”和“严重”问题的主机。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "severities": [3, 4]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "20170",             "name": "Database"         },         {             "hostid": "20183",             "name": "workstation"         }     ],     "id": 1 } ```

en-us	#### Searching host with tags and template tags  Retrieve a host with tags and all tags that are linked to parent templates.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "hostids": 10502,         "selectTags": ["tag", "value"],         "selectInheritedTags": ["tag", "value"]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10502",             "name": "Desktop",             "tags": [                 {                     "tag": "A",                     "value": "1"                 }             ],             "inheritedTags": [                 {                     "tag": "B",                     "value": "2"                 }             ]         }     ],     "id": 1 } ```
zh-cn	 #### 搜索主机标签和模板标签  检索带有标记的主机以及链接到父模板的所有标记。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "hostids": 10502,         "selectTags": ["tag", "value"],         "selectInheritedTags": ["tag", "value"]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10502",             "name": "Desktop",             "tags": [                 {                     "tag": "A",                     "value": "1"                 }             ],             "inheritedTags": [                 {                     "tag": "B",                     "value": "2"                 }             ]         }     ],     "id": 1 } ```

en-us	#### Searching host with tags and template tags  Retrieve a host with tags and all tags that are linked to parent templates.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "hostids": 10502,         "selectTags": ["tag", "value"],         "selectInheritedTags": ["tag", "value"]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10502",             "name": "Desktop",             "tags": [                 {                     "tag": "A",                     "value": "1"                 }             ],             "inheritedTags": [                 {                     "tag": "B",                     "value": "2"                 }             ]         }     ],     "id": 1 } ```
zh-cn	 #### 搜索主机标签和模板标签  检索带有标记的主机以及链接到父模板的所有标记。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "output": ["name"],         "hostids": 10502,         "selectTags": ["tag", "value"],         "selectInheritedTags": ["tag", "value"]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": [         {             "hostid": "10502",             "name": "Desktop",             "tags": [                 {                     "tag": "A",                     "value": "1"                 }             ],             "inheritedTags": [                 {                     "tag": "B",                     "value": "2"                 }             ]         }     ],     "id": 1 } ```

en-us	#### Search results  Search results consist of three separate blocks for hosts, host groups and templates.  ![](../../../assets/en/manual/web_interface/global_search_results.png){width="600"}  It is possible to collapse/expand each individual block. The entry count is displayed at the bottom of each block, for example, *Displaying 13 of 13 found*. Total entries displayed within one block are limited to 100.  Each entry provides links to monitoring and configuration data. See the [full list](/manual/web_interface/global_search#links_available) of links.  For all configuration data (such as items, triggers, graphs) the amount of entities found is displayed by a number next to the entity name, in gray. **Note** that if there are zero entities, no number is displayed.  Enabled hosts are displayed in blue, disabled hosts in red.
zh-cn	#### 搜索结果  搜索结果由主机、主机组和模板的三个独立块组成。  ![](../../../assets/en/manual/web_interface/global_search_results.png){width="600"}  可以折叠/展开每个单独的区域。条目计数显示在底部，例如，*Displaying 13 of 13 found*。一个区域内显示的总条目数限制为 100 个。  每个条目都提供了指向监控和配置数据的链接。请参阅链接的 [完整列表](/manual/web_interface/global_search#links_available)。  对于所有配置数据（例如监控项、触发器、图表），找到的实体数量由实体名称旁边的灰色数字显示。 **注意**，如果有零个实体，则不显示数字。  启用的主机显示为蓝色，禁用的主机显示为红色。

en-us	#### Sections  [Introduction](about) provides general information about current Zabbix software. Reading this section should equip you with some good reasons to choose Zabbix.  [Zabbix concepts](/manual/definitions) explain the terminology used in Zabbix and provides details on Zabbix components.  [Installation](/manual/installation/getting_zabbix) and [Quickstart](/manual/quickstart/item) sections should help you to get started with Zabbix. [Zabbix appliance](/manual/appliance) is an alternative for getting a quick taster of what it is like to use Zabbix.  [Configuration](/manual/config) is one of the largest and more important sections in this manual. It contains loads of essential advice about how to set up Zabbix to monitor your environment, from setting up hosts to getting essential data to viewing data to configuring notifications and remote commands to be executed in case of problems.  [IT services](/manual/it_services) section details how to use Zabbix for a high-level overview of your monitoring environment.  [Web monitoring](/manual/web_monitoring) should help you learn how to monitor the availability of web sites.  [Virtual machine monitoring](/manual/vm_monitoring) presents a how-to for configuring VMware environment monitoring.  [Maintenance](/manual/maintenance), [Regular expressions](/manual/regular_expressions), [Event acknowledgment](/manual/acknowledges) and [XML export/import](/manual/xml_export_import) are further sections that reveal how to use these various aspects of Zabbix software.  [Discovery](/manual/discovery) contains instructions for setting up automatic discovery of network devices, active agents, file systems, network interfaces, etc.  [Distributed monitoring](/manual/distributed_monitoring) deals with the possibilities of using Zabbix in larger and more complex environments.  [Encryption](/manual/encryption) helps explaining the possibilities of encrypting communications between Zabbix components.  [Web interface](/manual/web_interface) contains information specific for using the web interface of Zabbix.  [API](/manual/api) section presents details of working with Zabbix API.  Detailed lists of technical information are included in [Appendixes](/manual/appendix). This is where you will also find a FAQ section.
zh-cn	#### 章节  [简介](about) 提供有关当前 Zabbix 软件的一般信息。阅读本节应该为您提供选择 Zabbix 的一些充分理由。  [Zabbix 概念](/manual/definitions) 解释了 Zabbix 中使用的术语，并提供了 Zabbix 组件的详细信息。  [安装](/manual/installation/getting_zabbix) 和 [快速入门](/manual/quickstart/item) 部分应该可以帮助您开始使用 Zabbix。  [Zabbix 应用](/manual/appliance) 是一种快速体验 Zabbix 使用的替代方案。  [配置](/manual/config) 是本手册中最大和最重要的部分之一。它包含大量关于如何设置 Zabbix 以监控你的环境的基本建议，从设置主机到获取基本数据到查看数据到配置通知和远程命令以在出现问题时执行。  [IT 服务](/manual/it_services) 部分详细介绍了如何使用 Zabbix 对监控环境进行高级概述。  [Web 监控](/manual/web_monitoring) 可以帮助您了解如何监控网站的可用性。  [虚拟机监控](/manual/vm_monitoring) 提供了配置 VMware 环境监控的方法。  [维护](/manual/maintenance) ，[正则表达式](/manual/regular_expressions)，[事件确认](/manual/acknowledges) 和 [XML 导入/导出](/manual/xml_export_import) 部分进一步说明如何使用 Zabbix 软件的各个方面。  [发现](/manual/discovery) 包含有关设置网络设备、主动模式的 agent（自动注册）、文件系统、网络接口等的自动发现的说明。  [分布式监控](/manual/distributed_monitoring) 介绍在更大、更复杂的环境中使用 Zabbix 的可能性。  [加密](/manual/encryption) 帮助解释加密 Zabbix 组件之间的通信的可行性。  [Web 界面](/manual/web_interface) 包含特定的使用 Zabbix 的 Web 界面的信息。  [API](/manual/api) 部分介绍了使用 Zabbix API 的详细信息。  可以通过 [附录](/manual/appendix) 查看更详细的记述信息。还可以在此处找到常见问题解答部分。

en-us	#### Secure user for Zabbix agent  In the default configuration, Zabbix server and Zabbix agent processes share one 'zabbix' user. If you wish to make sure that the agent cannot access sensitive details in server configuration (e.g. database login information), the agent should be run as a different user:  1.  Create a secure user 2.  Specify this user in the agent [configuration     file](/manual/appendix/config/zabbix_agentd) ('User' parameter) 3.  Restart the agent with administrator privileges. Privileges will be     dropped to the specified user.
zh-cn	#### Zabbix agent 的安全用户  在默认配置中，Zabbix server 和 Zabbix agent 进程共享一个“zabbix”用户。若希望确保 Zabbix agent 无法访问 Zabbix server配置中的敏感信息（例：数据库登录信息），则应以不同的用户身份运行Zabbix agent：  1.  创建一个安全用户；`` 2.  在 Zabbix agent 的  [configuration file](/manual/appendix/config/zabbix_agentd) 中指定此用户（修改 'User' 参数）； 3.  以管理员权限的用户重启 Zabbix agent。此后权限将赋予给先前指定的用户。

en-us	##### Security  |Parameter|Description| |---------|-----------| |*Validate URI schemes*|Uncheck the box to disable URI scheme validation against the whitelist defined in *Valid URI schemes*. (enabled by default).| |*Valid URI schemes*|A comma-separated list of allowed URI schemes. Applies to all fields in the frontend where URIs are used (for example, map element URLs).<br>this field is editable only if *Validate URI schemes* is selected.| |*X-Frame-Options HTTP header*|Value of HTTP X-Frame-options header. Supported values:<br>**SAMEORIGIN** (default) - the page can only be displayed in a frame on the same origin as the page itself.<br>**DENY** - the page cannot be displayed in a frame, regardless of the site attempting to do so.<br>**null** - disable X-Frame-options header (not recommended).<br>Or a list (string) of comma-separated hostnames. If a listed hostname is not among allowed, the SAMEORIGIN option is used.| |*Use iframe sandboxing*|This parameter determines whether retrieved URL content should be put into the sandbox or not. Note, that turning off sandboxing is not recommended.| |*Iframe sandboxing exceptions*|If sandboxing is enabled and this field is empty, all sandbox attribute restrictions apply. To disable some of the restrictions, specified them in this field. This disables only restrictions listed here, other restrictions will still be applied. See [sandbox attribute](https://www.w3.org/TR/2010/WD-html5-20100624/the-iframe-element.html#attr-iframe-sandbox) description for additional information.|
zh-cn	##### 安全  |参数|说明| |---------|------------| |*验证 URI 方案*|取消选中该框以禁用针对*有效 URI 方案*中定义的白名单的 URI 方案验证。 （默认启用）。| |*有效的 URI 方案*|允许的 URI 方案的逗号分隔列表。适用于前端中的所有字段，其中使用URI（例如，映射元素URL）。<br>此字段仅在选择*验证URI方案*时才可编辑。| |*X-Frame-Options HTTP 标头*|HTTP X-Frame-options 标头的值。支持的值：<br>**SAMEORIGIN**（默认）- 页面只能显示在与页面本身同源的框架中。<br>**DENY** - 页面不能显示在框架中，无论站点是否尝试这样做。<br>**null** - 禁用 X-Frame-options 标头（不推荐）。<br>或逗号分隔的主机名列表（字符串）。如果不允许列出的主机名，则使用 SAMEORIGIN 选项。 |*使用 iframe 沙箱*|此参数决定是否将检索到的 URL 内容放入沙箱。请注意，不建议关闭沙盒。 |*Iframe 沙盒例外*|如果启用沙盒并且此字段为空，则适用所有沙盒属性限制。要禁用某些限制，请在此字段中指定它们。这只会禁用此处列出的限制，其他限制仍将适用。有关更多信息，请参阅 [沙盒属性](https://www.w3.org/TR/2010/WD-html5-20100624/the-if​​rame-element.html#attr-iframe-sandbox) 描述。|

en-us	### See also  1.  [Additional details about memory calculation in different     OS](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size)
zh-cn	### 参见  1.[关于不同操作系统内存计算的详细信息](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size)

en-us	### See also  1.  [Differences in the Zabbix agent configuration for active and     passive checks starting from version     2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858).
zh-cn	#### 参阅  1.  [Zabbix agent 主动和被动检查从2.0.0版本后配置对比详解](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858)

en-us	### See also  1.  [Differences in the Zabbix agent configuration for active and     passive checks starting from version     2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858).  
zh-cn	#### 参阅  1.  [Zabbix agent 主动和被动检查从2.0.0版本后配置对比详解](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858)

en-us	#### See also  1.  [Differences in the Zabbix agent configuration for active and     passive checks starting from version     2.0.0](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858)
zh-cn	#### 参阅  1.  [自2.0.0版本开始，Zabbix agent 主动和被动检查的配置差异](http://blog.zabbix.com/multiple-servers-for-active-agent-sure/858)

en-us	### See also  1.  [How to configure optimal count of zabbix     processes](http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457)
zh-cn	### 另请参阅  1.  [如何配置zabbix进程的最佳数量](http://blog.zabbix.com/monitoring-how-busy-zabbix-processes-are/457)

en-us	### See also  1.  [How to configure shared memory for Zabbix     daemons](http://www.zabbix.org/wiki/How_to/configure_shared_memory)
zh-cn	 ### 另见  1.  [如何为Zabbix守护进程配置共享内存](http://www.zabbix.org/wiki/How_to/configure_shared_memory)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
zh-cn	### 参见  -   [动作过滤](object#动作过滤) -   [动作操作](object#动作操作)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
zh-cn	### 参见  -   [动作过滤](object#动作过滤) -   [动作操作](object#动作操作)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
zh-cn	### 参见  -   [动作过滤](object#动作过滤) -   [动作操作](object#动作操作)

en-us	### See also  -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)
zh-cn	### 参见  -   [告警](/manual/api/reference/alert/object) -   [监控项](/manual/api/reference/item/object) -   [主机](/manual/api/reference/host/object) -   [LLD规则](/manual/api/reference/discoveryrule/object#lld_rule) -   [触发器](/manual/api/reference/trigger/object)

en-us	### See also  -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)
zh-cn	### 参见  -   [告警](/manual/api/reference/alert/object) -   [监控项](/manual/api/reference/item/object) -   [主机](/manual/api/reference/host/object) -   [自动发现规则](/manual/api/reference/discoveryrule/object#lld规则) -   [触发器](/manual/api/reference/trigger/object)

en-us	### See also  -   [Audit log object](/manual/api/reference/auditlog/object)
zh-cn	### 参见  -   [审计日志对象](/manual/api/reference/auditlog/object)

en-us	### See also  -   [Authentication](/manual/api/reference/authentication)
zh-cn	### 参考  -   [认证](/manual/api/reference/authentication)

en-us	### See also  -   [Authentication](/manual/api/reference/authentication) -   [Media](/manual/api/reference/user/object#media) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)
zh-cn	### 参考  -   [认证](/manual/api/reference/authentication) -   [媒介](/manual/api/reference/user/object#media) -   [用户组](/manual/api/reference/usergroup/object#user_group) -   [角色](/manual/api/reference/role/object#role)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovered host](/manual/api/reference/dhost/object#发现主机) -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check) -   [Host](/manual/api/reference/host/object#host)
zh-cn	 ### 参见  -   [Discovered     host](/manual/api/reference/dhost/object#发现主机) -   [Discovery     check](/manual/api/reference/dcheck/object#发现检查) -   [Host](/manual/api/reference/host/object#主机)

en-us	### See also  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service) -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)
zh-cn	### 参见  -   [发现服务](/manual/api/reference/dservice/object#discovered_service) -   [发现规则](/manual/api/reference/drule/object#discovery_rule)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovery     rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Graph item](/manual/api/reference/graphitem/object#graph_item) -   [Item](/manual/api/reference/item/object#item) -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template)
zh-cn	 ### 另见  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [图表监控项](/manual/api/reference/graphitem/object#graph_item) -   [监控项](/manual/api/reference/item/object#item) -   [主机](/manual/api/reference/host/object#host) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#template)

en-us	### See also  -   [Discovery     rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Graph item](/manual/api/reference/graphitem/object#graph_item) -   [Item](/manual/api/reference/item/object#item) -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template)
zh-cn	 ### 另见  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [图表监控项](/manual/api/reference/graphitem/object#图表监控项) -   [监控项](/manual/api/reference/item/object#监控项) -   [主机](/manual/api/reference/host/object#主机) -   [主机组](/manual/api/reference/hostgroup/object#主机组) -   [模板](/manual/api/reference/template/object#模板)

en-us	### See also  -   [Discovery rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Graph](/manual/api/reference/graph/object#graph) -   [Host](/manual/api/reference/host/object#host) -   [Host interface](/manual/api/reference/hostinterface/object#host_interface) -   [Trigger](/manual/api/reference/trigger/object#trigger)
zh-cn	### 另请参阅  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [图表](/manual/api/reference/graph/object#graph) -   [主机](/manual/api/reference/host/object#host) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface) -   [触发器](/manual/api/reference/trigger/object#trigger)

en-us	### See also  -   [Discovery     rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Graph](/manual/api/reference/graph/object#graph) -   [Host](/manual/api/reference/host/object#host) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface) -   [Trigger](/manual/api/reference/trigger/object#trigger)
zh-cn	### 另请参阅  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [图表](/manual/api/reference/graph/object#graph) -   [主机](/manual/api/reference/host/object#host) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface) -   [触发器](/manual/api/reference/trigger/object#trigger)

en-us	### See also  -   [Discovery     rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Item](/manual/api/reference/item/object#item) -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group)
zh-cn	### 另见  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [监控项](/manual/api/reference/item/object#item) -   [主机](/manual/api/reference/host/object#host) -   [主机组](/manual/api/reference/hostgroup/object#host_group)

en-us	### See also  -   [Discovery     rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Item](/manual/api/reference/item/object#item) -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group)
zh-cn	### 另见  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [监控项](/manual/api/reference/item/object#item) -   [主机](/manual/api/reference/host/object#host) -   [主机组](/manual/api/reference/hostgroup/object#host_group)

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8)  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8)  ------------------------------------------------------------------------  [ ]{#index}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}
zh-cn	## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAJ}
zh-cn	＃＃ 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAI}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAI}

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
zh-cn	### 另见  -   [图表监控项](/manual/api/reference/graphitem/object#图表监控项)

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
zh-cn	 ### 另见  -   [图表监控项](/manual/api/reference/graphitem/object#graph_item)

en-us	### See also  -   [Graph](/manual/api/reference/graph/object#graph)
zh-cn	 ### 另见  -   [图表](/manual/api/reference/graph/object#图表)

en-us	### See also  -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Host](/manual/api/reference/host/object#host) -   [Item prototype](/manual/api/reference/itemprototype/object#item_prototype) -   [LLD rule filter](object#lld_rule_filter) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [图形原型](/manual/api/reference/graphprototype/object#图形原型) - [主机](/manual/api/reference/host/object#主机) - [监控项原型](/manual/api/reference/itemprototype/object#监控项原型) - [LLD规则过滤](object#lld-规则过滤器) - [触发器原型](/manual/api/reference/triggerprototype/object#触发器原型)

en-us	### See also  -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Host](/manual/api/reference/host/object#host) -   [Item     prototype](/manual/api/reference/itemprototype/object#item_prototype) -   [LLD rule filter](object#lld_rule_filter) -   [Trigger     prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [图形原型](/manual/api/reference/graphprototype/object#图形原型) - [主机](/manual/api/reference/host/object#主机) - [监控项原型](/manual/api/reference/itemprototype/object#监控项原型) - [LLD规则过滤](object#lld-规则过滤器) - [触发器原型](/manual/api/reference/triggerprototype/object#触发器原型)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 另请参阅  -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#template) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface) -   [Host inventory](object#host_inventory) -   [Host tag](object#host_tag)
zh-cn	 ### 参考  -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface) -   [Host inventory](object#host_inventory) -   [Host tag](object#host_tag)

en-us	### See also  -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 参阅  -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](object#template) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [hostgroup.update](update) -   [hostgroup.massadd](massadd) -   [Host](/manual/api/reference/host/object#host) -   [Template](/manual/api/reference/template/object#template)
zh-cn	### 另请参阅  -   [主机组更新](update) -   [主机组批量添加](massadd) -   [主机](/manual/api/reference/host/object#host) -   [模板](/manual/api/reference/template/object#template)

en-us	### See also  -   [hostinterface.create](create) -   [host.massadd](/manual/api/reference/host/massadd) -   [Host](/manual/api/reference/host/object#host)
zh-cn	### 参考  -   [主机接口创建](create) -   [主机接口批量添加](/manual/api/reference/host/massadd) -   [主机](/manual/api/reference/host/object#host)

en-us	### See also  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)
zh-cn	### 参考  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)
zh-cn	### 参考  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)

en-us	### See also  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)
zh-cn	### 参考  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [主机](/manual/api/reference/host/object#host) - [图形原型](/manual/api/reference/graphprototype/object#graph_prototype) - [触发器原型](/manual/api/reference/triggerprototype/object#trigger_prototype)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Trigger     prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [主机](/manual/api/reference/host/object#host) - [图形原型](/manual/api/reference/graphprototype/object#graph_prototype) - [触发器原型](/manual/api/reference/triggerprototype/object#trigger_prototype)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Time period](object#time_period)
zh-cn	### 参见  - [主机](/manual/api/reference/host/object#host) - [主机组](/manual/api/reference/hostgroup/object#host_group) - [时间段](object#time_period)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Item](/manual/api/reference/item/object#item)
zh-cn	### 参考  -   [主机](/manual/api/reference/host/object#host) -   [监控项](/manual/api/reference/item/object#item)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#主机) -   [媒介类型](/manual/api/reference/mediatype/object#媒介类型) -   [用户](/manual/api/reference/user/object#用户)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -  [主机](/manual/api/reference/host/object#host) -  [proxy接口](object#proxy_interface)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#host) -   [proxy接口](object#proxy_interface)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#主机) -   [代理接口](object#代理接口)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Host](/manual/api/reference/host/object#主机) -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Template](/manual/api/reference/template/object#template)
zh-cn	### 另请参阅  -   [主机](/manual/api/reference/host/object#host) -   [模板](/manual/api/reference/template/object#template)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Template](/manual/api/reference/template/object#template)
zh-cn	### 另请参考  -   [主机](/manual/api/reference/host/object#host) -   [模板](/manual/api/reference/template/object#template)

en-us	### See also  -   [Host](/manual/api/reference/host/object#object_details) -   [Host group](/manual/api/reference/hostgroup/object#object_details)
zh-cn	### 另外参考 -   [主机](/manual/api/reference/host/object#对象_详情) -   [主机组](/manual/api/reference/hostgroup/object#对象_详情)

en-us	### See also  -   [host.massadd](massadd) -   [host.massupdate](massupdate) -   [host.massremove](massremove) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface) -   [Host inventory](object#host_inventory) -   [Host tag](object#host_tag)
zh-cn	### 另请参阅  -   [主机创建](massadd) -   [主机批量更新](massupdate) -   [主机批量删除](massremove) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#template) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface) -   [主机清单](object#host_inventory) -   [主机标签](object#host_tag)

en-us	### See also  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)
zh-cn	### 参考  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)

en-us	### See also  -   [host.update](update) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	 ### 另请参阅  -   [主机更新](update) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#template) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [host.massadd](massadd) -   [host.massremove](massremove) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#host_group) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 另请参阅  -   [主机更新](update) -   [主机批量创建](massadd) -   [主机批量删除](massremove) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#host_group) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 另请参阅  -   [主机更新](update) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	 ### 参见  -   [图标映射](object#icon_mapping)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	### 参阅  -   [图标映射关系（Icon mapping）](object#icon_mapping)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	### 参阅  -   [图标映射关系（Icon mapping）](object#icon_mapping)

en-us	### See also  -   [LLD rule filter](object#lld_rule_filter) -   [LLD macro paths](object#lld_macro_path) -   [LLD rule preprocessing](object#lld_rule_preprocessing)
zh-cn	### 参见  -   [LLD规则过滤](object#lld-规则过滤器) -   [LLD宏路径](object#lld宏路径) -   [LLD规则预处理](object#lld-规则预处理)

en-us	### See also  -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shape](object#map_shapes) -   [Map line](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Media](/manual/api/reference/user/object#media) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)
zh-cn	### 参考  -   [媒介](/manual/api/reference/user/object#media) -   [媒介类型](/manual/api/reference/mediatype/object#media_type) -   [用户组](/manual/api/reference/usergroup/object#user_group) -   [角色](/manual/api/reference/role/object#role)

en-us	### See also  -   [Permission](object#permission)
zh-cn	### 参考  -   [权限](object#permission)

en-us	### See also  -   [Permission](object#permission)
zh-cn	### 参考  -   [权限](object#permission)

en-us	### See also  -   [Role rules](/manual/api/reference/role/object#role_rules) -   [User](/manual/api/reference/user/object#user)
zh-cn	### 另请参考  -   [角色规则](/manual/api/reference/role/object#role_rules) -   [用户](/manual/api/reference/user/object#user)

en-us	### See also  -   [Role rules](object#role_rules) -   [UI element](object#ui_element) -   [Module](object#module) -   [Action](object#action)
zh-cn	### 另见  -   [Role rules](object#role_rules) -   [UI element](object#ui_element) -   [Module](object#module) -   [Action](object#action)

en-us	### See also  -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Task](/manual/api/reference/task/object) -   ['Check now' request object](/manual/api/reference/task/object) -   ['Diagnostic information' request object](/manual/api/reference/task/object) -   [Statistic request object](/manual/api/reference/task/object)
zh-cn	### 参阅 -   [任务](/manual/api/reference/task/object) -   ['Check now' 请求对象](/manual/api/reference/task/object) -   ['Diagnostic information' 请求对象](/manual/api/reference/task/object) -   [统计请求对象](/manual/api/reference/task/object)

en-us	### See also  -   [Task](/manual/api/reference/task/object) -   ['Check now' request object](/manual/api/reference/task/object) -   ['Diagnostic information' request     object](/manual/api/reference/task/object) -   [Statistic request object](/manual/api/reference/task/object)
zh-cn	### 参阅 -   [任务](/manual/api/reference/task/object) -   ['Check now' 请求对象](/manual/api/reference/task/object) -   ['Diagnostic information' 请求对象](/manual/api/reference/task/object) -   [统计请求对象](/manual/api/reference/task/object)

en-us	### See also  -   [Task](/manual/api/reference/task/object) -   [Statistic result object](/manual/api/reference/task/object#statistic_result_object)
zh-cn	### 参阅  -   [任务](/manual/api/reference/task/object) -   [统计结果对象](/manual/api/reference/task/object#statistic_result_object)

en-us	### See also  -   [Task](/manual/api/reference/task/object) -   [Statistic result     object](/manual/api/reference/task/object#statistic_result_object)
zh-cn	### 参阅  -   [任务](/manual/api/reference/task/object) -   [统计结果对象](/manual/api/reference/task/object#statistic_result_object)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘页面](object#template_dashboard_page) -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘页面](object#template_dashboard_page) -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [template.update](update) -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参阅  -   [更新](update) -   [主机](/manual/api/reference/host/object#host) -   [主机群组](/manual/api/reference/hostgroup/object#host_group) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [template.update](update) -   [template.massadd](massadd) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参阅  -   [更新模板](update) -   [批量添加模板](massadd) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [template.update](update) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参阅  -   [更新模板](update) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Time period](object#time_period)
zh-cn	### 另见  -   [Time period](object#time_period)

en-us	### See also  -   [Time period](object#time_period)
zh-cn	 ### 参见  - [时间段](object#time_period)

en-us	### See also  -   [trigger.adddependencies](adddependencies) -   [trigger.deletedependencies](deletedependencies)
zh-cn	### 另见  -   [触发器添加依赖](adddependencies) -   [触发器删除依赖](deletedependencies)

en-us	### See also  -   [trigger.update](update)
zh-cn	### 另见  -   [更新触发器](update)

en-us	### See also  -   [trigger.update](update) -   [Trigger dependencies](/manual/config/triggers/dependencies)
zh-cn	### 另见  -   [更新触发器](update) -   [触发器依赖关系](/manual/config/triggers/dependencies)

en-us	### See also  -   [user.login](login)
zh-cn	### 参考  -   [登录](login)

en-us	### See also  -   [user.logout](logout)
zh-cn	### 参考  -   [注销](logout)

en-us	### See also  -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参考  -   [用户](/manual/api/reference/user/object#user)

en-us	### See also  -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参见  -   [用户](/manual/api/reference/user/object#用户)

en-us	### See also  -   [Users](/manual/api/reference/user/object#users) -   [User groups](/manual/api/reference/user/object#user_groups)
zh-cn	### 另请参考  -   [用户](zh/manual/api/reference/user/object#users) -   [用户组](zh/manual/api/reference/user/object#user_groups)

en-us	### See also  -   [Users](object#users) -   [User groups](object#user_groups)
zh-cn	### 另请参考  -   [用户](object#users) -   [用户组](object#user_groups)

en-us	### See also  -   [Users](object#users) -   [User groups](object#user_groups)
zh-cn	### 另请参考  -   [用户](object#users) -   [用户组](object#user_groups)

en-us	#### See also  -   [Zabbix blog article on SNMP     traps](https://blog.zabbix.com/snmp-traps-in-zabbix) -   [Configuring snmptrapd (official net-snmp documentation)](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd) -   [Configuring snmptrapd to receive SNMPv3 notifications (official net-snmp documentation)](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications)
zh-cn	#### 请参阅  - · [关于SNMP traps的Zabbix博客文章](https://blog.zabbix.com/snmp-traps-in-zabbix) - · [配置snmptrapd（net-snmp官方文档）](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd) - · [配置snmptrapd接收SNMPv3通知（net-snmp官方文档）](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications)

en-us	#### Seeing data  With an item defined, you might be curious if it is actually gathering data. For that, go to *Monitoring → Latest data*, select 'New host' in the filter and click on *Apply*.  ![](../../../assets/en/manual/quickstart/latest_data.png){width="600"}  With that said, it may take up to 60 seconds for the first data to arrive. That, by default, is how often the server reads configuration changes and picks up new items to execute.  If you see no value in the 'Change' column, maybe only one value has been received so far. Wait 30 seconds for another value to arrive.  If you do not see information about the item as in the screenshot, make sure that:  -   you have filled out the item 'Key' and 'Type of information' fields     exactly as in the screenshot -   both the agent and the server are running -   host status is 'Monitored' and its availability icon is green -   a host is selected in the host dropdown, the item is active
zh-cn	#### 查看数据  当一个监控项创建完成后，你可能好奇它具体获得了什么值。前往*Monitoring → Latest data*， 在过滤器中选择刚才新建的主机，然后点击*Apply*。  ![](../../../assets/en/manual/quickstart/latest_data.png){width="600"}  同时，第一次获得的监控项值最多可能需要60秒。默认情况下，这是服务器读取变化后的配置文件，获取并执行新的监控项的频率。  如果你在”更改“列中没有看到值，可能到目前为止只获得了一次值。等待30秒以获得新的监控项值。  如果你在没有看到类似截图中的监控项信息，请确认：  -   你输入的监控项”键值“和”信息类型“同截图中的一致 -   agent和server都处于运行状态 -   主机状态为“已启用”并且它的可用性图标是绿色的 -   在主机的下拉菜单中已经选择了对应主机，且监控项处于已启用状态

en-us	#### Selecting a language  There are several ways to select a language in Zabbix web interface:  -   When installing web interface - in the frontend [installation     wizard](/manual/installation/frontend#welcome_screen). Selected     language will be set as system default. -   After the installation, system default language can be changed in     the *Administration→General→GUI* [menu     section](/manual/web_interface/frontend_sections/administration/general#gui). -   Language for a particular user can be changed in the [user     profile](/manual/web_interface/user_profile#user_profile).  If a locale for a language is not installed on the machine, this language will be greyed out in Zabbix language selector. A red icon is displayed next to the language selector if at least one locale is missing. Upon pressing on this icon the following message will be displayed: "You are not able to choose some of the languages, because locales for them are not installed on the web server."  ![locale\_warning.png](../../../../assets/en/manual/appendix/install/locale_warning.png){width="600"}
zh-cn	#### 选择语言  有几种方法可以在Zabbix Web界面中选择语言：  -   安装 Web 界面时 - 在前端 [installation wizard](/manual/installation/frontend#welcome_screen) 中。选择的语言将被设置为系统默认值。 -   安装完成后，系统默认语言可以在 *Administration→General→GUI* [menu section](/manual/web_interface/frontend_sections/administration/general#gui) 找到. -   特定用户的语言可以在 [user profile](/manual/web_interface/user_profile#user_profile)找到.  如果计算机上未安装某种语言的区域设置，则此语言将在 Zabbix 语言选择器中显示为灰色。如果没有一个可用的区域设置，则在语言选择器旁边显示一个红色图标。按下此图标后，将显示以下消息：“您无法选择某些语言，因为Web服务器上未安装它们。”  ![locale\_warning.png](../../../../assets/en/manual/appendix/install/locale_warning.png){width="600"}

en-us	#### Selecting elements  To select elements, select one and then hold down *Ctrl* to select the others.  You can also select multiple elements by dragging a rectangle in the editable area and selecting all elements in it.  Once you select more than one element, the element property form shifts to the mass-update mode so you can change attributes of selected elements in one go. To do so, mark the attribute using the checkbox and enter a new value for it. You may use macros here (for example, {HOST.NAME} for the element label).  ![](../../../../../assets/en/manual/config/visualization/map_update.png){width="600"}
zh-cn	#### 选择元素  要选择元素，请选择一个，然后按住 *Ctrl* 选择其他。  您还可以通过在可编辑区域并选择其中的所有元素。  一旦选择了多个元素，元素属性形式就会发生变化到批量更新模式，以便您可以更改选定的属性元素一气呵成。为此，请使用复选框标记属性，然后为其输入一个新值。您可以在此处使用宏（例如，{HOST.NAME} 用于元素标签）。  ![](../../../../../assets/en/manual/config/visualization/map_update.png){width="600"}

en-us	#### Self-signed certificate, unknown CA  [*OpenSSL*]{.underline}, in log:      error:'self signed certificate: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/statem/statem_clnt.c\           line 1924: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:\           TLS write fatal alert "unknown CA"'  This was observed when server certificate by mistake had the same Issuer and Subject string, although it was signed by CA. Issuer and Subject are equal in top-level CA certificate, but they cannot be equal in server certificate. (The same applies to proxy and agent certificates.)
zh-cn	 #### 自签证书，未知CA  [*OpenSSL*]{.underline}, 在日志中显示：      error:'self signed certificate: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/statem/statem_clnt.c\           line 1924: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:\           TLS write fatal alert "unknown CA"'  当服务器证书错误地具有相同的颁发者和主题字符串时，尽管该字符串是由 CA 签名的，但颁发者和主题在顶级 CA 证书中相同，但在服务器证书中不能相同时，就会看到这种情况。（这同样适用于proxy和agent证书。）

en-us	#### SELinux configuration  See [SELinux configuration](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) for RHEL/CentOS.  After the frontend and SELinux configuration is done, restart the Apache web server:      # service apache2 restart
zh-cn	#### 配置 SELinux   参阅适用于RHEL/CentOS 的 [SELinux 配置](/manual/installation/install_from_packages/rhel_centos#selinux_configuration)。  前端和 SELinux 配置好之后，重启 Apache 网络服务器：      # service apache2 restart

en-us	#### SELinux configuration Zabbix uses socket-based inter-process communication. On systems where SELinux is enabled, it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the SocketDir directory. Currently socket files are used by server (alerter, preprocessing, IPMI) and proxy (IPMI). Socket files are persistent, meaning they are present while the process is running.  Having SELinux status enabled in enforcing mode, you need to execute the following commands to enable communication between Zabbix frontend and server:  RHEL 7 and later:      # setsebool -P httpd_can_connect_zabbix on     If the database is accessible over network (including 'localhost' in case of PostgreSQL), you need to allow Zabbix frontend to connect to the database too:     # setsebool -P httpd_can_network_connect_db on  RHEL prior to 7:      # setsebool -P httpd_can_network_connect on     # setsebool -P zabbix_can_network on  After the frontend and SELinux configuration is done, restart the Apache web server:      # service httpd restart
zh-cn	 #### 配置 SELinux   Zabbix 使用基于套接字的进程间通信。在启用 SELinux 的系统上，可能需要添加 SELinux 规则以允许 Zabbix 在 SocketDir 目录中创建/使用 UNIX 域套接字。当前，server（警报器、预处理器、IPMI）和 proxy（IPMI）使用套接字文件。套接字文件是持久的，这意味着它们在进程运行时存在。  在 enforcing 模式下启用 SELinux 状态，你需要执行以下命令来启用 Zabbix 前端和服务器之间的通信：  RHEL 7 及更高版本：      # setsebool -P httpd_can_connect_zabbix on     If the database is accessible over network (including 'localhost' in case of PostgreSQL), you need to allow Zabbix frontend to connect to the database too:     # setsebool -P httpd_can_network_connect_db on  RHEL 7 之前的版本：      # setsebool -P httpd_can_network_connect on     # setsebool -P zabbix_can_network on  前端和 SELinux 配置完成后，重启 Apache 网络服务器：      # service httpd restart

en-us	##### Sending alerts via WinPopUps  WinPopUps maybe very useful if you're running Windows OS and want to get quick notification from Zabbix. It could be good addition for email-based alert messages. Details about enabling of WinPopUps can be found at <http://www.zabbix.com/forum/showthread.php?t=2147>.
zh-cn	#####  通过WinPopUps发送警报  如果您正在运行 Windows 操作系统并希望从 Zabbix 获得快速通知，WinPopUps 可能非常有用。对于基于电子邮件的警报消息，是一个很好的补充。有关启用 WinPopUps 的详细信息，请访问 <http://www.zabbix.com/forum/showthread.php?t=2147>。

en-us	##### Sending in data  In the simplest of cases, we may use [zabbix\_sender](/manual/concepts/sender) utility to send in some 'test value':      zabbix_sender -z <server IP address> -p 10051 -s "New host" -k trap -o "test value"  To send in the value we use these keys:  *-z* - to specify Zabbix server IP address  *-p* - to specify Zabbix server port number (10051 by default)  *-s* - to specify the host (make sure to use the 'technical' [host name](/manual/config/hosts/host#configuration) here, instead of the 'visible' name)  *-k* - to specify the key of the item we just defined  *-o* - to specify the actual value to send  ::: noteimportant Zabbix trapper process does not expand macros used in the item key in attempt to check corresponding item key existence for targeted host. :::
zh-cn	##### 数据发送  在最简单的情况下，我们可以使用 [zabbix\_sender](/manual/concepts/sender)程序来发送一些“测试值”：      zabbix_sender -z <server IP address> -p 10051 -s "New host" -k trap -o "test value"  我们使用下列这些关键字来指定发送值  *-z* - 指定Zabbix server的IP地址  *-p* - 指定Zabbix server的端口（默认为10051）  *-s* -指定主机（请确保在此使用“主机名称”的[主机名](/manual/config/hosts/host#configuration) ，而不是“可见的名称”名称）  *-k* - 指定我们之前定义的监控项的键值  *-o* - 指定要发送的实际值  ::: noteimportant  Zabbix trapper进程不会扩展监控项键值中使用的宏，以检查目标主机对应的监控项键值是否存在。 :::

en-us	 ##### Separate configuration files Each Zabbix agent 2 plugin now has a separate [configuration file](/manual/appendix/config/zabbix_agent2_plugins). By default, these files are located in the `./zabbix_agent2.d/plugins.d/` directory. The path is specified in the `Include` parameter of the agent 2 configuration file and can be relative to the [zabbix\_agent2.conf](/manual/appendix/config/zabbix_agent2) or [zabbix\_agent2.win.conf](/manual/appendix/config/zabbix_agent2_win) file location.
zh-cn	##### 单独的配置文件  每个 Zabbix agent 2 插件现在都有一个单独的 [配置文件](/manual/appendix/config/zabbix_agent2_plugins)。默认情况下，这些文件位于`./zabbix_agent2.d/plugins.d/` 目录中。该路径在 agent 2 配置文件的 `Include` 参数中指定，查看 [zabbix\_agent2.conf](/manual/appendix/config/zabbix_agent2)  或 [zabbix\_agent2.win.conf](/manual/appendix/config/zabbix_agent2_win) 文件相对路径。

en-us	##### Separate processing for ODBC checks  ODBC checks processing is now performed by separate server/proxy processes *odbc pollers*. Previously, ODBC checks were performed by regular pollers, which also work with Zabbix agent items, SSH checks, etc.   A new configuration parameter *StartODBCPollers* has been added to Zabbix [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files with the default value *1*. This parameter may need to be adjusted based on the number of ODBC checks performed by the server or proxy. You may also want to reduce the number of regular pollers set by the *StartPollers* parameter accordingly.  Internal item *zabbix[process,<type>]* can be used to monitor ODBC pollers load. 
zh-cn	##### 单独处理 ODBC 检查  ODBC 检查处理现在由单独的 server/proxy 进程 *odbc pollers*执行。以前，ODBC 检查是由常规轮询器执行的，它也适用于 Zabbix 代理项、SSH 检查等。  Zabbix [server](/manual/appendix/config/zabbix_server) 和 [proxy](/manual/appendix/config/zabbix_proxy) 配置文件中添加了一个新的配置参数  *StartODBCPollers* 默认值为 *1*。此参数可能需要根据 server 或  proxy 执行的 ODBC 检查次数进行调整。你也可以相应地减少 *StartPollers* 参数设置的常规轮询器的数量。  内部监控项 *zabbix[process,<type>]* 可用于监控 ODBC 轮询器负载。   

en-us	### Separate processing for ODBC checks  Processing ODBC checks has been moved from regular poller processes to separate server/proxy processes *ODBC pollers*. This change allows limiting the number of connections to the database created by poller processes. Previously, ODBC checks were performed by regular pollers, which also work with Zabbix agent items, SSH checks, etc.  A new configuration parameter *StartODBCPollers* has been added to Zabbix [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files.  You can use internal item *zabbix[process,<type>]* to monitor ODBC pollers load.  
zh-cn	### Item value widget  An *Item value* widget has been added to dashboard widgets.   This type of widget is useful for displaying values of  single items prominently. Different visual styles of display  are possible:  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets_new.png)  For more information, see [Item value widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value).  

en-us	### Separate processing for ODBC checks  Processing ODBC checks has been moved from regular poller processes to separate server/proxy processes *ODBC pollers*. This change allows limiting the number of connections to the database created by poller processes. Previously, ODBC checks were performed by regular pollers, which also work with Zabbix agent items, SSH checks, etc.  A new configuration parameter *StartODBCPollers* has been added to Zabbix [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files.  You can use internal item *zabbix[process,\<type\>]* to monitor ODBC pollers load.
zh-cn	### 单独处理 ODBC 检查  处理 ODBC 检查已从常规轮询器进程转移到单独的 server/proxy 进程 *ODBC pollers*。此更改允许限制轮询进程创建的与数据库的连接数。以前，ODBC 检查是由常规轮询器执行的，它也适用于 Zabbix agent 监控项、SSH 检查等。  Zabbix [server](/manual/appendix/config/zabbix_server) 和 [proxy](/manual/appendix/config/zabbix_proxy) 配置文件中添加了一个新的配置参数*StartODBCPollers* 。  您可以使用内部监控项 *zabbix[process,\<type\>]* 来监控 ODBC 轮询器负载。

en-us	##### Serialization rules  XML to JSON conversion will be processed according to the following rules (for JSON to XML conversions reversed rules are applied):  1\. XML attributes will be converted to keys that have their names prepended with '@'.  Example:  *Input:*       <xml foo="FOO">        <bar>          <baz>BAZ</baz>        </bar>      </xml>  *Output:*  ``` {.java}  {    "xml": {      "@foo": "FOO",      "bar": {        "baz": "BAZ"      }    }  } ```  2\. Self-closing elements (<foo/>) will be converted as having 'null' value.  Example:  *Input:*      <xml>       <foo/>     </xml>  *Output:*  ``` {.java} {   "xml": {     "foo": null   } } ```  3\. Empty attributes (with "" value) will be converted as having empty string ('') value.  Example:  *Input:*      <xml>       <foo bar="" />     </xml>  *Output:*  ``` {.java} {   "xml": {     "foo": {       "@bar": ""     }   } } ```  4\. Multiple child nodes with the same element name will be converted to a single key that has an array of values as its value.  Example:  *Input:*      <xml>       <foo>BAR</foo>       <foo>BAZ</foo>       <foo>QUX</foo>     </xml>  *Output:*  ``` {.java} {   "xml": {     "foo": ["BAR", "BAZ", "QUX"]   } } ```  5\. If a text element has no attributes and no children, it will be converted as a string.  Example:  *Input:*      <xml>         <foo>BAZ</foo>     </xml>  *Output:*  ``` {.java} {   "xml": {     "foo": "BAZ"    } } ```  6\. If a text element has no children, but has attributes: text content will be converted to an element with the key '\#text' and content as a value; attributes will be converted as described in the serialization rule 1.  Example:  *Input:*      <xml>       <foo bar="BAR">         BAZ       </foo>     </xml>  *Output:*  ``` {.java} {   "xml": {     "foo": {       "@bar": "BAR",       "#text": "BAZ"     }   } } ```
zh-cn	##### 序列化规则  XML 到 JSON 的转换将根据以下规则进行处理（对于 JSON 到 XML 的转换，应用相反的规则）：  1\. XML 属性将被转换为名称前面带有“@”的键。  示例:  *输入:*       <xml foo="FOO">        <bar>          <baz>BAZ</baz>        </bar>      </xml>  *输出:*  ``` {.java}  {    "xml": {      "@foo": "FOO",      "bar": {        "baz": "BAZ"      }    }  } ```  2\. 自闭合元素 (<foo/>) 将被转换为具有 'null' 值。  示例:  *输入:*      <xml>       <foo/>     </xml>  *输出:*  ``` {.java} {   "xml": {     "foo": null   } } ```  3\. 空属性（具有 "" 值）将被转换为具有空字符串 ('') 值。  示例:  *输入:*      <xml>       <foo bar="" />     </xml>  *输出:*  ``` {.java} {   "xml": {     "foo": {       "@bar": ""     }   } } ```  4\. 具有相同元素名称的多个子节点将被转换为具有值数组作为其值的单个键。  示例:  *输入:*      <xml>       <foo>BAR</foo>       <foo>BAZ</foo>       <foo>QUX</foo>     </xml>  *输出:*  ``` {.java} {   "xml": {     "foo": ["BAR", "BAZ", "QUX"]   } } ```  5\. 如果文本元素没有属性也没有子元素，它将被转换为字符串。  示例:  *输入:*      <xml>         <foo>BAZ</foo>     </xml>  *输出:*  ``` {.java} {   "xml": {     "foo": "BAZ"    } } ```  6\.如果一个文本元素没有子元素，但有属性：文本内容将被转换为一个元素，键为'\#text'，内容为值； 属性将按照序列化规则 1 中的说明进行转换。  示例:  *输入:*      <xml>       <foo bar="BAR">         BAZ       </foo>     </xml>  *输出:*  ``` {.java} {   "xml": {     "foo": {       "@bar": "BAR",       "#text": "BAZ"     }   } } ```

en-us	##### Server configuration  By default, the Zabbix server is not configured to start any IPMI pollers, thus any added IPMI items won't work. To change this, open the Zabbix server configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) as root and look for the following line:      # StartIPMIPollers=0  Uncomment it and set poller count to, say, 3, so that it reads:      StartIPMIPollers=3  Save the file and restart zabbix\_server afterwards.
zh-cn	 ##### 服务器配置  默认情况下，Zabbix服务器未配置为启动任何IPMI轮询，因此任何添加的IPMI监控项将无法正常工作。要更改此选项，请以root身份打开Zabbix服务器配置文件([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) 并查找以下行:      # StartIPMIPollers=0  取消注释，并设置 IPMI Poller 计数为3，如下:      StartIPMIPollers=3  保存文件，然后重启 zabbix\_server 。

en-us	### Server/frontend/agent installation  To install Zabbix server/frontend/agent with MySQL support:      # zypper install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-agent  Substitute 'apache' in the command with 'nginx' if using the package for Nginx web server. See also: [Nginx setup for Zabbix on SLES 12/15](/manual/appendix/install/nginx).  Substitute 'zabbix-agent' with 'zabbix-agent2' in these commands if using Zabbix agent 2 (only SLES 15 SP1+).  To install Zabbix proxy with MySQL support:      # zypper install zabbix-proxy-mysql  Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL.
zh-cn	### 安装Server/frontend/agent  安装支持MySQL的Zabbix server/frontend/agent:      # zypper install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-agent   如果将包用于 Nginx 网络服务器，请将命令中的 'apache' 替换为 'nginx' 。详见：[在 SLES 12/15 上为 Zabbix 设置 Nginx](/manual/appendix/install/nginx)。  若使用Zabbix agen 2（仅 SLES 15 SP1+)，需将命令中的 'zabbix-agent' 替换为 'zabbix-agent2' 。  安装支持 MySQL 的 Zabbix proxy：      # zypper install zabbix-proxy-mysql  将命令中的 'mysql'替换为 'pgsql' 以使用PostgreSQL。

en-us	#### Server is configured to connect with PSK to agent but agent accepts only unencrypted connections  In server or proxy log (with *GnuTLS* 3.3.16)      Get value from agent failed: zbx_tls_connect(): gnutls_handshake() failed: \         -110 The TLS connection was non-properly terminated.  In server or proxy log (with *OpenSSL* 1.0.2c)      Get value from agent failed: TCP connection successful, cannot establish TLS to [[127.0.0.1]:10050]: \         Connection closed by peer. Check allowed connection types and access rights
zh-cn	#### Server配置为使用 PSK 连接到agent，但agent仅接受未加密的连接  在server或proxy日志中有如下显示 (对于 *GnuTLS* 3.3.16)      Get value from agent failed: zbx_tls_connect(): gnutls_handshake() failed: \         -110 The TLS connection was non-properly terminated.  在server或proxy日志中有如下显示 (对于 *OpenSSL* 1.0.2c)      Get value from agent failed: TCP connection successful, cannot establish TLS to [[127.0.0.1]:10050]: \         Connection closed by peer. Check allowed connection types and access rights

en-us	##### Server  Mandatory requirements are needed always. Optional requirements are needed for the support of the specific function.  |Requirement|Status|Description| |-----------|------|-----------| |*libpcre*|Mandatory|PCRE library is required for [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) support.<br>The naming may differ depending on the GNU/Linux distribution, for example 'libpcre3' or 'libpcre1'. PCRE v8.x and PCRE2 v10.x (from Zabbix 6.0.0) are supported.| |*libevent*|^|Required for bulk metric support and IPMI monitoring. Version 1.4 or higher.<br>Note that for Zabbix proxy this requirement is optional; it is needed for IPMI monitoring support.| |*libpthread*|^|Required for mutex and read-write lock support.| |*zlib*|^|Required for compression support.| |*OpenIPMI*|Optional|Required for IPMI support.| |*libssh2* or *libssh*|^|Required for [SSH checks](/manual/config/items/itemtypes/ssh_checks#overview). Version 1.0 or higher (libssh2); 0.6.0 or higher (libssh).<br>libssh is supported since Zabbix 4.4.6.| |*fping*|^|Required for [ICMP ping items](/manual/config/items/itemtypes/simple_checks#icmp_pings).| |*libcurl*|^|Required for web monitoring, VMware monitoring, SMTP authentication, `web.page.*` Zabbix agent [items](/manual/config/items/itemtypes/zabbix_agent), HTTP agent items and Elasticsearch (if used). Version 7.28.0 or higher is recommended.<br>Libcurl version requirements:<br>- SMTP authentication: version 7.20.0 or higher<br>- Elasticsearch: version 7.28.0 or higher| |*libxml2*|^|Required for VMware monitoring and XML XPath preprocessing.| |*net-snmp*|^|Required for SNMP support. Version 5.3.0 or higher.| |*GnuTLS*, *OpenSSL* or *LibreSSL*|^|Required when using [encryption](/manual/encryption#compiling_zabbix_with_encryption_support).|
zh-cn	##### Server  强制性要求始终需要。可选要求在支持特定功能时需要。  |需求|状态|描述| |-----------|------|-----------| |*libpcre*|强制|PCRE 库 被 [Perl 兼容正则表达式](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) 支持 所需要。<br> 命名可能因 GNU/Linux 发行版而异，例如 'libpcre3' 或 'libpcre1'。(Zabbix 6.0.0)支持 PCRE v8.x 及 PCRE2 v10.x。| |*libevent*|^|大量请求指标和IPMI监控需要。1.4版本及以上。<br>Zabbix proxy该项可选；IPMI监控支持必须。| |*libpthread*|^|被 互斥锁（mutex）和 读写分离锁 （read-write lock）支持 所需要。| |*zlib*|^|被 压缩支持 所需要。| |*OpenIPMI*|可选|被 IPMI 支持 所需要。| |*libssh2*|^|被 SSH 支持所需要。 版本 1.0 以上。| |*fping*|^|被 [ICMP ping 监控项](/manual/config/items/itemtypes/simple_checks#icmp_pings) 所需要。| |*libcurl*|^| 被 web 监控， VMware 监控 和 SMTP 认证 所需要。如果是为了 SMTP 认证，需要 7.20.0 以上的版本，同时需要 Elasticsearch。| |*libiksemel*|^|被 Jabber 支持 所需要。| |*libxml2*|^|被 VMware 监控 所需要。| |*net-snmp*|^|被 SNMP 支持 所需要。|

en-us	#### Server  To enable encryption with certificate and database host identity verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_full     DBTLSCAFile=/etc/ssl/pgsql/root.crt     DBTLSCertFile=/etc/ssl/pgsql/client.crt     DBTLSKeyFile=/etc/ssl/pgsql/client.key     ...
zh-cn	#### 服务端  要使用证书和数据库主机身份验证为Zabbix服务器和数据库之间的连接启用加密，请配置该文件 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_full     DBTLSCAFile=/etc/ssl/pgsql/root.crt     DBTLSCertFile=/etc/ssl/pgsql/client.crt     DBTLSKeyFile=/etc/ssl/pgsql/client.key     ...

en-us	#### Server  To enable encryption with certificate verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/mysql/ca.pem     ...
zh-cn	#### 服务端  要为Zabbix服务器和数据库之间的连接启用加密和证书验证，请配置 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/mysql/ca.pem     ...