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/pgsql/root.crt     ...
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/pgsql/root.crt     ...

en-us	#### Server  To enable encryption with full 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/mysql/ca.pem     DBTLSCertFile=/etc/ssl/mysql/client-cert.pem     DBTLSKeyFile=/etc/ssl/mysql/client-key.pem     ...
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/mysql/ca.pem  DBTLSCertFile=/etc/ssl/mysql/client-cert.pem  DBTLSKeyFile=/etc/ssl/mysql/client-key.pem  ...

en-us	#### Server  To enable transport-only encryption for connections between server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...
zh-cn	#### 服务端 请配置下面的参数来启用 Zabbix 前端和数据库之间的仅传输加密连接：      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...   

en-us	#### Server  To enable transport-only encryption for connections between server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...
zh-cn	#### 服务端  要为服务端和数据库之间启用连接传输加密，请修改该文件 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...     

en-us	#### Server upgrade process
zh-cn	#### Server 升级步骤

en-us	#### Server upgrade process  
zh-cn	#### Server 升级步骤

en-us	##### Server  [Zabbix server](/manual/concepts/server) is the central component to which agents report availability and integrity information and statistics. The server is the central repository in which all configuration, statistical and operational data are stored.
zh-cn	##### Server  [Zabbix server](/manual/concepts/server) 是 agents 向其报告可用性和完整性信息和统计信息的中心组件。server 是存储所有配置、统计和操作数据的中央存储库。

en-us	#### Service actions  The following conditions can be set for service-based actions:  |Condition type|Supported operators|Description| |--------------|-------------------|-----------| |*Service*|equals<br>does not equal|Specify a service or a service to exclude.<br>**equals** - event belongs to this service.<br>**does not equal** - event does not belong to this service.<br>Specifying a parent service implicitly selects all child services. To specify the parent service only, all nested services have to be additionally set with the **does not equal** operator.| |*Service name*|contains<br>does not contain|Specify a string in the service name or a string to exclude.<br>**contains** - event is generated by a service, containing this string in the name.<br>**does not contain** - this string cannot be found in the service name.| |*Service tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag or an event tag to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag<br>**does not equal** - event does not have this tag<br>**contains** - event has a tag containing this string<br>**does not contain** - event does not have a tag containing this string.| |*Service tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag and value combination or a tag and value combination to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag and value<br>**does not equal** - event does not have this tag and value<br>**contains** - event has a tag and value containing these strings<br>**does not contain** - event does not have a tag and value containing these strings.|  
zh-cn	#### 服务动作  可以为基于服务的动作设置以下条件:  |条件类型|支持的操作符|说明| |--------------|-------------------|-----------| |*Service*|equals<br>does not equal|属于或者不属于某项服务<br>**equals** - 事件属于某项服务<br>**does not equal** - 事件不属于某项服务<br>父服务将包含所有的子服务，如需仅指定该父服务，则需要通过 **does not equal** 操作符将子服务排除| |*Service name*|contains<br>does not contain|服务名称包含或不包含指定字符串<br>**contains** - 由某项服务产生的事件，且该服务名称包含指定字符串<br>**does not contain** - 服务名称不包含指定字符串| |*Service tag name*|equals<br>does not equal<br>contains<br>does not contain|指定服务标签或者要排除的服务标签. 服务标签可以在服务配置的*Tags*页中进行配置.<br>**equals** - 具备该服务标签的服务事件<br>**does not equal** - 不具备该服务标签的事件<br>**contains** - 服务标签包含指定字符串的事件<br>**does not contain** - 服务标签不包含指定字符串的事件| |*Service tag value*|equals<br>does not equal<br>contains<br>does not contain|事件服务标签和值组合或要排除的服务标签和值组合。服务标签可以在服务配置的*Tags*页中进行配置.<br>**equals** - 具备该服务标签并且值等于给定值的事件<br>**does not equal** - 具备该服务标签但值不等于给定值的事件<br>**contains** - 具备该标签并且值包含指定字符串的事件<br>**does not contain** - 具备该标签并且值不包含指定字符串的事件|  

en-us	### Service alarm  ::: noteclassic Service alarms cannot be directly created, updated or deleted via the Zabbix API. :::  The service alarm objects represent a service's state change. It has the following properties.  | Property | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                         | |----------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| | clock    | timestamp                                           | Time when the service state change has happened.                                                                    | | value    | integer                                             | Status of the service.<br><br>Refer to the [service status property](object#service) for a list of possible values. |
zh-cn	 ### 服务告警  ::: noteclassic 服务告警不能通过Zabbix API直接创建，更新或者删除 。 :::  服务告警对象代表服务状态的变更。它有如下值：  | 属性 | [类型](/manual/api/reference_commentary#数据_类型) | 描述                                                                                                         | |----------|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| | clock    | timestamp                                           | 服务状态发生变更的时间。                                                                    | | value    | integer                                             | 服务状态。<br><br>可能值的清单请参考[服务状态属性](object#服务)。 |

en-us	### Service alarm  ::: noteclassic Service alarms cannot be directly created, updated or deleted via the Zabbix API. :::  The service alarm objects represent a service's state change. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |clock|timestamp|Time when the service state change has happened.| |value|integer|Status of the service.<br><br>Refer to the [service status property](object#service) for a list of possible values.|  
zh-cn	### Service alarm  ::: noteclassic Service alarms cannot be directly created, updated or deleted via the Zabbix API. :::  The service alarm objects represents an service's state change. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |clock|timestamp|Time when the service state change has happened.| |value|integer|Status of the service.<br><br>Refer to the [service status property](object#service) for a list of possible values.|  

en-us	#### service  Changes:\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.create`, `service.update`: added support of parameters `children`, `parents` and `tags`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`: added support of parameters `evaltype`, `tags`, `selectChildren`, `selectParents`, `selectTags`.\ [ZBXNEXT-6674](https://support.zabbix.com/browse/ZBXNEXT-6674) `service.create`, `service.update`: added support of parameter `problem_tags`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`: added support of parameters `problem_tags`, `without_problem_tags` and `selectProblemTags`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) Service object: added support of properties `weight`, `propagation_rule` and `propagation_value`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) Service object: added support of `status` value `-1` (OK).\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.create`, `service.update`: added support of parameter `status_rules`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`: added support of parameter `selectStatusRules`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`: added support of `count` for parameter `selectAlarms`.\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) Service object: added new property `readonly`.\ [ZBXNEXT-2406](https://support.zabbix.com/browse/ZBXNEXT-2406) `service.get`: added support of parameters `deep_parentids` and `selectProblemEvents`.\
zh-cn	 #### 服务  变更：\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.create`，`service.update`：添加对参数`children`，`parents`和`tags`的支持。\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`：添加对参数`evaltype`，`tags`，`selectChildren`，`selectParents`，`selectTags`的支持。\ [ZBXNEXT-6674](https://support.zabbix.com/browse/ZBXNEXT-6674) `service.create`，`service.update`：添加对参数`problem_tags`的支持。\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`：添加对参数`problem_tags`，`without_problem_tags`和`selectProblemTags`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) 服务对象：添加对属性`weight`，`propagation_rule`和`propagation_value`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) 服务对象：添加对`status`值为`-1`（OK）的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.create`，`service.update`：添加对参数`status_rules`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`：添加对参数`selectStatusRules`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`：添加对参数 `selectAlarms`的`count`的支持。\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 服务对象：添加新属性`readonly`。\ [ZBXNEXT-2406](https://support.zabbix.com/browse/ZBXNEXT-2406) `service.get`：添加对参数`deep_parentids`和`selectProblemEvents`的支持。\

en-us	#### service  Changes:\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) added new property `readonly`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) added support of properties `weight`, `propagation_rule` and `propagation_value`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) added support of `status` value *(-1 - OK)*.\ [ZBXNEXT-2406](https://support.zabbix.com/browse/ZBXNEXT-2406) `service.get`: added support of parameters `deep_parentids` and `selectProblemEvents`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.create`, `service.update`: added support of parameter `status_rules`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`: added support of parameter `selectStatusRules`.\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`: added support of `count` for parameter `selectAlarms`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.create`, `service.update`: added support of parameters `children`, `parents` and `tags`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`: added support of parameters `evaltype`, `tags`, `selectChildren`, `selectParents`, `selectTags`.\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`: added support of parameters `problem_tags`, `without_problem_tags` and `selectProblemTags`.\ [ZBXNEXT-6674](https://support.zabbix.com/browse/ZBXNEXT-6674) `service.create`, `service.update`: added support of parameter `problem_tags`.\
zh-cn	 #### 服务  变更：\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.create`，`service.update`：添加对参数`children`，`parents`和`tags`的支持。\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`：添加对参数`evaltype`，`tags`，`selectChildren`，`selectParents`，`selectTags`的支持。\ [ZBXNEXT-6674](https://support.zabbix.com/browse/ZBXNEXT-6674) `service.create`，`service.update`：添加对参数`problem_tags`的支持。\ [ZBXNEXT-3022](https://support.zabbix.com/browse/ZBXNEXT-3022) `service.get`：添加对参数`problem_tags`，`without_problem_tags`和`selectProblemTags`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) 服务对象：添加对属性`weight`，`propagation_rule`和`propagation_value`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) 服务对象：添加对`status`值为`-1`（OK）的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.create`，`service.update`：添加对参数`status_rules`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`：添加对参数`selectStatusRules`的支持。\ [ZBXNEXT-6800](https://support.zabbix.com/browse/ZBXNEXT-6800) `service.get`：添加对参数 `selectAlarms`的`count`的支持。\ [ZBXNEXT-6787](https://support.zabbix.com/browse/ZBXNEXT-6787) 服务对象：添加新属性`readonly`。\ [ZBXNEXT-2406](https://support.zabbix.com/browse/ZBXNEXT-2406) `service.get`：添加对参数`deep_parentids`和`selectProblemEvents`的支持。\

en-us	##### Service cloning  Services now can be cloned. The *Clone* button has been added to the [configuration form](/manual/web_interface/frontend_sections/monitoring/it_services#service_configuration) of a service. When a service is cloned, its parent links are preserved, while the child links are not.
zh-cn	##### 服务克隆  可以支持克隆服务。*克隆*按钮已添加到服务的[配置表单](/manual/web_interface/frontend_sections/monitoring/it_services#service_configuration)中。克隆服务时，会保留其父链接，而不会保留子链接。

en-us	### Service configuration  In the **Service** tab, specify required service parameters:  ![](../../../assets/en/manual/web_interface/service.png){width=600}  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |_**Name**_|Service name.| |_**Parent services**_|Parent services the service belongs to.<br> Leave this field empty if you are adding the service of highest level.<br> One service may have multiple parent services. In this case, it will be displayed in the service tree under each of the parent services.  | |_**Problem tags**_|Specify tags to map problem data to the service:<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>Tag name matching is always case-sensitive.| |_**Sort order**_|Sort order for display, lowest comes first.| |_**Status calculation rule**_|Rule for calculating service status:<br>**Most critical if all children have problems** - the most critical problem in the child nodes is used to color the service status, if all children have problems<br>**Most critical of child nodes** - the most critical problem in the child nodes is used to color the service status<br>**Set status to OK** - do not calculate service status<br>Mark the *Advanced configuration* checkbox below to configure additional status calculation rules.| |_**Description**_|Service description.| |_**Advanced configuration**_|Mark the checkbox to access [advanced configuration](#advanced-configuration) options.|
zh-cn	### 服务配置  在 **Service** 选项卡中，指定所需的服务参数：  ![](../../../assets/en/manual/web_interface/service.png){width=600}  所有必填输入字段均标有红色星号。  |参数|说明| |---------|-----------| |_**Name**_|服务名称。| |_**Parent services**_|服务所属的父服务。<br> 如果您要添加最高级别的服务，请将此字段留空。<br> 一个服务可以有多个父服务。在这种情况下，它将显示在每个父服务下的服务树中。  | |_**Problem tags**_|指定标签将问题数据映射到服务：<br>**Equals** - 包括指定的标签名和值（区分大小写）<br>**Contains** - 包括指定的标签名，其中标签值包含输入的字符串（子字符串的匹配不区分大小写）<br>标签名的匹配始终区分大小写。| |_**Sort order**_|显式的排序顺序，最低的排第一位。| |_**Status calculation rule**_|状态计算规则：<br>**Most critical if all children have problems** - 如果所有子节点都有问题，则根据子节点中最严重的问题对服务状态进行着色。<br>**Most critical of child nodes** - 根据子节点中最严重的问题对服务状态进行着色<br>**Set status to OK** - 不计算服务状态<br>勾选下面的 *高级配置* 复选框以配置其他状态计算规则。| |_**Description**_|服务说明。| |_**Advanced configuration**_|勾选复选框以访问 [高级配置](#高级配置) 选项。|

en-us	### Service configuration  The **Service** tab contains general service attributes:  ![](../../../../../assets/en/manual/web_interface/service.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |_**Name**_|Service name.| |_**Parent services**_|Parent services the service belongs to.| |_**Problem tags**_|Specify tags to map problem data to the service:<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>Tag name matching is always case-sensitive.| |_**Sort order**_|Sort order for display, lowest comes first.| |_**Status calculation rule**_|Rule for calculating service status:<br>**Most critical if all children have problems** - the most critical problem in the child services is used to color the service status, if all children have problems<br>**Most critical of child services** - the most critical problem in the child services is used to color the service status<br>**Set status to OK** - do not calculate service status<br>Mark the *Advanced configuration* checkbox below to configure additional status calculation rules.| |_**Description**_|Service description.| |_**Advanced configuration**_|Mark the checkbox to access on [advanced configuration](#advanced-configuration) options.|  #### Advanced configuration  ![](../../../../../assets/en/manual/web_interface/service_a.png)  |Parameter|Description| |---------|-----------| |_**Additional rules**_|Click on *Add* to define additional status calculation rules in a popup window.| |*Set status to*|Set service status to either *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster* in case of a condition match.| |*Condition*|Select the condition for direct child services:<br>**if at least (N) child services have (Status) status or above**<br>**if at least (N%) of child services have (Status) status or above**<br>**if less than (N) child services have (Status) status or below**<br>**if less than (N%) of child services have (Status) status or below**<br>**if weight of child services with (Status) status or above is at least (W)**<br>**if weight of child services with (Status) status or above is at least (N%)**<br>**if weight of child services with (Status) status or below is less than (W)**<br>**if weight of child services with (Status) status or below is less than (N%)**| |*N (W)*|Set the value of N or W (1-100000), or N% (1-100) in the condition.| |*Status*|Select the value of *Status* in the condition: *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster*.| |_**Status propagation rule**_|Rule for propagating the service status to the parent service:<br>**As is** - the status is propagated without change<br>**Increase by** - you may increase the propagated status by 1 to 5 severities<br>**Decrease by** - you may decrease the propagated status by 1 to 5 severities<br>**Ignore this service** - the status is not propagated to the parent service at all<br>**Fixed status** - the status is propagated statically, i.e. as always the same| |_**Weight**_|Weight of the service (integer in the range from 0 (default) to 1000000).|  The **Tags** tab contains service-level tags. Service-level tags are  used to identify a service. Service-level tags are not used to map  problems to the service (for that, see *Problem tags* in the first tab).  ![](../../../../../assets/en/manual/web_interface/service_b.png)  The **Child services** tab contains services the service depends on. Click on *Add* to add a service from those that are configured.
zh-cn	### 服务配置  **服务** 选项卡包含一般服务属性：  ![](../../../../../assets/en/manual/web_interface/service.png)  所有必填输入字段都标有红色星号。  |参数|描述| |---------|-----------| |_**Name**_|服务名称。| |_**Parent services**_|服务所属父级服务.| |_**Problem tags**_|指定标签以将问题数据映射到服务:<br>**Equals** - 包括指定的标签名称和值（区分大小写）<br>**Contains** - 包括指定的标签名称，其中标签值包含输入的字符串（子字符串匹配，不区分大小写）<br>标记名称匹配始终区分大小写。| |_**Sort order**_|显示排序顺序，从小到大。| |_**Status calculation rule**_|服务状态计算规则:<br>**最关键的是如果所有的孩子都有问题** - 如果所有子服务都有问题，子服务中最关键的问题用于为服务状态着色<br>**最关键的自服务** - 子服务中最关键的问题用于为服务状态着色<br>**设置状态为OK** - 不计算服务状态<br>标记 *高级配置* 下面的复选框配置额外的状态计算规则。| |_**Description**_|服务描述。| |_**Advanced configuration**_|标记复选框以访问 [高级配置](#advanced-configuration) 选项。|  #### 高级配置  ![](../../../../../assets/en/manual/web_interface/service_a.png)  |参数|描述| |---------|-----------| |_**Additional rules**_|单击 *Add* 以在弹出窗口中定义其他状态计算规则。| |*Set status to*|在条件匹配的情况下，将服务状态设置为 *OK*（默认）、*未分类*、*信息*、*警告*、*一般*、*严重* 或 *灾难*。| |*Condition*|选择直接子服务的条件:<br>**如果至少 (N) 个子服务具有 (Status) 状态或以上**<br>**如果至少 (N%) 的子服务具有 (Status) 状态或以上**<br>**如果少于 (N) 个子服务具有 (Status) 状态或以下**<br>**如果少于 (N%) 的子服务具有 (Status) 状态或以下**<br>**如果具有 (Status) 或以上状态的子服务的权重至少为 (W)**<br>**如果具有 (Status) 状态或以上的子服务的权重至少为 (N%)**<br>**如果具有 (Status) 或以下状态的子服务的权重小于 (W)**<br>**如果具有 (Status) 状态或以下状态的子服务的权重小于 (N%)**| |*N (W)*|在条件中设置 N 或 W（1-100000）或 N%（1-100）的值。| |*Status*|选择条件中*Status*的值： *OK* (默认), *未分类*, *信息*, *警告*, *一般*, *严重* 或 *灾难*.| |_**Status propagation rule**_|将服务状态传播到父服务的规则：<br>**As is** - 状态无变化地传播<br>**Increase by** - 您可以将传播状态增加 1 到 5 严重性<br>**Decrease by** - 您可以将传播状态降低 1 到 5 严重性<br>**Ignore this service** - 状态根本不会传播到父服务<br>**Fixed status** - 状态是静态传播的，即始终相同| |_**Weight**_|服务的权重（从 0（默认）到 1000000的整数）.|  **标签** 选项卡包含服务级别标签。 服务级别标签是用于标识服务。 服务级别标签不用于映射服务问题（为此，请参阅第一个选项卡中的*问题标签*）。  ![](../../../../../assets/en/manual/web_interface/service_b.png)  **子服务** 选项卡包含服务所依赖的服务。 单击 *Add* 从已配置的服务中添加服务。

en-us	# service.create
zh-cn	# 创建服务

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

en-us	### Service details  To access service details, click on the service name. To return to the  list of all services, click on *All services*.  Service details include the info box and the list of child services.  ![](../../../../../assets/en/manual/web_interface/service_details.png){width="600"}  To access the info box, click on the *Info* tab. The info box contains the  following entries:  - Names of parent services (if any) - Current status of this service - Current SLA(s) of this service, in the format `service tag:service level indicator`. 'service tag' is also link to the SLA report for this service. If you position the mouse on the service-level indicator (SLI), a pop-up info list is displayed with SLI details. - Service tags  The info box also contains a link to the [service configuration](#service-configuration).  To use the filter for child services, click on the *Filter* tab. When in  edit mode, the child service listing is complemented with additional  editing options:  -   ![](../../../../../assets/en/manual/web_interface/add_service.png) -     add a child service to this service -   ![](../../../../../assets/en/manual/web_interface/edit_service.png) -     edit this service -   ![](../../../../../assets/en/manual/web_interface/delete_service.png) -     delete this service
zh-cn	 ### 服务详情  要访问服务详情，请单击服务名称。要返回所有服务的列表，请单击*所有服务*。  服务详情包括信息框和子服务列表。  ![](../../../../../assets/en/manual/web_interface/service_details.png){width="600"}  要访问信息框，请单击*信息*选项卡。信息框包含以下条目：  - 父服务的名称（如有） - 此服务的当前状态 - 服务的当前SLA，格式为 `SLA名称:服务级别指示器`。 'SLA 名称' 也是链接到此服务的 SLA 报表。如果将鼠标放在服务级别指示器（SLI）旁边的信息框上，将显示一个带有SLI详细信息的弹出信息列表。服务级别指示器以百分比显示当前服务级别。 - 服务标签  信息框还包含指向 [服务配置](#服务配置) 的链接。  要对子服务使用过滤器，请单击*过滤器*选项卡。  在编辑模式下，子服务列表将补充其他编辑选项：  -   ![](../../../../../assets/en/manual/web_interface/add_service.png) -     添加子服务到此服务 -   ![](../../../../../assets/en/manual/web_interface/edit_service.png) -     编辑此服务 -   ![](../../../../../assets/en/manual/web_interface/delete_service.png) -     删除此服务

en-us	#### Service events  Service events are generated only if service actions for these events are enabled. In this case, each service status change creates a new event:  -   Problem event - when service status is changed from OK to PROBLEM -   OK event - when service status is changed from PROBLEM to OK  The event contains details of the service state change - when it happened and what the new state is.
zh-cn	#### 服务事件  只有在为这些事件启用了服务动作时才会生成服务事件。在这种情况下，每一个服务状态的改变都会生成一个新事件：  -   问题事件——当服务状态从OK变为问题时 -   OK事件——当服务状态从问题变为OK时  事件包含服务状态改变的详细信息——何时发生以及新状态是什么。

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

en-us	#### Service Level Agreement  Define Service Level Objectives (SLO), retrieve detailed Service Level Indicators (SLI) information about service performance.  [SLA API](/manual/api/reference/sla)
zh-cn	#### 服务水平协议  定义服务级别目标 （SLO），检索有关服务性能的详细服务级别指示器 （SLI） 信息。  [SLA API](/manual/api/reference/sla)

en-us	#### Service monitoring  Create a hierarchy representation of monitored IT infrastructure/business services data.  [Service API](/manual/api/reference/service)
zh-cn	#### 服务监控  Create a hierarchy representation of monitored IT infrastructure/business services data.  [Service API](/manual/api/reference/service)

en-us	#### Service monitoring  Retrieve detailed service layer availability information about any service.  [Service SLA calculation](/manual/api/reference/service/getsla)  
zh-cn	#### Tasks  Task manager allows to check items or low-level discovery rules without config reload.  [Task API](/manual/api/reference/task)  

en-us	 ##### Service monitoring    Several [major updates](/manual/introduction/whatsnew600#services) related to service monitoring functionality have been made. An existing service tree configuration will be changed during an upgrade in the following way:   - Trigger-based dependencies between problems and services are replaced by tag-based mapping of services to problems. Triggers that have been linked to a service will get a new tag `ServiceLink` : `<trigger ID>:<trigger name>` (tag value will be truncated to 32 characters). Linked services will get the same [problem tag](/manual/it_services/service_tree#problem-tags).  - Hard and soft dependencies no longer exist. Instead, a service will have multiple parent services.  - The 'Status calculation algorithm' will be upgraded using the following rules:     - Do not calculate → Set status to OK     - Problem, if at least one child has a problem → Most critical of child nodes     - Problem, if all children have problems → Most critical if all children have problems  - SLA is no longer a service attribute, but a separate entity which can be assigned to multiple services. During an upgrade, identical SLAs will be grouped and one SLA per each group will be created. Services will get a new [service tag](/manual/it_services/service_tree#service-tags) `SLA`:`<ID>` for matching.  See also:    - Detailed description of [service monitoring upgrade](/manual/appendix/services_upgrade); - Configuration of [services](/manual/it_services).
zh-cn	##### 服务监控    进行了与服务监控功能相关的几项 [重大更新](/manual/introduction/whatsnew600#services) 。升级期间将通过以下方式更改现有服务树配置：  - 问题和服务之间基于触发器的依赖关系被基于标签的服务到问题的映射所取代。已链接到服务的触发器将获得一个新标签`ServiceLink`：`<trigger ID>:<trigger name>`（标签值将被截断为 32 个字符）。链接的服务将获得相同的 [问题标签](/manual/it_services/service_tree#problem-tags)。  - 硬依赖和软依赖不再存在。相反，一个服务将有多个父服务。  - 'Status calculation algorithm（状态计算算法）' 将使用以下规则升级：      - Do not calculate（不计算） → 将状态设置为 OK     - 问题，如果至少一个子节点有问题 → 最关键的子节点     - 问题，如果所有子节点都有问题 → 如果所有子节点都有问题到达临界（最严重）  - SLA 不再是服务属性，而是可以分配给多个服务的单独实体。在升级期间，相同的 SLA 将被分组，并且每个组将创建一个 SLA。服务将获得一个新的 [服务标签](/manual/it_services/service_tree#service-tags) `SLA`:`<ID>` 用于匹配。  也可以参看：    - [服务监控升级](/manual/appendix/services_upgrade)详解； - [服务](/manual/it_services)配置。

