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

en-us	The **Axes** tab allows to customize how axes are displayed:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_axes.png)  |   |   | |---|---| |*Left Y*|Mark this checkbox to make left Y-axis visible. The checkbox may be disabled if unselected either in *Data set* or in *Overrides* tab.| |*Right Y*|Mark this checkbox to make right Y-axis visible. The checkbox may be disabled if unselected either in *Data set* or in *Overrides* tab.| |*X-Axis*|Unmark this checkbox to hide X-axis (marked by default).| |*Min*|Set the minimum value of the corresponding axis. Visible range minimum value of Y-axis is specified.| |*Max*|Set the maximum value of the corresponding axis. Visible range maximum value of Y-axis is specified.| |*Units*|Choose the unit for the graph axis values from the dropdown. If the *Auto* option is chosen axis values are displayed using units of the first item of the corresponding axis. *Static* option allows you to assign the corresponding axis' custom name. If the *Static* option is chosen and the *value* input field left blank the corresponding axis' name will only consist of a numeric value.|
zh-cn	**轴**选项卡允许自定义轴的显示方式：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_axes.png)  | | | |---|---| |*左 Y*|勾选复选框使左Y轴可见。如果在*数据集*或*覆盖*选项卡中没有选择，该复选框可能会被禁用。| |*右 Y*|勾选复选框，使右Y轴可见。如果在*数据集*或*覆盖*选项卡中没有选择，该复选框可能被禁用。| |*X-Axis*|取消该复选框可以隐藏X轴（默认为勾选）。| |*Min*|设置相应轴的最小值。指定Y轴的可视范围最小值。| |*Max*|设置对应轴的最大值。 | 指定了 Y 轴的可视范围最大值。 |*Units*|从下拉菜单中选择图轴数值的单位。如果选择了*自动*选项，轴值将使用相应轴的第一个监控项的单位来显示。*静态*选项允许你指定相应轴的自定义*名称*。如果选择了*静态*选项，并且字段留空，那么相应轴的名称仅显示数值。|

en-us	The **Displaying options** tab allows to define history data selection:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_displaying_options.png)  |   |   | |---|---| |*History data selection*|Set the source of graph data:<br>**Auto** - data are sourced according to the classic graph [algorithm](/manual/config/visualization/graphs/simple#generating_from_historytrends) (default)<br>**History** - data from history<br>**Trends** - data from trends|
zh-cn	**显示选项**选项卡允许定义历史数据选择：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_displaying_options.png)  | | | |---|---| |*历史数据选择*|设置图表数据来源：<br>**Auto** -  数据的来源是根据经典的图表[算法](/manual/config/visualization/graphs/simple#generating_from_historytrends) (默认)<br>**History** - 来自历史的数据<br>**Trends** - 来自趋势的数据|

en-us	# 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	 # 以下 krb5.conf 变量仅适用于 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	The **Legend** tab allows to customize the graph legend:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_legend.png)  |   |   | |---|---| |*Show legend*|Unmark this checkbox to hide the legend on the graph (marked by default).| |*Number of rows*|Set the number of rows to be displayed on the graph.|
zh-cn	**图例** 选项卡允许自定义图形图例：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_legend.png)  | | | |---|---| |*显示图例*|选中启用查看图例（默认）。| |*行数*|设置要在图表上显示的行数。|

en-us	The **Overrides** tab allows to add custom overrides for data sets:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_overrides.png){width="600"}  Overrides are useful when several items are selected for a data set using the `*` wildcard and you want to change how the items are displayed by default (e.g. default base color or any other property).  Existing overrides (if any) are displayed in a list. To add a new override:  -   Click on the     ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_override.png)     button -   Select hosts and items for the override. Alternatively, you may     enter host and item patterns. Wildcard patterns may be used (for     example, `*` will return results that match zero or more     characters). To specify a wildcard pattern, just enter the string     manually and press *Enter*. While you are typing, note how all     matching hosts are displayed in the dropdown. The wildcard symbol is     always interpreted, therefore it is not possible to add, for     example, an item named "item\*" individually if there are other     matching items (e.g. item2, item3). Host pattern and item pattern     fields are mandatory. -   Click on     ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_override2.png),     to select override parameters. At least one override parameter     should be selected. For parameter descriptions, see the *Data set*     tab above.  Information displayed by the graph widget can be downloaded as a .png image using the [widget menu](/manual/web_interface/frontend_sections/monitoring/dashboard#widget_menu):  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/graph_widget_as_png.png)  A screenshot of the widget will be saved to the Downloads folder.
zh-cn	**覆盖** 选项卡允许为数据集添加自定义覆盖：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_overrides.png){width="600"}  当使用*通配符为一个数据集选择了几个监控项，而你想改变这些监控项的默认显示方式（如默认的底色或任何其他属性）时，可以通过覆盖实现。  现有的覆盖（如果有的话）会显示在一个列表中。要添加一个新的覆盖：  - 点击    ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_override.png)    按钮 - 选择要在图表显示的主机和监控项，你也可以用主机和项目标签，支持通配符（例如，*将返回匹配零个或更多字符的结果）。要使用通配只需要输入特定文本再按下回车。当你输入的时候，所有匹配的主机会在下拉框显示。通配符不可以被添加，因为它会被解析。例如一个项目为"item*" ，如果存在匹配项也会显示（例如item2, item3）。主机参数和监控项参数必填。 - 点击 ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_override2.png)以选择覆盖参数。至少应选择一个覆盖参数。关于参数描述，见上面的数据集标签。  图表组件显示的信息可以通过 [组件菜单](/manual/web_interface/frontend_sections/monitoring/dashboard#widget_menu):保存 .png 图片：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/graph_widget_as_png.png)  组件的截图将被保存到浏览器的“下载”文件夹。

en-us	The **Problems** tab allows to customize the problem display:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_problems.png)  |   |   | |---|---| |*Show problems*|Mark this checkbox to enable problem displaying on the graph (unmarked, i.e. disabled by default).| |*Selected items only*|Mark this checkbox to include problems for the selected items only to be displayed on the graph.| |*Problem hosts*|Select the problem hosts to be displayed on the graph. Wildcard patterns may be used (for example, `*` will return results that match zero or more characters). To specify a wildcard pattern, just enter the string manually and press *Enter*. While you are typing, note how all matching hosts are displayed in the dropdown.| |*Severity*|Mark the problem severities to be displayed on the graph.| |*Problem*|Specify the problem's name to be displayed on the graph.| |*Tags*|Specify problem tags to limit the number of problems displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met|
zh-cn	**问题** 选项卡允许自定义问题显示：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_problems.png)  | | | |---|---| |*显示问题*|选中启用复选框，使问题显示在图表上（默认为禁用）。| |*仅选择的监控项*|选中启用复选框只显示选定监控项的问题在图表上。| |*问题主机*|选择要在图表上显示的问题主机。可以使用通配符模式（例如，*将返回匹配零个或更多字符的结果）要使用通配只需要输入特定文本再按下回车。当你输入的时候，所有匹配的主机会在下拉框显示。| |*严重性*|标记要在图表上显示的问题严重程度。| |*问题*|指定要在图表上显示的问题名称。| |*标签*|可以通过包括以及排除特定的标签和标签值的方法，指定标签以限制组件中同时显示的Web 监控项的数量。标签名称匹配区分大小写。<br>可以通过以下运算符对每个条件进行筛选：<br>**Exists** - 存在特定的标签名称<br>**Equals** - 存在特定的标签名称和值（区分大小写）<br>**Contains** - 输入的字符串存在特定的标签名称（通配，不区分大小写）<br>**Does not exist** - 排除存在特定的标签名称<br>**Does not equal ** - 排除存在特定的标签名称和值（区分大小写）<br>**Does not contain ** - 排除输入的字符串存在特定的标签名称（通配，不区分大小写）<br>支持两种运算方式：<br>**And/Or** - 所有条件同时满足，标签名相同的条件将按Or条件分组<br >**Or** - 满足任意条件即可|

en-us	##### The syntax  A special syntax for OID is used:  **<OID of data>\["index","<base OID of index>","<string to search for>"\]**  |Parameter|Description| |---------|-----------| |OID of data|Main OID to use for data retrieval on the item.| |index|Method of processing. Currently one method is supported:<br>**index** – search for index and append it to the data OID| |base OID of index|This OID will be looked up to get the index value corresponding to the string.| |string to search for|The string to use for an exact match with a value when doing lookup. Case sensitive.|
zh-cn	##### 语法  使用OID的特殊语法：  **<OID of data>\["index","<base OID of index>","<string to search for>"\]**  |参数|描述 | |----------------------------|-| |OID of data|主OID用于监控项上的数据检索。| |index |处理方法。目前支持一种方法：<br>**index** – 搜索索引，并将其附加到数据OID| |base OID of index|该OID将被搜索以获取与该字符串对应的索引值。| |string to search for|用于在进行查找时与值精确匹配的字符串。区分大小写。|

