en-us	#### Configuration  To configure, select *Data overview* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/data_overview.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Host groups*|Select host groups. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove the selected.| |*Hosts*|Select hosts. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove the selected.| |*Tags*|Specify tags to limit the number of item data 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| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hosts location*|Select host location - left or top.|
zh-cn	#### 配置  选择*数据概览*为类型来配置：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/data_overview.png)  除了所有组件的[通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 参数外，您也可以设置以下选项：  |   |   | |---|---| |*主机群组*|选择主机群组。此字段是自动完成的，所以输入群组的名称后，会出现一个包含匹配群组的下拉菜单。向下滚动来选择。点击'x'来移除已选择的群组。| |*主机*|选择主机。此字段是自动完成的，所以输入主机的名称后，会出现一个包含匹配主机的下拉菜单。向下滚动来选择。点击'x'来移除已选择的主机。| |*标签*|指定标签来限制组件中显示的监控项数据量。可选择包含或不包含特定标签和标签值。可设置多个条件。标签名称匹配一直是大小写敏感的。<br>每种条件下有多种运算符：<br>**存在** - 包含特定标签名称<br>**等于** - 包含特定标签名称和值（大小写敏感）<br>**包含** - 特定标签名称的值包含输入的字符串（部分匹配，大小写敏感），<br>**不存在** - 不包含特定标签名称<br>**不等于** - 不包含特定标签名称和值（大小写敏感）<br>**不包含** - 特定标签名称的值不包含输入的字符串（部分匹配，大小写敏感）<br>这些条件有两种计算类型：<br>**与/或** - 必须满足所有条件，相同标签名称的条件将会按或条件进行分组<br>**或** - 只需满足一个条件| |*显示抑制的问题*|勾选多选框来显示因主机维护不显示的问题。| |*主机位置*|选择主机位置 - 左侧或顶部。|