en-us	# > Service object  The following objects are directly related to the `service` API.
zh-cn	# > 服务对象  以下对象与`service` API直接关联。

en-us	### Service  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**serviceid**<br>(required)|string|ID of the Service.|
zh-cn	### 业务  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**serviceid**<br>(必要)|字符串|业务ID号。|

en-us	### Service  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**serviceid**<br>(required)|string|ID of the Service.|
zh-cn	### 业务  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**serviceid**<br>(必要)|字符串|业务ID号。|

en-us	 ### Services  In older Zabbix versions, services had two types of dependencies: soft and hard. After an upgrade, all dependencies will become equal.   If a service "Child service" has been previously linked to "Parent service 1" via hard dependency and additionally "Parent service 2" via soft dependency, after an upgrade the "Child service" will have two parent services "Parent service 1" and "Parent service 2".  Trigger-based mapping between problems and services has been replaced by tag-based mapping. In Zabbix 6.0 and newer, service configuration form has a new parameter *Problem tags*, which allows specifying one or multiple tag name and value pairs for problem matching.  Triggers that have been linked to a service will get a new tag `ServiceLink` : `<trigger ID>:<trigger name>` (tag value will be truncated to 32 characters). Linked services will get `ServiceLink` [problem tag](/manual/it_services/service_tree#problem-tags) with the same value.
zh-cn	 ### 服务  在旧的 Zabbix 版本中，服务有两种类型的依赖：软依赖和硬依赖。 升级后，所有依赖项都将变得相同。  如果一个服务的“子服务”先前已通过硬依赖关系链接到“父级服务 1”并通过软依赖关系另外链接到“父级服务 2”，则升级后“子服务”将有两个父级服务“父级服务 1”和 "父级服务2"。  问题和服务之间基于触发器的映射已被基于标签的映射所取代。 在 Zabbix 6.0 及更新版本中，服务配置表单有一个新参数 *问题标签*，它允许指定一个或多个标签名称和值对用于问题匹配。 · 已链接到服务的触发器将获得一个新标签 `ServiceLink` ：`<trigger ID>:<trigger name>`（标签值将被截断为 32 个字符）。 链接服务将获得具有相同值的“ServiceLink”[问题标签](/manual/it_services/service_tree#problem-tags)。

en-us	#### Services  Manage services for service-level monitoring and retrieve detailed SLA information about any service.  [Service API](/manual/api/reference/service)
zh-cn	#### 服务  管理服务以进行服务级别监视，并检索有关任何服务的详细 SLA 信息。  [Service API](/manual/api/reference/service)

en-us	### Services  Several updates have been made to the monitoring of **services**. Service  monitoring offers a high-level view of the monitored infrastructure in Zabbix.  There is now a new Services menu in Zabbix, with four menu sections:  - [Services](/manual/web_interface/frontend_sections/services/service) - for service overview and service configuration  (moved from *Monitoring* -> *Services*) - [Service actions](/manual/web_interface/frontend_sections/services/service_actions) - for service actions (new action type) - [SLA](/manual/web_interface/frontend_sections/services/sla) - for configuring SLAs - [SLA report](/manual/web_interface/frontend_sections/services/sla_report) - for SLA reports (also available as dashboard widget)  ![](../../../assets/en/manual/introduction/services_menu.png)  Other major improvements to the services functionality  are outlined below.
zh-cn	### 服务  对**服务**的监控进行了一些更新。服务监控提供了 Zabbix 中受监控基础设施的高级视图。  Zabbix 现在有一个新的服务菜单，包含四个菜单组件：  - [服务（Services）](/manual/web_interface/frontend_sections/services/service) - 用于服务概述和服务配置（从Monitoring 移动到 Services） - [服务动作（Service actions）](/manual/web_interface/frontend_sections/services/service_actions) - 用于服务动作（新操作类型） - [SLA](/manual/web_interface/frontend_sections/services/sla) - 用于配置 SLA - [SLA 报表](/manual/web_interface/frontend_sections/services/sla_report) - 用于 SLA 报表（也可用作仪表板小部件）  ![](../../../assets/en/manual/introduction/services_menu.png)  下面概述了对服务功能的其他主要改进。

en-us	### Service tag  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Tag name.<br><br>If empty string is specified, the service tag will not be used for service matching.| |value|string|Tag value.<br><br>If no value or empty string is specified, only the tag name will be used for service matching.|
zh-cn	### 业务标签  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**tag**<br>(必要)|字符串|标签名称。<br><br>若无填写内容，则该功能不会被使用。| |value|字符串|标签数值。<br><br>若该属性没有填写任何参数，那么只有标签名称会被用来对应业务。|

en-us	### Service tag  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Tag name.<br><br>If empty string is specified, the service tag will not be used for service matching.| |value|string|Tag value.<br><br>If no value or empty string is specified, only the tag name will be used for service matching.|
zh-cn	### 业务标签  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**tag**<br>(必要)|字符串|标签名称。<br><br>若无填写内容，则该功能不会被使用。| |value|字符串|标签数值。<br><br>若该属性没有填写任何参数，那么只有标签名称会被用来对应业务。|

en-us	### Service tag  The service tag object has the following properties.  | Property              | [Type](/manual/api/reference_commentary#data_types) | Description        | |-----------------------|-----------------------------------------------------|--------------------| | **tag**<br>(required) | string                                              | Service tag name.  | | value                 | string                                              | Service tag value. |
zh-cn	 ### 服务标记  服务标记对象有如下属性。  | 属性              | [类型](/manual/api/reference_commentary#数据_类型) | 描述        | |-----------------------|-----------------------------------------------------|--------------------| | **tag**<br>(必须) | string                                              | 服务标签名称。  | | value                 | string                                              | 服务标签值。 |

en-us	### Service tag  The service tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Service tag name.| |value|string|Service tag value.|  
zh-cn	### Service dependency 服务依赖  The service dependency object represents a dependency between services. It has the following properties. 服务依赖对象表示服务之间的依赖关系，它具有以下属性。  |Property 属性        T|pe 类型        Des|ription 说明| |------------------------|--------------------|--------------| |linkid|string 字符串    *(|eadonly 只读)* ID of the service dependency. 服务依赖的ID。| |**servicedownid**<br>(required 必须)|string 字符串    ID|of the service, that a service depends on, that is, the child service. An service can have multiple children. 被子服务依赖的服务ID，一个服务可以有多个子服务。| |**serviceupid**<br>(required 必须)|string 字符串    ID|of the service, that is dependent on a service, that is, the parent service. An service can have multiple parents forming a directed graph. 依赖于父服务的服务ID，一个服务可以有多个父服务，从而形成一张定向图表。| |**soft**<br>(required 必须)|integer 整数型   Ty<br>|e of dependency between services. 服务之间的依赖关系类型。<br>Possible values: 许可值：<br>0 - hard dependency; 硬依赖；<br>1 - soft dependency. 软依赖。<br><br>An service can have only one hard-dependent parent. This attribute has no effect on status or SLA calculation and is only used to create a core service tree. Additional parents can be added as soft dependencies forming a graph. 一个服务只能有一个强依赖的父服务。该属性对状态或SLA计算没有影响，仅用于创建核心服务树。 新增的父服务可以作为形成图形的软依赖添加。<br><br>An service can not be deleted if it has hard-dependent children. 如果服务有硬依赖子服务，则无法删除该服务。|  

en-us	### Service  The service object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |serviceid|string|*(readonly)* ID of the service.| |**algorithm**<br>(required)|integer|Status calculation rule. Only applicable if child services exist.<br><br>Possible values:<br>0 - set status to OK;<br>1 - most critical if all children have problems;<br>2 - most critical of child services.| |**name**<br>(required)|string|Name of the service.| |**showsla**<br>(required)|integer|Whether SLA should be calculated.<br><br>Possible values:<br>0 - do not calculate;<br>1 - calculate.| |**sortorder**<br>(required)|integer|Position of the service used for sorting.<br><br>Possible values: 0-999.| |goodsla|float|Minimum acceptable SLA value. If the SLA drops lower, the service is considered to be in problem state.<br><br>Possible values: 0-100.<br><br>Default: 99.9.| |weight|integer|Service weight.<br><br>Possible values: 0-1000000.<br><br>Default: 0.| |propagation\_rule|integer|Status propagation rule. Must be set together with `propagation_value`.<br><br>Possible values:<br>0 - *(default)* propagate service status as is - without any changes;<br>1 - increase the propagated status by a given `propagation_value` (by 1 to 5 severities);<br>2 - decrease the propagated status by a given `propagation_value` (by 1 to 5 severities);<br>3 - ignore this service - the status is not propagated to the parent service at all;<br>4 - set fixed service status using a given `propagation_value`.| |propagation\_value|integer|Status propagation value. Must be set together with `propagation_rule`.<br><br>Possible values for `propagation_rule` with values `0` and `3`: 0.<br><br>Possible values for `propagation_rule` with values `1` and `2`: 1-5.<br><br>Possible values for `propagation_rule` with value `4`:<br>-1 - OK;<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.| |status|integer|*(readonly)* Whether the service is in OK or problem state.<br><br>If the service is in problem state, `status` is equal either to:<br>- the severity of the most critical problem;<br>- the highest status of a child service in problem state.<br><br>If the service is in OK state, `status` is equal to -1.| |readonly|boolean|*(readonly)* Access to the service.<br><br>Possible values:<br>0 - Read-write;<br>1 - Read-only.|  
zh-cn	### Service 服务  The service object has the following properties. 服务对象具有以下属性。  |Property 属性     T|pe 类型        Des|ription 说明| |---------------------|--------------------|--------------| |serviceid|string 字符串    *(|eadonly 只读)* ID of the service. 服务的ID。| |**algorithm**<br>(required 必须)|integer 整数型   Al<br>|orithm used to calculate the state of the service. 用于计算服务状态的算法。<br>Possible values: 许可值：<br>0 - do not calculate; 不计算；<br>1 - problem 问题, if at least one child has a problem; 如果至少有一个子项有问题。<br>2 - problem问题, if all children have problems. 如果所有子项都有问题。| |**name**<br>(required 必须)|string 字符串    Na|e of the service. 服务的名称。| |**showsla**<br>(required 必须)|integer 整数型   Wh<br>|ther SLA should be calculated. 是否应计算SLA。<br>Possible values: 许可值：<br>0 - do not calculate; 不计算；<br>1 - calculate. 计算。| |**sortorder**<br>(required 必须)|integer 整数型   Po|ition of the service used for sorting. 用于排序服务的位置。| |goodsla|float 浮点数     Mi|imum acceptable SLA value. If the SLA drops lower, the service is considered to be in problem state. 最低可接受的SLA值，如果SLA降低，则该服务被认为处于有问题状态。<br><br>Default: 99.9. 默认：99.9。| |status|integer 整数型   *(|eadonly 只读)* Whether the service is in OK or problem state. 服务是否处于正常或问题状态。<br><br>If the service is in problem state, `status` is equal either to: 如果服务处于问题状态，`status`相当于以下情况之一：<br>- the priority of the linked trigger if it is set to 2, "Warning" or higher (priorities 0, "Not classified" and 1, "Information" are ignored); 优先级设置为2，"Warning"或更高级别所链接的触发器告警（忽略优先级0，"Not classified"和1，"Information"）<br>- the highest status of a child service in problem state. 其中一个最高级别状态的子服务处于问题中。<br><br>If the service is in OK state, `status` is equal to 0. 如果服务是正常状态，那么`status`等于0。| |triggerid|string 字符串    Tr|gger associated with the service. Can only be set for services that don't have children. 与服务相关联的触发器只能设置在没有子项的服务上。<br><br>Default: 0 默认：0|  

en-us	### Service  The service object has the following properties.  | Property                    | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | |-----------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | serviceid                   | string                                              | *(readonly)* ID of the service.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | | **algorithm**<br>(required) | integer                                             | Status calculation rule. Only applicable if child services exist.<br><br>Possible values:<br>0 - set status to OK;<br>1 - most critical if all children have problems;<br>2 - most critical of child services.                                                                                                                                                                                                                                                                                                                | | **name**<br>(required)      | string                                              | Name of the service.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | | **sortorder**<br>(required) | integer                                             | Position of the service used for sorting.<br><br>Possible values: 0-999.                                                                                                                                                                                                                                                                                                                                                                                                                                                      | | weight                      | integer                                             | Service weight.<br><br>Possible values: 0-1000000.<br><br>Default: 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | | propagation\_rule           | integer                                             | Status propagation rule. Must be set together with `propagation_value`.<br><br>Possible values:<br>0 - *(default)* propagate service status as is - without any changes;<br>1 - increase the propagated status by a given `propagation_value` (by 1 to 5 severities);<br>2 - decrease the propagated status by a given `propagation_value` (by 1 to 5 severities);<br>3 - ignore this service - the status is not propagated to the parent service at all;<br>4 - set fixed service status using a given `propagation_value`. | | propagation\_value          | integer                                             | Status propagation value. Must be set together with `propagation_rule`.<br><br>Possible values for `propagation_rule` with values `0` and `3`: 0.<br><br>Possible values for `propagation_rule` with values `1` and `2`: 1-5.<br><br>Possible values for `propagation_rule` with value `4`:<br>-1 - OK;<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.                                                                                                              | | status                      | integer                                             | *(readonly)* Whether the service is in OK or problem state.<br><br>If the service is in problem state, `status` is equal either to:<br>- the severity of the most critical problem;<br>- the highest status of a child service in problem state.<br><br>If the service is in OK state, `status` is equal to -1.                                                                                                                                                                                                               | | description                 | string                                              | Description of the service.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | | uuid                        | string                                              | Universal unique identifier. For update operations this field is *readonly*.                                                                                                                                                                                                                                                                                                                                                                                                                                                  | | created_at                  | integer                                             | Unix timestamp when service was created.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | | readonly                    | boolean                                             | *(readonly)* Access to the service.<br><br>Possible values:<br>0 - Read-write;<br>1 - Read-only.                                                                                                                                                                                                                                                                                                                                                                                                                              |  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 服务  服务对象有如下属性。  | 属性 | [类型](/manual/api/reference_commentary#数据_类型) | 描述 | |----|----|-----| | serviceid | string  | *(只读)* 服务ID。 | | **algorithm**<br>(必需) | integer | 状态计算规则。仅用于子服务存在时。<br><br>可能的值：<br>0 - 设置状态为正常;<br>1 - 最严重的，如果所有子服务存在问题；<br>2 - 子服务中最严重者。| | **name**<br>(required)  | string | 服务名称。| | **sortorder**<br>(必需) | integer | 用于排序的服务位置。<br><br>可能的值： 0-999.| | weight | integer | 服务权重。<br><br>可能的值： 0-1000000.<br><br>Default: 0.| | propagation\_rule | integer | 状态传播规则。必须与`propagation_value`一起设置。<br><br>可能的值：<br>0 - *(默认)* 原始传播服务状态；<br>1 - 按照给定的`propagation_value` (按照1到5的严重性)增加传播状态;<br>2 - 按照给定的`propagation_value` (按照1到5的严重性)降低传播状态；<br>3 - 忽略服务 - 状态根本不会传播给父服务；<br>4 - 按照给定`propagation_value`设定固定服务状态。| | propagation\_value | integer | 状态传播值。必须和`propagation_rule`一起设置。<br><br>取值0和3的`propagation_rule`可能的值：0.<br><br>取值1和2的`propagation_rule`可能的值：1-5.<br><br>取值为4的`propagation_rule`可能的值：<br>-1 - 正常；<br>0 - 未分类；<br>1 - 信息；<br>2 - 警告;<br>3 - 一般；<br>4 - 严重；<br>5 - 灾难。| | status | integer | *(只读)* 服务是正常或问题状态。<br><br>如果服务处于问题状态，`status`为以下其中一种:<br>- 最紧急问题的严重性；<br>- 处于问题状子服务的最高状态。<br><br>如果服务处于正常状态，`status`等于-1。| | description | string | 服务描述。| | uuid| string | 通用唯一标识符。对更新操作，该字段是 *只读*。| | readonly| boolean | *(只读)* 服务的访问权限。<br><br>可能的值：<br>0 - 读写；<br>1 - 只读。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Service  This class is designed to work with IT infrastructure/business services.  Object references:\  -   [Service](/manual/api/reference/service/object#service) -   [Status rule](/manual/api/reference/service/object#status_rule) -   [Service tag](/manual/api/reference/service/object#service_tag) -   [Service alarm](/manual/api/reference/service/object#service_alarm) -   [Problem tag](/manual/api/reference/service/object#problem_tag)  Available methods:\  -   [service.create](/manual/api/reference/service/create) - creating     new services -   [service.delete](/manual/api/reference/service/delete) - deleting     services -   [service.get](/manual/api/reference/service/get) - retrieving     services -   [service.update](/manual/api/reference/service/update) - updating     services
zh-cn	# 服务 此类为使用IT设施/业务服务而设计。 参考对象:\  -   [服务](/manual/api/reference/service/object#服务) -   [状态规则](/manual/api/reference/service/object#状态规则) -   [服务标签](/manual/api/reference/service/object#服务标签) -   [服务告警](/manual/api/reference/service/object#服务告警) -   [问题标记](/manual/api/reference/service/object#问题标记)  可用办法:\  -   [service.create](/manual/api/reference/service/create) - 创建新服务 -   [service.delete](/manual/api/reference/service/delete) - 删除服务 -   [service.get](/manual/api/reference/service/get) - 检索服务 -   [service.update](/manual/api/reference/service/update) - 更新服务

en-us	# Service  This class is designed to work with IT infrastructure/business services.  Object references:\  -   [Service](/manual/api/reference/service/object#service) -   [Status rule](/manual/api/reference/service/object#status_rule) -   [Service tag](/manual/api/reference/service/object#service_tag) -   [Service time](/manual/api/reference/service/object#service_time) -   [Service alarm](/manual/api/reference/service/object#service_alarm) -   [Problem tag](/manual/api/reference/service/object#problem_tag)  Available methods:\  -   [service.create](/manual/api/reference/service/create) - creating     new services -   [service.delete](/manual/api/reference/service/delete) - deleting     services -   [service.get](/manual/api/reference/service/get) - retrieving     services -   [service.getsla](/manual/api/reference/service/getsla) - retrieving     availability information about services -   [service.update](/manual/api/reference/service/update) - updating     services  
zh-cn	# 服务  This class is designed to work with services. 该类用于配合服务使用。  Object references 对象引用:\  -   [Service](/zh/manual/api/reference/service/object#service) -   [Service time](/zh/manual/api/reference/service/object#service_time) -   [Service     dependency](/zh/manual/api/reference/service/object#service_dependency) -   [Service     alarm](/zh/manual/api/reference/service/object#service_alarm)  Available methods 可用方法:\  -   [service.adddependencies](/zh/manual/api/reference/service/adddependencies) -     adding dependencies between IT services 增加IT服务之间的依赖关系 -   [service.addtimes](/zh/manual/api/reference/service/addtimes) -     adding service times 增加服务时间 -   [service.create](/zh/manual/api/reference/service/create) - creating     new IT services 创建新的IT服务 -   [service.delete](/zh/manual/api/reference/service/delete) - deleting     IT services 删除IT服务 -   [service.deletedependencies](/zh/manual/api/reference/service/deletedependencies) -     deleting dependencies between IT services 删除IT服务之间的依赖关系 -   [service.deletetimes](/zh/manual/api/reference/service/deletetimes) -     deleting service times 删除服务时间 -   [service.get](/zh/manual/api/reference/service/get) - retrieving IT     services 检索IT服务 -   [service.getsla](/zh/manual/api/reference/service/getsla) -     retrieving availability information about IT services     检索有关IT服务的可用性信息 -   [service.update](/zh/manual/api/reference/service/update) - updating     IT services 更新IT服务  

en-us	### Service time  The service time object defines periods, when an service is scheduled to be up or down. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**ts\_from**<br>(required)|integer|Time when the service time comes into effect.<br><br>For onetime downtimes `ts_from` must be set as a Unix timestamp, for other types - as a specific time in a week, in seconds, for example, 90000 for Mon, 1:00 AM.| |**ts\_to**<br>(required)|integer|Time when the service time ends.<br><br>For onetime uptimes `ts_to` must be set as a Unix timestamp, for other types - as a specific time in a week, in seconds, for example, 90000 for Mon, 1:00 AM.| |**type**<br>(required)|integer|Service time type.<br><br>Possible values:<br>0 - planned uptime, repeated every week;<br>1 - planned downtime, repeated every week;<br>2 - one-time downtime.| |note|string|Additional information about the service time.|  
zh-cn	### Service alarm 服务告警  ::: noteclassic Service alrams cannot be directly created, updated or deleted via the Zabbix API.不能通过Zabbix API直接创建，更新或删除服务告警。 :::  The service alarm objects represents an service's state change. It has the following properties. 服务告警对象代表服务的状态变化，它具有以下属性。  |Property 属性    T|pe 类型          Des|ription 说明| |--------------------|----------------------|--------------| |servicealarmid|string 字符串      ID|of the service alarm. 服务告警的ID。| |serviceid|string 字符串      ID|of the service. 服务的ID。| |clock|timestamp 时间戳   Ti|e when the service state change has happened. 服务状态发生变化的时间。| |value|integer 整数型     St|tus of the service. 服务的状态。<br><br>Refer the the [service status property](object#service) for a list of possible values. 请参阅[service status property](object#service)以获取许可值列表。|  

en-us	 ### Service tree  The next step is to build the service tree. In this example, the infrastructure is very basic and consists of three services: *Zabbix cluster* (parent) and two child services *Zabbix server node 1* and *Zabbix server node 2*.        Zabbix cluster     |     |- Zabbix server node 1     |- Zabbix server node 2  At the Services page, turn on *Edit* mode and press Create service:  ![](../../../assets/en/manual/config/service_mode.png){class="nozoom"}  In the service configuration window, enter name *Zabbix cluster* and mark the checkbox *Advanced configuration*.   ![](../../../assets/en/manual/config/service_cluster.png){width=600}  Configure additional rule:  ![](../../../assets/en/manual/config/service_add_rule.png){width=600}  Zabbix cluster will have two child services - one for each of the HA nodes. If both HA nodes have problems of at least *Warning* status,  parent service status should be set to *Disaster*. To achieve this, additional rule should be configured as:  - Set status to: Disaster - Condition: If at least `N` child services have `Status` status or above - N: 2 - Status: Warning  Switch to the *Tags* tab and add a tag `Zabbix:server`. This tag will be used later for service actions and SLA reports.  ![](../../../assets/en/manual/config/service_cluster1.png){width=600}  Save the new service. 
zh-cn	 ### 服务树  下一步是建立服务树。在此示例中，只包含基础的设置以及三个服务： *Zabbix cluster* (父) 和两个子服务 *Zabbix server node 1* 和*Zabbix server node 2*.        Zabbix cluster     |     |- Zabbix server node 1     |- Zabbix server node 2  在服务页面，打开 *编辑* 模式并点击创建服务：  ![](../../../assets/en/manual/config/service_mode.png){class="nozoom"}  在服务配置窗口中，输入名称*Zabbix cluster* 并选取检查框*高级配置*。  ![](../../../assets/en/manual/config/service_cluster.png){width=600}  配置额外规则：  ![](../../../assets/en/manual/config/service_add_rule.png){width=600}  Zabbix集群需要两个子服务 - 用于各自的HA节点。如果两个HA节点均产生至少为*警告* 级别的告警信息，父服务的状态将设置为*灾难*。要实现上述需求，需要配置如下的额外规则：  - 设置状态为：灾难 - 条件：如果至少 `N` 个子服务有`状态` 状态或以上 - N: 2 - 状态: 警告  切换到*标签* 界面并添加标签 `Zabbix:server`。此标签后续会用于服务动作和SLA报告。  ![](../../../assets/en/manual/config/service_cluster1.png){width=600}  保存新建的服务。