en-us	 The **Tags** tab contains [service-level tags](#service-tags). Service-level tags are  used to identify a service. Tags of this type are not used to map  problems to the service (for that, use *[Problem tags](#problem-tags)* from the first tab).  The **Child services** tab allows to specify dependant services. Click on *Add* to add a service from the list of existing services. If you want to add a new child service, save this service first, then click on a plus icon next to the service that you have just created. 
zh-cn	**Tags** 选项卡包含 [服务级别标签](#服务标签)。服务级别标签用于标识服务。这种类型的标签不用于将问题映射到服务（为此，使用第一个选项卡中的 *[问题标签](#问题标签)*）。  **Child services** 选项卡允许指定依赖服务。单击  *Add* 从现有服务列表中添加服务。如果要添加新的子服务，请先保存此服务，然后单击刚刚创建的服务旁边的加号图标。

en-us	 The template [*Oracle by Zabbix agent 2*](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2?at=refs%2Fheads%2Frelease%2F6.0) has been updated (multiple static items removed; multiple item prototypes added) according to the changes made to multiple [Zabbix agent 2 items](#query-separate-tablespaces-in-oracle-databases-with-zabbix-agent-2).  For more information about the updates, see [Template changes](/manual/installation/template_changes#changes-in-6.0.13).
zh-cn	模板 [*Oracle by Zabbix agent 2*](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2?at=refs%2Fheads%2Frelease%2F6.0) 已根据对多个 [Zabbix agent 2 监控项](#query-separate-tablespaces-in-oracle-databases-with-zabbix-agent-2) 所做的更改进行了更新（删除了多个静态监控项；添加了多个监控项原型）。  有关更新的更多信息，请参阅[模板变更](/manual/installation/template_changes#changes-in-6.0.13)。

en-us	 The template [*Oracle by Zabbix agent 2*](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2?at=refs%2Fheads%2Frelease%2F6.0) has been updated:  -   The following static items, that requested data for all existing relevant DB objects in a single query, have been removed:     -   "Oracle: Get archive log info"     -   "Oracle: Get ASM stats"     -   "Oracle: Get CDB and No-CDB info"     -   "Oracle: Get PDB info"     -   "Oracle: Get tablespaces stats"  -   The following agent item prototypes have been added to the corresponding discovery rules:     -   Archive log discovery rule: "Archivelog '{#DEST_NAME}': Get archive log info"     -   ASM disk groups discovery: "ASM '{#DGNAME}': Get ASM stats"     -   Database discovery: "Oracle Database '{#DBNAME}': Get CDB and No-CDB info"     -   PDB discovery: "Oracle Database '{#DBNAME}': Get PDB info"     -   Tablespace discovery: "Oracle TBS '{#TABLESPACE}': Get tablespace stats"
zh-cn	模板 [*Oracle by Zabbix agent 2*](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2?at=refs%2Fheads%2Frelease%2F6.0) 已经升级了：  - 已删除以下静态监控项，这些监控项在单个查询中请求所有现有相关数据库对象的数据：    - “Oracle：获取归档日志信息”    - “Oracle：获取 ASM 统计信息”    - “Oracle：获取 CDB 和 No-CDB 信息”    - “Oracle：获取 PDB 信息”    - “Oracle：获取表空间统计信息”  - 以下agent监控项原型已添加到相应的发现规则中：    - 归档日志发现规则：“Archivelog '{#DEST_NAME}'：获取归档日志信息”    - ASM 磁盘组发现：“ASM '{#DGNAME}'：获取 ASM 统计信息”    - 数据库发现：“Oracle 数据库‘{#DBNAME}’：获取 CDB 和非 CDB 信息”    - PDB 发现：“Oracle 数据库‘{#DBNAME}’：获取 PDB 信息”    - 表空间发现：“Oracle TBS '{#TABLESPACE}'：获取表空间统计信息”

en-us	The **Time period** tab allows to set a custom time period:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_time_period.png)  |   |   | |---|---| |*Set custom time period*|Mark this checkbox to set the custom time period for the graph (unmarked by default).| |*From*|Set the start time of the custom time period for the graph.| |*To*|Set the end time of the custom time period for the graph.|
zh-cn	**时间段**选项卡允许设置一个自定义的时间段：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_time_period.png)  | | | |---|---| |*设置自定义时间段*|勾选此复选框以设置图表的自定义时间段（默认未勾选）。| |*From*|设置图表的自定义时间段的开始时间。| |*To*|设置图表的自定义时间段的结束时间。|

en-us	##### Third-party external surrounding software  Mandatory requirements are needed always. Optional requirements are needed for the support of the specific function.  |Software|Mandatory status|Supported versions|Comments| |--|-|-|------| |*MySQL/Percona*|One of|8.0.X|Required if MySQL (or Percona) is used as Zabbix backend database. InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*MariaDB*|^|10.5.00-10.8.X|InnoDB engine is required. We recommend using the [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) library for building server/proxy.| |*Oracle*|^|19c - 21c|Required if Oracle is used as Zabbix backend database.| |*PostgreSQL*|^|13.0-15.X|Required if PostgreSQL is used as Zabbix backend database.<br>PostgreSQL 15 is supported since Zabbix 6.0.10.| |*TimescaleDB* for PostgreSQL|^|2.0.1-2.8|Required if TimescaleDB is used as a PostgreSQL database extension. Make sure to install TimescaleDB Community Edition, which supports compression.<br>Note that TimescaleDB **does not** support PostgreSQL 15 yet.| |*SQLite*|Optional|3.3.5-3.34.X|SQLite is only supported with Zabbix proxies. Required if SQLite is used as Zabbix proxy database.| |*smartmontools*|^|7.1 or later|Required for Zabbix agent 2.| |*who*|^| |Required for the user count plugin.| |*dpkg*|^| |Required for the system.sw.packages plugin.| |*pkgtool*|^| |Required for the system.sw.packages plugin.| |*rpm*|^| |Required for the system.sw.packages plugin.| |*pacman*|^| |Required for the system.sw.packages plugin.|  ::: noteclassic  Although Zabbix can work with databases available in the operating systems, for the best experience, we recommend using databases installed from the official database developer repositories.  :::
zh-cn	#####第三方外部周边软件  总是需要强制性要求。 特定功能的支持需要可选需求。  |软件|强制状态|支持版本|注释| |--|-|-|------| |*MySQL/Percona*||8.0.X 之一|如果 MySQL（或 Percona）用作 Zabbix 后端数据库，则为必需。 需要 InnoDB 引擎。 我们建议使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 库来构建server/proxy。| |*MariaDB*|^|10.5.00-10.8.X|InnoDB 引擎是必需的。 我们建议使用 [MariaDB Connector/C](https://downloads.mariadb.org/connector-c/) 库来构建server/proxy。| |*Oracle*|^|19c - 21c|如果将 Oracle 用作 Zabbix 后端数据库，则为必需。| |*PostgreSQL*|^|13.0-15.X|如果将 PostgreSQL 用作 Zabbix 后端数据库，则为必需。<br>自 Zabbix 6.0.10 起支持 PostgreSQL 15。| |*TimescaleDB* for PostgreSQL|^|2.0.1-2.8|如果将 TimescaleDB 用作 PostgreSQL 数据库扩展，则为必需。 确保安装支持压缩的 TimescaleDB Community Edition。<br>请注意，TimescaleDB **还不**支持 PostgreSQL 15。| |*SQLite*|可选|3.3.5-3.34.X|SQLite 仅支持 Zabbix 代理。 如果 SQLite 用作 Zabbix 代理数据库，则需要。| |*smartmontools*|^|7.1 或更高版本|Zabbix agent 2 需要。| |*who*|^| |用户计数插件需要。| |*dpkg*|^| |system.sw.packages 插件需要。| |*pkgtool*|^| |system.sw.packages 插件需要。| |*rpm*|^| |system.sw.packages 插件需要。| |*pacman*|^| |system.sw.packages 插件需要。|  ::: noteclassic   虽然 Zabbix 可以使用操作系统中可用的数据库，但为了获得最佳体验，我们建议使用从官方数据库开发人员存储库安装的数据库。 ::::

en-us	##### Threads cannot be selected with `cmdline` parameter in `proc.mem[]` and `proc.num[]` items  Let's take as an example one of kernel threads:      $ ps -ef| grep kthreadd     root         2     0  0 09:33 ?        00:00:00 [kthreadd]  It can be selected with process `name` parameter:      $ zabbix_get -s localhost -k 'proc.num[kthreadd,root]'     1  But selection by process `cmdline` parameter does not work:      $ zabbix_get -s localhost -k 'proc.num[,root,,kthreadd]'     0  The reason is that Zabbix agent takes the regular expression specified in `cmdline` parameter and applies it to contents of process `/proc/<pid>/cmdline`. For kernel threads their `/proc/<pid>/cmdline` files are empty. So, `cmdline` parameter never matches.
zh-cn	 #####  `proc.mem[]`  和  `proc.num[]`  监控项中的  `cmdline`  参数不可以使用线程  让我们以内核线程为例:      $ ps -ef| grep kthreadd     root         2     0  0 09:33 ?        00:00:00 [kthreadd]  可以用进程 `名称` 参数选择:      $ zabbix_get -s localhost -k 'proc.num[kthreadd,root]'     1  但使用进程`cmdline`  参数就不起作用:       $ zabbix_get -s localhost -k 'proc.num[,root,,kthreadd]'     0  原因是Zabbix agent采用“cmdline”参数中指定的正则表达式，并将其应用于进程的内容 `/proc/<pid>/cmdline`. 对于内核线程的 `/proc/<pid>/cmdline` 文件是空的， 所以, `cmdline` 参数不会匹配到。

en-us	##### - Threshold to reach  (**timeleft** only)\ Parameter `threshold` specifies a value the analyzed item has to reach, no difference if from above or from below. Once we have determined f(t) (see below) we should solve equation f(t) = `threshold` and return the root which is closer to now and to the right from now or 999999999999.9999 if there is no such root.  ::: notetip When item values approach the threshold and then cross it, **timeleft** assumes that intersection is already in the past and therefore switches to the next intersection with `threshold` level, if any. Best practice should be to use predictions as a complement to ordinary problem diagnostics, not as a substitution.[^1] :::
zh-cn	##### 2.3 达到阈值  (仅限**timeleft** )\ 参数 `threshold`指定分析监控项必须达到的值，不管从上还是从下达到。一旦确定了f(t) (见下文) ，我们应该求解方程 f(t) = `threshold`并返回更靠近现在和从现在开始向右的根，如果没有这样的根，则返回 999999999999.9999。  ::: notetip 当监控项值接近阈值然后越过它时, **timeleft** 假定交叉点已经过去，因此切换 `threshold` 水平的, 水平的下一个交叉点（如果有）。最佳实践应该是使用预测作为普通问题诊断的补充，而不是替代。[^1] :::

en-us	##### - Time interval  First of all, you should specify the historic period Zabbix should analyze to come up with the prediction. You do it in a familiar way by means of the `time period` parameter and optional time shift like you do it with **avg**, **count**, **delta**, **max**, **min** and **sum** functions.
zh-cn	##### 2.1 时间间隔  首先，你应该指定 Zabbix 需要分析的历史时间来提出预测。你可以通过 `time period`参数和 可选时间偏移以熟悉的方式执行此操作，就像使用 **avg**, **count**, **delta**, **max**, **min** and **sum**函数一样。

en-us	#### Timeout and session termination  IPMI message timeouts and retry counts are defined in OpenIPMI library. Due to the current design of OpenIPMI, it is not possible to make these values configurable in Zabbix, neither on interface nor item level.  IPMI session inactivity timeout for LAN is 60 +/-3 seconds. Currently it is not possible to implement periodic sending of Activate Session command with OpenIPMI. If there are no IPMI item checks from Zabbix to a particular BMC for more than the session timeout configured in BMC then the next IPMI check after the timeout expires will time out due to individual message timeouts, retries or receive error. After that a new session is opened and a full rescan of the BMC is initiated. If you want to avoid unnecessary rescans of the BMC it is advised to set the IPMI item polling interval below the IPMI session inactivity timeout configured in BMC.
zh-cn	#### 关于IPMI离散传感器的注意事项  要在主机上找到传感器启动Zabbix服务器，启用**DebugLevel=4**。等待几分钟，并在Zabbix服务器日志文件中查找传感器发现记录：      $ grep 'Added sensor' zabbix_server.log     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR'     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp'     8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH'  要解码IPMI传感器类型和状态，请在http:*www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html (在撰写本文时，最新的文件是http:*www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf)获取IPMI2.0规范的副本  开始的第一个参数是“reading\_type”。从规范中使用“表42-1，事件/读取类型代码范围”来解码“reading\_type”代码。我们示例中的大多数传感器都有“reading\_type：0x1”，这意味着是“threshold”传感器。 “表42-3，传感器类型代码”表示：“类型：0x1”表示温度传感器；“类型：0x2” -电压传感器；“类型：0x4” -风扇等阈值传感器有时称为“模拟”传感器，因为它们测量连续参数，如温度，电压，每分钟转数。  另一个例子 -一个带有“read\_type：0x3”的传感器。“表42-1，事件/读取类型代码范围”表示读取类型代码02h-0Ch表示“通用离散”传感器。离散传感器具有多达15个可能的状态（换句话说-最多15个有意义的位）。例如，对于具有“type：0x7”的传感器“CATERR”，“表42-3，传感器类型代码”表示此类型“处理器”，各个位的含义是：00h（最低有效位）-IERR ；01h - 散热等。  在我们的示例中有几个传感器具有“reading\_type：0x6f”。对于这些传感器，“表42-1，事件/读取类型代码范围”建议使用“表42-3，传感器类型代码”来解码位的含义。 例如，传感器“Power Unit Stat”的类型为“0x9”，表示“Power Unit”。 Offset 00h表示“PowerOff / Power Down”。换句话说，如果最低有效位为1，则服务器断电。为了测试这个位，可以使用**band**与掩码1的功能。触发表达式可能就像         {www.zabbix.com:Power Unit Stat.band(#1,1)}=1  警告服务器关机。

en-us	##### Timeout processing  Zabbix will not process a simple check longer than the Timeout seconds defined in the Zabbix server/proxy configuration file.
zh-cn	##### 超时处理  如果简单检查时间超过了 Zabbix server 或是 proxy 配置文件中设置的超时时间，Zabbix 将不会做处理。

en-us	##### Time period selector  Take note of the time period selector above the graph. It allows selecting often required periods with one mouse click.  See also: [Time period selector](/manual/config/visualization/graphs/simple#time_period_selector)
zh-cn	##### 时间段选择器  记下图表上方的时间段选择器。 它允许通过一次鼠标单击选择经常需要的时间段。  另请参见： [时间段选择器](/manual/config/visualization/graphs/simple#time_period_selector)

en-us	#### Time period selector  Take note of the time period selector above the graph. It allows to select often required periods with one mouse click.  Note that such options as *Today*, *This week*, *This month*, *This year* display the whole period, including the hours/days in the future. *Today so far*, in contrast, only displays the hours passed.  Once a period is selected, it can be moved back and forth in time by clicking on the ![](../../../../../assets/en/manual/config/visualization/left_arrow.png) ![](../../../../../assets/en/manual/config/visualization/right_arrow.png) arrow buttons. The *Zoom out* button allows to zoom out the period two times or by 50% in each direction. Zoom out is also possible by double-clicking in the graphs. The whole time period selector can be collapsed by clicking on the tab label containing the selected period string.  The *From/To* fields display the selected period in either:  -   absolute time syntax in format `Y-m-d H:i:s` -   relative time syntax, e.g.: `now-1d`  A date in relative format can contain one or several mathematical operations (- or +), e.g. `now-1d` or `now-1d-2h+5m`. For relative time the following abbreviations are supported:  -   now -   s (seconds) -   m (minutes) -   h (hours) -   d (days) -   w (weeks) -   M (months) -   y (years)  It is possible to pick a specific start/end date by clicking on the calendar icon next to the *From/To* fields. In this case, the date picker pop up will open.  ![](../../../../../assets/en/manual/config/date_picker.png){width="200"}  Within the date picker, it is possible to navigate between the blocks of year/month/date using Tab and Shift+Tab. Keyboard arrows or arrow buttons allow to select the desired value. Pressing Enter (or clicking on the desired value) activates the choice.  Another way of controlling the displayed time is to highlight an area in the graph with the left mouse button. The graph will zoom into the highlighted area once you release the left mouse button.  In case no time value is specified or field is left blank, time value will be set to "00:00:00". This doesn't apply to today's date selection: in that case time will be set to current value.
zh-cn	#### 时间段选择器  请注意图表上方的时间段选择器。它允许一键选择经常需要的时间段。  请注意，*今天*、*本周*、*本月*、*本年* 显示整个期间，包括未来的小时/天。*今天到目前为止*，相比之下，只显示过去的小时数。  一旦选择了一个周期，它可以在时间上来回移动点击![](../../../../../assets/en/manual/config/visualization/left_arrow.png)![](../../../../../assets/en/manual/config/visualization/right_arrow.png)箭头按钮。 *缩小*按钮允许缩小第二个周期次或在每个方向上增加 50%。缩小也可以通过双击图表。整个时间段选择器可以是通过单击包含所选期间的选项卡标签折叠。  *From/To* 字段以以下任一方式显示所选期间：  - 格式为“Y-m-d H:i:s”的绝对时间语法 - 相对时间语法，例如：`now-1d`  相对格式的日期可以包含一个或多个数学操作（- 或 +），例如`now-1d` 或`now-1d-2h+5m`。对于相对时间支持以下缩写：  -   现在 - s（秒） - 米（分钟） - h（小时） - d（天） - w（周） - M（月） - y（年）  可以通过单击选择特定的开始/结束日期*From/To* 字段旁边的日历图标。在这种情况下，日期选择器弹出窗口将打开。  ![](../../../../../assets/en/manual/config/date_picker.png){width="200"}  在日期选择器中，可以在使用 Tab 和 Shift+Tab 的年/月/日。键盘箭头或箭头按钮允许选择所需的值。按 Enter 键（或单击所需的值）激活选择。  控制显示时间的另一种方法是突出显示用鼠标左键绘制图形。图表将放大到松开鼠标左键后突出显示的区域。  如果未指定时间值或字段留空，则时间值将设置为“00:00:00”。这不适用于今天的日期选择：在这种情况下，时间将设置为当前值。

en-us	 #### Time period selector  The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter.
zh-cn	#### 时间段选择器  [时间段选择器](/manual/config/visualization/graphs/simple#时间段选择器)允许通过单击鼠标选择经常需要的周期。通过单击过滤器旁边的时间段选项卡，可以打开时间段选择器。

en-us	#### Time period selector  The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter.  Clicking on *Show* in the Graph column displays a bar graph where availability information is displayed in bar format each bar representing a past week of the current year.  ![](../../../../../assets/en/manual/web_interface/availability_bar.png){width="600"}  The green part of a bar stands for OK time and red for problem time.
zh-cn	 #### 时间段选择器  [时间段选择器](/manual/config/visualization/graphs/simple#时间段选择器)允许通过单击鼠标选择经常需要的周期。通过单击过滤器旁边的时间段选项卡，可以打开时间段选择器。  单击图形列中的*查看*，将显示一个条形图，其中可用性信息以条形图的形式显示，每个条形图代表当前一年中过去的一周。  ![](../../../../../assets/en/manual/web_interface/availability_bar.png){width="600"}  条形图的绿色部分代表正常时间，红色部分代表异常时间。

en-us	##### Time period  The **second** parameter allows to specify the time period for aggregation. The time period can only be expressed as time, the amount of values (prefixed with **\#**) is not supported.  [Supported unit symbols](/manual/appendix/suffixes) can be used in this parameter for convenience, for example '5m' (five minutes) instead of '300s' (300 seconds) or '1d' (one day) instead of '86400' (86400 seconds).  Time period is ignored by the server if passed with the *last\_foreach* function and can thus be omitted:      last_foreach(/*/key?[group="host group"])  Time period is not supported with the *exists\_foreach* function.
zh-cn	##### 时间段  **second** 参数允许指定时间段 聚合。时间段只能表示为时间，数量 不支持值（以 **\#** 为前缀）。  [Supported unit symbols](/manual/appendix/suffixes) 可以用在这个 为方便起见参数，例如“5m”（五分钟）而不是 '300s'（300 秒）或 '1d'（一天）而不是 '86400'（86400 秒）。  如果与 *last\_foreach* 一起传递，服务器将忽略时间段 函数，因此可以省略：      last_foreach(/*/key?[group="host group"])  *exists\_foreach* 函数不支持时间段。

en-us	### Time period  The time period object is used to define periods when the maintenance must come into effect. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |period|integer|Duration of the maintenance period in seconds.<br><br>The given value will be rounded down to minutes.<br><br>Default: 3600.| |timeperiod\_type|integer|Type of time period.<br><br>Possible values:<br>0 - *(default)* one time only;<br>2 - daily;<br>3 - weekly;<br>4 - monthly.| |start\_date|timestamp|Date when the maintenance period must come into effect.<br><br>Used only for one time periods.<br><br>The given value will be rounded down to minutes.<br><br>Default: current date.| |start\_time|integer|Time of day when the maintenance starts in seconds.<br><br>Used for daily, weekly and monthly periods.<br><br>The given value will be rounded down to minutes.<br><br>Default: 0.| |every|integer|Used for daily, weekly and monthly periods.<br><br>For daily and weekly periods `every` defines day or week intervals at which the maintenance must come into effect.<br><br>Default: 1.<br><br>For monthly periods, if `dayofweek` property contains at least one selected day of week, the `every` property defines the week of the month when the maintenance must come into effect.<br><br>Possible values:<br>1 - *(default)* first week;<br>2 - second week;<br>3 - third week;<br>4 - fourth week;<br>5 - last week.| |dayofweek|integer|Days of the week when the maintenance must come into effect.<br><br>Days are stored in binary form with each bit representing the corresponding day. For example, 4 equals 100 in binary and means, that maintenance will be enabled on Wednesday.<br><br>Used for weekly and monthly time periods. Required only for weekly time periods.<br><br>At least one `dayofweek` or `day` must be specified for monthly time periods.| |day|integer|Day of the month when the maintenance must come into effect.<br><br>Used only for monthly time periods.<br><br>At least one `dayofweek` or `day` must be specified for monthly time periods.| |month|integer|Months when the maintenance must come into effect.<br><br>Months are stored in binary form with each bit representing the corresponding month. For example, 5 equals 101 in binary and means, that maintenance will be enabled in January and March.<br><br>Required only for monthly time periods.|
zh-cn	 ### 时间段  时间段对象用于定义维护必须生效的时间段。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|----------------------------------------------------|------------| |period|integer|维护周期的持续时间，以秒为单位。<br><br>给定的值将向下舍入为分钟。<br><br>默认值：3600。| |timeperiod\_type|integer|时间段的类型。<br><br>可能的值：<br>0 - *（默认）* 仅一次；<br>2 - 每天；<br>3 - 每周；<br>4 - 每月一次。| |start\_date|timestamp|维护期必须生效的日期。<br><br>仅用于一个时间段。<br><br>给定值将四舍五入为分钟。<br><br>默认值：当前日期。| |start\_time|integer|一天中开始维护的时间，以秒为单位。<br><br>用于每日、每周和每月的周期。<br><br>给定值将向下舍入为分钟。<br ><br>默认值：0。| |every|integer|用于每日、每周和每月周期。<br><br>对于每日和每周周期，`every` 定义维护必须生效的天或周间隔。<br><br>默认值： 1.<br><br>对于月度周期，如果 `dayofweek` 属性包含至少一个选定的星期几，则 `every` 属性定义维护必须生效的月份中的星期几。<br><br >可能的值：<br>1 - *（默认值）* 第一周；<br>2 - 第二周；<br>3 - 第三周；<br>4 - 第四周；<br>5 - 上周。| |dayofweek|integer|维护必须生效的星期几。<br><br>天以二进制形式存储，每个位代表对应的日期。例如，4 等于二进制的 100，表示维护将在星期三启用。<br><br>用于每周和每月的时间段。仅对于每周时间段是必需的。<br><br>必须为每月时间段指定至少一个“dayofweek”或“day”。| |day|integer|维护必须生效的月份中的哪一天。<br><br>仅用于每月时间段。<br><br>必须至少指定一个 `dayofweek` 或 `day`每月时间段。| |month|integer|维护必须生效的月份。<br><br>月份以二进制形式存储，每个位代表对应的月份。例如，5 等于二进制的 101，表示维护将在 1 月和 3 月启用。<br><br>仅在每月的时间段内需要。|

en-us	### Time period  The time period object is used to define periods when the maintenance must come into effect. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |period|integer|Duration of the maintenance period in seconds.<br><br>The given value will be rounded down to minutes.<br><br>Default: 3600.| |timeperiod\_type|integer|Type of time period.<br><br>Possible values:<br>0 - *(default)* one time only;<br>2 - daily;<br>3 - weekly;<br>4 - monthly.| |start\_date|timestamp|Date when the maintenance period must come into effect.<br><br>Used only for one time periods.<br><br>The given value will be rounded down to minutes.<br><br>Default: current date.| |start\_time|integer|Time of day when the maintenance starts in seconds.<br><br>Used for daily, weekly and monthly periods.<br><br>The given value will be rounded down to minutes.<br><br>Default: 0.| |every|integer|Used for daily, weekly and monthly periods.<br><br>For daily and weekly periods `every` defines day or week intervals at which the maintenance must come into effect.<br><br>Default: 1.<br><br>For monthly periods, if `dayofweek` property contains at least one selected day of week, the `every` property defines the week of the month when the maintenance must come into effect.<br><br>Possible values:<br>1 - *(default)* first week;<br>2 - second week;<br>3 - third week;<br>4 - fourth week;<br>5 - last week.| |dayofweek|integer|Days of the week when the maintenance must come into effect.<br><br>Days are stored in binary form with each bit representing the corresponding day. For example, 4 equals 100 in binary and means, that maintenance will be enabled on Wednesday.<br><br>Used for weekly and monthly time periods. Required only for weekly time periods.<br><br>At least one `dayofweek` or `day` must be specified for monthly time periods.| |day|integer|Day of the month when the maintenance must come into effect.<br><br>Used only for monthly time periods.<br><br>At least one `dayofweek` or `day` must be specified for monthly time periods.| |month|integer|Months when the maintenance must come into effect.<br><br>Months are stored in binary form with each bit representing the corresponding month. For example, 5 equals 101 in binary and means, that maintenance will be enabled in January and March.<br><br>Required only for monthly time periods.|
zh-cn	 ### 时间段  时间段对象用于定义维护必须生效的时间段。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|----------------------------------------------------|------------| |period|integer|维护周期的持续时间，以秒为单位。<br><br>给定的值将向下舍入为分钟。<br><br>默认值：3600。| |timeperiod\_type|integer|时间段的类型。<br><br>可能的值：<br>0 - *（默认）* 仅一次；<br>2 - 每天；<br>3 - 每周；<br>4 - 每月一次。| |start\_date|timestamp|维护期必须生效的日期。<br><br>仅用于一个时间段。<br><br>给定值将四舍五入为分钟。<br><br>默认值：当前日期。| |start\_time|integer|一天中开始维护的时间，以秒为单位。<br><br>用于每日、每周和每月的周期。<br><br>给定值将向下舍入为分钟。<br ><br>默认值：0。| |every|integer|用于每日、每周和每月周期。<br><br>对于每日和每周周期，`every` 定义维护必须生效的天或周间隔。<br><br>默认值： 1.<br><br>对于月度周期，如果 `dayofweek` 属性包含至少一个选定的星期几，则 `every` 属性定义维护必须生效的月份中的星期几。<br><br >可能的值：<br>1 - *（默认值）* 第一周；<br>2 - 第二周；<br>3 - 第三周；<br>4 - 第四周；<br>5 - 上周。| |dayofweek|integer|维护必须生效的星期几。<br><br>天以二进制形式存储，每个位代表对应的日期。例如，4 等于二进制的 100，表示维护将在星期三启用。<br><br>用于每周和每月的时间段。仅对于每周时间段是必需的。<br><br>必须为每月时间段指定至少一个“dayofweek”或“day”。| |day|integer|维护必须生效的月份中的哪一天。<br><br>仅用于每月时间段。<br><br>必须至少指定一个 `dayofweek` 或 `day`每月时间段。| |month|integer|维护必须生效的月份。<br><br>月份以二进制形式存储，每个位代表对应的月份。例如，5 等于二进制的 101，表示维护将在 1 月和 3 月启用。<br><br>仅在每月的时间段内需要。|

en-us	### Time period  The time period object is used to define periods when the maintenance must come into effect. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |timeperiodid|string|*(readonly)* ID of the maintenance.| |day|integer|Day of the month when the maintenance must come into effect.<br><br>Required only for monthly time periods.| |dayofweek|integer|Days of the week when the maintenance must come into effect.<br><br>Days are stored in binary form with each bit representing the corresponding day. For example, 4 equals 100 in binary and means, that maintenance will be enabled on Wednesday.<br><br>Used for weekly and monthly time periods. Required only for weekly time periods.| |every|integer|For daily and weekly periods `every` defines day or week intervals at which the maintenance must come into effect.<br><br>For monthly periods `every` defines the week of the month when the maintenance must come into effect.<br>Possible values:<br>1 - first week;<br>2 - second week;<br>3 - third week;<br>4 - fourth week;<br>5 - last week.| |month|integer|Months when the maintenance must come into effect.<br><br>Months are stored in binary form with each bit representing the corresponding month. For example, 5 equals 101 in binary and means, that maintenance will be enabled in January and March.<br><br>Required only for monthly time periods.| |period|integer|Duration of the maintenance period in seconds.<br><br>Default: 3600.| |start\_date|timestamp|Date when the maintenance period must come into effect.<br><br>Required only for one time periods.<br><br>Default: current date.| |start\_time|integer|Time of day when the maintenance starts in seconds.<br><br>Required for daily, weekly and monthly periods.| |timeperiod\_type|integer|Type of time period.<br><br>Possible values:<br>0 - *(default)* one time only;<br>2 - daily;<br>3 - weekly;<br>4 - monthly.|  
zh-cn	### Time period 时间周期  The time period object is used to define periods when the maintenance must come into effect. It has the following properties. 时间周期对象用于定义维护模式生效的时间周期。它有如下属性。  |Property|Type|Description| |--------|----|-----------| |timeperiodid|string|*(readonly)* ID of the maintenance. 维护模式ID。| |day|integer|Day of the month when the maintenance must come into effect. 维护模式生效的月份天次。<br><br>Required only for monthly time periods. 月份时间周期要求。| |dayofweek|integer|Days of the week when the maintenance must come into effect. 维护模式生效的周次。<br><br>Days are stored in binary form with each bit representing the corresponding day. For example, 4 equals 100 in binary and means, that maintenance will be enabled on Wednesday. 日期以二进制形式存储，每个比特代表对应的一天。例如，4在二进制中等于100，意味着星期三将启用维护。<br><br>Used for weekly and monthly time periods. Required only for weekly time periods. 用于周或月时间周期。仅周时间周期要求。| |every|integer|For daily and weekly periods `every` defines day or week intervals at which the maintenance must come into effect. 对于天或者周的周期`every`定义维护模式生效的天或者周间隔。<br><br>For monthly periods `every` defines the week of the month when the maintenance must come into effect. 对于月周期`every`定义该月维护模式生效的周次。<br>Possible values: 可能的值：<br>1 - first week;<br>2 - second week;<br>3 - third week;<br>4 - fourth week;<br>5 - last week.| |month|integer|Months when the maintenance must come into effect. 维护模式必须生效的月份。<br><br>Months are stored in binary form with each bit representing the corresponding month. For example, 5 equals 101 in binary and means, that maintenance will be enabled in January and March. 月份以二进制形式存储，每个位代表相应月份。例如，5在二进制中等于101，意味着维护将在一月和3月启用。<br><br>Required only for monthly time periods. 只有月时间周期要求。| |period|integer|Time of day when the maintenance starts in seconds. 维护模式周期的时间（秒）。<br><br>Default: 3600.| |start\_date|timestamp|Date when the maintenance period must come into effect. 维护模式必须生效的日期。<br><br>Required only for one time periods.<br><br>Default: current date.| |start\_time|integer|Time of day when the maintenance starts in seconds. 一天内维护模式开始的时刻。<br><br>Required for daily, weekly and monthly periods.天、周、月周期要求。| |timeperiod\_type|integer|Type of time period. 时间周期类型。<br><br>Possible values: 可能的值：<br>0 - *(default)* one time only;<br>2 - daily;<br>3 - weekly;<br>4 - monthly.|  

en-us	 ### TimescaleDB 2.6 support  The maximum supported version for TimescaleDB is now 2.6. 
zh-cn	### TimescaleDB 2.6 支持  TimescaleDB 支持的最高版本现在是 2.6。

en-us	 ### TimescaleDB 2.7 support  The maximum supported version for TimescaleDB is now 2.7. 
zh-cn	### TimescaleDB 2.7 支持  TimescaleDB 支持的最高版本现在是 2.7。

en-us	 ### TimescaleDB 2.8 support  The maximum supported version for TimescaleDB is now 2.8.
zh-cn	### TimescaleDB 2.8 支持  TimescaleDB 支持的最高版本现在是 2.8。

en-us	### TimescaleDB 2.9 support  The maximum supported version for TimescaleDB is now 2.9.
zh-cn	### TimescaleDB 2.9 支持  TimescaleDB 支持的最高版本现在是 2.9。

en-us	#### TimescaleDB compression  Native TimescaleDB compression is supported starting from Zabbix 5.0 for PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher for all Zabbix tables that are managed by TimescaleDB. During the upgrade or migration to TimescaleDB, initial compression of the large tables may take a lot of time.  Note that compression is supported under the "timescale" Timescale Community license  and it is not supported under "apache" Apache 2.0 license. Starting with Zabbix  6.0.7, Zabbix detects if compression is supported. If it is not supported a  warning message is written into the Zabbix server log and users cannot enable  compression in the frontend.  ::: notetip Users are encouraged to get familiar with [TimescaleDB](https://docs.timescale.com/latest/using-timescaledb/compression) compression documentation before using compression. :::  Note, that there are certain limitations imposed by compression, specifically:  -   Compressed chunk modifications (inserts, deletes, updates) are not     allowed -   Schema changes for compressed tables are not allowed.  Compression settings can be changed in the *History and trends compression* block in *Administration* → *General* → *Housekeeping* section of Zabbix frontend.  |Parameter|Default|Comments| |--|--|------| |*Enable compression*|Enabled|Checking or unchecking the checkbox does not activate/deactivate compression immediately. Because compression is handled by the Housekeeper, the changes will take effect in up to 2 times `HousekeepingFrequency` hours (set in [zabbix\_server.conf](/manual/appendix/config/zabbix_server))<br><br>After disabling compression, new chunks that fall into the compression period will not be compressed. However, all previously compressed data will stay compressed. To uncompress previously compressed chunks, follow instructions in [TimescaleDB](https://docs.timescale.com/latest/using-timescaledb/compression) documentation.<br><br>When upgrading from older versions of Zabbix with TimescaleDB support, compression will not be enabled by default.| |*Compress records older than*|7d|This parameter cannot be less than 7 days.<br><br>Due to immutability of compressed chunks all late data (e.g. data delayed by a proxy) that is older than this value will be discarded.|
zh-cn	#### TimescaleDB 压缩  从 Zabbix 5.0 开始，PostgreSQL 版本 10.2 或更高版本以及 TimescaleDB 版本 1.5 或更高版本开始支持由 TimescaleDB 管理的所有 Zabbix 表的原生 TimescaleDB 压缩。 在升级或迁移到 TimescaleDB 期间，大表的初始压缩可能会花费很多时间。  请注意，“timescale”Timescale Community 许可支持压缩，“apache”Apache 2.0 许可不支持压缩。 从 Zabbix 6.0.7 开始，Zabbix 检测是否支持压缩。 如果不支持，则会在 Zabbix 服务器日志中写入一条警告消息，并且用户无法在前端启用压缩。  ::: notetip 鼓励用户在使用压缩之前熟悉 [TimescaleDB](https://docs.timescale.com/latest/using-timescaledb/compression) 压缩文档。 :::  请注意，压缩有一定的限制，特别是：  - · 不允许对压缩块进行修改（插入、删除、更新） - · 不允许更改压缩表的schema。  可以在 Zabbix 前端的 *管理* → *一般* → *管家* 部分的 *历史和趋势压缩* 块中更改压缩设置。  |参数|默认|注释| |--|--|------| |*启用压缩*|已启用|选中或取消选中该复选框不会立即激活/停用压缩。 因为压缩是由 Housekeeper 处理的，所以更改将在最多 2 倍的 `HousekeepingFrequency` 小时内生效（设置在 [zabbix\_server.conf](/manual/appendix/config/zabbix_server)）<br><br>禁用压缩后，落入压缩周期的新块将不会被压缩。 但是，所有以前压缩的数据将保持压缩状态。 要解压缩以前压缩的块，请按照 [TimescaleDB](https://docs.timescale.com/latest/using-timescaledb/compression) 文档中的说明进行操作。<br><br>从支持 TimescaleDB 的旧版本 Zabbix 升级时， 默认情况下不会启用压缩。| |*Compress records older than*|7d|此参数不能少于 7 天。<br><br>由于压缩块的不变性，所有早于此值的延迟数据（例如，代理延迟的数据）都将被丢弃。|

en-us	#### TimescaleDB  Instructions for creating and configuring TimescaleDB are provided in a separate [section](/manual/appendix/install/timescaledb).  
zh-cn	#### TimescaleDB  创建和配置 TimescaleDB 的操作在单独的  [章节](/manual/appendix/install/timescaledb) 中说明。

en-us	#### Timescale DB  PostgreSQL versions 9.6-12 use too much memory when updating tables with a large number of partitions ([see problem report](https://www.postgresql-archive.org/memory-problems-and-crash-of-db-when-deleting-data-from-table-with-thousands-of-partitions-td6108612.html)). This issue manifests itself when Zabbix updates trends on systems with TimescaleDB if trends are split into relatively small (e.g. 1 day) chunks. This leads to hundreds of chunks present in the trends tables with default housekeeping settings - the condition where PostgreSQL is likely to run out of memory.  The issue has been resolved since Zabbix 5.0.1 for new installations with TimescaleDB, but if TimescaleDB was set up with Zabbix before that, please see [ZBX-16347](https://support.zabbix.com/browse/ZBX-16347?focusedCommentId=430816&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-430816) for the migration notes.
zh-cn	#### Timescale DB  PostgreSQL 9.6-12 在更新具有大量分区的数据表时会使用过多的内存（[查看问题说明](https://www.postgresql-archive.org/memory-problems-and-crash-of-db-when-deleting-data-from-table-with-thousands-of-partitions-td6108612.html)）。这个问题会在 Zabbix + TimescaleDB 结构下更新系统上的趋势表（trends）且趋势表被分成相对较小（例如 1 天）的块的情况下体现出来。这导致趋势表中存在数百个具有默认管理设置的块 —— 因此 PostgreSQL 可能会耗尽内存。  如果使用 TimescaleDB 新装 Zabbix，则这个问题从 Zabbix 5.0.1 开始已得到解决。但如果在此之前就使用 Zabbix + TimescaleDB 结构，请参阅 [ZBX-16347](https://support.zabbix.com/browse/ZBX-16347?focusedCommentId=430816&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-430816) 以获取迁移说明。

en-us	#### TimescaleDB v1.x  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Upgrading tables  * Rename tables using `history_pk_prepare.sql`.  ``` sudo -u zabbix psql zabbix < /usr/share/doc/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ```  * Example of upgrading for **one** table:  ``` -- Verify that there is enough space to allow export of uncompressed data select sum(before_compression_total_bytes)/1024/1024 as before_compression_total_mbytes, sum(after_compression_total_bytes)/1024/1024 as after_compression_total_mbytes FROM chunk_compression_stats('history_uint_old');  -- Export data \copy (select * from history_uint_old) TO '/tmp/history_uint.csv' DELIMITER ',' CSV  CREATE TEMP TABLE temp_history_uint (  itemid                   bigint                                    NOT NULL,  clock                    integer         DEFAULT '0'               NOT NULL,  value                    numeric(20)     DEFAULT '0'               NOT NULL,  ns                       integer         DEFAULT '0'               NOT NULL ); -- Import data \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV  -- Create hypertable and populate it select create_hypertable('history_uint', 'clock', chunk_time_interval => 86400, migrate_data => true); INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  -- Enable compression select set_integer_now_func('history_uint', 'zbx_ts_unix_now', true); alter table history_uint set (timescaledb.compress,timescaledb.compress_segmentby='itemid',timescaledb.compress_orderby='clock,ns');  -- Job id will returned, it should be passed to run_job select add_compress_chunks_policy('history_uint', (   select (p.older_than).integer_interval from _timescaledb_config.bgw_policy_compress_chunks p    inner join _timescaledb_catalog.hypertable h on (h.id=p.hypertable_id) where h.table_name='history_uint'  )::integer );  select alter_job((select job_id from timescaledb_information.jobs where hypertable_schema='public' and hypertable_name='history_uint'), scheduled => true);  -- Run compression job call run_job(<JOB_ID>); -- May show 'NOTICE:  no chunks for hypertable public.history_uint that satisfy compress chunk policy', it is fine. ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  See also: Tips for [improving PostgreSQL insert performance](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/)  
zh-cn	#### TimescaleDB v1.x  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Upgrading tables  * Rename tables using [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/f3b9848e458867c5b834e4f299944e8e90eb0d37)  * Example of upgrading for **one** table:  ``` -- Verify that there is enough space to allow export of uncompressed data select sum(before_compression_total_bytes)/1024/1024 as before_compression_total_mbytes, sum(after_compression_total_bytes)/1024/1024 as after_compression_total_mbytes FROM chunk_compression_stats('history_uint_old');  -- Export data \copy (select * from history_uint_old) TO '/tmp/history_uint.csv' DELIMITER ',' CSV  CREATE TEMP TABLE temp_history_uint (  itemid                   bigint                                    NOT NULL,  clock                    integer         DEFAULT '0'               NOT NULL,  value                    numeric(20)     DEFAULT '0'               NOT NULL,  ns                       integer         DEFAULT '0'               NOT NULL ); -- Import data \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV  -- Create hypertable and populate it select create_hypertable('history_uint', 'clock', chunk_time_interval => 86400, migrate_data => true); INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  -- Enable compression select set_integer_now_func('history_uint', 'zbx_ts_unix_now', true); alter table history_uint set (timescaledb.compress,timescaledb.compress_segmentby='itemid',timescaledb.compress_orderby='clock,ns');  -- Job id will returned, it should be passed to run_job select add_compress_chunks_policy('history_uint', (   select (p.older_than).integer_interval from _timescaledb_config.bgw_policy_compress_chunks p    inner join _timescaledb_catalog.hypertable h on (h.id=p.hypertable_id) where h.table_name='history_uint'  )::integer );  select alter_job((select job_id from timescaledb_information.jobs where hypertable_schema='public' and hypertable_name='history_uint'), scheduled => true);  -- Run compression job call run_job(<JOB_ID>); -- May show 'NOTICE:  no chunks for hypertable public.history_uint that satisfy compress chunk policy', it is fine. ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  See also: Tips for [improving PostgreSQL insert performance](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/)  

en-us	 #### TimescaleDB v2.x  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Upgrading tables  * Rename tables using `history_pk_prepare.sql`.  ``` sudo -u zabbix psql zabbix < /usr/share/doc/zabbix-sql-scripts/postgresql/history_pk_prepare.sql ```  * Example of upgrading for **one** table:  ``` -- Verify that there is enough space to allow export of uncompressed data select sum(before_compression_total_bytes)/1024/1024 as before_compression_total_mbytes, sum(after_compression_total_bytes)/1024/1024 as after_compression_total_mbytes FROM chunk_compression_stats('history_uint_old');  -- Export data \copy (select * from history_uint_old) TO '/tmp/history_uint.csv' DELIMITER ',' CSV  CREATE TEMP TABLE temp_history_uint (  itemid                   bigint                                    NOT NULL,  clock                    integer         DEFAULT '0'               NOT NULL,  value                    numeric(20)     DEFAULT '0'               NOT NULL,  ns                       integer         DEFAULT '0'               NOT NULL ); -- Import data \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV  -- Create hypertable and populate it select create_hypertable('history_uint', 'clock', chunk_time_interval => 86400, migrate_data => true); INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  -- Enable compression select set_integer_now_func('history_uint', 'zbx_ts_unix_now', true); alter table history_uint set (timescaledb.compress,timescaledb.compress_segmentby='itemid',timescaledb.compress_orderby='clock,ns');  -- Substitute your schema in hypertable_schema -- Job id will returned, it should be passed to run_job select add_compression_policy('history_uint', (  select extract(epoch from (config::json->>'compress_after')::interval) from timescaledb_information.jobs where application_name like 'Compression%%' and hypertable_schema='public' and hypertable_name='history_uint_old'  )::integer );  select alter_job((select job_id from timescaledb_information.jobs where hypertable_schema='public' and hypertable_name='history_uint'), scheduled => true);  -- Run compression job call run_job(<JOB_ID>); -- May show 'NOTICE:  no chunks for hypertable public.history_uint that satisfy compress chunk policy', it is fine. ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  See also: Tips for [improving PostgreSQL insert performance](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/)  
zh-cn	 #### TimescaleDB v2.x  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Upgrading tables  * Rename tables using [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/f3b9848e458867c5b834e4f299944e8e90eb0d37])  * Example of upgrading for **one** table:  ``` -- Verify that there is enough space to allow export of uncompressed data select sum(before_compression_total_bytes)/1024/1024 as before_compression_total_mbytes, sum(after_compression_total_bytes)/1024/1024 as after_compression_total_mbytes FROM chunk_compression_stats('history_uint_old');  -- Export data \copy (select * from history_uint_old) TO '/tmp/history_uint.csv' DELIMITER ',' CSV  CREATE TEMP TABLE temp_history_uint (  itemid                   bigint                                    NOT NULL,  clock                    integer         DEFAULT '0'               NOT NULL,  value                    numeric(20)     DEFAULT '0'               NOT NULL,  ns                       integer         DEFAULT '0'               NOT NULL ); -- Import data \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV  -- Create hypertable and populate it select create_hypertable('history_uint', 'clock', chunk_time_interval => 86400, migrate_data => true); INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  -- Enable compression select set_integer_now_func('history_uint', 'zbx_ts_unix_now', true); alter table history_uint set (timescaledb.compress,timescaledb.compress_segmentby='itemid',timescaledb.compress_orderby='clock,ns');  -- Substitute your schema in hypertable_schema -- Job id will returned, it should be passed to run_job select add_compression_policy('history_uint', (  select extract(epoch from (config::json->>'compress_after')::interval) from timescaledb_information.jobs where application_name like 'Compression%%' and hypertable_schema='public' and hypertable_name='history_uint_old'  )::integer );  select alter_job((select job_id from timescaledb_information.jobs where hypertable_schema='public' and hypertable_name='history_uint'), scheduled => true);  -- Run compression job call run_job(<JOB_ID>); -- May show 'NOTICE:  no chunks for hypertable public.history_uint that satisfy compress chunk policy', it is fine. ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  See also: Tips for [improving PostgreSQL insert performance](https://blog.timescale.com/blog/13-tips-to-improve-postgresql-insert-performance/)  

en-us	##### Time shift  An optional time shift is supported with time or value count as the function parameter. This parameter allows to reference data from a period of time in the past.  Time shift starts with `now` - specifying the current time, and is followed by `+N<time unit>` or `-N<time unit>` - to add or subtract N time units.  For example, `avg(/host/key,1h:now-1d)` will return the average value for an hour one day ago.  **Time shift with absolute time periods**  Absolute time periods are supported in the time shift parameter, for example, midnight to midnight for a day, Monday-Sunday for a week, first day-last day of the month for a month.  Time shift for absolute time periods starts with `now` - specifying the current time, and is followed by any number of time operations: `/<time unit>` - defines the beginning and end of the time unit, for example, midnight to midnight for a day, `+N<time unit>` or `-N<time unit>` - to add or subtract N time units.  Please note that the value of time shift can be greater or equal to 0, while the time period minimum value is 1.  |Parameter|Description| |---------|-----------| |1d:now/d|Yesterday| |1d:now/d+1d|Today| |2d:now/d+1d|Last 2 days| |1w:now/w|Last week| |1w:now/w+1w|This week|
zh-cn	##### 时间偏移  支持可选的时间偏移，时间或值计数作为函数参数。此参数允许从一个引用过去一段时间的数据。  时移以 `now` 开头 - 指定当前时间，并且是 后跟 `+N<time unit>` 或 `-N<time unit>` - 加或减 N 时间单位  例如，`avg(/host/key,1h:now-1d)` 将返回一天前的一个小时的平均值。  **具有绝对时间段的时移**  时移参数支持绝对时间段，例如午夜，一天到午夜，一周的周一到周日，第一天到最后一天，一个月到下一个月。   绝对时间段的时移以 `now` 开始 - 指定当前时间，然后是任意数量的时间操作：`/<time unit>` - 定义时间单位的开始和结束，例如，从午夜到一天的午夜，`+N<time unit>` 或 `-N<time unit>` - 添加或减去 N 个时间单位.  请注意时移的值可以大于或等于0， 而时间段最小值为1。  |参数|描述| |---------|-----------| |1d:now/d|昨天| |1d:now/d+1d|今天| |2d:now/d+1d|过去 2 天| |1w:now/w|上星期| |1w:now/w+1w|这星期|

en-us	##### Time shift  An optional time shift is supported with time or value count as the function parameter. This parameter allows to reference data from a period of time in the past.  Time shift starts with `now` - specifying the current time, and is followed by `+N<time unit>` or `-N<time unit>` - to add or subtract N time units.  For example, `avg(/host/key,1h:now-1d)` will return the average value for an hour one day ago.  \*\* Time shift with absolute time periods \*\*  Absolute time periods are supported in time shift, for example, midnight to midnight for a day, Monday-Sunday for a week, first day-last day of the month for a month.  Time shift for absolute time periods starts with `now` - specifying the current time, and is followed by any number of time operations: `/<time unit>` - defines the beginning and end of the time unit, for example, midnight to midnight for a day, `+N<time unit>` or `-N<time unit>` - to add or subtract N time units.  |Parameter|Description| |---------|-----------| |1d:now/d|Yesterday| |1d:now/d+1d|Today| |2d:now/d+1d|Last 2 days| |1w:now/w|Last week| |1w:now/w+1w|This week|  
zh-cn	##### 时间偏移  An optional time shift is supported with time or value count as the function parameter. This parameter allows to reference data from a period of time in the past. 支持可选的时间偏移，时间或值计数作为 函数参数。此参数允许从一个引用数据 过去的一段时间。  时移以 `now` 开头 - 指定当前时间，并且是 后跟 `+N<time unit>` 或 `-N<time unit>` - 加或减 N 时间单位。  例如，`avg(/host/key,1h:now-1d)` 将返回平均值 一天前的一个小时。  \*\* 具有绝对时间段的时移 \*\*  时移支持绝对时间段，例如午夜 一天到午夜，一周的周一到周日，第一天到最后一天 一个月为一个月。  时移绝对时间时间开始于“now” —指定当前时间,和紧随其后的是任意数量的时间操作: `/<time unit>` —定义了开始和结束的时间单位,例如,午夜为一天午夜,`+N<time unit>` 或 `-N<time unit>` —添加或减去N时间单位。  |参数|描述| |---------|-----------| |1d:now/d|昨天| |1d:now/d+1d|今天| |2d:now/d+1d|过去 2 天| |1w:now/w|上周| |1w:now/w+1w|本周|  

en-us	#### Time synchronization  It is very important to have precise system time on the server with Zabbix running. [ntpd](http://www.ntp.org/) is the most popular daemon that synchronizes the host's time with the time of other machines. It's strongly recommended to maintain synchronized system time on all systems Zabbix components are running on.
zh-cn	#### 时间同步  服务器上拥有精确的系统时间对 Zabbix 的运行非常重要。 [ntpd](http://www.ntp.org/) 是最流行的守护程序，它将主机的时间与其他计算机的时间同步。强烈建议在运行 Zabbix 组件的所有系统上保持系统时间同步。

en-us	 To add a child service, press on the plus icon next to the Zabbix cluster service (the icon is visible only in *Edit* mode).  ![](../../../assets/en/manual/config/service_cluster2.png){width=600}  In the service configuration window, enter name *Zabbix server node 1*. Note that the Parent services parameter is already pre-filled with *Zabbix cluster*.   Availability of this service is affected by problems on the host *HA node 1*, marked with `component:HA node 1` problem tag. In the Problem tags parameter, enter:  - Name: component - Operation: Equals - Value: HA node 1  ![](../../../assets/en/manual/config/service_cluster3.png){width=600}  Switch to the *Tags* tab and add a service tag: `Zabbix server:node 1`. This tag will be used later for service actions and SLA reports.  ![](../../../assets/en/manual/config/service_cluster4.png){width=600}  Save the new service. 
zh-cn	 点击Zabbix集群服务旁边的加号图标(只有*编辑*模式才能看到加号图标)来创建子服务。  ![](../../../assets/en/manual/config/service_cluster2.png){width=600}  在服务配置窗口输入名称*Zabbix server node 1*。注意，父服务的参数已经用*Zabbix集群*预先填充了。   该服务的可用性受主机*HA node 1*产生的问题所影响，通过`component:HA node 1` 问题标签所标记。在问题标签参数中输入：  - 名称：组件 - 操作: 等于 - 值: HA node 1  ![](../../../assets/en/manual/config/service_cluster3.png){width=600}  切换到 *标签* 面板并添加服务标签：`Zabbix server:node 1`。此标签会用于后续的服务动作和SLA报告。   ![](../../../assets/en/manual/config/service_cluster4.png){width=600}  保存新建的服务。

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

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

en-us	# token.generate
zh-cn	# 生成

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

en-us	# > Token object  The following objects are directly related to the `token` API.
zh-cn	# > 令牌对象  以下对象与 `令牌` API 直接相关。

en-us	### Token  The token object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tokenid|string|*(readonly)* ID of the token.| |**name**<br>(required)|string|Name of the token.| |description|text|Description of the token.| |userid|string|*(readonly for update)* A user the token has been assigned to.<br><br>*Default: current user.*| |lastaccess|timestamp|*(readonly)* Most recent date and time the token was authenticated.<br><br>Zero if the token has never been authenticated.| |status|integer|Token status.<br><br>Possible values:<br>0 - *(default)* enabled token;<br>1 - disabled token.| |expires\_at|timestamp|Token expiration date and time.<br><br>Zero for never-expiring tokens.| |created\_at|timestamp|*(readonly)* Token creation date and time.| |creator\_userid|string|*(readonly)* The creator user of the token.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 令牌  令牌对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tokenid|string|*（只读）*令牌ID。| |**name**<br>（必需）|string|令牌名称。| |description|text|令牌描述。| |userid|string|*（只读更新）* 一个被分配令牌的用户。<br><br>*默认：当前用户。*| |lastaccess|timestamp|*（只读）* 验证令牌的最近日期和时间。<br><br>如果该令牌从未经过身份验证，则为零。| |status|integer|令牌状态。<br><br>可用值：<br>0 - *（默认）*启用令牌；<br>1 - 禁用令牌。| |expires\_at|timestamp|令牌的过期日期和时间。<br><br>永不过期的令牌为0。| |created\_at|timestamp|*（只读）* 令牌的创建日期和时间。| |creator\_userid|string|*（只读）* 令牌的创建者。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Token  This class is designed to work with tokens.  Object references:\  -   [Token](/manual/api/reference/token/object)  Available methods:\  -   [token.create](/manual/api/reference/token/create) - create new     tokens -   [token.delete](/manual/api/reference/token/delete) - delete tokens -   [token.get](/manual/api/reference/token/get) - retrieve tokens -   [token.update](/manual/api/reference/token/update) - update tokens -   [token.generate](/manual/api/reference/token/generate) - generate     tokens
zh-cn	# 令牌  此类用于管理令牌。  对象引用：\  -   [令牌](/manual/api/reference/token/object)  可用方法：\  -   [token.create](/manual/api/reference/token/create) - 创建新的令牌 -   [token.delete](/manual/api/reference/token/delete) - 删除令牌 -   [token.get](/manual/api/reference/token/get) - 获取令牌 -   [token.update](/manual/api/reference/token/update) - 更新令牌 -   [token.generate](/manual/api/reference/token/generate) - 生成令牌

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

en-us	#### Too long PSK value used with OpenSSL 1.1.1  In connecting-side log:      ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK 1"     ...zbx_psk_client_cb() requested PSK identity "PSK 1"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() set result code to SSL_ERROR_SSL: file ssl\statem\extensions_clnt.c line 801: error:14212044:SSL routines:tls_construct_ctos_early_data:internal error: TLS write fatal alert "internal error"'  In accepting-side log:      ...Message from 123.123.123.123 is missing header. Message ignored.  This problem typically arises when upgrading OpenSSL from 1.0.x or 1.1.0 to 1.1.1 and if the PSK value is longer than 512-bit (64-byte PSK, entered as 128 hexadecimal digits).  See also: [Value size limits](/manual/encryption/using_pre_shared_keys#size_limits)
zh-cn	 #### OpenSSL 1.1.1 使用了过长的PSK值  在连接发起端的日志中，会有如下信息显示：      ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK 1"     ...zbx_psk_client_cb() requested PSK identity "PSK 1"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() set result code to SSL_ERROR_SSL: file ssl\statem\extensions_clnt.c line 801: error:14212044:SSL routines:tls_construct_ctos_early_data:internal error: TLS write fatal alert "internal error"'  在连接接收端的日志中，会有如下信息显示：      ...Message from 123.123.123.123 is missing header. Message ignored.  将 OpenSSL 从 1.0.x 或 1.1.0 升级到 1.1.1 以及 PSK 值的长度超过 512 位（64 字节 PSK，以 128 个十六进制数字输入）时，通常会出现此问题。  参考: [值大小限制](/manual/encryption/using_pre_shared_keys#size_limits)

en-us	##### Top hosts  A *Top hosts* widget has been added to dashboard widgets. This widget is  designed to replace the *Data overview* widget that is now deprecated.  The *Top hosts* widget allows to create custom tables for data overview,  which is useful for *Top N*-like reports and bar-progress reports useful  for capacity planning.  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.png)  For more information, see [Top hosts widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts).
zh-cn	##### Top 主机  *Top hosts* 小部件被添加到仪表板小部件中。此小部件旨在替换弃用的 *数据概览* 小部件。  *Top hosts* 小部件允许为数据概览创建自定义表格，这对用于容量规划的类似 *Top N* 类报告和条形进度报告很有用。  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.png)  有关更多信息，请参阅 [Top 主机小部件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts)。

en-us	#### Translating customized severity names  ::: noteimportant If Zabbix frontend translations are used, custom severity names will override translated names by default. ::: Default trigger severity names are available for translation in all locales. If a severity name is changed, a custom name is used in all locales and additional manual translation is needed.  Custom severity name translation procedure:  -   set required custom severity name, for example, 'Important' -   edit     <frontend\_dir>/locale/<required\_locale>/LC\_MESSAGES/frontend.po -   add 2 lines:  ```{=html} <!-- --> ```     msgid "Important"     msgstr "<translation string>"  and save file.  -   create .mo files as described in <frontend\_dir>/locale/README  Here **msgid** should match the new custom severity name and **msgstr** should be the translation for it in the specific language.  This procedure should be performed after each severity name change.
zh-cn	#### 翻译自定义严重性的名称  ::: noteimportant 如果使用Zabbix前端翻译, 自定义严重性名称将会覆盖默认翻译名称。 ::: 默认触发器严重性名称可用于在所有语言环境中进行翻译。如果更改严重性名称，则会在所有区域设置中使用自定义名称，并且需要额外的手动翻译。  自定义严重性名称的翻译步骤:  -   设置自定义严重性名称，例如 '重要' -   编辑<frontend\_dir>/locale/<required\_locale>/LC\_MESSAGES/frontend.po -   添加如下2行:  ```{=html} <!-- --> ```     msgid "Important"     msgstr "<translation string>"  保存文件。  -   在<frontend\_dir>/locale/README创建.mo文件作为描述  这里 **msgid** 应该匹配新的自定义严重性名称， **msgstr** 应该是用特定语言翻译的。  此过程应在每个严重性名称更改之后执行。

en-us	#### Trapper process  Receiving internal metric requests from an external Zabbix instance is handled by the trapper process that validates the request, gathers the metrics, creates the JSON data buffer and sends the prepared JSON back, for example, from server:  ``` {.java} {   "response": "success",   "data": {     "boottime": N,     "uptime": N,     "hosts": N,     "items": N,     "items_unsupported": N,     "preprocessing_queue": N,     "process": {       "alert manager": {         "busy": {           "avg": N,           "max": N,           "min": N         },         "idle": {           "avg": N,           "max": N,           "min": N         },         "count": N       }, ...     },     "queue": N,     "rcache": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "requiredperformance": N,     "triggers": N,     "uptime": N,     "vcache": {       "buffer": {         "total": N,         "free": N,         "pfree": N,         "used": N,         "pused": N       },       "cache": {         "requests": N,         "hits": N,         "misses": N,         "mode": N       }     },     "vmware": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "version": "N",     "wcache": {       "values": {         "all": N,         "float": N,         "uint": N,         "str": N,         "log": N,         "text": N,         "not supported": N       },       "history": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "index": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "trend": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       }     }   } } ```
zh-cn	 #### 捕捉器执行过程  Zabbix实例接收内部指标请求由trapper进程处理，trapper进程验证请求、收集、创建JSON数据缓冲区并将准备好的JSON发回，例如从服务器:  ``` {.java} {   "response": "success",   "data": {     "boottime": N,     "uptime": N,     "hosts": N,     "items": N,     "items_unsupported": N,     "preprocessing_queue": N,     "process": {       "alert manager": {         "busy": {           "avg": N,           "max": N,           "min": N         },         "idle": {           "avg": N,           "max": N,           "min": N         },         "count": N       }, ...     },     "queue": N,     "rcache": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "requiredperformance": N,     "triggers": N,     "uptime": N,     "vcache": {       "buffer": {         "total": N,         "free": N,         "pfree": N,         "used": N,         "pused": N       },       "cache": {         "requests": N,         "hits": N,         "misses": N,         "mode": N       }     },     "vmware": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "version": "N",     "wcache": {       "values": {         "all": N,         "float": N,         "uint": N,         "str": N,         "log": N,         "text": N,         "not supported": N       },       "history": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "index": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "trend": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       }     }   } } ```

en-us	# trend.get
zh-cn	# 检索趋势

en-us	# > Trend object  The following objects are directly related to the `trend` API.  ::: noteclassic Trend objects differ depending on the item's type of information. They are created by the Zabbix server and cannot be modified via the API. :::
zh-cn	# > 趋势对象  以下对象与 `trend` API 直接相关.  ::: noteclassic 趋势对象根据监控项类型的信息而有所不同，它们由Zabbix Server创建，不能通过API进行修改. :::

en-us	#### Trends  Retrieve trend values calculated by Zabbix server for presentation or further processing.  [Trend API](/manual/api/reference/trend)
zh-cn	#### 趋势  检索由 Zabbix Server 计算的趋势值以进行展示或进一步处理。  [Trend API](/manual/api/reference/trend)

en-us	#### Trends  The following information is exported for a calculated trend value:  |Field|<|Type|Description| |-|---------|---------|---------------------------| |*host*|<|object|Host name of the item host.| | |host|string|Host name.| |^|name|string|Visible host name.| |*groups*|<|array|List of host groups of the item host; there should be at least one element in array.| | |\-|string|Host group name.| |*itemid*|<|number|Item ID.| |*name*|<|string|Visible item name.| |*clock*|<|number|Number of seconds since Epoch to the moment when value was collected (integer part).| |*count*|<|number|Number of values collected for a given hour.| |*min*|<|number|Minimum item value for a given hour.| |*avg*|<|number|Average item value for a given hour.| |*max*|<|number|Maximum item value for a given hour.| |*type*|<|number|Value type:<br>0 - numeric float, 3 - numeric unsigned|
zh-cn	#### 趋势  导出以下信息以获取计算的趋势值:  |Field|<|Type|Description| |-----|--------|-------|-----------| |*host*|<|object|监控项主机的主机名| |<|host|string|主机名| |<|name|string|可见的主机名.| |*groups*|<|array|监控项主机的主机组列表;数组中应至少有一个元素| | |\-|string|主机组名.| |*itemid*|<|number|监控项ID.| |*name*|<|string|可见监控项名称.| |*clock*|<|number|收集值那一刻的时间秒数（整数部分）.| |*count*|<|number|一小时内收集的值的数量。| |*min*|<|number|一小时内最小监控项值| |*avg*|<|number|一小时内平均监控项值| |*max*|<|number|一小时内最大监控项值| |*type*|<|number|值类型:<br>0 - 浮点数, 3 - 无符号数字|

en-us	# Trend  This class is designed to work with trend data.  Object references:\  -   [Trend](/manual/api/reference/trend/object#trend)  Available methods:\  -   [trend.get](/manual/api/reference/trend/get) - retrieving trends
zh-cn	# 趋势  此类用于处理趋势数据.  对象引用:  -   [趋势](/manual/api/reference/trend/object#trend)  可用方法:  -   [trend.get](/manual/api/reference/trend/get) - 检索趋势数据

en-us	#### Trigger actions  The following conditions can be set for trigger-based actions:  |Condition type|Supported operators|Description| |--------------|-------------------|-----------| |*Host group*|equals<br>does not equal|Specify host groups or host groups to exclude.<br>**equals** - event belongs to this host group.<br>**does not equal** - event does not belong to this host group.<br>Specifying a parent host group implicitly selects all nested host groups. To specify the parent group only, all nested groups have to be additionally set with the **does not equal** operator.| |*Template*|equals<br>does not equal|Specify templates or templates to exclude.<br>**equals** - event belongs to a trigger inherited from this template.<br>**does not equal** - event does not belong to a trigger inherited from this template.| |*Host*|equals<br>does not equal|Specify hosts or hosts to exclude.<br>**equals** - event belongs to this host.<br>**does not equal** - event does not belong to this host.| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag or event tag to exclude.<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| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag and value combination or tag and value combination to exclude.<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| |*Trigger*|equals<br>does not equal|Specify triggers or triggers to exclude.<br>**equals** - event is generated by this trigger.<br>**does not equal** - event is generated by any other trigger, except this one.| |*Trigger name*|contains<br>does not contain|Specify a string in the trigger name or a string to exclude.<br>**contains** - event is generated by a trigger, containing this string in the name.<br>**does not contain** - this string cannot be found in the trigger name.<br>*Note*: Entered value will be compared to trigger name with all macros expanded.| |*Trigger severity*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals|Specify trigger severity.<br>**equals** - equal to trigger severity<br>**does not equal** - not equal to trigger severity<br>**is greater than or equals** - more or equal to trigger severity<br>**is less than or equals** - less or equal to trigger severity| |*Time period*|in<br>not in|Specify a time period or a time period to exclude.<br>**in** - event time is within the time period.<br>**not in** - event time is not within the time period.<br>See the [time period specification](/manual/appendix/time_period) page for description of the format.<br>[User macros](/manual/config/macros/user_macros) are supported, since Zabbix 3.4.0.| |*Problem is suppressed*|no<br>yes|Specify if the problem is suppressed (not shown) because of host maintenance.<br>**no** - problem is not suppressed.<br>**yes** - problem is suppressed.<br>|  
zh-cn	 #### 触发器动作  可以为基于触发器的动作设置以下条件：  |条件类型|支持的操作符|说明| |--------------|-------------------|-----------| |*Host group*|equals<br>does not equal|主机组或要排除的主机组<br>**equals** - 属于该主机组的事件<br>**does not equal** - 不属于该主机组的事件<br>选择父主机组意味着选择了所有子主机组。如果需要设置仅适用于父主机组，那么需要通过**does not equal**操作符将所有其它子主机组排除。| |*Template*|equals<br>does not equal|模板或要排除的模板.<br>**equals** - 属于该模板上触发器触发的事件<br>**does not equal** - 不属于该模板上触发器触发的事件| |*Host*|equals<br>does not equal|主机或要排除的主机组<br>**equals** - 属于该主机的事件<br>**does not equal** - 不属于该主机的事件| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|标签名称或者要排除的标签名称<br>**equals** - 具备该标签的事件<br>**does not equal** - 不具备该标签的事件<br>**contains** - 标签名称中包含该字符串的事件<br>**does not contain** - 标签名称中不包含该字符串的事件| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|事件标签和值组合或要排除的标签和值组合<br>**equals** - 具备该标签并且值等于给定值的事件<br>**does not equal** - 具备该标签但值不等于给定值的事件<br>**contains** - 具备该标签并且值包含指定字符串的事件<br>**does not contain** - 具备该标签但值不包含指定字符串的事件| |*Trigger*|equals<br>does not equal|触发器或者要排除的触发器<br>**equals** - 由该触发器产生的时间<br>**does not equal** - 由该触发器以外的其它触发器产生的事件| |*Trigger name*|contains<br>does not contain|触发器名称中包含或者不包含指定字符串<br>**contains** - 触发器名称中包含指定字符串<br>**does not contain** - 触发器名称中不包含指定字符串<br>*注意*: 输入的值将与所有宏展开后的触发器名称进行比较。| |*Trigger severity*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals|触发器级别<br>**equals** - 等于某个触发器级别<br>**does not equal** - 不等于某个触发器级别<br>**is greater than or equals** - 等于或高于某个触发器级别<br>**is less than or equals** - 等于或低于某个触发器级别| |*Time period*|in<br>not in|事件是否产生在某个时间段内<br>**in** - 事件产生在某个时间段内<br>**not in** - 事件没有产生在某个时间段内<br>关于事件格式的说明，请参阅 [time period specification](/manual/appendix/time_period) <br>从Zabbix 3.4.0版本开始，支持[User macros](/manual/config/macros/user_macros) | |*Problem is suppressed*|no<br>yes|问题是否因为主机维护而被抑制（不显示）。<br>**no** - 问题没有被抑制<br>**yes** - 问题被抑制<br>|  

en-us	# trigger.adddependencies
zh-cn	# 添加触发依赖

en-us	#### trigger  Changes:\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `trigger.adddependencies`, `trigger.deletedependencies`: dropped the ability to edit the dependencies of inherited triggers.\
zh-cn	 #### 触发器  变更：\ [ZBXNEXT-6867](https://support.zabbix.com/browse/ZBXNEXT-6867) `trigger.adddependencies`，`trigger.deletedependencies`：删除编辑继承触发器依赖的功能。\

en-us	##### Trigger configuration  In trigger configuration, enable the *Allow manual close* option.  ![](../../../../assets/en/manual/config/manual_close_conf1.png)
zh-cn	##### 触发器配置  在触发器配置中，启用*允许手动关闭*选项。  ![](../../../../assets/en/manual/config/manual_close_conf1.png)

en-us	# trigger.create
zh-cn	# 创建触发器

en-us	# trigger.delete
zh-cn	# 删除触发器

en-us	# trigger.deletedependencies
zh-cn	# 删除触发器依赖

en-us	#### - Trigger displaying options  This section allows customizing how trigger status is displayed in the frontend and [trigger severity](/manual/config/triggers/severity) names and colors.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_triggers.png)  |Parameter|Description| |---------|-----------| |*Use custom event status colors*|Checking this parameter turns on the customization of colors for acknowledged/unacknowledged problems.| |*Unacknowledged PROBLEM events*,<br>*Acknowledged PROBLEM events*,<br>*Unacknowledged RESOLVED events*,<br>*Acknowledged RESOLVED events*|Enter new color code or click on the color to select a new one from the provided palette.<br>If *blinking* checkbox is marked, triggers will blink for some time upon the status change to become more visible.| |*Display OK triggers for*|Time period for displaying OK triggers. Allowed range: 0 - 24 hours. [Time suffixes](/manual/appendix/suffixes), e.g. 5m, 2h, 1d, are supported.| |*On status change triggers blink for*|Length of trigger blinking. Allowed range: 0 - 24 hours. [Time suffixes](/manual/appendix/suffixes), e.g. 5m, 2h, 1d, are supported.| |*Not classified*,<br>*Information*,<br>*Warning*,<br>*Average*,<br>*High*,<br>*Disaster*|Custom severity names and/or colors to display instead of system default.<br>Enter new color code or click on the color to select a new one from the provided palette.<br><br>Note, that custom severity names entered here will be used in all locales. If you need to translate them to other languages for certain users, see [Customizing trigger severities](/manual/config/triggers/customseverities) page.|
zh-cn	#### - 触发器显示选项  此部分允许自定义触发状态在前端的显示方式以及 [trigger severity](/manual/config/triggers/severity) 名称和颜色。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_triggers.png)  |参数|说明| |---------|------------| |*使用自定义事件状态颜色*|选中此参数将打开已确认/未确认问题的颜色自定义。| |*未确认的问题事件*,<br>*已确认的问题事件*,<br>*未确认的已解决事件*,<br>*已确认已解决事件*|输入新的颜色代码或单击颜色以从提供的调色板。<br>如果选中 *blinking* 复选框，触发器将在状态更改时闪烁一段时间以变得更加明显。| |*显示 OK 触发器*|显示 OK 触发器的时间段。允许范围：0 - 24 小时。 [时间后缀](/manual/appendix/suffixes)，例如支持5m、2h、1d。| |*在状态变化时触发器闪烁*|触发器闪烁的长度。允许范围：0 - 24 小时。 [时间后缀](/manual/appendix/suffixes)，例如支持5m、2h、1d。| |*未分类*,<br>*信息*,<br>*警告*,<br>*平均*,<br>*高*,<br>*灾难*|自定义严重性名称和/或颜色显示而不是系统默认值。<br>输入新颜色代码或单击颜色以从提供的调色板中选择新颜色。<br><br>请注意，此处输入的自定义严重性名称将用于所有区域设置。如果您需要为某些用户将它们翻译成其他语言，请参阅[自定义触发器严重性](/manual/config/triggers/customseverities) 页面。|

en-us	#### Trigger events  The following information is exported for a problem event:  |Field|<|<|Type|Description| |-|-|----------|----------|------------------------------| |*clock*|<|<|number|Number of seconds since Epoch to the moment when problem was detected (integer part).| |*ns*|<|<|number|Number of nanoseconds to be added to `clock` to get a precise problem detection time.| |*value*|<|<|number|1 (always).| |*eventid*|<|<|number|Problem event ID.| |*name*|<|<|string|Problem event name.| |*severity*|<|<|number|Problem event severity (0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster).| |*hosts*|<|<|array|List of hosts involved in the trigger expression; there should be at least one element in array.| | |\-|<|object|<| |^| |*host*|string|Host name.| |^|^|*name*|string|Visible host name.| |*groups*|<|<|array|List of host groups of all hosts involved in the trigger expression; there should be at least one element in array.| | |\-|<|string|Host group name.| |*tags*|<|<|array|List of problem tags (can be empty).| | |\-|<|object|<| |^| |*tag*|string|Tag name.| |^|^|*value*|string|Tag value (can be empty).|  The following information is exported for a recovery event:  |Field|Type|Description| |--|--|------| |*clock*|number|Number of seconds since Epoch to the moment when problem was resolved (integer part).| |*ns*|number|Number of nanoseconds to be added to `clock` to get a precise problem resolution time.| |*value*|number|0 (always).| |*eventid*|number|Recovery event ID.| |*p\_eventid*|number|Problem event ID.|
zh-cn	#### 触发器事件  为问题事件导出以下信息:  |字段|<|<|类型|描述| |-----|-|-|----|-----------| |*clock*|<|<|number|检测到问题的那一刻的时间秒数（整数部分）| |*ns*|<|<|number|要添加到`clock`以获得精确问题检测时间的纳秒数。| |*value*|<|<|number|1 (总是).| |*eventid*|<|<|number|问题事件ID.| |*name*|<|<|string|问题事件名称.| |*severity*|<|<|number|问题事件严重性 (0 - 未分类, 1 - 信息, 2 - 警告, 3 - 一般严重, 4 - 严重, 5 - 灾难).| |*hosts*|<|<|array|触发器表达式中涉及的主机列表;数组中应至少有一个元素。| |<|\-|<|object|<| |<|<|*host*|string|主机名.| |<|<|*name*|string|可见主机名| |*groups*|<|<|array|触发器表达式中涉及的所有主机的主机组列表;数组中应至少有一个元素.| |<|\-|<|string|主机组名称.| |*tags*|<|<|array|问题标签列表（可以为空）.| |<|\-|<|object|<| |<|<|*tag*|string|标签名称.| |<|<|*value*|string|标签值(可以为空).|  为恢复事件导出以下信息:  |字段|类型|描述| |-----|----|-----------| |*clock*|number|问题恢复那一刻的时间秒数（整数部分）.| |*ns*|number|要添加到`clock`以获得精确问题恢复时间的纳秒数。| |*value*|number|0 (总是).| |*eventid*|number|恢复事件ID.| |*p\_eventid*|number|问题事件ID.|

en-us	# trigger.get
zh-cn	# 检索触发器

en-us	##### Trigger lines  Simple triggers are displayed as lines with black dashes over trigger severity color -- take note of the blue line on the graph and the trigger information displayed in the legend. Up to 3 trigger lines can be displayed on the graph; if there are more triggers then the triggers with lower severity are prioritized. Triggers are always displayed in simple graphs, whereas displaying them in [custom graphs](custom#configuring_custom_graphs) is a user preference.  ![simple\_graph\_trigger.png](../../../../../assets/en/manual/config/simple_graph_trigger.png)
zh-cn	##### 触发器线  单一触发器显示成一条带有触发器严重性颜色的黑色虚线——注意图表上的蓝线和图例中显示的触发信息。最多 3 条触发器线可以显示在图表上；如果有更多触发器，那么严重性较低的触发器优先展示。触发器总是会显示在单一图表中，而在[自定义图表](custom#configuring_custom_graphs) 中可按照用户偏好显示。  ![simple\_graph\_trigger.png](../../../../../assets/en/manual/config/simple_graph_trigger.png)

en-us	# > Trigger object  The following objects are directly related to the `trigger` API.
zh-cn	# > 触发器对象  以下对象与`trigger`API直接相关.

en-us	# triggerprototype.create
zh-cn	# 创建触发器原型

en-us	# triggerprototype.delete
zh-cn	# 删除触发器原型

en-us	# triggerprototype.get
zh-cn	# 检索触发器原型

en-us	# > Trigger prototype object  The following objects are directly related to the `triggerprototype` API.
zh-cn	# > 触发器原型对象  以下对象与`triggerprototype`API直接相关.

en-us	#### Trigger prototypes  The following screenshot illustrates how we can use these macros in trigger prototypes:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/trigger_prototype_snmp.png)  ![](../../../../../assets/en/manual/discovery/low_level_discovery/trigger_prototypes_snmp.png)
zh-cn	#### 触发器原型  下面截图演示了如何在触发器原型中使用宏:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/trigger_prototype_snmp.png)  ![](../../../../../assets/en/manual/discovery/low_level_discovery/trigger_prototypes_snmp.png)

en-us	### Trigger prototype tag  The trigger prototype tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Trigger prototype tag name.| |value|string|Trigger prototype tag value.|
zh-cn	### 触发原型标签  触发器原型标记对象具有以下属性.  | 属性              | [类型](/manual/api/reference_commentary#data_types) | 描述              | | ----------------- | --------------------------------------------------- | ----------------- | | **tag**<br>(必须) | string                                              | 触发原型标签名称. | | value             | string                                              | 触发原型标签值.   |

en-us	### Trigger prototype tag  The trigger prototype tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Trigger prototype tag name.| |value|string|Trigger prototype tag value.|
zh-cn	### 触发原型标签  触发器原型标记对象具有以下属性.  | 属性              | [类型](/manual/api/reference_commentary#data_types) | 描述              | | ----------------- | --------------------------------------------------- | ----------------- | | **tag**<br>(必须) | string                                              | 触发原型标签名称. | | value             | string                                              | 触发原型标签值.   |

en-us	### Trigger prototype  The trigger prototype object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |triggerid|string|*(readonly)* ID of the trigger prototype.| |**description**<br>(required)|string|Name of the trigger prototype.| |**expression**<br>(required)|string|Reduced trigger expression.| |event\_name|string|Event name generated by the trigger.| |opdata|string|Operational data.| |comments|string|Additional comments to the trigger prototype.| |priority|integer|Severity of the trigger prototype.<br><br>Possible values:<br>0 - *(default)* not classified;<br>1 - information;<br>2 - warning;<br>3 - average;<br>4 - high;<br>5 - disaster.| |status|integer|Whether the trigger prototype is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |templateid|string|*(readonly)* ID of the parent template trigger prototype.| |type|integer|Whether the trigger prototype can generate multiple problem events.<br><br>Possible values:<br>0 - *(default)* do not generate multiple events;<br>1 - generate multiple events.| |url|string|URL associated with the trigger prototype.| |recovery\_mode|integer|OK event generation mode.<br><br>Possible values are:<br>0 - *(default)* Expression;<br>1 - Recovery expression;<br>2 - None.| |recovery\_expression|string|Reduced trigger recovery expression.| |correlation\_mode|integer|OK event closes.<br><br>Possible values are:<br>0 - *(default)* All problems;<br>1 - All problems if tag values match.| |correlation\_tag|string|Tag for matching.| |manual\_close|integer|Allow manual close.<br><br>Possible values are:<br>0 - *(default)* No;<br>1 - Yes.| |discover|integer|Trigger prototype discovery status.<br><br>Possible values:<br>0 - *(default)* new triggers will be discovered;<br>1 - new triggers will not be discovered and existing triggers will be marked as lost.| |uuid|string|Universal unique identifier, used for linking imported trigger prototypes to already existing ones. Used only for trigger prototypes on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 触发器原型  触发器原型对象包含以下属性.  | 属性| [类型](/manual/api/reference_commentary#data_types) | 描述 | | ----- | ----- | ----- | | triggerid | string| *(只读)* 触发器原型的ID. | | **description**<br>(必须) | string| 触发器原型的名称.| | **expression**<br>(必须)| string| 简化的触发器表达式.| | event\_name | string| 触发器生成的事件名称.| | opdata| string| 操作数据.| | comments| string| 触发器原型的附加注释.| | priority| integer | 触发器原型的严重性.<br><br>有效的值:<br>0 - *(默认)* 未分类;<br>1 - 信息;<br>2 - 警告;<br>3 - 一般严重;<br>4 - 严重;<br>5 - 灾难. | | status| integer | 触发器原型是启用还是禁用.<br><br>有效的值:<br>0 - *(默认)* 已启用;<br>1 - 已禁用. | | templateid| string| *(只读)* 触发器原型父模板的ID. | | type| integer | 触发器原型是否可以产生多个问题事件.<br><br>有效的值:<br>0 - *(默认)* 不能生成多个事件;<br>1 - 可以生成多个事件. | | url | string| 关联到触发器原型的URL. | | recovery\_mode| integer | 正常事件生成模式.<br><br>有效的值为:<br>0 - *(默认)* 表达式;<br>1 - 恢复表达式;<br>2 - 无. | | recovery\_expression| string| 简化的触发器恢复表达式.| | correlation\_mode | integer | 正常事件关闭.<br><br>有效的值为:<br>0 - *(默认)* 所有问题;<br>1 - 标签值匹配成功的所有问题. | | correlation\_tag| string| 匹配标签.| | manual\_close | integer | 允许手动关闭.<br><br>有效的值为:<br>0 - *(默认)* 否;<br>1 - 是. | | discover| integer | 触发器原型发现状态.<br><br>有效的值:<br>0 - *(默认)* 将发现新的触发器;<br>1 - 不会发现新触发器，现有触发器将被标记为丢失. | | uuid| string| 通用唯一标识符，用于将导入的触发器原型链接到现有的触发器原型。仅用于模板上的触发器原型。如果未给出，则自动生成.<br><br>对于更新操作，此字段为 *只读*. |  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Trigger prototype  This class is designed to work with trigger prototypes.  Object references:\  -   [Trigger     prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)  Available methods:\  -   [triggerprototype.create](/manual/api/reference/triggerprototype/create) -     creating new trigger prototypes -   [triggerprototype.delete](/manual/api/reference/triggerprototype/delete) -     deleting trigger prototypes -   [triggerprototype.get](/manual/api/reference/triggerprototype/get) -     retrieving trigger prototypes -   [triggerprototype.update](/manual/api/reference/triggerprototype/update) -     updating trigger prototypes
zh-cn	# 触发器原型  此类用于管理触发器原型.  对象引用:  -   [触发器原型](/manual/api/reference/triggerprototype/object#trigger_prototype)  可用方法:  -   [triggerprototype.create](/manual/api/reference/triggerprototype/create) - 创建新的触发器原型 -   [triggerprototype.delete](/manual/api/reference/triggerprototype/delete) - 删除触发器原型 -   [triggerprototype.get](/manual/api/reference/triggerprototype/get) - 检索触发器原型 -   [triggerprototype.update](/manual/api/reference/triggerprototype/update) - 更新触发器原型

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

en-us	#### Triggers  Configure triggers to notify you about problems in your system. Manage trigger dependencies.  [Trigger API](/manual/api/reference/trigger)
zh-cn	#### 触发器  配置触发器以通知您系统中的问题。管理触发器依赖关系。  [Trigger API](/manual/api/reference/trigger)

en-us	#### Triggers  In a [trigger](/manual/config/triggers/trigger) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Name|<|yes| |Operational data|<|yes| |Expression (only in constants and function parameters; secret macros are not supported).|<|yes| |Description|<|yes| |URL^[3](supported_by_location_user#footnotes)^|<|yes| |Tag for matching|<|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### 触发器  在 [触发器](/manual/config/triggers/trigger) 配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |名称|<|支持| |操作数据|<|支持| |表达式 (仅在常量和函数参数中; 不支持加密的宏).|<|支持| |描述|<|支持| |URL^[3](supported_by_location_user#footnotes)^|<|支持| |匹配标签|<|支持| |*标签*^[2](supported_by_location_user#footnotes)^|<|<| | |标签名字|支持| |^|标签值|支持|

en-us	##### Triggers  Triggers have an 'OK event generation' setting that controls how OK events are generated:  -   *Expression* - an OK event is generated for a trigger in problem     state when its expression evaluates to FALSE. This is the simplest     setting, enabled by default. -   *Recovery expression* - an OK event is generated for a trigger in     problem state when its expression evaluates to FALSE and the     recovery expression evaluates to TRUE. This can be used if trigger     recovery criteria is different from problem criteria. -   *None* - an OK event is never generated. This can be used in     conjunction with multiple problem event generation to simply send a     notification when something happens.  Additionally triggers have an 'OK event closes' setting that controls which problem events are closed:  -   *All problems* - an OK event will close all open problems created by     the trigger -   *All problems if tag values match* - an OK event will close open     problems created by the trigger and having at least one matching tag     value. The tag is defined by 'Tag for matching' trigger setting. If     there are no problem events to close then OK event is not generated.     This is often called trigger level event correlation.
zh-cn	##### 触发器  触发器有“正常事件生成”的设置用来控制如何生成正常事件：  -   *表达式*——当触发器在问题状态其表达式评估为FALSE时，会生成一个正常事件。这是最简单的设置，默认启用。 -   *恢复表达式*——当触发器在问题状态其表达式评估为FALSE且恢复表达式评估为TRUE。如果触发器恢复标准与问题标准不同可以使用此设置。 -   *无*——不生成正常事件，可以与多个问题事件生成组合使用，当某事件发生时可以简单地发送通知。  此外，触发器有“正常事件关闭”的设置用来控制关闭问题事件：  -   *所有问题* ——正常事件会关闭该触发器打开的所有问题事件。 -   *标签值匹配的所有问题* ——正常事件会关闭该触发器打开的所有问题事件并且至少有一个匹配的标签值。此标签由“匹配标签“的触发器设置。如果没有要关闭的问题事件就不会生成正常事件。这通常称为触发器级别事件关联。

en-us	### Trigger tag  The trigger tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Trigger tag name.| |value|string|Trigger tag value.|
zh-cn	### 触发器标签  触发标签对象具有以下属性.  | 属性                  | [类型](/manual/api/reference_commentary#data_types) | 描述              | | --------------------- | --------------------------------------------------- | ----------------- | | **tag**<br>(required) | string                                              | 触发器的标签名称. | | value                 | string                                              | 触发器的标签值.   |

en-us	### Trigger tag  The trigger tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Trigger tag name.| |value|string|Trigger tag value.|
zh-cn	### 触发器标签  触发标签对象具有以下属性.  | 属性                  | [类型](/manual/api/reference_commentary#data_types) | 描述              | | --------------------- | --------------------------------------------------- | ----------------- | | **tag**<br>(required) | string                                              | 触发器的标签名称. | | value                 | string                                              | 触发器的标签值.   |

en-us	### Trigger  The trigger object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |triggerid|string|*(readonly)* ID of the trigger.| |**description**<br>(required)|string|Name of the trigger.| |**expression**<br>(required)|string|Reduced trigger expression.| |event\_name|string|Event name generated by the trigger.| |opdata|string|Operational data.| |comments|string|Additional description of the trigger.| |error|string|*(readonly)* Error text if there have been any problems when updating the state of the trigger.| |flags|integer|*(readonly)* Origin of the trigger.<br><br>Possible values are:<br>0 - *(default)* a plain trigger;<br>4 - a discovered trigger.| |lastchange|timestamp|*(readonly)* Time when the trigger last changed its state.| |priority|integer|Severity of the trigger.<br><br>Possible values are:<br>0 - *(default)* not classified;<br>1 - information;<br>2 - warning;<br>3 - average;<br>4 - high;<br>5 - disaster.| |state|integer|*(readonly)* State of the trigger.<br><br>Possible values:<br>0 - *(default)* trigger state is up to date;<br>1 - current trigger state is unknown.| |status|integer|Whether the trigger is enabled or disabled.<br><br>Possible values are:<br>0 - *(default)* enabled;<br>1 - disabled.| |templateid|string|*(readonly)* ID of the parent template trigger.| |type|integer|Whether the trigger can generate multiple problem events.<br><br>Possible values are:<br>0 - *(default)* do not generate multiple events;<br>1 - generate multiple events.| |url|string|URL associated with the trigger.| |value|integer|*(readonly)* Whether the trigger is in OK or problem state.<br><br>Possible values are:<br>0 - *(default)* OK;<br>1 - problem.| |recovery\_mode|integer|OK event generation mode.<br><br>Possible values are:<br>0 - *(default)* Expression;<br>1 - Recovery expression;<br>2 - None.| |recovery\_expression|string|Reduced trigger recovery expression.| |correlation\_mode|integer|OK event closes.<br><br>Possible values are:<br>0 - *(default)* All problems;<br>1 - All problems if tag values match.| |correlation\_tag|string|Tag for matching.| |manual\_close|integer|Allow manual close.<br><br>Possible values are:<br>0 - *(default)* No;<br>1 - Yes.| |uuid|string|Universal unique identifier, used for linking imported triggers to already existing ones. Used only for triggers on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 触发器  触发器对象具有以下属性.  | 属性| [类型](/manual/api/reference_commentary#data_types) | 描述 | | ------ | ------ | ------ | | triggerid | string| *(只读)* 触发器的ID. | | **description**<br>(必须) | string| 触发器的名称.| | **expression**<br>(必须)| string| 简化的触发器表达式.| | event\_name | string| 生成触发器的事件名称.| | opdata| string| 当前的数据.| | comments| string| 触发器的附加说明.| | error | string| *(只读)* 更新触发器状态时出现的任何问题的错误文本. | | flags | integer | *(只读)* 原始触发器.<br><br>有效的值为:<br>0 - *(默认)* 普通触发器;<br>4 - 自动发现的触发器. | | lastchange| timestamp | *(只读)* 触发器最后更改其状态的时间. | | priority| integer | 触发器的严重性级别.<br><br>有效的值为:<br>0 - *(默认)* 未分类;<br>1 - 信息;<br>2 - 警告;<br>3 - 一般严重;<br>4 - 严重;<br>5 - 灾难. | | state | integer | *(只读)* 触发器的状态.<br><br>有效的值为:<br>0 - *(默认)* 触发器状态是最新的;<br>1 - 当前的触发器状态是未知的. | | status| integer | 触发器是否处于启用状态或禁用状态.<br><br>有效的值为:<br>0 - *(默认)* 已启用;<br>1 - 已禁用. | | templateid| string| *(只读)* 父触发器模板ID. | | type| integer | 触发器是否能够生成多个问题事件.<br><br>有效的值为:<br>0 - *(默认)* 不能生成多个事件;<br>1 - 可以生成多个事件. | | url | string| 与触发器相关联的URL. | | value | integer | *(只读)* 触发器是否处于正常或问题状态.<br><br>有效的值为:<br>0 - *(默认)* 正常状态;<br>1 - 问题状态. | | recovery\_mode| integer | 事件恢复生成模式.<br><br>有效的值为:<br>0 - *(默认)* 表达式;<br>1 - 恢复表达式;<br>2 - 无. | | recovery\_expression| string| 简化的触发恢复表达式.| | correlation\_mode | integer | 事件恢复关联的模式.<br><br>有效的值为:<br>0 - *(默认)* 所有问题;<br>1 - 与标签值匹配的所有问题. | | correlation\_tag| string| 用于匹配的标签.| | manual\_close | integer | 允许手动关闭.<br><br>有效的值为:<br>0 - *(默认)* 不允许;<br>1 - 允许. | | uuid| string| 通用唯一标识符，用于将导入的触发器链接到已经存在的触发器，仅用于模板上的触发器，如果没有提前给出则标识符会自动生成.<br><br>此字段是 *只读的*，不能通过更新操作修改已有标识符. |  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Trigger  This class is designed to work with triggers.  Object references:\  -   [Trigger](/manual/api/reference/trigger/object#trigger)  Available methods:\  -   [trigger.adddependencies](/manual/api/reference/trigger/adddependencies) -     adding new trigger dependencies -   [trigger.create](/manual/api/reference/trigger/create) - creating     new triggers -   [trigger.delete](/manual/api/reference/trigger/delete) - deleting     triggers -   [trigger.deletedependencies](/manual/api/reference/trigger/deletedependencies) -     deleting trigger dependencies -   [trigger.get](/manual/api/reference/trigger/get) - retrieving     triggers -   [trigger.update](/manual/api/reference/trigger/update) - updating     triggers
zh-cn	# 触发器  此类用于管理触发器.  对象引用:  -   [触发器](/manual/api/reference/trigger/object#trigger)  可用方法:  -   [trigger.adddependencies](/manual/api/reference/trigger/adddependencies) - 添加新的触发器依赖项 -   [trigger.create](/manual/api/reference/trigger/create) - 创建新的触发器 -   [trigger.delete](/manual/api/reference/trigger/delete) - 删除触发器 -   [trigger.deletedependencies](/manual/api/reference/trigger/deletedependencies) - 删除触发器依赖项 -   [trigger.get](/manual/api/reference/trigger/get) - 检索触发器 -   [trigger.update](/manual/api/reference/trigger/update) - 更新触发器

en-us	# trigger.update
zh-cn	# 更新触发器

en-us	##### Trigger  With the item working you need to configure the [trigger](/manual/config/triggers/trigger). It's important to decide what entries in the log file are worth paying attention to. For example, the following trigger expression will search for a string like 'Stopping' to signal potential problems:      find(/My host/log[/var/log/syslog],,"regexp","Stopping")=1   ::: noteimportant To make sure that each line containing the string "Stopping" is considered a problem also set the *Problem event generation mode* in trigger configuration to 'Multiple'. :::  Then define a recovery expression. The following recovery expression will resolve all problems if a log line is found containing the string "Starting":      find(/My host/log[/var/log/syslog],,"regexp","Starting")=1   Since we do not want that it's important to make sure somehow that the corresponding root problems are closed, not just all problems. That's where tagging can help.  Problems and resolutions can be matched by specifying a tag in the trigger configuration. The following settings have to be made:  -   *Problem event generation mode*: Multiple -   *OK event closes*: All problems if tag values match -   Enter the name of the tag for event matching  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger.png)  -   configure the [tags](/manual/config/tagging) to extract tag values     from log lines  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger2.png)  If configured successfully you will be able to see problem events tagged by application and matched to their resolution in *Monitoring* → *Problems*.  ![](../../../../assets/en/manual/config/matched_problems.png){width="600"}  ::: notewarning Because misconfiguration is possible, when similar event tags may be created for **unrelated** problems, please review the cases outlined below! :::  -   With two applications writing error and recovery messages to the     same log file a user may decide to use two *Application* tags in the     same trigger with different tag values by using separate regular     expressions in the tag values to extract the names of, say,     application A and application B from the {ITEM.VALUE} macro (e.g.     when the message formats differ). However, this may not work as     planned if there is no match to the regular expressions.     Non-matching regexps will yield empty tag values and a single empty     tag value in both problem and OK events is enough to correlate them.     So a recovery message from application A may accidentally close an     error message from application B.  ```{=html} <!-- --> ``` -   Actual tags and tag values only become visible when a trigger fires.     If the regular expression used is invalid, it is silently replaced     with an \*UNKNOWN\* string. If the initial problem event with an     \*UNKNOWN\* tag value is missed, there may appear subsequent OK     events with the same \*UNKNOWN\* tag value that may close problem     events which they shouldn't have closed.  ```{=html} <!-- --> ``` -   If a user uses the {ITEM.VALUE} macro without macro functions as the     tag value, the 255-character limitation applies. When log messages     are long and the first 255 characters are non-specific, this may     also result in similar event tags for unrelated problems.
zh-cn	##### 触发器  要让监控项工作，你需要配置[触发器](/manual/config/triggers/trigger)。重要的是要决定日志文件中哪些条目值得注意。例如，以下触发表达式将搜索像“Stopping”这样的字符串来发现潜在问题的信号：      find(/My host/log[/var/log/syslog],,"regexp","Stopping")=1   ::: noteimportant 为了确保包含字符串“Stopping”的每一行都被视为问题，还要在触发器配置中将*问题事件生成模式*设置为"多种”。 :::  然后定义一个恢复表达式。如果发现包含字符串“starting”的日志行，以下恢复表达式将解决所有问题：      find(/My host/log[/var/log/syslog],,"regexp","Starting")=1   由于以某种方式确保相应的根因问题得到解决很重要，我们不希望仅仅是解决所有问题。这就是标签可以提供帮助的地方。  问题和解决方案可以通过在触发器配置中指定标签来匹配。必须进行以下设置：  -   *问题事件生成模式*：多种 -   *正常事件关闭*：如果标签匹配所有事件 -   输入事件匹配的标签名称  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger.png)  -   配置[标签](/manual/config/tagging)从日志行中获取标签值  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger2.png)  如果配置成功，你将在*监控*→*问题*里看到问题事件被应用程序标识并匹配它们的解决方案  ![](../../../../assets/en/manual/config/matched_problems.png){width="600"}  ::: notewarning 因为可能配置错误，会为不*关联*的问题创建相似的事件标签，请阅读下面列出的案例！ :::  -   两个应用程序向同一个日志文件写入错误和恢复消息时，用户可能决定为同一个触发器使用两个标签值不同的*应用*标签，在标签值中使用不同的正则表达式从{ITEM.VALUE}宏获取应用名称A和B（例如，当消息格式不同时）。然而，如果没有与正则表达式匹配，这可能无法按计划工作。不匹配的正则表达式会产生空的标签值，同一个空标签值足以将问题事件和正常事件关联起来。所以，一个来自应用A的恢复消息会意外地关闭一个来自应用B的错误消息。  ```{=html} <!-- --> ``` -   实际标签和标签值仅在触发器触发时可见。如果正则表达式使用不正确，会不做提示的自动替换为一个\*UNKNOWN\*字符串。如果最初的有\*UNKNOWN\*标签值的问题事件被错过了，随后可能会出现一个有相同\*UNKNOWN\*标签值的正常事件来关闭本不该关闭的问题事件。  ```{=html} <!-- --> ``` -   如果用户使用{ITEM.VALUE}宏而没有将宏函数设为标签值，255个字符的限制会生效。当日志消息很长并且前255个字符不是特定的，这也可能导致非关联问题拥有相似的事件标签。

en-us	#### Trimmed long IPv6 IP address in failed login information  A failed login attempt message will display only the first 39 characters of a stored IP address as that's the character limit in the database field. That means that IPv6 IP addresses longer than 39 characters will be shown incompletely.
zh-cn	#### 裁剪了登录失败信息中的长 IPv6 IP 地址  登录失败的消息将仅显示存储的 IP 地址的前 39 个字符，这是由于数据库字段中的字符限制。这意味着超过 39 个字符的 IPv6 IP 地址将不能完整显示。

en-us	#### Troubleshooting agent items  -   If used with the passive agent, *Timeout* value in server     configuration may need to be higher than *Timeout* in the agent     configuration file. Otherwise the item may not get any value because     the server request to agent timed out first.
zh-cn	#### agent监控项故障排除  -   如果使用被动 agent，server 配置的*Timeout*值可能需要比 agent 配置的*Timeout*值高。     否则此监控项可能不会获取到任何值，因为 server 到 agent 的请求先超时了。

en-us	#### Troubleshooting  -   In case of unavailable metrics, please make sure if they are not     made unavailable or turned off by default in recent VMware vSphere     versions or if some limits are not placed on performance-metric     database queries. See     [ZBX-12094](https://support.zabbix.com/browse/ZBX-12094) for     additional details.  ```{=html} <!-- --> ``` -   In case of *'config.vpxd.stats.maxQueryMetrics' is invalid or     exceeds the maximum number of characters permitted\*\** error, add a     `config.vpxd.stats.maxQueryMetrics` parameter to the vCenter Server     settings. The value of this parameter should be the same as the     value of `maxQuerysize` in VMware's *web.xml*. See this VMware     knowledge base [article](https://kb.vmware.com/s/article/2107096)     for details.
zh-cn	#### 故障排除  -   如果指标不可用，请确保在当前的 VMware vSphere 版本中它们是否不可用或默认关闭，或者是否未对性能指标数据库查询设置一些限制。更多详细信息，请参见 [ZBX-12094](https://support.zabbix.com/browse/ZBX-12094) 。  ```{=html} <!-- --> ``` -   如果出现 *'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted\*\**  的报错，请向 vCenter Server 配置中添加参数 `config.vpxd.stats.maxQueryMetrics` 。此参数的值应与 VMware 的 *web.xml* 中 `maxQuerysize`  的值相同。有关详细信息，请参阅此 VMware 知识库 [文章](https://kb.vmware.com/s/article/2107096)。

en-us	#### Troubleshooting  The following steps may help you troubleshoot problems with Elasticsearch setup:  1.  Check if the mapping is correct (GET request to required index URL     like `http://localhost:9200/uint`). 2.  Check if shards are not in failed state (restart of Elasticsearch     should help). 3.  Check the configuration of Elasticsearch. Configuration should allow     access from the Zabbix frontend host and the Zabbix server host. 4.  Check Elasticsearch logs.  If you are still experiencing problems with your installation then please create a bug report with all the information from this list (mapping, error logs, configuration, version, etc.)
zh-cn	#### 故障排除 以下步骤可以帮助您解决Elasticsearch设置问题：  1.  检查映射是否正确 (通过URL的发送GET请求获取索引信息，例如： `http://localhost:9200/uint`) 2.  检查shards状态是否正常 (不正常时重启Elasticsearch可能解决问题) 3.  检查Elasticsearch配置文件，配置文件应允许从Zabbix前端及Zabbix server主机访问。 4.  检查Elasticsearch日志  如果您仍然遇到安装问题，请创建一个错误报告，包含此列表中的所有信息（映射，错误日志，配置，版本等信息）

en-us	##### Tuxedo  Tuxedo command line utilities tmadmin and qmadmin can be used in definition of a UserParameter in order to return per server/service/queue performance counters and availability of Tuxedo resources.
zh-cn	##### Tuxedo  Tuxedo 命令行实用程序 tmadmin 和 qmadmin 可用于定义用户参数，以便返回每个服务器/服务/队列的性能计数器和 Tuxedo 资源的可用性。

en-us	### UI element  The UI element object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Name of the UI element.<br><br>Possible values for users of any type:<br>`monitoring.dashboard` - *Monitoring → Dashboard*;<br>`monitoring.problems` - *Monitoring → Problems*;<br>`monitoring.hosts` - *Monitoring → Hosts*;<br>`monitoring.latest_data` - *Monitoring → Latest data*;<br>`monitoring.maps` - *Monitoring → Maps*;<br>`services.services` - *Services → Services*;<br>`services.sla_report` - *Services → SLA report*;<br>`inventory.overview` - *Inventory → Overview*;<br>`inventory.hosts` - *Inventory → Hosts*;<br>`reports.availability_report` - *Reports → Availability report*;<br>`reports.top_triggers` - *Reports → Triggers top 100*.<br><br>Possible values only for users of *Admin* and *Super admin* user types:<br>`monitoring.discovery` - *Monitoring → Discovery*;<br>`services.actions` - *Services → Service actions*;<br>`services.sla` - *Services → SLA*;<br>`reports.scheduled_reports` - *Reports → Scheduled reports*;<br>`reports.notifications` - *Reports → Notifications*;<br>`configuration.host_groups` - *Configuration → Host groups*;<br>`configuration.templates` - *Configuration → Templates*;<br>`configuration.hosts` - *Configuration → Hosts*;<br>`configuration.maintenance` - *Configuration → Maintenance*;<br>`configuration.actions` - *Configuration → Actions*;<br>`configuration.discovery` - *Configuration → Discovery*.<br><br>Possible values only for users of *Super admin* user type:<br>`reports.system_info` - *Reports → System information*;<br>`reports.audit` - *Reports → Audit*;<br>`reports.action_log` - *Reports → Action log*;<br>`configuration.event_correlation` - *Configuration → Event correlation*;<br>`administration.general` - *Administration → General*;<br>`administration.proxies` - *Administration → Proxies*;<br>`administration.authentication` - *Administration → Authentication*;<br>`administration.user_groups` - *Administration → User groups*;<br>`administration.user_roles` - *Administration → User roles*;<br>`administration.users` - *Administration → Users*;<br>`administration.media_types` - *Administration → Media types*;<br>`administration.scripts` - *Administration → Scripts*;<br>`administration.queue` - *Administration → Queue*.| |status|integer|Whether access to the UI element is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	### UI元素  UI元素包含下列属性对象：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**name**<br>(必需)|字符串|UI元素的名称。<br><br>普通用户可操作的配置数据包括：<br>`monitoring.dashboard` - *监控 → 仪表板*;<br>`monitoring.problems` - *监控 → 问题*；<br>`monitoring.hosts` - *监控 → 主机*;<br>`monitoring.overview` - *监控 → 概览*;<br>`monitoring.latest_data` - *监控 → 最新数据*;<br>`monitoring.maps` - *监控 → 拓扑图*;<br>`monitoring.services` - *监控 → 服务*;<br>`inventory.overview` - *资产清单 → 概览*;<br>`inventory.hosts` - *资产清单 → 主机*;<br>`reports.availability_report` - *报告 → 可行性报告*;<br>`reports.top_triggers` - *报告 → 前100触发器*。<br><br>*管理员*和*超级管理员* 可操作的配置数据包括：<br>`monitoring.discovery` - *监控 → 发现*;<br>`reports.scheduled_reports` - *报告 → 规划报告*;<br>`reports.notifications` - *报告 → 通知*;<br>`configuration.host_groups` - *配置 → 用户组*;<br>`configuration.templates` - *配置 → 模板*;<br>`configuration.hosts` - *配置 → 主机*;<br>`configuration.maintenance` - *配置 → 维护*;<br>`configuration.actions` - *配置 → 动作*;<br>`configuration.discovery` - *配置 → 发现*.<br><br>*超级管理员* 可操作的配置数据包括：<br>`reports.system_info` - *报告 → 系统信息*;<br>`reports.audit` - *报告 → 审计*;<br>`reports.action_log` - *报告 → 动作记录*;<br>`configuration.event_correlation` - *配置 → 关联事件*;<br>`administration.general` - *管理 → 通用配置*;<br>`administration.proxies` - *管理 → 代理*;<br>`administration.authentication` - *管理 → 授权*;<br>`administration.user_groups` - *管理 → 用户组*;<br>`administration.user_roles` - *管理 → 用户角色*;<br>`administration.users` - *管理 → 用户*;<br>`administration.media_types` - *管理 → 媒介类型*;<br>`administration.scripts` - *管理 → 脚本*;<br>`administration.queue` - *管理 → 队列*.| |status|整数|代表是否开启UI元素的访问。<br><br>可选值：<br>0 - 关闭；<br>1 - *(default)* 开启。|

en-us	#### Unavailable interface  After the UnreachablePeriod ends and the interface has not reappeared, the interface is treated as unavailable.  In the server log it is indicated by messages like these:      temporarily disabling Zabbix agent checks on host "New host": interface unavailable  and in the [frontend](/manual/web_interface/frontend_sections/configuration/hosts) the host availability icon goes from green/gray to yellow/red (the unreachable interface details can be seen in the hint box that is displayed when a mouse is positioned on the host availability icon):  ![](../../../../assets/en/manual/config/unavailable.png)  The **UnavailableDelay** parameter defines how often an interface is checked during interface unavailability.  By default it is 60 seconds (so in this case "temporarily disabling", from the log message above, will mean disabling checks for one minute).  When the connection to the interface is restored, the monitoring returns to normal automatically, too:      enabling Zabbix agent checks on host "New host": interface became available
zh-cn	 ####  不可用主机状态  主机不可达期结束后主机没有再次出现, 视主机为不可用。  在server 日志中，不可用是通过类似下面的消息来表示的:      temporarily disabling Zabbix agent checks on host "New host": interface unavailable  在[前端](/manual/web_interface/frontend_sections/configuration/hosts)  主机可用性图标由绿色（或灰色）变为红色（注意，在鼠标经过时会提示错误描述）:  ![](../../../../assets/en/manual/config/unavailable.png)  **UnavailableDelay**  参数定义了在主机不可用期间，主机被检查的频率。  默认为 60 秒 (所以此时从上面的日志信息来看， "temporarily disabling"意味着禁用检查一分钟)。  当主机连接恢复时，监控也会自动恢复正常:      enabling Zabbix agent checks on host "New host": interface became available

en-us	#### Unblocking multiple users  Unblock two users.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.unblock",     "params": [         "1",         "5"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "1",             "5"         ]     },     "id": 1 } ```
zh-cn	#### 批量解锁用户  解锁两个用户.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.unblock",     "params": [         "1",         "5"     ],     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "1",             "5"         ]     },     "id": 1 } ```

en-us	###      **unencrypted**   connect without encryption (default)  ```{=html} <!-- --> ```    **psk**   connect using TLS and a pre-shared key  ```{=html} <!-- --> ```    **cert**   connect using TLS and a certificate  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.  **--tls-crl-file** *CRL-file*   Full pathname of a file containing revoked certificates.  **--tls-agent-cert-issuer** *cert-issuer*   Allowed agent certificate issuer.  **--tls-agent-cert-subject** *cert-subject*   Allowed agent certificate subject.  **--tls-cert-file** *cert-file*   Full pathname of a file containing the certificate or certificate chain.  **--tls-key-file** *key-file*   Full pathname of a file containing the private key.  **--tls-psk-identity** *PSK-identity*   PSK-identity string.  **--tls-psk-file** *PSK-file*   Full pathname of a file containing the pre-shared key.  **--tls-cipher13** *cipher-string*   Cipher string for OpenSSL 1.1.1 or newer for TLS 1.3. Override the default ciphersuite selection criteria. This option is not available if OpenSSL version is less than 1.1.1.  **--tls-cipher** *cipher-string*   GnuTLS priority string (for TLS 1.2 and up) or OpenSSL cipher string (only for TLS 1.2). Override the default ciphersuite selection criteria.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAG}
zh-cn	 ###      **unencrypted**   无加密连接（默认）  ```{=html} <!-- --> ```    **psk**   使用TLS和预共享密钥进行连接  ```{=html} <!-- --> ```    **cert**   使用TLS和证书进行连接  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   包含用于对等证书验证的顶级CA证书的文件的完整路径名。  **--tls-crl-file** *CRL-file*   包含已吊销证书的文件的完整路径名。  **--tls-agent-cert-issuer** *cert-issuer*   允许的agent证书颁发者。  **--tls-agent-cert-subject** *cert-subject*   允许的agent证书主题。  **--tls-cert-file** *cert-file*   包含证书或证书链的文件的完整路径名。  **--tls-key-file** *key-file*   包含私钥的文件的完整路径名。  **--tls-psk-identity** *PSK-identity*   PSK标识字符串。  **--tls-psk-file** *PSK-file*   包含预共享密钥的文件的完整路径名。  **--tls-cipher13** *cipher-string*   OpenSSL 1.1.1或更新版本TLS 1.3的密码字符串。覆盖默认的密码套件选择条件。如果OpenSSL版本低于1.1.1，则此选项不可用。  **--tls-cipher** *cipher-string*   GnuTLS优先级字符串（适用于TLS 1.2及以上版本）或OpenSSL密码字符串（仅适用于TLS 1.2）。覆盖默认的密码套件选择条件。  **-h**, **--help**   显示本帮助信息然后退出。  **-V**, **--version**   输出版本信息然后退出  [ ]{#lbAG}

en-us	###      **unencrypted**   connect without encryption (default)  ```{=html} <!-- --> ```    **psk**   connect using TLS and a pre-shared key  ```{=html} <!-- --> ```    **cert**   connect using TLS and a certificate  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.  **--tls-crl-file** *CRL-file*   Full pathname of a file containing revoked certificates.  **--tls-server-cert-issuer** *cert-issuer*   Allowed server certificate issuer.  **--tls-server-cert-subject** *cert-subject*   Allowed server certificate subject.  **--tls-cert-file** *cert-file*   Full pathname of a file containing the certificate or certificate chain.  **--tls-key-file** *key-file*   Full pathname of a file containing the private key.  **--tls-psk-identity** *PSK-identity*   PSK-identity string.  **--tls-psk-file** *PSK-file*   Full pathname of a file containing the pre-shared key.  **--tls-cipher13** *cipher-string*   Cipher string for OpenSSL 1.1.1 or newer for TLS 1.3. Override the default ciphersuite selection criteria. This option is not available if OpenSSL version is less than 1.1.1.  **--tls-cipher** *cipher-string*   GnuTLS priority string (for TLS 1.2 and up) or OpenSSL cipher string (only for TLS 1.2). Override the default ciphersuite selection criteria.  **-v**, **--verbose**   Verbose mode, **-vv** for more details.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAG}
zh-cn	 ###      **unencrypted**   无加密连接（默认）  ```{=html} <!-- --> ```    **psk**   使用TLS和预共享密钥进行连接  ```{=html} <!-- --> ```    **cert**   使用TLS和证书进行连接  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   包含用于对等证书验证的顶级CA证书的文件的完整路径名。  **--tls-crl-file** *CRL-file*   包含已吊销证书的文件的完整路径名。  **--tls-server-cert-issuer** *cert-issuer*   允许的服务器证书颁发者。  **--tls-server-cert-subject** *cert-subject*   允许的服务器证书主题。  **--tls-cert-file** *cert-file*   包含证书或证书链的文件的完整路径名。  **--tls-key-file** *key-file*   包含私钥的文件的完整路径名。  **--tls-psk-identity** *PSK-identity*   PSK标识字符串。  **--tls-psk-file** *PSK-file*   包含预共享密钥的文件的完整路径名。  **--tls-cipher13** *cipher-string*   OpenSSL 1.1.1或更新版本TLS 1.3的密码字符串。覆盖默认的密码套件选择条件。如果OpenSSL版本低于1.1.1，则此选项不可用。  **--tls-cipher** *cipher-string*   GnuTLS优先级字符串（适用于TLS 1.2及以上版本）或OpenSSL密码字符串（仅适用于TLS 1.2）。覆盖默认的密码套件选择条件。  **-v**, **--verbose**   详细模式，**-vv**了解更多详细信息。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAG}

en-us	#### Uninstalling agent Windows service  To uninstall a single instance of Zabbix agent using the default configuration file:         zabbix_agentd.exe --uninstall  To uninstall a single instance of Zabbix agent using a non-default configuration file:         zabbix_agentd.exe --config <your_configuration_file> --uninstall  To uninstall multiple instances of Zabbix agent from Windows services:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --uninstall --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --uninstall --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --uninstall --multiple-agents
zh-cn	#### 卸载Windows 服务上的 zabbix agent   使用默认配置文件卸载单个实例的 Zabbix agent:         zabbix_agentd.exe --uninstall  指定配置文件卸载单个实例的 Zabbix agent:         zabbix_agentd.exe --config <your_configuration_file> --uninstall  卸载多个Zabbix agent实例，请执行以下操作:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --uninstall --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --uninstall --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --uninstall --multiple-agents

en-us	#### Unit conversion  By default, specifying a unit for an item results in a multiplier prefix being added - for example, an incoming value '2048' with unit 'B' would be displayed as '2KB'.  To prevent a unit from conversion, use the `!` prefix, for example, `!B`. To better understand how the conversion works with and without the exclamation mark, see the following examples of values and units:      1024 !B → 1024 B     1024 B → 1 KB     61 !s → 61 s     61 s → 1m 1s     0 !uptime → 0 uptime     0 uptime → 00:00:00     0 !! → 0 !     0 ! → 0  ::: noteclassic Before Zabbix 4.0, there was a hardcoded unit stoplist consisting of `ms`, `rpm`, `RPM`, `%`. This stoplist has been deprecated, thus the correct way to prevent converting such units is `!ms`, `!rpm`, `!RPM`, `!%`. :::
zh-cn	#### 单位转换  默认情况下，为监控项指定单位会自动添加该单位的乘数前缀 - 例如，单位为“B”的传入值“2048”将显示为“2KB”。  但是，可以通过使用 `!` 前缀来阻止单位转换，例如 `!B`。为了更好地理解在有单位转换和没有单位转换的情况下转换的方式，请参见以下值和单位示例：      1024 !B → 1024 B     1024 B → 1 KB     61 !s → 61 s     61 s → 1m 1s     0 !uptime → 0 uptime     0 uptime → 00:00:00     0 !! → 0 !     0 ! → 0  ::: noteclassic 在Zabbix 4.0之前，有一个硬编码的单位黑名单包括 `ms`, `rpm`, `RPM`, `%`。这个黑名单已被弃用，因此阻止这些单位转换的正确方法是使用 `!ms`, `!rpm`, `!RPM`, `!%`。 :::

en-us	#### Unknown interface status  Zabbix server determines an unknown status for the corresponding agent interface (Zabbix, SNMP, IPMI, JMX) if:  -   there are no enabled items on the interface (they were removed or     disabled); -   there are only active Zabbix agent items; -   there are no pollers for that type of the interface (e.g.     StartPollers=0); -   host is disabled; -   host is set to be monitored by proxy, a different proxy or by server     if it was monitored by proxy; -   host is monitored by a proxy that appears to be offline (no updates     received from the proxy during the maximum heartbeat interval - 1     hour).  Setting interface availability to unknown is done after server configuration cache synchronization. Restoring interface availability (available/unavailable) on hosts monitored by proxies is done after proxy configuration cache synchronization.  See also more details about host interface [unreachability](/manual/appendix/items/unreachability).
zh-cn	#### 未知接口状态  如果符合以下情况，Zabbix服务器相应代理接口(Zabbix、SNMP、IPMI、JMX)的状态置为未知:  -   界面上没有启用的监控项(它们被移除或禁用了) -   只有Zabbix agent 主动模式的监控项; -   没有这种类型的接口的轮询器(例如StartPollers=0); -   host被禁用; -   如果是由代理监控时，主机被设置为由代理，另一个不同的代理或服务器监控的; -   主机被一个可能离线的代理监控(在最大心跳间隔-1小时内没有收到来自代理的更新)。  在服务器配置缓存同步之后，将接口可用性设置为未知。在由代理监控的主机上恢复接口可用性(可用/不可用)需要在同步代理配置缓存后完成。  请参阅更多关于主机接口的详细信息 [不可触达](/manual/appendix/items/unreachability)。

en-us	#### Unlinking a template  To unlink a template from a host, do the following:  -   Go to *Configuration → Hosts* -   Click on the required host and find the *Templates* field -   Click on *Unlink* or *Unlink and clear* next to the template to     unlink -   Click on *Update* in the host attributes form  Choosing the *Unlink* option will simply remove association with the template, while leaving all its entities (items, triggers, graphs etc.) with the host.  Choosing the *Unlink and clear* option will remove both the association with the template and all its entities (items, triggers, graphs etc.).
zh-cn	#### 取消链接模板  要从主机中取消链接模板，请执行以下操作：  -   转到 *配置 → 主机* -   单击所需的主机并切换到*模板*选项卡 -   单击模板旁边的*取消链接*或*取消链接并清理*以取消链接 -   单击主机属性窗体中的*更新*  选择*取消链接*选项将简单地删除与模板的关联，同时将其所有实体（监控项，触发器，图形等）与主机保持一致。  选择*取消链接并清理*选项将删除与模板及其所有实体（监控项，触发器，图表等）的关联。

en-us	#### Unlinking templates from a host  Unlink templates "10106", "10104" from template "10085".  Request:  ```json {     "jsonrpc": "2.0",     "method": "template.massremove",     "params": {         "templateids": "10085",         "templateids_link": [             "10106",             "10104"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10085"         ]     },     "id": 1 } ```
zh-cn	#### 在一个主机中取消链接模版  在模版“10085”中取消链接模版“10106”和“10104”。  请求:  ```json {     "jsonrpc": "2.0",     "method": "template.massremove",     "params": {         "templateids": "10085",         "templateids_link": [             "10106",             "10104"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "templateids": [             "10085"         ]     },     "id": 1 } ```

en-us	#### Unlinking templates  Unlink and clear two templates from host.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10126",         "templates_clear": [             {                 "templateid": "10124"             },             {                 "templateid": "10125"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10126"         ]     },     "id": 1 } ```
zh-cn	#### 取消链接模板  从主机上取消链接并清除两个模板。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10126",         "templates_clear": [             {                 "templateid": "10124"             },             {                 "templateid": "10125"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10126"         ]     },     "id": 1 } ```

en-us	#### Unlinking templates  Unlink a template from two hosts and delete all of the templated entities.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.massremove",     "params": {         "hostids": ["69665", "69666"],         "templateids_clear": "325"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "69665",             "69666"         ]     },     "id": 1 } ```
zh-cn	#### 删除模板的链接  将模板与两台主机的链接解除，并删除所有模板实体。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.massremove",     "params": {         "hostids": ["69665", "69666"],         "templateids_clear": "325"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "69665",             "69666"         ]     },     "id": 1 } ```

en-us	#### Unreachable interface  A host interface is treated as unreachable after a failed check (network error, timeout) by Zabbix, SNMP, IPMI or JMX agents. Note that Zabbix agent active checks do not influence interface availability in any way.  From that moment **UnreachableDelay** defines how often an interface is rechecked using one of the items (including LLD rules) in this unreachability situation and such rechecks will be performed already by unreachable pollers (or IPMI pollers for IPMI checks). By default it is 15 seconds before the next check.  In the Zabbix server log unreachability is indicated by messages like these:      Zabbix agent item "system.cpu.load[percpu,avg1]" on host "New host" failed: first network error, wait for 15 seconds     Zabbix agent item "system.cpu.load[percpu,avg15]" on host "New host" failed: another network error, wait for 15 seconds  Note that the exact item that failed is indicated and the item type (Zabbix agent).  ::: noteclassic The *Timeout* parameter will also affect how early an interface is rechecked during unreachability. If the Timeout is 20 seconds and UnreachableDelay 30 seconds, the next check will be in 50 seconds after the first attempt. :::  The **UnreachablePeriod** parameter defines how long the unreachability period is in total. By default UnreachablePeriod is 45 seconds. UnreachablePeriod should be several times bigger than UnreachableDelay, so that an interface is rechecked more than once before an interface becomes unavailable.
zh-cn	 #### 不可达主机接口  主机接口在检查失败后被视为不可访问（网络 错误，超时）由 Zabbix、SNMP、IPMI 或 JMX agent。请注意，Zabbix agent主动检查不会以任何方式影响接口可用性。  从**UnreachableDelay** 那一刻起定义了在这种无法访问的情况下使用其中一项（包括 LLD 规则）重新检查接口的频率，并且此类重新检查将由无法访问的轮询器（或用于 IPMI 检查的 IPMI 轮询器）执行。默认情况下，下次15 秒后再次检查。  在 Zabbix 服务器日志中，不可达性由以下消息指示这些：      Zabbix agent item "system.cpu.load[percpu,avg1]" on host "New host" failed: first network error, wait for 15 seconds     Zabbix agent item "system.cpu.load[percpu,avg15]" on host "New host" failed: another network error, wait for 15 seconds  请注意，指示失败的确切监控项和监控项类型 （Zabbix agent）。  ::: noteclassic 在主机不可达期间，*Timeout* 参数也会影响主机再次被检查的时间。如果Timeout 是 20 秒，但是 UnreachableDelay 是 30 秒, 下一次检查在 50 秒后 。 :::  **UnreachablePeriod**参数定义了不可达的总时长。 UnreachablePeriod 应该比 UnreachableDelay大几倍, 这样在主机变为不可用之前，主机会被检查不止一次。  如果不可达主机再次出现，监控自动恢复正常:  恢复 Zabbix agent 对主机 "New host"的检查: 连接恢复

en-us	#### Unsupported items  An item can become unsupported if its value cannot be retrieved for some reason. Such items are still rechecked at their standard *[Update interval](/manual/config/items/item?#configuration)*.  Unsupported items are reported as having a NOT SUPPORTED state.
zh-cn	#### 不支持的监控项  如果由于某种原因无法检索到值，则该监控项会变为不受支持的。但是该监控项仍会以设定的*[更新间隔](/manual/config/items/item?#configuration)*重新检索。  不支持的监控项会被报告为“不支持（NOT SUPPORTED）”状态。

en-us	#### Update dependent item prototype  Update Dependent item prototype with new Master item prototype ID. Only dependencies on same host (template/discovery rule) are allowed, therefore Master and Dependent item should have same hostid and ruleid.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "master_itemid": "25570",         "itemid": "189030"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189030"         ]     },     "id": 1 } ```
zh-cn	#### 更新依赖监控项原型  使用新主监控项原型ID更新依赖监控项原型。 只允许依赖于同一主机（模板/发现规则）监控项原型，因此主监控项原型和从属监控项原型应具有相同的 hostid 和 ruleid。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "master_itemid": "25570",  · "itemid": "189030"  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "189030"  · ]  · },  · "id": 1 } ```

en-us	#### Update dependent item prototype  Update Dependent item prototype with new Master item prototype ID. Only dependencies on same host (template/discovery rule) are allowed, therefore Master and Dependent item should have same hostid and ruleid.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "master_itemid": "25570",         "itemid": "189030"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189030"         ]     },     "id": 1 } ```
zh-cn	#### 更新依赖监控项原型  使用新主监控项原型ID更新依赖监控项原型。 只允许依赖于同一主机（模板/发现规则）监控项原型，因此主监控项原型和从属监控项原型应具有相同的 hostid 和 ruleid。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "master_itemid": "25570",  · "itemid": "189030"  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "189030"  · ]  · },  · "id": 1 } ```

en-us	#### Update dependent item  Update Dependent item name and Master item ID. Only dependencies on same host are allowed, therefore Master and Dependent item should have same hostid.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "name": "Dependent item updated name",         "master_itemid": "25562",         "itemid": "189019"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189019"         ]     },     "id": 1 } ```
zh-cn	#### 更新依赖监控项  更新依赖监控项名称和主监控项 ID。仅允许依赖于同一主机，因此主监控项和依赖监控项应具有相同的主机 ID。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "name": "Dependent item updated name",         "master_itemid": "25562",         "itemid": "189019"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  更新：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189019"         ]     },     "id": 1 } ```

en-us	#### Update dependent item  Update Dependent item name and Master item ID. Only dependencies on same host are allowed, therefore Master and Dependent item should have same hostid.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "name": "Dependent item updated name",         "master_itemid": "25562",         "itemid": "189019"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189019"         ]     },     "id": 1 } ```
zh-cn	#### 更新依赖监控项  更新依赖监控项名称和主监控项 ID。仅允许依赖于同一主机，因此主监控项和依赖监控项应具有相同的主机 ID。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "name": "Dependent item updated name",         "master_itemid": "25562",         "itemid": "189019"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  更新：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "189019"         ]     },     "id": 1 } ```

en-us	#### Update HTTP agent item  Enable item value trapping.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "allow_traps": "1"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```
zh-cn	#### 更新 HTTP agent 监控项  启用监控项状态值捕获。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "allow_traps": "1"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```

en-us	#### Update HTTP agent item  Enable item value trapping.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "allow_traps": 1     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```
zh-cn	#### 更新 HTTP agent 监控项  启用监控项状态值捕获。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "allow_traps": "1"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```

en-us	#### Update HTTP agent item prototype  Change query fields and remove all custom headers.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid":"28305",         "query_fields": [             {                 "random": "qwertyuiopasdfghjklzxcvbnm"             }         ],         "headers": []     }     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28305"         ]     },     "id": 1 } ```
zh-cn	#### 更新HTTP代理监控项原型  修改查询字段和移除所有自定义的头部。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid":"28305",  · "query_fields": [  · {  · "random": "qwertyuiopasdfghjklzxcvbnm"  · }  · ],  · "headers": []  · }  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "28305"  · ]  · },  · "id": 1 } ```

en-us	#### Update HTTP agent item prototype  Change query fields and remove all custom headers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid":"28305",         "query_fields": [             {                 "random": "qwertyuiopasdfghjklzxcvbnm"             }         ],         "headers": []     }     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28305"         ]     },     "id": 1 } ```
zh-cn	#### 更新HTTP代理监控项原型  修改查询字段和移除所有自定义的头部。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid":"28305",  · "query_fields": [  · {  · "random": "qwertyuiopasdfghjklzxcvbnm"  · }  · ],  · "headers": []  · }  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "28305"  · ]  · },  · "id": 1 } ```

en-us	#### Update operation details  ![](../../../../../assets/en/manual/config/update_operation_details.png)  |   |   |   |   |   | |---|---|---|---|---| |*Operation*|<|<|<|Three operation types are available for update operations:<br>**Send message** - send update message to specified user when event is updated, for example, acknowledged<br>**Notify all involved** - send notification message to all users who received notification about the problem appearing and/or have updated the problem event.<br>**<remote command name>** - execute a remote command when the event is updated, for example, acknowledged. Commands are available for execution if previously defined in [global scripts](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script) with *Action operation* selected as its scope.<br>If the same recipient with unchanged default subject/message is defined in several operation types, duplicate notifications are not sent.<br>The person who updates a problem does not receive notification about their own update.| |<|Operation type: [send message](/manual/config/notifications/action/operation/message)|<|<|<| |^|*Send to user groups*|<|<|Click on *Add* to select user groups to send the update message to.<br>The user group must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|*Send to users*|<|<|Click on *Add* to select users to send the update message to.<br>The user must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |^|*Send only to*|<|<|Send update message to all defined media types or a selected one only.| |^|*Custom message*|<|<|If selected, the custom message can be defined.| |^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|*Message*|<|<|The custom message. The message may contain macros.| |^|Operation type: [remote command](/manual/config/notifications/action/operation/remote_command)|<|<|<| |^|*Target list*|<|<|Select targets to execute the command on:<br>**Current host** - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.<br>**Host** - select host(s) to execute the command on.<br>**Host group** - select host group(s) to execute the command on. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups.<br>A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).<br>The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.<br>Note that for global scripts, the target selection also depends on the *Host group* setting in global script [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script).| |<|Operation type: notify all involved|<|<|<| |^|*Default media type*|<|<|Users who update a problem but have not received notifications about the problem appearing will receive notifications about further updates on the selected default media type - Email or SMS.<br>This field is available since Zabbix 3.4.2.| |^|*Custom message*|<|<|If selected, the custom message can be defined.| |^|*Subject*|<|<|Subject of the custom message. The subject may contain macros.| |^|*Message*|<|<|The custom message. The message may contain macros.|  All mandatory input fields are marked with a red asterisk. When done, click on *Add* to add operation to the list of *Update operations*.
zh-cn	#### 更新操作详细信息  ![](../../../../../assets/en/manual/config/update_operation_details.png)  |   |   |   |   |   | |---|---|---|---|---| |*操作*|<|<|<|<|三种操作类型可用于更新操作：<br>**发送消息**-在更新事件时向指定用户发送更新消息，例如，已确认的<br>**通知所有相关人员**-向收到有关出现问题的通知和/或已更新问题事件的所有用户发送通知消息<br>**<remote command name>**-在事件更新时执行远程命令，例如，确认。如果之前在[全局脚本](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script)中定义了命令，并且选择了*Action operation*作为其范围，则可以执行这些命令<br>如果在多个操作类型中定义了默认主题/消息未更改的同一收件人，则不会发送重复通知<br>更新问题的人不会收到关于自己更新的通知| |<|操作类型：[发送消息](/manual/config/notifications/action/Operation/message)|<|<|<| |^|*发送到用户组*|<|<|单击*添加*选择要向其发送更新消息的用户组<br>用户组必须至少对主机具有“读取”[权限](/manual/config/users_和_usergroups/permissions)才能收到通知| |^|*发送给用户*|<|<|单击*添加*选择要向其发送更新消息的用户<br>用户必须至少对主机具有“读取”[权限](/manual/config/users_和_usergroups/permissions)才能收到通知| |^|*仅发送至*|<|<|向所有已定义的媒体类型或仅选定的媒体类型发送更新消息| |^|*自定义消息*|<|<|如果选中，可以定义自定义消息| |^|*主题*|<|<|自定义消息的主题。主题可能包含宏| |^|*消息*|<|<|自定义消息。该消息可能包含宏| |^|操作类型：[远程命令](/manual/config/notifications/action/Operation/remote_command)|<|<|<| |^|*目标列表*|<|<|选择要在其上执行命令的目标：<br>**当前主机**-在导致问题事件的触发器的主机上执行命令。如果触发器中有多台主机，此选项将不起作用<br>**主机**-选择要在其上执行命令的主机<br>**主机组**-选择要在其上执行命令的主机组。指定父主机组会隐式选择所有嵌套的主机组。因此，远程命令也将在嵌套组的主机上执行<br>主机上的命令仅执行一次，即使主机匹配多次(例如，来自多个主机组；单独或来自一个主机组)<br>如果在Zabbix服务器上执行命令，则目标列表没有意义。在这种情况下，选择更多目标只会导致命令在服务器上执行更多次<br>请注意，对于全局脚本，目标选择还取决于全局脚本[配置](/manual/web_interface/frontend_sections/administration/scripts#configuring_global_script)中的*Host group*设置| |<|操作类型：通知所有相关人员|<|<|<| |^|*默认媒体类型*|<|<|如果用户更新了问题，但尚未收到有关出现问题的通知，则会收到有关所选默认媒体类型(电子邮件或短信)的进一步更新的通知<br>此字段自Zabbix 3.4.2起可用| |^|*自定义消息*|<|<|如果选中，可以定义自定义消息| |^|*主题*|<|<|自定义消息的主题。主题可能包含宏| |^|*消息*|<|<|自定义消息。该消息可能包含宏| 所有必填输入字段均标有红色星号。完成后， 单击*添加*将操作添加到*更新操作*列表中。

en-us	 Update operations offer the same set of parameters as [Recovery operations](/manual/config/notifications/action/recovery_operations#Recovery_operation_details).  ![](../../../../../assets/en/manual/config/update_operation_details.png)
zh-cn	 更新操作提供与 [恢复操作](/manual/config/notifications/action/recovery_operations#Recovery_operation_details) 相同的参数集。  ![](../../../../../assets/en/manual/config/update_operation_details.png)

en-us	#### Updating an item  Enable an item, that is, set its status to "0":  ```json {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "10092",         "status": 0     },     "auth": "0424bd59b807674191e7d77572075f33",     "id": 5 } ```  A successful response will contain the ID of the updated item:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "10092"         ]     },     "id": 5 } ```  ::: notetip The `item.update` method as well as other update methods can also accept arrays of objects and update multiple items with one API call. :::
zh-cn	#### 更新监控项  启用监控项，即将其状态设置为“0”：  ``` {.json} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "10092",         "status": 0     },     "auth": "0424bd59b807674191e7d77572075f33",     "id": 5 } ```  操作成功的响应将包含被更新监控项的 ID： ``` {.json} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "10092"         ]     },     "id": 5 } ```  ::: notetip The `item.update` 方法以及其他 update 方法也可以接受对象数组并通过一次 API 调用更新多个监控项。 :::

en-us	#### Updating an item with preprocessing  Update an item with item preprocessing rule "In range".  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "preprocessing": [             {                 "type": "13",                 "params": "\n100",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项预处理  更新监控项预处理规则为 “In range” 。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "preprocessing": [             {                 "type": "13",                 "params": "\n100",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```

en-us	#### Updating an item with preprocessing  Update an item with item preprocessing rule "In range".  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "preprocessing": [             {                 "type": 13,                 "params": "\n100",                 "error_handler": 1,                 "error_handler_params": ""             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项预处理  更新监控项预处理规则为 “In range” 。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23856",         "preprocessing": [             {                 "type": "13",                 "params": "\n100",                 "error_handler": "1",                 "error_handler_params": ""             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23856"         ]     },     "id": 1 } ```

en-us	#### Updating a script item prototype  Update a script item prototype with a different script and remove unnecessary parameters that were used by previous script.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项原型脚本  使用不同的脚本更新监控项原型脚本，删除先前脚本使用的不必要参数。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "23865",  · "parameters": [],  · "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "23865"  · ]  · },  · "id": 1 } ```

en-us	#### Updating a script item prototype  Update a script item prototype with a different script and remove unnecessary parameters that were used by previous script.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项原型脚本  使用不同的脚本更新监控项原型脚本，删除先前脚本使用的不必要参数。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "23865",  · "parameters": [],  · "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "23865"  · ]  · },  · "id": 1 } ```

en-us	#### Updating a script item  Update a script item with a different script and remove unnecessary parameters that were used by previous script.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新脚本监控项  更新脚本监控项为其他脚本，并删除在旧脚本中使用的非必要参数。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```

en-us	#### Updating a script item  Update a script item with a different script and remove unnecessary parameters that were used by previous script.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新脚本监控项  更新脚本监控项为其他脚本，并删除在旧脚本中使用的非必要参数。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```

en-us	#### Updating dashboard pages  Rename the first dashboard page, replace widgets on the second dashboard page and add a new page as the third one. Delete all other dashboard pages.  Request:  ```json {     "jsonrpc": "2.0",     "method": "dashboard.update",     "params": {         "dashboardid": "2",         "pages": [             {                 "dashboard_pageid": 1,                 "name": 'Renamed Page'             },             {                 "dashboard_pageid": 2,                 "widgets": [                     {                         "type": "clock",                         "x": 0,                         "y": 0,                         "width": 4,                         "height": 3                     }                 ]             },             {                 "display_period": 60             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```
zh-cn	#### 更新仪表盘页面  重命名第一个仪表盘页面，替换第二个仪表盘页面上的部件，并添加一个新页面作为第三个页面。删除所有其他仪表盘页面。  请求：  ```json {     "jsonrpc": "2.0",     "method": "dashboard.update",     "params": {         "dashboardid": "2",         "pages": [             {                 "dashboard_pageid": 1,                 "name": 'Renamed Page'             },             {                 "dashboard_pageid": 2,                 "widgets": [                     {                         "type": "clock",                         "x": 0,                         "y": 0,                         "width": 4,                         "height": 3                     }                 ]             },             {                 "display_period": 60             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```

en-us	#### Updating global regular expression for file systems discovery.  Request:  ```json {     "jsonrpc": "2.0",     "method": "regexp.update",     "params": {       "regexpid": "1",       "name": "File systems for discovery",       "test_string": "",       "expressions": [         {           "expression": "^(btrfs|ext2|ext3|ext4|reiser|xfs|ffs|ufs|jfs|jfs2|vxfs|hfs|apfs|refs|zfs)$",           "expression_type": "3",           "exp_delimiter": ",",           "case_sensitive": "0"         },         {           "expression": "^(ntfs|fat32|fat16)$",           "expression_type": "3",           "exp_delimiter": ",",           "case_sensitive": "0"         }       ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 更新自动发现文件系统的全局正则表达式。  请求：  ```json {     "jsonrpc": "2.0",     "method": "regexp.update",     "params": {       "regexpid": "1",       "name": "File systems for discovery",       "test_string": "",       "expressions": [         {           "expression": "^(btrfs|ext2|ext3|ext4|reiser|xfs|ffs|ufs|jfs|jfs2|vxfs|hfs|apfs|refs|zfs)$",           "expression_type": "3",           "exp_delimiter": ",",           "case_sensitive": "0"         },         {           "expression": "^(ntfs|fat32|fat16)$",           "expression_type": "3",           "exp_delimiter": ",",           "case_sensitive": "0"         }       ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "regexpids": [             "1"         ]     },     "id": 1 } ```

en-us	#### Updating host inventory  Change inventory mode and add location  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10387",         "inventory_mode": 0,         "inventory": {             "location": "Latvia, Riga"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10387"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机资产  改变主机资产模式和添加位置。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10387",         "inventory_mode": 0,         "inventory": {             "location": "Latvia, Riga"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10387"         ]     },     "id": 1 } ```

en-us	#### Updating host macros  Replace all host macros with two new ones.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10126",         "macros": [             {                 "macro": "{$PASS}",                 "value": "password"             },             {                 "macro": "{$DISC}",                 "value": "sda",                 "description": "Updated description"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10126"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机宏  用两个新的宏替换所有主机宏。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10126",         "macros": [             {                 "macro": "{$PASS}",                 "value": "password"             },             {                 "macro": "{$DISC}",                 "value": "sda",                 "description": "Updated description"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10126"         ]     },     "id": 1 } ```

en-us	#### Updating host prototype custom interfaces  Replace inherited interfaces with host prototype custom interfaces.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.update",     "params": {         "hostid": "10092",         "custom_interfaces": "1",         "interfaces": [             {                 "main": "1",                 "type": "2",                 "useip": "1",                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": "2",                     "bulk": "1",                     "community": "{$SNMP_COMMUNITY}"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10092"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机原型自定义接口  用主机原型自定义接口替换继承的接口。  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.update",     "params": {         "hostid": "10092",         "custom_interfaces": "1",         "interfaces": [             {                 "main": "1",                 "type": "2",                 "useip": "1",                 "ip": "127.0.0.1",                 "dns": "",                 "port": "161",                 "details": {                     "version": "2",                     "bulk": "1",                     "community": "{$SNMP_COMMUNITY}"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10092"         ]     },     "id": 1 } ```

en-us	#### Updating host prototype tags  Replace host prototype tags with new ones.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.update",     "params": {         "hostid": "10092",         "tags": [             {                 "tag": "Datacenter",                 "value": "{#DATACENTER.NAME}"             },             {                 "tag": "Instance type",                 "value": "{#INSTANCE_TYPE}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10092"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机原型标签  替换新的主机原型标签  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostprototype.update",     "params": {         "hostid": "10092",         "tags": [             {                 "tag": "Datacenter",                 "value": "{#DATACENTER.NAME}"             },             {                 "tag": "Instance type",                 "value": "{#INSTANCE_TYPE}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10092"         ]     },     "id": 1 } ```

en-us	#### Updating host tags  Replace all host tags with a new one.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10387",         "tags": {             "tag": "OS",             "value": "RHEL 7"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10387"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机标签  用一个新的主机标签替换所有的主机标签。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.update",     "params": {         "hostid": "10387",         "tags": {             "tag": "OS",             "value": "CentOS 7"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10387"         ]     },     "id": 1 } ```

en-us	#### Updating item preprocessing options  Update an item prototype with item preprocessing rule “Custom multiplier”.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": "1",                 "params": "4",                 "error_handler": "2",                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项原型预处理选项  使用监控项原型预处理规则“自定义乘数”更新监控项。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "44211",  · "preprocessing": [  · {  · "type": "1",  · "params": "4",  · "error_handler": "2",  · "error_handler_params": "5"  · }  · ]  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44211"  · ]  · },  · "id": 1 } ```

en-us	#### Updating item preprocessing options  Update an item prototype with item preprocessing rule “Custom multiplier”.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": 1,                 "params": "4",                 "error_handler": 2,                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 更新监控项原型预处理选项  使用监控项原型预处理规则“自定义乘数”更新监控项。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "44211",  · "preprocessing": [  · {  · "type": "1",  · "params": "4",  · "error_handler": "2",  · "error_handler_params": "5"  · }  · ]  · },  · "auth": "700ca65537074ec963db7efabda78259",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "44211"  · ]  · },  · "id": 1 } ```

en-us	#### Updating LLD rule preprocessing options  Update an LLD rule with preprocessing rule “JSONPath”.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": "12",                 "params": "$.path.to.json",                 "error_handler": "2",                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 更新LLD规则预处理选项  使用预处理规则“JSONPath”更新LLD规则。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": "12",                 "params": "$.path.to.json",                 "error_handler": "2",                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Updating LLD rule preprocessing options  Update an LLD rule with preprocessing rule “JSONPath”.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": 12,                 "params": "$.path.to.json",                 "error_handler": 2,                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```
zh-cn	#### 更新LLD规则预处理选项  使用预处理规则“JSONPath”更新LLD规则。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "44211",         "preprocessing": [             {                 "type": "12",                 "params": "$.path.to.json",                 "error_handler": "2",                 "error_handler_params": "5"             }         ]     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "44211"         ]     },     "id": 1 } ```

en-us	#### Updating LLD rule script  Update an LLD rule script with a different script and remove unnecessary parameters that were used by previous script.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新LLD规则脚本  使用不同的脚本更新 LLD 规则脚本，并删除之前脚本使用的不必要参数。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```

en-us	#### Updating LLD rule script  Update an LLD rule script with a different script and remove unnecessary parameters that were used by previous script.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```
zh-cn	#### 更新LLD规则脚本  使用不同的脚本更新 LLD 规则脚本，并删除之前脚本使用的不必要参数。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "23865",         "parameters": [],         "script": "Zabbix.Log(3, 'Log test');\nreturn 1;"     },     "auth": "700ca65537074ec963db7efabda78259",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 1 } ```

en-us	#### Updating multiple triggers  Enable multiple triggers, that is, set their status to 0:  ```json {     "jsonrpc": "2.0",     "method": "trigger.update",     "params": [         {             "triggerid": "13938",             "status": 0         },         {             "triggerid": "13939",             "status": 0         }     ],     "auth": "0424bd59b807674191e7d77572075f33",     "id": 6 } ```  A successful response will contain the IDs of the updated triggers:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "13938",             "13939"         ]     },     "id": 6 } ```  ::: notetip This is the preferred method of updating. Some API methods like `host.massupdate` allow to write more simple code, but it's not recommended to use those methods, since they will be removed in the future releases. :::
zh-cn	#### 更新多个触发器  启用多个触发器，即将其状态设置为0：  ``` {.json} {     "jsonrpc": "2.0",     "method": "trigger.update",     "params": [         {             "triggerid": "13938",             "status": 0         },         {             "triggerid": "13939",             "status": 0         }     ],     "auth": "0424bd59b807674191e7d77572075f33",     "id": 6 } ```  成功的响应将包含被更新触发器的 ID数组：  ``` {.json} {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "13938",             "13939"         ]     },     "id": 6 } ```  ::: notetip 这是更新的首选方法。有些 API 方法比如 `host.massupdate` 允许编写更简单的代码，但不建议使用这些方法，因为它们将在未来的版本中删除。 :::

en-us	#### Updating problems  The problem update popup allows to:  -   comment on the problem -   view comments and actions so far -   change problem severity -   acknowledge/unacknowledge problem -   manually close problem  ![](../../assets/en/manual/acknowledges/update_problem.png){width="600"}  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |--|--------| |*Problem*|If only one problem is selected, the problem name is displayed.<br>If several problems are selected, *N problems selected* is displayed.| |*Message*|Enter text to comment on the problem (maximum 2048 characters).| |*History*|Previous activities and comments on the problem are listed, along with the time and user details.<br>For the meaning of icons used to denote user actions see the [event detail](/manual/web_interface/frontend_sections/monitoring/problems#viewing_details) page.<br>Note that history is displayed if only one problem is selected for the update.| |*Scope*|Define the scope of such actions as changing severity, acknowledging or manually closing problems:<br>**Only selected problem** - will affect this event only<br>**Selected and all other problems of related triggers** - in case of acknowledgment/closing problem, will affect this event and all other problems that are not acknowledged/closed so far. If the scope contains problems already acknowledged or closed, these problems will not be acknowledged/closed repeatedly. On the other hand, the number of message and severity change operations are not limited.| |*Change severity*|Mark the checkbox and click on the severity button to update problem severity.<br>The checkbox for changing severity is available if read-write permissions exist for at least one of the selected problems. Only those problems that are read-writable will be updated when clicking on *Update*.<br>If read-write permissions exist for none of the selected triggers, the checkbox is disabled.| |*Acknowledge*|Mark the checkbox to acknowledge the problem.<br>This checkbox is available if there is at least one unacknowledged problem among the selected.<br>It is not possible to add another acknowledgment for an already acknowledged problem (it is possible to add another comment though).| |*Unacknowledge*|Mark the checkbox to unacknowledge the problem.<br>This checkbox is available if there is at least one acknowledged problem among the selected.| |*Close problem*|Mark the checkbox to manually close the selected problem(s).<br>The checkbox for closing a problem is available if the *Allow manual close* option is checked in [trigger configuration](/manual/config/triggers/trigger) for at least one of the selected problems. Only those problems will be closed that are allowed to be closed when clicking on *Update*.<br>If no problem is manually closeable, the checkbox is disabled.<br>Already closed problems will not be closed repeatedly.|
zh-cn	#### 更新问题  问题更新弹出窗口允许：  -   评论问题 -   查看到目前为止的评论和操作 -   更改问题严重性 -   确认/取消确认(acknowledge/unacknowledge)问题 -   手动关闭问题  ![](../../assets/en/manual/acknowledges/update_problem.png){width="600"}  所有必填字段都标有红色星号。  |参数|描述| |---------|-----------| |*问题(Problem)*|如果只选择了一个问题，则会显示问题名称。<br>如果选择了多个问题，则会显示*已选择的 N 个问题*。| |*信息(Message)*|输入文本以评论问题（最多 2048 个字符）。| |*历史(History)*|列出了之前的操作记录和对该问题的评论，以及时间和用户详细信息。<br>有关用于表示用户操作的图标的含义，请参阅 [事件详细信息](/manual/web_interface/frontend_sections/monitoring/problems#viewing_details) 页面。<br>注意如果仅选择一个问题进行更新，则会显示历史记录。| |*范围(Scope)*|定义诸如更改严重性、确认或手动关闭问题等操作的范围：<br>**仅选定的问题(Only selected problem)** - 仅影响此事件<br>**选定的相关触发器的所有其他问题(Selected and all other problems of related triggers)** - 如果确认/关闭问题，将影响此事件和到目前为止尚未确认/关闭的所有其他问题。如果范围包含已经确认或关闭的问题，这些问题将不会重复确认/关闭。另一方面，消息的数量和严重性更改操作不受限制。| |*更改严重性(Change severity)*|标记复选框并单击严重性按钮以更新问题严重性。<br>如果至少有一个选定问题存在读写权限，则更改严重性的复选框可用。当点击更新时，只有那些可读写的问题才会被*更新*。<br>如果所有选定的触发器都没有读写权限，则该复选框被禁用。| |*确认(Acknowledge)*|标记复选框以确认问题。<br>如果所选中至少有一个未确认的问题，则此复选框可用。<br>无法为已确认的问题添加另一个确认（但是可以添加另一个评论）。| |*取消确认(Unacknowledge)*|标记复选框以取消确认问题。<br>如果在选定项中至少存在一个已确认的问题，则此复选框可用。<br>不可能对已经确认的问题再增加另外一个确认（尽管可以增加另外的评论）。| |*关闭问题(Close problem)*|标记复选框以手动关闭选定的问题。<br>如果在 [触发器配置](/manual/config/triggers/trigger)  中为至少一个选定的问题选中了 *允许手动关闭* 选项，则关闭问题的复选框可用。只有那些允许关闭的问题在点击 *更新(Update)* 时才会被关闭。<br>如果没有问题可以手动关闭，则该复选框被禁用。<br>已经关闭的问题不会重复关闭。|

en-us	#### Updating service tags  Make SLA with ID "5" to be calculated at monthly intervals for NoSQL related services, without changing its schedule or excluded downtimes; set SLO to 95%.  Request:  ```json {     "jsonrpc": "2.0",     "method": "sla.update",     "params": [         {             "slaid": "5",             "name": "NoSQL Database engines",             "slo": "95",             "period": 2,             "service_tags": [                 {                     "tag": "Database",                     "operator": "0",                     "value": "Redis"                 },                 {                     "tag": "Database",                     "operator": "0",                     "value": "MongoDB"                 }             ]         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 更新服务标签  为 NoSQL 相关服务每月计算一次 ID 为“5”的 SLA，不改变其时间表或排除停机时间；将 SLO 设置为 95%。  请求:  ```json {     "jsonrpc": "2.0",     "method": "sla.update",     "params": [         {             "slaid": "5",             "name": "NoSQL Database engines",             "slo": "95",             "period": 2,             "service_tags": [                 {                     "tag": "Database",                     "operator": "0",                     "value": "Redis"                 },                 {                     "tag": "Database",                     "operator": "0",                     "value": "MongoDB"                 }             ]         }     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Updating template dashboard pages  Rename the first dashboard page, replace widgets on the second dashboard page and add a new page as the third one. Delete all other dashboard pages.  Request:  ```json {     "jsonrpc": "2.0",     "method": "templatedashboard.update",     "params": {         "dashboardid": "2",         "pages": [             {                 "dashboard_pageid": 1,                 "name": 'Renamed Page'             },             {                 "dashboard_pageid": 2,                 "widgets": [                     {                         "type": "clock",                         "x": 0,                         "y": 0,                         "width": 4,                         "height": 3                     }                 ]             },             {                 "display_period": 60             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```
zh-cn	#### 更新模板仪表盘页面  重命名第一个仪表盘页面，替换第二个仪表盘页面上的组件，并添加一个新页面作为第三个页面。 删除所有其他仪表盘页面。  请求：  ```json {     "jsonrpc": "2.0",     "method": "templatedashboard.update",     "params": {         "dashboardid": "2",         "pages": [             {                 "dashboard_pageid": 1,                 "name": 'Renamed Page'             },             {                 "dashboard_pageid": 2,                 "widgets": [                     {                         "type": "clock",                         "x": 0,                         "y": 0,                         "width": 4,                         "height": 3                     }                 ]             },             {                 "display_period": 60             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```

en-us	#### Upgrade between minor versions  It is possible to upgrade between minor versions of 6.0.x (for example, from 6.0.1 to 6.0.3). Upgrading between minor versions is easy.  To execute Zabbix minor version upgrade it is required to run:      $ sudo yum upgrade 'zabbix-*'  To execute Zabbix server minor version upgrade run:      $ sudo yum upgrade 'zabbix-server-*'  To execute Zabbix agent minor version upgrade run:      $ sudo yum upgrade 'zabbix-agent-*'  or, for Zabbix agent 2:      $ sudo yum upgrade 'zabbix-agent2-*'  Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.
zh-cn	#### 小版本之间升级  可以在 6.0.x 的次要版本之间升级（例如，从 6.0.1 到 6.0.3）。 次要版本之间的升级很容易。  要执行 Zabbix 次要版本升级，需要运行：    · $ sudo yum upgrade 'zabbix-*'  要执行 Zabbix 服务器次要版本升级运行：    · $ sudo yum upgrade 'zabbix-server-*'  要执行 Zabbix agent次要版本升级运行：    · $ sudo yum upgrade 'zabbix-agent-*'  或者，对于 Zabbix 代理 2：    · $ sudo yum upgrade 'zabbix-agent2-*'  请注意，您也可以在这些命令中使用“更新”而不是“升级”。 虽然“升级”将删除过时的包，但“更新”将保留它们。

en-us	#### Upgrade between minor versions  It is possible to upgrade between minor versions of 6.0.x (for example, from 6.0.1 to 6.0.3). Upgrading between minor versions is easy.  To execute Zabbix minor version upgrade it is required to run:      $ sudo yum upgrade 'zabbix-*'  To execute Zabbix server minor version upgrade run:      $ sudo yum upgrade 'zabbix-server-*'  To execute Zabbix agent minor version upgrade run:      $ sudo yum upgrade 'zabbix-agent-*'  or, for Zabbix agent 2:      $ sudo yum upgrade 'zabbix-agent2-*'  Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.
zh-cn	#### Zabbix 次要版本之间的升级  如果要升级 Zabbix 6.0.x 的次要版本（例如：从 6.0.1 升级到 6.0.3），是非常容易的  在升级 Zabbix 所有组件的次要版本时，只需运行以下命令：      $ sudo yum upgrade 'zabbix-*'  在升级 Zabbix server 的次要版本时，只需运行以下命令：       $ sudo yum upgrade 'zabbix-server-*'  在升级 Zabbix agent 的次要版本时，只需运行以下命令：       $ sudo yum upgrade 'zabbix-agent-*'  在升级 Zabbix agent 2的次要版本时，只需运行以下命令：       $ sudo yum upgrade 'zabbix-agent2-*'  请注意，在这些命令中也可以使用'update' 而不是 'upgrade'。 两者区别是'upgrade' 将删除过时的软件包，但'update' 将保留它们。

en-us	#### Upgrade between minor versions  When upgrading between minor versions of 6.0.x (for example from 6.0.1 to 6.0.3) it is required to execute the same actions for server/proxy/agent as during the upgrade between major versions. The only difference is that when upgrading between minor versions no changes to the database are made.
zh-cn	#### 次版本之间的升级  升级 6.0.x 的次版本（例如从 6.0.1 到 6.0.3）时，需要对 server/proxy/agent 执行与主版本升级步骤相同的操作。唯一的区别是，在次版本之间进行升级时，不会对数据库进行任何更改。

en-us	#### Upgrade between minor versions  When upgrading between minor versions of 6.0.x (for example from 6.0.1 to 6.0.3) it is required to execute the same actions for server/proxy/agent as during the upgrade between major versions. The only difference is that when upgrading between minor versions no changes to the database are made.  
zh-cn	#### 次版本之间的升级  升级 6.0.x 的次版本（例如从 6.0.1 到 6.0.3）时，需要对 server/proxy/agent 执行与主版本升级步骤相同的操作。唯一的区别是，在次版本之间进行升级时，不会对数据库进行任何更改。

en-us	#### Upgrade procedure
zh-cn	#### 升级程序

en-us	#### Upgrade procedure
zh-cn	#### 升级过程

en-us	#### Upgrade procedure
zh-cn	#### 升级过程

en-us	#### - Upgrading  The Zabbix appliance packages may be upgraded. To do so, run:      dnf update zabbix*
zh-cn	#### - 升级  Zabbix Appliance 的包可以升级。为此，可以执行：      dnf update zabbix*

en-us	#### Usage
zh-cn	#### 使用方法

en-us	#### Usage example  Executing the script **check\_oracle.sh** with the first parameters '-h'. The second parameter will be replaced by IP address or DNS name, depending on the selection in the host properties.      check_oracle.sh["-h","{HOST.CONN}"]  Assuming host is configured to use IP address, Zabbix will execute:      check_oracle.sh '-h' '192.168.1.4'
zh-cn	#### 用法示例  使用第一个参数执行脚本 **check\_oracle.sh** '-h'。第二个参数将替换为 IP 地址或 DNS 名称， 取决于主机属性中的选择。      check_oracle.sh["-h","{HOST.CONN}"]  假设主机配置为使用 IP 地址，Zabbix 将执行：      check_oracle.sh '-h' '192.168.1.4'

en-us	#### Usage examples
zh-cn	#### 用法示例

en-us	##### Usage examples  **Example 1**  The example demonstrates how to run Zabbix server with MySQL database support, Zabbix web interface based on the Nginx web server and Zabbix Java gateway.  1\. Create network dedicated for Zabbix component containers:      docker network create --subnet 172.20.0.0/16 --ip-range 172.20.240.0/20 zabbix-net  2\. Start empty MySQL server instance      docker run --name mysql-server -t \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           --network=zabbix-net \           --restart unless-stopped \           -d mysql:8.0 \           --character-set-server=utf8 --collation-server=utf8_bin \           --default-authentication-plugin=mysql_native_password  3\. Start Zabbix Java gateway instance      docker run --name zabbix-java-gateway -t \           --network=zabbix-net \           --restart unless-stopped \           -d zabbix/zabbix-java-gateway:alpine-6.0-latest  4\. Start Zabbix server instance and link the instance with created MySQL server instance      docker run --name zabbix-server-mysql -t \           -e DB_SERVER_HOST="mysql-server" \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           -e ZBX_JAVAGATEWAY="zabbix-java-gateway" \           --network=zabbix-net \           -p 10051:10051 \           --restart unless-stopped \           -d zabbix/zabbix-server-mysql:alpine-6.0-latest  ::: noteclassic Zabbix server instance exposes 10051/TCP port (Zabbix trapper) to host machine. :::  5\. Start Zabbix web interface and link the instance with created MySQL server and Zabbix server instances      docker run --name zabbix-web-nginx-mysql -t \           -e ZBX_SERVER_HOST="zabbix-server-mysql" \           -e DB_SERVER_HOST="mysql-server" \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           --network=zabbix-net \           -p 80:8080 \           --restart unless-stopped \           -d zabbix/zabbix-web-nginx-mysql:alpine-6.0-latest  ::: noteclassic Zabbix web interface instance exposes 80/TCP port (HTTP) to host machine. :::  **Example 2**  The example demonstrates how to run Zabbix server with PostgreSQL database support, Zabbix web interface based on the Nginx web server and SNMP trap feature.  1\. Create network dedicated for Zabbix component containers:      docker network create --subnet 172.20.0.0/16 --ip-range 172.20.240.0/20 zabbix-net  2\. Start empty PostgreSQL server instance      docker run --name postgres-server -t \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           --network=zabbix-net \           --restart unless-stopped \           -d postgres:latest  3\. Start Zabbix snmptraps instance      docker run --name zabbix-snmptraps -t \           -v /zbx_instance/snmptraps:/var/lib/zabbix/snmptraps:rw \           -v /var/lib/zabbix/mibs:/usr/share/snmp/mibs:ro \           --network=zabbix-net \           -p 162:1162/udp \           --restart unless-stopped \           -d zabbix/zabbix-snmptraps:alpine-6.0-latest  ::: noteclassic Zabbix snmptrap instance exposes the 162/UDP port (SNMP traps) to host machine. :::  4\. Start Zabbix server instance and link the instance with created PostgreSQL server instance      docker run --name zabbix-server-pgsql -t \           -e DB_SERVER_HOST="postgres-server" \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           -e ZBX_ENABLE_SNMP_TRAPS="true" \           --network=zabbix-net \           -p 10051:10051 \           --volumes-from zabbix-snmptraps \           --restart unless-stopped \           -d zabbix/zabbix-server-pgsql:alpine-6.0-latest  ::: noteclassic Zabbix server instance exposes the 10051/TCP port (Zabbix trapper) to host machine. :::  5\. Start Zabbix web interface and link the instance with created PostgreSQL server and Zabbix server instances      docker run --name zabbix-web-nginx-pgsql -t \           -e ZBX_SERVER_HOST="zabbix-server-pgsql" \           -e DB_SERVER_HOST="postgres-server" \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           --network=zabbix-net \           -p 443:8443 \           -p 80:8080 \           -v /etc/ssl/nginx:/etc/ssl/nginx:ro \           --restart unless-stopped \           -d zabbix/zabbix-web-nginx-pgsql:alpine-6.0-latest  ::: noteclassic Zabbix web interface instance exposes the 443/TCP port (HTTPS) to host machine.\ Directory */etc/ssl/nginx* must contain certificate with required name. :::  **Example 3**  The example demonstrates how to run Zabbix server with MySQL database support, Zabbix web interface based on the Nginx web server and Zabbix Java gateway using `podman` on Red Hat 8.  1\. Create new pod with name `zabbix` and exposed ports (web-interface, Zabbix server trapper):      podman pod create --name zabbix -p 80:8080 -p 10051:10051  2\. (optional) Start Zabbix agent container in `zabbix` pod location:      podman run --name zabbix-agent \         -e ZBX_SERVER_HOST="127.0.0.1,localhost" \         --restart=always \         --pod=zabbix \         -d registry.connect.redhat.com/zabbix/zabbix-agent-60:latest  3\. Create `./mysql/` directory on host and start Oracle MySQL server 8.0:      podman run --name mysql-server -t \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           -v ./mysql/:/var/lib/mysql/:Z \           --restart=always \           --pod=zabbix \           -d mysql:8.0 \           --character-set-server=utf8 --collation-server=utf8_bin \           --default-authentication-plugin=mysql_native_password  4\. Start Zabbix server container:      podman run --name zabbix-server-mysql -t \                       -e DB_SERVER_HOST="127.0.0.1" \                       -e MYSQL_DATABASE="zabbix" \                       -e MYSQL_USER="zabbix" \                       -e MYSQL_PASSWORD="zabbix_pwd" \                       -e MYSQL_ROOT_PASSWORD="root_pwd" \                       -e ZBX_JAVAGATEWAY="127.0.0.1" \                       --restart=always \                       --pod=zabbix \                       -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-60  5\. Start Zabbix Java Gateway container:      podman run --name zabbix-java-gateway -t \           --restart=always \           --pod=zabbix \           -d registry.connect.redhat.com/zabbix/zabbix-java-gateway-60  6\. Start Zabbix web-interface container:      podman run --name zabbix-web-mysql -t \                       -e ZBX_SERVER_HOST="127.0.0.1" \                       -e DB_SERVER_HOST="127.0.0.1" \                       -e MYSQL_DATABASE="zabbix" \                       -e MYSQL_USER="zabbix" \                       -e MYSQL_PASSWORD="zabbix_pwd" \                       -e MYSQL_ROOT_PASSWORD="root_pwd" \                       --restart=always \                       --pod=zabbix \                       -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-60  ::: noteclassic Pod `zabbix` exposes 80/TCP port (HTTP) to host machine from 8080/TCP of `zabbix-web-mysql` container. :::
zh-cn	##### 使用示例  **示例 1**  该示例示范了如何运行 MySQL 数据库支持的 Zabbix Server 、基于 Nginx Web 服务器的 Zabbix Web 界面和 Zabbix Java 网关。  1\. 创建专用于 Zabbix 组件容器的网络：      docker network create --subnet 172.20.0.0/16 --ip-range 172.20.240.0/20 zabbix-net  2\. 启动空的 MySQL 服务器实例：      docker run --name mysql-server -t \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           --network=zabbix-net \           --restart unless-stopped \           -d mysql:8.0 \           --character-set-server=utf8 --collation-server=utf8_bin \           --default-authentication-plugin=mysql_native_password  3\. 启动 Zabbix Java 网关实例：       docker run --name zabbix-java-gateway -t \           --network=zabbix-net \           --restart unless-stopped \           -d zabbix/zabbix-java-gateway:alpine-5.4-latest  4\. 启动 Zabbix server 实例，并将其关联到已创建的 MySQL server 实例：      docker run --name zabbix-server-mysql -t \           -e DB_SERVER_HOST="mysql-server" \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           -e ZBX_JAVAGATEWAY="zabbix-java-gateway" \           --network=zabbix-net \           -p 10051:10051 \           --restart unless-stopped \           -d zabbix/zabbix-server-mysql:alpine-5.4-latest  ::: noteclassic Zabbix server 实例将 10051/TCP 端口（Zabbix trapper）暴露给主机。 :::  5\. 启动 Zabbix Web 界面，并将其关联到已创建的 MySQL server 和 Zabbix server 实例：      docker run --name zabbix-web-nginx-mysql -t \           -e ZBX_SERVER_HOST="zabbix-server-mysql" \           -e DB_SERVER_HOST="mysql-server" \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           --network=zabbix-net \           -p 80:8080 \           --restart unless-stopped \           -d zabbix/zabbix-web-nginx-mysql:alpine-5.4-latest  ::: noteclassic Zabbix web 界面实例将 80/TCP 端口（HTTP）暴露给主机。 :::  **示例 2**  该示例示范了如何运行 PostgreSQL 数据库支持的 Zabbix server、基于 Nginx Web 服务器的 Zabbix Web 界面和 SNMP trap功能。  1\. 创建专用于 Zabbix 组件容器的网络：      # docker network create --subnet 172.20.0.0/16 --ip-range 172.20.240.0/20 zabbix-net  2\. 启动空的 PostgreSQL server 实例：      docker run --name postgres-server -t \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           --network=zabbix-net \           --restart unless-stopped \           -d postgres:latest  3\. 启动 Zabbix snmptraps 实例：      docker run --name zabbix-snmptraps -t \           -v /zbx_instance/snmptraps:/var/lib/zabbix/snmptraps:rw \           -v /var/lib/zabbix/mibs:/usr/share/snmp/mibs:ro \           --network=zabbix-net \           -p 162:1162/udp \           --restart unless-stopped \           -d zabbix/zabbix-snmptraps:alpine-5.4-latest  ::: noteclassic Zabbix snmptrap 实例将 162/UDP 端口（SNMP traps）暴露给主机。 :::  4\. 启动 Zabbix server 实例，并将其关联到已创建的 PostgreSQL server 实例：      docker run --name zabbix-server-pgsql -t \           -e DB_SERVER_HOST="postgres-server" \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           -e ZBX_ENABLE_SNMP_TRAPS="true" \           --network=zabbix-net \           -p 10051:10051 \           --volumes-from zabbix-snmptraps \           --restart unless-stopped \           -d zabbix/zabbix-server-pgsql:alpine-5.4-latest  ::: noteclassic Zabbix server 实例将 10051/TCP 端口（Zabbix trapper）暴露给主机。 :::  5\. 启动 Zabbix Web 界面，并将其关联到已创建的 PostgreSQL server 和 Zabbix server 实例：      docker run --name zabbix-web-nginx-pgsql -t \           -e ZBX_SERVER_HOST="zabbix-server-pgsql" \           -e DB_SERVER_HOST="postgres-server" \           -e POSTGRES_USER="zabbix" \           -e POSTGRES_PASSWORD="zabbix_pwd" \           -e POSTGRES_DB="zabbix" \           --network=zabbix-net \           -p 443:8443 \           -p 80:8080 \           -v /etc/ssl/nginx:/etc/ssl/nginx:ro \           --restart unless-stopped \           -d zabbix/zabbix-web-nginx-pgsql:alpine-5.4-latest  ::: noteclassic Zabbix web 界面实例将 443/TCP 端口（HTTPS）暴露给主机。\ */etc/ssl/nginx* 目录必须包含具有所需名称的证书。 :::  **示例 3**  该示例示范了如何在Red Hat 8上使用 `podman` 运行 MySQL 数据库支持的 Zabbix Server 、基于 Nginx Web 服务器的 Zabbix Web 界面和 Zabbix Java 网关。  1\. 创建一个名为 `zabbix` 的 pod 并暴露端口 (web 界面、Zabbix server trapper)：      podman pod create --name zabbix -p 80:8080 -p 10051:10051  2\. （可选）在 `zabbix` pod 中启动 Zabbix agent 容器：      podman run --name zabbix-agent \         -eZBX_SERVER_HOST="127.0.0.1,localhost" \         --restart=always \         --pod=zabbix \         -d registry.connect.redhat.com/zabbix/zabbix-agent-50:latest  3\. 在主机上创建`./mysql/` 目录并启动 Oracle MySQL server 8.0:      podman run --name mysql-server -t \           -e MYSQL_DATABASE="zabbix" \           -e MYSQL_USER="zabbix" \           -e MYSQL_PASSWORD="zabbix_pwd" \           -e MYSQL_ROOT_PASSWORD="root_pwd" \           -v ./mysql/:/var/lib/mysql/:Z \           --restart=always \           --pod=zabbix \           -d mysql:8.0 \           --character-set-server=utf8 --collation-server=utf8_bin \           --default-authentication-plugin=mysql_native_password  3\. 启动 Zabbix server 容器：      podman run --name zabbix-server-mysql -t \                       -e DB_SERVER_HOST="127.0.0.1" \                       -e MYSQL_DATABASE="zabbix" \                       -e MYSQL_USER="zabbix" \                       -e MYSQL_PASSWORD="zabbix_pwd" \                       -e MYSQL_ROOT_PASSWORD="root_pwd" \                       -e ZBX_JAVAGATEWAY="127.0.0.1" \                       --restart=always \                       --pod=zabbix \                       -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-50  4\. 启动 Zabbix Java 网关容器：      podman run --name zabbix-java-gateway -t \           --restart=always \           --pod=zabbix \           -d registry.connect.redhat.com/zabbix/zabbix-java-gateway-50  5\. 启动 Zabbix web 界面 容器：      podman run --name zabbix-web-mysql -t \                       -e ZBX_SERVER_HOST="127.0.0.1" \                       -e DB_SERVER_HOST="127.0.0.1" \                       -e MYSQL_DATABASE="zabbix" \                       -e MYSQL_USER="zabbix" \                       -e MYSQL_PASSWORD="zabbix_pwd" \                       -e MYSQL_ROOT_PASSWORD="root_pwd" \                       --restart=always \                       --pod=zabbix \                       -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-50  ::: noteclassic `zabbix` pod 从 `zabbix-web-mysql` 容器的 8080/TCP 向 主机的 80/TCP port (HTTP) 暴露端口。 :::

en-us	#### Usage examples  Examples of keys for aggregate calculations.
zh-cn	#### 使用示例  用于聚合计算的键的示例

en-us	#### Usage      zabbix_js -s script-file -p input-param [-l log-level] [-t timeout]     zabbix_js -s script-file -i input-file [-l log-level] [-t timeout]     zabbix_js -h     zabbix_js -V  zabbix\_js accepts the following command line parameters:        -s, --script script-file          Specify the file name of the script to execute. If '-' is specified as file name, the script will be read from stdin.       -i, --input input-file            Specify the file name of the input parameter. If '-' is specified as file name, the input will be read from stdin.       -p, --param input-param           Specify the input parameter.       -l, --loglevel log-level          Specify the log level.       -t, --timeout timeout             Specify the timeout in seconds.       -h, --help                        Display help information.       -V, --version                     Display the version number.  Example:      zabbix_js -s script-file.js -p example
zh-cn	#### 用法      zabbix_js -s script-file -p input-param [-l log-level] [-t timeout]     zabbix_js -s script-file -i input-file [-l log-level] [-t timeout]     zabbix_js -h     zabbix_js -V  zabbix\_js 可接收如下命令行参数：        -s, --script script-file          指定待执行脚本的文件名。若 '-' 作为文件名时，脚本名由stdin输入。       -i, --input input-file            指定输入参数的文件名。若 '-' 作为文件名时，脚本名由stdin输入。       -p, --param input-param           指定输入参数。       -l, --loglevel log-level          指定日志级别。       -t, --timeout timeout             指定超时时间（单位：秒）。       -h, --help                        显示帮助信息。       -V, --version                     显示版本号。  例如：      zabbix_js -s script-file.js -p example

en-us	#### Use cases
zh-cn	#### 用例

en-us	#### Use cases
zh-cn	#### 用例

en-us	### Use cases  Some use cases for recovery operations are as follows:  1.  Notify on a recovery all users that were notified on the problem:     -  Select *Notify all involved* as operation type.  2.  Have multiple operations upon recovery: send a notification and execute a remote command:     -  Add operation types for sending a message and executing a command.  3.  Open a ticket in external helpdesk/ticketing system and close it when the problem is resolved:     -  Create an external script that communicates with the helpdesk system.     -  Create an action having operation that executes this script and thus opens a ticket.     -  Have a recovery operation that executes this script with other parameters and closes the ticket.     -  Use the {EVENT.ID} macro to reference the original problem.
zh-cn	### 用例  恢复操作的一些用例如下：  1.   通知所有收到问题通知的用户恢复：    -  选择*通知所有相关人员*作为操作类型。  2.   恢复后有多个操作：发送通知和执行远程命令：    -  添加发送消息和执行命令的操作类型。  3.   在外部帮助台/工单系统中打开一个工单，并在问题解决后将其关闭：    -  创建一个与服务台系统通信的外部脚本。    -  创建一个具有执行此脚本并因此打开工单的操作的动作。    -  进行恢复操作，使用其他参数执行此脚本并关闭票证。    -  使用 {EVENT.ID} 宏来引用原始问题。

en-us	#### Use cases  Some use cases for this functionality are as follows:  1.  Mark trigger events in the frontend     -   Define tags on trigger level;     -   See how all trigger problems are marked with these tags in         *Monitoring* → *Problems*. 2.  Mark all template-inherited problems     -   Define a tag on template level, for example 'App=MySQL';     -   See how those host problems that are created by triggers from         this template are marked with these tags in *Monitoring* →         *Problems*. 3.  Mark all host problems     -   Define a tag on host level, for example 'Service=JIRA';     -   See how all problems of the host triggers are marked with these         tags in *Monitoring* → *Problems* 4.  Group related items     -   Define a tag on item level, for example 'MySQL';     -   See all items tagged as 'MySQL' in *Latest data* by using the         tag filter 5.  Identify problems in a log file and close them separately     -   Define tags in the log trigger that will identify events using         value extraction by the `{{ITEM.VALUE<N>}.regsub()}` macro;     -   In trigger configuration, have multiple problem event generation         mode;     -   In trigger configuration, use [event         correlation](/manual/config/event_correlation): select the         option that OK event closes only matching events and choose the         tag for matching;     -   See problem events created with a tag and closed individually. 6.  Use it to filter notifications     -   Define tags on the trigger level to mark events by different         tags;     -   Use tag filtering in action conditions to receive notifications         only on the events that match tag data. 7.  Use information extracted from item value as tag value     -   Use an `{{ITEM.VALUE<N>}.regsub()}` macro in the tag value;     -   See tag values in *Monitoring* → *Problems* as extracted data         from item value. 8.  Identify problems better in notifications     -   Define tags on the trigger level;     -   Use an {EVENT.TAGS} macro in the problem notification;     -   Easier identify which application/service the notification         belongs to. 9.  Simplify configuration tasks by using tags on the template level     -   Define tags on the template trigger level;     -   See these tags on all triggers created from template triggers. 10. Create triggers with tags from low-level discovery (LLD)     -   Define tags on trigger prototypes;     -   Use LLD macros in the tag name or value;     -   See these tags on all triggers created from trigger prototypes.
zh-cn	#### 用例  此功能的一些用例如下：  1.  在前端标记触发事件     -   在触发器级别定义标签;     -   在*监控* → *问题*中查看所有触发问题是如何用这些标签标记的. 2.  标记所有模板继承的问题     -   在模板级别定义标签，例如'App=MySQL';     -   查在*监控*→* 问题 *中，可以看到由该模板中的触发器创建的那些主机问题是如何被标记为这些标记的。 3.  标记所有主机问题     -   在主机级别定义标签，例如'Service=JIRA';     -   在*监控*中的标签→*问题*中查看主机触发器的所有问题是如何用这些标记的。 4.  相关监控项组     -   在监控项级别定义标签，例如'MySQL';     -   使用 *最新数据* 的监控项标签过滤器查看所有标记为'MySQL'。 5.  识别日志文件中的问题并分别关闭     -   在日志触发器中定义标签，这些标签将通过提取宏{{ITEM.VALUE<N>}.regsub()}的值来标记事件;     -   在触发器配置中，使用多个问题事件生成模式;     -   在触发器配置中，使用 [event相关性](/manual/config/event_correlation): 选择OK 事件仅关闭匹配事件并选择匹配标签;     -   查看使用标签创建并单独关闭的问题事件。 6.  用来过滤通知     -   在触发级别上定义标签，以便通过不同的标签标记事件;     -   在动作条件中使用标签过滤，仅接收与标签数据匹配的事件通知。 7.   使用从监控项值中提取的信息作为标签值     -   在标签值中使用 `{{ITEM.VALUE<N>}.regsub()}` 宏;     -   在 *监控* → *问题* 中查看从监控项值中提取的数据作为标签值。 8.  在通知中更好地识别问题     -   在触发级别定义标签;     -   在问题通知中使用 {EVENT.TAGS} 宏;     -   更容易识别通知所属的应用程序/服务。 9.  使用模板级别的标签简化配置任务     -   在模板触发级别定义标签;     -   查看从模板触发器创建的所有触发器上的这些标记. 10. 使用来自低级别发现 (LLD) 的标签创建触发器     -   在触发器原型上定义标签;     -   在标签名称或值中使用 LLD 宏;     -   查看从触发器原型创建的所有触发器上的这些标签。

en-us	#### Use cases  User macros with context can be defined to accomplish more flexible thresholds in trigger expressions (based on the values retrieved by low-level discovery). For example, you may define the following macros:  -   {$LOW\_SPACE\_LIMIT} = 10 -   {$LOW\_SPACE\_LIMIT:/home} = 20 -   {$LOW\_SPACE\_LIMIT:regex:"\^\\/\[a-z\]+$"} = 30  Then a low-level discovery macro may be used as macro context in a trigger prototype for mounted file system discovery:      last(/host/vfs.fs.size[{#FSNAME},pfree])<{$LOW_SPACE_LIMIT:"{#FSNAME}"}  After the discovery different low-space thresholds will apply in triggers depending on the discovered mount points or file system types. Problem events will be generated if:  -   /home folder has less than 20% of free disk space -   folders that match the regexp pattern (like /etc, /tmp or /var) have     less than 30% of free disk space -   folders that don't match the regexp pattern and are not /home have     less than 10% of free disk space
zh-cn	####  用例  可以定义具有上下文的用户宏以实现更灵活触发器表达式中的阈值（基于检索到的值低级发现）。例如，您可以定义以下宏：  - {$LOW\_SPACE\_LIMIT} = 10 - {$LOW\_SPACE\_LIMIT:/home} = 20 - {$LOW\_SPACE\_LIMIT:正则表达式:"\^\\/\[a-z\]+$"} = 30  然后一个低级发现宏可以用作宏上下文已挂载文件系统发现的触发器原型：   · last(/host/vfs.fs.size[{#FSNAME},pfree])<{$LOW_SPACE_LIMIT:"{#FSNAME}"}  发现后将应用不同的低空间阈值根据发现的挂载点或文件系统类型触发。如果出现以下情况，将生成问题事件：  - /home 文件夹的可用磁盘空间不足 20% - 匹配正则表达式模式的文件夹（如 /etc、/tmp 或 /var）具有不到 30% 的可用磁盘空间 - 与正则表达式模式不匹配且不是 /home 的文件夹有不到 10% 的可用磁盘空间

en-us	#### user  Changes:\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) `user.create` and `user.update`: implemented password strength validation according the password policy.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) added new method `user.unblock`.\
zh-cn	 #### 用户  变更：\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) `user.create`和`user.update`：根据密码策略实现密码强度验证。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 添加新方法`user.unblock`。\

en-us	#### user  Changes:\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) added new method `user.unblock`.\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) `user.create`, `user.update`: implemented password strength validation according the password policy.\
zh-cn	 #### 用户  变更：\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) `user.create`和`user.update`：根据密码策略实现密码强度验证。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 添加新方法`user.unblock`。\

en-us	#### user  Changes:\ [ZBXNEXT-7971](https://support.zabbix.com/browse/ZBXNEXT-7971) `user.create`, `user.update`: increased max length of the "url" field to 2048 characters.\
zh-cn	#### 用户  变化：\ [ZBXNEXT-7971](https://support.zabbix.com/browse/ZBXNEXT-7971) `user.create`、`user.update`：将“url”字段的最大长度增加到 2048 个字符。\

en-us	# user.checkAuthentication
zh-cn	# 检查认证

en-us	#### User-configured ciphersuites  The built-in ciphersuite selection criteria can be overridden with user-configured ciphersuites.  ::: noteimportant User-configured ciphersuites is a feature intended for advanced users who understand TLS ciphersuites, their security and consequences of mistakes, and who are comfortable with TLS troubleshooting. :::  The built-in ciphersuite selection criteria can be overridden using the following parameters:  |Override scope|Parameter|Value|Description| |--------------|---------|-----|-----------| |Ciphersuite selection for certificates|TLSCipherCert13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Certificate-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherCert|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Certificate-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Ciphersuite selection for PSK|TLSCipherPSK13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|PSK-based ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherPSK|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|PSK-based ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)| |Combined ciphersuite list for certificate and PSK|TLSCipherAll13|Valid OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.3 protocol (their values are passed to the OpenSSL function SSL\_CTX\_set\_ciphersuites()).|Ciphersuite selection criteria for TLS 1.3<br><br>Only OpenSSL 1.1.1 or newer.| |^|TLSCipherAll|Valid OpenSSL [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) for TLS 1.2 or valid GnuTLS [priority strings](https://gnutls.org/manual/html_node/Priority-Strings.html). Their values are passed to the SSL\_CTX\_set\_cipher\_list() or gnutls\_priority\_init() functions, respectively.|Ciphersuite selection criteria for TLS 1.2/1.3 (GnuTLS), TLS 1.2 (OpenSSL)|  To override the ciphersuite selection in [zabbix\_get](/manpages/zabbix_get) and [zabbix\_sender](/manpages/zabbix_sender) utilities - use the command-line parameters:  -   `--tls-cipher13` -   `--tls-cipher`  The new parameters are optional. If a parameter is not specified, the internal default value is used. If a parameter is defined it cannot be empty.  If the setting of a TLSCipher\* value in the crypto library fails then the server, proxy or agent will not start and an error is logged.  It is important to understand when each parameter is applicable.
zh-cn	####  用户配置密码套件  内置的密码套件选择标准可以被用户配置的密码套件覆盖。  ::: noteimportant 用户配置的密码套件是针对了解TLS密码套件、其安全性和错误后果以及熟悉TLS故障排除的高级用户的特性。 :::  内置的密码套件选择标准可以使用以下参数覆盖:  |覆盖范围|参数|值|描述| |--------------|---------|-----|-----------| |证书的密码套件选择|TLSCipherCert13|有效 OpenSSL 1.1.1 [cipher strings](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) 对于TLS 1.3协议(它们的值被传递到OpenSSL函数SSL\_CTX\_set\_ciphersuites())。|TLS 1.3的基于证书的加密套件选择标准<br><br>仅支持OpenSSL 1.1.1及以上版本。| |^|TLSCipherCert|针对TLS 1.2的有效OpenSSL[密码字符串](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) 或有效的GnuTLS[优先级字符串](https://gnutls.org/manual/html_node/Priority-Strings.html)。它们的值分别传递给SSL\_CTX\_set\_cipher\_list()或gnutls\_priority\_init()函数。|针对TLS 1.2/1.3 (GnuTLS)、TLS 1.2 (OpenSSL)的基于证书的密码套件选择标准。| |Ciphersuite selection for PSK|TLSCipherPSK13|有效的OpenSSL 1.1.1[密码字符串](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html) 对于TLS 1.3协议(它们的值被传递到OpenSSL函数SSL\_CTX\_set\_ciphersuites())。|基于psk的TLS 1.3加密套件选择标准<br><br>仅支持OpenSSL 1.1.1及以上版本。| |^|TLSCipherPSK|对于TLS 1.2有效的OpenSSL[密码字符串](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html)或有效的GnuTLS[优先级字符串](https://gnutls.org/manual/html_node/Priority-Strings.html)。它们的值分别传递给SSL\_CTX\_set\_cipher\_list()或gnutls\_priority\_init()函数。|基于psk的TLS 1.2/1.3 (GnuTLS)、TLS 1.2 (OpenSSL)加密套件选择标准。| |Combined ciphersuite list for certificate and PSK|TLSCipherAll13|TLS 1.3协议的有效的OpenSSL 1.1.1[密码字符串](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html)(它们的值被传递到OpenSSL函数SSL\_CTX\_set\_ciphersuites())。|TLS 1.3<br><br>仅支持OpenSSL 1.1.1及以上版本。| |^|TLSCipherAll|对于TLS 1.2有效的OpenSSL[密码字符串](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html)或有效的GnuTLS[优先级字符串](https://gnutls.org/manual/html_node/Priority-Strings.html)。它们的值分别传递给SSL\_CTX\_set\_cipher\_list()或gnutls\_priority\_init()函数。|针对TLS 1.2/1.3 (GnuTLS)、TLS 1.2 (OpenSSL)的加密套件选择标准.|  在[zabbix\_get](/manpages/zabbix_get)和[zabbix\_sender](/manpages/zabbix_sender)工具中覆盖密码套件选择 - 使用命令行参数:  -   `--tls-cipher13` -   `--tls-cipher`  新参数为可选参数。 如果没有指定参数，则使用内部的默认值。 如果参数已定义，则它不能为空。  如果加密库中的tlsciphher \*值设置失败，则server、proxy或agent将无法启动，并记录一个错误。  理解每个参数何时适用是很重要的。

en-us	# user.create
zh-cn	# 创建用户

en-us	# user.delete
zh-cn	# 删除用户

en-us	# user.get
zh-cn	# 查询用户

en-us	#### usergroup  Changes:\ [ZBXNEXT-6866](https://support.zabbix.com/browse/ZBXNEXT-6866) `usergroup.create`, `usergroup.update`: `userids` parameter is now deprecated. Use `users` instead.\
zh-cn	 #### 用户组  变更：\ [ZBXNEXT-6866](https://support.zabbix.com/browse/ZBXNEXT-6866) `usergroup.create`，`usergroup.update`：`userids`参数现在已被弃用。改为使用`users`。\

en-us	#### usergroup  Changes:\ [ZBXNEXT-6866](https://support.zabbix.com/browse/ZBXNEXT-6866) `usergroup.create`, `usergroup.update`: `userids` parameter is now deprecated. Use `users` instead.\
zh-cn	 #### 用户组  变更：\ [ZBXNEXT-6866](https://support.zabbix.com/browse/ZBXNEXT-6866) `usergroup.create`，`usergroup.update`：`userids`参数现在已被弃用。改为使用`users`。\

en-us	# usergroup.create
zh-cn	# 创建用户组

en-us	# usergroup.delete
zh-cn	# 删除用户组

en-us	# usergroup.get
zh-cn	# 查询用户组

en-us	# > User group object  The following objects are directly related to the `usergroup` API.
zh-cn	# > 用户组对象  以下对象与`usergroup` 接口相关.

en-us	#### User groups  A listing of existing user groups with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/user_groups0.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the user group. Clicking on the user group name opens the user group [configuration form](/manual/config/users_and_usergroups/usergroup#configuration).| |*\#*|The number of users in the group. Clicking on *Users* will display the respective users filtered out in the user list.| |*Members*|Usernames of individual users in the user group (with name and surname in parentheses). Clicking on the username will open the user configuration form. Users from disabled groups are displayed in red.| |*Frontend access*|Frontend access level is displayed:<br>**System default** - Zabbix, LDAP or HTTP authentication; depending on the chosen authentication [method](authentication)<br>**Internal** - the user is authenticated by Zabbix regardless of system settings<br>**Disabled** - frontend access for this user is disabled.<br>By clicking on the current level you can change it.| |*Debug mode*|[Debug mode](/manual/web_interface/debug_mode) status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it.| |*Status*|User group status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it.|  To configure a new user group, click on the *Create user group* button in the top right-hand corner.
zh-cn	#### 用户组  将显示现有用户组及其详细信息的列表。  ![](../../../../../assets/en/manual/web_interface/user_groups0.png){width="600"}  显示数据：  |栏目|说明| |--------|------------| |*名称*|用户组的名称。点击用户组名打开用户组[配置表单](/manual/config/users_and_usergroups/usergroup#configuration)。| |*\#*|组中的用户数。单击 *用户* 将显示在用户列表中过滤掉的各个用户。| |*成员*|用户组中各个用户的用户名（括号中包含姓名和姓氏）。单击用户名将打开用户配置表单。来自禁用组的用户显示为红色。| |*前端访问*|显示前端访问级别：<br>**系统默认** - Zabbix, LDAP or HTTP 认证; 取决于选择的身份验证 [方法]（身份验证）<br>**内部** - 无论系统设置如何，用户都由 Zabbix 进行身份验证<br>**停用** - 此用户的前端访问被禁用。<br>通过单击当前级别，您可以更改它。| |*调试模式*|[调试模式](/manual/web_interface/debug_mode) 显示状态 - *Enabled* 或 *Disabled*。通过单击状态，您可以更改它。| |*状态*|显示用户组状态 - *启用* 或 *停用*。通过单击状态可以更改。|  要配置新用户组，请单击右上角的*创建用户组*按钮。

en-us	### User groups  The user groups object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**usrgrpid**<br>(required)|string|ID of user group to send the report to.| |access\_userid|string|ID of user on whose behalf the report will be generated.<br><br>0 - *(default)* Generate report by recipient.|
zh-cn	### 用户组  用户组对象包含以下属性： |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>(必要)|字符串|发送报告的用户组ID。| |access\_userid|字符串|将为其生成报告的用户组ID。<br><br>0 - *(缺省值)* 按收件人生成报告。|

en-us	### User groups  The user groups object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>(required)|string|ID of user group to send the report to.| |access\_userid|string|ID of user on whose behalf the report will be generated.<br><br>0 - *(default)* Generate report by recipient.|
zh-cn	### 用户组  用户组对象包含以下属性： |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**usrgrpid**<br>(必要)|字符串|发送报告的用户组ID。| |access\_userid|字符串|将为其生成报告的用户组ID。<br><br>0 - *(缺省值)* 按收件人生成报告。|

en-us	### User group  The user group object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |usrgrpid|string|*(readonly)* ID of the user group.| |**name**<br>(required)|string|Name of the user group.| |debug\_mode|integer|Whether debug mode is enabled or disabled.<br><br>Possible values are:<br>0 - *(default)* disabled;<br>1 - enabled.| |gui\_access|integer|Frontend authentication method of the users in the group.<br><br>Possible values:<br>0 - *(default)* use the system default authentication method;<br>1 - use internal authentication;<br>2 - use LDAP authentication;<br>3 - disable access to the frontend.| |users\_status|integer|Whether the user group is enabled or disabled.<br><br>Possible values are:<br>0 - *(default)* enabled;<br>1 - disabled.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 用户组  用户组对象具有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |usrgrpid|string|*(只读)* 用户组ID.| |**name**<br>(必需)|string|用户组名称.| |debug\_mode|integer|是否启用或禁用调试模式.<br><br>可用值:<br>0 - *(default)* 禁用;<br>1 - 启用.| |gui\_access|integer|组内用户的前端身份验证方法.<br><br>可用值:<br>0 - *(default)* 使用系统默认身份验证方法;<br>1 - 使用内部认证;<br>2 - 使用LDAP认证;<br>3 - 禁止访问前端.| |users\_status|integer|用户组是启用还是禁用.<br><br>可用值:<br>0 - *(default)* 启用;<br>1 - 禁用.|   注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# User group  This class is designed to work with user groups.  Object references:\  -   [User group](/manual/api/reference/usergroup/object#user_group)  Available methods:\  -   [usergroup.create](/manual/api/reference/usergroup/create) -     creating new user groups -   [usergroup.delete](/manual/api/reference/usergroup/delete) -     deleting user groups -   [usergroup.get](/manual/api/reference/usergroup/get) - retrieving     user groups -   [usergroup.update](/manual/api/reference/usergroup/update) -     updating user groups
zh-cn	# 用户组  这个类用于操作用户组.  对象引用:\  -   [用户组](/manual/api/reference/usergroup/object#user_group)  可用方法:\  -   [usergroup.create](/manual/api/reference/usergroup/create) - 创建新用户组 -   [usergroup.delete](/manual/api/reference/usergroup/delete) - 删除用户组 -   [usergroup.get](/manual/api/reference/usergroup/get) - 查询用户组 -   [usergroup.update](/manual/api/reference/usergroup/update) - 更新用户组

en-us	# usergroup.update
zh-cn	# 更新用户组

en-us	# user.login
zh-cn	# 登录用户

en-us	# user.logout
zh-cn	# 注销用户

en-us	#### User macro context  See [user macros with context](/manual/config/macros/user_macros_context).
zh-cn	#### 用户宏上下文  请参阅 [用户宏上下文](/manual/config/macros/user_macros_context)。

en-us	# usermacro.create
zh-cn	# 创建用户宏

en-us	# usermacro.createglobal
zh-cn	# 创建全局宏

en-us	# usermacro.delete
zh-cn	# 删除主机宏

en-us	# usermacro.deleteglobal
zh-cn	# 删除全局宏

en-us	# usermacro.get
zh-cn	# 查询用户宏

en-us	# > User macro object  The following objects are directly related to the `usermacro` API.
zh-cn	# > 用户宏对象  以下对象均与 `usermacro` 接口相关 .

en-us	##### User macros in item name no longer supported  The support for user macros in item names (including discovery rule names), deprecated since Zabbix 4.0, has been fully removed.
zh-cn	##### 不再支持监控项名称中的用户宏  自 Zabbix 4.0 起已弃用的监控项名称（包括发现规则名称）中对用户宏的支持已被完全删除。

en-us	##### User macros in item name no longer supported  The support for user macros in item names (including discovery rule names), deprecated since Zabbix 4.0, has been fully removed.
zh-cn	##### 不再支持监控项名称中的用户宏  自 Zabbix 4.0 起已弃用的监控项名称（包括发现规则名称）中对用户宏的支持已被完全删除。

en-us	# User macro  This class is designed to work with host and global macros.  Object references:\  -   [Global macro](/manual/api/reference/usermacro/object#global_macro) -   [Host macro](/manual/api/reference/usermacro/object#host_macro)  Available methods:\  -   [usermacro.create](/manual/api/reference/usermacro/create) -     creating new host macros -   [usermacro.createglobal](/manual/api/reference/usermacro/createglobal) -     creating new global macros -   [usermacro.delete](/manual/api/reference/usermacro/delete) -     deleting host macros -   [usermacro.deleteglobal](/manual/api/reference/usermacro/deleteglobal) -     deleting global macros -   [usermacro.get](/manual/api/reference/usermacro/get) - retrieving     host and global macros -   [usermacro.update](/manual/api/reference/usermacro/update) -     updating host macros -   [usermacro.updateglobal](/manual/api/reference/usermacro/updateglobal) -     updating global macros
zh-cn	# 用户宏  该类用于处理主机宏和全局宏.  对象引用:\  -   [全局宏](/manual/api/reference/usermacro/object#global_macro) -   [主机宏](/manual/api/reference/usermacro/object#host_macro)  可用方法:\  -   [usermacro.create](/manual/api/reference/usermacro/create) - 创建主机宏 -   [usermacro.createglobal](/manual/api/reference/usermacro/createglobal) - 创建全局宏 -   [usermacro.delete](/manual/api/reference/usermacro/delete) - 删除主机宏 -   [usermacro.deleteglobal](/manual/api/reference/usermacro/deleteglobal) - 删除全局宏 -   [usermacro.get](/manual/api/reference/usermacro/get) - 查询主机宏和全局宏 -   [usermacro.update](/manual/api/reference/usermacro/update) - 更新主机宏 -   [usermacro.updateglobal](/manual/api/reference/usermacro/updateglobal) - 更新全局宏

en-us	# usermacro.update
zh-cn	# 更新主机宏

en-us	# usermacro.updateglobal
zh-cn	# 更新全局宏

en-us	#### User media  Once the e-mail media type is configured, go to the *Administration → Users* section and edit user profile to assign e-mail media to the user. Steps for setting up user media, being common for all media types, are described on the [Media types](/manual/config/notifications/media#user_media) page.
zh-cn	#### 用户媒介  当完成电子邮件媒介类型的配置，请前往 *管理 → 用户* 配置栏，对用户属性中的电子邮件媒介进行配置。 用户媒介的设定步骤， 该设定适用于所有媒介类型， 请参考 [媒介类型](/manual/config/notifications/media#user_media) 页面。

en-us	#### User media  Once the media type is configured, go to the *Administration → Users* section and assign the webhook media to an existing user or create a new user to represent the webhook. Steps for setting up user media for an existing user, being common for all media types, are described on the [Media types](/manual/config/notifications/media#user_media) page.  If a webhook uses tags to store ticket\\message ID, avoid assigning the same webhook as a media to different users as doing so may cause webhook errors (applies to the majority of webhooks that utilize *Include event menu entry* option). In this case, the best practice is to create a dedicated user to represent the webhook:  1.  After configuring the webhook media type, go to the *Administration     → Users* section and create a dedicated Zabbix user to represent the     webhook - for example, with a username *Slack* for the Slack     webhook. All settings, except media, can be left at their defaults     as this user will not be logging into Zabbix. 2.  In the user profile, go to a tab *Media* and [add a     webhook](/manual/config/notifications/media#user_media) with the     required contact information. If the webhook does not use a *Send     to* field, enter any combination of supported characters to bypass     validation requirements. 3.  Grant this user at least read     [permissions](/manual/config/users_and_usergroups/permissions#permissions_to_host_groups)     to all hosts for which it should send the alerts.  When configuring alert action, add this user in the *Send to users* field in Operation details - this will tell Zabbix to use the webhook for notifications from this action.
zh-cn	#### 用户媒介  媒介类型配置完成后， 前往 *管理 → 用户* 部分，为一个现有用户或创建一个新用户并指定其webhook媒介。关于如何为用户指定用户媒介的方式和指定其它媒介类型类似，具体请参见 [媒介类型](/manual/config/notifications/media#user_media)。  如果webhook使用标签来存储 ticket\\message ID, 避免将同一个 webhook 作为媒体分配给不同的用户，因为这样做可能会导致webhook错误 (适用于大多数使用了 _Include event menu entry_ 选项)。 在这种情况下，最好的做法是创建一个专用的用户来表示webhook:  1.  配置好webhook媒体类型后， 前往 *管理 → 用户* 部分，并创建一个专用的Zabbix用户来表示webhook - 例如, 为 Slack webhook添加一个别名  _Slack_。 所有的设置可以保持默认值（除了媒体），因为这个用户不会登录到Zabbix。 2.  在用户配置中， 进入*Media* 选项卡并且填写  [add a webhook](/manual/config/notifications/media#user_media)  所需的联系信息。 如果webhook没有使用*Send to*  字段, 可以输入任何支持的字符组合来绕过验证要求。 3.  至少授予该用户对要向其发送警报的所有主机有可读的 [权限](/manual/config/users_and_usergroups/permissions#permissions_to_host_groups)。  配置告警动作时，请在*Send to users*字段中添加该用户 - 这将告诉Zabbix使用webhook来获取来自这个动作的通知。

en-us	#### User media  Once the SMS media type is configured, go to the *Administration → Users* section and edit user profile to assign SMS media to the user. Steps for setting up user media, being common for all media types, are described on the [Media types](/manual/config/notifications/media#user_media) page.
zh-cn	#### 用户媒介 配置完SMS媒体类型后，需进入 *管理 →用户* 为用户配置SMS媒介。配置用户媒介的步骤和配置其它媒介类型的方式类似，可以参见[媒介类型](/manual/config/notifications/media#user_media) 

en-us	#### User media  The *Media* tab contains a listing of all media defined for the user. Media are used for sending notifications. Click on *Add* to assign media to the user.  See the [Media types](/manual/config/notifications/media#user_media) section for details on configuring user media.
zh-cn	#### 用户媒体  *Media* 选项卡包含为用户定义的所有媒体的列表。媒体用于发送通知。点击 *Add* 分配媒体给用户。  请参阅 [媒体类型](/manual/config/notifications/media#user_media)有关配置用户媒体的详细信息部分。

en-us	# > User object  The following objects are directly related to the `user` API.
zh-cn	# > 用户对象  以下对象都是与 `user` 相关的API.

en-us	##### User passwords  Previously, spaces in user passwords have been automatically trimmed in both the User configuration form and the Login form. After the introduction of configurable [password complexity requirements](/manual/introduction/whatsnew600#password_requirements), spaces in passwords are no longer trimmed. So users, who thought that they had spaces in their passwords, will not be able to log in as usual and will have to enter their 'old' password without spaces. To continue using passwords with spaces, they will need to recreate their passwords.
zh-cn	##### 用户密码  以前，在用户配置表单和登录表单中，用户密码中的空格已被自动修剪。引入可配置 [密码复杂度要求](/manual/introduction/whatsnew600#password_requirements) 后，密码中的空格不再修剪。因此，密码中有空格的用户将无法像往常一样登录，而必须输入没有空格的 '旧' 密码。要继续使用带空格的密码，他们需要重新创建密码。

en-us	#### User permission check  Does the user have permission to write to hosts whose names begin with "MySQL" or "Linux" ?  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "countOutput": true,         "search": {             "host": ["MySQL", "Linux"]         },         "editable": true,         "startSearch": true,         "searchByAny": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": "0",     "id": 1 } ```  ::: noteclassic Zero result means no hosts with read/write permissions. :::
zh-cn	#### 用户权限检查  用户是否有权限修改以“MySQL”或“Linux”开头的主机？  请求：  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "countOutput": true,         "search": {             "host": ["MySQL", "Linux"]         },         "editable": true,         "startSearch": true,         "searchByAny": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": "0",     "id": 1 } ```  ::: noteclassic 结果0，表示没有具有读/写权限的主机。 :::

en-us	#### User role  The user role defines which parts of UI, which API methods, and which actions are available to the user. The following roles are pre-defined in Zabbix:  |User type|Description| |---------|-----------| |*Guest role*|The user has access to the Monitoring, Inventory, and Reports menu sections, but without the rights to perform any actions.| |*User role*|The user has access to the Monitoring, Inventory, and Reports menu sections. The user has no access to any resources by default. Any permissions to host groups must be explicitly assigned.| |*Admin role*|The user has access to the Monitoring, Inventory, Reports and Configuration menu sections. The user has no access to any host groups by default. Any permissions to host groups must be explicitly given.| |*Super Admin role*|The user has access to all menu sections. The user has a read-write access to all host groups. Permissions cannot be revoked by denying access to specific host groups.|  [User roles](/manual/web_interface/frontend_sections/administration/user_roles) are configured in the *Administration→User roles* section. Super Admins can modify or delete pre-defined roles and create more roles with custom sets of permissions.  To assign a role to the user, go to the Permissions tab in the user configuration form, locate the *Role* field and select a role. Once a role is selected a list of associated permissions will be displayed below.  ![user\_permissions.png](../../../../assets/en/manual/config/user_permissions.png)
zh-cn	#### 用户角色  用户角色定义了 UI 的哪些部分、哪些 API 方法以及哪些操作可供用户使用。以下角色是预定义的在Zabbix：  |用户类型|说明| |---------|------------| |*访客角色*|用户有权访问“监控”、“清单”和“报告”菜单部分，但无权执行任何操作。| |*用户角色*|用户有权访问“监控”、“清单”和“报告”菜单部分。默认情况下，用户无权访问任何资源。必须明确分配对主机组的任何权限。| |*管理员角色*|用户有权访问“监控”、“库存”、“报告”和“配置”菜单部分。默认情况下，用户无权访问任何主机组。必须明确授予对主机组的任何权限。| |*超级管理员角色*|用户有权访问所有菜单部分。用户具有对所有主机组的读写访问权限。不能通过拒绝对特定主机组的访问来撤销权限。|  [用户角色](/manual/web_interface/frontend_sections/administration/user_roles)在 *Administration→User roles* 部分进行配置。超级管理员可以修改或删除预定义的角色并使用自定义创建更多角色权限集。  要为用户分配角色，请转到用户中的权限选项卡配置表单，找到 *Role* 字段并选择一个角色。一旦角色被选中，将显示相关权限列表以下。  ![user\_permissions.png](../../../../assets/en/manual/config/user_permissions.png)

en-us	#### Users  Add users that will have access to Zabbix, assign them to user groups and grant permissions. Make roles for granular management of user rights. Track configuration changes each user has done. Configure media types and multiple ways users will receive alerts.  [User API](/manual/api/reference/user) | [User group API](/manual/api/reference/usergroup) | [User role API](/manual/api/reference/role) | [Media type API](/manual/api/reference/mediatype) | [Audit log API](/manual/api/reference/auditlog)
zh-cn	#### 用户  添加将有权访问 Zabbix 的用户，将其分配到用户组并授予权限。创建角色以精细管理用户权限。跟踪每个用户已完成的配置更改。配置媒介类型和用户接收警报的多种方式。  [User API](/manual/api/reference/user) | [User group API](/manual/api/reference/usergroup) | [User role API](/manual/api/reference/role) | [Media type API](/manual/api/reference/mediatype) | [Audit log API](/manual/api/reference/auditlog)

en-us	#### Users  A listing of existing users with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/users.png){width="600"}  From the dropdown to the right in the *Users* bar you can choose whether to display all users or those belonging to one particular group.  Displayed data:  |Column|Description| |------|-----------| |*Username*|Username for logging into Zabbix. Clicking on the username opens the user [configuration form](/manual/config/users_and_usergroups/user).| |*Name*|First name of the user.| |*Last name*|Second name of the user.| |*User role*|[User role](/manual/web_interface/frontend_sections/administration/user_roles) is displayed.| |*Groups*|Groups that the user is a member of are listed. Clicking on the user group name opens the user group configuration form. Disabled groups are displayed in red.| |*Is online?*|The on-line status of the user is displayed - *Yes* or *No*. The time of last user activity is displayed in parentheses.| |*Login*|The login status of the user is displayed - *Ok* or *Blocked*. A user can become temporarily blocked upon exceeding the number of unsuccessful login attempts set in the *[Administration→General](/manual/web_interface/frontend_sections/administration/general#other_parameters)* section (five by default). By clicking on *Blocked* you can unblock the user.| |*Frontend access*|Frontend access level is displayed - *System default*, *Internal* or *Disabled*, depending on the one set for the whole user group.| |*API access*|API access status is displayed - *Enabled* or *Disabled*, depending on the one set for the user role.| |*Debug mode*|Debug mode status is displayed - *Enabled* or *Disabled*, depending on the one set for the whole user group.| |*Status*|User status is displayed - *Enabled* or *Disabled*, depending on the one set for the whole user group.|  To configure a new user, click on the *Create user* button in the top right-hand corner.
zh-cn	#### 用户  将显示现有用户的列表及其详细信息。  ![](../../../../../assets/en/manual/web_interface/users.png){width="600"}  从 *用户* 栏右侧的下拉列表中，您可以选择是显示所有用户还是显示属于某个特定组的用户。  显示数据：  |栏目|说明| |--------|------------| |*用户名*|登录 Zabbix 的用户名。点击用户名打开用户[配置表单](/manual/config/users_and_usergroups/user)。| |*名*|用户的名字。| |*姓*|用户姓。| |*用户角色*|显示[用户角色](/manual/web_interface/frontend_sections/administration/user_roles)。| |*用户组*|列出了用户所属的组。单击用户组名称会打开用户组配置表单。禁用的组以红色显示。| |*在线吗？*|显示用户的在线状态 - *是* 或 *否*。最后用户活动的时间显示在括号中。| |*登录*|显示用户的登录状态 - *正常* 或 *锁定*。如果超过 *[Administration→General](/manual/web_interface/frontend_sections/administration/general#other_parameters)* 部分中设置的不成功登录尝试次数（默认为 5 次），用户可能会被暂时阻止。通过点击 *锁定* 您可以解除对用户的阻止。| |*前端访问*|显示前端访问级别 - *系统默认*、*内部*或*禁用*，取决于为整个用户组设置的一个。| |*API 访问*|显示 API 访问状态 - *启用* 或 *停用*，取决于用户角色的设置。| |*调试模式*|显示调试模式状态 - *启用* 或 *停用*，取决于为整个用户组设置的一组。| |*状态*|显示用户状态 - *启用* 或 *停用*，取决于为整个用户组设置的一组。|  要配置新用户，请单击右上角的 *创建用户* 按钮。

en-us	#### Users of Zabbix  Many organizations of different size around the world rely on Zabbix as a primary monitoring platform.
zh-cn	#### Zabbix 用户  世界各地许多不同规模的组织都依赖 Zabbix 作为主要监控平台。

en-us	### Users  The users object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**userid**<br>(required)|string|ID of user to send the report to.| |access\_userid|string|ID of user on whose behalf the report will be generated.<br><br>0 - *(default)* Generate report by recipient.| |exclude|integer|Whether to exclude the user from mailing list.<br><br>Possible values:<br>0 - *(default)* Include;<br>1 - Exclude.|
zh-cn	### 用户  用户对象包含下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**userid**<br>(必要)|字符串|需要发送报告的对象用户ID。| |access\_userid|字符串|将为其生成报告的用户ID。<br><br>0 - *(缺省值)* 按收件人生成报告。| |exclude|整数|从发送的用户名单中删除目标用户。<br><br>Possible values:<br>0 - *(缺省值)* 包含；<br>1 - 删除。|

en-us	### Users  The users object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**userid**<br>(required)|string|ID of user to send the report to.| |access\_userid|string|ID of user on whose behalf the report will be generated.<br><br>0 - *(default)* Generate report by recipient.| |exclude|integer|Whether to exclude the user from mailing list.<br><br>Possible values:<br>0 - *(default)* Include;<br>1 - Exclude.|
zh-cn	### 用户  用户对象包含下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**userid**<br>(必要)|字符串|需要发送报告的对象用户ID。| |access\_userid|字符串|将为其生成报告的用户ID。<br><br>0 - *(缺省值)* 按收件人生成报告。| |exclude|整数|从发送的用户名单中删除目标用户。<br><br>Possible values:<br>0 - *(缺省值)* 包含；<br>1 - 删除。|

en-us	# User  This class is designed to work with users.  Object references:\  -   [User](/manual/api/reference/user/object#user)  Available methods:\  -   [user.checkauthentication](/manual/api/reference/user/checkauthentication) -     checking and prolonging user sessions -   [user.create](/manual/api/reference/user/create) - creating new     users -   [user.delete](/manual/api/reference/user/delete) - deleting users -   [user.get](/manual/api/reference/user/get) - retrieving users -   [user.login](/manual/api/reference/user/login) - logging in to the     API -   [user.logout](/manual/api/reference/user/logout) - logging out of     the API -   [user.unblock](/manual/api/reference/user/unblock) - unblocking     users -   [user.update](/manual/api/reference/user/update) - updating users
zh-cn	# 用户  这个类用于操作用户.  对象属性:\  -   [用户](/manual/api/reference/user/object#user)  可用方法:\  -   [user.checkauthentication](/manual/api/reference/user/checkauthentication) - 检查并延长用户会话 -   [user.create](/manual/api/reference/user/create) - 创建用户 -   [user.delete](/manual/api/reference/user/delete) - 删除用户 -   [user.get](/manual/api/reference/user/get) - 查询用户 -   [user.login](/manual/api/reference/user/login) - 登录用户 -   [user.logout](/manual/api/reference/user/logout) - 注销用户 -   [user.unblock](/manual/api/reference/user/unblock) - 解锁用户 -   [user.update](/manual/api/reference/user/update) - 更新用户

en-us	# user.unblock
zh-cn	# 解锁用户

en-us	# user.update
zh-cn	# 更新用户

en-us	#### Using a custom expression filter  Create a correlation that will use a custom filter condition. The formula IDs "A" or "B" have been chosen arbitrarily. Condition type will be "Host group" with operator "<>".  Request:  ```json {     "jsonrpc": "2.0",     "method": "correlation.create",     "params": {         "name": "new host group correlation",         "description": "a custom description",         "status": 0,         "filter": {             "evaltype": 3,             "formula": "A or B",             "conditions": [                 {                     "type": 2,                     "operator": 1,                     "formulaid": "A"                 },                 {                     "type": 2,                     "operator": 1,                     "formulaid": "B"                 }             ]         },         "operations": [             {                 "type": 1             }         ]     },     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "correlationids": [             "2"         ]     },     "id": 1 } ```
zh-cn	 #### 使用一个自定义表达式过滤  使用自定义过滤条件创建一个`关联`。公式ID  A 或 B 是任意选择的。条件类型为“主机组”，操作符为 “<>”。  请求:  ```json {     "jsonrpc": "2.0",     "method": "correlation.create",     "params": {         "name": "new host group correlation",         "description": "a custom description",         "status": 0,         "filter": {             "evaltype": 3,             "formula": "A or B",             "conditions": [                 {                     "type": 2,                     "operator": 1,                     "formulaid": "A"                 },                 {                     "type": 2,                     "operator": 1,                     "formulaid": "B"                 }             ]         },         "operations": [             {                 "type": 1             }         ]     },     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "correlationids": [             "2"         ]     },     "id": 1 } ```

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