en-us	#### Configuration  To configure, select *Graph* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_dataset.png){width="600"}  The **Data set** tab allows to add data sets and define their visual representation:  |   |   |   | |---|---|---| |*Data set*|<|Select hosts and items to display on the graph. 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.<br>Up to 50 items may be displayed in the graph.<br>Host pattern and item pattern fields are mandatory.<br>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).| | |*Base color*|Adjust base color, either from the color picker or manually. The base color is used to calculate different colors for each item of the data set. Base color input field is mandatory.| |^|*Draw*|Choose the draw type of the metric. Possible draw types are *Line* (set by default), *Points*, *Staircase* and *Bar*.<br>Note that if there's only one data point in the line/staircase graph it is drawn as a point regardless of the draw type. The point size is calculated from the line width, but it cannot be smaller than 3 pixels, even if the line width is less.| |^|*Width*|Set the line width. This option is available when *Line* or *Staircase* draw type is selected.| |^|*Point size*|Set the point size. This option is available when *Points* draw type is selected.| |^|*Transparency*|Set the transparency level.| |^|*Fill*|Set the fill level. This option is available when *Line* or *Staircase* draw type is selected.| |^|*Missing data*|Select the option for displaying missing data:<br>**None** - the gap is left empty<br>**Connected** - two border values are connected<br>**Treat as 0** - the missing data is displayed as 0 values<br>Not applicable for the *Points* and *Bar* draw type.| |^|*Y-axis*|Select the side of the graph where the Y-axis will be displayed.| |^|*Time shift*|Specify time shift if required. You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. Negative values are allowed.| |^|*Aggregation function*|Specify which aggregation function to use:<br>**min** - display the smallest value<br>**max** - display the largest value<br>**avg** - display the average value<br>**sum** - display the sum of values<br>**count** - display the count of values<br>**first** - display the first value<br>**last** - display the last value<br>**none** - display all values (no aggregation)<br>Aggregation allows to display an aggregated value for the chosen interval (5 minutes, an hour, a day), instead of all values. See also: [Aggregation in graphs](/manual/config/visualization/graphs/aggregate).<br>This option is supported since Zabbix 4.4.| |^|*Aggregation interval*|Specify the interval for aggregating values. You may use [time suffixes](/manual/appendix/suffixes#time_suffixes) in this field. A numeric value without a suffix will be regarded as seconds.<br>This option is supported since Zabbix 4.4.| |^|*Aggregate*|Specify whether to aggregate:<br>**Each item** - each item in the dataset will be aggregated and displayed separately.<br>**Data set** - all dataset items will be aggregated and displayed as one value.<br>This option is supported since Zabbix 4.4.|  Existing data sets are displayed in a list. You may:  -   ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_data_set.png) -     click on this button to add a new data set -   ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/color_icon.png) -     click on the color icon to expand/collapse data set details -   ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/move_icon.png) -     click on the move icon and drag a data set to a new place in the     list
zh-cn	＃＃＃＃ 配置  选择 *图表* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_dataset.png){width="600"}  通过*数据集*选项卡添加数据以及可视化效果：  | | | | |---|---|---| |*数据集*|<|选择要在图表显示的主机和监控项，你也可以用主机和项目标签，支持通配符（例如，*将返回匹配零个或更多字符的结果）。要使用通配只需要输入特定文本再按下回车。当你输入的时候，所有匹配的主机会在下拉框显示。<br>图表最多支持显示50个监控项。<br>主机参数和监控项参数必填。<br>通配符不可以被添加，因为它会被解析，因此如果有其他匹配项（例如 item2、item3）也会显示出来，无法单独添加名为“item\*”的项目。| | |*基色*|调整基色，可以通过颜色选择器或者手动输入。基色用于为监控项显示指定的颜色。基色参数必填。| |^|*绘制*|选择绘制的方式。可以选择*线*（默认设置）、*点*、*梯图*和*条状*。<br>请注意，如果线/梯图中只有一个数据点，那么不管绘制类型如何，它都会被绘制成一个点。点大小是根据线宽计算的，点大小不能小于 3 像素，即使线宽更小也是如此。| |^|*线宽*|设置线宽。这个选项在绘制*线*和*梯图*类型时可用。| |^|*点大小*|设置点的大小。这个选项在选择绘制*点*类型时可用。| |^|*透明度*|设置透明度。| |^|*填充率*|设置填充率。这个选项在选择绘制*线*或*梯图*类型时可用。| |^|*缺失数据*|选择显示缺失数据的方式：<br>**None** - 留空<br>**Connected** - 将缺失数据两侧连接<br>**Treat as 0** - 缺失数据按照数值0绘制图形<br>不适用于 *点* 和 *条状* 绘制类型。| |^|*Y 轴*|选择图表上Y轴显示内容。| |^|*间隔*|如果需要，可以设置时间间隔。支持输入[时间单位](/manual/appendix/suffixes#time_suffixes)。| |^|*聚合函数*|指定使用的聚合函数：<br>**min** - 显示最小值<br>**max** - 显示最大值<br>**avg** -显示平均值<br>**sum** - 显示值的总和<br>**count** -  显示数值的个数<br>**first** - 显示第一个值<br>** last** - 显示最后一个值<br>**none** - 显示所有值（无聚合）<br>聚合允许显示所选区间（5分钟、1小时、1天）的聚合值，而不是所有值。另请参阅：[聚合图形](/manual/config/visualization/graphs/aggregate)。<br>从Zabbix 4.4开始支持这个选项。| |^|*聚合间隔*|指定聚合的时间间隔。 您可以在此字段中使用[时间单位](/manual/appendix/suffixes#time_suffixes)。 输入纯数字视作秒。<br>从Zabbix 4.4开始支持这个选项。| |^|*聚合*|指定是否聚合：<br>**Each item** - 数据集中的每个监控项将被汇总并单独显示。<br>**Data set** - 所有的数据集监控项将被汇总并显示为一个值。<br>从Zabbix 4.4开始支持这个选项。  现有的数据集会显示在一个列表中。你可以：  - ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/add_data_set.png) -     点击这个按钮来添加一个新的数据集 - ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/color_icon.png) -     点击颜色图标，展开/折叠数据集细节设置 - ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/move_icon.png) -     点击移动图标，将数据集拖到列表中的新位置。

en-us	#### Configuration  To configure, select *Graph (classic)* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_classic.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Source*|Select graph type:<br>**Graph** - custom graph<br>**Simple graph** - simple graph| |*Graph*|Select the custom graph to display.<br>This option is available if 'Graph' is selected as *Source*.| |*Item*|Select the item to display in a simple graph.<br>This option is available if 'Simple graph' is selected as *Source*.| |*Show legend*|Unmark this checkbox to hide the legend on the graph (marked by default).| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set graph to display different data depending on the selected host.|  Information displayed by the classic graph widget can be downloaded as .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_download.png)  A screenshot of the widget will be saved to the Downloads folder.
zh-cn	#### 配置  选择*图表（经典）*作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_classic.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*来源*|选择图表类型：<br>**图表** - 自定义图表<br>**简单图表** - 简单图表| |*图表*|选择要显示的自定义图表。<br>如果选择“图表”作为*来源*，则此选项可用。| |*监控项*|选择要在简单图表中显示的项目。<br>如果选择“简单图表”作为*来源*，则此选项可用。| |*显示图例*|取消标记此复选框以隐藏图表上的图例（默认标记）。| |*[动态项目](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|设置图表以根据所选主机显示不同的数据。|  图表组件显示的信息可以通过[组件菜单](/manual/web_interface/frontend_sections/monitoring/dashboard#widget_menu)保存 .png 图片： ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/graph_download.png)  组件的截图将被保存到浏览器的“下载”文件夹。

en-us	#### Configuration  To configure, select *Graph prototype* as widget type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_prototype.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Source*|Select source: either a **Graph prototype** or a **Simple graph prototype**.| |*Graph prototype*|Select a graph prototype to display discovered graphs of the graph prototype.<br>This option is available if 'Graph prototype' is selected as Source.| |*Item prototype*|Select an item prototype to display simple graphs based on discovered items of an item prototype.<br>This option is available if 'Simple graph prototype' is selected as Source.| |*Show legend*|Mark this checkbox to show the legend on the graphs (marked by default).| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set graphs to display different data depending on the selected host.| |*Columns*|Enter the number of columns of graphs to display within a graph prototype widget.| |*Rows*|Enter the number of rows of graphs to display within a graph prototype widget.|  While the *Columns* and *Rows* settings allow fitting more than one graph in the widget, there still may be more discovered graphs than there are columns/rows in the widget. In this case paging becomes available in the widget and a slide-up header allows to switch between pages using the left and right arrows.  ![](../../../../../../../assets/en/manual/config/visualization/host_dashboards_discovered.png)
zh-cn	#### 配置  选择 *图形原型* 作为组件类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/graph_prototype.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*来源*|选择来源：**图形原型**或**简单图形原型**。| |*图形原型*|选择图形原型以显示图形原型的已发现图形。<br>如果选择“图形原型”作为源，则此选项可用。| |*监控项原型*|选择监控项原型以显示基于监控项原型的已发现监控项的简单图形。<br>如果选择“简单图形原型”作为源，则此选项可用。| |*显示图例*|选择复选框以在图表上显示图例（默认选中）。| |*[动态项目](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|根据选定的主机，设置图形显示不同的数据。| |*列*|输入要在图形原型组件中显示的图形的列数。| |*行*|输入要在图形原型组件中显示的图形行数。|  虽然通过*列*和*行*的设置允许在小部件中合并显示多个图表，但展示的图表可能比小部件中的列/行多。 在这种情况下，组件中可以使用分页，并且顶部标题允许使用左右箭头在页面之间切换。   ![](../../../../../../../assets/en/manual/config/visualization/host_dashboards_discovered.png)

en-us	 #### Configuration  To configure, select *Host availability* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/host_availability.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Host groups*|Select host group(s). This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove the selected.| |*Interface type*|Select which host interfaces you want to see availability data for.<br>Availability of all interfaces is displayed by default if nothing is selected.| |*Layout*|Select horizontal display (columns) or vertical display (lines).| |*Show hosts in maintenance*|Include hosts that are in maintenance in the statistics.|
zh-cn	  #### 配置  选择 *主机可用性* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/host_availability.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*主机组*|选择主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。点击'x'来移除已选择的主机组。| |*接口类型*|选择你需要查看的主机接口的可用性数据。<br>如果没有选择选项，默认状态下所有接口的可用性将显示出来。| |*布局*|选择水平显示（列）或垂直显示（行）。| |*显示维护中的主机*|统计数量时包含维护中的主机。|

en-us	#### Configuration  To configure, select *Item value* as the widget type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |_**Item**_ |Select the item. | |_**Show**_ |Mark the checkbox to display the respective element (description, value, time, change indicator). Unmark to hide.<br>At least one element must be selected. | |_**Advanced configuration**_ |Mark the checkbox to display [advanced configuration](#advanced-configuration) options. | |_**[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic-widgets)**_ |Mark the checkbox to display a different value depending on the selected host. |
zh-cn	＃＃＃＃ 配置  选择*项目值*作为组件类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |_**监控项**_ |选择监控项。 | |_**显示**_ |选中复选框以显示相应的元素（描述、值、时间、变化指示器）。取消标记来隐藏。<br>至少选择一个元素。 | |_**高级配置**_ |选中复选框以显示[高级配置](#advanced-configuration)选项。 | |_**[动态项目](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic-widgets)**_ |选中复选框，取决于主机的不同会显示不同的数据。 |

en-us	#### Configuration  To configure, select *Map* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/map.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Source type*|Select to display:<br>**Map** - network map<br>**Map navigation tree** - one of the maps in the selected map navigation tree| |*Map*|Select the map to display.<br>This option is available if 'Map' is selected as *Source type*.| |*Filter*|Select the map navigation tree to display the maps of.<br>This option is available if 'Map navigation tree' is selected as *Source type*.|  See also: [known issue with IE11](/manual/installation/known_issues#ie11_issue_with_map_resizing_in_dashboard_widgets)
zh-cn	#### 配置  选择 *拓扑图* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/map.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*来源类型*|选择显示的内容：<br>**拓扑图** - 网络拓扑图<br>**拓扑图导航树** - 选定的拓扑图导航树中的一个拓扑图| |*拓扑图*|选择要显示的拓扑图。<br>这个选项在"拓扑图"被选为源类型时可用。| |*筛选*|选择要显示的拓扑图导航树的拓扑图。<br>这个选项在 "拓扑图导航树"被选为源类型时可用。|  另请参阅：[IE11浏览器中的已知问题](/manual/installation/known_issues#ie11_issue_with_map_resizing_in_dashboard_widgets)

en-us	#### Configuration  To configure, select *Plain text* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/plain_text.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Items*|Select the items.| |*Items location*|Choose the location of selected items to be displayed in the widget.| |*Show lines*|Set how many latest data lines will be displayed in the widget.| |*Show text as HTML*|Set to display text as HTML.| |*[Dynamic item](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|Set to display different data depending on the selected host.|
zh-cn	#### 配置  选择 *纯文本* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/plain_text.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*监控项*|选择监控项。| |*监控项位置*|选择要在组件中显示的选定监控项的位置。| |*显示行数*|设置将在组件中显示多少最新的数据行。| |*显示文本为HTML*|设置以HTML方式显示文本。| |*[动态监控项](/manual/web_interface/frontend_sections/monitoring/dashboard#dynamic_widgets)*|设置根据选定的主机显示不同的数据。|

en-us	#### Configuration  To configure, select *Problem hosts* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problem_hosts.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |Parameter|Description| |---------|-----------| |*Host groups*|Enter host groups to display in the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host data from these host groups will be displayed in the widget. If no host groups are entered, all host groups will be displayed.| |*Exclude host groups*|Enter host groups to hide from the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Host data from these host groups will not be displayed in the widget. For example, hosts 001, 002, 003 may be in Group A and hosts 002, 003 in Group B as well. If we select to *show* Group A and *exclude* Group B at the same time, only data from host 001 will be displayed in the Dashboard.| |*Hosts*|Enter hosts to display in the widget. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts.<br>If no hosts are entered, all hosts will be displayed.| |*Problem*|You can limit the number of problem hosts displayed by the problem name. If you enter a string here, only those hosts with problems whose name contains the entered string will be displayed. Macros are not expanded.| |*Severity*|Mark the problem severities to be displayed in the widget.| |*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| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hide groups without problems*|Mark the *Hide groups without problems* option to hide data from host groups without problems in the widget.| |*Problem display*|Display problem count as:<br>**All** - full problem count will be displayed<br>**Separated** - unacknowledged problem count will be displayed separated as a number of the total problem count<br>**Unacknowledged only** - only the unacknowledged problem count will be displayed.|
zh-cn	#### 配置  选择 *问题主机* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problem_hosts.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  |参数|说明| |---------|------------| |*主机组*|输入要在组件中显示的主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。<br>指定一个父级主机组意味着同时选择所有嵌套的主机组。<br>来自这些主机组的主机数据将被显示在组件中。如果没有输入主机组，所有的主机组将被显示。| |*排除主机组*|输入要从组件中隐藏的主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。<br>指定一个父级主机组意味着同时选择所有嵌套的主机组。<br>来自这些主机组的主机数据将不会显示在组件中。例如主机001, 002, 003属于A组，主机002, 003也属于B组。如果我们选择同时显示A组和排除B组，只有主机001的数据将显示在仪表板中。| |*主机*|输入要在组件中显示的主机。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机名称。<br>如果未输入主机，将显示所有主机。| |*问题*|可以输入问题名称来控制显示的主机数量，仅显示问题名称包含输入的文本的主机。不支持通配。| |*严重性*|标记要在组件中显示的问题严重性。| |*标签*|可以通过包括以及排除特定的标签和标签值的方法，指定标签以限制组件中同时显示的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** - 满足任意条件即可| |*显示抑制的问题*|选中复选框以显示因主机维护而被抑制（不显示）的问题。| |*隐藏没有问题的组*|选中复选框以隐藏没有问题的主机组的数据。| |*问题显示*|按照以下方法计算问题数量：<br>**All** - 所有的问题都计入总数<br>**Separated** - 独立计算未确认问题和问题总数<br>**Unacknowledged only** - 仅计算未确认问题的数量。|

en-us	#### Configuration  To configure, select *Problems* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problems.png)  You can limit how many problems are displayed in the widget in various ways - by problem status, problem name, severity, host group, host, event tag, acknowledgment status, etc.  |Parameter|Description| |---------|-----------| |*Show*|Filter by problem status:<br>**Recent problems** - unresolved and recently resolved problems are displayed (default)<br>**Problems** - unresolved problems are displayed<br>**History** - history of all events is displayed| |*Host groups*|Enter host groups to display problems of in the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Problems from these host groups will be displayed in the widget. If no host groups are entered, problems from all host groups will be displayed.| |*Exclude host groups*|Enter host groups to hide problems of from the widget. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.<br>Specifying a parent host group implicitly selects all nested host groups.<br>Problems from these host groups will not be displayed in the widget. For example, hosts 001, 002, 003 may be in Group A and hosts 002, 003 in Group B as well. If we select to *show* Group A and *exclude* Group B at the same time, only problems from host 001 will be displayed in the widget.| |*Hosts*|Enter hosts to display problems of in the widget. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts.<br>If no hosts are entered, problems of all hosts will be displayed.| |*Problem*|You can limit the number of problems displayed by their name. If you enter a string here, only those problems whose name contains the entered string will be displayed. Macros are not expanded.| |*Severity*|Mark the problem severities to be displayed in the widget.| |*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<br>When filtered, the tags specified here will be displayed first with the problem, unless overridden by the *Tag display priority* (see below) list.| |*Show tags*|Select the number of displayed tags:<br>**None** - no *Tags* column in *Monitoring → Problems*<br>**1** - *Tags* column contains one tag<br>**2** - *Tags* column contains two tags<br>**3** - *Tags* column contains three tags<br>To see all tags for the problem roll your mouse over the three dots icon.| |*Tag name*|Select tag name display mode:<br>**Full** - tag names and values are displayed in full<br>**Shortened** - tag names are shortened to 3 symbols; tag values are displayed in full<br>**None** - only tag values are displayed; no names| |*Tag display priority*|Enter tag display priority for a problem, as a comma-separated list of tags (for example: `Services,Applications,Application`). Tag names only should be used, no values. The tags of this list will always be displayed first, overriding the natural ordering by alphabet.| |*Show operational data*|Select the mode for displaying [operational data](/manual/web_interface/frontend_sections/monitoring/problems#operational_data_of_problems):<br>**None** - no operational data is displayed<br>**Separately** - operational data is displayed in a separate column<br>**With problem name** - append operational data to the problem name, using parentheses for the operational data| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Show unacknowledged only*|Mark the checkbox to display unacknowledged problems only.| |*Sort entries by*|Sort entries by:<br>**Time** (descending or ascending)<br>**Severity** (descending or ascending)<br>**Problem name** (descending or ascending)<br>**Host** (descending or ascending).| |*Show timeline*|Mark the checkbox to display a visual timeline.| |*Show lines*|Specify the number of problem lines to display.|
zh-cn	#### 配置  选择 *问题* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/problems.png)  您可以通过各种方式限制组件中显示的问题数量--按问题状态、问题名称、严重程度、主机组、主机、事件标签、确认状态等。  |参数|说明| |---------|------------| |*显示*|按问题状态过滤：<br>**最近的问题** - 显示未解决和最近解决的问题（默认）<br>**问题** - 显示未解决的问题<br>**历史记录** - 显示所有事件的历史| |*主机组*|输入要在组件中显示的主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。<br>指定一个父级主机组意味着同时选择所有嵌套的主机组。<br>来自这些主机组的主机数据将被显示在组件中。如果没有输入主机组，所有的主机组将被显示。| |*排除主机组*|输入要从组件中隐藏的主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。<br>指定一个父级主机组意味着同时选择所有嵌套的主机组。<br>来自这些主机组的主机数据将不会显示在组件中。例如主机001, 002, 003属于A组，主机002, 003也属于B组。如果我们选择同时显示A组和排除B组，只有主机001的数据将显示在仪表板中。| |*主机*|输入要在组件中显示的主机。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机名称。<br>如果未输入主机，将显示所有主机。| |*问题*|可以输入问题名称来控制显示的主机数量，仅显示问题名称包含输入的文本的主机。不支持通配。| |*严重性*|标记要在组件中显示的问题严重性。| |*标签*|可以通过包括以及排除特定的标签和标签值的方法，指定标签以限制组件中同时显示的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** - 满足任意条件即可<br>过滤模式限定的标签会被优先显示，可以被*标签显示优先级*覆盖，见下文。| |*显示标签*|选择显示标签的数量：<br>**None** - *监测→ 问题* 中没有*标签* 列<br>**1** - *标签* 列包含一个标签< br>**2** - *标签* 列包含两个标签<br>**3** - *标签* 列包含三个标签<br>要查看该问题的所有标签，请将鼠标移到三个点的图标上。| |*标签名称*|选择标签名称显示模式：<br>**Full** - 标记的名称和值被完整地显示出来<br>**Shortened** - 标签名称被缩短为3个符号；标签值被完整显示<br>**无** - 只显示标签值，不显示名称。| |*标签显示优先级*| 输入问题的标签显示优先级，以逗号分隔的标签列表（例如：服务、应用程序、应用）。优先级仅匹配标签名称不匹配具体数据。此列表中的标签将始终被优先显示，而不是按字母顺序自然排序。| |*显示操作数据*|选择显示[操作数据](/manual/web_interface/frontend_sections/monitoring/problems#operational_data_of_problems)的模式:<br>**None ** - 不显示操作数据<br>**Separately ** - 操作数据显示在单独的列中<br>**With problem name ** - 将操作数据附加到问题名称，使用括号表示操作数据| |*显示抑制的问题*|选中复选框以显示因主机维护而被抑制（不显示）的问题。| |*仅显示未确认的问题*|选中复选框只显示未确认的问题。| |排序依据|按以下顺序排序条目：<br>**Time**（降序或升序）<br>**Severity **（降序或升序）<br>**Problem name**（降序或升序） )<br>**Host**（降序或升序）| |*显示时间线*|选中复选框显示时间轴| |*显示行*|选中显示的问题最大行数。|

en-us	#### Configuration  To configure, select *SLA report* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/sla_report.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*SLA*|Select the SLA for the report.| |*Service*|Select the service for the report.| |*Show periods*|Set how many periods will be displayed in the widget (20 by default, 100 maximum).| |*From*|Select the beginning date for the report.<br>Relative dates are supported: `now`, `now/d`, `now/w-1w` etc; supported date modifiers: d, w, M, y.| |*To*|Select the end date for the report.<br>Relative dates are supported: `now`, `now/d`, `now/w-1w` etc; supported date modifiers: d, w, M, y.|
zh-cn	#### 配置  点击配置，类型选择*SLA报表*：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/sla_report.png)  除了所有小部件 [通用参数](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#通用参数 ) 外，您还可以设置以下特定选项：  |   |   | |---|---| |*SLA*|选择SLA报表。| |*Service*|选择服务报表。| |*Show periods*|设置小部件中显示的时间段（默认为20，最大为100）。| |*From*|选择报告的开始日期<br>支持相对日期：`now`、`now/d`、`now/w-1w`等；支持的日期修饰符：d、w、M、y。| |*To*|选择报告的结束日期<br>支持相对日期：`now`、`now/d`、`now/w-1w`等；支持的日期修饰符：d、w、M、y。|

en-us	#### Configuration  To configure, select *System information* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/system_information.png)  All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets.
zh-cn	#### 配置  选择 *System information* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/system_information.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的。

en-us	#### Configuration  To configure, select *Top hosts* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.1.png){width="600"}
zh-cn	#### 配置  点击配置，选择类型为*Top hosts*：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.1.png){width="600"}

en-us	#### Configuration  To configure, select *Trigger overview* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/trigger_overview.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |--|--------| |*Show*|Filter by problem status:<br>**Recent problems** - unresolved and recently resolved problems are displayed (default)<br>**Problems** - unresolved problems are displayed<br>**Any** - history of all events is displayed| |*Host groups*|Select the host group(s). This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups.| |*Hosts*|Select hosts. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove the selected.| |*Tags*|Specify tags to limit the number of item and trigger data 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| |*Show suppressed problems*|Mark the checkbox to display problems that would otherwise be suppressed (not shown) because of host maintenance.| |*Hosts location*|Select host location - left or top.|
zh-cn	#### 配置  选择*触发器概览*作为配置类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/trigger_overview.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*显示*|按问题状态过滤：<br>**最近的问题** - 显示未解决和最近解决的问题（默认）<br>**问题** - 显示未解决的问题<br>**任何** - 显示所有事件的历史| |*主机组*|选择主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。| |*主机*|选择主机。这个字段支持自动补全，输入一个主机的名称在下拉框选择你需要的主机名称。单击“x”删除对应主机。| |*标签*|指定标签以限制小部件中显示的监控项和触发器数据的数量。 可以包括也可以排除特定的标签和标签值。 可以设置多个条件，标签名称匹配始终区分大小写。<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	#### Configuration  To configure services, go to: *Monitoring → [Services](/manual/web_interface/frontend_sections/monitoring/it_services)*.  In this section you can build a hierarchy of your monitored infrastructure by adding parent services and child services to the parent services.  
zh-cn	#### 概述  #### Overview  服务(Serivce)监控功能是为帮助那些想要在IT基础设施监控之上获得更高层面（业务）监控需求的人设计。在许多情况下，我们不关心底层设施监控细节，比如磁盘空间不足，CPU高负载等等。我们关心的是IT部门提供的服务（业务）整体的可用性。我们还关心在 整体IT基础设施中最薄弱的环节，以及各种IT服务的SLA指标（SLA服务等级协议），更关心识别现有IT基础设施架构薄弱环节，以及更高层面（业务）的监控信息。  Service monitoring functionality is intended for those who want to get a high-level (business) view of monitored infrastructure. In many cases, we are not interested in low-level details, like the lack of disk space, high processor load, etc. What we are interested in is the availability of service provided by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information of a higher level.  Zabbix 服务监控（service）就是针对上述问题提出的解决方案。  Zabbix service monitoring provides answers to all mentioned questions.  服务监控（service）是分层表现监控数据的。  Services is a hierarchy representation of monitored data.  下面我们来看一个非常简单的服务监控（service）例子：  A very simple service structure may look like:      Service     |     |-Workstations     | |     | |-Workstation1     | |     | |-Workstation2     |     |-Servers  在结构上每个节点都具有监控属性状态。这个状态根据所选算法计算状态关联上层状态，服务监控（service）功能最底层是关联的触发器（triggers）。每个节点状态都是受其触发器（triggers）状态影响。  Each node of the structure has attribute status. The status is calculated and propagated to upper levels according to the selected algorithm. At the lowest level of services are triggers. The status of individual nodes is affected by the status of their triggers.  ::: noteclassic 提示：触发器（triggers）的严重等级 如：*不分类（Not classified）* 或*信息（Information）*是不影响SLA指标（SLA服务等级协议）计算的。 :::  ::: noteclassic Note that triggers with a *Not classified* or *Information* severity do not impact SLA calculation. :::  #### 配置  #### Configuration  配置服务监控（service），请访问：*配置（Configuration） → 服务监控（Services）*. To configure services, go to: *Configuration → Services*.  在该界面，您可以创建一个分层监控结构。 最高的父节点服务是'root'。您可以向下创建更低层服务监控（service）子节点，实现相互层级结构。  On this screen you can build a hierarchy of your monitored infrastructure. The highest-level parent service is 'root'. You can build your hierarchy downward by adding lower-level parent services and then individual nodes to them.  在这个屏幕上，您可以构建被监视的基础结构的层次结构。最高级的父服务是“root”。您可以向下构建层次结构，方法是添加低级的父服务，然后向它们添加单个节点。  ![](../../assets/en/manual/config/itservice_add.png)  点击 *添加子节点（Add child）* 增加服务监控（service）。 点击名称可编辑已该服务监控（service），您可以通过弹出的界面编辑该服务监控（service）属性。  Click on *Add child* to add services. To edit an existing service, click on its name. A form is displayed where you can edit the service attributes.  ##### 配置一个服务监控（service）  ##### Configuring a service  **服务监控（service)** 选项包含通用的服务监控（service）属性  The **Service** tab contains general service attributes:  ![](../../assets/en/manual/config/itservice.png)  所有必填字段都标有\*红色星号。  All mandatory input fields are marked with a red asterisk.  |参数                                             说|<|<| |------------------------------------------------------|-|-| |*名称（Name）*                                   服务监|名称.|<| |*上层服务（Parent service）*                     服务监控（|ervice） 从属的上层父节点|<| |*状态计算算法（Status calculation algorithm）*   服务监控（se|vice)状态计算方法:\                                                                                              服务状态的计算方法:\\ \\ \***不要计算(Do not calculate)** - 不计算节点状态。<br>**问题, 如果至少一个下层有一个问题（Problem, if at least one child has a problem）** -只要一个子节点有异常，该节点就异常。<br>**问题, 如果所有的下层都有问题（Problem, if all children have problems）** - 当所有节点都异常时，该节点才异常。|\*不计算\* \*,不计算服务状态\\ \\ \* \*问题,如果至少有一个子节点服务有问题\* \*——问题状态,如果至少一个子节点服务有问题\\ \\ \* \*问题,如果所有的孩子都有问题\* \*——问题状态,如果所有的子服务有问题| |*计算SLA（Calculate SLA）*                       勾选✔|是否计算SLA指标。|<| |*可接受的SAL(%)（Acceptable SLA (in %)）*        此服务监控|service)节点，可接受的SLA百分比，用于报告。|<| |*触发器（Trigger）*                              选择关联|触发器（Trigger）:<br>**None** - 没有关联的触发器（Trigger）<br>**触发器名称（trigger name）** - 选择绑定触发器（Trigger），因此节点状态依赖触发器（Trigger）状态<br>. 最底层服务计算必须依赖触发器状态(否则，它们的状态将无法得到准确的计算)<br>当触发器被关联后，其触发器以前的状态告警是不计算的。|<| |*排序（Sort order）*                             显示排|的顺序，数字小的优先|<|  |Parameter|Description| |---------|-----------| |*Name*|Service name.| |*Parent service*|Parent service the service belongs to.| |*Status calculation algorithm*|Method of calculating service status:<br>**Do not calculate** - do not calculate service status<br>**Problem, if at least one child has a problem** - problem status, if at least one child service has a problem<br>**Problem, if all children have problems** - problem status, if all child services are having problems| |*Calculate SLA*|Enable SLA calculation and display.| |*Acceptable SLA (in %)*|SLA percentage that is acceptable for this service. Used for reporting.| |*Trigger*|Linkage to trigger:<br>**None** - no linkage<br>**trigger name** - linked to the trigger, thus depends on the trigger status<br>Services of the lowest level must be linked to triggers. (Otherwise their state will not be represented accurately.)<br>When triggers are linked, their state prior to linking is not counted.| |*Sort order*|Sort order for display, lowest comes first.|  **依赖关系（Dependencies）** 选项卡可以看到该服务监控（service)所有子节点。单击 *Add* 增加一个之前配置过的 服务监控（service)节点。  The **Dependencies** tab contains services the service depends on. Click on *Add* to add a service from those that are configured.  ![](../../assets/en/manual/config/itservice_b.png)  **硬依赖和软依赖（Hard and soft dependency）** **Hard and soft dependency**  服务的可用性指标，可能取决于其他多个服务，而不仅仅是一个。 界面第一个选项服务监控（service)是直接增加子节点。  Availability of a service may depend on several other services, not just one. The first option is to add all those directly as child services.  而然，如果服务（service)在其他节点已增加过，则不能简单的将它移动到该子节点。那该如何创建服务（service)节点依赖？这个问题答案是"软链接"。增加一个服务（service) 依赖是，勾选√*软连接(soft)*选项。通过这种方式，服务（service)可以保留节点之前原始位置，有可以绑定依赖到其他服务（service)上。这种“软连接”的服务（service)节点在服务树上显示是灰色的。另外，如果一个服务只有一个“软连接”节点，就可以删除此服务，而不用删除软连接的子节点。  However, if some service is already added somewhere else in the services tree, it cannot be simply moved out of there to a child service here. How to create a dependency on it? The answer is "soft" linking. Add the service and mark the *Soft* check box. That way the service can remain in its original location in the tree, yet be depended upon from several other services. Services that are "soft-linked" are displayed in grey in the tree. Additionally, if a service has only "soft" dependencies, it can be deleted directly, without deleting child services first.  **时间（Time）** 选型，用于设置服务（service)的工作时间。 The **Time** tab contains the service time specification.  ![](../../assets/en/manual/config/itservice_c.png)  |参数                                 说|<| |------------------------------------------|-| |*服务时间（Service times）*          默认，所有|务（Service）都是预设 24x7x365 统计时间，如有特殊需要，请增加 新的服务时间（New service time）。| |*新的服务时间（New service time）*   服务时间（Se|vice times）:<br>**在线时间（Uptime）** - 服务正常运行时间<br>**故障停机时间（Downtime）** - 故障停机时间周期内不会纳入SLA服务时间统计.<br>**单次停机（One-time downtime）** - 单次停机时间，在该时间阶段内不会纳入SLA服务时间统计a single downtime. Service state within this period does not affect SLA.<br>增加相应的时间段。<br>*Note*: 服务时间仅影响其配置的服务（Service）。因此，父节点服务（Service）不会考虑子节点（Service）上配置的服务时间（Service times）（除非您在父节点也配置相应的服务时间）。\\\\在前端页面计算服务（Service）状态和SLA时，会考虑这个服务时间（Service times）。然而需要您知道是，不管服务时间如何配置计算，关于服务（Service）原始可用性信息仍会连续不断写入到数据库中。|  |Parameter|Description| |---------|-----------| |*Service times*|By default, all services are expected to operate 24x7x365. If exceptions needed, add new service times.| |*New service time*|Service times:<br>**Uptime** - service uptime<br>**Downtime** - service state within this period does not affect SLA.<br>**One-time downtime** - a single downtime. Service state within this period does not affect SLA.<br>Add the respective hours.<br>*Note*: Service times affect only the service they are configured for. Thus, a parent service will not take into account the service time configured on a child service (unless a corresponding service time is configured on the parent service as well).<br>Service times are taken into account when calculating service status and SLA by the frontend. However, information on service availability is being inserted into database continuously, regardless of service times.|  #### 前端显示  #### Display  服务（Service），去 监控中（Monitoring）-→ 服务（Service）  To monitor services, go to *[Monitoring → Services](/manual/web_interface/frontend_sections/monitoring/it_services)*.  

en-us	#### Configuration  To configure services, go to the [Services](/manual/web_interface/frontend_sections/services) menu.  The services menu consists of these sections:  - [Services](/manual/web_interface/frontend_sections/services/service)  In this section you can build a hierarchy of your monitored infrastructure by adding parent services, and then - child  services to the parent services.  - [Service actions](/manual/web_interface/frontend_sections/services/service_actions)  In this section you can configure service actions.  - [SLA](/manual/web_interface/frontend_sections/services/sla)  In this section you can view the SLA of services.  - [SLA report](/manual/web_interface/frontend_sections/services/sla_report)  In this section you can view SLA reports.
zh-cn	#### 配置  要配置服务，请转到 [Services（服务）](/manual/web_interface/frontend_sections/services) 菜单。  服务菜单由以下部分组成：  - [Services（服务）](/manual/web_interface/frontend_sections/services/service)  在本节中，您可以通过添加父服务来构建受监控基础架构的层次结构，然后将子服务添加到父服务的下级。  - [Service actions（服务行动）](/manual/web_interface/frontend_sections/services/service_actions)  在本节中，可以配置服务操作。  - [SLA](/manual/web_interface/frontend_sections/services/sla)  在本节中，可以查看服务的 SLA。  - [SLA report](/manual/web_interface/frontend_sections/services/sla_report)  在本节中，可以查看 SLA 报告。

en-us	#### Configuration  To configure SMS as the media type:  -   Go to *Administration → Media types* -   Click on *Create media type* (or click on *SMS* in the list of     pre-defined media types).  The following parameters are specific for the SMS media type:  |Parameter|Description| |--|--------| |*GSM modem*|Set the serial device name of the GSM modem.|  See [common media type parameters](/manual/config/notifications/media#common_parameters) for details on how to configure default messages and alert processing options. Note that parallel processing of sending SMS notifications is not possible.
zh-cn	#### 配置  将 SMS 配置为媒介类型：  -   进入 *管理 → 媒介类型* -   点击 *创建媒介类型* (或者点击预定义的媒介类型列表中的 SMS)。  如下参数仅适用于SMS媒介类型：  |参数|说明| |---------|-----------| |*GSM modem*|设置GSM调制解调器的串行设备名称。|  有关如何配置默认消息和告警处理的详细内容，请参见[通用媒介类型参数](/manual/config/notifications/media#common_parameters) 。请注意，SMS 通知无法并行发送。

en-us	#### Configuration  To configure the navigation tree widget, select *Map navigation tree* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/map_tree.png)  In addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Show unavailable maps*|Mark this checkbox to display maps that the user does not have read permission to.<br>Unavailable maps in the navigation tree will be displayed with a grayed-out icon.<br>Note that if this checkbox is marked, available sub-maps are displayed even if the parent level map is unavailable. If unmarked, available sub-maps to an unavailable parent map will not be displayed at all.<br>Problem count is calculated based on available maps and available map elements.|
zh-cn	####  配置  选择 *拓扑图导航树* 作为类型：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/map_tree.png)  [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*显示不可用的拓扑图*|选中复选框以显示用户没有访问权限的拓扑图。<br>导航树中不可用的拓扑图会以灰色的图标显示。<br>注意，如果该复选框被选中，即使父级拓扑图不可用，也会显示可用的子拓扑图。如果没有选中，父拓扑图不可用时，即使有权限的子拓扑图也无法显示。<br>问题计数是根据可用拓扑图和可用拓扑图元素计算的。|

en-us	#### Configuration  To create an ad-hoc graph, do the following:  -   Go to *Monitoring* → *Latest data* -   Use filter to display items that you want -   Mark checkboxes of the items you want to graph -   Click on *Display stacked graph* or *Display graph* buttons  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graphs.png){width="600"}  Your graph is created instantly:  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graph.png){width="600"}  Note that to avoid displaying too many lines in the graph, only the average value for each item is displayed (min/max value lines are not displayed). Triggers and trigger information is not displayed in the graph.  In the created graph window you have the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) available and the possibility to switch from the "normal" line graph to a stacked one (and back).  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_stacked.png){width="600"}
zh-cn	####  配置  要创建Ad-hoc图表，请执行以下操作：  - 转到*监控* → *最新数据* - 使用过滤器显示您想要的监控项 - 标记要绘制的监控项的复选框 - 点击*显示堆叠数据图*或*显示数据图*按钮  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graphs.png){width="600"}  您的图表会立即创建：  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graph.png){width="600"}  请注意，为避免在图表中显示过多的线，只会显示每个监控项的平均值（不显示最小值/最大值行显示）。触发器和触发器信息不显示在图形。  在创建的图形窗口中，您可以使用[时间段选择器](/manual/config/visualization/graphs/simple#time_period_selector)，也可以从“正常”折线图切换到堆叠图（可来回切换）。  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_stacked.png){width="600"}

en-us	### Configuration  To create a new service action, go to the *Service actions* subsection of the *Services* menu, then click on *Create action* in the upper right corner.  Service actions are configured in the same way as other types of actions in Zabbix. For more details, see configuring [actions](/manual/config/notifications/action#configuring-an-action).   The key differences are:     - User access to service actions depends on access rights to services granted by user's [role](/manual/web_interface/frontend_sections/administration/user_roles).    - Service actions support different set of [conditions](#conditions).
zh-cn	### 配置  要创建新的服务动作，请转到 *Services* 菜单的 *Service actions* 子部分，然后单击右上角的 *Create action*。  服务动作的配置方式与 Zabbix 中其他类型的动作相同。有关更多详细信息，请参阅配置 [动作](/manual/config/notifications/action#配置动作)。  主要区别在于：    - 用户对服务动作的访问取决于用户 [角色](/manual/web_interface/frontend_sections/administration/user_roles) 授予的对服务的访问权限。   - 服务动作支持不同的 [条件](#conditions) 集。

en-us	### Configuration  To create a new SLA, click on the *Create SLA* button.  The **SLA** tab allows to specify general  SLA parameters.  ![](../../../assets/en/manual/web_interface/sla.png){width=600}  |Parameter|Description| |---------|-----------| |*Name*|Enter the SLA name. | |*SLO*|Enter the service level objective (SLO) as percentage. | |*Reporting period*|Selecting the period will affect what periods are used in the [SLA report](/manual/web_interface/frontend_sections/services/sla_report) - *daily*, *weekly*, *monthly*, *quarterly*, or *annually*. | |*Time zone*|Select the SLA time zone. | |*Schedule*|Select the SLA schedule - 24x7 or custom. | |*Effective date*|Select the date of starting SLA calculation. | |*Service tags*|Add service tags to identify the services towards which this SLA should be applied. <br> **Name** - service tag name, must be exact match, case-sensitive. <br> **Operation** - select *Equals* if the tag value must match exactly (case-sensitive) or *Contains* if part of the tag value must match (case-insensitive). <br> **Value** - service tag value to search for according to selected operation.<br> The SLA is applied to a service, if at least one service tag matches.  | |*Description*|Add a description for the SLA. | |*Enabled*|Mark the checkbox to enable the SLA calculation. |  The **Excluded downtimes** tab allows to specify downtimes  that are excluded from the SLA calculation.  ![](../../../assets/en/manual/web_interface/sla_b.png){width=600}  Click on *Add* to configure excluded downtimes, then enter the period name, start date and duration. 
zh-cn	### 配置  点击 *创建 SLA* 按钮新建一个SLA。  **SLA** 面板可以指定通用的SLA参数。  ![](../../../assets/en/manual/web_interface/sla.png){width=600}  |参数|描述| |---------|-----------| |*名称*|输入SLA名称。 | |*SLO*|输入服务级别目标(SLO)，格式为百分比。| |*报告周期*|[SLA 报告](/manual/web_interface/frontend_sections/services/sla_report)中使用的时间周期 - *每天*, *每周*, *每月*, *每季度*, 或 *每年*。 | |*时区*|SLA的时区。| |*时间表*|SLA运行的时间表 - 24x7或自定义。| |*生效日期*|开始SLA计算的日期。| |*服务标签*|添加服务标签，用于识别SLA对应的服务。<br> **名称** - 服务标签名称，必须严格匹配，大小写敏感。<br> **操作** - 如果标签值必须严格匹配(大小写敏感)，就选择 *等于*。如果部分标签值匹配(大小写不敏感)，则选择 *包含*。<br> **值** - 需要进行搜索的服务标签值。<br> 如果至少匹配了一个服务标签，则SLA应用于该服务。| |*描述*|为SLA添加描述。| |*启用*|勾选检查框来启用SLA。|  **例外停机时间** 面板可以指定停机时间，SLA不会将其计算在内。  ![](../../../assets/en/manual/web_interface/sla_b.png){width=600}  点击 *添加* 来配置例外停机时间，输入时间周期名称，开始日期和持续时长。

en-us	#### Configuration  To define user macros, go to the corresponding location in the frontend:  -   for global macros, visit *Administration → General → Macros* -   for host and template level macros, open host or template properties     and look for the *Macros* tab  ::: notetip If a user macro is used in items or triggers in a template, it is suggested to add that macro to the template even if it is defined on a global level. That way, if the macro type is *text* exporting the template to XML and importing it in another system will still allow it to work as expected. Values of secret macros are not [exported](/manual/xml_export_import).  :::  A user macro has the following attributes:  ![](../../../../assets/en/manual/config/macros/user_macros.png){width="600"}  |Parameter|Description| |--|--------| |*Macro*|Macro name. The name must be wrapped in curly brackets and start with a dollar sign.<br>Example: {$FRONTEND\_URL}. The following characters are allowed in the macro names: **A-Z** (uppercase only) , **0-9** , **\_** , **.**| |*Value*|Macro value. Three value types are supported:<br>**Text** (default) - plain-text value<br>**Secret text** - the value is masked with asterisks, which could be useful to protect sensitive information such as passwords or shared keys.<br>**Vault secret** - the value contains a reference path (as 'path:key', for example “secret/zabbix:password”) to a [Vault secret](/manual/config/secrets)<br><br>*Note* that while the value of a secret macro is hidden from sight, the value can be revealed through the use in items. For example, in an external script an 'echo' statement referencing a secret macro may be used to reveal the macro value to the frontend because Zabbix server has access to the real macro value.<br><br>To select the value type click on the button at the end of the value input field:<br>![](../../../../assets/en/manual/config/macros/macro_type_text.png) icon indicates a text macro;<br>![](../../../../assets/en/manual/config/macros/macro_type_secret.png) icon indicates a secret text macro. Upon hovering, the value field transforms into a ![](../../../../assets/en/manual/config/macros/macro_type_secret2.png) button, which allows to enter a new value of the macro (to exit without saving a new value, click the backwards arrow (![](../../../../assets/en/manual/config/macros/macro_type_secret3.png)).<br>![](../../../../assets/en/manual/config/macros/macro_type_vault.png) icon indicates a secret Vault macro.<br><br>Maximum length of a user macro value is 2048 characters (255 characters in versions before 5.2.0).| |*Description*|Text field used to provide more information about this macro.|  ::: noteclassic  URLs that contain a secret macro will not work as the macro in them will be resolved as "\*\*\*\*\*\*".  :::  ::: noteimportant In trigger expressions user macros will resolve if referencing a parameter or constant. They will NOT resolve if referencing a host, item key, function, operator or another trigger expression. Secret macros cannot be used in trigger expressions. :::
zh-cn	#### 配置  要定义用户宏，请转到前端中的相应位置：  - 有关全局宏，请访问*管理→ 一般→ 宏* - 对于主机和模板级宏，请打开主机或模板属性，然后查找*macros*选项卡  ::: notetip 如果用户宏用于模板中的监控项或触发器，建议将该宏添加到模板中，即使该宏是在全局级别定义的。这样，如果宏类型为*text*，则将模板导出为XML并将其导入另一个系统仍将允许其按预期工作。秘密宏的值不会[导出](/manual/xml\u export\u import)。 :::  用户宏具有以下属性：  ![](../../../../assets/en/manual/config/macros/user_macros.png){width=“600”}  |参数|描述| |---------|-----------| |*宏*|宏名称。名字必须用花括号括起来，并以美元符号开头<br>示例：{$FRONTEND\_URL}。宏名称中允许使用以下字符：**A-Z**(仅大写)，**0-9**，**\_**，**.**| |*值*|宏值。支持三种值类型：<br>**Text**(默认)-纯文本值<br>**Secret Text**-该值用星号屏蔽，可用于保护密码或共享密钥等敏感信息<br>**Vault secret**-该值包含指向[Vault secret](/manual/config/secrets)的参考路径(如“path:key”，例如“secret/zabbix:password”)<br><br>*注意*当secret宏的值隐藏在视线之外时，可以通过在监控项中使用来显示该值。例如，在外部脚本中，可以使用引用秘密宏的“echo”语句向前端显示宏值，因为Zabbix服务器可以访问真正的宏值<br><br>要选择值类型，请单击值输入字段末尾的按钮：<br>![](../../../../assets/en/manual/config/macros/macro_type_text.png)图标表示文本宏<br>![](../../../../assets/en/manual/config/macros/macro_type_secret.png)图标表示密文宏。悬停时，值字段将转换为![](../../../../assets/en/manual/config/macros/macro_type_secret2.png)按钮，用于输入宏的新值(要退出而不保存新值，请单击向后箭头(![](../../../assets/en/manual/config/macros/macro_type_secret3.png))<br>![](../../../../assets/en/manual/config/macros/macro_type_vault.png)图标表示秘密vault宏<br><br>用户宏值的最大长度为2048个字符(在5.2.0之前的版本中为255个字符)| |*Description*|用于提供有关此宏的更多信息的文本字段|  :::noteclassic 包含秘密宏的URLs将无法工作，因为其中的宏将解析为“\*\*\*\*\*\*\*”。 :::  ::: noteimportant 在触发器表达式中，用户宏将解析是否引用参数或常量。如果引用主机、监控项键、函数、运算符或其他触发器表达式，则它们将不会解析。不能在触发器表达式中使用秘密宏。 :::

en-us	#### Configuration  To ensure proper communication between all elements involved make sure server configuration file and frontend configuration file parameters are properly configured.
zh-cn	#### 配置 为确保所涉及的所有元素之间的正确通信，请确保服务器配置文件和前端配置文件参数正确。

en-us	#### Configuration  To execute a passive check immediately:  -   click on *Execute now* in an existing item (or discovery rule)     configuration form:  ![execute\_now.png](../../../../assets/en/manual/config/items/execute_now.png)  -   click on *Execute now* for selected items/rules in the list of     items/discovery rules:  ![](../../../../assets/en/manual/config/items/execute_now_list.png)  In the latter case several items/rules can be selected and "executed now" at once.
zh-cn	#### 配置  要立刻执行被动检查：  -   在已存在的监控项（或自动发现规则）配置表单中点击*立即检查*:  ![check\_now.png](../../../../assets/en/manual/config/items/execute_now.png)  -   在监控项（或发现规则列表）中，选定监控项/规则后，单击*立即检查*:  ![](../../../../assets/en/manual/config/items/execute_now_list.png)  在第二种情况下，可以选择几个项目/规则，一次性对它们进行“立刻检查”。

en-us	#### Configuration  To start using a webhook integration:  1.  Locate required .xml file in the `templates/media` directory of the     downloaded Zabbix version or download it from Zabbix [git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse) 2.  [Import](/manual/xml_export_import/media#importing) the file into     your Zabbix installation. The webhook will appear in the list of     media types. 3.  Configure the webhook according to instructions in the *Readme.md*     file (you may click on a webhook's name above to quickly access     *Readme.md*).  To create a custom webhook from scratch:  -   Go to *Administration → Media types* -   Click on *Create media type*  The **Media type** tab contains various attributes specific for this media type:  ![](../../../../../assets/en/manual/config/notifications/media/media_webhook_express.png)  All mandatory input fields are marked with a red asterisk.  The following parameters are specific for the webhook media type:  |Parameter|Description| |--|--------| |*Parameters*|Specify the webhook variables as the attribute and value pairs.<br>For preconfigured webhooks, a list of parameters varies, depending on the service. Check the webhook's *Readme.md* file for parameter description.<br>For new webhooks, several common variables are included by default (URL:<empty>, HTTPProxy:<empty>, To:{ALERT.SENDTO}, Subject:{ALERT.SUBJECT}, Message:{ALERT.MESSAGE}), feel free to keep or remove them.<br>All [macros](/manual/appendix/macros/supported_by_location) that are supported in problem notifications are supported in the parameters.<br>If you specify an HTTP proxy, the field supports the same functionality as in the item configuration [HTTP proxy](/manual/config/items/itemtypes/http#configuration) field. The proxy string may be prefixed with `[scheme]://` to specify which kind of proxy is used (e.g. https, socks4, socks5; see [documentation](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html)).| |*Script*|Enter JavaScript code in the block that appears when clicking in the parameter field (or on the view/edit button next to it). This code will perform the webhook operation.<br>The script is a function code that accepts parameter - value pairs. The values should be converted into JSON objects using JSON.parse() method, for example: `var params = JSON.parse(value);`.<br><br>The code has access to all parameters, it may perform HTTP GET, POST, PUT and DELETE requests and has control over HTTP headers and request body.<br>The script must contain a return operator, otherwise it will not be valid. It may return OK status along with an optional list of tags and tag values (see *Process tags* option) or an error string.<br><br>Note, that the script is executed only after an alert is created. If the script is configured to return and process tags, these tags will not get resolved in {EVENT.TAGS} and {EVENT.RECOVERY.TAGS} macros in the initial problem message and recovery messages because the script has not had the time to run yet.<br><br>See also: [Webhook development guidelines](https://www.zabbix.com/documentation/guidelines/en/webhooks), [Webhook script examples](/manual/config/notifications/media/webhook/webhook_examples), [Additional JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects).<br>| |*Timeout*|JavaScript execution timeout (1-60s, default 30s).<br>Time suffixes are supported, e.g. 30s, 1m.| |*Process tags*|Mark the checkbox to process returned JSON property values as tags. These tags are added to the already existing (if any) problem event tags in Zabbix.<br>If a webhook uses tags (the Process tags checkbox is marked), the webhook should always return a JSON object containing at least an empty object for tags:`var result = {tags: {}};`.<br>Examples of tags that can be returned: *Jira ID: PROD-1234*, *Responsible: John Smith*, *Processed:<no value>*, etc.| |*Include event menu entry*|Mark the checkbox to include an entry in the [event menu](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) linking to the created external ticket.<br>If marked, the webhook should not be used to send notifications to different users (consider creating a [dedicated user](/manual/config/notifications/media/webhook#user_media) instead) or in several alert actions [related to a single problem event](/manual/config/notifications/media/webhook#configuring_alert_actions).| |*Menu entry name*|Specify the menu entry name.<br>{EVENT.TAGS.<tag name>} macro is supported.<br>This field is only mandatory if *Include event menu entry* is selected.| |*Menu entry URL*|Specify the underlying URL of the menu entry.<br>{EVENT.TAGS.<tag name>} macro is supported.<br>This field is only mandatory if *Include event menu entry* is selected.|  See [common media type parameters](/manual/config/notifications/media#common_parameters) for details on how to configure default messages and alert processing options.  ::: notewarning  Even if a webhook doesn't use default messages, message templates for operation types used by this webhook must still be defined. :::
zh-cn	#### 配置  开始使用webhook集成:  1.  在已下载的 Zabbix 的 `templates/media`目录中，找到所需的.xml文件；或者从Zabbix的 [git仓库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse)中下载 2.  将文件[导入](/manual/xml_export_import/media#importing) 到 Zabbix 安装，Webhook 将出现在媒体类型列表中。 3.  根据 *Readme.md* 文件中的说明来配置 webhook （也可以点击 webhook's 名称来快速访问 *Readme.md* ） 。  从零开始创建一个自定义的webhook:  -   进入*管理 → 媒介类型* -   点击*创建媒介类型*  **媒介类型**选项卡包含了针对这种媒介类型的各种属性:  ![](../../../../../assets/en/manual/config/notifications/media/media_webhook_express.png)  红色星号标记的为必填字段。  webhook媒介类型的具体参数如下:  |参数|说明| |---------|-----------| |*参数*|webhook变量作为属性和值对。<br>对于预先配置的webhook，参数列表会随着服务的不同而变化。检查webhook的*Readme.md* 参数说明文件。<br>对于新的webhooks，默认情况下包含了几个常见的变量 (URL:<empty>, HTTPProxy:<empty>, To:{ALERT.SENDTO}, Subject:{ALERT.SUBJECT}, Message:{ALERT.MESSAGE}), 你可以保留或删除它们。<br>参数中支持问题通知中支持的所有[宏](/manual/appendix/macros/supported_by_location) <br>如果指定了HTTP Proxy，该字段支持与监控项配置[HTTP proxy](/manual/config/items/itemtypes/http#configuration)字段相同的功能。 Proxy字符串可以加上前缀 `[scheme]://` 来指定使用哪种代理例如https, socks4, socks5; 请参见[documentation](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html)).| |*脚本*|在点击参数字段(或旁边的查看/编辑按钮)时出现的块中输入JavaScript代码。这段代码将执行webhook操作。<br>脚本是接受参数-值对的一段功能代码，它的值应该使用JSON.parse() 方法转换为JSON对象，例如：`var params = JSON.parse(value);`.<br><br>代码可以访问所有参数，它可以执行HTTP GET、POST、PUT和DELETE请求，并可控制HTTP头和请求正文。<br>脚本必须包含一个返回值，否则它将无效。它可以返回OK状态以及一个可选的标签列表，标签值(参见*Process tags*选项)，或一个错误的字符串。<br><br>注意，脚本只有在创建警报之后才会执行。如果脚本被配置为返回和处理标签 (参见*处理标签* 选项),这些标签将不会在初始问题消息和恢复消息中的 {EVENT.TAGS} 和 {EVENT.RECOVERY.TAGS} 宏中解析，因为脚本还没有时间运行。<br><br>另请参阅： [Webhook开发指南](https://www.zabbix.com/documentation/guidelines/webhooks), [Webhook脚本样例](/manual/config/notifications/media/webhook/webhook_examples), [额外的 JavaScript 对象](/manual/config/items/preprocessing/javascript/javascript_objects).<br>| |*超时*|JavaScript执行超时 (1-60s, 默认为30s)。<br>支持时间后缀, 例如 30s, 1m。| |*处理标签*|选中复选框标以将返回的JSON属性值作为标签处理。这些标签将被添加到Zabbix中已经存在的(如果有的话)问题事件标签中。<br>如果webhook使用了标签(Process tags复选框被选中),webhook应该返回一个至少带有一个空标签的JSON对象`var result = {tags: {}};`.<br>返回的标签示例: *Jira ID: PROD-1234*, *Responsible: John Smith*, *Processed:<no value>*, 等.| |*包括事件菜单项*|选中复选框以在[事件菜单](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) 中包含一个链接到创建的外部目标的条目。<br>若选中此项，webhook就不应该被用来向不同的用户发送通知 (考虑创建一个[专有用户](/manual/config/notifications/media/webhook#user_media)) 或者在几个告警动作中[关联单个问题事件](/manual/config/notifications/media/webhook#configuring_alert_actions).| |*菜单项名称*|指定菜单入口名称。<br>支持{EVENT.TAGS.<tag name>}宏<br>只有当*包括事件菜单项* 被选中时，该字段才为必填项。 |*菜单项URL*|指定菜单入口的URL。<br>支持{EVENT.TAGS.<tag name>} 宏<br>只有当*包括事件菜单项* 被选中时，该字段才为必填项。  关于如何配置默认消息和告警处理选项的详细信息，请参见 [通用媒介类型参数](/manual/config/notifications/media#common_parameters)  ::: notewarning  即使webhook不使用默认消息，webhook使用的操作类型的消息模板也必须定义。 :::

en-us	#### Configuration  Two steps are required to close a problem manually.
zh-cn	#### 配置  手动关闭问题需要两步。

en-us	#### Configuration  We assume that TimescaleDB extension has been already installed on the database server (see [installation instructions](https://docs.timescale.com/latest/getting-started/installation)).  TimescaleDB extension must also be enabled for the specific DB by executing:      echo "CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;" | sudo -u postgres psql zabbix  Running this command requires database administrator privileges.  ::: noteclassic If you use a database schema other than 'public' you need to add a SCHEMA clause to the command above. E.g.:\ `echo "CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;" | sudo -u postgres psql zabbix` :::  Then run the `timescaledb.sql` script located in database/postgresql. For new installations the script must be run after the regular PostgreSQL database has been created with initial schema/data (see [database creation](/manual/appendix/install/db_scripts)):      cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: noteimportant Please ignore warning messages informing that the best practices are not followed while running `timescaledb.sql` script on TimescaleDB version 2.9.0 and higher. Regardless of this warning, the configuration will be completed successfully. :::  The migration of existing history and trend data may take a lot of time. Zabbix server and frontend must be down for the period of migration.  The `timescaledb.sql` script sets the following housekeeping parameters:  -   Override item history period -   Override item trend period  In order to use partitioned housekeeping for history and trends, both these options must be enabled. It is also possible to enable override individually either for history only or trends only.  For PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher, the `timescaledb.sql` script sets two additional parameters:  -   Enable compression -   Compress records older than 7 days
zh-cn	#### 配置  我们假设数据库服务器上已经安装了 TimescaleDB 扩展（参见[安装说明](https://docs.timescale.com/latest/getting-started/installation)）。  还必须通过执行以下命令为特定数据库启用 TimescaleDB 扩展：      echo "CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;" | sudo -u postgres psql zabbix  运行此命令需要数据库管理员权限。  ::: noteclassic 如果您使用“public”以外的数据库模式，则需要在上面的命令中添加一个 SCHEMA 子句。 例如：\ `echo "CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;" | sudo -u postgres psql zabbix` :::  然后运行位于 database/postgresql 中的“timescaledb.sql”脚本。 对于新安装，必须在使用初始模式/数据创建常规 PostgreSQL 数据库后运行脚本（请参阅 [数据库创建](/manual/appendix/install/db_scripts)）：      cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: 注意重要 请忽略通知在 TimescaleDB 2.9.0 及更高版本上运行“timescaledb.sql”脚本时未遵循最佳实践的警告消息。 不管此警告如何，配置都将成功完成。 :::  现有历史和趋势数据的迁移可能需要很长时间。 Zabbix 服务器和前端在迁移期间必须关闭。  `timescaledb.sql` 脚本设置以下管理参数：  -  覆盖项目历史时期 -  覆盖项目趋势期  为了对历史和趋势使用分区管理，必须启用这两个选项。 也可以单独为仅历史或仅趋势启用覆盖。  对于 PostgreSQL 10.2 或更高版本和 TimescaleDB 1.5 或更高版本，`timescaledb.sql` 脚本设置了两个附加参数：  -  启用压缩 -  压缩超过 7 天的记录

en-us	##### Configure database for Zabbix proxy  Edit zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  In DBName for Zabbix proxy use a separate database from Zabbix server.  In DBPassword use Zabbix database password for MySQL; PosgreSQL user password for PosgreSQL.  Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. Refer to the [respective section](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) for RHEL/CentOS for instructions.
zh-cn	##### 为Zabbix proxy配置数据库  编辑 zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  在DBName 中为 Zabbix proxy创建单独的数据库或重命名数据库。  在DBPassword 中对MySQL使用Zabbix数据库密码；PosgreSQL使用它自己的用户密码。  将 `DBHost=` 与PostgreSQL一起用，你可能需要保留默认设置 `DBHost=localhost` (或1个 IP 地址)，但这可能会使PostgreSQL 通过网络套字连接到Zabbix。参考 RHEL/CentOS 的 [Selinux 配置](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) 获取说明。

en-us	##### Configure database for Zabbix proxy  Edit zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  In DBName for Zabbix proxy use a separate database from Zabbix server.  In DBPassword use Zabbix database password for MySQL; PosgreSQL user password for PosgreSQL.  Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. See [SELinux configuration](/manual/installation/install_from_packages/rhel_centos#selinux_configuration) for instructions.
zh-cn	 ##### 为Zabbix proxy配置数据库  编辑 zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  在 Zabbix proxy 的 DBName 中，使用与 Zabbix server 不同的数据库。  在 DBPassword 中为 MySQL 使用 Zabbix 数据库密码； PosgreSQL 用户 PosgreSQL 的密码。  将 `DBHost=` 与PostgreSQL一起用，你可能需要保留默认设置 `DBHost=localhost` (或1个 IP 地址)，但这可能会使PostgreSQL 通过网络套连接至Zabbix。参考 [SELinux configuration](/manual/installation/install_from_packages/rhel_centos#selinux_configuration)获取说明。

en-us	##### Configure database for Zabbix proxy  Edit zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  In DBName for Zabbix proxy use a separate database from Zabbix server.  In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL.  Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. See [SELinux configuration](/manual/installation/install_from_packages/rhel#selinux_configuration) for instructions.
zh-cn	##### 为 Zabbix 代理配置数据库  编辑 zabbix\_proxy.conf：   · # vi /etc/zabbix/zabbix_proxy.conf  · DBHost=localhost  · DBName=zabbix  · DBUser=zabbix  · DBPassword=<password>  在 Zabbix 代理的 DBName 中，使用与 Zabbix 服务器不同的数据库。  在 DBPassword 中使用 MySQL 的 Zabbix 数据库密码； PostgreSQL 的 PostgreSQL 用户密码。  在 PostgreSQL 中使用 `DBHost=`。 您可能希望保留默认值设置 `DBHost=localhost`（或 IP 地址），但这会使PostgreSQL 使用网络套接字连接到 Zabbix。 有关说明，请参阅 [SELinux 配置] (/manual/installation/install_from_packages/rhel#selinux_configuration)。

en-us	#### Configure database for Zabbix server/proxy  Edit /etc/zabbix/zabbix\_server.conf (and zabbix\_proxy.conf) to use their respective databases. For example:      # vi /etc/zabbix/zabbix_server.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  In DBPassword use Zabbix database password for MySQL; PosgreSQL user password for PosgreSQL.  Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix.
zh-cn	#### 为 Zabbix server/proxy 配置数据库  编辑 /etc/zabbix/zabbix\_server.conf 和 zabbix\_proxy.conf 来使用它们各自的数据库。例如：      # vi /etc/zabbix/zabbix_server.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  在DBPassword中对MySQL使用 Zabbix 数据库密码 ；在 PosgreSQL 中用 PosgreSQL 用户密码。  将 `DBHost=` 与PostgreSQL一起用，你可能希望保留默认值设置  `DBHost=localhost` (或一个IP地址)，但这会使PostgreSQL使用网络套接连接到Zabbix。

en-us	#### Configure DB connection  Enter details for connecting to the database. Zabbix database must already be created.  ![](../../../assets/en/manual/installation/install_3a.png){width="550"}  If the *Database TLS encryption* option is checked, then additional fields for [configuring the TLS connection](/manual/appendix/install/db_encrypt) to the database appear in the form (MySQL or PostgreSQL only).  If HashiCorp Vault option is selected for storing credentials, additional fields are available for specifying the Vault API endpoint, secret path and authentication token:  ![](../../../assets/en/manual/installation/install_3b.png){width="550"}
zh-cn	#### 配置数据库连通性  请在该页面输入连接到数据库所需的详细信息。在创建与数据库的连接前，Zabbix数据库必须先被创建。  ![](../../../assets/en/manual/installation/install_3a.png){width="550"}   若选择 *Database TLS encryption* 选项，则需要在出现的信息栏中填写有关 [configuring the TLS connection](/manual/appendix/install/db_encrypt)的配置信息（该功能仅限数据库类型为 MySQL 或 PostgreSQL）。 若选择 HashiCorp Vault 选项来进行凭据存储，请在附加的信息栏中输入相关信息，用以说明 Vault API 端点、隐藏路径以及身份验证令牌：  ![](../../../assets/en/manual/installation/install_3b.png){width="550"}

en-us	#### Configuring agent  Both generations of Zabbix agents run as a Windows service. For Zabbix agent 2, replace *agentd* with *agent2* in the instructions below.  You can run a single instance of Zabbix agent or multiple instances of the agent on a Microsoft Windows host. A single instance can use the default configuration file `C:\zabbix_agentd.conf` or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).  An example configuration file is available in Zabbix source archive as `conf/zabbix_agentd.win.conf`.  See the [configuration file](/manual/appendix/config/zabbix_agentd_win) options for details on configuring Zabbix Windows agent.
zh-cn	#### 配置 agent  两代Zabbix agent都是做为 Windows 服务运行的。对于 Zabbix agent 2，请在下面的说明中将 *agentd*  替换为 *agent2* 。  您可以在 Microsoft Windows 主机上运行 Zabbix agent的单个实例或多个实例。单个实例可以使用默认配置文件 `C:\zabbix_agentd.conf`或在命令行中指定的配置文件。在多个实例的情况下，每个代理实例都必须有自己的配置文件（其中一个实例可以使用默认配置文件）。  在Zabbix源码包中提供了一个示例配置文件，如下 `conf/zabbix_agentd.win.conf`.  有关配置 Zabbix Windows agent的详细信息的选项，另见 [配置文件](/manual/appendix/config/zabbix_agentd_win)。   ::: notewarning  ** 适用于 Windows 的 Zabbix  agent不支持非标准 Windows 配置，其 CPU 在 NUMA 节点之间不是统一分布的。 ** 如果逻辑 CPU 分布不均匀，则 CPU 性能指标可能不适用于某些 CPU。例如，如果有 72 个逻辑 CPU 和 2 个 NUMA 节点，则两个节点都必须有 36 个 CPU。 :::

en-us	#### Configuring a global script  ![](../../../../../assets/en/manual/web_interface/script.png)  Script attributes:  |Parameter|<|<|<|Description| |---------|-|-|-|-----------| |*Name*|<|<|<|Unique name of the script.<br>E.g. `Clear /tmp filesystem`| |*Scope*|<|<|<|Scope of the script - action operation, manual host action or manual event action. This setting determines where the script can be used - in remote commands of action operations, from the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) or from the [event menu](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) respectively.<br>Setting the scope to 'Action operation' makes the script available for all users with access to *Configuration* → *Actions*.<br>If a script is actually used in an action, its scope cannot be changed away from 'action operation'.<br>**Macro support**<br>The scope affects the range of available macros. For example, user-related macros ({USER.\*}) are supported in scripts to allow passing information about the user that launched the script. However, they are not supported if the script scope is action operation, as action operations are executed automatically.<br>To find out which macros are supported, do a search for 'Trigger-based notifications and commands/Trigger-based commands', 'Manual host action scripts' and 'Manual event action scripts' in the [supported macro](/manual/appendix/macros/supported_by_location) table. Note that if a macro may resolve to a value with spaces (for example, host name), don't forget to quote as needed.| |*Menu path*|<|<|<|The desired menu path to the script. For example, `Default` or `Default/`, will display the script in the respective directory. Menus can be nested, e.g. `Main menu/Sub menu1/Sub menu2`. When accessing scripts through the host/event menu in monitoring sections, they will be organized according to the given directories.<br>This field is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.| |*Type*|<|<|<|Click the respective button to select script type:<br>**Webhook**, **Script**, **SSH**, **Telnet** or **[IPMI](/manual/config/notifications/action/operation/remote_command#ipmi_remote_commands)** command.| |<|Script type: Webhook|<|<|<| |^|*Parameters*|<|<|Specify the webhook variables as attribute-value pairs.<br>See also: [Webhook](/manual/config/notifications/media/webhook) media configuration.<br>Macros and custom [user macros](/manual/config/macros/user_macros) are supported in parameter values. Macro support depends on the scope of the script (see *Scope* above).| |^|*Script*|<|<|Enter the JavaScript code in the block that appears when clicking in the parameter field (or on the view/edit button next to it).<br>Macro support depends on the scope of the script (see *Scope* above).<br>See also: [Webhook](/manual/config/notifications/media/webhook) media configuration, [Additional Javascript objects](/manual/config/items/preprocessing/javascript/javascript_objects).| |^|*Timeout*|<|<|JavaScript execution timeout (1-60s, default 30s).<br>Time suffixes are supported, e.g. 30s, 1m.| |<|Script type: Script|<|<|<| |^|*Execute on*|<|<|Click the respective button to execute the shell script on:<br>**Zabbix agent** - the script will be executed by Zabbix agent (if the system.run item is [allowed](/manual/config/items/restrict_checks)) on the host<br>**Zabbix server (proxy)** - the script will be executed by Zabbix server or proxy (if enabled by [EnableRemoteCommands](/manual/appendix/config/zabbix_proxy)) - depending on whether the host is monitored by server or proxy<br>**Zabbix server** - the script will be executed by Zabbix server only| |^|*Commands*|<|<|Enter full path to the commands to be executed within the script.<br>Macro support depends on the scope of the script (see *Scope* above). Custom [user macros](/manual/config/macros/user_macros) are supported.| |<|Script type: SSH|<|<|<| |^|*Authentication method*|<|<|Select authentication method - password or public key.| |^|*Username*|<|<|Enter the username.| |^|*Password*|<|<|Enter the password.<br>This field is available if 'Password' is selected as the authentication method.| |^|*Public key file*|<|<|Enter the path to the public key file.<br>This field is available if 'Public key' is selected as the authentication method.| |^|*Private key file*|<|<|Enter the path to the private key file.<br>This field is available if 'Public key' is selected as the authentication method.| |^|*Passphrase*|<|<|Enter the passphrase.<br>This field is available if 'Public key' is selected as the authentication method.| |^|*Port*|<|<|Enter the port.| |^|*Commands*|<|<|Enter the commands.<br>Macro support depends on the scope of the script (see *Scope* above). Custom [user macros](/manual/config/macros/user_macros) are supported.| |<|Script type: Telnet|<|<|<| |^|*Username*|<|<|Enter the username.| |^|*Password*|<|<|Enter the password.| |^|*Port*|<|<|Enter the port.| |^|*Commands*|<|<|Enter the commands.<br>Macro support depends on the scope of the script (see *Scope* above). Custom [user macros](/manual/config/macros/user_macros) are supported.| |<|Script type: IPMI|<|<|<| |^|*Command*|<|<|Enter the IPMI command.<br>Macro support depends on the scope of the script (see *Scope* above). Custom [user macros](/manual/config/macros/user_macros) are supported.| |*Description*|<|<|<|Enter a description for the script.| |*Host group*|<|<|<|Select the host group that the script will be available for (or *All* for all host groups).| |*User group*|<|<|<|Select the user group that the script will be available to (or *All* for all user groups).<br>This field is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.| |*Required host permissions*|<|<|<|Select the permission level for the host group - *Read* or *Write*. Only users with the required permission level will have access to executing the script.<br>This field is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.| |*Enable confirmation*|<|<|<|Mark the checkbox to display a confirmation message before executing the script. This feature might be especially useful with potentially dangerous operations (like a reboot script) or ones that might take a long time.<br>This option is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.| |*Confirmation text*|<|<|<|Enter a custom confirmation text for the confirmation popup enabled with the checkbox above (for example, *Remote system will be rebooted. Are you sure?*). To see how the text will look like, click on *Test confirmation* next to the field.<br>{HOST.\*} and {USER.\*} macros are supported. Custom [user macros](/manual/config/macros/user_macros) are supported.<br>*Note:* the macros will not be expanded when testing the confirmation message.<br>This field is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.|
zh-cn	### 配置全局脚本  ![](../../../../../assets/en/manual/web_interface/script.png)  脚本属性：  |参数|<|<|<|说明| |---------|-|-|-|------------| |*名称*|<|<|<|脚本的唯一名称。<br>例如`清除 /tmp 文件系统`| |*范围*|<|<|<|脚本的范围 - 动作操作、手动主机动作或手动事件动作。此设置确定脚本可以在哪里使用 - 在操作操作的远程命令中，来自 [主机菜单](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) 或来自 [事件菜单](/manual/web_interface/ frontend_sections/monitoring/problems#event_menu)。<br>将范围设置为“操作操作”使脚本可供所有有权访问 *配置* → *动作* 的用户使用。<br>如果脚本实际用于动作，它的范围不能从“动作操作”改变。<br>**宏支持**<br>范围影响可用宏的范围。例如，脚本支持与用户相关的宏 ({USER.\*})，以允许传递有关启动脚本的用户的信息。但是，如果脚本范围是操作操作，则不支持它们，因为操作操作会自动执行。<br>要了解支持哪些宏，请搜索“基于触发器的通知和命令/基于触发器的命令”， [支持的宏](/manual/appendix/macros/supported_by_location) 表中的“手动主机操作脚本”和“手动事件操作脚本”。请注意，如果宏可以解析为带有空格的值（例如，主机名），请不要忘记根据需要引用。| |*菜单路径*|<|<|<|脚本所需的菜单路径。例如，`Default` 或 `Default/`，将在各自的目录中显示脚本。菜单可以嵌套，例如`主菜单/子菜单1/子菜单2`。通过监控部分中的主机/事件菜单访问脚本时，它们将根据给定目录进行组织。<br>仅当“手动主机操作”或“手动事件操作”选择为 *范围* 时，才会显示此字段。 | |*类型*|<|<|<|点击相应的按钮选择脚本类型：<br>**Webhook**, **Script**, **SSH**, **Telnet** or **[ IPMI](/manual/config/notifications/action/operation/remote_command#ipmi_remote_commands)** 命令。| |<|脚本类型：Webhook|<|<|<| |^|*参数*|<|<|将 webhook 变量指定为属性值对。<br>另请参阅：[Webhook](/manual/config/notifications/media/webhook) 媒体配置。<br>宏和参数值支持自定义 [用户宏](/manual/config/macros/user_macros)。宏支持取决于脚本的范围（参见上面的*范围*）。| |^|*脚本*|<|<|在单击参数字段（或旁边的查看/编辑按钮）时出现的块中输入 JavaScript 代码。<br>宏支持取决于脚本（请参阅上面的 *Scope*）。<br>另请参阅：[Webhook](/manual/config/notifications/media/webhook) 媒体配置，[其他 Javascript 对象](/manual/config/items/preprocessing/javascript/ javascript_objects)。| |^|*超时*|<|<|JavaScript 执行超时（1-60 秒，默认 30 秒）。<br>支持时间后缀，例如30s，1m。| |<|脚本类型：脚本|<|<|<| |^|*执行于*|<|<|点击相应的按钮执行shell脚本：<br>**Zabbix agent** - 脚本将由Zabbix agent执行（如果system.run项是[ allowed](/manual/config/items/restrict_checks)) 在主机上<br>**Zabbix server (proxy)** - 脚本将由 Zabbix server 或 proxy 执行（如果由 [EnableRemoteCommands](/manual/ appendix/config/zabbix_proxy)) - 取决于主机是由服务器监控还是代理监控<br>**Zabbix server** - 脚本将仅由Zabbix server执行| |^|*命令*|<|<|输入要在脚本中执行的命令的完整路径。<br>宏支持取决于脚本的范围（参见上面的*Scope*）。支持自定义 [用户宏](/manual/config/macros/user_macros)。| |<|脚本类型：SSH|<|<|<| |^|*认证方式*|<|<|选择认证方式-密码或公钥。| |^|*用户名*|<|<|输入用户名。| |^|*密码*|<|<|输入密码。<br>如果选择“密码”作为验证方法，则此字段可用。| |^|*公钥文件*|<|<|输入公钥文件的路径。<br>如果选择“公钥”作为身份验证方法，则此字段可用。| |^|*私钥文件*|<|<|输入私钥文件的路径。<br>如果选择“公钥”作为验证方法，则此字段可用。| |^|*密码*|<|<|输入密码。<br>如果选择“公钥”作为身份验证方法，则此字段可用。| |^|*端口*|<|<|输入端口。| |^|*命令*|<|<|输入命令。<br>宏支持取决于脚本的范围（参见上面的*Scope*）。支持自定义 [用户宏](/manual/config/macros/user_macros)。| |<|脚本类型：Telnet|<|<|<| |^|*用户名*|<|<|输入用户名。| |^|*密码*|<|<|输入密码。| |^|*端口*|<|<|输入端口。| |^|*命令*|<|<|输入命令。<br>宏支持取决于脚本的范围（参见上面的*Scope*）。支持自定义 [用户宏](/manual/config/macros/user_macros)。| |<|脚本类型：IPMI|<|<|<| |^|*命令*|<|<|输入 IPMI 命令。<br>宏支持取决于脚本的范围（参见上面的 *Scope*）。支持自定义 [用户宏](/manual/config/macros/user_macros)。| |*描述*|<|<|<|输入脚本的描述。| |*主机组*|<|<|<|选择脚本可用于的主机组（或 *All* 用于所有主机组）。| |*用户组*|<|<|<|选择脚本可用的用户组（或所有用户组的*全部*）。<br>此字段仅在“手动主机操作”或“手动事件操作'被选为 *Scope*。| |*必需的主机权限*|<|<|<|选择主机组的权限级别 - *Read* 或 *Write*。 Only users with the required permission level will have access to executing the script.<br>This field is displayed only if 'Manual host action' or 'Manual event action' is selected as *Scope*.| |*启用确认*|<|<|<|标记复选框以在执行脚本之前显示确认消息。此功能对于具有潜在危险的操作（如重新启动脚本）或可能需要很长时间的操作可能特别有用。<br>仅当“手动主机操作”或“手动事件操作”选为 *Scope 时才会显示此选项*.| |*确认文本*|<|<|<|为使用上面的复选框启用的确认弹出窗口输入自定义确认文本（例如，*远程系统将重新启动。您确定吗？*）。要查看文本的外观，请单击字段旁边的*测试确认*。<br>支持 {HOST.\*} 和 {USER.\*} 宏。支持自定义 [用户宏](/manual/config/macros/user_macros)。<br>*注意：* 测试确认消息时不会展开宏。<br>仅当“手动主机操作”时才会显示此字段' 或 '手动事件操作' 被选为 *Scope*。|

en-us	#### Configuring alert actions  Actions determine which notifications should be sent via the webhook. Steps for [configuring actions](/manual/config/notifications/action) involving webhooks are the same as for all other media types with these exceptions:  -   If a webhook uses tags to store ticket\\message ID and to follow up     with update\\resolve operations, this webhook should not be used in     several alert actions for a single problem event. If     {EVENT.TAGS.<name>} already exists, and is updated in the     webhook, then its resulting value is not defined. For such a case, a     new tag name should be used in the webhook to store updated values.     This applies to Jira, Jira Service Desk, Mattermost, Opsgenie, OTRS,     Redmine, ServiceNow, Slack, Zammad, and Zendesk webhooks provided by     Zabbix and to the majority of webhooks that utilize *Include event     menu entry* option. Using the webhook in several operations is     allowed if those operations or escalation steps belong to the same     action. It is also ok to use this webhook in different actions if     the actions will not be applied to the same problem event due to     different filter conditions. -   When using a webhook in actions for [internal     events](/manual/config/events/sources#internal_events): in the     action operation configuration, check the *Custom message* checkbox     and define the custom message, otherwise, a notification will not be     sent.
zh-cn	#### 配置告警动作  告警动作决定了哪些通知应该通过webhook发送。webhook的[configuring actions](/manual/config/notifications/action) 步骤与所有其他媒体类型相同，但有以下例外:  -   如果webhook使用标签来存储 ticket\\message ID 以及后续的 update\\resolve operations 操作, 这个webhook不应该用于单个问题事件的多个告警动作中。这适用于Zabbix提供的Jira, Jira Service Desk, Mattermost, Opsgenie, OTRS, Redmine, ServiceNow, Slack, Zammad和Zendesk webhooks以及大多数使用 *Include event menu entry* 选项的webhook。 如果操作或升级步骤属于同一个动作，允许在多个操作中使用webhook。在不同的动作中使用webhook也是可以的，由于不同的筛选器条件，动作不会应用到相同的问题事件中。 -   当在动作中使用webhook用于  [internal events](/manual/config/events/sources#internal_events): 在动作操作配置中，选中 *Custom message*复选框，输入自定义消息内容 ，否则通知不会被发送出去。

en-us	#### Configuring an action  To configure an action, do the following:  -   In the *Configuration* menu section, click on *Actions* and select     the required action type from the submenu that appears. (You can     also use the title dropdown to switch between action types later.) -   Click on *Create action* -   Name the action -   Choose [conditions](/manual/config/notifications/action/conditions)     upon which operations are carried out -   Choose the     [operations](/manual/config/notifications/action/operation) to carry     out  General action attributes:  ![](../../../../assets/en/manual/config/notifications/action.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Name*|Unique action name.| |*Type of calculation*|Select the evaluation [option](/manual/config/notifications/action/conditions#type_of_calculation) for action conditions (with more than one condition):<br>**And** - all conditions must be met<br>**Or** - enough if one condition is met<br>**And/Or** - combination of the two: AND with different condition types and OR with the same condition type<br>**Custom expression** - a user-defined calculation formula for evaluating action conditions.| |*Conditions*|List of action conditions.<br>Click on *Add* to add a new [condition](/manual/config/notifications/action/conditions).| |*Enabled*|Mark the checkbox to enable the action. Otherwise, it will be disabled.|  
zh-cn	 #### 配置动作  配置动作，步骤如下：  -   在 *Configuration* 菜单中点击*Actions*并且选择对应的动作类型。(也可以在标题下拉框中进行动作类型的切换) -   点击*Create action* -   给动作命名 -   选择执行动作的条件[conditions](/manual/config/notifications/action/conditions) -   选择执行动作的操作[operations](/manual/config/notifications/action/operation)  常见动作属性：  ![](../../../../assets/en/manual/config/notifications/action.png)  带有红色星号的为必填字段。  |参数|说明| |---------|-----------| |*Name*|动作名称(需唯一)| |*Type of calculation*|选择评估 [option](/manual/config/notifications/action/conditions#type_of_calculation) 作为行动条件（有多个条件）：<br>**And** - 必须满足所有条件<br>**Or** - 只需满足其中一个条件<br>**And/Or** - 两者的组合：AND有不同的条件类型，OR有相同的条件类型<br>**自定义的表达式** - 用户自定义计算公式来进行条件的计算.| |*Conditions*|条件的清单。<br>点击*Add*添加一个新的[condition](/manual/config/notifications/action/conditions).| |*Enabled*|选中复选框以启用该操作。否则将被禁用。|  

en-us	#### Configuring and running Java gateway  Configuration parameters of Zabbix Java gateway may be tuned in the file:      /etc/zabbix/zabbix_java_gateway.conf  For more details, see Zabbix Java gateway configuration [parameters](/manual/appendix/config/zabbix_java).  To start Zabbix Java gateway:      # service zabbix-java-gateway restart  To automatically start Zabbix Java gateway on boot:  RHEL 7 and later:      # systemctl enable zabbix-java-gateway  RHEL prior to 7:      # chkconfig --level 12345 zabbix-java-gateway on
zh-cn	#### 配置并运行 JAVA 网关  Zabbix Java 网关的配置参数可以通过如下文件进行调整：      /etc/zabbix/zabbix_java_gateway.conf  关于更多信息，详见 Zabbix Java 网关配置[参数](/manual/appendix/config/zabbix_java)。  通过以下命令启动 Zabbix Java 网关:      # service zabbix-java-gateway restart  通过以下命令配置 Zabbix Java 网关开机自启动:  RHEL 7 和 RHEL 7 之后的系统：      # systemctl enable zabbix-java-gateway  RHEL 7 之前的系统：      # chkconfig --level 12345 zabbix-java-gateway on

en-us	#### Configuring an operation  To configure an operation, go to the *Operations* tab in [action](/manual/config/notifications/action) configuration.  ![](../../../../../assets/en/manual/config/notifications/action_operation.png){width="600"}  General operation attributes:  |Parameter|Description| |--|-----------| |*Default operation step duration*|Duration of one operation step by default (60 seconds to 1 week).<br>For example, an hour-long step duration means that if an operation is carried out, an hour will pass before the next step.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 60s, 1m, 2h, 1d, since Zabbix 3.4.0.<br>[User macros](/manual/config/macros/user_macros) are supported, since Zabbix 3.4.0.| |*Operations*|Action operations (if any) are displayed, with these details:<br>**Steps** - escalation step(s) to which the operation is assigned<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Start in** - how long after an event the operation is performed<br>**Duration (sec)** - step duration is displayed. *Default* is displayed if the step uses default duration, and a time is displayed if custom duration is used.<br>**Action** - links for editing and removing an operation are displayed.| |*Recovery operations*|Action operations (if any) are displayed, with these details:<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Action** - links for editing and removing an operation are displayed.| |*Update operations*|Action operations (if any) are displayed, with these details:<br>**Details** - type of operation and its recipient/target.<br>The operation list also displays the media type (e-mail, SMS or script) used as well as the name and surname (in parentheses after the username) of a notification recipient.<br>**Action** - links for editing and removing an operation are displayed.| |*Pause operations for suppressed problems*|Mark this checkbox to delay the start of operations for the duration of a maintenance period. When operations are started, after the maintenance, all operations are performed including those for the events during the maintenance.<br>Note that this setting affects only problem escalations; recovery and update operations will not be affected.<br>If you unmark this checkbox, operations will be executed without delay even during a maintenance period.<br>This option is not available for *Service actions*.| |*Notify about canceled escalations*|Unmark this checkbox to disable notifications about canceled escalations (when host, item, trigger or action is disabled).|  All mandatory input fields are marked with a red asterisk.  To configure details of a new operation, click on ![](../../../../../assets/en/manual/config/add_link.png) in the Operations block. To edit an existing operation, click on ![](../../../../../assets/en/manual/config/edit_link.png) next to the operation. A popup window will open where you can edit the operation step details.
zh-cn	#### 配置操作  要配置操作，请转到 [动作](/manual/config/notifications/action) 配置中的 *操作* 选项卡。  ![](../../../../../assets/en/manual/config/notifications/action_operation.png){width="600"}  一般操作属性：  |参数|说明| |--|------------| |*默认操作步骤持续时间*|默认一个操作步骤的持续时间（60秒到1周）。<br>例如，长达一个小时的步骤持续时间，意味着如果进行了该操作，一个小时后才会执行下个步骤。<br>支持[时间后缀](/manual/appendix/suffixes)，例如 60s, 1m, 2h, 1d, since Zabbix 3.4.0.<br>从Zabbix 3.4.0开始支持[用户宏](/manual/config/macros/user_macros)| |*操作*|显示动作的操作（如果有），以及以下详细信息：<br>**步骤** - 操作分配到的升级步骤<br>**详细信息** - 操作类型及其收件人/目标。<br>操作列表还显示使用的媒体类型（电子邮件、短信或脚本）以及通知收件人的姓名（在用户名后的括号中）。<br>* *开始于** - 事件发生后多长时间执行操作<br>**持续时间（秒）** - 显示步骤持续时间。 如果步骤使用默认持续时间，则显示*默认*，如果使用自定义持续时间，则显示时间。<br>**动作** - 显示用于编辑和删除操作的链接。| |*恢复操作*|显示动作的操作（如果有），以及以下详细信息：<br>**详细信息** - 操作类型及其接收者/目标。<br>操作列表还显示媒体类型（电子邮件、短信或脚本）以及通知收件人的姓名（在用户名后的括号中）。<br>**动作** - 显示用于编辑和删除操作的链接。| |*更新操作*|显示动作的操作（如果有），以及以下详细信息：<br>**详细信息** - 操作类型及其接收者/目标。<br>操作列表还显示媒体类型（电子邮件、短信或脚本）以及通知收件人的姓名（在用户名后的括号中）。<br>**动作** - 显示用于编辑和删除操作的链接。| |*被抑制的问题暂停操作*|标记此复选框以在维护期间延迟操作的开始。 在维护之后，当操作开始时，包括维护期间事件内的所有操作都会执行。<br>请注意，此设置仅影响问题升级；恢复和更新操作不会受到影响。<br>如果取消选中此复选框，即使在维护期间也将立即执行操作。<br>此选项不适用于*服务动作*。| |*通知已取消的升级*|取消标记此复选框以禁用有关已取消升级的通知（当主机、监控项、触发器或动作被禁用时）。|  所有必填输入字段都标有红色星号。  要配置新操作的详细信息，请单击操作块中的 ![](../../../../../assets/en/manual/config/add_link.png)。 要编辑现有操作，请单击操作旁边的 ![](../../../../../assets/en/manual/config/edit_link.png)。 将打开一个弹出窗口，您可以在其中编辑操作步骤详细信息。

en-us	#### Configuring an update operation  To configure an update operation go to the *Operations* tab in action [configuration](/manual/config/notifications/action).  ![](../../../../../assets/en/manual/config/update_operation.png)  To configure details of a new update operation, click on ![](../../../../../assets/en/manual/config/add_link.png) in the Update operations block. To edit an existing operation, click on ![](../../../../../assets/en/manual/config/edit_link.png) next to the operation. A popup window will open where you can edit the operation step details.
zh-cn	#### 配置更新操作  要配置更新操作，请转到操作中的[配置](/manual/config/notifications/action)选项卡。  ![](../../../../../assets/en/manual/config/update_operation.png)  要配置新更新操作的详细信息，请在更新操作块中单击![](../../../../../assets/en/manual/config/add_link.png)。要编辑现有操作，请在下个选项卡中单击![](../../../../../assets/en/manual/config/edit_link.png)。将会打开一个弹出窗口，您可以在其中编辑操作步骤细节。

en-us	### Configuring a recovery operation  To configure a recovery operation, go to the *Operations* tab in [action](/manual/config/notifications/action) configuration.  ![](../../../../../assets/en/manual/config/recovery_operation.png)  To configure details of a new recovery operation, click on ![](../../../../../assets/en/manual/config/add_link.png) in the Recovery operations block. To edit an existing operation, click on ![](../../../../../assets/en/manual/config/edit_link.png) next to the operation. A popup window will open where you can edit the operation step details.
zh-cn	### 配置恢复操作  要配置恢复操作，请转到 [动作](/manual/config/notifications/action) 配置中的 *操作* 选项卡。  ![](../../../../../assets/en/manual/config/recovery_operation.png)  要配置新恢复操作的详细信息，请单击恢复操作块中的 ![](../../../../../assets/en/manual/config/add_link.png)。 要编辑现有操作，请单击操作旁边的 ![](../../../../../assets/en/manual/config/edit_link.png)。 将打开一个弹出窗口，您可以在其中编辑操作步骤详细信息。

en-us	#### Configuring authentication  The **Authentication** tab allows you to configure scenario authentication options. A green dot next to the tab name indicates that some type of HTTP authentication is enabled.  ![](../../assets/en/manual/config/scenario_d.png)  Authentication parameters:  |Parameter|Description| |--|--------| |*Authentication*|Authentication options.<br>**None** - no authentication used.<br>**Basic** - basic authentication is used.<br>**NTLM** - NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) authentication is used.<br>**Kerberos** - Kerberos authentication is used. See also: [Configuring Kerberos with Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - Digest authentication is used.<br>Selecting an authentication method will provide two additional fields for entering a user name and password.<br>User macros can be used in user and password fields.| |*SSL verify peer*|Mark the checkbox to verify the SSL certificate of the web server.<br>The server certificate will be automatically taken from system-wide certificate authority (CA) location. You can override the location of CA files using Zabbix server or proxy configuration parameter [SSLCALocation](/manual/appendix/config/zabbix_server).<br>This sets the [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL option.| |*SSL verify host*|Mark the checkbox to verify that the *Common Name* field or the *Subject Alternate Name* field of the web server certificate matches.<br>This sets the [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL option.| |*SSL certificate file*|Name of the SSL certificate file used for client authentication. The certificate file must be in PEM^1^ format. If the certificate file contains also the private key, leave the *SSL key file* field empty. If the key is encrypted, specify the password in *SSL key password* field. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL option.| |*SSL key file*|Name of the SSL private key file used for client authentication. The private key file must be in PEM^1^ format. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL option.| |*SSL key password*|SSL private key file password.<br>User macros can be used in this field.<br>This sets the [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL option.|  ::: noteimportant  \[1\] Zabbix supports certificate and private key files in PEM format only. In case you have your certificate and private key data in PKCS \#12 format file (usually with extension \*.p12 or \*.pfx) you may generate the PEM file from it using the following commands:      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes  -out ssl-cert.key   :::  ::: noteclassic  Zabbix server picks up changes in certificates without a restart.  :::  ::: noteclassic  If you have client certificate and private key in a single file just specify it in a "SSL certificate file" field and leave "SSL key file" field empty. The certificate and key must still be in PEM format. Combining certificate and key is easy:      cat client.crt client.key > client.pem   :::
zh-cn	#### 配置认证  **认证** 选项卡允许配置场景身份认证选项。选项卡名称旁边的绿点表示启用了某种类型的 HTTP 身份验证。  ![](../../assets/en/manual/config/scenario_d.png)  认证参数：  |参数|描述| |---------|-----------| |*Authentication（认证）*|身份认证选项。<br>**None（无）** - 不使用身份认证。<br>**Basic（基本）** - 使用基本身份验证。<br>**NTLM** - 使用 NTLM（ [Windows NT LAN Manager](http://en.wikipedia.org/wiki/NTLM)） 身份认证。<br>**Kerberos** - 使用 Kerberos 身份验证。另请参阅：[Zabbix 配置 Kerberos 认证](/manual/appendix/items/kerberos).<br>**Digest** - 使用 Digest 身份认证。<br>选择身份认证将提供两个额外的字段用于输入用户名和密码。<br>用户宏可用于用户和密码字段。| |*SSL verify peer（SSL验证对端）*|勾选复选框以验证 Web 服务器的 SSL 证书。<br>服务器证书将自动从系统范围的证书颁发机构 (CA) 位置获取。您可以使用 Zabbix server 或 proxy 配置参数 [SSLCALocation](/manual/appendix/config/zabbix_server) 覆盖 CA 文件的位置。<br>这将设置 [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL 选项。| |*SSL verify host（SSL验证主机）*|标记复选框以验证Web 服务器证书的 *Common Name* 字段或 *Subject Alternate Name* 字段是否匹配。<br>这将设置 [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL 选项。| |*SSL certificate file（SSL证书文件）*|用于客户端身份验证的 SSL 证书文件的名称。证书文件必须为  PEM^1^ 格式。如果证书文件还包含私钥，请将 *SSL key file（SSL秘钥文件）* 字段留空。如果密钥已加密，请在 *SSL key password（SSL秘钥密码）*字段中指定密码。包含此文件的目录由  Zabbix server 或 proxy 配置参数 [SSLCertLocation](/manual/appendix/config/zabbix_server)指定。<br>支持`HOST.*` 宏和用户宏。<br>这将设置 [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL 选项。| |*SSL key file（SSL秘钥文件）*|用于客户端身份验证的 SSL 私钥文件的名称。私钥文件必须是 PEM^1^ 格式。包含此文件的目录由 Zabbix server 或 proxy 配置参数 [SSLKeyLocation](/manual/appendix/config/zabbix_server) 指定。<br>支持`HOST.*` 宏和用户宏。<br>这将设置 [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL 选项。| |*SSL key password（SSL秘钥密码）*|SSL 私钥文件密码。<br>支持用户宏。<br>这将设置 [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL 选项。|  ::: noteimportant  \[1\] Zabbix 仅支持 PEM 格式的证书和私钥文件。如果你有 PKCS \#12 格式文件（通常带有扩展名 \*.p12 或 \*.pfx）的证书和私钥数据，可以使用以下命令从中生成 PEM 文件：      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes · -out ssl-cert.key  :::  ::: noteclassic  Zabbix server 无需重启即可获取证书中的更改。 :::  ::: noteclassic 如果你在单个文件中有客户端证书和私钥，只需在 "SSL certificate file（SSL 证书文件）" 字段中指定它，并将 "SSL key file（SSL秘钥文件）" 字段留空。证书和密钥必须仍为 PEM 格式。组合证书和密钥很容易：      cat client.crt client.key > client.pem   :::

en-us	#### Configuring a web scenario  To configure a web scenario:  -   Go to: *Configuration → Hosts* (or *Templates*) -   Click on *Web* in the row of the host/template -   Click on *Create scenario* to the right (or on the scenario name to     edit an existing scenario) -   Enter parameters of the scenario in the form  The **Scenario** tab allows you to configure the general parameters of a web scenario.  ![](../../assets/en/manual/config/scenario.png)  All mandatory input fields are marked with a red asterisk.  Scenario parameters:  |Parameter|Description| |--|--------| |*Host*|Name of the host/template that the scenario belongs to.| |*Name*|Unique scenario name.| |*Update interval*|How often the scenario will be executed.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported. *Note* that if a user macro is used and its value is changed (e.g. 5m → 30s), the next check will be executed according to the previous value (farther in the future with the example values).| |*Attempts*|The number of attempts for executing web scenario steps. In case of network problems (timeout, no connectivity, etc) Zabbix can repeat executing a step several times. The figure set will equally affect each step of the scenario. Up to 10 attempts can be specified, default value is 1.<br>*Note*: Zabbix will not repeat a step because of a wrong response code or the mismatch of a required string.| |*Agent*|Select a client agent.<br>Zabbix will pretend to be the selected browser. This is useful when a website returns different content for different browsers.<br>User macros can be used in this field.| |*HTTP proxy*|You can specify an HTTP proxy to use, using the format `[protocol://][username[:password]@]proxy.example.com[:port]`.<br>This sets the [CURLOPT\_PROXY](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html) cURL option.<br>The optional `protocol://` prefix may be used to specify alternative proxy protocols (the protocol prefix support was added in cURL 7.21.7). With no protocol specified, the proxy will be treated as an HTTP proxy.<br>By default, 1080 port will be used.<br>If specified, the proxy will overwrite proxy related environment variables like http\_proxy, HTTPS\_PROXY. If not specified, the proxy will not overwrite proxy-related environment variables. The entered value is passed on "as is", no sanity checking takes place.<br>You may also enter a SOCKS proxy address. If you specify the wrong protocol, the connection will fail and the item will become unsupported.<br>*Note* that only simple authentication is supported with HTTP proxy.<br>User macros can be used in this field.| |*Variables*|Variables that may be used in scenario steps (URL, post variables).<br>They have the following format:<br>**{macro1}**=value1<br>**{macro2}**=value2<br>**{macro3}**=regex:<regular expression><br>For example:<br>{username}=Alexei<br>{password}=kj3h5kJ34bd<br>{hostid}=regex:hostid is (\[0-9\]+)<br>The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values. Note that variables with `regex:` need one step to get the value of the regular expression so the extracted value can only be applied to the step after.<br>If the value part starts with `regex:` then the part after it is treated as a regular expression that searches the web page and, if found, stores the match in the variable. At least one subgroup must be present so that the matched value can be extracted.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.<br>Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.| |*Headers*|HTTP Headers are used when performing a request. Default and custom headers can be used.<br>Headers will be assigned using default settings depending on the Agent type selected from a drop-down list on a scenario level, and will be applied to all the steps, unless they are custom defined on a step level.<br>**It should be noted that defining the header on a step level automatically discards all the previously defined headers, except for a default header that is assigned by selecting the 'User-Agent' from a drop-down list on a scenario level.**<br>However, even the 'User-Agent' default header can be overridden by specifying it on a step level.<br>To unset the header on a scenario level, the header should be named and attributed with no value on a step level.<br>Headers should be listed using the same syntax as they would appear in the HTTP protocol, optionally using some additional features supported by the [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL option.<br>For example:<br>Accept-Charset=utf-8<br>Accept-Language=en-US<br>Content-Type=application/xml; charset=utf-8<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Enabled*|The scenario is active if this box is checked, otherwise - disabled.|  Note that when editing an existing scenario, two extra buttons are available in the form:  |   |   | |--|--------| |![](../../assets/en/manual/web_monitoring/buttons_clone.png)|Create another scenario based on the properties of the existing one.| |![](../../assets/en/manual/web_monitoring/buttons_clear.png)|Delete history and trend data for the scenario. This will make the server perform the scenario immediately after deleting the data.|  ::: notetip If *HTTP proxy* field is left empty, another way for using an HTTP proxy is to set proxy related environment variables.  For HTTP checks - set the **http\_proxy** environment variable for the Zabbix server user. For example, `http_proxy=http://proxy_ip:proxy_port`.  For HTTPS checks - set the **HTTPS\_PROXY** environment variable. For example, `HTTPS_PROXY=http://proxy_ip:proxy_port`. More details are available by running a shell command: *\# man curl*. :::  The **Steps** tab allows you to configure the web scenario steps. To add a web scenario step, click on *Add* in the *Steps* block.  ![](../../assets/en/manual/config/scenario_b.png){width="600"}  ::: noteclassic Secret [user macros](/manual/config/macros/user_macros#configuration) must not be used in URLs as they will resolve to "\*\*\*\*\*\*". :::
zh-cn	#### 配置 Web 场景  配置 Web 场景流程：  -   *Configuration（配置） → Hosts（主机）*（或 *模板*） -   单击 主机/模板 行中的 *Web*  -   单击右侧的  *Create scenario（创建场景）* （或在场景名称上编辑现有场景） -   在表格中输入场景的参数  **场景** 选项卡可以配置 Web 场景的常规参数。  ![](../../assets/en/manual/config/scenario.png)  所有必填字段都标有红色星号。  场景参数：  |参数|描述| |---------|-----------| |*Host*|场景所属的主机/模板的名称。| |*Name*|场景的唯一名称。| |*Update interval*|场景执行的频率。<br>支持 [时间后缀](/manual/appendix/suffixes) ，例如 30s、1m、2h、1d。<br>[支持用户宏](/manual/config/macros/user_macros) 。*注意*： 如果使用用户宏并更改其值 (例如 5m → 30s)，则将根据先前的值执行下一次检查（示例值在更远的将来）。| |*Attempts*|尝试执行 Web 场景步骤的次数。如果出现网络问题（超时、无连接等），Zabbix 可以多次重复执行一个步骤。图集同样会影响场景的每个步骤。最多可以指定 10 次尝试，默认值为 1。<br>*注意*：Zabbix 不会因为响应码错误或所需字符串不匹配而重复步骤。| |*Agent（客户端）*|选择客户端。<br>Zabbix 会伪装成被选中的浏览器。当网站为不同的浏览器返回不同的内容时，这很有用。<br>用户宏可用于该字段。| |*HTTP proxy（HTTP 代理）*|您可以按照示例要求的格式使用 HTTP 代理 `[protocol://][username[:password]@]proxy.example.com[:port]`。<br>这将设置 [CURLOPT\_PROXY](https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html) cURL 选项。<br>可选 `protocol://` 前缀可用于指定替代代理协议（cURL 7.21.7 中添加了协议前缀支持）。如果未指定协议，代理将被视为 HTTP 代理。<br>默认情况下，将使用 1080 端口。<br>如果指定，代理将覆盖代理相关的环境变量，如 http\_proxy, HTTPS\_PROXY。如果未指定，代理将不会覆盖与代理相关的环境变量。输入的值“按原样”传递，不进行完整性检查。<br>您也可以输入 SOCKS 代理地址。如果您指定了错误的协议，则连接将失败并且该项目将变得不受支持。<br>*注意*： HTTP 代理仅支持简单身份验证。<br>用户宏可用于该字段。| |*Variables（变量）*|可能在场景步骤中使用的变量（URL、post 变量）。<br>它们具有以下格式：<br>**{macro1}**=value1<br>**{macro2}**=value2<br>**{macro3}**=regex:<正则表达式><br>示例：<br>{username}=Alexei<br>{password}=kj3h5kJ34bd<br>{hostid}=regex:hostid is (\[0-9\]+)<br>然后可以在步骤中以  {username}, {password} 和 {hostid} 的形式引用宏。Zabbix 会自动将它们替换为实际值。注意，变量 `regex:` 需要一步来获取正则表达式的值，因此提取的值只能应用于后面的步骤。<br>如果值部分以`regex:` 然后将其后面的部分视为搜索网页的正则表达式，如果找到，则将匹配项存储在变量中。必须至少存在一个子组，以便可以提取匹配值。<br>支持用户宏和  {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) 。<br>变量在用于查询字段或用于发布变量的表单数据时会自动进行 URL 编码，但在原始发布或直接在 URL 中使用时必须手动进行 URL 编码。| |*Headers（标头）*|执行请求时将发送的自定义 HTTP 标头。可以使用默认和自定义标头。<br>标头将使用默认设置分配，具体取决于从场景级别的下拉列表中选择的代理类型，并将应用于所有步骤，除非它们是在步骤级别自定义定义的。<br>**应该注意的是，在步骤级别定义标头会自动丢弃所有先前定义的标头，但通过从场景级别的下拉列表中选择“用户代理”来分配的默认标头除外。**<br>但是，即使是“User-Agent”默认标头也可以通过在步骤级别指定它来覆盖。<br>要在场景级别取消设置标头，标头应该在步骤级别上命名并且属性不设置值。<br>标头应使用与它们在 HTTP 协议中出现的相同语法列出，可选择使用 [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) 选项支持的一些附加功能。<br>例如：<br>Accept-Charset=utf-8<br>Accept-Language=en-US<br>Content-Type=application/xml; charset=utf-8<br>用户宏和  {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) 是支持的.| |*Enabled*|如果选中此框，则该场景处于活动状态，否则 - 禁用。|  请注意，在编辑现有场景时，表单中有两个额外的按钮可用：  |   |   | |---|---| |![](../../assets/en/manual/web_monitoring/buttons_clone.png)|根据现有场景的属性创建另一个场景。| |![](../../assets/en/manual/web_monitoring/buttons_clear.png)|删除场景的历史和趋势数据。这将使服务器在删除数据后立即执行场景。|  ::: notetip 如果 *HTTP 代理* 字段留空，使用 HTTP 代理的另一种方法是设置代理相关的环境变量。  对于 HTTP 检查 - 为 Zabbix server 用户设置 **http\_proxy** 环境变量。 例如，`http_proxy=http://proxy_ip:proxy_port`。  对于 HTTPS 检查 - 为 Zabbix server 用户设置 **HTTPS\_proxy** 环境变量。 例如，`HTTPS_PROXY=http://proxy_ip:proxy_port`。运行 shell 命令获得更多详细信息： *\# man curl*。 :::  **Steps（步骤）**选项卡可以配置 Web 场景步骤。要添加 Web 场景步骤，请单击 *Steps（步骤）* 块中的  *Add（添加）* 。  ![](../../assets/en/manual/config/scenario_b.png){width="600"}  ::: noteclassic 不得在 URL 中使用加密 [用户宏](/manual/config/macros/user_macros#configuration) 因为它们会被解析成 "\*\*\*\*\*\*"。 :::

en-us	#### Configuring certificate-based encryption for Zabbix agent  1\. Prepare files with top-level CA certificates, agent certificate (chain) and private key as described in [Configuring certificate on Zabbix server](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server). Edit parameters `TLSCAFile`, `TLSCertFile`, `TLSKeyFile` in agent configuration accordingly.  2\. For active checks edit `TLSConnect` parameter:      TLSConnect=cert  For passive checks edit `TLSAccept` parameter:      TLSAccept=cert  3\. Now you have a minimal certificate-based agent configuration. You may prefer to improve agent security by setting `TLSServerCertIssuer` and `TLSServerCertSubject` parameters. (see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject)).  4\. In final agent configuration file TLS parameters may look like:      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix proxy,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_agentd.crt     TLSKeyFile=/home/zabbix/zabbix_agentd.key  (Example assumes that host is monitored via proxy, hence proxy certificate Subject.)  5\. Configure encryption for this agent in Zabbix frontend:  -   Go to: *Configuration → Hosts* -   Select host and click on **Encryption** tab  In example below Issuer and Subject fields are filled in - see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) why and how to use these fields.  ![agent\_config.png](../../../assets/en/manual/encryption/agent_config.png)
zh-cn	 #### Zabbix agent配置基于证书的加密  1\.使用顶级CA证书，代理证书（链）和私钥准备文件，如在[Zabbix server配置证书](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server)中所述。编辑参数`TLSCAFile`，`TLSCertFile`，`TLSKeyFile`在agent配置相应。  2\. 对于主动模式检查编辑`TLSConnect`参数：      TLSConnect=cert  对于被动模式检查编辑`TLSAccept`参数：      TLSAccept=cert  3\.现在，您有一个基于证书的最小agent配置。您可能希望通过设置`TLSServerCertIssuer`和`TLSServerCertSubject`参数提高agent安全性。(请参阅[限制允许的证书发行者和主体](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject))。   4\. 在最终agent配置文件中，TLS参数可能如下所示：      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix proxy,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_agentd.crt     TLSKeyFile=/home/zabbix/zabbix_agentd.key  (例如，假设主机是通过proxy监视的，因此是proxy证书主体。)  5\. 在Zabbix前端为此agent配置加密：  -   前往: *Configuration → Hosts* -   选择主机然后点击**加密** 选项卡  在下面的示例中，发行者和主体字段填写 - 请参阅[限制允许的证书发行者和主体](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) 原因以及如何使用这些字段。  ![agent\_config.png](../../../assets/en/manual/encryption/agent_config.png)

en-us	#### Configuring certificate-based encryption for Zabbix proxy  1\. Prepare files with top-level CA certificates, proxy certificate (chain) and private key as described in [Configuring certificate on Zabbix server](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server). Edit parameters `TLSCAFile`, `TLSCertFile`, `TLSKeyFile` in proxy configuration accordingly.  2\. For active proxy edit `TLSConnect` parameter:      TLSConnect=cert  For passive proxy edit `TLSAccept` parameter:      TLSAccept=cert  3\. Now you have a minimal certificate-based proxy configuration. You may prefer to improve proxy security by setting `TLSServerCertIssuer` and `TLSServerCertSubject` parameters (see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject)).  4\. In final proxy configuration file TLS parameters may look like:      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix server,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_proxy.crt     TLSKeyFile=/home/zabbix/zabbix_proxy.key  5\. Configure encryption for this proxy in Zabbix frontend:  -   Go to: *Administration → Proxies* -   Select proxy and click on **Encryption** tab  In examples below Issuer and Subject fields are filled in - see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) why and how to use these fields.  For active proxy  ![proxy\_active\_cert.png](../../../assets/en/manual/encryption/proxy_active_cert.png)  For passive proxy  ![proxy\_passive\_cert.png](../../../assets/en/manual/encryption/proxy_passive_cert.png)
zh-cn	 #### Zabbix proxy配置基于证书的加密  1\.使用顶级CA证书，proxy证书（链）和私钥准备文件，如在[Zabbix server上配置证书](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server)中所述。编辑参数`TLSCAFile`，`TLSCertFile`， `TLSKeyFile`在proxy配置相应。 编辑参数`TLSCAFile`，`TLSCertFile`， `TLSKeyFile`在proxy配置相应。  2\. 对于主动模式proxy 编辑`TLSConnect`参数：      TLSConnect=cert  对于被动模式proxy编辑`TLSAccept`参数：      TLSAccept=cert  3\. 现在你有一个基于证书的最小proxy配置。您可能希望通过设置`TLSServerCertIssuer`和`TLSServerCertSubject`参数来提高proxy安全性 (请参阅 [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject))。  4\. 在最终的代理配置文件中，TLS参数可能看起来像:      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix server,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_proxy.crt     TLSKeyFile=/home/zabbix/zabbix_proxy.key  5\.  在Zabbix前端配置此proxy的加密：  -   转到：_管理→agent代理程序(proxies)_ -   选择代理，然后单击**加密**选项卡  在下面的例子中，发行人和主题字段被填充-请参阅 [限制允许的证书颁发者和主题](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) 为什么以及如何使用这些字段。  主动模式proxy  ![proxy\_active\_cert.png](../../../assets/en/manual/encryption/proxy_active_cert.png)  被动模式proxy  ![proxy\_passive\_cert.png](../../../assets/en/manual/encryption/proxy_passive_cert.png)

en-us	#### Configuring certificate on Zabbix server  1\. In order to verify peer certificates, Zabbix server must have access to file with their top-level self-signed root CA certificates. For example, if we expect certificates from two independent root CAs, we can put their certificates into file `/home/zabbix/zabbix_ca_file` like this:      Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA                 ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE                 ...     -----BEGIN CERTIFICATE-----     MIID2jCCAsKgAwIBAgIBATANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB     ....     9wEzdN8uTrqoyU78gi12npLj08LegRKjb5hFTVmO     -----END CERTIFICATE-----     Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA                 ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ....             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE                 ....            -----BEGIN CERTIFICATE-----     MIID3DCCAsSgAwIBAgIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQB     ...     vdGNYoSfvu41GQAR5Vj5FnRJRzv5XQOZ3B6894GY1zY=     -----END CERTIFICATE-----  2\. Put Zabbix server certificate chain into file, for example, `/home/zabbix/zabbix_server.crt`:      Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA             ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Zabbix server             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                     ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Digital Signature, Key Encipherment                 X509v3 Basic Constraints:                      CA:FALSE                 ...     -----BEGIN CERTIFICATE-----     MIIECDCCAvCgAwIBAgIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixk     ...     h02u1GHiy46GI+xfR3LsPwFKlkTaaLaL/6aaoQ==     -----END CERTIFICATE-----     Certificate:         Data:             Version: 3 (0x2)             Serial Number: 2 (0x2)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA             ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE, pathlen:0             ...     -----BEGIN CERTIFICATE-----     MIID4TCCAsmgAwIBAgIBAjANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB     ...     dyCeWnvL7u5sd6ffo8iRny0QzbHKmQt/wUtcVIvWXdMIFJM0Hw==     -----END CERTIFICATE-----  Here the first is Zabbix server certificate, followed by intermediate CA certificate.  3\. Put Zabbix server private key into file, for example, `/home/zabbix/zabbix_server.key`:      -----BEGIN PRIVATE KEY-----     MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAAoIBAQC9tIXIJoVnNXDl     ...     IJLkhbybBYEf47MLhffWa7XvZTY=     -----END PRIVATE KEY-----  4\. Edit TLS parameters in Zabbix server configuration file like this:      TLSCAFile=/home/zabbix/zabbix_ca_file     TLSCertFile=/home/zabbix/zabbix_server.crt     TLSKeyFile=/home/zabbix/zabbix_server.key
zh-cn	 #### 在Zabbix server上配置证书  1\. 为了验证对等证书，Zabbix server必须具有使用其顶级自签名根CA证书的文件访问权限。例如，如果我们期望来自两个独立根CA的证书，我们可以将其证书放入文件中 `/home/zabbix/zabbix_ca_file`：      Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA                 ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE                 ...     -----BEGIN CERTIFICATE-----     MIID2jCCAsKgAwIBAgIBATANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB     ....     9wEzdN8uTrqoyU78gi12npLj08LegRKjb5hFTVmO     -----END CERTIFICATE-----     Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA                 ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root2 CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ....             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE                 ....            -----BEGIN CERTIFICATE-----     MIID3DCCAsSgAwIBAgIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQB     ...     vdGNYoSfvu41GQAR5Vj5FnRJRzv5XQOZ3B6894GY1zY=     -----END CERTIFICATE-----  2\. 将Zabbix服务器证书链放入文件中，例如`/home/zabbix/zabbix_server.crt`:      Certificate:         Data:             Version: 3 (0x2)             Serial Number: 1 (0x1)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA             ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Zabbix server             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                     ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Digital Signature, Key Encipherment                 X509v3 Basic Constraints:                      CA:FALSE                 ...     -----BEGIN CERTIFICATE-----     MIIECDCCAvCgAwIBAgIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixk     ...     h02u1GHiy46GI+xfR3LsPwFKlkTaaLaL/6aaoQ==     -----END CERTIFICATE-----     Certificate:         Data:             Version: 3 (0x2)             Serial Number: 2 (0x2)         Signature Algorithm: sha1WithRSAEncryption             Issuer: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Root1 CA             ...             Subject: DC=com, DC=zabbix, O=Zabbix SIA, OU=Development group, CN=Signing CA             Subject Public Key Info:                 Public Key Algorithm: rsaEncryption                     Public-Key: (2048 bit)                 ...             X509v3 extensions:                 X509v3 Key Usage: critical                     Certificate Sign, CRL Sign                 X509v3 Basic Constraints: critical                     CA:TRUE, pathlen:0             ...     -----BEGIN CERTIFICATE-----     MIID4TCCAsmgAwIBAgIBAjANBgkqhkiG9w0BAQUFADB+MRMwEQYKCZImiZPyLGQB     ...     dyCeWnvL7u5sd6ffo8iRny0QzbHKmQt/wUtcVIvWXdMIFJM0Hw==     -----END CERTIFICATE-----  先放入Zabbix server证书，随后是中间CA的证书。  3\. 将Zabbix server私钥放入文件中，例如`/home/zabbix/zabbix_server.key`：      -----BEGIN PRIVATE KEY-----     MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAAoIBAQC9tIXIJoVnNXDl     ...     IJLkhbybBYEf47MLhffWa7XvZTY=     -----END PRIVATE KEY-----  4\. 在Zabbix server配置文件中编辑TLS参数，如下所示：      TLSCAFile=/home/zabbix/zabbix_ca_file     TLSCertFile=/home/zabbix/zabbix_server.crt     TLSKeyFile=/home/zabbix/zabbix_server.key

en-us	#### Configuring custom graphs  To create a custom graph, do the following:  -   Go to *Configuration → Hosts (or Templates)* -   Click on *Graphs* in the row next to the desired host or template -   In the Graphs screen click on *Create graph* -   Edit graph attributes  ![](../../../../../assets/en/manual/config/visualization/graph2.png){width="600"}  All mandatory input fields are marked with a red asterisk.  Graph attributes:  |Parameter|<|Description| |---------|-|-----------| |*Name*|<|Unique graph name.<br>Expression [macros](/manual/appendix/macros/supported_by_location) are supported in this field, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).<br>{HOST.HOST<1-9>} macros are supported for the use within this macro, referencing the first, second, third, etc. host in the graph, for example `{?avg(/{HOST.HOST2}/key,1h)}`. Note that referencing the first host with this macro is redundant, as the first host can be referenced implicitly, for example `{?avg(//key,1h)}`.| |*Width*|<|Graph width in pixels (for preview and pie/exploded graphs only).| |*Height*|<|Graph height in pixels.| |*Graph type*|<|Graph type:<br>**Normal** - normal graph, values displayed as lines<br>**Stacked** - stacked graph, filled areas displayed<br>**Pie** - pie graph<br>**Exploded** - "exploded" pie graph, portions displayed as "cut out" of the pie| |*Show legend*|<|Checking this box will set to display the graph legend.| |*Show working time*|<|If selected, non-working hours will be shown with a gray background. Not available for pie and exploded pie graphs.| |*Show triggers*|<|If selected, simple triggers will be displayed as lines with black dashes over trigger severity color. Not available for pie and exploded pie graphs.| |*Percentile line (left)*|<|Display percentile for left Y-axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 percent of the values fall under. Displayed as a bright green line. Only available for normal graphs.| |*Percentile line (right)*|<|Display percentile for right Y-axis. If, for example, 95% percentile is set, then the percentile line will be at the level where 95 percent of the values fall under. Displayed as a bright red line. Only available for normal graphs.| |*Y axis MIN value*|<|Minimum value of Y-axis:<br>**Calculated** - Y axis minimum value will be automatically calculated<br>**Fixed** - fixed minimum value for Y-axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the minimum value| |*Y axis MAX value*|<|Maximum value of Y-axis:<br>**Calculated** - Y axis maximum value will be automatically calculated<br>**Fixed** - fixed maximum value for Y-axis. Not available for pie and exploded pie graphs.<br>**Item** - last value of the selected item will be the maximum value| |*3D view*|<|Enable 3D style. For pie and exploded pie graphs only.| |*Items*|<|Items, data of which are to be displayed in this graph. Click on *Add* to select items. You can also select various displaying options (function, draw style, left/right axis display, color).| |<|*Sort order (0→100)*|Draw order. 0 will be processed first. Can be used to draw lines or regions behind (or in front of) another.<br>You can drag and drop items by the arrow at the beginning of a line to set the sort order or which item is displayed in front of the other.| |^|*Name*|Name of the selected item is displayed as a link. Clicking on the link opens the list of other available items.| |^|*Type*|Type (only available for pie and exploded pie graphs):<br>**Simple** - the value of the item is represented proportionally on the pie<br>**Graph sum** - the value of the item represents the whole pie<br>Note that coloring of the "graph sum" item will only be visible to the extent that it is not taken up by "proportional" items.| |^|*Function*|Select what values will be displayed when more than one value exists per vertical graph pixel for an item:<br>**all** - display all possible values (minimum, maximum, average) in the graph. Note that for shorter periods this setting has no effect; only for longer periods, when data congestion in a vertical graph pixel increases, 'all' starts displaying minimum, maximum, and average values. This function is only available for *Normal* graph type. See also: Generating graphs [from history/trends](/manual/config/visualization/graphs/simple#generating_from_historytrends).<br>**avg** - display the average values<br>**last** - display the latest values. This function is only available if either *Pie/Exploded pie* is selected as graph type.<br>**max** - display the maximum values<br>**min** - display the minimum values| |^|*Draw style*|Select the draw style (only available for normal graphs; for stacked graphs filled region is always used) to apply to the item data - *Line*, *Bold line*, *Filled region*, *Dot*, *Dashed line*, *Gradient line*.| |^|*Y axis side*|Select the Y axis side to show the item data - *Left*, *Right*.| |^|*Color*|Select the color to apply to the item data.|
zh-cn	#### 配置自定义图表  要创建自定义图表，请执行以下操作：  - 转到*配置 → 主机（或模板）* - 单击所需主机或模板旁边行中的 *图表* - 在图表屏幕中点击*创建图表* - 编辑图表属性  ![](../../../../../assets/en/manual/config/visualization/graph2.png){width="600"}  所有必填字段都标有红色星号。  图表属性：  |参数|<|说明| |---------|-|------------| |*名称*|<|唯一的图形名称。<br>此字段支持表达式 [宏](/manual/appendix/macros/supported_by_location)，但仅限于 `avg`、`last`、`min` 和 ` max` 函数，以时间为参数（例如，`{?avg(/host/key,1h)}`）。<br>支持在此宏中使用{HOST.HOST<1-9>} 宏，引用图中的第一个、第二个、第三个等主机，例如`{?avg(/{HOST.HOST2}/key,1h)}`。请注意，使用此宏引用第一个主机是多余的，因为可以隐式引用第一个主机，例如 `{?avg(//key,1h)}`。| |*宽度*|<|以像素为单位的图形宽度（仅用于预览和饼图/分解图）。| |*高度*|<|以像素为单位的图形高度。| |*图表类型*|<|图表类型：<br>**正常** - 正常图表，值显示为线条<br>**堆叠** - 堆叠图表，显示填充区域<br>**饼图** - 饼图<br>**展开** - “展开”饼图，部分显示为饼图的“切出”| |*显示图例*|<|选中此框将设置为显示图例。| |*显示工作时间*|<|如果选择，非工作时间将以灰色背景显示。不适用于饼图和分解饼图。| |*显示触发器*|<|如果选中，简单触发器将显示为带有黑色短划线的线条，上面有触发器严重性颜色。不适用于饼图和分解饼图。| |*百分位线（左）*|<|显示左 Y 轴的百分位。例如，如果设置了 95% 的百分位，则百分位线将位于 95% 的值所在的水平。显示为亮绿色线。仅适用于普通图。| |*百分位线（右）*|<|显示右侧 Y 轴的百分位。例如，如果设置了 95% 的百分位，则百分位线将位于 95% 的值所在的水平。显示为一条鲜红的线。仅适用于普通图。| |*Y 轴最小值*|<|Y 轴最小值：<br>**计算** - Y 轴最小值将自动计算<br>**固定** - Y 轴固定最小值.不适用于饼图和分解饼图。<br>**监控项** - 所选项目的最后一个值将是最小值| |*Y 轴最大值*|<|Y 轴最大值：<br>**计算** - Y 轴最大值将自动计算<br>**固定** - Y 轴最大值固定.不适用于饼图和分解饼图。<br>**监控项** - 所选项目的最后一个值将是最大值| |*3D 视图*|<|启用 3D 样式。仅适用于饼图和分解饼图。| |*监控项*|<|要在此图中显示的数据的监控项。单击 *增加* 以选择项目。您还可以选择各种显示选项（功能、绘制样式、左/右轴显示、颜色）。| |<|*排序顺序（0→100）*|绘制顺序。 0 将首先被处理。可用于在另一个后面（或前面）绘制线条或区域。<br>您可以通过线条开头的箭头拖放项目以设置排序顺序或哪个项目显示在另一个前面.| |^|*名称*|所选项目的名称显示为链接。单击该链接可打开其他可用项目的列表。| |^|*类型*|类型（仅适用于饼图和分解饼图）：<br>**简单** - 项目的值在饼图中按比例表示<br>**图表求和** -监控项值代表整个饼图<br>请注意，“图形总和”项目的着色仅在“比例”项目不占用的范围内可见。| |^|*功能*|选择当一个项目的每个垂直图形像素存在多个值时将显示哪些值：<br>**all** - 在图形中显示所有可能的值（最小值、最大值、平均值） .请注意，对于较短的时间段，此设置无效；仅在较长时期内，当垂直图像素中的数据拥塞增加时，“全部”开始显示最小值、最大值和平均值。此功能仅适用于 *Normal* 图形类型。另请参阅：生成图表 [从历史/趋势](/manual/config/visualization/graphs/simple#generating_from_historytrends)。<br>**avg** - 显示平均值<br>**last** - 显示最新值。此功能仅适用于*饼图/爆炸的饼图*作为图形类型。** max **  - 显示最大值<br> ** min **  - 显示最小值| |^|*绘制样式*|选择绘制样式（仅适用于普通图；堆叠图始终使用填充区域）应用于项目数据 - *线条*、*粗线*、*填充区域*、*点*，*虚线*，*渐变线*。| |^|*Y轴侧*|选择Y轴侧显示项目数据-*左*，*右*。| |^|*颜色*|选择要应用到项目数据的颜色。|

en-us	#### Configuring JMX interfaces and items in Zabbix frontend  With Java gateway running, server knowing where to find it and a Java application started with support for remote JMX monitoring, it is time to configure the interfaces and items in Zabbix GUI.
zh-cn	#### 在Zabbix web管理页面上配置JMX接口和监控项  Java网关在运行时，服务器会主动连接它，Java应用程序启用了远程JMX监视，现在可以在Zabbix GUI中配置接口和监控项了。

en-us	##### Configuring JMX interface  You begin by creating a JMX-type interface on the host of interest.\ ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_interface.png){width="600"}  All mandatory input fields are marked with a red asterisk.
zh-cn	##### 配置JMX接口  首先在相关主机上创建一个JMX类型的接口。\ ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_interface.png){width="600"}  标有红色星号的为必填项。

en-us	#### Configuring low-level discovery rules  See the [low-level discovery](/manual/discovery/low_level_discovery) section of the manual.
zh-cn	 #### 配置低级别自动发现规则  请参阅手册的[低级别自动发现](/manual/discovery/low_level_discovery)部分。

en-us	### Configuring low-level discovery  We will illustrate low-level discovery based on an example of file system discovery.  To configure the discovery, do the following:  -   Go to: *Configuration* → *Templates* or *Hosts* -   Click on *Discovery* in the row of an appropriate template/host  ![](../../../assets/en/manual/discovery/low_level_discovery/fs_templates.png)  -   Click on *Create discovery rule* in the upper right corner of the     screen -   Fill in the discovery rule form with the required details
zh-cn	### 配置底层自动发现  下面是一个文件系统自动发现的例子。  要配置自动发现, 需完成下列操作:  -   找到: *配置* → *模板* 或 *主机* -   在对应模板/主机中点击 *自动发现*   ![](../../../assets/en/manual/discovery/low_level_discovery/fs_templates.png)  -   在屏幕右上角点击 *创建自动发现规则* -   在发现规则表格中填入所需信息

en-us	#### Configuring nested templates  To link templates, you need to take an existing template or a new one, and then:  -   Open the [template configuration form](/manual/config/templates/template#creating-a-template) -   Find the *Templates* field -   Click *Select* to open the *Templates* popup window -   In the popup window, choose required templates, then click *Select* to add the templates to the list -   Click *Add* or *Update* in the template configuration form  Thus, all entities of the parent template, as well as all entities of linked templates (such as items, triggers, graphs, etc.) will now appear in the template configuration, except for linked template dashboards, which will, nevertheless, be inherited by hosts.  To unlink any of the linked templates, in the same form use the *Unlink* or *Unlink and clear* buttons and click *Update*.  Choosing the *Unlink* option will simply remove the association with the linked template, while not removing all its entities (items, triggers, graphs, etc.).  Choosing the *Unlink and clear* option will remove both the association with the linked template and all its entities (items, triggers, graphs, etc.).
zh-cn	#### 配置嵌套模板  要链接模板，您需要使用现有模板或新模板，然后：  -   打开[模板配置表单](/manual/config/templates/template#creating-a-template) -   找到*模板*字段 -   点击*选择*打开*模板*弹出窗口 -   在弹出窗口中，选择所需的模板，然后单击*选择*将模板添加到列表中 -   点击模板配置表单中的*添加*或*更新*  因此，父模板的所有实体以及链接模板的所有实体（例如监控项、触发器、图形等）现在都将出现在模板配置中，但链接模板仪表板除外，它仍然会被主机继承。  要取消链接任何链接的模板，请在同一表格中使用 *取消链接* 或 *取消链接并清理* 按钮，然后单击 *更新*。  选择 *取消链接* 选项只会删除与链接模板的关联，而不会删除其所有实体（监控项、触发器、图表等）。  选择 *取消链接并清理* 选项将删除与链接模板及其所有实体（监控项、触发器、图形等）的关联。

en-us	##### Configuring Perl trap receiver  Requirements: Perl, Net-SNMP compiled with --enable-embedded-perl (done by default since Net-SNMP 5.4)  A Perl trap receiver (look for misc/snmptrap/zabbix\_trap\_receiver.pl) can be used to pass traps to Zabbix server directly from snmptrapd. To configure it:  -   add the Perl script to the snmptrapd configuration file     (snmptrapd.conf), e.g.:      perl do "[FULL PATH TO PERL RECEIVER SCRIPT]";  -   configure the receiver, e.g:      $SNMPTrapperFile = '[TRAP FILE]';     $DateTimeFormat = '[DATE TIME FORMAT]';  ::: notetip If the script name is not quoted, snmptrapd will refuse to start up with messages, similar to these:      Regexp modifiers "/l" and "/a" are mutually exclusive at (eval 2) line 1, at end of line     Regexp modifier "/l" may not appear twice at (eval 2) line 1, at end of line  :::
zh-cn	##### 配置 Perl trap 接收器  要求：Perl，使用 --enable-embedded-perl 编译的 Net-SNMP（自 Net-SNMP 5.4 起默认完成）  Perl 陷阱接收器（查找 misc/snmptrap/zabbix\_trap\_receiver.pl）可用于将陷阱直接从 snmptrapd 传递到 Zabbix 服务器。 配置它：  - · 将 Perl 脚本添加到 snmptrapd 配置文件（snmptrapd.conf）中，例如：    · perl do "[FULL PATH TO PERL RECEIVER SCRIPT]";  - · 配置接收器，例如：   · $SNMPTrapperFile = '[TRAP FILE]';  · $DateTimeFormat = '[DATE TIME FORMAT]';  ::: notetip 如果没有引用脚本名称，snmptrapd 将拒绝启动并显示消息，类似于这些：   · Regexp modifiers "/l" and "/a" are mutually exclusive at (eval 2) line 1, at end of line  · Regexp modifier "/l" may not appear twice at (eval 2) line 1, at end of line  ::::

en-us	#### Configuring PSK for server - active proxy communication (example)  On the proxy, write the PSK value into a file, for example, `/home/zabbix/zabbix_proxy.psk`. The file must contain PSK in the first text string, for example:      e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9  Set access rights to PSK file - it must be readable only by Zabbix user.  Edit TLS parameters in proxy configuration file `zabbix_proxy.conf`, for example, set:      TLSConnect=psk     TLSPSKFile=/home/zabbix/zabbix_proxy.psk     TLSPSKIdentity=PSK 002  The proxy will connect to server using PSK. PSK identity will be "PSK 002".  (To minimize downtime see how to change connection type in [Connection encryption management](/manual/encryption#connection_encryption_management)).  Configure PSK for this proxy in Zabbix frontend. Go to *Administration→Proxies*, select the proxy, go to "Encryption" tab. In "Connections from proxy" mark `PSK`. Paste into "PSK identity" field "PSK 002" and "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" into "PSK" field. Click "Update".  Restart proxy. It will start using PSK-based encrypted connections to server. Check server and proxy logfiles for error messages.  For a passive proxy the procedure is very similar. The only difference - set `TLSAccept=psk` in proxy configuration file and set "Connections to proxy" in Zabbix frontend to `PSK`.
zh-cn	 #### 为服务器配置 PSK - 活动代理通信（示例）  在代理上，将 PSK 值写入文件，例如, `/home/zabbix/zabbix_proxy.psk`。该文件必须在第一个文本字符串中包含 PSK，例如：  ```   e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9 ``` 设置PSK文件的访问权限 - 它必须只能由Zabbix用户读取。   在代理配置文件 `zabbix_proxy.conf`中编辑TLS参数, 例如，设置: ```   TLSConnect=psk   TLSPSKFile=/home/zabbix/zabbix_proxy.psk   TLSPSKIdentity=PSK 002 ``` 代理将使用 PSK 连接到服务器。PSK 标识将是 "PSK 002"。  (为最大限度地减少停机时间，请参阅 [连接加密管理](/manual/encryption#connection_encryption_management))。  在 Zabbix 前端中为此代理配置 PSK。 转到*管理→代理*, 选择代理, 转到 "加密" 选项卡。 在"来自代理的连接" 中，标记`PSK`。将"PSK 002"粘贴到"PSK 标识"字段中，将"e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" 粘贴到"PSK" 字段。 点击 "更新"。  重新启动代理。它将开始使用基于 PSK 的加密连接到服务器。检查服务器和代理日志文件中是否有错误消息。  对于被动代理，该过程非常相似。唯一的区别是 - 在代理配置文件中设置 `TLSAccept=psk`，并将Zabbix前端中的 "连接到 代理" 设置为 `PSK`。

en-us	#### Configuring server for use with Java gateway  With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead.      JavaGateway=192.168.3.14     JavaGatewayPort=10052  By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers.      StartJavaPollers=5  Do not forget to restart server or proxy, once you are done with configuring them.
zh-cn	#### 配置 Zabbix Server 关联 Java 网关  当Java网关启动并运行后，你需要告诉Zabbix server去哪里找Zabbix Java网关。通过在[server 配置文件](/manual/appendix/config/zabbix_server)中指定JavaGateway和JavaGatewayPort来完成这个操作。如果运行JMX应用程序的主机是由Zabbix代理监控的，则可以在[proxy 配置文件](/manual/appendix/config/zabbix_server)中指定连接参数。      JavaGateway=192.168.3.14     JavaGatewayPort=10052  默认情况下，server不会启动任何与JMX监控相关的进程。如果你希望用到它，则必须指定Java pollers的数量。此操作与配置常规 pollers 和 trappers数量一样。      StartJavaPollers=5  配置完server或proxy后，一定不要忘记重启server或proxy。

en-us	#### Configuring server for use with Java gateway  With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead.      JavaGateway=192.168.3.14     JavaGatewayPort=10052  By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers.      StartJavaPollers=5  Do not forget to restart server or proxy, once you are done with configuring them.
zh-cn	#### 配置 Zabbix Server 关联 Java 网关  当Java网关启动并运行后，你需要告诉Zabbix server去哪里找Zabbix Java网关。通过在[server 配置文件](/manual/appendix/config/zabbix_server)中指定JavaGateway和JavaGatewayPort来完成这个操作。如果运行JMX应用程序的主机是由Zabbix代理监控的，则可以在[proxy 配置文件](/manual/appendix/config/zabbix_server)中指定连接参数。      JavaGateway=192.168.3.14     JavaGatewayPort=10052  默认情况下，server不会启动任何与JMX监控相关的进程。如果你希望用到它，则必须指定Java pollers的数量。此操作与配置常规 pollers 和 trappers数量一样。      StartJavaPollers=5  配置完server或proxy后，一定不要忘记重启server或proxy。

en-us	#### Configuring server for use with Java gateway  With Java gateway up and running, you have to tell Zabbix server where to find Zabbix Java gateway. This is done by specifying JavaGateway and JavaGatewayPort parameters in the [server configuration file](/manual/appendix/config/zabbix_server). If the host on which JMX application is running is monitored by Zabbix proxy, then you specify the connection parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) instead.      JavaGateway=192.168.3.14     JavaGatewayPort=10052  By default, server does not start any processes related to JMX monitoring. If you wish to use it, however, you have to specify the number of pre-forked instances of Java pollers. You do this in the same way you specify regular pollers and trappers.      StartJavaPollers=5  Do not forget to restart server or proxy, once you are done with configuring them.
zh-cn	#### 配置Zabbix Server 关联Java网关  当Java网关启动并运行后，你需要告诉Zabbix server去哪里找Zabbix Java网关。通过在[server 配置文件](/manual/appendix/config/zabbix_server)中指定JavaGateway和JavaGatewayPort来完成这个操作。如果运行JMX应用程序的主机是由Zabbix代理监控的，则可以在[proxy 配置文件](/manual/appendix/config/zabbix_server)中指定连接参数。      JavaGateway=192.168.3.14     JavaGatewayPort=10052  默认情况下，server不会启动任何与JMX监控相关的进程。如果你希望用到它，则必须指定Java pollers的数量。此操作与配置常规 pollers 和 trappers数量一样。      StartJavaPollers=5  配置完server或proxy后，一定不要忘记重启server或proxy。

en-us	#### Configuring SNMP monitoring  To start monitoring a device through SNMP, the following steps have to be performed:
zh-cn	#### 配置SNMP监控  要通过SNMP开始监控设备，必须执行以下步骤：

en-us	#### Configuring SNMP traps  Configuring the following fields in the frontend is specific for this item type:  -   Your host must have an SNMP interface  In *Configuration → Hosts*, in the **Host interface** field set an SNMP interface with the correct IP or DNS address. The address from each received trap is compared to the IP and DNS addresses of all SNMP interfaces to find the corresponding hosts.  -   Configure the item  In the **Key** field use one of the SNMP trap keys:  |Key|<|<| |--|--|------| |Description|Return value|Comments| |**snmptrap**\[regexp\]|<|<| |Catches all SNMP traps that match the [regular expression](/manual/regular_expressions) specified in **regexp**. If regexp is unspecified, catches any trap.|SNMP trap|This item can be set only for SNMP interfaces.<br>User macros and global regular expressions are supported in the parameter of this item key.| |**snmptrap.fallback**|<|<| |Catches all SNMP traps that were not caught by any of the snmptrap\[\] items for that interface.|SNMP trap|This item can be set only for SNMP interfaces.|  ::: noteclassic Multiline regular expression matching is not supported at this time. :::  Set the **Type of information** to 'Log' for the timestamps to be parsed. Note that other formats such as 'Numeric' are also acceptable but might require a custom trap handler.  ::: notetip For SNMP trap monitoring to work, it must first be set up  correctly (see below). :::
zh-cn	#### - 配置 SNMP 陷阱  在前端配置以下字段是特定于该监控项类型：  - 您的主机必须有 SNMP 接口  在 *配置 → 主机* 中，在 **主机接口** 字段中填入正确的 IP 或 DNS 地址设置 SNMP 接口。将每个接收到的陷阱的地址与所有 SNMP 接口的 IP 和 DNS 地址进行比较，以找到相应的主机。  - 配置监控项  在 **键值** 字段中，使用 SNMP 陷阱key之一：  |键|<|<| |---|-|-| |描述|返回值|注释| |**snmptrap**\[regexp\]|<|<| |捕获与 **regexp** 中指定的 [正则表达式](/manual/regular_expressions) 匹配的所有 SNMP 陷阱。如果未指定 regexp，则捕获任何陷阱。|SNMP 陷阱|此监控项只能为 SNMP 接口设置。<br>此监控项键的参数支持用户宏和全局正则表达式。| |snmptrap.fallback|<|<| |捕获所有未被该接口的任何 snmptrap\[\] 监控项捕获的 SNMP 陷阱。|SNMP 陷阱|只能为 SNMP 接口设置此监控项。|  ::: noteclassic 此处不支持多行正则表达式匹配。 :::  将 **信息类型** 设置为“Log”以获取要解析的时间戳。 请注意，其他格式（例如“数字”）也是可以接受的，但可能需要自定义陷阱处理程序。  ::: notetip 要使 SNMP 陷阱监控工作，它必须首先正确设置（见下文）。 :::

en-us	##### Configuring SNMPTT  At first, snmptrapd should be configured to use SNMPTT.  ::: notetip For the best performance, SNMPTT should be configured as a daemon using **snmptthandler-embedded** to pass the traps to it. See instructions for [configuring SNMPTT](http://snmptt.sourceforge.net/docs/snmptt.shtml). :::  When SNMPTT is configured to receive the traps, configure `snmptt.ini`:  1.  enable the use of the Perl module from the NET-SNMP package:      net\_snmp\_perl\_enable = 1  2.  log traps to the trap file which will be read by Zabbix:      log_enable = 1     log_file = [TRAP FILE]      3.  set the date-time format:      date_time_format = %H:%M:%S %Y/%m/%d = [DATE TIME FORMAT]  ::: notewarning The "net-snmp-perl" package has been removed in RHEL 8.0-8.2;  re-added in RHEL 8.3. For more information, see the [known issues](/manual/installation/known_issues#snmp_traps). :::  Now format the traps for Zabbix to recognize them (edit snmptt.conf):  1.  Each FORMAT statement should start with "ZBXTRAP \[address\]", where     \[address\] will be compared to IP and DNS addresses of SNMP     interfaces on Zabbix. E.g.:      EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal     FORMAT ZBXTRAP $aA Device reinitialized (coldStart)  2.  See more about SNMP trap format below.  ::: noteimportant Do not use unknown traps - Zabbix will not be able to recognize them.  Unknown traps can be handled by defining a general event in snmptt.conf:\ EVENT general .\* "General event" Normal :::
zh-cn	##### 配置 SNMPTT  首先，snmptrapd 应该配置为使用 SNMPTT。  ::: notetip 为获得最佳性能，SNMPTT 应配置使用 **snmptthandler-embedded** 将陷阱传递给它的守护进程。请参阅 [配置 SNMPTT](http://snmptt.sourceforge.net/docs/snmptt.shtml) 的说明。 ::::  当 SNMPTT 配置为接收陷阱时，配置 `snmptt.ini`：  1. 启用 NET-SNMP 包中的 Perl 模块：\    net\_snmp\_perl\_enable = 1 2. 将陷阱记录到 Zabbix 将读取的陷阱文件中：:\    log\_enable = 1\    log\_file = \[TRAP FILE\] 3. 设置日期时间格式：\  · date\_time\_format = %H:%M:%S %Y/%m/%d = \[DATE TIME FORMAT\]  ::: notewarning “net-snmp-perl”包已在RHEL 8.0-8.2被移除；但在 RHEL 8.3 中重新添加。有关详细信息，请参阅 [已知问题](/manual/installation/known_issues#snmp_traps)。 :::  现在格式化陷阱以便 Zabbix 识别它们（编辑 snmptt.conf）：  1.  每个FORMAT格式化语句应以“ZBXTRAP \[address\]”开头，其中\[address\] 将与 Zabbix 上 SNMP 接口的 IP 和 DNS 地址进行比较。例如： \    EVENT coldStart .1.3.6.1.6.3.1.1.5.1 "Status Events" Normal\    FORMAT ZBXTRAP $aA Device reinitialized (coldStart) 2.  在下面查看更多关于 SNMP 陷阱格式的信息。  ::: noteimportant 不要使用未知的陷阱 - Zabbix 将无法识别它们。 可以通过在 snmptt.conf 中定义一般事件来处理未知陷阱：\ EVENT general .\* "General event" Normal :::

en-us	#### Configuring steps  ![](../../assets/en/manual/config/scenario_step.png){width="600"}  Step parameters:  |Parameter|Description| |--|--------| |*Name*|Unique step name.| |*URL*|URL to connect to and retrieve data. For example:<br>https://www.example.com<br>http://www.example.com/download<br>Domain names can be specified in Unicode characters. They are automatically punycode-converted to ASCII when executing the web scenario step.<br>The *Parse* button can be used to separate optional query fields (like ?name=Admin&password=mypassword) from the URL, moving the attributes and values into *Query fields* for automatic URL-encoding.<br>Variables can be used in the URL, using the {macro} syntax. Variables can be URL-encoded manually using a {{macro}.urlencode()} syntax.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.<br>Limited to 2048 characters.| |*Query fields*|HTTP GET variables for the URL.<br>Specified as attribute and value pairs.<br>Values are URL-encoded automatically. Values from scenario variables, user macros or {HOST.\*} macros are resolved and then URL-encoded automatically. Using a {{macro}.urlencode()} syntax will double URL-encode them.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Post*|HTTP POST variables.<br>In **Form data** mode, specified as attribute and value pairs.<br>Values are URL-encoded automatically. Values from scenario variables, user macros or {HOST.\*} macros are resolved and then URL-encoded automatically.<br>In **Raw data** mode, attributes/values are displayed on a single line and concatenated with a **&** symbol.<br>Raw values can be URL-encoded/decoded manually using a {{macro}.urlencode()} or {{macro}.urldecode()} syntax.<br>For example: id=2345&userid={user}<br>If {user} is defined as a variable of the web scenario, it will be replaced by its value when the step is executed. If you wish to URL-encode the variable, substitute {user} with {{user}.urlencode()}.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Variables*|Step-level variables that may be used for GET and POST functions.<br>Specified as attribute and value pairs.<br>Step-level variables override scenario-level variables or variables from the previous step. However, the value of a step-level variable only affects the step after (and not the current step).<br>They have the following format:<br>**{macro}**=value<br>**{macro}**=regex:<regular expression><br>For more information see variable description on the [scenario](web_monitoring#configuring_a_web_scenario) level.<br>Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.| |*Headers*|Custom HTTP headers that will be sent when performing a request.<br>Specified as attribute and value pairs.<br>A header defined on a step level will be used for that particular step.<br>**It should be noted that defining the header on a step level automatically discards all the previously defined headers, except for a default header that is assigned by selecting the 'User-Agent' from a drop-down list on a scenario level.**<br>However, even the 'User-Agent' default header can be overridden by specifying it on a step level.<br>For example, assigning the name to a header, but setting no value will unset the default header on a scenario level.<br>User macros and {HOST.\*} macros are supported.<br>This sets the [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL option.<br>Specifying custom headers is supported *starting with Zabbix 2.4*.| |*Follow redirects*|Mark the checkbox to follow HTTP redirects.<br>This sets the [CURLOPT\_FOLLOWLOCATION](http://curl.haxx.se/libcurl/c/CURLOPT_FOLLOWLOCATION.html) cURL option.| |*Retrieve mode*|Select the retrieve mode:<br>**Body** - retrieve only body from the HTTP response<br>**Headers** - retrieve only headers from the HTTP response<br>**Body and headers** - retrieve body and headers from the HTTP response| |*Timeout*|Zabbix will not spend more than the set amount of time on processing the URL (from one second to maximum of 1 hour). Actually this parameter defines the maximum time for making connection to the URL and maximum time for performing an HTTP request. Therefore, Zabbix will not spend more than **2 x Timeout** seconds on the step.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 1h. [User macros](/manual/config/macros/user_macros) are supported.| |*Required string*|Required regular expression pattern.<br>Unless retrieved content (HTML) matches the required pattern the step will fail. If empty, no check on required string is performed.<br>For example:<br>Homepage of Zabbix<br>Welcome.\*admin<br>*Note*: Referencing [regular expressions](regular_expressions) created in the Zabbix frontend is not supported in this field.<br>User macros and {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) are supported.| |*Required status codes*|List of expected HTTP status codes. If Zabbix gets a code which is not in the list, the step will fail.<br>If empty, no check on status codes is performed.<br>For example: 200,201,210-299<br>User macros are supported.|  ::: noteclassic Any changes in web scenario steps will only be saved when the whole scenario is saved. :::  See also a [real-life example](/manual/web_monitoring/example) of how web monitoring steps can be configured.
zh-cn	#### 配置步骤  ![](../../assets/en/manual/config/scenario_step.png){width="600"}  步骤参数：  |参数|描述| |---------|-----------| |*Name*|唯一的步骤名称。| |*URL*|用于连接和检索数据的 URL。例如：<br>https://www.example.com<br>http://www.example.com/download<br>域名可以用 Unicode 字符指定。 在执行 Web 场景步骤时，它们会自动转换为 ASCII 码。<br>*Parse* 按钮​​可用于将可选查询字段 （如 ?name=Admin&password=mypassword)）与 URL 分开，将属性和值移动到 *查询字段* 中以进行自动 URL 编码。<br>变量可以在 URL 中使用，使用 {macro} 语法。可以使用 {{macro}.urlencode()} 语法手动对变量进行 URL 编码。<br>支持用户宏和 {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) <br>限制为 2048 个字符。| |*Query fields*|URL 的 HTTP GET 变量。<br>指定为属性和值对。<br>值会自动进行 URL 编码。来自场景变量、用户宏或 {HOST.\*} 宏的值被解析，然后自动进行 URL 编码。使用 {{macro}.urlencode()} 语法将对它们进行双重 URL 编码。<br>支持用户宏和 {HOST.*} {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) 。| |*Post*|HTTP POST 变量。<br>在 **表单数据** 模式下，指定为属性和值对。<br>值会自动进行 URL 编码。来自场景变量、用户宏或 {HOST.\*} 宏的值被解析，然后自动进行 URL 编码。<br>在 **原始数据** 模式下，属性/值显示在单行上，并与 **&** 符号连接。<br>可以使用  {{macro}.urlencode()} 或 {{macro}.urldecode()} 语法手动对原始值进行 URL 编码/解码。<br>例如：id=2345&userid={user}<br>如果 {user} 被定义为web场景的变量，执行步骤时会被替换为它的值。如果您希望对变量进行 URL 编码，请将 {user} 替换为 {{user}.urlencode()}.<br>支持用户宏和 {HOST.*} {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) 。| |*Variables*|可用于 GET 和 POST 函数的步骤级变量。<br>指定为属性和值对。<br>步骤级变量会覆盖场景级变量或上一步中的变量。 但是，步骤级变量的值仅影响之后的步骤（而不影响当前步骤）。<br>它们具有以下格式：<br>**{macro}**=value<br>**{macro}**=regex:<regular expression><br>有关详细信息，请参阅 [场景](web_monitoring#configuring_a_web_scenario) 级别的变量描述。<br>变量在用于查询字段或用于发布变量的表单数据时会自动进行 URL 编码，但在原始发布或直接在 URL 中使用时必须手动进行 URL 编码。| |*Headers*|执行请求时将发送的自定义 HTTP 标头。<br>指定为属性和值对。<br>步骤级别的标题将覆盖为场景指定的标题。<br>**应该注意的是，在步骤级别定义标头会自动丢弃所有先前定义的标头，但通过从场景级别的下拉列表中选择“用户代理”来分配的默认标头除外。* *<br>但是，即使是“User-Agent”默认标头也可以通过在步骤级别指定它来覆盖。<br>例如，设置没有值的 'User-Agent' 属性将删除在场景级别设置的 User-Agent 值。<br>支持用户宏和 {HOST.\*} 宏。<br>设置 [CURLOPT\_HTTPHEADER](http://curl.haxx.se/libcurl/c/CURLOPT_HTTPHEADER.html) cURL 选项。<br>*从 Zabbix 2.4 开始*支持指定自定义标头。| |*Follow redirects*|标记复选框以遵循 HTTP 重定向。<br>设置 [CURLOPT\_FOLLOWLOCATION](http://curl.haxx.se/libcurl/c/CURLOPT_FOLLOWLOCATION.html) cURL 选项。| |*Retrieve mode*|选择恢复模式：<br>**Body** - 从 HTTP 响应中仅检索正文<br>**Headers** - 从 HTTP 响应中仅检索标头<br>**Body and headers** - 从 HTTP 响应中检索正文和标头| |*Timeout*|Zabbix 处理 URL 的时间不会超过设定的时间 （从 1 秒到最长 1 小时）。实际上，这个参数定义了连接到 URL 的最长时间和执行 HTTP 请求的最长时间。因此，Zabbix 在该步骤上花费的时间不会超过 **2 x Timeout** 秒。<br>[支持时间后缀](/manual/appendix/suffixes) ，例如 30s、1m、1h。支持 [用户宏](/manual/config/macros/user_macros) 。| |*Required string*|要求正则表达式模式。<br>除非检索到的内容 (HTML) 与所需的模式匹配，否则该步骤将失败。如果为空，则不检查所需的字符串。<br>例如：<br> Zabbix<br>Welcome.\*admin 主页<br>*注意*：该字段不支持引用在 Zabbix 前端创建的 [正则表达式](regular_expressions) 。<br>支持用户宏和 {HOST.*} {HOST.\*} [宏](/manual/appendix/macros/supported_by_location) 。| |*Required status codes*|预期的 HTTP 状态代码列表。如果 Zabbix 获得不在列表中的代码，则该步骤将失败。<br>如果为空，则不检查状态代码。<br>例如：支持 200,201,210-299<br>支持 用户宏。|  ::: noteclassic Web 场景步骤中的任何更改只有在保存整个场景时才会保存。 :::  查看配置 Web 监控步骤的 [真实案例](/manual/web_monitoring/example) 。

en-us	#### Configuring tags  The **Tags** tab allows to define scenario-level [tags](/manual/config/tagging).  ![](../../assets/en/manual/config/scenario_c.png)  Tagging allows to filter web scenarios and web monitoring [items](/manual/web_monitoring/items).
zh-cn	#### 配置标签  **标签** 选项卡允许定义场景级别的 [标签](/manual/config/tagging)。  ![](../../assets/en/manual/config/scenario_c.png)  标签允许过滤 Web 场景和 Web [监控项](/manual/web_monitoring/items)。

en-us	##### Configuring Zabbix server/proxy  To read the traps, Zabbix server or proxy must be configured to start the SNMP trapper process and point to the trap file that is being written by SNMPTT or a Bash/Perl trap receiver. To do that, edit the configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server) or [zabbix\_proxy.conf](/manual/appendix/config/zabbix_proxy)):      StartSNMPTrapper=1     SNMPTrapperFile=[TRAP FILE]  ::: notewarning If systemd parameter **[PrivateTmp](http://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=)** is used, this file is unlikely to work in */tmp*. :::  ##### Configuring Bash trap receiver  Requirements: only snmptrapd.  A Bash trap receiver [script](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh) can be used to pass traps to Zabbix server directly from snmptrapd. To configure it, add the `traphandle` option to snmptrapd configuration file (`snmptrapd.conf`), see [example](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/etc/snmp/snmptrapd.conf).
zh-cn	##### 配置 Zabbix Server/Proxy  要读取trap，必须将Zabbix Server/Proxy配置为启动SNMPtrap进程，并指向由SNMPTT或perl trap接收器写入的trap文件。为此，编辑配置文件 ([zabbix\_server.conf](/zh/manual/appendix/config/zabbix_server) 或 [zabbix\_proxy.conf](/zh/manual/appendix/config/zabbix_proxy))：   StartSNMPTrapper=1  SNMPTrapperFile=\[TRAP FILE\]  ::: notewarning 如果使用systemd参数 **[PrivateTmp](http://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=)**，则该文件不太可能在*/tmp*下工作。 :::  ##### 配置 Bash 陷阱接收器  要求：只有snmptrapd。  Bash 陷阱接收器 [脚本](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine/conf/usr/sbin/zabbix_trap_handler.sh) 可用于将陷阱直接从 snmptrapd 传递给 Zabbix 服务器。 要配置它，请将 `traphandle` 选项添加到 snmptrapd 配置文件 (`snmptrapd.conf`)，参见 [示例](https://raw.githubusercontent.com/zabbix/zabbix-docker/6.2/Dockerfiles/snmptraps/alpine /conf/etc/snmp/snmptrapd.conf）。

en-us	#### Connection encryption management  Connections in Zabbix can use:  -   no encryption (default) -   [RSA certificate-based     encryption](/manual/encryption/using_certificates) -   [PSK-based encryption](/manual/encryption/using_pre_shared_keys)  There are two important parameters used to specify encryption between Zabbix components:  -   TLSConnect - specifies what encryption to use for outgoing     connections (unencrypted, PSK or certificate) -   TLSAccept - specifies what types of connections are allowed for     incoming connections (unencrypted, PSK or certificate). One or more     values can be specified.  `TLSConnect` is used in the configuration files for Zabbix proxy (in active mode, specifies only connections to server) and Zabbix agent (for active checks). In Zabbix frontend the TLSConnect equivalent is the *Connections to host* field in *Configuration → Hosts → <some host> → Encryption* tab and the *Connections to proxy* field in *Administration → Proxies → <some proxy> → Encryption* tab. If the configured encryption type for connection fails, no other encryption types will be tried.  `TLSAccept` is used in the configuration files for Zabbix proxy (in passive mode, specifies only connections from server) and Zabbix agent (for passive checks). In Zabbix frontend the TLSAccept equivalent is the *Connections from host* field in *Configuration → Hosts → <some host> → Encryption* tab and the *Connections from proxy* field in *Administration → Proxies → <some proxy> → Encryption* tab.  Normally you configure only one type of encryption for incoming encryptions. But you may want to switch the encryption type, e.g. from unencrypted to certificate-based with minimum downtime and rollback possibility. To achieve this:  -   Set `TLSAccept=unencrypted,cert` in the agent configuration file and     restart Zabbix agent -   Test connection with zabbix\_get to the agent using certificate. If     it works, you can reconfigure encryption for that agent in Zabbix     frontend in the *Configuration → Hosts → <some host> →     Encryption* tab by setting *Connections to host* to "Certificate". -   When server configuration cache gets updated (and proxy     configuration is updated if the host is monitored by proxy) then     connections to that agent will be encrypted -   If everything works as expected you can set `TLSAccept=cert` in the     agent configuration file and restart Zabbix agent. Now the agent     will be accepting only encrypted certificate-based connections.     Unencrypted and PSK-based connections will be rejected.  In a similar way it works on server and proxy. If in Zabbix frontend in host configuration *Connections from host* is set to "Certificate" then only certificate-based encrypted connections will be accepted from the agent (active checks) and zabbix\_sender (trapper items).  Most likely you will configure incoming and outgoing connections to use the same encryption type or no encryption at all. But technically it is possible to configure it asymmetrically, e.g. certificate-based encryption for incoming and PSK-based for outgoing connections.  Encryption configuration for each host is displayed in the Zabbix frontend, in *Configuration → Hosts* in the *Agent encryption* column. For example:  |Example|Connections to host|Allowed connections from host|Rejected connections from host| |-------|-------------------|-----------------------------|------------------------------| |![none\_none.png](../../assets/en/manual/encryption/none_none.png)|Unencrypted|Unencrypted|Encrypted, certificate and PSK-based encrypted| |![cert\_cert.png](../../assets/en/manual/encryption/cert_cert.png)|Encrypted, certificate-based|Encrypted, certificate-based|Unencrypted and PSK-based encrypted| |![psk\_psk.png](../../assets/en/manual/encryption/psk_psk.png)|Encrypted, PSK-based|Encrypted, PSK-based|Unencrypted and certificate-based encrypted| |![psk\_none\_psk.png](../../assets/en/manual/encryption/psk_none_psk.png)|Encrypted, PSK-based|Unencrypted and PSK-based encrypted|Certificate-based encrypted| |![cert\_all.png](../../assets/en/manual/encryption/cert_all.png)|Encrypted, certificate-based|Unencrypted, PSK or certificate-based encrypted|\-|  ::: noteimportant Connections are unencrypted by default. Encryption must be configured for each host and proxy individually. :::
zh-cn	 ####  连接加密管理  Zabbix中的连接可以使用：  -   不加密 (默认) -   [基于RSA证书的加密](/manual/encryption/using_certificates) -   [基于PSK基础加密](/manual/encryption/using_pre_shared_keys)  有两个重要的参数用于指定之间的加密Zabbix组件:  -   TLSConnect -指定对传出连接使用何种加密(未加密、PSK或证书) -   TLSAccept - 指定允许传入连接的类型(未加密的，PSK或证书)。 可以指定一个或多个值。  `TLSConnect` 在Zabbix proxy(在主动模式下，仅指定到server的连接)和Zabbix agent(在主动检查中)的配置文件中使用。在Zabbix前端TLSConnect等效的是*配置→主机→<一些主机>→加密*标签中的*连接到主机*字段和*管理→Proxy代理→<一些proxy代理>→加密*标签中的*连接到proxy*字段。如果为连接配置的加密类型失败，则不会尝试其他加密类型。  `TLSAccept` 在Zabbix proxy(被动模式，仅指定来自server的连接)和Zabbix agent(被动检查)的配置文件中使用。在Zabbix前端TLSAccept等价的是*配置→主机→<一些主机>→加密*标签中的*主机连接*字段和*管理→proxy代理→<一些proxy代理>→加密*标签中的*proxy连接*字段。  通常您只为传入加密配置一种类型的加密。 但您可能希望切换加密类型，例如，从未加密切换到基于证书的加密，并尽可能减少停机时间和回滚可能性。 为实现这一目标:  -   设置 `TLSAccept=unencrypted,cert` 在agent配置文件中设置，重启Zabbix agent -   使用证书测试zabbix\_get到agent的连接。如果它能工作，你可以在Zabbix前端的*Configuration→Hosts→<some host>→encryption *选项卡中通过将*Connections to host*设置为“Certificate”来重新配置该agent的加密。 -   当server配置缓存被更新时(如果主机被proxy监视，则proxy配置被更新)，那么到该proxy的连接将被加密 -   如果一切正常，您可以在agent配置文件中设置' TLSAccept=cert '，并重启Zabbix agent。现在agent将只接受加密的基于证书的连接。 未加密的和基于psk的连接将被拒绝。  以类似的方式，它在server和proxy上工作。 如果在Zabbix前端主机配置*来自主机的连接*设置为“证书”，那么只有基于证书的加密连接将被接受从agent(主动检查)和Zabbix\_sender(trapper监控项)。  最可能的情况是将传入和传出连接配置为使用相同的加密类型或完全不加密。 但在技术上，可以不对称地配置它，例如，对传入连接进行基于证书的加密，对传出连接进行基于psk的加密。  Zabbix前端“*Agent加密*”列的“*配置→主机*”中显示各主机的加密配置信息。 例如:  |例子|连接到主机|允许连接的主机|拒绝连接的主机| |-------|-------------------|-----------------------------|------------------------------| |![none\_none.png](../../assets/en/manual/encryption/none_none.png)|非加密的|非加密的|加密，证书和psk加密| |![cert\_cert.png](../../assets/en/manual/encryption/cert_cert.png)|加密的,基于证书|加密的, 基于证书|加密的基于PSK| |![psk\_psk.png](../../assets/en/manual/encryption/psk_psk.png)|加密的, 基于PSK|加密的, 基于PSK|非加密的基于证书加密的| |![psk\_none\_psk.png](../../assets/en/manual/encryption/psk_none_psk.png)|加密的, 基于PSK|非加密和基于PSK加密|基于证书加密| |![cert\_all.png](../../assets/en/manual/encryption/cert_all.png)|加密, 证书加密|未加密, PSK或者or基于证书加密|\-|  :: noteimportant 默认情况下，连接是不加密的。如果使用加密那么必须分别为每个主机和proxy配置加密。 :::

en-us	### Connection set up  Zabbix supports two types of connect identifiers (connection methods):  -   Easy Connect -   Net Service Name  Connection configuration parameters for Zabbix server and Zabbix proxy can be set in the configuration files. Important parameters for the server and proxy are *DBHost*, *DBUser*, *DBName* and *DBPassword*. The same parameters are important for the frontend: *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*.  Zabbix uses the following connection string syntax:      {DBUser/DBPassword[@<connect_identifier>]}   <connect\_identifier> can be specified either in the form of "Net Service Name" or "Easy Connect".      @[[//]Host[:Port]/<service_name> | <net_service_name>]
zh-cn	### 连接设置  Zabbix支持两种类型的连接标识符（连接方法）：  -   Easy Connect -   Net Service Name  Zabbix server 和 Zabbix proxy的连接配置参数可以在配置文件中设置。server和proxy的重要参数是 *DBHost*, *DBUser*, *DBName* 和*DBPassword*。相同的参数对于前端很重要：  *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*.  Zabbix 使用以下连接字符串语法：      {DBUser/DBPassword[@<connect_identifier>]}   <connect\_identifier> 可以以以下形式指定 "Net Service Name" 或 "Easy Connect".      @[[//]Host[:Port]/<service_name> | <net_service_name>]

en-us	#### Copy an LLD rule to multiple hosts  Copy an LLD rule to two hosts.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.copy",     "params": {         "discoveryids": [             "27426"         ],         "hostids": [             "10196",             "10197"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```
zh-cn	#### LLD 规则复制到多个主机  将 LLD 规则复制到两台主机。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.copy",     "params": {         "discoveryids": [             "27426"         ],         "hostids": [             "10196",             "10197"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```

en-us	#### Copy an LLD rule to multiple hosts  Copy an LLD rule to two hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.copy",     "params": {         "discoveryids": [             "27426"         ],         "hostids": [             "10196",             "10197"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```
zh-cn	#### LLD 规则复制到多个主机  将 LLD 规则复制到两台主机。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.copy",     "params": {         "discoveryids": [             "27426"         ],         "hostids": [             "10196",             "10197"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```

en-us	#### Copying/pasting pages  Dashboard pages can be copied and pasted, allowing to create a new page with the properties of an existing one. They can be pasted from the same dashboard or a different dashboard.  To paste an existing page to the dashboard, first copy it, using the [page menu](#page_menu):  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_copy.png)  To paste the copied page:  -   Make sure the dashboard is in the [editing     mode](#viewing_and_editing_a_dashboard) -   Click on the arrow next to the *Add* button and select the *Paste     page* option
zh-cn	#### 复制/粘贴页面  仪表盘页面可被复制和粘贴，可通过现有页面的属性创建一个新页面。他们可粘贴到同一个仪表盘或不同仪表盘中。  要粘贴一个现有页面到仪表盘，先复制，使用[页面菜单](#page_menu)：  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_copy.png)  要粘贴已复制的页面：  -   确保仪表盘在[编辑模式](#viewing_and_editing_a_dashboard) -   点击*添加*按钮旁的箭头，并选择*粘贴页面*选项。

en-us	#### Copying/pasting widgets  Dashboard widgets can be copied and pasted, allowing to create a new widget with the properties of an existing one. They can be copy-pasted within the same dashboard, or between dashboards opened in different tabs.  A widget can be copied using the [widget menu](#widget_menu). To paste the widget:  -   click on the arrow next to the *Add* button and selecting the *Paste     widget* option, when editing the dashboard -   use the *Paste widget* option when adding a new widget by selecting     some area in the dashboard (a widget must be copied first for the     paste option to become available)  A copied widget can be used to paste over an existing widget using the *Paste* option in the [widget menu](#widget_menu).
zh-cn	#### 复制/粘贴组件  仪表盘组件可被复制和粘贴，允许通过现有组件的属性创建一个新的组件。可以在同一个仪表盘进行复制，或者在不同标签页打开的多个仪表盘之间进行复制。  可使用[组件菜单](#widget_menu)来复制。要粘贴组件：  -   在编辑仪表盘时，点击*添加*按钮旁的箭头并选择*粘贴组件*选项 -   在选择仪表盘的某区域来添加组件时，使用*粘贴组件*选项（需要先复制一个组件，粘贴选项才会可用）  使用[组件菜单](#widget_menu)中的*粘贴*选项，一个复制的组件可被用于粘贴覆 盖一个现有的组件。

en-us	##### Copying PHP files  Zabbix frontend is written in PHP, so to run it a PHP supported webserver is needed. Installation is done by simply copying the PHP files from the ui directory to the webserver HTML documents directory.  Common locations of HTML documents directories for Apache web servers include:  -   /usr/local/apache2/htdocs (default directory when installing Apache     from source) -   /srv/www/htdocs (OpenSUSE, SLES) -   /var/www/html (Debian, Ubuntu, Fedora, RHEL, CentOS)  It is suggested to use a subdirectory instead of the HTML root. To create a subdirectory and copy Zabbix frontend files into it, execute the following commands, replacing the actual directory:      mkdir <htdocs>/zabbix     cd ui     cp -a . <htdocs>/zabbix  If planning to use any other language than English, see [Installation of additional frontend languages](/manual/appendix/install/locales) for instructions.
zh-cn	##### 复制PHP文件  Zabbix前端是PHP编写的，所以运行它需要PHP支持的网络服务器。安装只需简单的从 ui 目录复制PHP文件到网络服务器 HTML文档目录。  Apache网络服务器的HTML文档目录的常见位置包括：  -   /usr/local/apache2/htdocs (从源代码安装Apache的默认目录) -   /srv/www/htdocs (OpenSUSE, SLES) -   /var/www/html (Debian, Ubuntu, Fedora, RHEL, CentOS)  建议使用子目录而非HTML根目录。要创建子目录并将Zabbix前端文件复制过去，请执行如下命令，以替换实际目录：      mkdir <htdocs>/zabbix     cd ui     cp -a . <htdocs>/zabbix  如果计划用英语之外的语言，请参考[前端安装其他语言](/manual/appendix/install/locales) 。

en-us	 ### Copyright notice  Zabbix documentation is NOT distributed under a GPL license. Use  of Zabbix documentation is subject to the following terms:   You may create a printed copy of this documentation solely for your  own personal use. Conversion to other formats is allowed as long as  the actual content is not altered or edited in any way. You shall  not publish or distribute this documentation in any form or on any  media, except if you distribute the documentation in a manner similar  to how Zabbix disseminates it (that is, electronically for download  on a Zabbix web site) or on a USB or similar medium, provided however  that the documentation is disseminated together with the software on  the same medium. Any other use, such as any dissemination of printed  copies or use of this documentation, in whole or in part, in another  publication, requires the prior written consent from an authorized  representative of Zabbix. Zabbix reserves any and all rights to this  documentation not expressly granted above.
zh-cn	 ＃＃＃ 版权声明  Zabbix 文档不在 GPL 许可下分发。利用Zabbix 文档受以下条款约束：  您可以为了个人使用需要打印文档副本。在未以任何方式更改或编辑实际内容的前提下，允许转换成其他格式。你应该不得以任何形式或在任何 媒体上传播此文档，除非您以类似Zabbix 的方式传播文档（即以电子方式在 Zabbix 网站上下载）或 USB 或类似媒介上，但前提是该文档与软件在相同的媒介一起传播。任何其他用途，例如复制或使用该文档，使用全部或部分文档进行出版，需要事先获得Zabbix书面授权同意。 Zabbix对此文档以上未明确授权的所有文件保留所有权。

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

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

en-us	#### Correlation filter condition  The correlation filter condition object defines a specific condition that must be checked before running the correlation operations.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>0 - old event tag;<br>1 - new event tag;<br>2 - new event host group;<br>3 - event tag pair;<br>4 - old event tag value;<br>5 - new event tag value.| |tag|string|Event tag (old or new). Required when type of condition is: 0, 1, 4, 5.| |groupid|string|Host group ID. Required when type of condition is: 2.| |oldtag|string|Old event tag. Required when type of condition is: 3.| |newtag|string|New event tag. Required when type of condition is: 3.| |value|string|Event tag (old or new) value. Required when type of condition is: 4, 5.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Required when type of condition is: 2, 4, 5.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [correlation.get](get#retrieve_correlations) and [correlation.create](create#using_a_custom_expression_filter) method pages. :::  The following operators and values are supported for each condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |2|Host group|=, <>|Host group ID.| |4|Old event tag value|=, <>, like, not like|string| |5|New event tag value|=, <>, like, not like|string|
zh-cn	#### 关联过滤条件  关联过滤条件对象定义了在运行关联操作之前必须检查的特定条件。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**type**<br>（required）|integer|条件类型。<br><br>可用值：<br>0 - 旧事件标签；<br>1 - 新事件标签；<br>2 - 新事件主机组；<br>3 - 事件标签对；<br>4 - 旧事件标签值；<br>5 - 新事件标签值。| |tag|string|标签（旧或新）。条件类型是：0, 1, 4, 5 时需要。| |groupid|string|主机组ID。条件类型是：2 时需要。| |oldtag|string|旧事件标签。条件类型是：3 时需要。| |newtag|string|新事件标签。条件类型是：3 时需要。| |value|string|事件标签(旧或新)值。条件类型是：4, 5 时需要。| |formulaid|string|任意唯一 ID，用于引用一个自定义表达式中的条件。只能包含大写字母。当修改过滤条件时，该 ID 必须由用户定义，但以后请求它们时会重新生成。| |operator|integer|条件运算符。<br><br>条件类型是：2, 4, 5 时需要。|  ::: notetip 为了更好地了解如何使用具有各种类型的过滤表达式，请参阅 [correlation.get](get#获取关联) 和[correlation.create](create#使用一个自定义表达式过滤) 方法页面上的示例。 :::  以下运算符和值都支持每种条件类型。  |条件|条件名称|支持运算符|期望的值| |---------|--------------|-------------------|--------------| |2|主机组|=, <>|主机组 ID。| |4|旧事件标签值|=, <>, like, not like|string| |5|新事件标签值|=, <>, like, not like|string|

en-us	### Correlation filter  The correlation filter object defines a set of conditions that must be met to perform the configured correlation operations. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.|
zh-cn	 ### 关联过滤  关联过滤对象定义了执行配置的关联操作必须满足的一组条件。它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**evaltype**<br>（必需）|integer|过滤条件的评估方法。<br><br>可用值：<br>0 - 与/或；<br>1 - 与；<br>2 - 或；<br>3 - 自定义表达式。| |**conditions**<br>（必需）|array|用来过滤结果的一组过滤条件集。| |eval\_formula|string|*（只读）* 生成的表达式将用于评估过滤条件。该表达式包含通过 “formulaid” 引用特定筛选条件的 ID。对于具有自定义表达式的筛选，`eval_formula` 的值等于 `formula` 的值。| |formula|string|用于具有自定义表达式的过滤评估条件。该表达式必须包含通过 “formulaid” 引用特定筛选条件的 ID。表达式中使用的 ID 必须与过滤条件中定义的 ID 完全匹配：没有条件时可以不使用或省略。<br><br>自定义表达式过滤必需。|

en-us	### Correlation filter  The correlation filter object defines a set of conditions that must be met to perform the configured correlation operations. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.|
zh-cn	 ### 关联过滤  关联过滤对象定义了执行配置的关联操作必须满足的一组条件。它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**evaltype**<br>（必需）|integer|过滤条件的评估方法。<br><br>可用值：<br>0 - 与/或；<br>1 - 与；<br>2 - 或；<br>3 - 自定义表达式。| |**conditions**<br>（必需）|array|用来过滤结果的一组过滤条件集。| |eval\_formula|string|*（只读）* 生成的表达式将用于评估过滤条件。该表达式包含通过 “formulaid” 引用特定筛选条件的 ID。对于具有自定义表达式的筛选，`eval_formula` 的值等于 `formula` 的值。| |formula|string|用于具有自定义表达式的过滤评估条件。该表达式必须包含通过 “formulaid” 引用特定筛选条件的 ID。表达式中使用的 ID 必须与过滤条件中定义的 ID 完全匹配：没有条件时可以不使用或省略。<br><br>自定义表达式过滤必需。|

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

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

en-us	### Correlation operation  The correlation operation object defines an operation that will be performed when a correlation is executed. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - close old events;<br>1 - close new event.|
zh-cn	### 关联操作  关联操作对象定义执行关联时将执行的操作。它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**type**<br>（必需）|integer|操作类型。<br><br>可用值：<br>0 - 关闭旧事件；<br>1 - 关闭新事件。|

en-us	### Correlation operation  The correlation operation object defines an operation that will be performed when a correlation is executed. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - close old events;<br>1 - close new event.|
zh-cn	### 关联操作  关联操作对象定义执行关联时将执行的操作。它具有如下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |--------|---------------------------------------------------|-----------| |**type**<br>（必需）|integer|操作类型。<br><br>可用值：<br>0 - 关闭旧事件；<br>1 - 关闭新事件。|

en-us	### Correlation  The correlation object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |correlationid|string|*(readonly)* ID of the correlation.| |**name**<br>(required)|string|Name of the correlation.| |description|string|Description of the correlation.| |status|integer|Whether the correlation 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#数据类型)|说明| |--------|---------------------------------------------------|-----------| |correlationid|字符|*（只读）*关联ID。| |**name**<br>（必需）|字符|关联名称。| |description|字符|关联描述。| |status|整数|关联是否开启。<br><br>可用值：<br>0 - *（默认）*启用；<br>1 - 禁用。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Correlation  This class is designed to work with correlations.  Object references:\  -   [Correlation](/manual/api/reference/correlation/object#correlation)  Available methods:\  -   [correlation.create](/manual/api/reference/correlation/create) -     creating new correlations -   [correlation.delete](/manual/api/reference/correlation/delete) -     deleting correlations -   [correlation.get](/manual/api/reference/correlation/get) -     retrieving correlations -   [correlation.update](/manual/api/reference/correlation/update) -     updating correlations
zh-cn	 # 关联  此类用于关联。  对象引用：  -   [关联](/manual/api/reference/correlation/object#关联)  可用方法：  -   [correlation.create](/manual/api/reference/correlation/create) - 创建新关联 -   [correlation.delete](/manual/api/reference/correlation/delete) - 删除关联 -   [correlation.get](/manual/api/reference/correlation/get) - 获取关联 -   [correlation.update](/manual/api/reference/correlation/update) - 更新关联

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

en-us	##### Counting of threads in `proc.mem[]` and `proc.num[]` items  Linux kernel threads are counted by `proc.num[]` item but do not report memory in `proc.mem[]` item. For example:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     1      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory.  But what happens if there is a user process with the same name as a kernel thread ? Then it could look like this:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]     zabbix    9611  6133  0 17:58 pts/1    00:00:00 ./kthreadd      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     2      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     4157440  `proc.num[]` counted both the kernel thread and the user process. `proc.mem[]` reports memory for the user process only and counts the kernel thread memory as if it was 0. This is different from the case above when ZBX\_NOTSUPPORTED was reported.  Be careful when using `proc.mem[]` and `proc.num[]` items if the program name happens to match one of the thread.  Before putting parameters into `proc.mem[]` and `proc.num[]` items, you may want to test the parameters using `proc.num[]` item and `ps` command.
zh-cn	 ##### `proc.mem[]`  和`proc.num[]`  监控项中的线程计数  Linux 内核线程通过`proc.num[]`  监控项计数，但是  `proc.mem[]`  监控项并不报告内存。 例如:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     1      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory.  但是如果用户线程和内核线程名字相同会发生什么呢 ? 可能会是这样:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]     zabbix    9611  6133  0 17:58 pts/1    00:00:00 ./kthreadd      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     2      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     4157440   `proc.num[]`  计算内核线程和用户进程。  `proc.mem[]`  只计算用户进程内存，如果为0计算内核线程内存。这和上面报告 ZBX_NOTSUPPORTED 的例子不同。  如果程序名恰好匹配其中一个线程，请小心使用`proc.mem[]`  和`proc.num[]`  监控项 。  在给  `proc.mem[]`  和`proc.num[]`  监控项配置参数时, 你应该使用  `proc.num[]`  监控项 和  `ps`  命令测试该参数。

en-us	##### CPU  Zabbix and especially Zabbix database may require significant CPU resources depending on number of monitored parameters and chosen database engine.
zh-cn	##### CPU  Zabbix，尤其是 Zabbix 数据库可能需要大量 CPU 资源，该具体取决于被监控参数的数量和所选的数据库引擎。

en-us	#### Create a custom script  Create a custom script that will reboot a server. The script will require write access to the host and will display a configuration message before running in the frontend.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "Reboot server",         "command": "reboot server 1",         "confirmation": "Are you sure you would like to reboot the server?",         "scope": 2,         "type": 0     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "4"         ]     },     "id": 1 } ```
zh-cn	#### 创建定制脚本  创建一个重启服务器的定制脚本。该脚本会要求主机的写权限，并且在前端运行之前会显示配置信息。  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "Reboot server",         "command": "reboot server 1",         "confirmation": "Are you sure you would like to reboot the server?",         "scope": 2,         "type": 0     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "4"         ]     },     "id": 1 } ```

en-us	#### Create a discovery action  Create an action that will link discovered hosts to template "10091".  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Discovery action",         "eventsource": 1,         "status": 0,         "esc_period": "0s",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 21,                     "value": "1"                 },                 {                     "conditiontype": 10,                     "value": "2"                 }             ]         },         "operations": [             {                 "esc_step_from": 1,                 "esc_period": "0s",                 "optemplate": [                     {                         "templateid": "10091"                     }                 ],                 "operationtype": 6,                 "esc_step_to": 1             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```  
zh-cn	#### 创建发现动作  创建一个将发现的主机链接到模板 `30085` 的动作。  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Discovery action",         "eventsource": 1,         "status": 0,         "esc_period": "0s",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 21,                     "value": "1"                 },                 {                     "conditiontype": 10,                     "value": "2"                 }             ]         },         "operations": [             {                 "esc_step_from": 1,                 "esc_period": "0s",                 "optemplate": [                     {                         "templateid": "10091"                     }                 ],                 "operationtype": 6,                 "esc_step_to": 1             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```  

en-us	#### Create a discovery action  Create an action that will link discovered hosts to template "10091".  Request:  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Discovery action",         "eventsource": 1,         "status": 0,         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 21,                     "operator": 0,                     "value": "1"                 },                 {                     "conditiontype": 10,                     "operator": 0,                     "value": "2"                 }             ]         },         "operations": [             {                 "operationtype": 6,                 "optemplate": [                     {                         "templateid": "10091"                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```
zh-cn	#### 创建发现动作  创建一个将发现的主机链接到模板 "10091" 的动作。  请求：  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Discovery action",         "eventsource": 1,         "status": 0,         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 21,                     "operator": 0,                     "value": "1"                 },                 {                     "conditiontype": 10,                     "operator": 0,                     "value": "2"                 }             ]         },         "operations": [             {                 "operationtype": 6,                 "optemplate": [                     {                         "templateid": "10091"                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "18"         ]     },     "id": 1 } ```

en-us	#### Create a discovery rule  Create a discovery rule to find machines running the Zabbix agent in the local network. The rule must use a single Zabbix agent check on port 10050.  Request:  ```json {     "jsonrpc": "2.0",     "method": "drule.create",     "params": {         "name": "Zabbix agent discovery",         "iprange": "192.168.1.1-255",         "dchecks": [             {                 "type": "9",                 "key_": "system.uname",                 "ports": "10050",                 "uniq": "0"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "6"         ]     },     "id": 1 } ```
zh-cn	#### 创建发现规则  创建一个发现规则来查找在内部网络中运行 Zabbix agent 的机器。该规则必须在端口10050上使用单个Zabbix agent检查。  请求：  ```json {     "jsonrpc": "2.0",     "method": "drule.create",     "params": {         "name": "Zabbix agent discovery",         "iprange": "192.168.1.1-255",         "dchecks": [             {                 "type": "9",                 "key_": "system.uname",                 "ports": "10050",                 "uniq": "0"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "6"         ]     },     "id": 1 } ```

en-us	#### Create agent autoregistration rule  Add a host to host group "Linux servers" when host name contains "SRV" or metadata contains "AlmaLinux".  Request:  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Register Linux servers",         "eventsource": "2",         "status": "0",         "filter": {             "evaltype": "2",             "conditions": [                 {                     "conditiontype": "22",                     "operator": "2",                     "value": "SRV"                 },                 {                     "conditiontype": "24",                     "operator": "2",                     "value": "AlmaLinux"                 }             ]         },         "operations": [             {                 "operationtype": "4",                 "opgroup": [                     {                         "groupid": "2"                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             19         ]     },     "id": 1 } ```
zh-cn	#### 创建 agent 自动注册规则  当主机名中包含 "SRV" 或元数据中包含 "AlmaLinux" 时，向 "Linux servers" 主机组中添加主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Register Linux servers",         "eventsource": "2",         "status": "0",         "filter": {             "evaltype": "2",             "conditions": [                 {                     "conditiontype": "22",                     "operator": "2",                     "value": "SRV"                 },                 {                     "conditiontype": "24",                     "operator": "2",                     "value": "CentOS"                 }             ]         },         "operations": [             {                 "operationtype": "4",                 "opgroup": [                     {                         "groupid": "2"                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             19         ]     },     "id": 1 } ```

en-us	#### Create agent autoregistration rule  Add a host to host group "Linux servers" when host name contains "SRV" or metadata contains "CentOS".  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Register Linux servers",         "eventsource": "2",         "status": "0",         "filter": {             "evaltype": "2",             "formula": "A or B",             "conditions": [                 {                     "conditiontype": "22",                     "operator": "2",                     "value": "SRV",                     "value2": "",                     "formulaid": "B"                 },                 {                     "conditiontype": "24",                     "operator": "2",                     "value": "CentOS",                     "value2": "",                     "formulaid": "A"                 }             ]         },         "operations": [             {                 "actionid": "9",                 "operationtype": "4",                 "esc_period": "0",                 "esc_step_from": "1",                 "esc_step_to": "1",                 "evaltype": "0",                 "opgroup": [                     {                         "operationid": "16",                         "groupid": "2"                     }                 ]             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             19         ]     },     "id": 1 } ```  
zh-cn	### 参见  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)  

en-us	#### Create a host map  Create a map with two host elements and a link between them. Note the use of temporary "selementid1" and "selementid2" values in the map link object to refer to map elements.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Host map",         "width": 600,         "height": 600,         "selements": [             {                 "selementid": "1",                 "elements": [                     {"hostid": "1033"}                 ],                 "elementtype": 0,                 "iconid_off": "2"             },              {                 "selementid": "2",                 "elements": [                     {"hostid": "1037"}                 ],                 "elementtype": 0,                 "iconid_off": "2"             }         ],         "links": [             {                 "selementid1": "1",                 "selementid2": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "9"         ]     },     "id": 1 } ```
zh-cn	#### 创建主机映射  创建一个包含两个主机元素和它们之间链接的拓扑图。 请注意在拓扑图链接对象中使用临时“selementid1”和“selementid2”值来引用拓扑图元素。  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Host map",         "width": 600,         "height": 600,         "selements": [             {                 "selementid": "1",                 "elements": [                     {"hostid": "1033"}                 ],                 "elementtype": 0,                 "iconid_off": "2"             },             {                 "selementid": "2",                 "elements": [                     {"hostid": "1037"}                 ],                 "elementtype": 0,                 "iconid_off": "2"             }         ],         "links": [             {                 "selementid1": "1",                 "selementid2": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "9"         ]     },     "id": 1 } ```

en-us	#### Create an active proxy  Create an action proxy "Active proxy" and assign a host to be monitored by it.  Request:  ```json {     "jsonrpc": "2.0",     "method": "proxy.create",     "params": {         "host": "Active proxy",         "status": "5",         "hosts": [             {                 "hostid": "10279"             }         ]     },     "auth": "ab9638041ec6922cb14b07982b268f47",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10280"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个主动代理  创建主动代理"Active proxy"，并分配要监控的主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "proxy.create",     "params": {         "host": "Active proxy",         "status": "5",         "hosts": [             {                 "hostid": "10279"             }         ]     },     "auth": "ab9638041ec6922cb14b07982b268f47",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10280"         ]     },     "id": 1 } ```

en-us	#### Create an empty map  Create a map with no elements.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map",         "width": 600,         "height": 600     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "8"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个空的拓扑图  创建一个没有任何元素的拓扑图  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map",         "width": 600,         "height": 600     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "8"         ]     },     "id": 1 } ```

en-us	#### Create a new event tag correlation  Create a correlation using evaluation method `AND/OR` with one condition and one operation. By default the correlation will be enabled.  Request:  ```json {     "jsonrpc": "2.0",     "method": "correlation.create",     "params": {         "name": "new event tag correlation",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "type": 1,                     "tag": "ok"                 }             ]         },         "operations": [             {                 "type": 0             }         ]     },     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "correlationids": [             "1"         ]     },     "id": 1 } ```
zh-cn	 #### 创建一个新的事件标签关联  使用具有一个条件和一个操作的评估方法 `AND/OR` 创建一个`关联`。默认情况下，这个关联将被启用。  请求:  ```json {     "jsonrpc": "2.0",     "method": "correlation.create",     "params": {         "name": "new event tag correlation",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "type": 1,                     "tag": "ok"                 }             ]         },         "operations": [             {                 "type": 0             }         ]     },     "auth": "343baad4f88b4106b9b5961e77437688",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "correlationids": [             "1"         ]     },     "id": 1 } ```

en-us	#### Create a new interface  Create a secondary IP agent interface on host "30052."  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.create",     "params": {         "hostid": "30052",         "main": "0",         "type": "1",         "useip": "1",         "ip": "127.0.0.1",         "dns": "",         "port": "10050",     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30062"         ]     },     "id": 1 } ```
zh-cn	#### 创建主机接口  给ID为30052主机创建辅助IP代理接口  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.create",     "params": {         "hostid": "30052",         "main": "0",         "type": "1",         "useip": "1"         "ip": "127.0.0.1",         "dns": "",         "port": "10050",     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30062"         ]     },     "id": 1 } ```

en-us	#### Create an icon map  Create an icon map to display hosts of different types.  Request:  ```json {     "jsonrpc": "2.0",     "method": "iconmap.create",     "params": {         "name": "Type icons",         "default_iconid": "2",         "mappings": [             {                 "inventory_link": 1,                 "expression": "server",                 "iconid": "3"             },             {                 "inventory_link": 1,                 "expression": "switch",                 "iconid": "4"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "iconmapids": [             "2"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个图标映射  创建一个图标映射以展现不同类型的主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "iconmap.create",     "params": {         "name": "Type icons",         "default_iconid": "2",         "mappings": [             {                 "inventory_link": 1,                 "expression": "server",                 "iconid": "3"             },             {                 "inventory_link": 1,                 "expression": "switch",                 "iconid": "4"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "iconmapids": [             "2"         ]     },     "id": 1 } ```

en-us	#### Create an image  Create a cloud icon.  Request:  ```json {     "jsonrpc": "2.0",     "method": "image.create",     "params": {         "imagetype": 1,         "name": "Cloud_(24)",         "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII="     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "imageids": [             "188"         ]     },     "id": 1 } ```
zh-cn	#### 创建新图像  创建云图标。  请求：  ```json {     "jsonrpc": "2.0",     "method": "image.create",     "params": {         "imagetype": 1,         "name": "Cloud_(24)",         "image": "iVBORw0KGgoAAAANSUhEUgAAABgAAAANCAYAAACzbK7QAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAACmAAAApgBNtNH3wAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAIcSURBVDjLrZLbSxRRHMdPKiEiRQ89CD0s+N5j9BIMEf4Hg/jWexD2ZEXQbC9tWUFZimtLhswuZiVujK1UJmYXW9PaCUdtb83enL3P7s6ss5f5dc7EUsmqkPuFH3M4/Ob7+V0OAgC0UyDENFEU03rh1uNOs/lFG75o2i2/rkd9Y3Tgyj3HiaezbukdH9A/rP4E9vWi0u+Y4fuGnMf3DRgYc3Z/84YrQSkD3mgKhFAC+KAEK74Y2Lj3MjPoOokQ3Xyx/1GHeXCifbfO6lRPH/wi+AvZQhGSsgKxdB5CCRkCGPbDgMXBMbukTc4vK5/WRHizsq7fZl2LFuvE4T0BZDTXHtgv4TNUqlUolsqQL2qQwbDEXzBBTIJ7I4y/cfAENmHZF4XrY9Mc+X9HAFmoyXS2ddy1IOg6/KNyBcM0DFP/wFZFCcOy4N9Mw0YkCTOfhdL5AfZQXQBFn2t/ODXHC8FYVcoWjNEQ03qqwTJ5FdI44jg/msoB2Zd5ZKq3q6evA1FUS60bYyyj3AJf3V72HiLZJQxTtRLk1C2IYEg4mTNg63hPd1mOJd7Ict911OMNlWEf0nFxpCt16zcshTuLpGSwDDuPIfv0xzNyQYVGicC0cgUUDLM6Xp02lvvW/V2EBssnxlSGmWsxljw0znV9XfPLjTCW84r+cn7Jc8c2eWrbM6Wbe6/aTJbhJ/TNkWc9/xXW592Xb9iPkKnUfH8BKdLgFy0lDyQAAAAASUVORK5CYII="     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "imageids": [             "188"         ]     },     "id": 1 } ```

en-us	#### Create an interface with SNMP details  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.create",     "params": {         "hostid": "10456",         "main": "0",         "type": "2",         "useip": "1",         "ip": "127.0.0.1",         "dns": "",         "port": "1601",         "details": {             "version": "2",             "bulk": "1",             "community": "{$SNMP_COMMUNITY}"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30063"         ]     },     "id": 1 } ```
zh-cn	#### 创建SNMP详细信息的主机接口  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.create",     "params": {         "hostid": "10456",         "main": "0",         "type": "2",         "useip": "1",         "ip": "127.0.0.1",         "dns": "",         "port": "1601",         "details": {             "version": "2",             "bulk": "1",             "community": "{$SNMP_COMMUNITY}"         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30063"         ]     },     "id": 1 } ```

en-us	 Create another child service of Zabbix cluster with name "Zabbix server node 2".   Set the Problem tags as:   - Name: component - Operation: Equals - Value: HA node 2  Switch to the *Tags* tab and add a service tag: `Zabbix server:node 2`.  Save the new service. 
zh-cn	 创建另一个子服务 "Zabbix server node 2".   设置问题标签:   - 名称：组件 - 操作：等于 - 值：HA node 2  切换到*标签* 面板并添加服务标签：`Zabbix server:node 2`。  保存新建的服务。

en-us	#### Create a passive proxy  Create a passive proxy "Passive proxy" and assign two hosts to be monitored by it.  Request:  ```json {     "jsonrpc": "2.0",     "method": "proxy.create",     "params": {         "host": "Passive proxy",         "status": "6",         "interface": {             "ip": "127.0.0.1",             "dns": "",             "useip": "1",             "port": "10051"         },         "hosts": [             {                 "hostid": "10192"             },             {                 "hostid": "10139"             }         ]     },     "auth": "ab9638041ec6922cb14b07982b268f47",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10284"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个被动代理  创建一个被动代理“Passive proxy”，并分配两台要监控的主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "proxy.create",     "params": {         "host": "Passive proxy",         "status": "6",         "interface": {             "ip": "127.0.0.1",             "dns": "",             "useip": "1",             "port": "10051"         },         "hosts": [             {                 "hostid": "10192"             },             {                 "hostid": "10139"             }         ]     },     "auth": "ab9638041ec6922cb14b07982b268f47",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10284"         ]     },     "id": 1 } ```

en-us	#### Create a SSH script  Create a SSH script with public key authentication that can be executed on a host and has a context menu.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "SSH script",         "command": "my script command",         "type": 2,         "username": "John",         "publickey": "pub.key",         "privatekey": "priv.key",         "password": "secret",         "port": "12345",         "scope": 2,         "menu_path": "All scripts/SSH",         "usrgrpid": "7",         "groupid": "4"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 创建SSH脚本  创建一个SSH脚本，通过公钥完成身份验证从而可以在主机运行，并且带有上下文菜单。  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "SSH script",         "command": "my script command",         "type": 2,         "username": "John",         "publickey": "pub.key",         "privatekey": "priv.key",         "password": "secret",         "port": "12345",         "scope": 2,         "menu_path": "All scripts/SSH",         "usrgrpid": "7",         "groupid": "4"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Create a token  Create an enabled token that never expires and authenticates user of ID 2.  Request:  ```json {     "jsonrpc": "2.0",     "method": "token.create",     "params": {         "name": "Your token",         "userid": "2"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "188"         ]     },     "id": 1 } ```  Create a disabled token that expires at January 21st, 2021. This token will authenticate current user.  Request:  ```json {     "jsonrpc": "2.0",     "method": "token.create",     "params": {         "name": "Your token",         "status": "1",         "expires_at": "1611238072"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "189"         ]     },     "id": 1 } ```
zh-cn	#### 创建令牌  创建一个永不过期的已启用令牌，并对ID为2的用户进行身份验证。  请求：  ```json {     "jsonrpc": "2.0",     "method": "token.create",     "params": {         "name": "Your token",         "userid": "2"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "188"         ]     },     "id": 1 } ```  创建2021年1月21日到期的禁用令牌。此令牌将对当前用户进行身份验证。  请求：  ```json {     "jsonrpc": "2.0",     "method": "token.create",     "params": {         "name": "Your token",         "status": "1",         "expires_at": "1611238072"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "tokenids": [             "189"         ]     },     "id": 1 } ```

en-us	#### Create a trigger action  Create an action that will be run when a trigger from host "10084" that has the word "memory" in its name goes into problem state. The action must first send a message to all users in user group "7". If the event is not resolved in 4 minutes, it will run script "3" on all hosts in group "2". On trigger recovery it will notify all users who received any messages regarding the problem before. On trigger update, message with custom subject and body will be sent to all who left acknowledgments and comments via all media types.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084"                 },                 {                     "conditiontype": 3,                     "operator": 2,                     "value": "memory"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             },             {                 "operationtype": 1,                 "esc_step_from": 3,                 "esc_step_to": 4,                 "evaltype": 0,                 "opconditions": [                     {                         "conditiontype": 14,                         "operator": 0,                         "value": "0"                     }                 ],                 "opcommand_grp": [                     {                         "groupid": "2"                     }                 ],                 "opcommand": {                     "scriptid": "3"                 }             }         ],         "recovery_operations": [             {                 "operationtype": "11",                 "opmessage": {                     "default_msg": 1                 }             }             ],         "update_operations": [             {                 "operationtype": "12",                 "opmessage": {                     "default_msg": 0,                     "message": "Custom update operation message body",                     "subject": "Custom update operation message subject"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17"         ]     },     "id": 1 } ```  
zh-cn	#### 创建触发器动作  创建一个动作，动作如下描述，当主机 `30045` ，它的触发器中的 `memory` 进入问题状态时。该动作必须首先向用户组 `7` 中的所有用户发送消息。如果事件在 4 分钟内未被解决，它将在 `2` 组中的所有主机上运行脚本 `3`。在触发恢复中，它将通知所有接收到关于该问题的消息的用户。在触发器确认中，带有自定义主体和主体的消息将通过所有媒体类型发送给所有确认和评论的所有人。  请求:  ``` {.java} {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "def_shortdata": "{TRIGGER.NAME}: {TRIGGER.STATUS}",         "def_longdata": "{TRIGGER.NAME}: {TRIGGER.STATUS}\r\nLast value: {ITEM.LASTVALUE}\r\n\r\n{TRIGGER.URL}",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084"                 },                 {                     "conditiontype": 3,                     "operator": 2,                     "value": "memory"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             },             {                 "operationtype": 1,                 "esc_step_from": 3,                 "esc_step_to": 4,                 "evaltype": 0,                 "opconditions": [                     {                         "conditiontype": 14,                         "operator": 0,                         "value": "0"                     }                 ],                 "opcommand_grp": [                     {                         "groupid": "2"                     }                 ],                 "opcommand": {                     "type": 4,                     "scriptid": "3"                 }             }         ],         "recovery_operations": [             {                 "operationtype": "11",                 "opmessage": {                     "default_msg": 1                 }             }             ],         "acknowledge_operations": [             {                 "operationtype": "12",                 "opmessage": {                     "message": "Custom acknowledge operation message body",                     "subject": "Custom acknowledge operation message subject"                 }             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17"         ]     },     "id": 1 } ```  

en-us	#### Create a trigger action  Create an action that will be run when a trigger from host "10084" that has the word "memory" in its name goes into problem state. The action must first send a message to all users in user group "7". If the event is not resolved in 4 minutes, it will run script "3" on all hosts in group "2". On trigger recovery it will notify all users who received any messages regarding the problem before. On trigger update, message with custom subject and body will be sent to all who left acknowledgments and comments via all media types.  Request:  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084"                 },                 {                     "conditiontype": 3,                     "operator": 2,                     "value": "memory"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             },             {                 "operationtype": 1,                 "esc_step_from": 3,                 "esc_step_to": 4,                 "evaltype": 0,                 "opconditions": [                     {                         "conditiontype": 14,                         "operator": 0,                         "value": "0"                     }                 ],                 "opcommand_grp": [                     {                         "groupid": "2"                     }                 ],                 "opcommand": {                     "scriptid": "3"                 }             }         ],         "recovery_operations": [             {                 "operationtype": "11",                 "opmessage": {                     "default_msg": 1                 }             }             ],         "update_operations": [             {                 "operationtype": "12",                 "opmessage": {                     "default_msg": 0,                     "message": "Custom update operation message body",                     "subject": "Custom update operation message subject"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17"         ]     },     "id": 1 } ```
zh-cn	#### 创建触发器动作  创建一个动作，它将在 主机 "10084"  名字中包含 "memory" 的触发器进入problem状态时运行。这个动作必须首先向用户组 "7" 中的所有用户发送消息。如果事件在 4 分钟内未被解决，它将在 "2" 组中的所有主机上运行脚本 "3"。在触发器恢复时，它将通知之前收到有关该问题的任何消息的所有用户。在触发器确认中，带有自定义主体和主体的消息将通过所有媒体类型发送给所有确认和评论的所有人。  请求：  ```json {     "jsonrpc": "2.0",     "method": "action.create",     "params": {         "name": "Trigger action",         "eventsource": 0,         "status": 0,         "esc_period": "2m",         "filter": {             "evaltype": 0,             "conditions": [                 {                     "conditiontype": 1,                     "operator": 0,                     "value": "10084"                 },                 {                     "conditiontype": 3,                     "operator": 2,                     "value": "memory"                 }             ]         },         "operations": [             {                 "operationtype": 0,                 "esc_period": "0s",                 "esc_step_from": 1,                 "esc_step_to": 2,                 "evaltype": 0,                 "opmessage_grp": [                     {                         "usrgrpid": "7"                     }                 ],                 "opmessage": {                     "default_msg": 1,                     "mediatypeid": "1"                 }             },             {                 "operationtype": 1,                 "esc_step_from": 3,                 "esc_step_to": 4,                 "evaltype": 0,                 "opconditions": [                     {                         "conditiontype": 14,                         "operator": 0,                         "value": "0"                     }                 ],                 "opcommand_grp": [                     {                         "groupid": "2"                     }                 ],                 "opcommand": {                     "scriptid": "3"                 }             }         ],         "recovery_operations": [             {                 "operationtype": "11",                 "opmessage": {                     "default_msg": 1                 }             }             ],         "update_operations": [             {                 "operationtype": "12",                 "opmessage": {                     "default_msg": 0,                     "message": "Custom update operation message body",                     "subject": "Custom update operation message subject"                 }             }         ],         "pause_suppressed": "0",         "notify_if_canceled": "0"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "actionids": [             "17"         ]     },     "id": 1 } ```

en-us	#### Create a trigger map  Create a map with trigger element, which contains two triggers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Trigger map",         "width": 600,         "height": 600,         "selements": [             {                 "elements": [                     {"triggerid": "12345"},                     {"triggerid": "67890"}                 ],                 "elementtype": 2,                 "iconid_off": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "10"         ]     },     "id": 1 } ```
zh-cn	#### 创建一个触发器拓扑图  创建一个包含两个触发器元素的拓扑图。  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Trigger map",         "width": 600,         "height": 600,         "selements": [             {                 "elements": [                     {"triggerid": "12345"},                     {"triggerid": "67890"}                 ],                 "elementtype": 2,                 "iconid_off": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "10"         ]     },     "id": 1 } ```

en-us	#### Create a webhook script  Create a webhook script that sends HTTP request to external service.  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "Webhook script",         "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}",         "type": 5,         "timeout": "40s",         "parameters": [             {                 "name": "token",                 "value": "{$WEBHOOK.TOKEN}"             },             {                 "name": "host",                 "value": "{HOST.HOST}"             },             {                 "name": "v",                 "value": "2.2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "3"         ]     },     "id": 1 } ```
zh-cn	#### 创建webhook脚本  创建一个webhook脚本向外部服务发送HTTP请求。  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.create",     "params": {         "name": "Webhook script",         "command": "try {\n var request = new HttpRequest(),\n response,\n data;\n\n request.addHeader('Content-Type: application/json');\n\n response = request.post('https://localhost/post', value);\n\n try {\n response = JSON.parse(response);\n }\n catch (error) {\n response = null;\n }\n\n if (request.getStatus() !== 200 || !('data' in response)) {\n throw 'Unexpected response.';\n }\n\n data = JSON.stringify(response.data);\n\n Zabbix.Log(3, '[Webhook Script] response data: ' + data);\n\n return data;\n}\ncatch (error) {\n Zabbix.Log(3, '[Webhook Script] script execution failed: ' + error);\n throw 'Execution failed: ' + error + '.';\n}",         "type": 5,         "timeout": "40s",         "parameters": [             {                 "name": "token",                 "value": "{$WEBHOOK.TOKEN}"             },             {                 "name": "host",                 "value": "{HOST.HOST}"             },             {                 "name": "v",                 "value": "2.2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "3"         ]     },     "id": 1 } ```

en-us	#### Create HTTP agent item  Create POST request method item with JSON response preprocessing.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "url":"http://127.0.0.1/http.php",         "query_fields": [             {                 "mode":"json"             },             {                 "min": "10"             },             {                 "max": "100"             }         ],         "interfaceid": "1",         "type":"19",         "hostid":"10254",         "delay":"5s",         "key_":"json",         "name":"http agent example JSON",         "value_type":"0",         "output_format":"1",         "preprocessing": [             {                 "type": "12",                 "params": "$.random"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```
zh-cn	#### 创建 HTTP agent 监控项  创建 JSON 响应预处理式的 POST 请求方法监控项。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "url":"http://127.0.0.1/http.php",         "query_fields": [             {                 "mode":"json"             },             {                 "min": "10"             },             {                 "max": "100"             }         ],         "interfaceid": "1",         "type":"19",         "hostid":"10254",         "delay":"5s",         "key_":"json",         "name":"http agent example JSON",         "value_type":"0",         "output_format":"1",         "preprocessing": [             {                 "type": "12",                 "params": "$.random"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```

en-us	#### Create HTTP agent item  Create POST request method item with JSON response preprocessing.  Request:  ```json {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "url": "http://127.0.0.1/http.php",         "query_fields": [             {                 "mode": "json"             },             {                 "min": "10"             },             {                 "max": "100"             }         ],         "interfaceid": "1",         "type": 19,         "hostid": "10254",         "delay": "5s",         "key_": "json",         "name": "HTTP agent example JSON",         "value_type": 0,         "output_format": 1,         "preprocessing": [             {                 "type": 12,                 "params": "$.random",                 "error_handler": 0,                 "error_handler_params": ""             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```
zh-cn	#### 创建 HTTP agent 监控项  创建 JSON 响应预处理式的 POST 请求方法监控项。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "item.create",     "params": {         "url":"http://127.0.0.1/http.php",         "query_fields": [             {                 "mode":"json"             },             {                 "min": "10"             },             {                 "max": "100"             }         ],         "interfaceid": "1",         "type":"19",         "hostid":"10254",         "delay":"5s",         "key_":"json",         "name":"http agent example JSON",         "value_type":"0",         "output_format":"1",         "preprocessing": [             {                 "type": "12",                 "params": "$.random"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "23865"         ]     },     "id": 3 } ```

en-us	#### Create HTTP agent item prototype  Create item prototype with URL using user macro, query fields and custom headers.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {         "type": "19",         "hostid": "10254",         "ruleid":"28256",         "interfaceid":"2",         "name": "api item prototype example",         "key_": "api_http_item",         "value_type": "3",         "url": "{$URL_PROTOTYPE}",         "query_fields": [             {                 "min": "10"             },             {                 "max": "100"             }         ],         "headers": {             "X-Source": "api"         },         "delay":"35"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28305"         ]     },     "id": 1 } ```
zh-cn	#### 创建HTTP代理监控项原型  使用用户宏、查询字段和自定义头部创建带有URL的监控项原型。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "type": "19",  · "hostid": "10254",  · "ruleid":"28256",  · "interfaceid":"2",  · "name": "api item prototype example",  · "key_": "api_http_item",  · "value_type": "3",  · "url": "{$URL_PROTOTYPE}",  · "query_fields": [  · {  · "min": "10"  · },  · {  · "max": "100"  · }  · ],  · "headers": {  · "X-Source": "api"  · },  · "delay":"35"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "28305"  · ]  · },  · "id": 1 } ```

en-us	#### Create HTTP agent item prototype  Create item prototype with URL using user macro, query fields and custom headers.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.create",     "params": {         "type": "19",         "hostid": "10254",         "ruleid": "28256",         "interfaceid": "2",         "name": "api item prototype example",         "key_": "api_http_item",         "value_type": 3,         "url": "{$URL_PROTOTYPE}",         "query_fields": [             {                 "min": "10"             },             {                 "max": "100"             }         ],         "headers": {             "X-Source": "api"         },         "delay": "35"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "28305"         ]     },     "id": 1 } ```
zh-cn	#### 创建HTTP代理监控项原型  使用用户宏、查询字段和自定义头部创建带有URL的监控项原型。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.create",  · "params": {  · "type": "19",  · "hostid": "10254",  · "ruleid":"28256",  · "interfaceid":"2",  · "name": "api item prototype example",  · "key_": "api_http_item",  · "value_type": "3",  · "url": "{$URL_PROTOTYPE}",  · "query_fields": [  · {  · "min": "10"  · },  · {  · "max": "100"  · }  · ],  · "headers": {  · "X-Source": "api"  · },  · "delay":"35"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "28305"  · ]  · },  · "id": 1 } ```

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

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

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

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