en-us	# service.update
zh-cn	 # service.update

en-us	#### settings  Changes:\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `settings.get`, `settings.update`: added support of parameter `auditlog_enabled`.\ [ZBXNEXT-6945](https://support.zabbix.com/browse/ZBXNEXT-6945) `settings.get`, `settings.update`: added support of parameters `geomaps_tile_provider`, `geomaps_tile_url`, `geomaps_max_zoom` and `geomaps_attribution`.\
zh-cn	 #### 设置  变更：\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `settings.get`，`settings.update`：添加对参数`auditlog_enabled`的支持。\ [ZBXNEXT-6945](https://support.zabbix.com/browse/ZBXNEXT-6945) `settings.get`，`settings.update`：添加对参数`geomaps_tile_provider`，`geomaps_tile_url`，`geomaps_max_zoom`和`geomaps_attribution`的支持。\

en-us	#### settings  Changes:\ [ZBXNEXT-6945](https://support.zabbix.com/browse/ZBXNEXT-6945) `settings.get`, `settings.update`: added support of parameters `geomaps_tile_provider`, `geomaps_tile_url`, `geomaps_max_zoom` and `geomaps_attribution`.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `settings.get`, `settings.update`: added support of parameter `auditlog_enabled`.\
zh-cn	 #### 设置  变更：\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `settings.get`，`settings.update`：添加对参数`auditlog_enabled`的支持。\ [ZBXNEXT-6945](https://support.zabbix.com/browse/ZBXNEXT-6945) `settings.get`，`settings.update`：添加对参数`geomaps_tile_provider`，`geomaps_tile_url`，`geomaps_max_zoom`和`geomaps_attribution`的支持。\

en-us	#### Settings  Entering a name for Zabbix server is optional, however, if submitted, it will be displayed in the menu bar and page titles.  Set the default [time zone](/manual/web_interface/time_zone#overview) and theme for the frontend.  ![](../../../assets/en/manual/installation/install_4.png){width="550"}
zh-cn	#### 配置  对Zabbix服务器进行命名的配置为可选配置。该配置一旦提交，设定的服务器名称就会显示在网页的菜单栏和页面标题中。  配置默认[time zone](/manual/web_interface/time_zone#overview)和前端的主题。  ![](../../../assets/en/manual/installation/install_4.png){width="550"}

en-us	#### Settings  Entering a name for Zabbix server is optional, however, if submitted, it will be displayed in the menu bar and page titles.  Set the default [time zone](/manual/web_interface/time_zone#overview) and theme for the frontend.  ![](../../../assets/en/manual/installation/install_4.png){width="550"}  
zh-cn	#### 配置  对Zabbix服务器进行命名的配置为可选配置。该配置一旦提交，设定的服务器名称就会显示在网页的菜单栏和页面标题中。  配置默认[time zone](/manual/web_interface/time_zone#overview)和前端的主题。  ![](../../../assets/en/manual/installation/install_4.png){width="550"}

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

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

en-us	# Settings  This class is designed to work with common administration settings.  Object references:\  -   [Settings](/manual/api/reference/settings/object#settings)  Available methods:\  -   [settings.get](/manual/api/reference/settings/get) - retrieve     settings -   [settings.update](/manual/api/reference/settings/update) - update     settings
zh-cn	 # 设置  此类为进行常用管理设置而设计。  参考对象:\  -   [设置](/manual/api/reference/settings/object#设置)  可用办法\  -   [settings.get](/manual/api/reference/settings/get) - 检索设置 -   [settings.update](/manual/api/reference/settings/update) - 更新设置

en-us	# settings.update
zh-cn	 # settings.update

en-us	#### Setting the maximum for the Y scale  Set the maximum of the Y scale to a fixed value of 100.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graph.update",     "params": {         "graphid": "439",         "ymax_type": 1,         "yaxismax": 100     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "439"         ]     },     "id": 1 } ```
zh-cn	#### 设置 Y 刻度的最大值  将Y刻度的最大值设置为固定值100。  请求：  ```json {     "jsonrpc": "2.0",     "method": "graph.update",     "params": {         "graphid": "439",         "ymax_type": 1,         "yaxismax": 100     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "439"         ]     },     "id": 1 } ```

en-us	#### Setting the parent for a service  Make service with ID "3" to be the parent for service with ID "5".  Request:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "serviceid": "5",         "parents": [             {                 "serviceid": "3"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 设置服务的父服务  使ID为“3”的服务成为ID为“5”的服务的父服务。   请求：  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "serviceid": "5",         "parents": [             {                 "serviceid": "3"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "5"         ]     },     "id": 1 } ```

en-us	#### - Setting up SNMP trap monitoring
zh-cn	#### - 设置SNMP trap监控

en-us	#### Setting up SSL for Zabbix frontend  On RHEL/Centos, install mod\_ssl package:      yum install mod_ssl  Create directory for SSL keys:      mkdir -p /etc/httpd/ssl/private     chmod 700 /etc/httpd/ssl/private  Create SSL certificate:      openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/httpd/ssl/private/apache-selfsigned.key -out /etc/httpd/ssl/apache-selfsigned.crt  Fill out the prompts appropriately. The most important line is the one that requests the Common Name. You need to enter the domain name that you want to be associated with your server. You can enter the public IP address instead if you do not have a domain name. We will use *example.com* in this article.      Country Name (2 letter code) [XX]:     State or Province Name (full name) []:     Locality Name (eg, city) [Default City]:     Organization Name (eg, company) [Default Company Ltd]:     Organizational Unit Name (eg, section) []:     Common Name (eg, your name or your server's hostname) []:example.com     Email Address []:  Edit Apache SSL configuration:      /etc/httpd/conf.d/ssl.conf      DocumentRoot "/usr/share/zabbix"     ServerName example.com:443     SSLCertificateFile /etc/httpd/ssl/apache-selfsigned.crt     SSLCertificateKeyFile /etc/httpd/ssl/private/apache-selfsigned.key  Restart the Apache service to apply the changes:      systemctl restart httpd.service
zh-cn	#### 为 Zabbix 前端设置 SSL  在 RHEL/Centos 操作系统上，安装 mod\_ssl 包：      yum install mod_ssl  为 SSL keys 创建目录：      mkdir -p /etc/httpd/ssl/private     chmod 700 /etc/httpd/ssl/private  创建 SSL 证书：      openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/httpd/ssl/private/apache-selfsigned.key -out /etc/httpd/ssl/apache-selfsigned.crt  请用户根据需求适当填写下列提示内容。最重要的参数是请求 Common Name 参数。 您需要输入要与服务器关联的域名。 如果您没有域名，则可以输入公共IP地址。 下面将使用 *example.com*。      Country Name (两个字母) [XX]:     State or Province Name (全名) []:     Locality Name (eg, city) [默认的城市]:     Organization Name (eg, company) [默认的公司名]:     Organizational Unit Name (eg, section) []:     Common Name (eg, your name or your server's hostname) []:example.com     Email Address []:  编辑 Apache SSL 配置：      /etc/httpd/conf.d/ssl.conf      DocumentRoot "/usr/share/zabbix"     ServerName example.com:443     SSLCertificateFile /etc/httpd/ssl/apache-selfsigned.crt     SSLCertificateKeyFile /etc/httpd/ssl/private/apache-selfsigned.key  重启 Apache 服务使以上修改的配置生效：      systemctl restart httpd.service

en-us	#### Setting up the identity provider  In order to work with Zabbix, a SAML identity provider ([onelogin.com](https://onelogin.com), [auth0.com](https://auth0.com), [okta.com](https://okta.com), etc.) needs to be configured in the following way:  -   *Assertion Consumer URL* should be set to     `<path_to_zabbix_ui>/index_sso.php?acs` -   *Single Logout URL* should be set to     `<path_to_zabbix_ui>/index_sso.php?sls`  `<path_to_zabbix_ui>` examples: %% <https://example.com/zabbix/ui>, <http://another.example.com/zabbix>, <http://><any\_public\_ip\_address>/zabbix %%
zh-cn	#### 设置身份提供者  为了与 Zabbix 合作，SAML 身份提供商 ([onelogin.com](https://onelogin.com)、[auth0.com](https://auth0.com)、[okta.com](https: //okta.com) 等) 需要按如下方式配置：  - · *Assertion Consumer URL* 应该设置为   · `<path_to_zabbix_ui>/index_sso.php?acs` - · *Single Logout URL* 应设置为   · `<path_to_zabbix_ui>/index_sso.php?sls`  `<path_to_zabbix_ui>` 示例：%% <https://example.com/zabbix/ui>, <http://another.example.com/zabbix>, <http://><any\_public\_ip\_address>/zabbix %%

en-us	#### Setting up Zabbix  ::: noteimportant It is required to install php-openssl if you want to use SAML authentication in the frontend. :::  To use SAML authentication Zabbix should be configured in the following way:  1\. Private key and certificate should be stored in the *ui/conf/certs*/, unless custom paths are provided in [zabbix.conf.php](authentication#advanced_settings).  By default, Zabbix will look in the following locations:  -   ui/conf/certs/sp.key - SP private key file -   ui/conf/certs/sp.crt - SP cert file -   ui/conf/certs/idp.crt - IDP cert file  2\. All of the most important settings can be configured in the Zabbix frontend. However, it is possible to specify additional settings in the [configuration file](authentication#advanced_settings).  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth_saml.png)  Configuration parameters, available in the Zabbix frontend:  |Parameter|Description| |---------|-----------| |*Enable SAML authentication*|Mark the checkbox to enable SAML authentication.| |*IDP entity ID*|The unique identifier of SAML identity provider.| |*SSO service URL*|The URL users will be redirected to when logging in.| |*SLO Service URL*|The URL users will be redirected to when logging out. If left empty, the SLO service will not be used.| |// Username attribute//|SAML attribute to be used as a username when logging into Zabbix.<br>List of supported values is determined by the identity provider.<br><br>Examples:<br>uid<br>userprincipalname<br>samaccountname<br>username<br>userusername<br><urn:oid:0.9.2342.19200300.100.1.1><br><urn:oid:1.3.6.1.4.1.5923.1.1.1.13><br><urn:oid:0.9.2342.19200300.100.1.44>| |*SP entity ID*|The unique identifier of SAML service provider.| |*SP name ID format*|Defines which name identifier format should be used.<br><br>Examples:<br><urn:oasis:names:tc:SAML:2.0:nameid-format:persistent><br><urn:oasis:names:tc:SAML:2.0:nameid-format:transient><br><urn:oasis:names:tc:SAML:2.0:nameid-format:kerberos><br><urn:oasis:names:tc:SAML:2.0:nameid-format:entity>| |*Sign*|Mark the checkboxes to select entities for which SAML signature should be enabled:<br>*Messages*<br>*Assertions*<br>*AuthN requests*<br>*Logout requests*<br>*Logout responses*| |*Encrypt*|Mark the checkboxes to select entities for which SAML encryption should be enabled:<br>*Assertions*<br>*Name ID*| |*Case-sensitive login*|Mark the checkbox to enable case-sensitive login (disabled by default) for usernames.<br>E.g. disable case-sensitive login and log in with, for example, 'ADMIN' user even if the Zabbix user is 'Admin'.<br>*Note* that with case-sensitive login disabled the login will be denied if multiple users exist in Zabbix database with similar usernames (e.g. Admin, admin).|
zh-cn	#### 设置 Zabbix  ::: noteimportant 如果要在前端使用 SAML 身份验证，则需要安装 php-openssl。 :::  要使用 SAML 身份验证，Zabbix 应按以下方式配置：  1\. 私钥和证书应存储在 *ui/conf/certs*/ 中，除非 [zabbix.conf.php](authentication#advanced_settings) 中提供了自定义路径。  默认情况下，Zabbix 将在以下位置查找：  - · ui/conf/certs/sp.key - SP私钥文件 - · ui/conf/certs/sp.crt - SP 证书文件 - · ui/conf/certs/idp.crt - IDP 证书文件  2\. 所有最重要的设置都可以在 Zabbix 前端进行配置。但是，可以在 [配置文件](authentication#advanced_settings) 中指定其他设置。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth_saml.png)  配置参数，在 Zabbix 前端可用：  |参数|说明| |---------|------------| |*启用 SAML 身份验证*|选中复选框以启用 SAML 身份验证。| |*IDP 实体 ID*|SAML 身份提供者的唯一标识符。| |*SSO 服务 URL*|用户登录时将被重定向到的 URL。| |*SLO 服务 URL*|用户注销时将被重定向到的 URL。如果留空，则不会使用 SLO 服务。| |// 用户名属性//|登录 Zabbix 时用作用户名的 SAML 属性。<br>支持的值列表由身份提供者确定。<br><br>示例：<br>uid<br>用户主体名<br>samaccountname<br>用户名<br>用户用户名<br><urn:oid:0.9.2342.19200300.100.1.1><br><urn:oid:1.3.6.1.4.1.5923.1.1.1.13>< br><urn:oid:0.9.2342.19200300.100.1.44>| |*SP 实体 ID*|SAML 服务提供者的唯一标识符。| |*SP 名称 ID 格式*|定义应使用的名称标识符格式。<br><br>示例：<br><urn:oasis:names:tc:SAML:2.0:nameid-format:persistent><br> <urn:oasis:names:tc:SAML:2.0:nameid-format:transient><br><urn:oasis:names:tc:SAML:2.0:nameid-format:kerberos><br><urn:oasis:names :tc:SAML:2.0:nameid-format:entity>| |*Sign*|标记复选框以选择应为其启用 SAML 签名的实体：<br>*消息*<br>*断言*<br>*AuthN 请求*<br>*注销请求*<br>*注销回复*| |*加密*|标记复选框以选择应启用 SAML 加密的实体：<br>*断言*<br>*名称 ID*| |*区分大小写的登录*|标记复选框以启用用户名区分大小写的登录（默认禁用）。<br>例如禁用区分大小写的登录并使用例如“ADMIN”用户登录，即使 Zabbix 用户是“Admin”。<br>*注意*禁用区分大小写登录的情况下，如果存在多个用户，登录将被拒绝具有相似用户名的 Zabbix 数据库（例如 Admin、admin）。|

en-us	#### Setup examples using different SNMP protocol versions  This example uses snmptrapd and a Bash receiver script to pass traps to Zabbix server.  Setup:  1.  Configure Zabbix to start SNMP trapper and     set the trap file. Add to `zabbix_server.conf`:      StartSNMPTrapper=1     SNMPTrapperFile=/tmp/my_zabbix_traps.tmp  2.  Download the Bash script to `/usr/sbin/zabbix_trap_handler.sh`:      curl -o /usr/sbin/zabbix_trap_handler.sh https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh  If necessary, adjust the ZABBIX_TRAPS_FILE variable in the script. To use the default value, create the parent directory first:      mkdir -p /var/lib/zabbix/snmptraps  3. Add the following to `snmtrapd.conf` (refer to working [example](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/etc/snmp/snmptrapd.conf))      traphandle default /bin/bash /usr/sbin/zabbix_trap_handler.sh  4.  Create an SNMP item TEST:\      Host SNMP interface IP: 127.0.0.1     Key: `snmptrap["linkup"]`     Log time format: yyyyMMdd.hhmmss  5.  Next we will configure `snmptrapd` for our chosen SNMP protocol version and     send test traps using the `snmptrap` utility.  ##### SNMPv1, SNMPv2  SNMPv1 and SNMPv2 protocols rely on "community string" authentication. In the example below we will use "secret" as community string. It must be set to the same value on SNMP trap senders.  Please note that while still widely used in production environments, SNMPv2 doesn't offer any encryption and real sender authentication. The data is sent as plain text and therefore  these protocol versions should only be used in secure environments such as private network  and should never be used over any public or third-party network.  SNMP version 1 isn't really used these days since it doesn't support 64-bit counters and is considered a legacy protocol.  To enable accepting SNMPv1 or SNMPv2 traps you should add the following line to `snmptrapd.conf`. Replace "secret" with the SNMP community string configured on SNMP trap senders:      authCommunity log,execute,net secret  Next we can send a test trap using `snmptrap`. We will use the common "link up" OID in this example:      snmptrap -v 2c -c secret localhost 0 linkUp.0  ##### SNMPv3  SNMPv3 addresses SNMPv1/v2 security issues and provides authentication and encryption. You can use the MD5 or multiple SHA authentication methods and DES/multiple AES as cipher.  To enable accepting SNMPv3 add the following line to `snmptrapd.conf`:      createUser -e 0x8000000001020304 traptest SHA mypassword AES     authuser log,execute traptest  :::noteimportant Please note the "execute" keyword that allows to execute scripts for this user security model. :::      # snmptrap -v 3 -n "" -a SHA -A mypassword -x AES -X mypassword -l authPriv -u traptest -e 0x8000000001020304 localhost 0 linkUp.0  ::: notewarning If you wish to use strong encryption methods such as AES192 or AES256, please use net-snmp starting with version 5.8. You might have to recompile it with `configure` option: `--enable-blumenthal-aes`. Older versions of net-snmp do not support AES192/AES256. See also: http://www.net-snmp.org/wiki/index.php/Strong_Authentication_or_Encryption :::  ##### Verification   In both examples you will see similar lines in your `/var/lib/zabbix/snmptraps/snmptraps.log`:      20220805.102235 ZBXTRAP 127.0.0.1     UDP: [127.0.0.1]:35736->[127.0.0.1]:162     DISMAN-EVENT-MIB::sysUpTimeInstance = 0:0:00:00.00     SNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0  The item value in Zabbix will be:      2022-08-05 10:54:43 2022-08-05 10:54:41       20220805.105441 UDP: [127.0.0.1]:44262->[127.0.0.1]:162     DISMAN-EVENT-MIB::sysUpTimeInstance = 0:0:00:00.00     SNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0
zh-cn	#### 使用不同 SNMP 协议版本的设置示例  此示例使用 snmptrapd 和 Bash 接收器脚本将陷阱传递到 Zabbix 服务器。  设置：  1.  配置Zabbix启动SNMP trapper并设置trap文件。 添加到 `zabbix_server.conf`：     StartSNMPTrapper=1    SNMPTrapperFile=/tmp/my_zabbix_traps.tmp  2.  下载Bash脚本到`/usr/sbin/zabbix_trap_handler.sh`：     curl -o /usr/sbin/zabbix_trap_handler.sh https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh  如有必要，调整脚本中的 ZABBIX_TRAPS_FILE 变量。 要使用默认值，首先创建父目录：     mkdir -p /var/lib/zabbix/snmptraps  3.将以下内容添加到`snmtrapd.conf`（参考工作[示例]（https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/etc/snmp/snmptrapd .conf））     traphandle default /bin/bash /usr/sbin/zabbix_trap_handler.sh  4.  创建一个 SNMP 测试监控项:    Host SNMP interface IP: 127.0.0.1   Key: `snmptrap["linkup"]`   Log time format: yyyyMMdd.hhmmss  5.  接下来我们将为我们选择的 SNMP 协议版本配置 `snmptrapd`，并使用 `snmptrap` 实用程序发送测试陷阱。  ##### SNMPv1，SNMPv2  SNMPv1 和 SNMPv2 协议依赖于“团体名”身份验证。 在下面的示例中，我们将使用“secret”作为团体名。 它必须在 SNMP 陷阱发送器上设置为相同的值。  请注意，虽然 SNMPv2 仍在生产环境中广泛使用，但它不提供任何加密和真实发件人身份验证。 数据以纯文本形式发送，因此这些协议版本只能在安全环境（例如专用网络）中使用，绝不能在任何公共或第三方网络上使用。  SNMPv1 目前并没有真正被使用，因为它不支持 64 位计数器并且被认为是一个遗留协议。  要启用接受 SNMPv1 或 SNMPv2 陷阱，您应该将以下行添加到 `snmptrapd.conf`。将“secret”替换为在 SNMP 陷阱发件人上配置的 SNMP 团体字：     authCommunity log,execute,net secret  接下来我们可以使用 snmptrap 发送测试陷阱。 我们将在此示例中使用通用的“link up”OID：     snmptrap -v 2c -c secret localhost 0 linkUp.0  ##### SNMPv3  SNMPv3 解决了 SNMPv1/v2 安全问题并提供身份验证和加密。您可以使用 SHA 或 MD5 作为身份验证方法，使用 AES 或 DES 作为密码。  要启用接受 SNMPv3，请将以下行添加到 `snmptrapd.conf`：     createUser -e 0x8000000001020304 traptest SHA mypassword AES    authuser log,execute traptest  :::noteimportant 请注意允许为此用户安全模型执行脚本的“执行”关键字。 :::     # snmptrap -v 3 -n "" -a SHA -A mypassword -x AES -X mypassword -l authPriv -u traptest -e 0x8000000001020304 localhost 0 linkUp.0  ::: notewarning 如果您希望使用 AES192 或 AES256 等强加密方法，从 5.8 版本开始请使用 net-snmp。 您可能必须使用“configure”选项重新编译它：“--enable-blumenthal-aes”。旧版本的 net-snmp 不支持 AES192/AES256。另请参阅：http://www.net-snmp.org/wiki/index.php/Strong_Authentication_or_Encryption :::  ##### 确认  在这两个示例中，您将在“/var/lib/zabbix/snmptraps/snmptraps.log”中看到类似的行：     20220805.102235 ZBXTRAP 127.0.0.1    UDP: [127.0.0.1]:35736->[127.0.0.1]:162    DISMAN-EVENT-MIB::sysUpTimeInstance = 0:0:00:00.00    SNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0  Zabbix 中的监控项值将是：     2022-08-05 10:54:43→2022-08-05 10:54:41→    20220805.105441 UDP: [127.0.0.1]:44262->[127.0.0.1]:162    DISMAN-EVENT-MIB::sysUpTimeInstance = 0:0:00:00.00    SNMPv2-MIB::snmpTrapOID.0 = IF-MIB::linkUp.0

en-us	# - Setup from sources  
zh-cn	# 1 使用源码安装

en-us	#### Setup wizard on SUSE with NGINX and php-fpm  Frontend setup wizard cannot save configuration file on SUSE with NGINX + php-fpm. This is caused by a setting in /usr/lib/systemd/system/php-fpm.service unit, which prevents Zabbix from writing to /etc. (introduced in [PHP 7.4](https://bugs.php.net/bug.php?id=72510)).  There are two workaround options available:  -   Set the     [ProtectSystem](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectSystem=)     option to 'true' instead of 'full' in the php-fpm systemd unit. -   Manually save /etc/zabbix/web/zabbix.conf.php file.
zh-cn	#### 使用 NGINX 和 php-fpm 在 SUSE 上设置向导  在 SUSE 上使用 NGINX + php-fpm，前端设置向导将无法保存配置文件。这是由 /usr/lib/systemd/system/php-fpm.service 单元中的设置引起的，该设置阻止 Zabbix 写入 /etc。 (在 [PHP 7.4 中引入](https://bugs.php.net/bug.php?id=72510)).。  有两种解决方法可供选择：  -   在 php-fpm systemd 单元中将 [ProtectSystem](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectSystem=) 选项设置为 'true' 而不是 'full'。 -   手动保存 /etc/zabbix/web/zabbix.conf.php 文件。

en-us	#### Sharing  The **Sharing** tab contains the map type as well as sharing options (user groups, users) for private maps:  ![](../../../../../assets/en/manual/config/visualization/map_config2.png)  |Parameter|Description| |---------|-----------| |*Type*|Select map type:<br>**Private** - map is visible only to selected user groups and users<br>**Public** - map is visible to all| |*List of user group shares*|Select user groups that the map is accessible to.<br>You may allow read-only or read-write access.| |*List of user shares*|Select users that the map is accessible to.<br>You may allow read-only or read-write access.|  When you click on *Add* to save this map, you have created an empty map with a name, dimensions, and certain preferences. Now you need to add some elements. For that, click on *Constructor* in the map list to open the editable area.
zh-cn	#### 分享  **分享**选项卡包含地图类型以及私有地图的分析享选项（用户组，用户）：  ![](../../../../../assets/en/manual/config/visualization/map_config2.png)  |参数|说明| |---------|------------| |*Type*|选择地图类型：<br>**Private** - 地图仅对选定的用户组和用户可见<br>**Public** - 地图对所有人可见| |*用户组共享列表*|选择地图可访问的用户组。<br>您可以允许只读或读写访问。| |*用户共享列表*|选择可以访问地图的用户。<br>您可以允许只读或读写访问。|  当您单击 *Add* 保存此地图时，您已创建了一个具有名称、尺寸和某些偏好的空地图。现在您需要添加一些元素。为此，请单击地图列表中的 *Constructor* 以打开可编辑区域。

en-us	##### Shell configuration form  This step should be performed only once for every host that will be monitored by SSH checks.  By using the following command the **public** key file can be installed on a remote host *10.10.10.10* so that then SSH checks can be performed with a *root* account:      # sudo -u zabbix ssh-copy-id root@10.10.10.10     The authenticity of host '10.10.10.10 (10.10.10.10)' can't be established.     RSA key fingerprint is 38:ba:f2:a4:b5:d9:8f:52:00:09:f7:1f:75:cc:0b:46.     Are you sure you want to continue connecting (yes/no)? yes     Warning: Permanently added '10.10.10.10' (RSA) to the list of known hosts.     root@10.10.10.10's password:      Now try logging into the machine, with "ssh 'root@10.10.10.10'", and check in:       .ssh/authorized_keys     to make sure we haven't added extra keys that you weren't expecting.  Now it's possible to check the SSH login using the default private key (*/home/zabbix/.ssh/id\_rsa*) for *zabbix* user account:      # sudo -u zabbix ssh root@10.10.10.10  If the login is successful, then the configuration part in the shell is finished and remote SSH session can be closed.
zh-cn	##### Shell 配置表单  对于每一个将被SSH监控的主机。这个步骤应该只执行一次。  通过下面的命令，**公钥**文件可以安装在远程主机*10.10.10.10*上，这样就可以使用*root*帐户执行SSH检查:      # sudo -u zabbix ssh-copy-id root@10.10.10.10     The authenticity of host '10.10.10.10 (10.10.10.10)' can't be established.     RSA key fingerprint is 38:ba:f2:a4:b5:d9:8f:52:00:09:f7:1f:75:cc:0b:46.     Are you sure you want to continue connecting (yes/no)? yes     Warning: Permanently added '10.10.10.10' (RSA) to the list of known hosts.     root@10.10.10.10's password:      Now try logging into the machine, with "ssh 'root@10.10.10.10'", and check in:       .ssh/authorized_keys     to make sure we haven't added extra keys that you weren't expecting.  现在*zabbix* 用户可以使用默认私钥(*/home/zabbix/.ssh/id\_rsa*) ，对目标主机进行SSH免密登录检查      # sudo -u zabbix ssh root@10.10.10.10  如果登录成功,表示shell中的配置部分已经完成，可以关闭远程SSH会话。

en-us	#### Simple checks  There is a bug in **fping** versions earlier than v3.10 that mishandles duplicate echo replay packets. This may cause unexpected results for `icmpping`, `icmppingloss`, `icmppingsec` items. It is recommended to use the latest version of **fping**. Please see [ZBX-11726](https://support.zabbix.com/browse/ZBX-11726) for more details.
zh-cn	#### 简单检查  在 v3.10 之前的  **fping**  版本中存在错误处理重复的回显重放数据包的 bug。可能会导致 `icmpping`, `icmppingloss`, `icmppingsec` 监控项故障。建议使用最新版本的 **fping**。参考 [ZBX-11726](https://support.zabbix.com/browse/ZBX-11726) 。

en-us	##### Simple data collection  Collect the content of *https://www.example.com/release\_notes*:  -   Create an item with type "Script".\ -   In the *Script* field, enter the following code:  ``` {.java} var request = new HttpRequest(); return request.get("https://www.example.com/release_notes"); ```
zh-cn	##### 简单的数据采集  从 *https://www.example.com/release\_notes* 页面收集内容:  - 创建一个监控项，类型选择”脚本“。 \ - 在*脚本*字段填写下面的代码：  ``` {.java} var request = new HttpRequest(); return request.get("https://www.example.com/release_notes"); ```

en-us	 #### Simple macros replaced by expression macros  A new expression syntax for triggers and calculated items was introduced in [Zabbix 5.4](https://www.zabbix.com/documentation/5.4/manual/introduction/whatsnew540). However, the old syntax still remained in use in simple macros. In the new version, the functionality of simple macros has been transferred to expression macros and the new expression syntax is used. See the comparison below for details of the change:  |In Zabbix 6.0|Before Zabbix 6.0| |-------------|-----------------| |`{?avg(/host/key,1h)}`<br><br>Example of an expression macro in the new version.|`{host:key.avg(1h)}`<br><br>Example of a simple macro in previous versions.|  The existing simple macros will be converted to expression macros during the upgrade. The scope of expression macros covers the same that was offered by simple macros. Thus, expression macros can be used in:  -   problem notifications and commands -   problem update notifications and commands -   map element labels -   map link labels -   map shape labels -   graph names  
zh-cn	### New functions  

en-us	 ##### Simple macros replaced by expression macros  A new expression syntax for triggers and calculated items was introduced in [Zabbix 5.4](https://www.zabbix.com/documentation/5.4/manual/introduction/whatsnew540). However, the old syntax still remained in use in simple macros. In the new version, the functionality of simple macros has been transferred to expression macros and the new expression syntax is used. See the comparison below for details of the change:  |In Zabbix 6.0|Before Zabbix 6.0| |-------------|-----------------| |`{?avg(/host/key,1h)}`<br><br>Example of an expression macro in the new version.|`{host:key.avg(1h)}`<br><br>Example of a simple macro in previous versions.|  The existing simple macros will be converted to expression macros during the upgrade. The scope of expression macros covers the same that was offered by simple macros. Thus, expression macros can be used in:  -   problem notifications and commands -   problem update notifications and commands -   map element labels -   map link labels -   map shape labels -   graph names
zh-cn	##### 由表达式宏替换的简单宏  [Zabbix 5.4](https://www.zabbix.com/documentation/5.4/manual/introduction/whatsnew540) 中引入了触发器和可计算监控项的新表达式语法。然而，旧的语法仍然在简单的宏中使用。在新版本中，简单宏的功能已转移到表达式宏中，并使用了新的表达式语法。有关更改的详细信息，请参见下面的比较：  |Zabbix 6.0|Zabbix 6.0 之前| |-------------|-----------------| |`{?avg(/host/key,1h)}`<br><br>新版本中的表达式宏示例。|`{host:key.avg(1h)}`<br><br>之前版本中的简单宏示例。|  现有的简单宏将在升级过程中转换为表达式宏。表达式宏的范围与简单宏提供的范围相同。因此，表达式宏可用于：  -   问题通知和命令 -   问题更新通知和命令 -   地图元素标签 -   地图链接标签 -   地图形状标签 -   图形名称

en-us	##### Simple macros replaced by expression macros  The functionality of simple macros has been [transferred](/manual/introduction/whatsnew600#simple_macros_replaced_by_expression_macros) to expression macros. The existing simple macros will be converted to expression macros during the upgrade. Macros that can not be converted without exceeding the length limit will not be converted with a warning printed in the log file.
zh-cn	##### 表达式宏取代简单宏  简单宏的功能已 [转移到表达式宏](/manual/introduction/whatsnew600#simple_macros_replaced_by_expression_macros)。现有的简单宏将在升级过程中转换为表达式宏。在不超过长度限制的情况下无法转换的宏将不会被转换，这会在日志中输出警告。

en-us	#### Size limits  There are size limits for PSK identity and value in Zabbix, in some cases a crypto library can have lower limit:  |Component|PSK identity max size|PSK value min size|PSK value max size| |---------|---------------------|------------------|------------------| |*Zabbix*|128 UTF-8 characters|128-bit (16-byte PSK, entered as 32 hexadecimal digits)|2048-bit (256-byte PSK, entered as 512 hexadecimal digits)| |*GnuTLS*|128 bytes (may include UTF-8 characters)|\-|2048-bit (256-byte PSK, entered as 512 hexadecimal digits)| |*OpenSSL 1.0.x, 1.1.0*|127 bytes (may include UTF-8 characters)|\-|2048-bit (256-byte PSK, entered as 512 hexadecimal digits)| |*OpenSSL 1.1.1*|127 bytes (may include UTF-8 characters)|\-|512-bit (64-byte PSK, entered as 128 hexadecimal digits)| |*OpenSSL 1.1.1a and later*|127 bytes (may include UTF-8 characters)|\-|2048-bit (256-byte PSK, entered as 512 hexadecimal digits)|  ::: noteimportant  Zabbix frontend allows configuring up to 128-character long PSK identity string and 2048-bit long PSK regardless of crypto libraries used.\ If some Zabbix components support lower limits, it is the user's responsibility to configure PSK identity and value with allowed length for these components.\ Exceeding length limits results in communication failures between Zabbix components.  :::  Before Zabbix server connects to agent using PSK, the server looks up the PSK identity and PSK value configured for that agent in database (actually in configuration cache). Upon receiving a connection the agent uses PSK identity and PSK value from its configuration file. If both parties have the same PSK identity string and PSK value the connection may succeed.  ::: noteimportant  Each PSK identity must be paired with only one value. It is the user's responsibility to ensure that there are no two PSKs with the same identity string but different values. Failing to do so may lead to unpredictable disruptions of communication between Zabbix components using PSKs with this PSK identity string.  :::
zh-cn	#### 尺寸限制  Zabbix中的PSK标识和值有大小限制，在某些情况下，加密库可以具有下限:  |组件|PSK标识最大尺寸|PSK值最小尺寸|PSK值最大尺寸| |---------|---------------------|------------------|------------------| |*Zabbix*|128个UTF-8字符|128位（16字节PSK，输入为32个十六进制数字）|2048位（256字节PSK，输入为512个十六进制数字）| |*GnuTLS*|128字节（可能包括UTF-8字符）|\-|2048位（256字节PSK，输入为512个十六进制数字）| |*OpenSSL 1.0.x, 1.1.0*|127 字节（可能包括 UTF-8 字符）|\-|2048 位（256 字节 PSK，输入为 512 个十六进制数字）| |*OpenSSL 1.1.1*|127 字节（可能包括 UTF-8 字符）|\-|512 位（64 字节 PSK，输入为 128 个十六进制数字）| |*OpenSSL 1.1.1a 及更高版本*|127 字节（可能包括 UTF-8 字符）|\-|2048 位（256 字节 PSK，输入为 512 个十六进制数字）|  ::: 注意   Zabbix 前端允许配置最多128 个字符长的 PSK 标识字符串和 2048 位长的 PSK，而不考虑使用哪种加密库。\ 如果某些Zabbix组件支持下限，则用户有责任为这些组件配置具有允许长度的PSK标识和值。\ 超过长度限制会导致Zabbix组件之间的通信故障。  :::  在Zabbix服务器使用PSK连接到代理之前，服务器会在数据库（实际上是在配置缓存中）中查找为该代理配置的PSK标识和PSK值。收到连接后，代理使用其配置文件中的PSK标识和PSK值。 如果双方具有相同的PSK标识字符串和PSK值，则连接可能会成功。  ::: 注意 用户有责任确保没有两个具有相同标识字符串但值不同的PSK。 否则，使用带有此PSK标识字符串的PSK的Zabbix组件之间的通信可能会出现不可预测的中断。 :::

en-us	#### sla Changes:\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) added new API `sla` with methods: `sla.create`, `sla.delete`, `sla.get`, `sla.getsli`, `sla.update`.\
zh-cn	#### 服务等级协议 变化：\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) 添加了新的 API `sla` 方法：`sla.create`、`sla.delete`、`sla.get`、` sla.getsli`、`sla.update`。\

en-us	#### Slack webhook (custom)  This webhook will forward notifications from Zabbix to a Slack channel.  ![](../../../../../../assets/en/manual/config/notifications/media/webhook_slack1.png)  ``` {.java} try {     var params = JSON.parse(value),         req = new HttpRequest(),         response;      if (params.HTTPProxy) {         req.setProxy(params.HTTPProxy);     }      req.addHeader('Content-Type: application/x-www-form-urlencoded');      Zabbix.log(4, '[ Slack webhook ] Webhook request with value=' + value);      response = req.post(params.hook_url, 'payload=' + encodeURIComponent(value));     Zabbix.log(4, '[ Slack webhook ] Responded with code: ' + req.Status() + '. Response: ' + response);      try {         response = JSON.parse(response);     }     catch (error) {         if (req.getStatus() < 200 || req.getStatus() >= 300) {             throw 'Request failed with status code ' + req.getStatus();         }         else {             throw 'Request success, but response parsing failed.';         }     }      if (req.getStatus() !== 200 || !response.ok || response.ok === 'false') {         throw response.error;     }      return 'OK'; } catch (error) {     Zabbix.log(3, '[ Slack webhook ] Sending failed. Error: ' + error);      throw 'Failed with error: ' + error; } ```
zh-cn	#### Slack webhook (自定义)  此webhook将把Zabbix的通知转发到Slack channel中。  ![](../../../../../../assets/en/manual/config/notifications/media/webhook_slack1.png)  ``` {.java} try {     var params = JSON.parse(value),         req = new HttpRequest(),         response;      if (params.HTTPProxy) {         req.setProxy(params.HTTPProxy);     }      req.addHeader('Content-Type: application/x-www-form-urlencoded');      Zabbix.log(4, '[ Slack webhook ] Webhook request with value=' + value);      response = req.post(params.hook_url, 'payload=' + encodeURIComponent(value));     Zabbix.log(4, '[ Slack webhook ] Responded with code: ' + req.Status() + '. Response: ' + response);      try {         response = JSON.parse(response);     }     catch (error) {         if (req.getStatus() < 200 || req.getStatus() >= 300) {             throw 'Request failed with status code ' + req.getStatus();         }         else {             throw 'Request success, but response parsing failed.';         }     }      if (req.getStatus() !== 200 || !response.ok || response.ok === 'false') {         throw response.error;     }      return 'OK'; } catch (error) {     Zabbix.log(3, '[ Jira webhook ] Sending failed. Error: ' + error);      throw 'Failed with error: ' + error; } ```

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

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

en-us	### SLA excluded downtime  The excluded downtime object defines periods where the connected service(s) are scheduled to be out of working order, without affecting SLI, e.g. undergoing planned maintenance.
zh-cn	### SLA 排除停机时间  排除的停机时间对象定义了计划连接的服务无法正常工作的时间段， 不影响 SLI，例如正在进行有计划的维护。

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

en-us	# sla.getsli
zh-cn	# sla.getsli

en-us	 ### SLA  In this example, expected Zabbix cluster performance is 100% excluding semi-annual one hour maintenance period.     First, you need to add a new service level agreement.   Go to the *Services->SLA* menu section and press Create SLA. Enter name *Zabbix cluster performance* and set the SLO to 100%.   The service Zabbix cluster has a service tag `Zabbix:server`. To use this SLA for measuring performance of Zabbix cluster, in the *Service tags* parameter, specify:  - Name: Zabbix - Operation: Equals - Value: server  ![](../../../assets/en/manual/config/service_sla.png){width=600}  In a real-life setup, you can also update desired reporting period, time zone and start date or change the schedule from 24/7 to custom. For this example, the default settings are sufficient.   Switch to the *Excluded downtimes* tab and add downtimes for scheduled maintenance periods to exclude these periods from SLA calculation. In the Excluded downtimes section press the Add link, enter downtime name, planned start time and duration.  ![](../../../assets/en/manual/config/service_sla1.png){width=600}  Press Add to save the new SLA.  Switch to the SLA reports section to view the SLA report for Zabbix cluster.    ![](../../../assets/en/manual/config/service_sla2.png){width=600}  The SLA info can also be checked in the *Services* section.   ![](../../../assets/en/manual/config/service_sla3.png){width=600}
zh-cn	 ### SLA  在此示例中，预期的Zabbix集群性能是100%，排除了每半年一次的一小时维护时间。  首先需要添加一个服务级别协议。  转到 *服务->SLA* 菜单点击创建SLA。输入名称 *Zabbix集群性能* 并 设置SLO为100%。  Zabbix集群有 `Zabbix:server`标签。要使用该SLA来测量Zabbix集群的性能，需要在*服务标签*的参数中指定：  - 名称：Zabbix - 操作：Equals - 值：server  ![](../../../assets/en/manual/config/service_sla.png){width=600}  在实际设置中，还可以更新所需的报告周期、时区和开始日期，或把时间表从24/7改为自定义。就这个例子来说，默认设置就够了。  切换到*例外停机时间* 面板并添加用于例行维护的停机时间，这样SLA就不会将这些时间段计算在内了。在例外停机时间面板总点击添加(Add)链接，输入停机时间名称、计划开始时间和持续时长。  ![](../../../assets/en/manual/config/service_sla1.png){width=600}  点击添加(Add)来保存新建的SLA。  切换到SLA报告界面查看关于Zabbix集群的SLA报告。  ![](../../../assets/en/manual/config/service_sla2.png){width=600}  还可以在*服务* 界面下查看SLA信息。  ![](../../../assets/en/manual/config/service_sla3.png){width=600}

en-us	# > SLA object  The following objects are directly related to the `sla` (Service Level Agreement) API.
zh-cn	# > SLA 对象  以下对象与 `sla`（服务级别协议）API 直接相关。

en-us	 ### SLA reports  How a service performs compared to an SLA is visible in the [SLA report](/manual/web_interface/frontend_sections/services/sla_report). SLA reports can be viewed:    - from the *SLA* section by clicking on the SLA report hyperlink;   - from the *Services* section by clicking on the SLA name in the info tab;   - in the Dashboard [widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/sla_report) *SLA report*.      Once an SLA is configured, the *Info* tab in the services section will also display some information about service performance. 
zh-cn	 ### SLA 报告  [SLA 报告](/manual/web_interface/frontend_sections/services/sla_report)中展示了服务的性能与SLA之间的对比数据。SLA报告可以通过以下方式查看：    - 点击*SLA*界面的SLA报告超链接;   - 点击 *服务* 界面下的信息(info)面板上的SLA名称;   - 在仪表盘(Dashboard)的[窗体小部件(widget)](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/sla_report) 中添加*SLA 报告*.      SLA配置好以后，服务界面下的*信息*面板同样会显示一些有关服务性能的信息。

en-us	### SLAs  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  A list of the configured SLAs is displayed. *Note* that only the SLAs  related to services accessible to the user will be displayed (as read-only,  unless *Manage SLA* is enabled for the user role).   Displayed data:  |Parameter|Description| |--|--------| |*Name*|The SLA name is displayed.<br>The name is a link to [SLA configuration](/manual/it_services/sla#configuration). | |*SLO*|The service level objective (SLO) is displayed. | |*Effective date*|The date of starting SLA calculation is displayed. | |*Reporting period*|The period used in the SLA report is displayed - *daily*, *weekly*, *monthly*, *quarterly*, or *annually*. | |*Time zone*|The SLA time zone is displayed. | |*Schedule*|The SLA schedule is displayed - 24x7 or custom. | |*SLA report*|Click on the link to see the SLA report for this SLA. | |*Status*|The SLA status is displayed - enabled or disabled. |
zh-cn	### SLAs  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  显示已配置SLA的列表。 *注意*只有与用户可访问的服务相关的SLA才会显示（只读，除非为用户角色启用了*管理SLA*）。   显示的数据：  |参数|描述| |---------|-----------| |*Name*|显示SLA名称。<br>该名称链接到[SLA配置](/manual/it_services/sla#configuration)。| |*SLO*|显示服务级别目标（SLO）。| |*Effective date*|显示开始SLA计算的日期。| |*Reporting period*|显示SLA报告中使用的期间 - *每天*，*每周*，*每月*，*每季*，或者*每年*。| |*Time zone*|显示SLA时区。| |*Schedule*|显示SLA计划 - 全天候或定制。| |*SLA report*|点击链接查看此SLA的SLA报告。| |*Status*|显示SLA状态 - 可用或者禁用。|

en-us	### SLA Schedule  The SLA schedule object defines periods where the connected service(s) are scheduled to be in working order. It has the following properties.
zh-cn	### SLA 时间表  SLA 计划对象定义了连接的服务计划处于工作状态的时间段。它具有以下属性。

en-us	### SLA service tag  The SLA service tag object links services to include in the calculations for the SLA. It has the following properties.
zh-cn	### SLA 服务标签  SLA 服务标签对象链接服务以包括在 SLA 的计算中。它具有以下属性。

en-us	### SLA  The SLA object has the following properties.  | Property                   | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                                                                                               | |----------------------------|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | slaid                      | string                                              | *(readonly)* ID of the SLA.                                                                                                                                                                                                               | | **name**<br>(required)     | string                                              | Name of the SLA.                                                                                                                                                                                                                          | | **period**<br>(required)   | integer                                             | Reporting period of the SLA.<br><br>Possible values:<br>0 - daily;<br>1 - weekly;<br>2 - monthly;<br>3 - quarterly;<br>4 - annually.                                                                                                      | | **slo**<br>(required)      | float                                               | Minimum acceptable Service Level Objective expressed as a percent. If the Service Level Indicator (SLI) drops lower, the SLA is considered to be in problem/unfulfilled state.<br><br>Possible values: 0-100 (up to 4 fractional digits). | | effective_date             | integer                                             | Effective date of the SLA.<br><br>Possible values: date timestamp in UTC.                                                                                                                                                                 | | **timezone**<br>(required) | string                                              | Reporting time zone, for example: `Europe/London`, `UTC`.<br><br>For the full list of supported time zones please refer to [PHP documentation](https://www.php.net/manual/en/timezones.php).                                              | | status                     | integer                                             | Status of the SLA.<br><br>Possible values:<br>0 - *(default)* disabled SLA;<br>1 - enabled SLA.                                                                                                                                           | | description                | string                                              | Description of the SLA.                                                                                                                                                                                                                   |  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### SLA  SLA 对象具有以下属性。  | 属性| [类型](/manual/api/reference_commentary#data_types) | Description | |----|----|----| | slaid | 字符串| *(只读)*SLA的ID | | **name**<br>(必填) | 字符串| SLA的名称 | | **period**<br>(必填) | 整型| SLA 的报告期。<br><br>可能的值：<br>0 - 每天；<br>1 - 每周；<br>2 - 每月；<br>3 - 每季度；<br>4 - 每年。| | **slo**<br>(必填)| 浮点数| 以百分比表示的最低可接受服务水平目标。如果服务水平指标 (SLI) 下降，则 SLA 被认为处于问题/未完成状态。<br><br>可能的值：0-100（最多4个小数位）。| | effective_date | 整型|SLA 的生效日期。<br><br>可能的值：UTC 日期时间戳。| | **timezone**<br>(必填) | 字符串|报告时区，例如：`Europe/London`、`UTC`。<br><br>有关支持的时区的完整列表，请参阅 [PHP 文档](https://www.php.net/manual/en/timezones.php)。| | status | 整型| SLA 的状态。<br><br>可能的值：<br>0 - *（默认）* 禁用 SLA；<br>1 - 启用 SLA。| | description| 字符串| SLA的描述 |  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

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

en-us	#### SLES 12  In SUSE Linux Enterprise Server 12 you need to add the Nginx repository, before installing Nginx:      zypper addrepo -G -t dnf -c 'http://nginx.org/packages/sles/12' nginx  You also need to configure `php-fpm`:      cp /etc/php5/fpm/php-fpm.conf{.default,}     sed -i 's/user = nobody/user = wwwrun/; s/group = nobody/group = www/' /etc/php5/fpm/php-fpm.conf
zh-cn	#### SLES 12  在SUSE Linux Enterprise Server 12中，您需要添加Nginx存储库，然后再安装Nginx:      zypper addrepo -G -t dnf -c 'http://nginx.org/packages/sles/12' nginx  您还需要配置 `php-fpm`:      cp /etc/php5/fpm/php-fpm.conf{.default,}     sed -i 's/user = nobody/user = wwwrun/; s/group = nobody/group = www/' /etc/php5/fpm/php-fpm.conf

en-us	#### SLES 15  In SUSE Linux Enterprise Server 15 you need to configure `php-fpm`:      cp /etc/php7/fpm/php-fpm.conf{.default,}     cp /etc/php7/fpm/php-fpm.d/www.conf{.default,}     sed -i 's/user = nobody/user = wwwrun/; s/group = nobody/group = www/' /etc/php7/fpm/php-fpm.d/www.conf
zh-cn	#### SLES 15  在 SUSE Linux Enterprise Server 15 中，您需要配置 `php-fpm`:      cp /etc/php7/fpm/php-fpm.conf{.default,}     cp /etc/php7/fpm/php-fpm.d/www.conf{.default,}     sed -i 's/user = nobody/user = wwwrun/; s/group = nobody/group = www/' /etc/php7/fpm/php-fpm.d/www.conf

en-us	#### SLI data  The SLI data returned for each reported period and service consists of:  | Property            | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                                                                                                                                                                                                                                                         | |---------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | uptime              | integer                                             | Amount of time service spent in an _OK_ state during scheduled uptime, less the excluded downtimes.                                                                                                                                                                                                                                                                                                 | | downtime            | integer                                             | Amount of time service spent in a _not OK_ state during scheduled uptime, less the excluded downtimes.                                                                                                                                                                                                                                                                                              | | sli                 | float                                               | SLI (per cent of total uptime), based on uptime and downtime.                                                                                                                                                                                                                                                                                                                                       | | error\_budget       | integer                                             | Error budget (in seconds), based on the SLI and the SLO.                                                                                                                                                                                                                                                                                                                                            | | excluded\_downtimes | array                                               | Array of excluded downtimes in this reporting period.<br><br>Each object will contain the following parameters:<br>- _name_ - Name of the excluded downtime.<br>- _period\_from_ - Starting date and time (inclusive) of the excluded downtime.<br>- _period\_to_ - Ending date and time (exclusive) of the excluded downtime.<br><br>Excluded downtimes are sorted by period_from field ascending. |
zh-cn	#### SLI 数据   每个报告期间和服务返回的 SLI 数据包括：  | 属性| [类型](/manual/api/reference_commentary#data_types) | 描述| |---------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | uptime              | 整型| 在计划的正常运行时间内服务处于 _OK_ 状态的时间量，减去排除的停机时间。                                                                                                                                                                                                                                                                                          | | downtime            | 整型|在计划的正常运行时间内服务处于_not OK_状态的时间量，减去排除的停机时间。                                                                                                                                                                                                                                                                                             | | sli                 | 浮点数| SLI（占总正常运行时间的百分比），基于正常运行时间和停机时间。                                                                                                                                                                                                                                                                                                                                  | | error\_budget       | 整型| 基于 SLI 和 SLO 的错误预算（以秒为单位）。                                                                                                                                                                                                                                                                                                                                      | | excluded\_downtimes | 数组|此报告期间排除的停机时间数组。<br><br>每个对象将包含以下参数：<br>- _name_ - 排除的停机时间的名称。<br>- _period\_from_ - 开始日期和时间（含）排除的停机时间。<br>- _period\_to_ - 排除的停机时间的结束日期和时间（不包括）。<br><br>排除的停机时间按 period_from 字段升序排序。|

en-us	#### Slideshow  It is possible to activate a slideshow in the dashboard:  -   `/zabbix.php?action=dashboard.view&slideshow=1` - activate slideshow
zh-cn	#### 幻灯片模式  可以在仪表板中激活幻灯片模式：  -   `/zabbix.php?action=dashboard.view&slideshow=1` - 激活幻灯片模式

en-us	 ### S.M.A.R.T.  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |smart.attribute.discovery|<|<|<| |Returns a list of S.M.A.R.T. device attributes.|JSON object| |The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#ID}, {\#ATTRNAME}, {\#THRESH}.<br>HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"} | |smart.disk.discovery|<|<|<| |Returns a list of S.M.A.R.T. devices.|JSON object| |The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#MODEL}, {\#SN}, {\#PATH}, {\#ATTRIBUTES}, {\#RAIDTYPE}.<br>HDD, SSD and NVME drive types are supported. If a drive does not belong to a RAID, {\#RAIDTYPE} will be empty. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"} | |smart.disk.get[<path>,<raid_type>]|<|<|<| |Returns all available properties of S.M.A.R.T. devices.|JSON object|**path** (since Zabbix 6.0.4) - disk path, the {\#PATH} macro may be used as a value<br>**raid_type** (since Zabbix 6.0.4) - RAID type, the {\#RAID} macro may be used as a value |HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID.<br>The data includes smartctl version and call arguments, and additional fields:<br>*disk\_name* - holds the name with the required add-ons for RAID discovery, e.g: {"disk\_name": "/dev/sda cciss,2"}<br>*disk\_type* - holds the disk type HDD, SSD, or NVME, e.g: {"disk\_type": "ssd"})<br>If no parameters are specified, the item will return information about all disks. |
zh-cn	### S.M.A.R.T.  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |smart.attribute.discovery|<|<|<| |返回 S.M.A.R.T. 设备属性列表.|JSON 对象| |将返回以下宏以及对应的值: {\#NAME}, {\#DISKTYPE}, {\#ID}, {\#ATTRNAME}, {\#THRESH}.<br>支持 HDD, SSD 和 NVME 设备类型. 设备可以单独或组合在一个RAID中. {\#NAME} 会有一个 RAID 组件, 比如: {"{\#NAME}": "/dev/sda cciss,2"} | |smart.disk.discovery|<|<|<| |返回 S.M.A.R.T. 设备列表.|JSON 对象| |将返回以下宏以及对应的值: {\#NAME}, {\#DISKTYPE}, {\#MODEL}, {\#SN}.<br>支持 HDD, SSD 和 NVME 设备类型. 设备可以单独或组合在一个RAID中. {\#NAME} 会有一个 RAID 组件, 比如: {"{\#NAME}": "/dev/sda cciss,2"} | |smart.disk.get|<|<|<| |返回 S.M.A.R.T. 设备的所有可用属性.|JSON 对象| |支持 HDD, SSD 和 NVME 设备类型. 设备可以单独或组合在一个RAID中.<br>该数据包含 smartctl 版本和调用参数，以及附加字段:<br>*disk\_name* - 包含RAID发现所需的附加组件的名称, 比如: {"disk\_name": "/dev/sda cciss,2"}<br>*disk\_type* - 包含磁盘类型 HDD, SSD, 或者 NVME, 比如: {"disk\_type": "ssd"}) |

en-us	 ### S.M.A.R.T. monitoring  *Smart plugin*, supported for Zabbix agent 2, now provides more efficient disk discovery and allows returning information about a specific disk, instead of all discovered disks. Zabbix agent 2 [items](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) **smart.disk.discovery** and **smart.disk.get** have been updated. The templates *SMART by Zabbix agent 2* and *SMART by Zabbix agent 2 (active)*  have also been modified to incorporate the new functionality.  
zh-cn	 ### S.M.A.R.T. 监控  Zabbix agent 2 支持的 *Smart plugin* 现在提供了更高效的磁盘发现，并允许返回有关特定磁盘的信息，而不是所有发现的磁盘。Zabbix agent 2 [监控项](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) **smart.disk.discovery** 和 **smart.disk.get** 已更新。模板 *SMART by Zabbix agent 2* 和 *SMART by Zabbix agent 2 (active)* 已修改，以纳入新功能。

en-us	### SNI support in encrypted connections Encrypted TCP connections between Zabbix agent and Zabbix server or proxy now support SNI.  
zh-cn	### 加密连接中的SNI支持 Zabbix agent 和 Zabbix server 或 proxy 之间的加密 TCP 连接现在支持 SNI。

en-us	#### SNMP checks  If the OpenBSD operating system is used, a use-after-free bug in the Net-SNMP library up to the 5.7.3 version can cause a crash of Zabbix server if the SourceIP parameter is set in the Zabbix server configuration file. As a workaround, please do not set the SourceIP parameter. The same problem applies also for Linux, but it does not cause Zabbix server to stop working. A local patch for the net-snmp package on OpenBSD was applied and will be released with OpenBSD 6.3.
zh-cn	#### SNMP 检查  对于 OpenBSD 操作系统，如果在 Zabbix server 配置文件中设置了 SourceIP 参数，则 5.7.3（及之前）版本中 Net-SNMP 库的 use-after-free bug 会导致 Zabbix server 崩溃。其中一种解决办法是不设置 SourceIP 参数。同样的问题也存在于 Linux，但它不会导致 Zabbix server 停止工作。OpenBSD 上的 net-snmp 软件包的本地补丁已启用，并将与 OpenBSD 6.3 一起发布。

en-us	#### SNMP checks  If the OpenBSD operating system is used, a use-after-free bug in the Net-SNMP library up to the 5.7.3 version can cause a crash of Zabbix server if the SourceIP parameter is set in the Zabbix server configuration file. As a workaround, please do not set the SourceIP parameter. The same problem applies also for Linux, but it does not cause Zabbix server to stop working. A local patch for the net-snmp package on OpenBSD was applied and will be released with OpenBSD 6.3.  
zh-cn	#### SNMP 检查  对于 OpenBSD 操作系统，如果在 Zabbix server 配置文件中设置了 SourceIP 参数，则 5.7.3（及之前）版本中 Net-SNMP 库的 use-after-free bug 会导致 Zabbix server 崩溃。其中一种解决办法是不设置 SourceIP 参数。同样的问题也存在于 Linux，但它不会导致 Zabbix server 停止工作。OpenBSD 上的 net-snmp 软件包的本地补丁已启用，并将与 OpenBSD 6.3 一起发布。

en-us	#### SNMP data spikes  Spikes in SNMP data have been observed that may be related to certain physical factors like voltage spikes in the mains. See [ZBX-14318](https://support.zabbix.com/browse/ZBX-14318) more details.
zh-cn	#### SNMP 数据峰值  SNMP 监控数据中的峰值可能与某些物理因素有关，如电源中的电压峰值。详情点击 [ZBX-14318](https://support.zabbix.com/browse/ZBX-14318)。

en-us	##### SNMP trap format  All customized Perl trap receivers and SNMPTT trap configuration must format the trap in the following way:       [timestamp] [the trap, part1] ZBXTRAP [address] [the trap, part 2]  where  -   \[timestamp\] - the timestamp used for log items -   ZBXTRAP - header that indicates that a new trap starts in this line -   \[address\] - IP address used to find the host for this trap  Note that "ZBXTRAP" and "\[address\]" will be cut out from the message during processing. If the trap is formatted otherwise, Zabbix might parse the traps unexpectedly.  Example trap:      11:30:15 2011/07/27 .1.3.6.1.6.3.1.1.5.3 Normal "Status Events"     localhost - ZBXTRAP 192.168.1.1 Link down on interface 2. Admin state:     1. Operational state: 2  This will result in the following trap for SNMP interface with IP=192.168.1.1:      11:30:15 2011/07/27 .1.3.6.1.6.3.1.1.5.3 Normal "Status Events"     localhost - Link down on interface 2. Admin state: 1. Operational state: 2
zh-cn	##### SNMP 陷阱格式  所有自定义的 Perl 陷阱接收器和 SNMPTT 陷阱配置必须按以下方式格式化陷阱：     [timestamp] [the trap, part1] ZBXTRAP [address] [the trap, part 2]  在哪里  - · \[timestamp\] - 用于日志监控项的时间戳 - · ZBXTRAP - 头表示一个新的陷阱从这一行开始 - · \[address\] - 用于查找此trap的主机的 IP 地址  请注意，“ZBXTRAP”和“\[address\]”将在处理过程中从消息中删除。 如果陷阱以其他方式格式化，Zabbix 可能会意外地解析陷阱。  trap示例：   · 11:30:15 2011/07/27 .1.3.6.1.6.3.1.1.5.3 Normal "Status Events"  · localhost - ZBXTRAP 192.168.1.1 Link down on interface 2. Admin state: 1. Operational state: 2  这将导致 IP=192.168.1.1 的 SNMP 接口出现以下陷阱：   · 11:30:15 2011/07/27 .1.3.6.1.6.3.1.1.5.3 Normal "Status Events"  · localhost - Link down on interface 2. Admin state: 1. Operational state: 2

en-us	#### SNMP traps  The "net-snmp-perl" package, needed for SNMP traps, has been removed in RHEL/CentOS 8.0-8.2; re-added in RHEL 8.3.  So if you are using RHEL 8.0-8.2, the best solution is to upgrade to RHEL 8.3; if you are using CentOS 8.0-8.2, you may wait for CentOS 8.3 or use a package from EPEL.  Please also see [ZBX-17192](https://support.zabbix.com/browse/ZBX-17192) for more information.
zh-cn	#### SNMP trap  SNMP trap 所需的 “net-snmp-perl” 软件包已在 RHEL/CentOS 8.0-8.2 中删除，在 RHEL 8.3 中重新添加。  所以如果你使用的是 RHEL 8.0-8.2，最好的解决方案是升级到 RHEL 8.3；如果你使用的是 CentOS 8.0-8.2，您可以等待 CentOS 8.3 或使用 EPEL 源提供的软件包。  详情参阅 [ZBX-17192](https://support.zabbix.com/browse/ZBX-17192) 。

en-us	#### SNMP traps  The "net-snmp-perl" package, needed for SNMP traps, has been removed in RHEL/CentOS 8.0-8.2; re-added in RHEL 8.3.  So if you are using RHEL 8.0-8.2, the best solution is to upgrade to RHEL 8.3; if you are using CentOS 8.0-8.2, you may wait for CentOS 8.3 or use a package from EPEL.  Please also see [ZBX-17192](https://support.zabbix.com/browse/ZBX-17192) for more information.  
zh-cn	#### SNMP trap  SNMP trap 所需的 “net-snmp-perl” 软件包已在 RHEL/CentOS 8.0-8.2 中删除，在 RHEL 8.3 中重新添加。  所以如果你使用的是 RHEL 8.0-8.2，最好的解决方案是升级到 RHEL 8.3；如果你使用的是 CentOS 8.0-8.2，您可以等待 CentOS 8.3 或使用 EPEL 源提供的软件包。  详情参阅 [ZBX-17192](https://support.zabbix.com/browse/ZBX-17192) 。

en-us	##### Solaris  By default the `ps` command does not show changing activities. One option is to use `/usr/ucb/ps` instead. If `watch` command is not installed, a periodically updated list of processes can be shown with      while [ 1 ]; do /usr/ucb/ps gxww; sleep 1; clear; done  On Solaris 11:  -   `/usr/ucb/ps` is not installed by default. You may need to install     *ucb* package, e.g. `pkg install compatibility/ucb`, -   if Zabbix daemon has been started by privileged user its activities     are not shown to non-privileged user. -   the `sleep` command accepts not only whole seconds but also     fractions of second (e.g. `sleep 0.2`).
zh-cn	##### Solaris  默认情况下，该 `ps` 命令不显示变化的活动。一种选择是`/usr/ucb/ps` 来替代。 如果没有安装 `watch`命令，则可以显示定期更新的进程列表      while [ 1 ]; do /usr/ucb/ps gxww; sleep 1; clear; done  在 Solaris 11:  -   `/usr/ucb/ps`默认情况下不安装。您可能需要安装*ucb* 包，例如 `pkg install compatibility/ucb`。 -   如果 Zabbix 守护进程已由特权用户启动，则其活动不会显示给非特权用户。 -   `sleep` 命令不仅接受整秒，还接受秒的小数部分（例如`sleep 0.2`）。

en-us	#### Solaris  See values supported for 'memtype' parameter on Solaris in the table.  |Supported value|Description|Source in psinfo structure|Tries to be compatible with| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Size of process image|pr\_size|ps -o vsz| |pmem|Percentage of real memory|pr\_pctmem|ps -o pmem| |rss|Resident set size<br>It may be underestimated - see rss description in "man ps".|pr\_rssize|ps -o rss|
zh-cn	#### Solaris  请参见表中的Solaris上的“memtype”参数所支持的值。  |支持值|描述|psinfo 结构中的源代码|兼容| |---------------|-----------|--------------------------|---------------------------| |vsize ^[1](proc_mem_notes#footnotes)^|过程映像的大小|pr\_size|ps -o vsz| |pmem|实际内存百分比|pr\_pctmem|ps -o pmem| |rss|驻留集大小<br>可能被低估了 - 请参阅“man ps”中的 rss 描述。|pr\_rssize|ps -o rss|

en-us	### Source  CAction::create() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::create() 。

en-us	### Source  CAction::delete() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::delete()。

en-us	### Source  CAction::get() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::get()。

en-us	### Source  CAction::update() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::update()。

en-us	### Source  CAlert::get() in *ui/include/classes/api/services/CAlert.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAlert.php* 中的 CAlert::get()。

en-us	### Source  CAPIInfo::version() in *ui/include/classes/api/services/CAPIInfo.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAPIInfo.php* 中的 CAPIInfo::version()。

en-us	### Source  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.
zh-cn	### 来源  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.

en-us	### Source  CAuthentication::get() in *ui/include/classes/api/services/CAuthentication.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAuthentication.php* 中的 CAuthentication::get()。

en-us	### Source  CAuthentication::update() in *ui/include/classes/api/services/CAuthentication.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAuthentication.php* 中的 CAuthentication::update()。

en-us	### Source  CAutoregistration::get() in *ui/include/classes/api/services/CAutoregistration.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAutoregistration.php* 中的 CAutoregistration::get()。

en-us	### Source  CAutoregistration::update() in *ui/include/classes/api/services/CAutoregistration.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAutoregistration.php* 中的 CAutoregistration::update()。

en-us	### Source  CConfiguration::export() in *ui/include/classes/api/services/CConfiguration.php*.
zh-cn	### 来源  CConfiguration::export() in *ui/include/classes/api/services/CConfiguration.php*.

en-us	### Source  CConfiguration::importcompare() in *ui/include/classes/api/services/CConfiguration.php*.
zh-cn	### 来源  CConfiguration::importcompare() in *ui/include/classes/api/services/CConfiguration.php*.

en-us	### Source  CConfiguration::import() in *ui/include/classes/api/services/CConfiguration.php*.
zh-cn	### 来源  CConfiguration::import() in *ui/include/classes/api/services/CConfiguration.php*.

en-us	### Source  CCorrelation::create() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::create()。

en-us	### Source  CCorrelation::delete() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::delete()。

en-us	### Source  CCorrelation::get() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::get()。

en-us	### Source  CCorrelation::update() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::update()。

en-us	### Source  CDashboard::create() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::create()。

en-us	### Source  CDashboard::delete() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::delete() 。

en-us	### Source  CDashboard::get() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::get() 。

en-us	### Source  CDashboard::update() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::update() 。

en-us	### Source  CDCheck::get() in *ui/include/classes/api/services/CDCheck.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDCheck.php* 中的 CDCheck::get()。

en-us	### Source  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.
zh-cn	### 源代码  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.

en-us	### Source  CDiscoveryRule::create() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::create()。

en-us	### Source  CDiscoveryRule::delete() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::delete()。

en-us	### Source  CDiscoveryRule::get() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::get()。

en-us	### Source  CDiscoveryRule::update() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::update()。

en-us	### Source  CDRule::create() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::create()。

en-us	### Source  CDRule::delete() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::delete()。

en-us	### Source  CDRule::get() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::get()。

en-us	### Source  CDRule::update() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::update()。

en-us	### Source  CDService::get() in *ui/include/classes/api/services/CDService.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDService.php* 中的 CDService::get()。

en-us	### Source  CEvent::acknowledge() in *ui/include/classes/api/services/CEvent.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CEvent.php* 中的 CEvent::acknowledge() 。

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CEvent.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CEvent.php* 中的 CEvent::get() 。

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CProblem.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CProblem.php* 中的 CEvent::get()。

en-us	### Source  CGraph::create() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CGraph.php*中的CGraph::create()。

en-us	### Source  CGraph::delete() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::delete()。

en-us	### Source  CGraph::get() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::get()。

en-us	### Source  CGraphItem::get() in *ui/include/classes/api/services/CGraphItem.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphItem.php* 中的 CGraphItem::get()。

en-us	### Source  CGraphPrototype::create() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::create()。

en-us	### Source  CGraphPrototype::delete() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::delete()。

en-us	### Source  CGraphPrototype::get() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::get()。

en-us	### Source  CGraphPrototype::update() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::update()。

en-us	### Source  CGraph::update() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::update()。

en-us	### Source  CHaNode::get() in *ui/include/classes/api/services/CHaNode.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHaNode.php* 的 CHaNode::get()。

en-us	### Source  CHistory::clear() in *ui/include/classes/api/services/CHistory.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHistory.php* 的 CHistory::clear()。

en-us	### Source  CHistory::get() in *ui/include/classes/api/services/CHistory.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHistory.php* 的 CHistory::get()。

en-us	### Source  CHost::create() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::create() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::delete() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::delete() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::get() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::get() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::delete() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::delete() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*.  
zh-cn	### 来源  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源 CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.  
zh-cn	### 来源  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHost::update() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::update() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.  
zh-cn	### 来源  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.  
zh-cn	### 来源  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CIconMap::create() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::create() 。

en-us	### Source  CIconMap::delete() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::delete()。

en-us	### Source  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	 ### 来源  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::update() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::update()。

en-us	### Source  CImage::create() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::create()

en-us	### Source  CImage::delete() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::delete()

en-us	### Source  CImage::get() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::get()

en-us	### Source  CImage::update() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::update()

en-us	### Source  CItem::create() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::create()

en-us	### Source  CItem::delete() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::delete()

en-us	### Source  CItem::get() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::get()

en-us	### Source  CItemPrototype::create() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::create() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::get() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::get() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::update() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::update() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItem::update() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::update()

en-us	### Source  CMaintenance::create() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::create() in *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::delete() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::delete() in *frontends/php/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::get() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::get() 在 *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::update() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::update() in *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMap::create() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源   CMap::create() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::delete() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::delete() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::get() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::get() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::update() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::update() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMediaType::create() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::create()。

en-us	### Source  CMediaType::delete() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::delete()。

en-us	### Source  CMediaType::get() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源   *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::get()。

en-us	### Source  CMediaType::update() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::update()。

en-us	### Source  CProxy::create() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CProxy.php* 中的 CProxy::create()。

en-us	### Source  CProxy::delete() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源   *ui/include/classes/api/services/CProxy.php* 中的 CProxy::delete()。

en-us	### Source  CProxy::get() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  CProxy::get() in *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CProxy::update() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  CProxy::update() in *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CRegexp::create() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::create() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::delete() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::delete() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::get() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::get() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::update() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::update() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CReport::create() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::create() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::delete() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::delete() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::get() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::get() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::update() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::update() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CRole::create() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 来源  CRole::create() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::delete() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::delete() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::get() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::get() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::update() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::update() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CScript::create() in *ui/include/classes/api/services/CScript.php*.  
zh-cn	### 源代码  CScript::create() 在 *ui/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::delete() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码  CScript::delete() 在*frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::execute() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::execute() 在*ui/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::get() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::get() 在*frontends/php/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::getScriptsByHosts() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::getScriptsByHosts()  在*frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::update() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::update() 在 *frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CService::create() in *ui/include/classes/api/services/CService.php*.
zh-cn	### 来源 CService::create() 在 *frontends/php/include/classes/api/services/CService.php*。

en-us	### Source  CService::delete() in *ui/include/classes/api/services/CService.php*.
zh-cn	 ### 来源  CService::delete() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CService::get() in *ui/include/classes/api/services/CService.php*.
zh-cn	### 来源  CService::get() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CService::update() in *ui/include/classes/api/services/CService.php*.
zh-cn	 ### 来源  CService::update() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CSettings::get() in *ui/include/classes/api/services/CSettings.php*.
zh-cn	 ### 来源  CSettings::get()见*ui/include/classes/api/services/CSettings.php*。

en-us	### Source  CSettings::update() in *ui/include/classes/api/services/CSettings.php*.
zh-cn	 ### 来源  CSettings::update() 在*ui/include/classes/api/services/CSettings.php*。

en-us	### Source  CSla::create() in *ui/include/classes/api/services/CSla.php*.
zh-cn	### 来源  CSla::create() in *ui/include/classes/api/services/CSla.php*.

en-us	### Source  CSla::delete() in *ui/include/classes/api/services/CSla.php*.
zh-cn	### 来源  CSla::delete() in *ui/include/classes/api/services/CSla.php*.

en-us	### Source  CSla:get() in *ui/include/classes/api/services/CSla.php*.
zh-cn	### 来源  CSla:get() in *ui/include/classes/api/services/CSla.php*.

en-us	### Source  CSla::getSli() in *ui/include/classes/api/services/CSla.php*
zh-cn	### 来源  *ui/include/classes/api/services/CSla.php* 中的 CSla::getSli()

en-us	### Source  CSla::update() in *ui/include/classes/api/services/CSla.php*.
zh-cn	### 来源  CSla::update() in *ui/include/classes/api/services/CSla.php*.

en-us	### Source  CTask::create() in *ui/include/classes/api/services/CTask.php*.
zh-cn	### 来源  CTask::create() in *ui/include/classes/api/services/CTask.php*.

en-us	### Source  CTask::get() in *ui/include/classes/api/services/CTask.php*.
zh-cn	### 来源  CTask::get() in *ui/include/classes/api/services/CTask.php*.

en-us	### Source  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 来源  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplateDashboard::create() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::create() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::delete() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::delete() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::get() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::get() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::update() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::update() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplate::delete() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 来源  CTemplate::delete() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::get() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::get() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massAdd() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massAdd() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massRemove() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massRemove() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massUpdate() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massUpdate() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::update() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码 CTemplate::update() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CToken::create() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::create()。

en-us	### Source  CToken::delete() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::delete()。

en-us	### Source  CToken::generate() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::generate()。

en-us	### Source  CToken::get() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::get()。

en-us	### Source  CToken::update() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::update()。

en-us	### Source  CTrend::get() in *ui/include/classes/api/services/CTrend.php*.
zh-cn	### 源码  CTrend::get() in *ui/include/classes/api/services/CTrend.php*.

en-us	### Source  CTrigger::addDependencies() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::addDependencies() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::create() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::create() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::deleteDependencies() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::deleteDependencies() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::delete() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::delete() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::get() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::get() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTriggerPrototype::create() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::create() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTriggerPrototype::delete() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::delete() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTriggerPrototype::get() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::get() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTriggerPrototype::update() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::update() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTrigger::update() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::update() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CUser::checkAuthentication() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::checkAuthentication() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::create() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::create() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::delete() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::delete() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::get() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源<br>CUser::get() in ui/include/classes/api/services/CUser.php.

en-us	### Source  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::delete() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::delete() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::get() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::get() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::update() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::update() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUser::login() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::login() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::login() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::login() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUserMacro::createGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::createGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::create() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::create() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::deleteGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::deleteGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::delete() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::delete() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::get() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::get() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::updateGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::updateGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::update() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::update() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUser::unblock() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::unblock() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::update() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::update() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CValueMap::create() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::create() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::delete() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::delete() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::get() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	 ### 来源  CValueMap::get() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::update() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::update() in *ui/include/classes/api/services/CValueMap.php*.

en-us	 ### SourceIP support in LDAP simple checks  SourceIP support has been added to LDAP [simple checks](/manual/config/items/itemtypes/simple_checks). *Note* that with OpenLDAP, version 2.6.1 or above is required.
zh-cn	### LDAP 简单检查中的 SourceIP 支持  SourceIP 支持已添加到 LDAP [简单检查](/manual/config/items/itemtypes/simple_checks)。 *注意*对于 OpenLDAP，需要 2.6.1 或更高版本。

en-us	Specific parameters for item value columns:  |   |   | |--|--------| |*Item*|Select the item.<br>Selecting non-numeric items is supported since Zabbix 6.0.4.| |*Time shift*|Specify time shift if required.<br>You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. Negative values are allowed.| |*Aggregation function*|Specify which aggregation function to use:<br>**min** - display the smallest value<br>**max** - display the largest value<br>**avg** - display the average value<br>**sum** - display the sum of values<br>**count** - display the count of values<br>**first** - display the first value<br>**last** - display the last value<br>**none** - display all values (no aggregation)<br>Aggregation allows to display an aggregated value for the chosen interval (5 minutes, an hour, a day), instead of all values.<br>Note that only numeric items can be displayed in this column if this setting is not "none".| |*Aggregation interval*|Specify the interval for aggregating values. You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. A numeric value without a suffix will be regarded as seconds.<br>This field will not be displayed if *Aggregation function* is "none".| |*Display*|Define how the value should be displayed:<br>**As is** - as regular text<br>**Bar** - as solid, color-filled bar<br>**Indicators** - as segmented, color-filled bar<br>Note that only numeric items can be displayed in this column if this setting is not "as is".| |*History*|Take data from history or trends:<br>**Auto** - automatic selection<br>**History** - take history data<br>**Trends** - take trend data<br>This setting applies only to numeric data. Non-numeric data will always be taken from history.| |*Min*|Minimum value for bar/indicators.| |*Max*|Maximum value for bar/indicators.| |*Thresholds*|Specify threshold values when the background/fill color should change. The list will be sorted in ascending order when saved.<br>Note that only numeric items can be displayed in this column if thresholds are used.|
zh-cn	监控项的值列的特定参数：  |   |   | |---|---| |*Item*|选择监控项<br>从Zabbix 6.0.4开始，支持选择非数字监控项。| |*Time shift*|如果需要，请指定时间偏移<br>您可以在这个字段使用[时间后缀](/manual/appendix/suffixes#time_suffixes) ，允许负值。| |*Aggregation function*|指定要使用的聚合函数：<br>**min** - 显示最小值<br>**max** - 显示最大值<br>**avg** - 显示平均值<br>**sum** - 显示值的总和<br>**count** - 显示值的数量<br>**first** - 显示第一个值<br>**last** - 显示最后一个值<br>**none** - 显示所有值 (不推荐)<br>聚合允许显示所选间隔（5分钟、一小时、一天）的聚合值，而不是所有值<br>请注意，如果此设置不是“none”，则此列中只能显示数字监控项。| |*Aggregation interval*|指定聚合值的间隔。您可以在此字段中使用[时间后缀](/manual/appendix/suffixes#time_suffixes) 。 没有后缀的数值将被视为秒<br>如果*聚合函数*为“none”，则不显示此字段。| |*Display*|定义应如何显示值：<br>**As is** - 按常规文本显示<br>**Bar** - 按实心彩色填充条形图显示<br>**Indicators** - 按分段彩色填充条形图显示<br>请注意，如果此设置不是“as is”，则此列中只能显示数字监控项。| |*History*|从历史或趋势中获取数据：<br>**Auto** - 自动选择<br>**History** - 获取历史数据<br>**Trends** - 获取趋势数据<br>此设置仅适用于数字数据。非数字数据将始终取自历史记录。| |*Min*|条形图/指示器的最小值。| |*Max*|条形图/指示器的最大值。| |*Thresholds*|指定背景/填充颜色应更改的阈值。保存时，列表将按升序排序<br>请注意，如果使用阈值，则此列中只能显示数字项。|

en-us	Specific parameters for text columns:  |   |   | |---|---| |*Text*|Enter the string to display. May contain host and inventory [macros](/manual/appendix/macros/supported_by_location).|
zh-cn	文本列的特定参数：  |   |   | |---|---| |*Text*|输入要显示的字符串。可能包含主机和资产[宏] (/manual/appendix/macros/supported_by_location).|

en-us	##### Specify server  Make sure you have the Zabbix server identified in the agent [configuration file](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf      ServerActive=10.0.0.1  Unless you specifically define a *Hostname* in zabbix\_agentd.conf, the system hostname of agent location will be used by server for naming the host. The system hostname in Linux can be obtained by running the 'hostname' command.  If *Hostname* is defined in Zabbix agent configuration as a comma-delimited list of hosts, hosts will be created for all listed hostnames.  Restart the agent after making any changes to the configuration file.
zh-cn	##### 定义Zabbix server  确保在 [配置文件](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf中定义了Zabbix server。      ServerActive=10.0.0.1  如果不在zabbix\_agentd.conf中定义 *主机名称(Hostname)*，则Zabbix会使用agent所在系统的主机名称给主机命名。Linux系统的主机名称可以通过运行命令 'hostname' 来获取。  如果定义的 *主机名称(Hostname)* 是以逗号分隔的多台主机，那么其中定义的所有主机均会被创建。  agent配置变更需要重启agent生效。

en-us	#### SQLite  Using SQLite is supported for **Zabbix proxy** only!  The database will be automatically created if it does not exist.  Return to the [installation section](/manual/installation/install).
zh-cn	#### SQLite  仅 **Zabbix proxy** 支持使用 SQLite！  如果数据库不存在，将自动创建该数据库。  返回[安装部分](/manual/installation/install)。

en-us	#### SSH checks  Some Linux distributions like Debian, Ubuntu do not support encrypted private keys (with passphrase) if the libssh2 library is installed from packages. Please see [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850) for more details.  When using libssh 0.9.x on CentOS 8 with OpenSSH 8 SSH checks may occasionally report "Cannot read data from SSH server". This is caused by a libssh [issue](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101) ([more detailed report](https://bugs.libssh.org/T231)). The error is expected to have been fixed by a stable libssh 0.9.5 release. See also [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756) for details.
zh-cn	#### SSH 检查  如果从软件包安装 libssh2 库，则某些 Linux 发行版（如 Debian、Ubuntu）不支持加密的私钥（带密码）。详情参考 [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850) 。  在 CentOS 8 上使用带有 OpenSSH 8 的 libssh 0.9.x 时，SSH 检查可能偶尔会报错 “无法从 SSH 服务器读取数据”。这是由 libssh [问题](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101)  引起的 ([参考更详细的说明](https://bugs.libssh.org/T231))。预计该错误已在稳定的 libssh 0.9.5 版本中被修复。有关详细说明，另请参阅 [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756) 。

en-us	#### SSH checks     - Some Linux distributions like Debian, Ubuntu do not support encrypted    private keys (with passphrase) if the libssh2 library is installed from    packages. Please see [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850) for more details.     - When using libssh 0.9.x on some Linux distributions with OpenSSH 8 SSH checks may    occasionally report "Cannot read data from SSH server". This is caused    by a libssh [issue](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101)     ([more detailed report](https://bugs.libssh.org/T231)). The error is expected     to have been fixed by a stable libssh 0.9.5 release. See also     [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756) for details.     - Using the pipe "|" in the SSH script may lead to a     "Cannot read data from SSH server" error. In this case it is recommended     to upgrade the libssh library version. See also [ZBX-21337](https://support.zabbix.com/browse/ZBX-21337)     for details.
zh-cn	#### SSH 检查    · - 如果 libssh2 库是从软件包安装的，一些 Linux 发行版如 Debian、Ubuntu 不支持加密私钥（带密码）。 有关详细信息，请参阅 [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850)。    · - 在某些带有 OpenSSH 8 的 Linux 发行版上使用 libssh 0.9.x 时，SSH 检查可能偶尔会报告“无法从 SSH 服务器读取数据”。 这是由 libssh [问题](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101) 引起的（[更详细的报告](https://bugs.libssh.org/T231)） . 该错误预计已由稳定的 libssh 0.9.5 版本修复。 有关详细信息，另请参阅 [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756)。    · - 使用管道“|” 在 SSH 脚本中可能会导致“无法从 SSH 服务器读取数据”错误。 在这种情况下，建议升级 libssh 库版本。 有关详细信息，另请参阅 [ZBX-21337](https://support.zabbix.com/browse/ZBX-21337)。

en-us	#### Starting agent  To start the agent service, you can use Control Panel or do it from command line.  To start a single instance of Zabbix agent with the default configuration file:       zabbix_agentd.exe --start  To start a single instance of Zabbix agent with another configuration file:       zabbix_agentd.exe --config <your_configuration_file> --start  To start one of multiple instances of Zabbix agent:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --start --multiple-agents
zh-cn	#### Starting agent 要启动agent服务，可以使用"控制面板"或从命令行执行此操作  使用默认配置文件启动单个实例的 Zabbix agent:       zabbix_agentd.exe --start  指定配置文件启动单个实例的 Zabbix agent:       zabbix_agentd.exe --config <your_configuration_file> --start  启动多个Zabbix agent实例的其中一个，请执行以下操作：       zabbix_agentd.exe --config <configuration_file_for_this_instance> --start --multiple-agents

en-us	##### Starting Zabbix proxy process  To start a Zabbix proxy process and make it start at system boot:      # service zabbix-proxy start     # systemctl enable zabbix-proxy
zh-cn	##### 启动 Zabbix proxy进程  要启动 Zabbix proxy 进程并使其在系统启动时启动，请执行以下操作:      # service zabbix-proxy start     # systemctl enable zabbix-proxy

en-us	##### Starting Zabbix server as cluster node  Two parameters are required  in the server [configuration](/manual/appendix/config/zabbix_server)  to start a Zabbix server as cluster node:  -    **HANodeName** parameter must be specified for each Zabbix server  that will be an HA cluster node.   This is a unique node identifier (e.g. `zabbix-node-01`) that the server will be referred to in agent and proxy  configurations. If you do not specify HANodeName, then the server will be started  in standalone mode.  -    **NodeAddress** parameter must be specified for each node.   The NodeAddress parameter (address:port) will be used by Zabbix frontend to connect  to the active server node. NodeAddress must match the IP or FQDN name of the respective Zabbix server.  Restart all Zabbix servers after making changes to the configuration files. They will  now be started as cluster nodes. The new status of the servers can be seen in  *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)*  and also by running:  ``` zabbix_server -R ha_status ```  This runtime command will log the current HA cluster status into the Zabbix server log (and to stdout):  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}
zh-cn	##### 作为集群节点启动Zabbix server  在server[配置](/manual/appendix/config/zabbix_server)中需要两个参数来启动Zabbix server作为集群节点:  -    **HANodeName** 集群中每个zabbix server节点名称必须要有且唯一。  这是将在agent和proxy配置中引用server的名称 (例如： `zabbix-node-01`)。如果您没有指定HANodeName，那么服务器将以standalone模式启动。  -    **NodeAddress** 参数必须为每个节点指定。  NodeAddress参数(address:port)将被Zabbix前端用来连接到主server节点。NodeAddress必须匹配相应Zabbix server的IP或FQDN名称。  在对配置文件进行更改后，重新启动所有Zabbix server。-   它们现在将作为集群节点启动。-   server的新状态可以在 *报表* → *[系统信息](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)* 查看 ，也可以用以下命令查看:  ``` zabbix_server -R ha_status ```  此运行时命令会将当前 HA 集群状态记录到 Zabbix 服务器日志中（并输出到标准输出）：  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_proxy binary and execute:      shell> zabbix_proxy  You can use the following command line parameters with Zabbix proxy:      -c --config <file>              path to the configuration file     -f --foreground                 run Zabbix proxy in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  ::: noteclassic Runtime control is not supported on OpenBSD and NetBSD. :::  Examples of running Zabbix proxy with command line parameters:      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf     shell> zabbix_proxy --help     shell> zabbix_proxy -V  
zh-cn	##### 运行时控制  运行时控制包含的选项：  |选项                                          描|目标|<| |---------------------------------------------------|------|-| |config\_cache\_reload|重新加载配置缓存。如果当前正在加载缓存，则忽略。<br>主动模式下的 Zabbix proxy 将连接到Zabbix server 并请求配置数据。|<| |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 选项重新加载 proxy 的配置缓存：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R config_cache_reload  例如，使用 housekeeper\_execute 选项来触发管家服务执行：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R housekeeper_execute  例如，使用 log\_level\_increase 选项来改变日志级别：      增加所有进程的日志级别：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase      增加第二个 Poller 进程的日志级别：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=poller,2      增加 PID 为 1234 进程的日志级别：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_increase=1234      降低 http poller 进程的日志级别：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R log_level_decrease="http poller"  

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_server binary and execute:      shell> zabbix_server  You can use the following command line parameters with Zabbix server:      -c --config <file>              path to the configuration file (default is /usr/local/etc/zabbix_server.conf)     -f --foreground                 run Zabbix server in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  ::: noteclassic Runtime control is not supported on OpenBSD and NetBSD. :::  Examples of running Zabbix server with command line parameters:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf     shell> zabbix_server --help     shell> zabbix_server -V  
zh-cn	##### 手动启动  如果以上操作均无效，您可能需要手动启动，找到 Zabbix Server二进制文件的路径并且执行：      shell> zabbix_server  您可以将以下命令行参数用于 Zabbix server：      -c --config <file>              配置文件路径（默认的是 /usr/local/etc/zabbix_server.conf）     -R --runtime-control <option>   执行管理功能     -h --help                       帮助     -V --version                    显示版本号  ::: noteclassic 运行时控制不支持 OpenBSD 和 NetBSD 系统。 :::  使用命令行参数运行 Zabbix server 的示例：      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf     shell> zabbix_server --help     shell> zabbix_server -V

en-us	##### Start-up scripts  The scripts are used to automatically start/stop Zabbix processes during system's start-up/shutdown. The scripts are located under directory misc/init.d.
zh-cn	##### 启动脚本  这些脚本用于在系统启动和关闭期间自动启动和停止 Zabbix 进程。 此脚本位于 misc/init.d 目录下。

en-us	#### Statistic request object  Statistic request object is used to define what type of information should be collected about server/proxy internal processes. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |stats|query|Statistic object properties to be returned. The list of available fields for each type of diagnostic information statistic are [described in detail below](object#list_of_statistic_fields_available_for_each_type_of_diagnostic_information_request).<br><br>Default: `extend` will return all available statistic fields.| |top|object|Object to sort and limit returned statistic values. The list of available fields for each type of diagnostic information statistic are [described in detail below](object#list_of_sorting_fields_available_for_each_type_of_diagnostic_information_request).<br><br>Example:<br>{ “source.alerts”: 10 }|
zh-cn	 #### 统计请求对象  Statistic request对象用于定义应收集的关于服务器/代理内部进程的信息类型。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |stats|query|要返回的统计对象属性。每种类型的诊断信息统计的可用字段列表如下[详细描述如下](object#list_of_statistic_fields_available_for_each_type_of_diagnostic_information_request)。<br><br>默认值：`extend`将返回所有可用的统计字段。| |top|object|对象对返回的统计值进行排序和限制。每种类型的诊断信息统计的可用字段列表如下[详细描述如下](object#list_of_sorting_fields_available_for_each_type_of_diagnostic_information_request)。<br><br>例如：<br>{ “source.alerts”: 10 }|

en-us	#### Statistic request object  Statistic request object is used to define what type of information should be collected about server/proxy internal processes. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |stats|query|Statistic object properties to be returned. The list of available fields for each type of diagnostic information statistic are [described in detail below](object#list_of_statistic_fields_available_for_each_type_of_diagnostic_information_request).<br><br>Default: `extend` will return all available statistic fields.| |top|object|Object to sort and limit returned statistic values. The list of available fields for each type of diagnostic information statistic are [described in detail below](object#list_of_sorting_fields_available_for_each_type_of_diagnostic_information_request).<br><br>Example:<br>{ “source.alerts”: 10 }|
zh-cn	 #### 统计请求对象  Statistic request对象用于定义应收集的关于服务器/代理内部进程的信息类型。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |stats|query|要返回的统计对象属性。每种类型的诊断信息统计的可用字段列表如下[详细描述如下](object#list_of_statistic_fields_available_for_each_type_of_diagnostic_information_request)。<br><br>默认值：`extend`将返回所有可用的统计字段。| |top|object|对象对返回的统计值进行排序和限制。每种类型的诊断信息统计的可用字段列表如下[详细描述如下](object#list_of_sorting_fields_available_for_each_type_of_diagnostic_information_request)。<br><br>例如：<br>{ “source.alerts”: 10 }|

en-us	#### Statistic result object  Statistic result object is retrieved in `result` field of task object.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |status|integer|*(readonly)* Status of the task result.<br><br>Possible values:<br>-1 - error occurred during performing task;<br>0 - task result is created.| |data|string/object|Results according the statistic request object of particular diagnostic information task. Contains error message string if error occurred during performing task.|
zh-cn	#### 统计结果对象  在任务对象的‘result’字段中检索统计结果对象。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |status|integer|*(只读)* 任务结果的状态.<br><br>可能的值：<br>-1 - 执行任务时发生错误；<br>0 - 任务结果已创建。| |data|string/object|结果根据特定诊断信息任务的统计请求对象。 如果在执行任务期间发生错误，则包含错误消息字符串。|

en-us	#### Statistic result object  Statistic result object is retrieved in `result` field of task object.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |status|integer|*(readonly)* Status of the task result.<br><br>Possible values:<br>-1 - error occurred during performing task;<br>0 - task result is created.| |data|string/object|Results according the statistic request object of particular diagnostic information task. Contains error message string if error occurred during performing task.|
zh-cn	#### 统计结果对象  在任务对象的‘result’字段中检索统计结果对象。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |status|integer|*(只读)* 任务结果的状态.<br><br>可能的值：<br>-1 - 执行任务时发生错误；<br>0 - 任务结果已创建。| |data|string/object|结果根据特定诊断信息任务的统计请求对象。 如果在执行任务期间发生错误，则包含错误消息字符串。|

en-us	##### Status ​calculation ​and propagation rules  There are new status calculation rules and flexible ​additional rules for calculating the status of a parent service based on the statuses and weight of direct children. It is now also possible to set flexible rules for propagating a service status to parent services.  
zh-cn	#### Status ​calculation ​and propagation rules  There are new status calculation rules and flexible ​additional rules for calculating the status of a parent service based on the statuses and weight of direct children. It is now also possible to set flexible rules for propagating a service status to parent services.  

en-us	##### Status calculation and propagation rules  There are new status calculation rules and flexible additional rules for calculating the status of a parent service based on the statuses and weight of direct children. It is now also possible to set flexible rules for propagating a service status to parent services.
zh-cn	##### 状态计算和传播规则  有新的状态计算规则和灵活的附加规则，用于基于直接子服务的状态和权重计算父服务的状态。现在还可以设置灵活的规则来将服务状态传播到父服务。

en-us	### Status rule  The status rule object has the following properties.  | Property                        | [Type](/manual/api/reference_commentary#data_types) | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | |---------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **type**<br>(required)          | integer                                             | Condition for setting (New status) status.<br><br>Possible values:<br>0 - if at least (N) child services have (Status) status or above;<br>1 - if at least (N%) of child services have (Status) status or above;<br>2 - if less than (N) child services have (Status) status or below;<br>3 - if less than (N%) of child services have (Status) status or below;<br>4 - if weight of child services with (Status) status or above is at least (W);<br>5 - if weight of child services with (Status) status or above is at least (N%);<br>6 - if weight of child services with (Status) status or below is less than (W);<br>7 - if weight of child services with (Status) status or below is less than (N%).<br><br>Where:<br>- N (W) is `limit_value`;<br>- (Status) is `limit_status`;<br>- (New status) is `new_status`. | | **limit\_value**<br>(required)  | integer                                             | Limit value.<br><br>Possible values:<br>- for N and W: 1-100000;<br>- for N%: 1-100.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | | **limit\_status**<br>(required) | integer                                             | Limit status.<br><br>Possible values:<br>-1 - OK;<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | | **new\_status**<br>(required)   | integer                                             | New status value.<br><br>Possible values:<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
zh-cn	 ### 状态规则  状态规则对象有如下属性。  | 属性                        | [类型](/manual/api/reference_commentary#数据_类型) | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | |---------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **type**<br>(必需)          | integer                                             | 设置(New status)状态的条件。<br><br>可能的值：<br>0 - 如果至少（N）个子服务处于（Status）或更高的状态；<br>1 - 如果至少（N%）的子服务处于（Status）或更高的状态；<br>2 - 如果不到（N）个子服务处于（Status）或更低状态；<br>3 - 如果不到（N%）的子服务处于（Status）或更低状态；<br>4 - 如果处于（Status）或更高状态的子服务的重量至少达到（W）；<br>5 - 如果处于（Status）或更高状态的子服务的重量至少达到（N%）；<br>6 - 如果处于（Status）或更低状态的子服务的重量低于（W）；<br>7 - 如果处于（Status）或更低状态的子服务的重量低于（N%）。<br><br>其中：<br>- N (W) 是 `limit_value`；<br>- (Status) 是 `limit_status`；<br>- (New status) 是 `new_status`。 | | **limit\_value**<br>(必需)  | integer                                             | 极限值。<br><br>可能的值：<br>- 对N和W： 1-100000；<br>- 对 N%： 1-100。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | | **limit\_status**<br>（必需） | integer                                             | 极限状态。<br><br>可能的值：<br>-1 - 正常；<br>0 - 未分类；<br>1 - 信息；<br>2 - 警告；<br>3 - 一般；<br>4 - 严重；<br>5 - 灾难。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | | **new\_status**<br>（必需）  | integer                                             | 新状态值：<br><br>可能的值：<br>0 - 未分类；<br>1 - 信息；<br>2 - 警告；<br>3 - 一般；<br>4 - 严重；<br>5 - 灾难。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |

en-us	### Status rule  The status rule object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|Condition for setting (New status) status.<br><br>Possible values:<br>0 - if at least (N) child services have (Status) status or above;<br>1 - if at least (N%) of child services have (Status) status or above;<br>2 - if less than (N) child services have (Status) status or below;<br>3 - if less than (N%) of child services have (Status) status or below;<br>4 - if weight of child services with (Status) status or above is at least (W);<br>5 - if weight of child services with (Status) status or above is at least (N%);<br>6 - if weight of child services with (Status) status or below is less than (W);<br>7 - if weight of child services with (Status) status or below is less than (N%).<br><br>Where:<br>- N (W) is `limit_value`;<br>- (Status) is `limit_status`;<br>- (New status) is `new_status`.| |**limit\_value**<br>(required)|integer|Limit value.<br><br>Possible values:<br>- for N and W: 1-100000;<br>- for N%: 1-100.| |**limit\_status**<br>(required)|integer|Limit status.<br><br>Possible values:<br>-1 - OK;<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.| |**new\_status**<br>(required)|integer|New status value.<br><br>Possible values:<br>0 - Not classified;<br>1 - Information;<br>2 - Warning;<br>3 - Average;<br>4 - High;<br>5 - Disaster.|  
zh-cn	### Service time 服务时间  The service time object defines periods, when an service is scheduled to be up or down. It has the following properties. 当一个服务按照计划上线或下线时，服务时间对象可定义周期。服务时间对象具有以下属性。  |Property 属性     T|pe 类型        Des|ription 说明| |---------------------|--------------------|--------------| |timeid|string 字符串    *(|eadonly 只读)* ID of the service time. 服务时间的ID。| |**serviceid**<br>(required 必须)|string 字符串    ID<br>|of the service. 服务的ID。<br>Cannot be updated. 不可更新。| |**ts\_from**<br>(required 必须)|integer 整数型   Ti<br>|e when the service time comes into effect. 服务时间生效的时间。<br>For onetime downtimes `ts_from` must be set as a Unix timestamp, for other types - as a specific time in a week, in seconds, for example, 90000 for Tue, 2:00 AM. 对于一次性停机时间，`ts_from`必须设置为Unix时间戳，对于其他类型的事件 —— 设置为一周中的特定时间，以秒为单位，例如，90000代表星期二，凌晨2:00。| |**ts\_to**<br>(required 必须)|integer 整数型   Ti<br>|e when the service time ends. 服务时间关闭的时间。<br>For onetime uptimes `ts_to` must be set as a Unix timestamp, for other types - as a specific time in a week, in seconds, for example, 90000 for Tue, 2:00 AM. 对于一次性开机时间，`ts_to`必须设置为Unix时间戳，对于其他类型的事件 —— 设置为一周中的特定时间，以秒为单位，例如，90000代表星期二，凌晨2:00。| |**type**<br>(required 必须)|integer 整数型   Se<br>|vice time type. 服务时间类型<br>Possible values: 许可值：<br>0 - planned uptime, repeated every week; 计划开机，每周重复；<br>1 - planned downtime, repeated every week; 计划停机，每周重复；<br>2 - one-time downtime. 一次性停机。| |note|string 字符串    Ad|itional information about the service time. 有关服务时间的附加信息。|  

en-us	##### Step 1  Add a new web scenario.  We will add a scenario to monitor the web interface of Zabbix. The scenario will execute a number of steps.  Go to *Configuration → Hosts*, pick a host and click on *Web* in the row of that host. Then click on *Create web scenario*.  ![](../../../assets/en/manual/web_monitoring/new_scenario.png)  All mandatory input fields are marked with a red asterisk.  In the new scenario form we will name the scenario as *Zabbix frontend*. We will also create two variables: {user} and {password}.  You may also want to add a new *Application:Zabbix frontend* tag in the Tags tab.
zh-cn	##### 第1步  添加一个新的 Web 场景。  我们将添加一个场景来监控 Zabbix 的 Web 界面。该场景将执行多个步骤。  点击 *Configuration（配置） → Hosts（主机）*，选择一个主机并单击该主机行中的 *Web* 。然后单击 *Create web scenario（创建 web 场景）*。  ![](../../../assets/en/manual/web_monitoring/new_scenario.png)  所有必填字段都标有红色星号。  在新的场景表单中，我们将场景命名为 *Zabbix frontend*。我们还将创建两个变量：{user} 和 {password}。  可能还想在标签选项卡中添加一个新的 *Application:Zabbix frontend* 标签。

en-us	##### Step 1  Configure [some media](media), such as e-mail, SMS, or script to use for the notifications. Refer to the corresponding sections of the manual to perform this task.  ::: noteimportant For notifying on internal events the default severity ('Not classified') is used, so leave it checked when configuring [user media](/manual/config/notifications/media/email#user_media) if you want to receive notifications for internal events. :::
zh-cn	##### 第一步  配置[某些媒体]（媒体），例如电子邮件、短信或脚本以用于通知。请参阅手册的相应章节以执行此任务。  ::: noteimportant 对于内部事件通知，使用默认严重性（“未分类”），因此，如果要接收内部事件通知，请在配置[用户媒体](/manual/config/notifications/media/email#user_media)时保持选中状态。 :::

en-us	##### Step 1  Define new media.  The media will execute a script which will send required information to OpenView.
zh-cn	#####  第1步  定义新媒介。  媒介将执行一个脚本，将所需的信息发送到 OpenView。

en-us	##### Step 1  Defining a network discovery rule for our IP range.  ![](../../../../assets/en/manual/discovery/network_discovery/discovery.png)  Zabbix will try to discover hosts in the IP range of 192.168.1.1-192.168.1.254 by connecting to Zabbix agents and getting the value from the **system.uname** key. The value received from the agent can be used to name the hosts and also to apply different actions for different operating systems. For example, link Windows servers to the template *Windows*, Linux servers to the template *Linux*.  The rule will be executed every 10 minutes.  When this rule is added, Zabbix will automatically start the discovery and generation of the discovery-based events for further processing.
zh-cn	##### 第一步  给IP地址范围定义网络发现规则。  ![](../../../../assets/en/manual/discovery/network_discovery/discovery.png)  主机的发现机制是通过尝试连接主机上的Zabbix agent并获取 **system.uname** 这个键来实现的。从Zabbix agent获取到的值可以用于给主机命名以及为不同操作系统执行不同的动作。比如链接Windows服务器到 *Windows* 模板，链接Linux服务器到 *Linux* 模板。  规则每十分钟执行一次。   添加规则后，发现会自动执行，同时会产生相关事件。

en-us	##### Step 1  Install Kerberos package.  For Debian/Ubuntu:      apt install krb5-user  For RHEL:      dnf install krb5-workstation
zh-cn	##### 第1步  安装 Kerberos 包。  对于 Debian/Ubuntu：     apt install krb5-user  对于 RHEL：     dnf install krb5-workstation

en-us	##### Step 1  To define your own theme you'll need to create a CSS file and save it in the `assets/styles/` folder (for example, *custom-theme.css*). You can either copy the files from a different theme and create your theme based on it or start from scratch.
zh-cn	##### 步骤1  要定义您自己的主题，您需要创建一个 CSS 文件并将其保存在 `assets/styles/` 文件夹中（例如，*custom-theme.css*）。您可以从不同的主题复制文件并基于它创建主题，也可以从头开始。

en-us	##### Step 1  Write a script or command line to retrieve required parameter.  For example, we may write the following command in order to get total number of queries executed by a MySQL server:      mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  When executed, the command returns total number of SQL queries.
zh-cn	##### 第一步  写一个脚本或命令行以检测所需的参数。\  举个例子，我们编辑了下面的命令以获取 MySQL Server 执行的查询总数：      mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  这个命令执行后，将恢复返回 SQL 查询的总数。

en-us	##### Step 2  Add the command to zabbix\_agentd.conf:      UserParameter=mysql.questions,mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  **mysql.questions** is a unique identifier. It can be any valid key identifier, for example, *queries*.  Test this parameter by using Zabbix agent with "-t" flag (if running under root, however, note that the agent may have different permissions when launched as a daemon):      zabbix_agentd -t mysql.questions
zh-cn	##### 第二步  添加命令到 zabbix\_agentd.conf:      UserParameter=mysql.questions,mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  **mysql.questions** 作为key需要是唯一标识符。可以是任何有效的字符，比如*queries*。  通过使用带有 ‘-t’ 标识的 zabbix\_agentd命令测试此用户自定义参数的执行。（如果是以root用户运行，请注意agent与作为守护进程执行时的权限差异）：      zabbix_agentd -t mysql.questions

en-us	##### Step 2  Add your theme to the list of themes returned by the APP::getThemes() method. You can do this by overriding the ZBase::getThemes() method in the APP class. This can be done by adding the following code before the closing brace in *include/classes/core/APP.php*:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme')           ]);       }  ::: noteimportant Note that the name you specify within the first pair of quotes must match the name of the theme file without extension. :::  To add multiple themes, just list them under the first theme, for example:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme'),               'anothertheme' => _('Another theme'),               'onemoretheme' => _('One more theme')           ]);       }  Note that every theme except the last one must have a trailing comma.  ::: notetip To change graph colors, the entry must be added in the *graph\_theme* database table. :::
zh-cn	##### 步骤2  将您的主题添加到 APP::getThemes() 方法返回的主题列表中。您可以通过覆盖 APP 类中的 ZBase::getThemes() 方法来做到这一点。这可以通过在 *include/classes/core/APP.php* 的右大括号之前添加以下代码来完成：        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme')           ]);       }  ::: noteimportant 请注意，您在第一对引号中指定的名称必须与不带扩展名的主题文件的名称匹配。 :::  要添加多个主题，只需将它们列在第一个主题下即可，例如：        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme'),               'anothertheme' => _('Another theme'),               'onemoretheme' => _('One more theme')           ]);       }  请注意，除了最后一个主题之外的每个主题都必须有一个尾随逗号。  ::: notetip 要更改图形颜色，必须在 *graph\_theme* 数据库表中添加条目。 :::

en-us	##### Step 2  Configure Kerberos configuration file (see MIT documentation for details)  ``` {.java} cat /etc/krb5.conf  [libdefaults]     default_realm = EXAMPLE.COM  # The following krb5.conf variables are only for MIT Kerberos.     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```
zh-cn	##### 第2步  设置Kerberos配置文件 (看MIT详细文档)  ``` {.java} cat /etc/krb5.conf  [libdefaults]     default_realm = EXAMPLE.COM  # The following krb5.conf variables are only for MIT Kerberos.     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```

en-us	##### Step 2  Define new user.  The user has to be linked with the media.
zh-cn	##### 第2步  定义新用户。  用户必须与媒介链接。

en-us	##### Step 2  Define steps for the scenario.  Click on *Add* button in the *Steps* tab to add individual steps.  *Web scenario step 1*  We start by checking that the first page responds correctly, returns with HTTP response code 200 and contains text "Zabbix SIA".  ![](../../../assets/en/manual/web_monitoring/scen_step1.png){width="600"}  When done configuring the step, click on *Add*.  *Web scenario step 2*  We continue by logging in to the Zabbix frontend, and we do so by reusing the macros (variables) we defined on the scenario level - {user} and {password}.  ![](../../../assets/en/manual/web_monitoring/scen_step2.png){width="600"}  ::: noteimportant Note that Zabbix frontend uses JavaScript redirect when logging in, thus first we must log in, and only in further steps we may check for logged-in features. Additionally, the login step must use full URL to **index.php** file. :::  Take note also of how we are getting the content of the `{sid}` variable (session ID) using a variable syntax with regular expression: `regex:name="csrf-token" content="([0-9a-z]{16})"`. This variable will be required in step 4.  *Web scenario step 3*  Being logged in, we should now verify the fact. To do so, we check for a string that is only visible when logged in - for example, **Administration**.  ![](../../../assets/en/manual/web_monitoring/scen_step3.png){width="600"}  *Web scenario step 4*  Now that we have verified that frontend is accessible and we can log in and retrieve logged-in content, we should also log out - otherwise Zabbix database will become polluted with lots and lots of open session records.  ![](../../../assets/en/manual/web_monitoring/scen_step4.png){width="600"}  *Web scenario step 5*  We can also check that we have logged out by looking for the **Username** string.  ![](../../../assets/en/manual/web_monitoring/scen_step5.png){width="600"}  *Complete configuration of steps*  A complete configuration of web scenario steps should look like this:  ![](../../../assets/en/manual/web_monitoring/scenario_steps.png){width="600"}
zh-cn	##### 第2步  定义场景的步骤。  单击  *Steps（步骤）* 中的 *Add（添加）* 按钮以添加各个步骤。   *Web scenario step 1（Web 场景步骤 1）*  我们首先检查第一页是否正确响应，返回 HTTP 响应代码 200 并包含文本 "Zabbix SIA"。  ![](../../../assets/en/manual/web_monitoring/scen_step1.png){width="600"}  完成配置步骤后，单击 *Add（添加）*。  *Web scenario step 2（Web 场景步骤 2）*  我们继续登录 Zabbix 前端，并通过重用我们在场景级别定义的宏（变量） - {user} 和 {password}。  ![](../../../assets/en/manual/web_monitoring/scen_step2.png){width="600"}  ::: noteimportant 注意 Zabbix 前端在登录时使用 JavaScript 重定向，因此首先我们必须登录，并且只有在进一步的步骤中，我们才能检查已登录的功能。此外，登录步骤必须使用 **index.php** 文件的完整 URL。 :::  注意我们是如何使用正则表达式的变量语法 'regex:name="csrf-token" content="([0-9a-z]{16})" '获取 ' {sid} ' 变量 (会话ID) 的内容的。这个变量在步骤4中是必需的。  *Web 场景步骤 3*  登录后，我们应该验证。为此，我们检查仅在登录时可见的字符串，例如**Administration**。  ![](../../../assets/en/manual/web_monitoring/scen_step3.png){width="600"}  *Web 场景步骤 4*  已经验证了前端是可访问的并且可以登录并检索登录的内容，之后应该注销 - 否则 Zabbix 数据库将被大量打开的会话记录污染。  ![](../../../assets/en/manual/web_monitoring/scen_step4.png){width="600"}  *Web 场景步骤 5*  可以通过查找 **Username（用户名）** 字符串来确认是否已注销。  ![](../../../assets/en/manual/web_monitoring/scen_step5.png){width="600"}  *步骤的完整配置*  一个完整的 Web 场景步骤的配置如下所示：  ![](../../../assets/en/manual/web_monitoring/scenario_steps.png){width="600"}

en-us	##### Step 2  Defining a discovery [action](/manual/config/notifications/action) for adding the discovered Linux servers to the respective group/template.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action.png)  The action will be activated if:  -   the "Zabbix agent" service is "up" -   the value of system.uname (the Zabbix agent key we used in rule     definition) contains "Linux" -   Uptime is 1 hour (3600 seconds) or more  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_b.png)  The action will execute the following operations:  -   add the discovered host to the "Linux servers" group (and also add     host if it wasn't added previously) -   link host to the *Linux* template. Zabbix will automatically start     monitoring the host using items and triggers from the "Linux"     template.
zh-cn	##### 第二步  定义一个网络发现 [动作](/manual/config/notifications/action) ，用于 添加发现的Linux服务器到对应的组并链接到对应模板。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action.png)  同时满足下列条件才会使动作生效:  -   "Zabbix agent" 服务是已启动(up)状态的 -   system.uname(规则里定义的Zabbix agent的键)的值包含 "Linux"  -   运行时长(uptime)大于1小时(3600秒)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_b.png)  动作会执行下列操作:  -   添加发现的主机到 "Linux服务器" 组(如果之前主机不存在，则同时创建主机) -   链接主机到 *Linux* 模板。主机会自动纳入监控，监控使用 "Linux" 模板中的监控项和触发器

en-us	##### Step 2  Go to *Configuration → Actions* and select *Internal actions* from the page title dropdown.  ![](../../../../assets/en/manual/config/internal_actions.png){width="600"}  Click on *Create action* to the right to open an action configuration form.
zh-cn	##### 第二步  转到*配置→ 操作*并从页面标题下拉列表中选择*内部操作*。  ![](../../../../assets/en/manual/config/internal_actions.png){width=“600”}  单击右侧的*创建操作*打开操作配置表单。

en-us	##### Step 3  Activate the new theme.  In Zabbix frontend, you may either set this theme to be the default one or change your theme in the user profile.  Enjoy the new look and feel!
zh-cn	##### 步骤 3  激活新主题。  在 Zabbix 前端，您可以将此主题设置为默认主题，也可以在用户配置文件中更改您的主题。  享受新的外观和感觉！

en-us	##### Step 3  Configure actions.  Configure actions to send all (or selected) trigger status changes to the user.
zh-cn	##### 第3步  配置动作。  配置动作以将所有（或选定的）触发器状态更改发送给用户。

en-us	##### Step 3  Create a Kerberos ticket for user *zabbix*. Run the following command as user *zabbix*:      kinit zabbix  ::: noteimportant It is important to run the above command as user *zabbix*. If you run it as *root* the authentication will not work. :::
zh-cn	 ##### 第3步  创建*zabbix*用户的Kerberos ticket。使用*zabbix*执行命令：      kinit zabbix  ::: noteimportant 要使用*zabbix*用户执行以上命令。如果使用 root 用户将不会通过认证。 :::

en-us	##### Step 3  Defining a discovery action for adding the discovered Windows servers to the respective group/template.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win_b.png)
zh-cn	##### 第三步  定义网络发现动作，添加发现的Windows服务器到对应组并链接到对应模板。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win_b.png)

en-us	##### Step 3  In the **Action** tab enter a name for the action. Then click on *Add* in the condition block to add a new condition.  In the new condition popup window select *Event type* as the condition type and then select *Item in "not supported" state* as the event type value.  ![](../../../../assets/en/manual/config/notifications/action/report_unsupported_cond.png)  Don't forget to click on *Add* to actually list the condition in the *Conditions* block.
zh-cn	##### 第三步  在**操作**选项卡中输入操作的名称。然后单击条件块中的*Add*，添加一个新条件。  在新条件弹出窗口中，选择*事件类型*作为条件类型，然后选择*处于“不支持”状态的项目*作为事件类型值。  ![](../../../../assets/en/manual/config/notifications/action/report_unsupported_cond.png)  别忘了点击*Add*，在*Conditions*块中实际列出条件。

en-us	##### Step 3  Reload user parameters from the configuration file by running:      zabbix_agentd -R userparameter_reload  You may also restart the agent instead of the runtime control command.  Test the parameter by using [zabbix\_get](/manual/concepts/get) utility.
zh-cn	##### 第三步  通过如下方式重新加载用户自定义参数:      zabbix_agentd -R userparameter_reload  除了执行命令行，也可以重启agent来实现。  使用 [zabbix\_get](/manual/concepts/get) 程序测试该用户自定义参数。

en-us	##### Step 3  Save the finished web monitoring scenario.  The scenario will be added to a host. To view web scenario information go to *Monitoring → Hosts*, locate the host in the list and click on the Web hyperlink in the last column.  ![](../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  Click on the scenario name to see more detailed statistics:  ![](../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}
zh-cn	##### 步骤 3  保存完成的 Web 监控场景。  该场景将被添加到主机。要查看 Web 场景信息，请转到 *Monitoring（监控中） → Hosts（主机）*，在列表中找到主机，然后单击最后一列中的 Web 超链接。  ![](../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  点击场景名称可查看更详细的统计信息：  ![](../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}

en-us	##### Step 4  Add new item with Key=mysql.questions to the monitored host. Type of the item must be either Zabbix Agent or Zabbix Agent (active).  Be aware that type of returned values must be set correctly on Zabbix server. Otherwise Zabbix won't accept them.
zh-cn	##### 第四步  在被监控主机中添加使用key值为 ‘mysql.questions’的新监控项。监控项类型必须使用 Zabbix Agent 或 Zabbix Agent（Active）。\  注意在 Zabbix Server上。必须设置正确的返回值类型，否则Zabbix无法处理。\

en-us	##### Step 4  Create a web scenario or HTTP agent item with Kerberos authentication type.  Optionally can be tested with the following curl command:      curl -v --negotiate -u : http://example.com  Note that for lengthy web monitoring it is necessary to take care of renewing the Kerberos ticket. Default time of ticket expiration is 10h.
zh-cn	 ##### 第4步  创建具有Kerberos身份验证类型的web方案或HTTP代理监控项。  可以选择使用以下curl命令进行测试：      curl -v --negotiate -u : http://example.com  请注意，对于冗长的web监视，有必要更新Kerberos ticket。Kerberos ticket到期时间默认为10小时。

en-us	##### Step 4  Defining a discovery action for removing lost servers.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove_b.png)  A server will be removed if "Zabbix agent" service is 'down' for more than 24 hours (86400 seconds).
zh-cn	##### 第四步  定义网络发现动作，删除丢失的(lost)主机。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove_b.png)  如果 "Zabbix agent" 服务停止(down)时间超过24小时(86400秒)，则会删除对应主机。

en-us	##### Step 4  In the **Operations** tab, click on *Add* in the *Operations* block and select some recipients of the message (user groups/users) and the media types (or 'All') to use for delivery.  Select *Custom message* checkbox if you wish to enter the custom subject/content of the problem message.  ![](../../../../assets/en/manual/config/unsupp_operation.png)  ![](../../../../assets/en/manual/config/unsupp_operation_b.png)  Click on *Add* to actually list the operation in the *Operations* block.  If you wish to receive more than one notification, set the operation step duration (interval between messages sent) and add another step.
zh-cn	##### 第四步  在**操作**选项卡中，单击*Operations*块中的*Add*，然后选择邮件的一些收件人（用户组/用户）和用于传递的媒体类型（或“全部”）。  如果希望输入问题消息的自定义主题/内容，请选中“自定义消息”复选框。  ![](../../../../assets/en/manual/config/unsupp_operation.png) ![](../../../../assets/en/manual/config/unsupp_operation_b.png)  单击*添加*以实际列出*操作*块中的操作。  如果希望接收多个通知，请设置操作步骤持续时间（发送消息之间的间隔）并添加另一个步骤。

en-us	##### Step 4  Write media script.  The script will have the following logic. If trigger is ON, then execute OpenView command *opcmsg -id application=<application> msg\_grp=<msg\_grp> object=<object> msg\_text=<text>*. The command will return unique message ID which has to be stored somewhere, preferably in a new table of ZABBIX database. If trigger is OFF then *opcmack <message id>* has to be executed with message ID retrieved from the database.  Refer to OpenView official documentation for more details about opcmsg and opcmack. The media script is not given here.
zh-cn	##### 第4步  编写媒介脚本。  该脚本将具有以下逻辑。如果触发器为 ON，则执行 OpenView 命令 *opcmsg -id application=<application>msg\_grp=<msg\_grp> object=<object> msg\_text=<text>*。 该命令将返回必须存储在某处的唯一消息 ID，最好是在 ZABBIX 数据库的新表中。 如果触发器关闭 OFF ，则必须使用从数据库中检索到的消息 ID 执行 *opcmack <message id>* 。  有关 opcmsg 和 opcmack 的更多详细信息，请参阅 OpenView 官方文档。这里没有给出媒介脚本。

en-us	##### Step 5  The **Recovery operations** block allows to configure a recovery notification when an item goes back to the normal state. Click on *Add* in the *Recovery operations* block, select the operation type, the recipients of the message (user groups/users) and the media types (or 'All') to use for delivery.  Select *Custom message* checkbox if you wish to enter the custom subject/content of the problem message.  ![](../../../../assets/en/manual/config/unsupp_recovery.png)  Click on *Add* in the *Operation details* popup window to actually list the operation in the *Recovery operations* block.
zh-cn	#####第五步  **Recovery operations**块允许在项目返回正常状态时配置恢复通知。单击*恢复操作*块中的*添加*，选择操作类型、邮件收件人（用户组/用户）和用于传递的媒体类型（或“全部”）。  如果希望输入问题消息的自定义主题/内容，请选中“自定义消息”复选框。  ![](../../../../assets/en/manual/config/unsupp_recovery.png)  在*Operation details*弹出窗口中单击*Add*，以实际列出*Recovery operations*块中的操作。

en-us	##### Step 6  When finished, click on the **Add** button at the bottom of the form.  And that's it, you're done! Now you can look forward to receiving your first notification from Zabbix if some item turns unsupported.
zh-cn	##### 第六步  完成后，单击表单底部的**添加**按钮。  就这样，你完了！现在，如果某些项目变得不受支持，您可以期待从Zabbix收到第一次通知。

en-us	#### Steps
zh-cn	#### 步骤

en-us	### Steps  **1**. Download the plugin sources from [Zabbix Cloud Images and Appliances](https://cdn.zabbix.com/zabbix-agent2-plugins/sources/). The official download page will be available soon.  **2**. Transfer the archive to the machine where you are going to build the plugin.  **3**. Unarchive the tarball, e.g.:       tar xvf zabbix-agent2-plugin-postgresql-6.0.13.tar.gz  Make sure to replace "zabbix-agent2-plugin-postgresql-6.0.13.tar.gz" with the name of the downloaded archive.  **4**. Enter the extracted directory:      cd <path to directory>  **5**. Run:      make  **6**. The plugin executable may be placed anywhere as long as it is loadable by Zabbix agent 2. Specify the path to the plugin binary in the plugin configuration file, e.g. in postgresql.conf for the PostgreSQL plugin:      Plugins.PostgreSQL.System.Path=/path/to/executable/zabbix-agent2-plugin-postgresql  **7**. Path to the plugin configuration file must be specified in the Include parameter of the Zabbix agent 2 configuration file:      Include=/path/to/plugin/configuration/file/postgresql.conf
zh-cn	### 步骤  **1**. 从[Zabbix Cloud Images and Appliances](https://cdn.zabbix.com/zabbix-agent2-plugins/sources/)下载插件源码。 官方下载页面即将上线。  **2**. 将压缩包传输到您要构建插件的机器上。  **3**. 解压压缩包，例如:     tar xvf zabbix-agent2-plugin-postgresql-6.0.13.tar.gz  确保将“zabbix-agent2-plugin-postgresql-6.0.13.tar.gz”替换为下载存档的名称。  **4**. 进入解压后的目录：    cd <path to directory>  **5**. 运行:    make  **6**. 插件可执行文件可以放置在任何地方，只要它可以被 Zabbix agent 2 加载。在插件配置文件中指定插件二进制文件的路径，例如在PostgreSQL 插件的 postgresql.conf 中：    Plugins.PostgreSQL.System.Path=/path/to/executable/zabbix-agent2-plugin-postgresql  **7**. 必须在 Zabbix agent 2 配置文件的 Include 参数中指定插件配置文件的路径：    Include=/path/to/plugin/configuration/file/postgresql.conf

en-us	#### Stopping agent  To stop the agent service, you can use Control Panel or do it from command line.  To stop a single instance of Zabbix agent started with the default configuration file:       zabbix_agentd.exe --stop  To stop a single instance of Zabbix agent started with another configuration file:       zabbix_agentd.exe --config <your_configuration_file> --stop  To stop one of multiple instances of Zabbix agent:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --stop --multiple-agents
zh-cn	#### 停止 agent  要停止agent服务，可以使用"控制面板"或从命令行执行此操作.  使用默认配置文件停止单个实例的 Zabbix agent:       zabbix_agentd.exe --stop       指定配置文件停止单个实例的 Zabbix agent:       zabbix_agentd.exe --config <your_configuration_file> --stop  停止多个Zabbix agent实例的其中一个，请执行以下操作:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --stop --multiple-agents

en-us	#### Storage  Compose files are configured to support local storage on a host machine. Docker Compose will create a `zbx_env` directory in the folder with the compose file when you run Zabbix components using the compose file. The directory will contain the same structure as described above in the [Volumes](#Volumes) section and directory for database storage.  There are also volumes in read-only mode for `/etc/localtime` and `/etc/timezone` files.
zh-cn	#### 存储  Compose 文件已经配置为支持主机上的存储。当你使用 Compose 文件运行 Zabbix 组件时，Docker Compose 将在其所在文件夹中创建一个 `zbx_env` 目录，该目录将包含于 [Volumes](#Volumes) 章节所述相同的结构，以用于数据库存储。  此外，volume 下的文件 `/etc/localtime` 和 `/etc/timezone` 为只读模式。

en-us	#### Storing history data in multiple date-based indices  This section describes additional steps required to work with pipelines and ingest nodes.  To begin with, you must create templates for indices.  The ​following example shows a request for creating uint template:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/uint_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "uint*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "type": "long"          }       }    } }' ```  To create other templates, user should change the URL (last part is the name of template), change `"​index_patterns"`​ field to match index name and to set valid mapping, which can be taken from `​database/​elasticsearch/​elasticsearch.map`​.  For example, the following command can be used to create a template for text index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/text_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "text*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "fields": {                "analyzed": {                   "index": true,                   "type": "text",                   "analyzer": "standard"                }             },             "index": false,             "type": "text"          }       }    } }' ```  This is required to allow Elasticsearch to set valid mapping for indices created automatically. Then it is required to create the pipeline definition. Pipeline is some sort of preprocessing of data before putting data in indices. The following command can be used to create pipeline for uint index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_ingest/pipeline/uint-pipeline \  -H 'content-type:application/json' \  -d '{    "description": "daily uint index naming",    "processors": [       {          "date_index_name": {             "field": "clock",             "date_formats": [                "UNIX"             ],             "index_name_prefix": "uint-",             "date_rounding": "d"          }       }    ] }' ```  User can change the rounding parameter ("date\_rounding") to set a specific index rotation period. To create other pipelines, user should change the URL (last part is the name of pipeline) and change "index\_name\_prefix" field to match index name.  See also [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/master/date-index-name-processor.html).  Additionally, storing history data in multiple date-based indices should also be enabled in the new parameter in Zabbix server configuration:      ### Option: HistoryStorageDateIndex     # Enable preprocessing of history values in history storage to store values in different indices based on date.     # 0 - disable     # 1 - enable     #     # Mandatory: no     # Default:     # HistoryStorageDateIndex=0  
zh-cn	##### Zabbix server 和前端  

en-us	#### Storing history data in multiple date-based indices  This section describes additional steps required to work with pipelines and ingest nodes.  To begin with, you must create templates for indices.  The following example shows a request for creating uint template:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/uint_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "uint*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "type": "long"          }       }    } }' ```  To create other templates, user should change the URL (last part is the name of template), change `"index_patterns"` field to match index name and to set valid mapping, which can be taken from `database/elasticsearch/elasticsearch.map`.  For example, the following command can be used to create a template for text index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/text_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "text*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "fields": {                "analyzed": {                   "index": true,                   "type": "text",                   "analyzer": "standard"                }             },             "index": false,             "type": "text"          }       }    } }' ```  This is required to allow Elasticsearch to set valid mapping for indices created automatically. Then it is required to create the pipeline definition. Pipeline is some sort of preprocessing of data before putting data in indices. The following command can be used to create pipeline for uint index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_ingest/pipeline/uint-pipeline \  -H 'content-type:application/json' \  -d '{    "description": "daily uint index naming",    "processors": [       {          "date_index_name": {             "field": "clock",             "date_formats": [                "UNIX"             ],             "index_name_prefix": "uint-",             "date_rounding": "d"          }       }    ] }' ```  User can change the rounding parameter ("date\_rounding") to set a specific index rotation period. To create other pipelines, user should change the URL (last part is the name of pipeline) and change "index\_name\_prefix" field to match index name.  See also [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/master/date-index-name-processor.html).  Additionally, storing history data in multiple date-based indices should also be enabled in the new parameter in Zabbix server configuration:      ### Option: HistoryStorageDateIndex     # Enable preprocessing of history values in history storage to store values in different indices based on date.     # 0 - disable     # 1 - enable     #     # Mandatory: no     # Default:     # HistoryStorageDateIndex=0
zh-cn	#### 将历史数据存储在多个基于日期的索引中  本节介绍使用管道和引入节点所需的其他步骤。 首先，必须为索引创建模板。 以下示例为创建 uint 模板的请求：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/uint_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "uint*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "type": "long"          }       }    } }' ``` 要创建其他模板，用户应更改URL（最后一部分是模板的名称），更改`"index_patterns"`字段以匹配索引名称并设置有效的映射，这可以在`database/elasticsearch/elasticsearch.map`获取。 以下命令可用于为文本索引创建模板，例如：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/text_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "text*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "fields": {                "analyzed": {                   "index": true,                   "type": "text",                   "analyzer": "standard"                }             },             "index": false,             "type": "text"          }       }    } }' ``` 这是允许 Elasticsearch 为自动创建的索引设置有效的映射所必需做的。然后需要创建pipeline定义。pipeline是在将数据放入索引之前对数据的某种预处理。以下命令可用于为 uint 索引创建pipeline：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_ingest/pipeline/uint-pipeline \  -H 'content-type:application/json' \  -d '{    "description": "daily uint index naming",    "processors": [       {          "date_index_name": {             "field": "clock",             "date_formats": [                "UNIX"             ],             "index_name_prefix": "uint-",             "date_rounding": "d"          }       }    ] }' ``` 用户可以更改参数("date\_rounding")以设置特定的索引轮换周期。要创建其他pipelines，用户应更改 URL（最后一部分是pipelines的名称）并更改"index\_name\_prefix"字段以匹配索引名称 另见 [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/master/date-index-name-processor.html). 此外，在Zabbix服务器新的配置参数中，还应启用将历史数据存储在多个基于日期的索引中：      ### Option: HistoryStorageDateIndex     # Enable preprocessing of history values in history storage to store values in different indices based on date.     # 0 - disable     # 1 - enable     #     # Mandatory: no     # Default:     # HistoryStorageDateIndex=0

en-us	##### String functions [String function](/manual/appendix/functions/history) **concat** now allows concatenating more than two parameters. It can be used to combine strings and values in different combinations or append two or more values to each other. Numeric data types are also supported. 
zh-cn	##### 字符串函数  [字符串函数](/manual/appendix/functions/history) **concat** 允许连接两个以上的参数。它可用于以不同的组合组合字符串和值，或将两个或多个值相互附加。还支持数字数据类型。

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

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

en-us	#### Strings  Strings should be enclosed with single ' or double " quotes. Inside the strings, single or double quotes (depending on which are used to enclose it) and backslashes `\` are escaped with the backslash `\` character.  
zh-cn	#### 字符串  字符串应该用单 ' 或双 " 引号括起来。在字符串内，单引号或双引号（取决于使用哪个引号括起来）和反斜杠 `\` 用反斜杠 `\` 字符转义。

en-us	#### Structure  All Zabbix components are available in the following Docker repositories:  -   Zabbix agent -     [zabbix/zabbix-agent](https://hub.docker.com/r/zabbix/zabbix-agent/) -   Zabbix server     -   Zabbix server with MySQL database support -         [zabbix/zabbix-server-mysql](https://hub.docker.com/r/zabbix/zabbix-server-mysql/)     -   Zabbix server with PostgreSQL database support -         [zabbix/zabbix-server-pgsql](https://hub.docker.com/r/zabbix/zabbix-server-pgsql/) -   Zabbix web-interface     -   Zabbix web-interface based on Apache2 web server with MySQL         database support -         [zabbix/zabbix-web-apache-mysql](https://hub.docker.com/r/zabbix/zabbix-web-apache-mysql/)     -   Zabbix web-interface based on Apache2 web server with PostgreSQL         database support -         [zabbix/zabbix-web-apache-pgsql](https://hub.docker.com/r/zabbix/zabbix-web-apache-pgsql/)     -   Zabbix web-interface based on Nginx web server with MySQL         database support -         [zabbix/zabbix-web-nginx-mysql](https://hub.docker.com/r/zabbix/zabbix-web-nginx-mysql/)     -   Zabbix web-interface based on Nginx web server with PostgreSQL         database support -         [zabbix/zabbix-web-nginx-pgsql](https://hub.docker.com/r/zabbix/zabbix-web-nginx-pgsql/) -   Zabbix proxy     -   Zabbix proxy with SQLite3 database support -         [zabbix/zabbix-proxy-sqlite3](https://hub.docker.com/r/zabbix/zabbix-proxy-sqlite3/)     -   Zabbix proxy with MySQL database support -         [zabbix/zabbix-proxy-mysql](https://hub.docker.com/r/zabbix/zabbix-proxy-mysql/) -   Zabbix Java Gateway -     [zabbix/zabbix-java-gateway](https://hub.docker.com/r/zabbix/zabbix-java-gateway/)  Additionally there is SNMP trap support. It is provided as additional repository ([zabbix/zabbix-snmptraps](https://hub.docker.com/r/zabbix/zabbix-snmptraps/)) based on Ubuntu Trusty only. It could be linked with Zabbix server and Zabbix proxy.
zh-cn	#### 结构  所有 Zabbix 组件在以下 Docker 存储库中可用：  -   Zabbix agent -     [zabbix/zabbix-agent](https://hub.docker.com/r/zabbix/zabbix-agent/) -   Zabbix server     -   支持 MySQL 数据库的 Zabbix server -         [zabbix/zabbix-server-mysql](https://hub.docker.com/r/zabbix/zabbix-server-mysql/)     -   支持 PostgreSQL 数据库的 Zabbix server -         [zabbix/zabbix-server-pgsql](https://hub.docker.com/r/zabbix/zabbix-server-pgsql/) -   Zabbix web界面     -   基于Apache2 Web服务器 的 Zabbix web 界面，支持 MySQL 数据库 -         [zabbix/zabbix-web-apache-mysql](https://hub.docker.com/r/zabbix/zabbix-web-apache-mysql/)     -   基于Apache2 Web服务器 的 Zabbix web 界面，支持 PostgreSQL 数据库 -         [zabbix/zabbix-web-apache-pgsql](https://hub.docker.com/r/zabbix/zabbix-web-apache-pgsql/)     -   基于Nginx Web服务器 的 Zabbix web 界面，支持 MySQL 数据库 -         [zabbix/zabbix-web-nginx-mysql](https://hub.docker.com/r/zabbix/zabbix-web-nginx-mysql/)     -   基于Nginx Web服务器 的 Zabbix web 界面，支持 PostgreSQL 数据库 -         [zabbix/zabbix-web-nginx-pgsql](https://hub.docker.com/r/zabbix/zabbix-web-nginx-pgsql/) -   Zabbix proxy     -   Zabbix proxy ，支持 SQLite3 数据库 -         [zabbix/zabbix-proxy-sqlite3](https://hub.docker.com/r/zabbix/zabbix-proxy-sqlite3/)     -   Zabbix proxy， 支持 MySQL 数据库 -         [zabbix/zabbix-proxy-mysql](https://hub.docker.com/r/zabbix/zabbix-proxy-mysql/) -   Zabbix Java 网关 -     [zabbix/zabbix-java-gateway](https://hub.docker.com/r/zabbix/zabbix-java-gateway/)  此外，还有 SNMP trap 支持。它仅作为基于 Ubuntu Trusty 的附加存储库 ([zabbix/zabbix-snmptraps](https://hub.docker.com/r/zabbix/zabbix-snmptraps/)) 提供。它可以与 Zabbix server 和 Zabbix proxy 链接。

en-us	### Structure  The API consists of a number of methods that are nominally grouped into separate APIs. Each of the methods performs one specific task. For example, the `host.create` method belongs to the *host* API and is used to create new hosts. Historically, APIs are sometimes referred to as "classes".  ::: notetip Most APIs contain at least four methods: `get`, `create`, `update` and `delete` for retrieving, creating, updating and deleting data respectively, but some of the APIs may provide a totally different set of methods. :::
zh-cn	### 结构  Zabbix API 由许多名义上分组的独立 API 方法组成。每个方法执行一个特定任务。例如，方法 `host.create` 隶属于 *host* 这个 API 分组 ，用于创建新主机。历史上，API 分组有时被称为 "classes"。  ::: notetip 大多数API至少包含四种方法：`get`,`create`, `update` 和 `delete` ，分别是检索，创建，更新和删除数据，但是某些API提供一套完全不同的方法。 :::

en-us	#### Structure  The content of this manual is divided into sections and subsections to provide easy access to particular subjects of interest.  When you navigate to respective sections, make sure that you expand section folders to reveal full content of what is included in subsections and individual pages.  Cross-linking between pages of related content is provided as much as possible to make sure that relevant information is not missed by the users.
zh-cn	#### 结构  本手册的内容分为多个部分和小节，以便您轻松访问感兴趣的特定主题。  当您导航到各个部分时，请确保展开部分文件夹以显示子文件和各个页面中包含的全部内容。  手册尽可能提供相关内容页面之间的交叉链接，以确保用户不会错过相关信息。

en-us	 #### Structure  The header consists of four fields. All numbers in the header are formatted as little-endian.  |Field|Size|Size<br>(large packet)|Description| |--|-|-|------| |`<PROTOCOL>`|4|4|`"ZBXD"` or `5A 42 58 44`| |`<FLAGS>`|1|1|Protocol flags:<br>`0x01` - Zabbix communications protocol<br>`0x02` - compression<br>`0x04` - large packet| |`<DATALEN>`|4|8|Data length.| |`<RESERVED>`|4|8|When compression is used (`0x02` flag) - the length of uncompressed data<br>When compression is not used - `00 00 00 00`|
zh-cn	#### 结构  标头由四个字段组成。 标头中的所有数字都采用小端格式。  |字段|大小|大小<br>（大包）|描述| |---|---|---|------| |`<PROTOCOL>`|4|4|`"ZBXD"` 或 `5A 42 58 44`| |`<FLAGS>`|1|1|协议标志：<br>`0x01` - Zabbix 通信协议<br>`0x02` - 压缩<br>`0x04` - 大数据包| |`<DATALEN>`|4|8|数据长度。| |`<RESERVED>`|4|8|使用压缩时（`0x02` 标志）- 未压缩数据的长度<br>不使用压缩时- `00 00 00 00`|

en-us	##### Substring extraction in trigger tags  Substring extraction is supported for populating the tag name or tag value, using a macro [function](/manual/config/macros/macro_functions) - applying a regular expression to the value obtained by the {ITEM.VALUE}, {ITEM.LASTVALUE} macro or a low-level discovery macro. For example:      {{ITEM.VALUE}.regsub(pattern, output)}     {{ITEM.VALUE}.iregsub(pattern, output)}      {{#LLDMACRO}.regsub(pattern, output)}     {{#LLDMACRO}.iregsub(pattern, output)}  Tag name and value will be cut to 255 characters if their length exceeds 255 characters after macro resolution.  See also: Using macro functions in [low-level discovery macros](/manual/config/macros/lld_macros#using_macro_functions) for event tagging.
zh-cn	##### 触发器标签中提取子字符串  支持提取子字符串以填充标签名称或标签值，使用宏 [function](/manual/config/macros/macro_functions) -将正则表达式应用于 {ITEM.VALUE}，{ITEM.LASTVALUE} 宏或低级发现宏所获得的值。例如：      {{ITEM.VALUE}.regsub（pattern，output）}     {{ITEM.VALUE}.iregsub（pattern，output）}      {{#LLDMACRO}.regsub（pattern，output）}     {{#LLDMACRO}.iregsub（pattern，output）}  如果标签名和标签值的宏被解析后长度超过255 个字符，标记名和值将被切割为255个字符。  另请参阅：在 [低级发现宏](/manual/config/macros/lld_macros#using_macro_functions)使用宏函数来实现事件标记。

en-us	#### Supported agents 2  Older Zabbix agents 2 from version 4.4 onwards are compatible with Zabbix 6.0; Zabbix agent 2 must not be newer than 6.0.  Note that when using Zabbix agent 2 versions 4.4 and 5.0, the default interval of 10 minutes is used for refreshing unsupported items.  To take full advantage of the latest metrics, improved performance and reduced memory usage, use the latest supported agent 2.
zh-cn	####  支持的 agents 2  从 4.4 版开始的旧Zabbix agents 2 与 Zabbix 6.0 兼容；Zabbix agent 2不得高于 6.0。  请注意，当使用 Zabbix agent 2 版本 4.4 和 5.0 时，不支持的监控项默认刷新间隔 为10 分钟。  为了充分利用最新的指标、改进的性能和减少的内存使用，请使用最新支持的 agent 2。