en-us	 #### Batch migration of history tables  * Prepare directories for Data Pump.  Data Pump must have read and write permissions to these directories.  Example:  ``` {.bash} mkdir -pv /export/history chown -R oracle:oracle /export ```  * Create a directory object and grant read and write permissions to this object to the user used for Zabbix authentication ('zabbix' in the example below). Under *sysdba* role, run:  ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; ```  * Export tables. Replace N with the desired thread count.  ``` {.bash} expdp zabbix/password@oracle_host/service \     DIRECTORY=history \     TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \     PARALLEL=N ```  * Import tables. Replace N with the desired thread count.  ``` {.bash} impdp zabbix/password@oracle_host/service \     DIRECTORY=history \     TABLES=history_uint_old \  REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \     data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND  PARALLEL=N CONTENT=data_only ```  * Follow [post-migration instructions](#after-migration) to drop the old tables.
zh-cn	####历史表批量迁移  * 为数据泵准备目录。  Data Pump 必须对这些目录具有读写权限。  例子：  ``` {.bash} mkdir -pv /export/history chown -R oracle:oracle /export ```  * 创建一个目录对象，并将该对象的读写权限授予用于 Zabbix 身份验证的用户（下例中的“zabbix”）。 在 *sysdba* 角色下，运行：  ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix; ```  * 导出表。 将 N 替换为所需的线程数。  ``` {.bash} expdp zabbix/password@oracle_host/service \  · DIRECTORY=history \  · TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \  · PARALLEL=N ```  * 导入表。 将 N 替换为所需的线程数。  ``` {.bash} impdp zabbix/password@oracle_host/service \  · DIRECTORY=history \  · TABLES=history_uint_old \  REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \  · data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND · PARALLEL=N CONTENT=data_only ```  * 按照 [post-migration instructions](#after-migration) 删除旧表。

en-us	# Best practices for secure Zabbix setup  
zh-cn	# 安全设置 Zabbix 的最佳方式  

en-us	##### Better navigation between item configuration and latest data  A new context menu for items has been introduced in *[Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data)* allowing to access the  item configuration and available graphs:  ![](../../../assets/en/manual/introduction/item_menu_latest.png)  Conversely, a new context menu has been introduced in the [item list](/manual/web_interface/frontend_sections/configuration/hosts/items) in  configuration menu allowing to access the latest data for the item and other useful options:  ![](../../../assets/en/manual/introduction/item_menu_conf.png)  This menu replaces the wizard option in previous versions. A similar menu has  also been introduced for [template items](/manual/web_interface/frontend_sections/configuration/_templates/items)  and [item prototypes](/manual/discovery/low_level_discovery/item_prototypes).
zh-cn	##### 在监控项配置和最新数据之间更好地导航  *[最新数据](/manual/web_interface/frontend_sections/monitoring/latest_data)* 中引入了新的监控项上下文菜单，允许访问监控项配置和可用图表：  ![](../../../assets/en/manual/introduction/item_menu_latest.png)  相反，在配置菜单的 [监控项列表](/manual/web_interface/frontend_sections/configuration/hosts/items) 中引入了一个新的上下文菜单，允许访问监控项的最新数据和其他有用的选项：  ![](../../../assets/en/manual/introduction/item_menu_conf.png)  此菜单取代了以前版本中的向导选项。还为 [模板监控项](/manual/web_interface/frontend_sections/configuration/_templates/items)和 [监控项原型](/manual/discovery/low_level_discovery/item_prototypes) 引入了类似的菜单。

en-us	## Breaking changes
zh-cn	## 重大变化

en-us	 ## Breaking changes
zh-cn	## 重大变化

en-us	 ## Breaking changes
zh-cn	## 重大变化

en-us	 ### Breaking changes  #### Loadable plugin versioning  [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 now use the same versioning system as Zabbix itself.  The following version changes have been made:  - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13  These plugins are supported for any minor version of Zabbix 6.0.  Note that source code repository for each plugin now contains a dedicated *release/6.0* branch (previously, there was only *master* branch).  
zh-cn	### 重大变化  #### 可加载插件版本控制  [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 现在使用与 Zabbix 本身相同的版本控制系统。 进行了以下版本更改：  - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13  Zabbix 6.0 的任何次要版本都支持这些插件。 请注意，每个插件的源代码存储库现在包含一个专用的 *release/6.0* 分支（以前只有 *master* 分支）。 

en-us	 ### Breaking changes  #### Loadable plugin versioning  [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 now use the same versioning system as Zabbix itself. The following version changes have been made:  - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13  These plugins are supported for any minor version of Zabbix 6.0.  Note that source code repository for each plugin now contains a dedicated *release/6.0* branch (previously, there was only *master* branch).  
zh-cn	### 重大变化  #### 可加载插件版本控制  [Loadable plugins](/manual/config/items/plugins#loadable) for Zabbix agent 2 现在使用与 Zabbix 本身相同的版本控制系统。 进行了以下版本更改：  - MongoDB 1.2.0 -> MongoDB 6.0.13 - PostgreSQL 1.2.1 -> PostgreSQL 6.0.13  Zabbix 6.0 的任何次要版本都支持这些插件。 请注意，每个插件的源代码存储库现在包含一个专用的 *release/6.0* 分支（以前只有 *master* 分支）。

en-us	##### BSD systems  If `watch` command is not installed, a similar effect can be achieved with      while [ 1 ]; do ps x; sleep 0.2; clear; done
zh-cn	##### BSD 系统  如果没有安装`watch` 命令 ，可以达到类似的效果      while [ 1 ]; do ps x; sleep 0.2; clear; done

en-us	##### Build 32bit PCRE  1\. Run:      mingw32-make clean  2\. Delete *CMakeCache.txt*:      del CMakeCache.txt     rmdir /q /s CMakeFiles  3\. Run cmake:      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32  4\. Next, run:      mingw32-make install
zh-cn	##### 构建32位PCRE  1\. 运行：      mingw32-make clean  2\. 删除 *CMakeCache.txt*：      del CMakeCache.txt     rmdir /q /s CMakeFiles  3\. 运行cmake：      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32  4\. 接下来，运行：      mingw32-make install

en-us	##### Build 32bit PCRE  1\. Run:      mingw32-make clean  2\. Delete *CMakeCache.txt*:      del CMakeCache.txt     rmdir /q /s CMakeFiles  3\. Run cmake:      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32  4\. Next, run:      mingw32-make install  
zh-cn	##### 构建32位PCRE  1\. 运行：      mingw32-make clean  2\. 删除 *CMakeCache.txt*：      del CMakeCache.txt     rmdir /q /s CMakeFiles  3\. 运行cmake：      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-m32 -O2 -g" -DCMAKE_CXX_FLAGS="-m32 -O2 -g" -DCMAKE_EXE_LINKER_FLAGS="-Wl,-mi386pe" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre32  4\. 接下来，运行：      mingw32-make install

en-us	##### Build 64bit PCRE  1\. Delete old configuration/cache if exists:      del CMakeCache.txt     rmdir /q /s CMakeFiles  2\. Run cmake (CMake can be installed from <https://cmake.org/download/>):      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre  3\. Next, run:      mingw32-make clean     mingw32-make install
zh-cn	##### 构建64位 PCRE  1\. 删除就配置/缓存（如果有）：      del CMakeCache.txt     rmdir /q /s CMakeFiles  2\. 运行 cmake (CMake 可从这里安装<https://cmake.org/download/>):      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre  3\. 接下来，运行：      mingw32-make clean     mingw32-make install

en-us	##### Build 64bit PCRE  1\. Delete old configuration/cache if exists:      del CMakeCache.txt     rmdir /q /s CMakeFiles  2\. Run cmake (CMake can be installed from <https://cmake.org/download/>):      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre  3\. Next, run:      mingw32-make clean     mingw32-make install  
zh-cn	##### 构建64位 PCRE  1\. 删除就配置/缓存（如果有）：      del CMakeCache.txt     rmdir /q /s CMakeFiles  2\. 运行 cmake (CMake 可从这里安装<https://cmake.org/download/>):      cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-O2 -g" -DCMAKE_CXX_FLAGS="-O2 -g" -DCMAKE_INSTALL_PREFIX=c:\dev\pcre  3\. 接下来，运行：      mingw32-make clean     mingw32-make install

en-us	#### Building inventory
zh-cn	#### 构建资产库

en-us	##### - Building modules  Modules are currently meant to be built inside Zabbix source tree, because the module API depends on some data structures that are defined in Zabbix headers.  The most important header for loadable modules is **include/module.h**, which defines these data structures. Other necessary system headers that help **include/module.h** to work properly are **stdlib.h** and **stdint.h**.  With this information in mind, everything is ready for the module to be built. The module should include **stdlib.h**, **stdint.h** and **module.h**, and the build script should make sure that these files are in the include path. See example "dummy" module below for details.  Another useful header is **include/log.h**, which defines **zabbix\_log()** function, which can be used for logging and debugging purposes.
zh-cn	##### - 构建模块  目前，模块应当再ZABBIX源代码树中构建，因为模块API依赖于一些ZABBIX头文件中定义的一些数据结构。\  对可加载模块来说，最重要的头是**include/module.h**，它定义了这些住居结构。另一个很有用的头文件**include/sysinc.h** ，它的执行会包含必要的系统头文件，这有助于include/module.h 的正常工作。\  为了include/module.h 和 include/sysinc.h被导入，应在ZABBIX源代码树的根目录下执行**./configure**命令。这将创建 **include/config.h**文件，其中包含了 include/sysinc.h依赖。（如果你获得的ZABBIX源代码来自子版本存储库，则 ./configure脚本尚不存在，应首先运行 **./bootstrap.sh** 脚本来生成它。）  记住这些信息，一切都准备好了去构建模块。该模块应包含 **sysinc.h** 和**module.h**，构建脚本应确保这两个文件包含于路径中。有关详细信息，参见下文“dummy”模块。\  其它有用的头文件**include/log.h**，它定义了**zabbix\_log()**函数，可用于记录和调试目的。

en-us	### Built-in objects
zh-cn	### 内置对象

en-us	 ##### Bulk processing  Bulk processing is supported for dependent items. To enable caching and indexing,  the *Prometheus pattern* preprocessing must be the **first** preprocessing step.  When *Prometheus pattern* is first preprocessing step then the parsed Prometheus  data is cached and indexed by the first `<label>==<value>` condition in the  *Prometheus pattern* preprocessing step. This cache is reused when processing  other dependent items in this batch. For optimal performance, the first label  should be the one with most different values.  If there is other preprocessing to be done before the first step, it should be  moved either to the master item or to a new dependent item which would be used as  the master item for the dependent items.
zh-cn	##### 批量处理  从属监控项支持批量处理。为了启用缓存和索引，是 *Prometheus 正则匹配* 步骤必须是预处理配置的**第一个**步骤。当 *Prometheus 正则匹配*是预处理的第一步时，经过这个预处理步骤配置的第一组 `<label>==<value>` 条件解析后的Prometheus数据会被缓存并建立索引。这个缓存可以在其他从属监控项的其他后续预处理过程中得到重用。为了更好的优化性能，第一个作为条件的label，应当匹配尽可能多的不同值。  如果有额外的预处理步骤需要在第一步之前执行，正确做法是将该步骤放在主要监控项或者新建一个从属监控项，并将这个监控项作为处理Prometheus数据处理监控项的主监控项。

en-us	##### Bulk processing for Prometheus metrics  As bulk processing of dependent items has been introduced in the preprocessing  queue for Prometheus metrics, dependent items will no longer be processed in  parallel and that may have an affect on how fast they are processed.
zh-cn	##### Prometheus 指标的批量处理  由于在 Prometheus 指标的预处理队列中引入了依赖监控项的批量处理，依赖监控项将不再并行处理，这可能会影响它们的处理速度。

en-us	##### Buttons  |   |   | |---|---| |![](../../../../../assets/en/manual/web_interface/button_clone.png)|Clone the service.<br>When a service is cloned, its parent links are preserved, while the child links are not.|
zh-cn	##### 按钮  | · | · | |---|---| |![](../../../../../assets/en/manual/web_interface/button_clone.png)|克隆服务。<br>克隆服务时，将保留其父链接，但不保留子链接。|

en-us	##### Buttons  Buttons to the right offer the following options:  |   |   | |--|--------| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/edit_map.png)|Go to map constructor to edit the map content.| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/add_to_fav1.png)|Add map to the favorites widget in the [Dashboard](dashboard).| |![](../../../../../assets/en/manual/web_interface/button_add_fav2.png)|The map is in the favorites widget in the [Dashboard](dashboard). Click to remove map from the favorites widget.|  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  右侧的按钮提供以下选项：  | · | · | |---|---| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/edit_map.png)|跳转到聚合图形构造器来编辑聚合图形。| |![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/add_to_fav1.png)|把聚合图形添加到[仪表盘](dashboard)中的“收藏夹”小构件中。| |![](../../../../../assets/en/manual/web_interface/button_add_fav2.png)|在[仪表盘](dashboard)“收藏夹”小构件中的聚合图形。单击会从“收藏夹”中移除聚合图形。|  在[监控](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页介绍了所有部分通用的显示模式按钮。

en-us	##### Buttons  *Create host* allows to create a [new host](/manual/config/hosts/host). This button is available for Admin and Super Admin users only.  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  *创建主机* 允许创建 [新主机](/manual/config/hosts/host)。此按钮仅对管理员和超级管理员用户可用。  [监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页介绍了所有部分通用的视图模式按钮。

en-us	##### Buttons  The button to the right offers the following option:  |   |   | |--|--------| |![](../../../../../assets/en/manual/web_interface/button_csv.png)|Export content from all pages to a CSV file.|  View mode buttons, being common for all sections, are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  右侧的按钮提供以下选项：  | · | · | |---|---| |![](../../../../../assets/en/manual/web_interface/button_csv.png)|将页面所有内容导出到CSV文件。|  在[监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页面介绍了所有通用的查看模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	 ##### 按钮  在 [监测](/manual/web_interface/frontend_sections/monitoring#查看模式按钮) 页面中描述了所有节的常见视图模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监控](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)中介绍了通用的显示模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页上介绍了所有部分通用的显示模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监控](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页介绍了所有部分通用的监控模式按钮。

en-us	##### Buttons  View mode buttons, being common for all sections, are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页上介绍了所有部分通用的视图模式按钮。

en-us	By default, the widget displays all enabled hosts with valid geographical coordinates defined in the host configuration. It is possible to configure host filtering in the widget parameters.  The valid host coordinates are:   - Latitude: from -90 to 90 (can be integer or float number)  - Longitude: from -180 to 180 (can be integer or float number) 
zh-cn	默认情况下，组件会显示所有的已启用且定义了地理坐标的主机。可以在组件参数中配置主机过滤参数。  主机坐标的有效值：  - 纬度：从-90到90（整数或浮点数皆可） - 经度：从-180到180（整数或浮点数皆可）

en-us	#### Calculation time  A trigger is recalculated every time Zabbix server receives a new value that is part of the expression. When a new value is received, each function that is included in the expression is recalculated (not just the one that received the new value).  Additionally, a trigger is recalculated each time when a new value is received **and** every 30 seconds if time-based functions are used in the expression.  Time-based functions are **nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**; they are recalculated every 30 seconds by the Zabbix history syncer process.  Triggers that reference trend functions **only** are evaluated once per  the smallest time period in the expression. See also [trend functions](/manual/appendix/functions/trends).
zh-cn	#### 计算时间  每次 Zabbix 服务器收到作为表达式一部分的新值时，都会重新计算触发器。 当接收到新值时，表达式中包含的每个函数都会重新计算（不仅仅是接收到新值的函数）。  此外，如果在表达式中使用了基于时间的函数，则每次接收到新值**和**每 30 秒重新计算一次触发器。  基于时间的函数是 **nodata()**、**date()**、**dayofmonth()**、**dayofweek()**、**time()**、**now() **; Zabbix 历史同步器进程每 30 秒重新计算一次。  引用趋势函数的触发器**only**在表达式中的每个最小时间段评估一次。 另见 [趋势函数](/manual/appendix/functions/trends)。

en-us	#### Calculation time  A trigger is recalculated every time Zabbix server receives a new value that is part of the expression. When a new value is received, each function that is included in the expression is recalculated (not just the one that received the new value).  Additionally, a trigger is recalculated each time when a new value is received **and** every 30 seconds if time-based functions are used in the expression.  Time-based functions are **nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**); they are recalculated every 30 seconds by the Zabbix history syncer process.  Triggers that reference trend functions **only** are evaluated once per  the smallest time period in the expression. See also [trend functions](/manual/appendix/functions/trends).
zh-cn	#### 计算时间  每次 Zabbix server接收到新值时，都会重新计算一次触发器 这是表达式的一部分。当接收到一个新值时，每个表达式中的函数都会重新计算（不仅仅是收到新值的那个）。  此外，每次出现新值时都会重新计算触发器，以及每30秒重新计算，如果使用了基于时间的函数。  如果在表达式中使用基于时间的函数(**nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**)，触发器就会由Zabbix history syncer进程每30秒重新计算一次。  如果触发器包含趋势数据函数，则根据表达式中最小时间间隔进行评估。 参考 [trend functions](/manual/appendix/functions/trends).

en-us	### Ceph  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |ceph.df.details\[connString,<user>,<apikey>\]|<|<|<| |Cluster’s data usage and distribution among pools.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.stats\[connString,<user>,<apikey>\]|<|<|<| |Aggregated and per OSD statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.discovery\[connString,<user>,<apikey>\]|<|<|<| |List of discovered OSDs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.osd.dump\[connString,<user>,<apikey>\]|<|<|<| |Usage thresholds and statuses of OSDs.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.ping\[connString,<user>,<apikey>\]|<|<|<| |Tests whether a connection to Ceph can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br><br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.pool.discovery\[connString,<user>,<apikey>\]|<|<|<| |List of discovered pools. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| | |ceph.status\[connString,<user>,<apikey>\]|<|<|<| |Overall cluster's status.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.| |
zh-cn	### Ceph  |键值|<|<|<| |--|--|------|------| |**描述**|**返回值**|**参数**|**注释**| |ceph.df.details\[connString,<user>,<apikey>\]|<|<|<| |集群数据在 pool 中的使用和分布。|JSON 对象|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据。| | |ceph.osd.stats\[connString,<user>,<apikey>\]|<|<|<| |聚合和每个 OSD 统计信息。|JSON 对象|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据。| | |ceph.osd.discovery\[connString,<user>,<apikey>\]|<|<|<| |已发现的 OSD 列表。 用于[底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)。|JSON 对象|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据 .| | |ceph.osd.dump\[connString,<user>,<apikey>\]|<|<|<| |OSD 的使用阈值和状态。|JSON 对象|**connString** - URI 或会话名称。<br>**用户、密码** - Ceph 登录凭据。| | |ceph.ping\[connString,<user>,<apikey>\]|<|<|<| |测试是否可以建立与 Ceph 的连接。|0 - 连接断开（如果出现任何错误，包括认证和配置问题）<br><br>1 - 连接成功。|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据。| | |ceph.pool.discovery\[connString,<user>,<apikey>\]|<|<|<| |已发现的pool列表。 用于[底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)。|JSON 对象|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据 .| | |ceph.status\[connString,<user>,<apikey>\]|<|<|<| |整个集群的状态。|JSON 对象|**connString** - URI 或会话名称。<br>**user, password** - Ceph 登录凭据。| |

en-us	#### Certificate configuration parameters  |Parameter|Mandatory|Description| |---------|---------|-----------| |*TLSCAFile*|\*|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.<br>In case of certificate chain with several members they must be ordered: lower level CA certificates first followed by certificates of higher level CA(s).<br>Certificates from multiple CA(s) can be included in a single file.| |*TLSCRLFile*|<|Full pathname of a file containing Certificate Revocation Lists. See notes in [Certificate Revocation Lists (CRL)](/manual/encryption/using_certificates?&#certificate_revocation_lists_crl).| |*TLSCertFile*|\*|Full pathname of a file containing certificate (certificate chain).<br>In case of certificate chain with several members they must be ordered: server, proxy, or agent certificate first, followed by lower level CA certificates then certificates of higher level CA(s).| |*TLSKeyFile*|\*|Full pathname of a file containing private key. Set access rights to this file - it must be readable only by Zabbix user.| |*TLSServerCertIssuer*|<|Allowed server certificate issuer.| |*TLSServerCertSubject*|<|Allowed server certificate subject.|
zh-cn	 #### 证书配置参数  |参数|是否必须|描述| |---------|---------|-----------| |*TLSCAFile*|\*|包含用于对等证书验证的顶级CA证书的文件的完整路径名。在具有多个成员的证书链的情况下，它们必须被排序：较低级别的CA证书，然后是较高级别的CA证书。来自多个CA的证书可以包含在单个文件中。| |*TLSCRLFile*|<|包含证书吊销列表的文件的完整路径名。 看 [证书吊销清单 (CRL)](/manual/encryption/using_certificates?&#certificate_revocation_lists_crl)。| |*TLSCertFile*|\*|包含证书（证书链）的文件的完整路径名。<br>在有几个成员的证书链中，它们必须排序:首先是server、proxy或agent证书，然后是低级CA证书，然后是高级CA证书。| |*TLSKeyFile*|\*|包含私钥的文件的完整路径名。 设置此文件的访问权限—它必须只有Zabbix用户可读。| |*TLSServerCertIssuer*|<|-允许的服务器证书颁发者。| |*TLSServerCertSubject*|<|允许的服务器证书主题。|

en-us	#### Certificate Revocation Lists (CRL)  If a certificate is compromised CA can revoke it by including in CRL. CRLs can be configured in server, proxy and agent configuration file using parameter `TLSCRLFile`. For example:      TLSCRLFile=/home/zabbix/zabbix_crl_file  where `zabbix_crl_file` may contain CRLs from several CAs and look like:      -----BEGIN X509 CRL-----     MIIB/DCB5QIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixkARkWA2Nv     ...     treZeUPjb7LSmZ3K2hpbZN7SoOZcAoHQ3GWd9npuctg=     -----END X509 CRL-----     -----BEGIN X509 CRL-----     MIIB+TCB4gIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQBGRYDY29t     ...     CAEebS2CND3ShBedZ8YSil59O6JvaDP61lR5lNs=     -----END X509 CRL-----  CRL file is loaded only on Zabbix start. CRL update requires restart.  ::: noteimportant  If Zabbix component is compiled with *OpenSSL* and CRLs are used then each top and intermediate level CA in certificate chains must have a corresponding CRL (it can be empty) in `TLSCRLFile`.  :::
zh-cn	#### 证书撤销列表(CRL) 如果证书被破坏，CA可以通过将其包含在CRL中来撤销它。 CRLs 可以通过“TLSCRLFile”参数在server、proxy和agent配置文件中配置。 例如:      TLSCRLFile=/home/zabbix/zabbix_crl_file  其中' zabbix_crl_file '可能包含来自多个CAs的CRLs，如下所示:      -----BEGIN X509 CRL-----     MIIB/DCB5QIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixkARkWA2Nv     ...     treZeUPjb7LSmZ3K2hpbZN7SoOZcAoHQ3GWd9npuctg=     -----END X509 CRL-----     -----BEGIN X509 CRL-----     MIIB+TCB4gIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQBGRYDY29t     ...     CAEebS2CND3ShBedZ8YSil59O6JvaDP61lR5lNs=     -----END X509 CRL-----  CRL文件只在Zabbix启动时加载。 更新CRL需要重新启动。  ::: noteimportant  如果Zabbix组件是用*OpenSSL*编译的，并且使用了CRLs，那么证书链中的每个顶级和中级CA必须在' TLSCRLFile'中有一个对应的CRL(可以为空)。  :::

en-us	##### Change count  A new [history function](/manual/appendix/functions/history) **changecount()** has been added allowing to count the number of changes between adjacent values. The function supports three different modes for counting all changes, only decreases, or only increases. As an example, it can be used to track changes in the number of users or the number of system uptime decreases.
zh-cn	##### 更改计数  添加了一个新的 [历史函数](/manual/appendix/functions/history)**changecount()** ，允许计算相邻值之间的更改次数。该函数支持三种不同的模式：计算所有变化，只减少，或者只增加。例如，它可用于跟踪用户数量的变化或系统正常运行时间的减少。

en-us	#### Change dashboard owner  Available only for admins and super admins.  Request:  ```json {     "jsonrpc": "2.0",     "method": "dashboard.update",     "params": {         "dashboardid": "2",         "userid": "1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```
zh-cn	#### 变更仪表盘所有者  仅适用于管理员以及超级管理员用户。  请求：  ```json {     "jsonrpc": "2.0",     "method": "dashboard.update",     "params": {         "dashboardid": "2",         "userid": "1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "dashboardids": [             "2"         ]     },     "id": 2 } ```

en-us	#### Change hosts monitored by a proxy  Update the proxy to monitor the two given hosts.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "hosts": [             "10294",             "10295"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```  
zh-cn	#### Change hosts monitored by a proxy 改变一个主机的代理  Update the proxy to monitor the two given hosts.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "hosts": [             "10294",             "10295"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```  

en-us	#### Change hosts monitored by a proxy  Update the proxy to monitor the two given hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "hosts": [             {                 "hostid": "10294"             },             {                 "hostid": "10295"             },         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```
zh-cn	#### 更改proxy监控的主机  更新proxy以监视两个给定主机。  请求：  ```json {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "hosts": [             "10294",             "10295"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```

en-us	#### Change map owner  Available only for admins and super admins.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.update",     "params": {         "sysmapid": "9",         "userid": "1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "9"         ]     },     "id": 2 } ```
zh-cn	#### 改变拓扑图的拥有者  仅适用于管理员和超级管理员  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.update",     "params": {         "sysmapid": "9",         "userid": "1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 2 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "9"         ]     },     "id": 2 } ```

en-us	#### Change proxy status  Change the proxy to an active proxy and rename it to "Active proxy".  Request:  ```json {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "host": "Active proxy",         "status": "5"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```
zh-cn	#### 更改proxy状态  将代理更改为主动proxy，并重命名为“Active proxy”。  请求：  ```json {     "jsonrpc": "2.0",     "method": "proxy.update",     "params": {         "proxyid": "10293",         "host": "Active proxy",         "status": "5"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "proxyids": [             "10293"         ]     },     "id": 1 } ```

en-us	#### Change script command  Change the command of the script to "/bin/ping -c 10 {HOST.CONN} 2>&1".  Request:  ```json {     "jsonrpc": "2.0",     "method": "script.update",     "params": {         "scriptid": "1",         "command": "/bin/ping -c 10 {HOST.CONN} 2>&1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 修改脚本命令  把脚本命令修改为“/bin/ping -c 10 {HOST.CONN} 2>&1”。  请求：  ```json {     "jsonrpc": "2.0",     "method": "script.update",     "params": {         "scriptid": "1",         "command": "/bin/ping -c 10 {HOST.CONN} 2>&1"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "scriptids": [             "1"         ]     },     "id": 1 } ```

en-us	#### CHANGES IN 6.0.0
zh-cn	#### 在6.0.0中的变化

en-us	 #### CHANGES IN 6.0.13  New templates are available:  - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).
zh-cn	#### 6.0.13 中的变化  新模板可用：  - AWS EC2 by HTTP - AWS by HTTP - AWS RDS instance by HTTP - AWS S3 bucket by HTTP  请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http) 的设置说明。

en-us	#### CHANGES IN 6.0.2  The template *Generic Java JMX* now contains two discovery rules:  - Garbage collector discovery - Memory pool discovery
zh-cn	#### 在6.0.2中的变化  模板*Generic Java JMX*现在包含两个发现规则： - Garbage collector discovery - Memory pool discovery

en-us	#### CHANGES IN 6.0.3  A new template *OpenWeatherMap by HTTP* is available.  The following changes have been made in the existing templates:  - In the templates *Windows services by Zabbix agent*, *Windows services by Zabbix agent active*,  *Windows by Zabbix agent*, *Windows by Zabbix agent active*  {$SERVICE.NAME.NOT_MATCHES} macro value has been updated to filter out an extended list of services.   - The template *PostgreSQL by Zabbix agent 2* now will check the number of slow queries and generate a problem if the amount exceeds a threshold.
zh-cn	#### 在6.0.3中的变化  可使用新的模板*OpenWeatherMap by HTTP*。  对现有模板进行了以下更改:  - 在模板*Windows services by Zabbix agent*, *Windows services by Zabbix agent active*,  *Windows by Zabbix agent*, *Windows by Zabbix agent active*中 {$SERVICE.NAME.NOT_MATCHES}宏值已被更新，以过滤掉扩展的服务列表。  - 模版*PostgreSQL by Zabbix agent 2* 现在将检查慢速查询的数量，如果数量超过阈值将产生问题。

en-us	#### CHANGES IN 6.0.4  New templates are available:  - *TrueNAS SNMP* - monitoring of TrueNAS storage OS by SNMP - *Proxmox VE by HTTP* - see setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http)  The templates *SMART by Zabbix agent 2* and *SMART by Zabbix agent 2 (active)* have been updated:  - the *Attribute discovery* LLD rule has been deleted, whereas the *Disk discovery* LLD rule will now discover disks based on the pre-defined vendor-specific set of attributes; - **smart.disk.get** item can now return information about a specific disk only, instead of all disks.     New macros allowing to define warning and critical thresholds of the filesystem utilization for virtual file system monitoring have been added to the templates  *HOST-RESOURCES-MIB storage SNMP*,  *Linux by Prom*,  *Linux filesystems SNMP*,  *Linux filesystems by Zabbix agent active*,  *Linux filesystems by Zabbix agent*,  *Mellanox SNMP*,  *PFSense SNMP*,  *Windows filesystems by Zabbix agent active*, *Windows filesystems by Zabbix agent*. Filesystem utilization triggers have been updated to use these macros. 
zh-cn	#### 在6.0.4中的变化  可用的新模版：  - *TrueNAS SNMP* - 通过SNMP监控TrueNAS存储操作系统。 - *Proxmox VE by HTTP* - 参见[HTTP模板](/manual/config/templates_out_of_the_box/http)的设置说明。  模版 *SMART by Zabbix agent 2* and *SMART by Zabbix agent 2 (active)* 已更新：  - *Attribute discovery* LLD规则已被删除，而*Disk discovery*LLD规则现在将基于预定义的特定厂商的属性集发现磁盘； - **smart.disk.get** 项现在只能返回关于特定磁盘的信息，而不是所有磁盘的信息。  模板中添加了新的宏，用于定义用于监控虚拟文件系统的文件系统利用率的警告和临界阈值。 *HOST-RESOURCES-MIB storage SNMP*,  *Linux by Prom*,  *Linux filesystems SNMP*,  *Linux filesystems by Zabbix agent active*,  *Linux filesystems by Zabbix agent*,  *Mellanox SNMP*,  *PFSense SNMP*,  *Windows filesystems by Zabbix agent active*, *Windows filesystems by Zabbix agent*. 为使用这些宏文件系统利用率触发器已经更新。

en-us	 #### CHANGES IN 6.0.5  New templates are available:  - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).
zh-cn	#### 6.0.5 中的变化  新模板可用：  - CockroachDB by HTTP - Envoy Proxy by HTTP - HashiCorp Consul Cluster by HTTP - HashiCorp Consul Node by HTTP  请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http) 的设置说明。

en-us	 #### CHANGES IN 6.0.6  New templates are available:  - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP  See setup instructions for [HTTP templates](/manual/config/templates_out_of_the_box/http).
zh-cn	#### 6.0.6 中的变化  新模板可用：  - HPE MSA 2040 Storage by HTTP - HPE MSA 2060 Storage by HTTP - HPE Primera by HTTP  请参阅 [HTTP 模板](/manual/config/templates_out_of_the_box/http) 的设置说明。

en-us	 #### CHANGES IN 6.0.7  A new [template](/manual/config/templates_out_of_the_box/http) *HPE Synergy by HTTP* is available.  The templates *HashiCorp Consul Node by HTTP* and *HashiCorp Consul Cluster by HTTP* now support Consul namespaces. 
zh-cn	#### 6.0.7 中的变化  新的[模板](/manual/config/templates_out_of_the_box/http) *HPE Synergy by HTTP* 可用。  模板 *HashiCorp Consul Node by HTTP* 和 *HashiCorp Consul Cluster by HTTP* 现在支持 Consul 命名空间。

en-us	 #### CHANGES IN 6.0.8  A new [template](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense by SNMP* is available.
zh-cn	#### 6.0.8 中的变化  一个新的[模板](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/opnsense_snmp?at=refs%2Fheads%2Frelease%2F6.0) *OPNsense by SNMP* 是可用的。

en-us	##### Changes in templates  -   The {\#FSLABEL} macro has been added to the corresponding item names     and descriptions in *Windows by Zabbix agent* and *Windows by Zabbix     agent active* templates -   The vfs.file.cksum\[/etc/passwd\] agent item has been changed to     vfs.file.cksum\[/etc/passwd,sha256\] -   A new check zabbix\[process,odbc poller,avg,busy\] has been added to *Zabbix server*, *Zabbix proxy*, *Remote Zabbix server* and *Remote Zabbix proxy* templates. The metric is used for monitoring the average time for which ODBC processes have been busy during the last minute (in percentage).
zh-cn	##### 模版的变化  -   {\#FSLABEL}宏已添加到对应的项目名称和描述在*Windows by Zabbix agent*和*Windows by Zabbix agent active*模板中 -   vfs.file.cksum\[/etc/passwd\] 代理项目已经被更改成 vfs.file.cksum\[/etc/passwd,sha256\] -   A new check zabbix\[process,odbc poller,avg,busy\] has been added to *Zabbix server*, *Zabbix proxy*, *Remote Zabbix server* and *Remote Zabbix proxy* templates. The metric is used for monitoring the average time for which ODBC processes have been busy during the last minute (in percentage).一个新的检查zabbix\[process,odbc poller,avg,busy]已添加到*Zabbix server*, *Zabbix proxy*, *Remote Zabbix server* 和*Remote Zabbix proxy*模板。该指标用于监视ODBC进程在最后一分钟内忙碌的平均时间(百分比)。

en-us	#### - Changes to AlmaLinux 8 configuration  The appliance is based on AlmaLinux 8. There are some changes applied to the base AlmaLinux configuration.
zh-cn	#### - 对 AlmaLinux 8 配置的更改  Appliance 基于 AlmaLinux 8。有一些配置与基本的 AlmaLinux 设置有一定区别。

en-us	##### - Changes to Zabbix configuration  -   Frontend timezone is set to Europe/Riga (this can be modified in     **/etc/php-fpm.d/zabbix.conf**);
zh-cn	##### - 对 Zabbix 配置的更改  -   前端时区已被设置为 Europe/Riga （可以在 **/etc/php-fpm.d/zabbix.conf** 中修改）；

en-us	#### Change the IP range of a discovery rule  Change the IP range of a discovery rule to "192.168.2.1-255".  Request:  ```json {     "jsonrpc": "2.0",     "method": "drule.update",     "params": {         "druleid": "6",         "iprange": "192.168.2.1-255"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "6"         ]     },     "id": 1 } ```
zh-cn	#### 更改发现规则的IP范围  将发现规则的IP范围更改为“192.168.2.1-255”。  请求：  ```json {     "jsonrpc": "2.0",     "method": "drule.update",     "params": {         "druleid": "6",         "iprange": "192.168.2.1-255"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "druleids": [             "6"         ]     },     "id": 1 } ```

en-us	#### Changing a host interface port  Change the port of a host interface.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.update",     "params": {         "interfaceid": "30048",         "port": "30050"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30048"         ]     },     "id": 1 } ```
zh-cn	#### 更新主机接口端口  更新主机接口的端口  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostinterface.update",     "params": {         "interfaceid": "30048",         "port": "30050"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "interfaceids": [             "30048"         ]     },     "id": 1 } ```

en-us	 ##### Changing dependency for inherited triggers disabled  The possibility to change dependencies for triggers inherited from a template is now disabled.  The reason is that upon updating the dependencies of a template trigger, the dependencies of  inherited triggers are overwritten. Thus it is more reliable always to set trigger dependencies  only on the root template level.
zh-cn	##### 禁用更改继承触发器的依赖项  禁用了更改从模板继承的触发器的依赖关系的功能。  原因是在更新模板的触发器依赖关系时，继承触发器的依赖关系被覆盖。  因此，始终仅在根模板级别设置触发器依赖更可靠。

en-us	#### Changing event's severity  Change severity for multiple events and leave a message.  Request:  ```json {     "jsonrpc": "2.0",     "method": "event.acknowledge",     "params": {         "eventids": ["20427", "20428"],         "action": 12,         "message": "Maintenance required to fix it.",         "severity": 4     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "eventids": [             "20427",             "20428"         ]     },     "id": 1 } ```
zh-cn	#### 更改事件的严重性  更改多个事件的严重性并留言。  请求:  ```json {     "jsonrpc": "2.0",     "method": "event.acknowledge",     "params": {     "eventids": ["20427", "20428"],     "action": 12,     "message": "Maintenance required to fix it.",     "severity": 4     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {     "eventids": [     "20427",     "20428"     ]     },     "id": 1 } ```   

en-us	#### Changing mappings for one value map.  Request:  ```json {     "jsonrpc": "2.0",     "method": "valuemap.update",     "params": {         "valuemapid": "2",         "mappings": [             {                 "type": "0",                 "value": "0",                 "newvalue": "Online"             },             {                 "type": "0",                 "value": "1",                 "newvalue": "Offline"             }         ]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "2"         ]     },     "id": 1 } ```
zh-cn	#### 更新一个值映射的映射关系。  请求：  ```json {     "jsonrpc": "2.0",     "method": "valuemap.update",     "params": {         "valuemapid": "2",         "mappings": [             {                 "type": "0",                 "value": "0",                 "newvalue": "Online"             },             {                 "type": "0",                 "value": "1",                 "newvalue": "Offline"             }         ]     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "2"         ]     },     "id": 1 } ```

en-us	#### Changing proxy setting  The hosts discovered by different proxies are always treated as different hosts. While this allows to perform discovery on matching IP ranges used by different subnets, changing proxy for an already monitored subnet is complicated because the proxy changes must be also applied to all discovered hosts.  For example the steps to replace proxy in a discovery rule:  1.  disable discovery rule 2.  sync proxy configuration 3.  replace the proxy in the discovery rule 4.  replace the proxy for all hosts discovered by this rule 5.  enable discovery rule
zh-cn	#### 更改proxy设置  通过不同的proxy发现的主机始终被视为不同的主机。即便这种操作可以对不同的子网执行自动发现，但是为一个已纳入监控的子网替换proxy也很复杂，因为proxy的变更会同时应用到所有已发现的主机上。  比如下面在发现规则中替换proxy的步骤：  1.  禁用规则 2.  同步proxy配置 3.  替换规则中的proxy 4.  替换此规则发现的所有主机的proxy 5.  启用规则

en-us	#### Changing the excluded downtimes for an SLA  Add a planned 4 hour long RAM upgrade downtime on the 6th of April, 2022, while keeping (needs to be defined anew) a previously existing software upgrade planned on the 4th of July for the SLA with ID "5".  Request:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "slaid": "5",         "excluded_downtimes": [             {                 "name": "Software version upgrade rollout",                 "period_from": "1648760400",                 "period_to": "1648764900"             },             {                 "name": "RAM upgrade",                 "period_from": "1649192400",                 "period_to": "1649206800"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 更改 SLA 的排除停机时间  对于ID为“5”的 SLA，添加在2022年4月6日计划的4小时 RAM 升级停机时间，同时保留（需要重新定义）先前存在的7月4日软件升级计划。  请求:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "slaid": "5",         "excluded_downtimes": [             {                 "name": "Software version upgrade rollout",                 "period_from": "1648760400",                 "period_to": "1648764900"             },             {                 "name": "RAM upgrade",                 "period_from": "1649192400",                 "period_to": "1649206800"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Changing the interface of an item prototype  Change the host interface that will be used by discovered items.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "27428",         "interfaceid": "132"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27428"         ]     },     "id": 1 } ```
zh-cn	#### 修改监控项原型接口  修改自动发现监控项的主机接口。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "27428",  · "interfaceid": "132"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "27428"  · ]  · },  · "id": 1 } ```

en-us	#### Changing the interface of an item prototype  Change the host interface that will be used by discovered items.  Request:  ```json {     "jsonrpc": "2.0",     "method": "itemprototype.update",     "params": {         "itemid": "27428",         "interfaceid": "132"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "27428"         ]     },     "id": 1 } ```
zh-cn	#### 修改监控项原型接口  修改自动发现监控项的主机接口。  请求:  ``` {.java} {  · "jsonrpc": "2.0",  · "method": "itemprototype.update",  · "params": {  · "itemid": "27428",  · "interfaceid": "132"  · },  · "auth": "038e1d7b1735c6a5436ee9eae095879e",  · "id": 1 } ```  返回:  ``` {.java} {  · "jsonrpc": "2.0",  · "result": {  · "itemids": [  · "27428"  · ]  · },  · "id": 1 } ```

en-us	#### Changing the schedule of an SLA  Switch the SLA with ID "5" to a 24x7 schedule.  Request:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "slaid": "5",         "schedule": []     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```
zh-cn	#### 更改 SLA 计划  将 ID 为“5”的 SLA 切换为 24x7 计划。  请求:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "slaid": "5",         "schedule": []     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "slaids": [             "5"         ]     },     "id": 1 } ```

en-us	#### Changing the size of a graph prototype  Change the size of a graph prototype to 1100 to 400 pixels.  Request:  ```json {     "jsonrpc": "2.0",     "method": "graphprototype.update",     "params": {         "graphid": "439",         "width": 1100,         "height": 400     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "439"         ]     },     "id": 1 } ```
zh-cn	#### 改变图表原型的大小  将图表原型的大小改为 1100 * 400 像素。  请求： ```json {     "jsonrpc": "2.0",     "method": "graphprototype.update",     "params": {         "graphid": "439",         "width": 1100,         "height": 400     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应： ```json {     "jsonrpc": "2.0",     "result": {         "graphids": [             "439"         ]     },     "id": 1 } ```

en-us	#### Changing the value of a global macro  Change the value of a global macro to "public".  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.updateglobal",     "params": {         "globalmacroid": "1",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 变更一个全局宏的值  变更全局宏"public"的值.  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.updateglobal",     "params": {         "globalmacroid": "1",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "globalmacroids": [             "1"         ]     },     "id": 1 } ```

en-us	#### Changing the value of a host macro  Change the value of a host macro to "public".  Request:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.update",     "params": {         "hostmacroid": "1",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "1"         ]     },     "id": 1 } ```
zh-cn	#### 更改一个主机宏的值  更改一个主机宏"public"的值.  请求:  ```json {     "jsonrpc": "2.0",     "method": "usermacro.update",     "params": {         "hostmacroid": "1",         "value": "public"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "hostmacroids": [             "1"         ]     },     "id": 1 } ```

en-us	##### - Changing time zone  By default the appliance uses UTC for the system clock. To change the time zone, copy the appropriate file from */usr/share/zoneinfo* to */etc/localtime*, for example:      cp /usr/share/zoneinfo/Europe/Riga /etc/localtime
zh-cn	##### - 更改时区  应用默认使用 UTC 作为系统时钟。如需更改时区，那么从 */usr/share/zoneinfo* 中复制合适的文件到  */etc/localtime* 中，例如：      cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

en-us	#### Changing user role  Change a role of a user.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.update",     "params": {         "userid": "12",         "roleid": "6"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "12"         ]     },     "id": 1 } ```
zh-cn	#### 变更用户角色  变更一个用户的角色.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.update",     "params": {         "userid": "12",         "roleid": "6"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": {         "userids": [             "12"         ]     },     "id": 1 } ```

en-us	#### Changing value map name  Change value map name to "Device status".  Request:  ```json {     "jsonrpc": "2.0",     "method": "valuemap.update",     "params": {         "valuemapid": "2",         "name": "Device status"     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "2"         ]     },     "id": 1 } ```
zh-cn	#### 更新值映射名称  将值映射名称更新为“Device status”。  请求：  ```json {     "jsonrpc": "2.0",     "method": "valuemap.update",     "params": {         "valuemapid": "2",         "name": "Device status"     },     "auth": "57562fd409b3b3b9a4d916d45207bbcb",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "valuemapids": [             "2"         ]     },     "id": 1 } ```

en-us	### 'Check now' request object  The 'Check now' task request object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|ID of item and low-level discovery rules.|
zh-cn	### “立即检查”请求对象  “立即检查”任务请求对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |itemid|string|监控项和低级别自动发现规则的ID。|

en-us	### 'Check now' request object  The 'Check now' task request object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |itemid|string|ID of item and low-level discovery rules.|
zh-cn	### “立即检查”请求对象  “立即检查”任务请求对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |itemid|string|监控项和低级别自动发现规则的ID。|

en-us	#### Check of pre-requisites  Make sure that all software prerequisites are met.  ![](../../../assets/en/manual/installation/install_2.png){width="550"}  |Pre-requisite|Minimum value|Description| |-------------|-------------|-----------| |*PHP version*|7.2.5| | |*PHP memory\_limit option*|128MB|In php.ini:<br>memory\_limit = 128M| |*PHP post\_max\_size option*|16MB|In php.ini:<br>post\_max\_size = 16M| |*PHP upload\_max\_filesize option*|2MB|In php.ini:<br>upload\_max\_filesize = 2M| |*PHP max\_execution\_time option*|300 seconds (values 0 and -1 are allowed)|In php.ini:<br>max\_execution\_time = 300| |*PHP max\_input\_time option*|300 seconds (values 0 and -1 are allowed)|In php.ini:<br>max\_input\_time = 300| |*PHP session.auto\_start option*|must be disabled|In php.ini:<br>session.auto\_start = 0| |*Database support*|One of: MySQL, Oracle, PostgreSQL.|One of the following modules must be installed:<br>mysql, oci8, pgsql| |*bcmath*| |php-bcmath| |*mbstring*| |php-mbstring| |*PHP mbstring.func\_overload option*|must be disabled|In php.ini:<br>mbstring.func\_overload = 0| |*sockets*| |php-net-socket. Required for user script support.| |*gd*|2.0.28|php-gd. PHP GD extension must support PNG images (*--with-png-dir*), JPEG (*--with-jpeg-dir*) images and FreeType 2 (*--with-freetype-dir*).| |*libxml*|2.6.15|php-xml| |*xmlwriter*| |php-xmlwriter| |*xmlreader*| |php-xmlreader| |*ctype*| |php-ctype| |*session*| |php-session| |*gettext*| |php-gettext<br>Since Zabbix 2.2.1, the PHP gettext extension is not a mandatory requirement for installing Zabbix. If gettext is not installed, the frontend will work as usual, however, the translations will not be available.|  Optional pre-requisites may also be present in the list. A failed optional prerequisite is displayed in orange and has a *Warning* status. With a failed optional pre-requisite, the setup may continue.  ::: noteimportant If there is a need to change the Apache user or user group, permissions to the session folder must be verified. Otherwise Zabbix setup may be unable to continue. :::
zh-cn	#### 先决条件检查  确保满足所有软件先决条件。  ![](../../../assets/en/manual/installation/install_2.png){width="550"}  |先决条件|最小值|描述| |-------------|-------------|------------| |*PHP 版本*|7.2.5|<| |*PHP memory\_limit 选项*|128MB|在 php.ini 中：<br>memory\_limit = 128M| |*PHP post\_max\_size 选项*|16MB|在 php.ini 中：<br>post\_max\_size = 16M| |*PHP upload\_max\_filesize 选项*|2MB|在 php.ini 中：<br>upload\_max\_filesize = 2M| |*PHP max\_execution\_time 选项*|300 秒（允许值 0 和 -1）|在 php.ini 中：<br>max\_execution\_time = 300| |*PHP max\_input\_time 选项*|300 秒（允许值 0 和 -1）|在 php.ini 中：<br>max\_input\_time = 300| |*PHP session.auto\_start 选项*|必须禁用|在 php.ini:<br>session.auto\_start = 0| |*数据库支持*|其中之一：MySQL、Oracle、PostgreSQL。|必须安装以下模块之一：<br>mysql、oci8、pgsql| |*bcmath*|<|php-bcmath| |*mbstring*|<|php-mbstring| |*PHP mbstring.func\_overload 选项*|必须禁用|在 php.ini:<br>mbstring.func\_overload = 0| |*sockets*|<|php-net-socket.需要用户脚本支持。| |*gd*|2.0.28|php-gd. PHP GD 扩展必须支持 PNG 图像 (*--with-png-dir*)、JPEG (*--with-jpeg-dir*) 图像和 FreeType 2 (*--with-freetype-dir*)。| |*libxml*|2.6.15|php-xml| |*xmlwriter*|<|php-xmlwriter| |*xmlreader*|<|php-xmlreader| |*ctype*|<|php-ctype| |*session*|<|php-session| |*gettext*|<|php-gettext<br>自 Zabbix 2.2.1 起，PHP gettext 扩展不是安装 Zabbix 的强制要求。如果未安装 gettext，前端将照常工作，但是翻译将不可用。|  可选的先决条件也会罗列在列表中。一个失败的可选先决条件会显示为橙色，并具有*Warning*的状态。如果可选先决条件不满足，安装程序也可以继续进行。  ::: noteimportant 若需要更改 Apache 的用户或用户组，则必须验证会话文件夹的权限。否则 Zabbix 的安装将无法继续。 :::

en-us	#### Check status of nodes at specific IP addresses  Request:  ```json {     "jsonrpc": "2.0",     "method": "hanode.get",     "params": {         "output": ["name", "status"],         "filter": {             "address": ["192.168.1.7", "192.168.1.13"]         }     },     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": [         {             "name": "node3",             "status": "0"         },         {             "name": "node-active",             "status": "3"         }     ],     "id": 1 } ```
zh-cn	#### 检查特定IP地址的节点的状态  请求： ```json {     "jsonrpc": "2.0",     "method": "hanode.get",     "params": {         "output": ["name", "status"],         "filter": {             "address": ["192.168.1.7", "192.168.1.13"]         }     },     "auth": "3a57200802b24cda67c4e4010b50c065",     "id": 1 } ```  响应： ```json {     "jsonrpc": "2.0",     "result": [         {             "name": "node3",             "status": "0"         },         {             "name": "node-active",             "status": "3"         }     ],     "id": 1 } ```

en-us	#### Chromium for Zabbix web service on Ubuntu 20  Though in most cases, Zabbix web service can run with Chromium, on Ubuntu 20.04 using Chromium causes the following error:      Cannot fetch data: chrome failed to start:cmd_run.go:994:     WARNING: cannot create user data directory: cannot create      "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied     Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details.  This error occurs because `/var/lib/zabbix` is used as a home directory of user 'zabbix'.
zh-cn	#### 在 Ubuntu 20 上使用 Chromium 运行 Zabbix web  尽管在大多数情况下，Zabbix Web 服务可以使用 Chromium 运行，但在 Ubuntu 20.04 上使用 Chromium 会导致以下错误：      Cannot fetch data: chrome failed to start:cmd_run.go:994:     WARNING: cannot create user data directory: cannot create "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied     Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details.  发生此错误是因为 `/var/lib/zabbix` 已经被用作用户 'zabbix' 的主目录。

en-us	#### Ciphersuites  Ciphersuites by default are configured internally during Zabbix startup and, before Zabbix 4.0.19, 4.4.7, are not user-configurable.  Since Zabbix 4.0.19, 4.4.7 also user-configured ciphersuites are supported for GnuTLS and OpenSSL. Users may [configure](#user-configured_ciphersuites) ciphersuites according to their security policies. Using this feature is optional (built-in default ciphersuites still work).  For crypto libraries compiled with default settings Zabbix built-in rules typically result in the following ciphersuites (in order from higher to lower priority):  |Library|Certificate ciphersuites|PSK ciphersuites| |-------|------------------------|----------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA|
zh-cn	#### 密码套件  默认情况下，密码套件是在Zabbix启动期间内部配置的，在Zabbix 4.0.19和4.4.7之前是不能由用户配置的。  从Zabbix 4.0.19，4.4.7开始也支持GnuTLS和OpenSSL用户配置的密码套件。用户可以根据他们的安全策略[配置](#user-configured_ciphersuites)密码套件。使用这个特性是可选的(内置的默认密码套件仍然可以使用)。  对于使用默认设置编译的加密库，Zabbix内置规则通常会导致以下加密套件(按优先级由高到低的顺序):  |库|证书密码套件|PSK密码套件| |-------|------------------------|----------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA|

en-us	#### Clear history  Request:  ```json {     "jsonrpc": "2.0",     "method": "history.clear",     "params": [         "10325",         "13205"     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "10325",             "13205"         ]     },     "id": 1 } ```
zh-cn	#### 删除历史数据  请求:  ```json {     "jsonrpc": "2.0",     "method": "history.clear",     "params": [         "10325",         "13205"     ],     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "10325",             "13205"         ]     },     "id": 1 } ```

en-us	##### Collapsed menu  When the menu is collapsed to icons only, a full menu reappears as soon as the mouse cursor is placed upon it. Note that it reappears over page content; to move page content to the right you have to click on the expand button. If the mouse cursor again is placed outside the full menu, the menu will collapse again after two seconds.  You can also make a collapsed menu reappear fully by hitting the Tab key. Hitting the Tab key repeatedly will allow to focus on the next menu element.
zh-cn	##### 折叠菜单  当菜单折叠成图标时，完整的菜单会在光标移动到菜单上方时重新显示。请注意菜单会在 页面内容的上方显示；要把页面内容移到右边，你需要点击扩展按钮。如果光标又移动到 完整菜单的外部，菜单在两秒后又会折叠。  你也可以按Tab键使折叠的菜单重新显示。重复按Tab键会允许聚焦到下一个菜单元素。

en-us	##### Column configuration  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.2.png){width="600"}
zh-cn	##### 列配置  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.2.png){width="600"}

en-us	#### Command-line based installation
zh-cn	#### 命令行安装 

en-us	#### Command-line based installation  
zh-cn	#### 命令行安装 

en-us	[comment]: # attributes: noaside  # 11 Recipes for monitoring
zh-cn	# 11 监控方法

en-us	[comment]: # (tags: proxy) # 4 Proxy
zh-cn	[comment]: # (tags: proxy) # 4 Proxy

en-us	#### Common agent items supported on Windows  |Item key|User group|<| |--------|----------|-| | |Recommended|Minimum technically acceptable (functionality is limited)| |agent.hostname|Guests|Guests| |agent.ping|Guests|Guests| |agent.variant|Guests|Guests| |agent.version|Guests|Guests| |log|Administrators|Guests| |log.count|Administrators|Guests| |logrt|Administrators|Guests| |logrt.count|Administrators|Guests| |net.dns|Guests|Guests| |net.dns.record|Guests|Guests| |net.if.discovery|Guests|Guests| |net.if.in|Guests|Guests| |net.if.out|Guests|Guests| |net.if.total|Guests|Guests| |net.tcp.listen|Guests|Guests| |net.tcp.port|Guests|Guests| |net.tcp.service|Guests|Guests| |net.tcp.service.perf|Guests|Guests| |net.udp.service|Guests|Guests| |net.udp.service.perf|Guests|Guests| |proc.num|Administrators|Guests| |system.cpu.discovery|Performance Monitor Users|Performance Monitor Users| |system.cpu.load|Performance Monitor Users|Performance Monitor Users| |system.cpu.num|Guests|Guests| |system.cpu.util|Performance Monitor Users|Performance Monitor Users| |system.hostname|Guests|Guests| |system.localtime|Guests|Guests| |system.run|Administrators|Guests| |system.sw.arch|Guests|Guests| |system.swap.size|Guests|Guests| |system.uname|Guests|Guests| |system.uptime|Performance Monitor Users|Performance Monitor Users| |vfs.dir.count|Administrators|Guests| |vfs.dir.get|Administrators|Guests| |vfs.dir.size|Administrators|Guests| |vfs.file.cksum|Administrators|Guests| |vfs.file.contents|Administrators|Guests| |vfs.file.exists|Administrators|Guests| |vfs.file.md5sum|Administrators|Guests| |vfs.file.regexp|Administrators|Guests| |vfs.file.regmatch|Administrators|Guests| |vfs.file.size|Administrators|Guests| |vfs.file.time|Administrators|Guests| |vfs.fs.discovery|Administrators|Guests| |vfs.fs.size|Administrators|Guests| |vm.memory.size|Guests|Guests| |web.page.get|Guests|Guests| |web.page.perf|Guests|Guests| |web.page.regexp|Guests|Guests| |zabbix.stats|Guests|Guests|
zh-cn	 #### Windows 上支持的常用 agent 监控项  |监控项 key|用户组|<| |--------|----------|-| | |推荐的|技术上可接受的最低权限组 (功能有限)| |agent.hostname|Guests|Guests| |agent.ping|Guests|Guests| |agent.variant|Guests|Guests| |agent.version|Guests|Guests| |log|Administrators|Guests| |log.count|Administrators|Guests| |logrt|Administrators|Guests| |logrt.count|Administrators|Guests| |net.dns|Guests|Guests| |net.dns.record|Guests|Guests| |net.if.discovery|Guests|Guests| |net.if.in|Guests|Guests| |net.if.out|Guests|Guests| |net.if.total|Guests|Guests| |net.tcp.listen|Guests|Guests| |net.tcp.port|Guests|Guests| |net.tcp.service|Guests|Guests| |net.tcp.service.perf|Guests|Guests| |net.udp.service|Guests|Guests| |net.udp.service.perf|Guests|Guests| |proc.num|Administrators|Guests| |system.cpu.discovery|Performance Monitor Users|Performance Monitor Users| |system.cpu.load|Performance Monitor Users|Performance Monitor Users| |system.cpu.num|Guests|Guests| |system.cpu.util|Performance Monitor Users|Performance Monitor Users| |system.hostname|Guests|Guests| |system.localtime|Guests|Guests| |system.run|Administrators|Guests| |system.sw.arch|Guests|Guests| |system.swap.size|Guests|Guests| |system.uname|Guests|Guests| |system.uptime|Performance Monitor Users|Performance Monitor Users| |vfs.dir.count|Administrators|Guests| |vfs.dir.get|Administrators|Guests| |vfs.dir.size|Administrators|Guests| |vfs.file.cksum|Administrators|Guests| |vfs.file.contents|Administrators|Guests| |vfs.file.exists|Administrators|Guests| |vfs.file.md5sum|Administrators|Guests| |vfs.file.regexp|Administrators|Guests| |vfs.file.regmatch|Administrators|Guests| |vfs.file.size|Administrators|Guests| |vfs.file.time|Administrators|Guests| |vfs.fs.discovery|Administrators|Guests| |vfs.fs.size|Administrators|Guests| |vm.memory.size|Guests|Guests| |web.page.get|Guests|Guests| |web.page.perf|Guests|Guests| |web.page.regexp|Guests|Guests| |zabbix.stats|Guests|Guests|

en-us	Common column parameters:  |   |   | |---|---| |*Name*|Name of the column.| |*Data*|Data type to display in the column:<br>**Item value** - value of the specified item<br>**Host name** - host name of the item specified in the *Item value* column<br>**Text** - static text string| |*Base color*|Background color of the column; fill color if *Item value* data is displayed as bar/indicators.<br>For *Item value* data the default color can be overridden by custom color, if the item value is over one of the specified "Thresholds".|
zh-cn	通用列参数:  |   |   | |---|---| |*Name*|列的名称。| |*Data*|要在列中显示的数据类型：<br>**监控项的值**-指定监控项的值<br>**主机名**-在*监控项的值*列中指定监控项的主机名<br>**文本**-静态文本字符串| |*Base color*|列的背景色；如果*监控项的值*数据显示为条形图/指示器，则填充颜色<br>对于*监控项的值*数据，如果监控项的值超过指定的“阈值”之一，则默认颜色可以由自定义颜色覆盖。|

en-us	##### Common parameters  -   `/host/key` is a common mandatory first parameter for the functions     referencing the host item history -   `(sec|#num)<:time shift>` is a common second parameter for the     functions referencing the host item history, where:     -   **sec** - maximum [evaluation         period](/manual/config/triggers#evaluation_period) in seconds         (time [suffixes](/manual/appendix/suffixes) can be used), or     -   **\#num** - maximum [evaluation         range](/manual/config/triggers#evaluation_period) in latest         collected values (if preceded by a hash mark)     -   **time shift** (optional) allows to move the evaluation point         back in time. See [more         details](/manual/config/triggers/expression#time_shift) on         specifying time shift.
zh-cn	##### 常用参数  -   `/host/key` 是引用主机监控项历史记录函数的常用强制性首选参数 -   `(sec|#num)<:time shift>` 是引用主机监控项历史记录函数的常用强制性次选参数 ，其中：     -   **sec** - 以秒为单位的最大 [评估周期](/manual/config/triggers#evaluation_period)  (可以使用时间 [后缀](/manual/appendix/suffixes) )，或者     -   **\#num** - 最新收集值最大 [评估范围](/manual/config/triggers#evaluation_period)(如果前面有井号)     -   **time shift** (可选) 允许将评估点及时移回。参阅有关指定时间偏移 [更多详细内容](/manual/config/triggers/expression#time_shift)

en-us	##### Common parameters  -   `/host/key` is a common mandatory first parameter for the functions     referencing the host item history -   `(sec|#num)<:time shift>` is a common second parameter for the     functions referencing the host item history, where:     -   **sec** - maximum [evaluation         period](/manual/config/triggers#evaluation_period) in seconds         (time [suffixes](/manual/appendix/suffixes) can be used), or     -   **\#num** - maximum [evaluation         range](/manual/config/triggers#evaluation_period) in latest         collected values (if preceded by a hash mark)     -   **time shift** (optional) allows to move the evaluation point         back in time. See [more         details](/manual/config/triggers/expression#time_shift) on         specifying time shift.
zh-cn	##### 常用参数  -   `/host/key`是函数的常见强制性第一个参数 引用主机监控项历史 -   `(sec|#num)<:time shift>` 是常见的第二个参数 引用主机监控项历史的函数，其中     -   **sec** - 最大[评估周期](/manual/config/triggers#evaluation_period) in seconds(时间 [时间戳后缀](/manual/appendix/suffixes) 可以使用), or     -   **\#num** - 最大次数 [评估范围](/manual/config/triggers#evaluation_period)最新 收集的值（如果前面有#号）     -   **time shift**（可选）允许移动评估点历史点。关于指定时移更多[细节](/manual/config/triggers/expression#time_shift)查看。

en-us	##### Common parameters  -   `/host/key` is a common mandatory first parameter for the functions     referencing the host item history -   `(sec|#num)<:time shift>` is a common second parameter for the     functions referencing the host item history, where:     -   **sec** - maximum [evaluation         period](/manual/config/triggers#evaluation_period) in seconds         (time [suffixes](/manual/appendix/suffixes) can be used), or     -   **\#num** - maximum [evaluation         range](/manual/config/triggers#evaluation_period) in latest         collected values (if preceded by a hash mark)     -   **time shift** (optional) allows to move the evaluation point         back in time. See [more         details](/manual/config/triggers/expression#time_shift) on         specifying time shift.
zh-cn	##### 常用参数   - `/host/key` 是引用主机监控项历史记录函数的常用强制性首选参数  - `(sec|#num)<:time shift>` 是引用主机监控项历史记录函数的常用强制性次选参数 ，其中：  - **sec** - 以秒为单位的最大 [评估周期](/manual/config/triggers#evaluation_period) (可以使用时间 [后缀](/manual/appendix/suffixes) )，或者  - **\#num** - 最新收集值最大 [评估范围](/manual/config/triggers#evaluation_period)(如果前面有#符号)  - **time shift** (可选) 允许将评估点及时移回。参阅有关指定时间偏移 [更多详细内容](/manual/config/triggers/expression#time_shift)

en-us	##### Common parameters  -   `/host/key` is a common mandatory first parameter -   `time period:time shift` is a common second parameter, where:     -   **time period** - the time period (minimum '1h'), defined as \<N>\<time unit> where `N` - the number of time units, `time unit` - h (hour), d (day), w (week), M (month) or y (year).     -   **time shift** - the time period offset (see function examples)
zh-cn	##### 常用参数  - · `/host/key` 是常见的强制第一个参数 - · `time period:time shift`是常用的第二个参数，其中： - · **time period** - 时间段（最小'1h'），定义为\<N>\<time unit> 其中`N` - 时间单位数，`time unit` - h（小时） , d（日），w（周），M（月）或 y（年）。 - · **time shift** - 时间段偏移量（见函数示例）

en-us	##### Common use cases of global and host macros  -   use a global macro in several locations; then change the macro value     and apply configuration changes to all locations with one click -   take advantage of templates with host-specific attributes:     passwords, port numbers, file names, regular expressions, etc.
zh-cn	##### 全局和宿主宏的常见用例  - 在多个位置使用全局宏；然后更改宏值并一键将配置更改应用于所有位置 - 利用具有主机特定属性的模板：密码、端口号、文件名、正则表达式等。

en-us	##### Communication with Zabbix server  |Parameter|Description| |---------|-----------| |*Network timeout*|How many seconds to wait before closing an idle socket (if a connection to Zabbix server has been established earlier, but frontend can not finish read/send data operation during this time, the connection will be dropped). Allowed range: 1 - 300s (default: 3s).| |*Connection timeout*|How many seconds to wait before stopping an attempt to connect to Zabbix server. Allowed range: 1 - 30s (default: 3s).| |*Network timeout for media type test*|How many seconds to wait for a response when testing a media type. Allowed range: 1 - 300s (default: 65s).| |*Network timeout for script execution*|How many seconds to wait for a response when executing a script. Allowed range: 1 - 300s (default: 60s).| |*Network timeout for item test*|How many seconds to wait for returned data when testing an item. Allowed range: 1 - 300s (default: 60s).| |*Network timeout for scheduled report test*|How many seconds to wait for returned data when testing a scheduled report. Allowed range: 1 - 300s (default: 60s).|
zh-cn	##### 与 Zabbix 服务器通信  |参数|说明| |---------|------------| |*网络超时*|关闭空闲套接字前等待多少秒（如果之前已经建立了与 Zabbix 服务器的连接，但在此期间前端无法完成读取/发送数据操作，则连接将被丢弃）。允许范围：1 - 300s（默认值：3s）。| |*连接超时*|在停止尝试连接到 Zabbix 服务器之前等待多少秒。允许范围：1 - 30s（默认：3s）。| |*媒体类型测试的网络超时*|测试媒体类型时等待响应的秒数。允许范围：1 - 300s（默认值：65s）。| |*脚本执行的网络超时*|执行脚本时等待响应的秒数。允许范围：1 - 300s（默认值：60s）。| |*项目测试的网络超时*|测试项目时等待返回数据的秒数。允许范围：1 - 300s（默认值：60s）。| |*计划报告测试的网络超时*|测试计划报告时等待返回数据的秒数。允许范围：1 - 300s（默认值：60s）。|

en-us	#### Compiling OpenSSL  The following steps will help you to compile OpenSSL from sources on MS Windows 10 (64-bit).  1.  For compiling OpenSSL you will need on Windows machine:     1.  C compiler (e.g. VS 2017 RC),     2.  NASM (<https://www.nasm.us/>),     3.  Perl (e.g. Strawberry Perl from <http://strawberryperl.com/>),     4.  Perl module Text::Template (cpan Text::Template). 2.  Get OpenSSL sources from <https://www.openssl.org/>. OpenSSL 1.1.1     is used here. 3.  Unpack OpenSSL sources, for example, in E:\\openssl-1.1.1. 4.  Open a commandline window e.g. the x64 Native Tools Command Prompt     for VS 2017 RC. 5.  Go to the OpenSSL source directory, e.g. E:\\openssl-1.1.1.     1.  Verify that NASM can be found:`e:\openssl-1.1.1> nasm --version         NASM version 2.13.01 compiled on May  1 2017         ` 6.  Configure OpenSSL, for     example:`e:\openssl-1.1.1> perl E:\openssl-1.1.1\Configure VC-WIN64A no-shared no-capieng no-srp no-gost no-dgram no-dtls1-method no-dtls1_2-method  --api=1.1.0 --prefix=C:\OpenSSL-Win64-111-static --openssldir=C:\OpenSSL-Win64-111-static     `     -   Note the option 'no-shared': if 'no-shared' is used then the         OpenSSL static libraries libcrypto.lib and libssl.lib will be         'self-sufficient' and resulting Zabbix binaries will include         OpenSSL in themselves, no need for external OpenSSL DLLs.         Advantage: Zabbix binaries can be copied to other Windows         machines without OpenSSL libraries. Disadvantage: when a new         OpenSSL bugfix version is released, Zabbix agent needs to         recompiled and reinstalled.     -   If 'no-shared' is not used, then the static libraries         libcrypto.lib and libssl.lib will be using OpenSSL DLLs at         runtime. Advantage: when a new OpenSSL bugfix version is         released, probably you can upgrade only OpenSSL DLLs, without         recompiling Zabbix agent. Disadvantage: copying Zabbix agent to         another machine requires copying OpenSSL DLLs, too. 7.  Compile OpenSSL, run tests, install:`e:\openssl-1.1.1> nmake     e:\openssl-1.1.1> nmake test     ...     All tests successful.     Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr +  0.61 sys =  1.28 CPU)     Result: PASS     e:\openssl-1.1.1> nmake install_sw     `'install\_sw' installs only software components (i.e. libraries,     header files, but no documentation). If you want everything, use     "nmake install".
zh-cn	 #### 编译OpenSSL  接下来的步骤将助你在MS Windows 10（64位）的源中编译OpenSSL。  1.  编译OpenSSL你需要在Windows机器上安装：     1.  C compiler (e.g. VS 2017 RC),     2.  NASM (<https://www.nasm.us/>),     3.  Perl (e.g. Strawberry Perl from <http://strawberryperl.com/>),     4.  Perl module Text::Template (cpan Text::Template). 2.  获取 OpenSSL 源代码 <https://www.openssl.org/>。这里用OpenSSL 1.1.1 版本。 3.  解压 OpenSSL 源，例如，解压在 E:\\openssl-1.1.1。 4.  打开命令行窗口。例如，VS 2017 RC的 x64 原生工具命令提示符。 5.  至 OpenSSL 源目录, 例如，E:\\openssl-1.1.1。     1.  验证 NASM 能被找到：`e:\openssl-1.1.1> nasm --version         NASM version 2.13.01 compiled on May  1 2017         ` 6.  配置OpenSSL，例如：`e:\openssl-1.1.1> perl E:\openssl-1.1.1\Configure VC-WIN64A no-shared no-capieng no-srp no-gost no-dgram no-dtls1-method no-dtls1_2-method  --api=1.1.0 --prefix=C:\OpenSSL-Win64-111-static --openssldir=C:\OpenSSL-Win64-111-static     `     -   请注意选项 'no-shared'：如果使用 'no-shared' 那么OpenSSL静态库 libcrypto.lib和libssl.lib 将         '自给自足'，生成的Zabbix二进制文件本身将包含OpenSSL ，不需要外部的OpenSSL DLLs。         优点： Zabbix二进制文件可以复制到其他没有OpenSSL库的Windows机器上。          缺点：当新的OpenSSL bugfix 版本发布时，需要重新编译并安装Zabbix agent。     -   如果不使用'no-shared'，那么静态库 libcrypto.lib和 libssl.lib 会在运行时使用OpenSSL DLLs 。     - 优点：当新的OpenSSL bugfix版本发布时，你可能只需要升级OpenSSL DLLs不用重新编译Zabbix agent。     - 缺点：复制Zabbix agent到另一个机器时，需要同时复制OpenSSL DLLs。 7.  编译OpenSSL，运行测试，安装：`e:\openssl-1.1.1> nmake     e:\openssl-1.1.1> nmake test     ...     All tests successful.     Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr +  0.61 sys =  1.28 CPU)     Result: PASS     e:\openssl-1.1.1> nmake install_sw     `'install\_sw' 仅安装软件组件（例如 库，头文件，但不安装文档）。如果你希望安装所有的文件，请用 "nmake install"。

en-us	#### Compiling Zabbix agent 2
zh-cn	#### 编译Zabbix agent 2

en-us	#### Compiling Zabbix agent on HP-UX  If you install the PCRE library from a popular HP-UX package site <http://hpux.connect.org.uk>, for example from file `pcre-8.42-ia64_64-11.31.depot`, you get only the 64-bit version of the library installed in the /usr/local/lib/hpux64 directory.  In this case, for successful agent compilation customized options need to be used for the "configure" script, e.g.:      CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64
zh-cn	#### 在 HP-UX 上编译 Zabbix agent  如果从常规的 HP-UX 软件包站点 http://hpux.connect.org.uk 安装 PCRE 库（例如 `pcre-8.42-ia64_64-11.31.depot` 文件），你将仅获得安装在 /usr/local/lib/hpux64 路径下的 64 位版本的库。  在这种情况下，为了成功编译 agent，需要为“配置”脚本使用自定义选项，例如：      CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64

en-us	#### Compiling Zabbix  The following steps will help you to compile Zabbix from sources on MS Windows 10 (64-bit). When compiling Zabbix with/without TLS support the only significant difference is in step 4.  1.  On a Linux machine check out the source from     git:`` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git     $ cd zabbix     $ ./bootstrap.sh     $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd`     $ make dbschema     $ make dist      `` 2.  Copy and unpack the archive, e.g. zabbix-4.4.0.tar.gz, on a Windows     machine. 3.  Let's assume that sources are in e:\\zabbix-4.4.0. Open a     commandline window e.g. the x64 Native Tools Command Prompt for VS     2017 RC. Go to E:\\zabbix-4.4.0\\build\\win32\\project. 4.  Compile zabbix\_get, zabbix\_sender and zabbix\_agent.     -   without TLS:         `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         `     -   with TLS:         `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         ` 5.  New binaries are located in e:\\zabbix-4.4.0\\bin\\win64. Since     OpenSSL was compiled with 'no-shared' option, Zabbix binaries     contain OpenSSL within themselves and can be copied to other     machines that do not have OpenSSL.
zh-cn	#### 编译 Zabbix  以下步骤将助你从MS Windows 10 (64位)上的源码中编译Zabbix。在编译有或没有TLS支持的Zabbix时，唯一显著的区别在步骤4。  1.  在Linux机器上，检查git源代码：`` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git     $ cd zabbix     $ ./bootstrap.sh     $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd`     $ make dbschema     $ make dist      `` 2.  在Windows机器上复制和解压归档文件，例如 zabbix-4.4.0.tar.gz。 3.  我们假设源代码在 e:\\zabbix-4.4.0中。打开命令行窗口，例如 VS 2017 RC中的 x64原生工具命令提示符。转至 E:\\zabbix-4.4.0\\build\\win32\\project。 4.  编译 zabbix\_get， zabbix\_sender 和 zabbix\_agent。     -   无TLS：         `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         `     -   有TLS：         `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         ` 5.  新的二进制文件位于 e:\\zabbix-4.4.0\\bin\\win64。由于 OpenSSL 是用 'no-shared' 选项编译的，Zabbix二进制文件本身包含OpenSSL，可以复制到其他没有OpenSSL的机器中。

en-us	#### Compiling Zabbix  The following steps will help you to compile Zabbix from sources on MS Windows 10 (64-bit). When compiling Zabbix with/without TLS support the only significant difference is in step 4.  1.  On a Linux machine check out the source from     git:`` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git     $ cd zabbix     $ ./bootstrap.sh     $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd`     $ make dbschema     $ make dist      `` 2.  Copy and unpack the archive, e.g. zabbix-4.4.0.tar.gz, on a Windows     machine. 3.  Let's assume that sources are in e:\\zabbix-4.4.0. Open a     commandline window e.g. the x64 Native Tools Command Prompt for VS     2017 RC. Go to E:\\zabbix-4.4.0\\build\\win32\\project. 4.  Compile zabbix\_get, zabbix\_sender and zabbix\_agent.     -   without TLS:         `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         `     -   with TLS:         `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         ` 5.  New binaries are located in e:\\zabbix-4.4.0\\bin\\win64. Since     OpenSSL was compiled with 'no-shared' option, Zabbix binaries     contain OpenSSL within themselves and can be copied to other     machines that do not have OpenSSL.  
zh-cn	#### 编译 Zabbix  以下步骤将助你从MS Windows 10 (64位)上的源码中编译Zabbix。在编译有或没有TLS支持的Zabbix时，唯一显著的区别在步骤4。  1.  在Linux机器上，检查git源代码：`` $ git clone https://git.zabbix.com/scm/zbx/zabbix.git     $ cd zabbix     $ ./bootstrap.sh     $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd`     $ make dbschema     $ make dist      `` 2.  在Windows机器上复制和解压归档文件，例如 zabbix-4.4.0.tar.gz。 3.  我们假设源代码在 e:\\zabbix-4.4.0中。打开命令行窗口，例如 VS 2017 RC中的 x64原生工具命令提示符。转至 E:\\zabbix-4.4.0\\build\\win32\\project。 4.  编译 zabbix\_get， zabbix\_sender 和 zabbix\_agent。     -   无TLS：         `E:\zabbix-4.4.0\build\win32\project> nmake /K PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         `     -   有TLS：         `E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_get TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_sender TLS=openssl TLSINCDIR="C:\OpenSSL-Win64-111-static\include TLSLIBDIR="C:\OpenSSL-Win64-111-static\lib" PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         E:\zabbix-4.4.0\build\win32\project> nmake /K -f Makefile_agent TLS=openssl TLSINCDIR=C:\OpenSSL-Win64-111-static\include TLSLIBDIR=C:\OpenSSL-Win64-111-static\lib PCREINCDIR=E:\pcre2-10.39-install\include PCRELIBDIR=E:\pcre2-10.39-install\lib         ` 5.  新的二进制文件位于 e:\\zabbix-4.4.0\\bin\\win64。由于 OpenSSL 是用 'no-shared' 选项编译的，Zabbix二进制文件本身包含OpenSSL，可以复制到其他没有OpenSSL的机器中。

en-us	### Conditions  The following conditions can be used in service actions:  |Condition type|Supported operators|Description| |--------------|-------------------|-----------| |*Service*|equals<br>does not equal|Specify a service or a service to exclude.<br>**equals** - event belongs to this service.<br>**does not equal** - event does not belong to this service.<br>Specifying a parent service implicitly selects all child services. To specify the parent service only, all nested services have to be additionally set with the **does not equal** operator.| |*Service name*|contains<br>does not contain|Specify a string in the service name or a string to exclude.<br>**contains** - event is generated by a service, containing this string in the name.<br>**does not contain** - this string cannot be found in the service name.| |*Service tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag or an event tag to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag<br>**does not equal** - event does not have this tag<br>**contains** - event has a tag containing this string<br>**does not contain** - event does not have a tag containing this string.| |*Service tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify an event tag and value combination or a tag and value combination to exclude. Service event tags can be defined in the service configuration section *Tags*.<br>**equals** - event has this tag and value<br>**does not equal** - event does not have this tag and value<br>**contains** - event has a tag and value containing these strings<br>**does not contain** - event does not have a tag and value containing these strings.|  :::noteimportant Make sure to define [message templates](/manual/config/notifications/media#overview) for Service actions in the *Administration->Media types* menu. Otherwise, the notifications will not be sent.  :::
zh-cn	### 条件  以下条件可用于服务动作：  |条件类型|支持的运算符|说明| |--------------|-------------------|-----------| |*Service*|等于<br>不等于|设置服务。<br>**equals** - 事件等于此服务。<br>**does not equal** - 事件不等于此服务。<br>指定父服务会隐式选择所有子服务。要仅指定父服务，必须使用 **does not equal** 运算符额外设置所有嵌套服务。| |*Service name*|包含<br>不包含|设置服务名中的字符串。<br>**contains** - 事件由服务生成，服务名称中包含此字符串。<br>**does not contain** - 在服务名中找不到此字符串。| |*Service tag name*|等于<br>不等于<br>包含<br>不包含|设置事件标签。服务事件标签可以在服务配置部分 *Tag* 中定义。<br>**equals** - 事件标签名等于 tag 值<br>**does not equal** - 事件标签名不等于 tag 值<br>**contains** - 事件标签名包含指定字符串<br>**does not contain** - 事件标签名不包含指定字符串。| |*Service tag value*|等于<br>不等于<br>包含<br>不包含|设置事件标签和值的组合。服务事件标签可以在服务配置部分 *Tag* 中定义。<br>**equals** - 事件标签值等于 value 值<br>**does not equal** - 事件标签值不等于 value 值<br>**contains** - 事件标签的值包含指定字符串<br>**does not contain** - 事件标签的值不包含指定字符串。|  :::noteimportant 确保在 *Administration->Media types* 菜单中为服务动作定义[消息模板](/manual/config/notifications/media#概述)。否则，将不会发送通知。 :::

en-us	#### Configurable fields  Actual command(s) to be executed must be placed in the **Executed script** field in the item configuration.\ Multiple commands can be executed one after another by placing them on a new line. In this case returned value also will be formatted as multilined.  Supported characters that the shell prompt can end with:  -   $ -   \# -   \> -   %  ::: noteclassic A telnet prompt line which ended with one of these characters will be removed from the returned value, but only for the first command in the commands list, i.e. only at a start of the telnet session. :::  |Key|Description| |--|------| |**telnet.run\[<unique short description>,<ip>,<port>,<encoding>\]**|Run a command on a remote device using telnet connection||  ::: noteimportant If a telnet check returns a value with non-ASCII characters and in non-UTF8 encoding then the *<encoding>* parameter of the key should be properly specified. See [encoding of returned values](/manual/appendix/items/encoding_of_values) page for more details. :::
zh-cn	#### 可配置字段  要执行的实际命令必须放在监控项配置中的 **执行的脚本**  字段中。如果要执行多条命令，一行写一条，命令将逐条执行。这种情况下，返回值也将为多行显示。  支持的 shell 提示符结尾的字符：  - $ - \# - > - %  ::: noteclassic 以上结束符的telnet提示行将从返回值中删除，但仅针对命令列表中的第一个命令，即仅在telnet会话开始处。 :::  |键值|描述| |---|-----------| |**telnet.run\[<unique short description>,<ip>,<port>,<encoding>\]**|使用 telnet 连接在远程设备上运行命令|<|  ::: noteimportant 如果telnet检查返回一个非ascii字符和非utf8编码的值,那应该正确的指定<encoding>参数。有关详细信息，请参阅[编码返回值](/manual/appendix/items/encoding_of_values) 页面。 :::

en-us	#### Configurable fields  The **key** is a unique item identifier (per host). You can create any key name using supported symbols.  Calculation definition should be entered in the **Formula** field. There is virtually no connection between the formula and the key. The key parameters are not used in the formula in any way.  The syntax of a simple formula is:      function(/host/key,<parameter1>,<parameter2>,...)  where:  |   |   | |--|--------| |*function*|One of the [supported functions](/manual/appendix/functions): last, min, max, avg, count, etc| |*host*|Host of the item that is used for calculation.<br>The current host can be omitted (i.e. as in `function(//key,parameter,...)`).| |*key*|Key of the item that is used for calculation.| |*parameter(s)*|Parameters of the function, if required.|  ::: noteimportant [User macros](/manual/config/macros/user_macros) in the formula will be expanded if used to reference a function parameter, item filter parameter, or a constant. User macros will NOT be expanded if referencing a function, host name, item key, item key parameter or operator. :::  A more complex formula may use a combination of functions, operators and brackets. You can use all functions and [operators](/manual/config/triggers/expression#operators) supported in trigger expressions. The logic and operator precedence are exactly the same.  Unlike trigger expressions, Zabbix processes calculated items according to the item update interval, not upon receiving a new value.  All items that are referenced by history functions in the calculated item formula must exist and be collecting data. Also, if you change the item key of a referenced item, you have to manually update any formulas using that key.  A calculated item may become unsupported in several cases:  -   referenced item(s)     -   is not found     -   is disabled     -   belongs to a disabled host     -   is not supported (except with nodata() function and         [operators](/manual/config/triggers/expression#operators) with         unknown values) -   no data to calculate a function -   division by zero -   incorrect syntax used
zh-cn	#### 可配置字段   **key** 是唯一的监控项标识符(每个主机)。您可以使用支持的符号创建任何键名。  应在 **公式** 字段中输入计算定义。公式和密钥之间几乎没有任何联系。公式中不以任何方式使用关键参数。  一个简单公式的语法是：      function(/host/key,<parameter1>,<parameter2>,...)  这里:  |   |   | |---|---| |*function*|[支持的函数](/manual/appendix/functions)之一: last, min, max, avg, count, 等| |*host*|用于计算的主机监控项<br>当前主机可以省略 (如下所示 `function(//key,parameter,...)`).| |*key*|用于计算的监控项的键| |*parameter(s)*|函数的参数，如果需要。|  ::: noteimportant 如果用于引用函数参数或常量，公式中的[用户宏](/manual/config/macros/user_macros)将被扩展，如果引用函数、主机名、监控项键、监控项键参数或运算符，则不会扩展用户宏。 :::  更复杂的公式可以使用函数、运算符和括号的组合。您可以使用触发器表达式中支持的所有函数和 [运算符](/manual/config/triggers/expression#operators)。逻辑和运算符优先级完全相同。  与触发器表达式不同，Zabbix 根据监控项更新间隔处理可计算监控项，而不是在接收到新值时。  可计算监控项公式中历史函数引用的所有监控项都必须存在并且正在收集数据。此外，如果您更改引用监控项的键，则必须手动更新任何使用该键的公式。  在以下几种情况下，可计算监控项可能会变得不受支持：  -   引用的监控项     -   没有找到     -   被禁用     -   属于禁用的主机     -   不支持 (除了 nodata() 函数和具有未知值的 [运算符](/manual/config/triggers/expression#operators)) -   没有数据来计算函数 -   被0除 -  使用了不正确的语法

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	 #### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration  
zh-cn	#### 配置

en-us	 ### Configuration  1. Create disabled Script item on the main VMware host (where the **eventlog[]** item is present) with the following parameters:  ![](../../../../assets/en/manual/appendix/items/perf_counter_item.png)  - *Name*:  VMware metrics - *Type*: Script - *Key*: vmware.metrics - *Type of information*: Text - *Script*: copy and paste the [script](#script) provided below - *Timeout*: 10 - *History storage period*: Do not keep history - *Enabled*: unmarked   #### Script      try {         Zabbix.log(4, 'vmware metrics script');          var result, resp,         req = new HttpRequest();         req.addHeader('Content-Type: application/xml');         req.addHeader('SOAPAction: "urn:vim25/6.0"');          login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\         <soapenv:Header/>\         <soapenv:Body>\             <urn:Login>\                 <urn:_this type="SessionManager">SessionManager</urn:_this>\                 <urn:userName>{$VMWARE.USERNAME}</urn:userName>\                 <urn:password>{$VMWARE.PASSWORD}</urn:password>\             </urn:Login>\         </soapenv:Body>\     </soapenv:Envelope>'         resp = req.post("{$VMWARE.URL}", login);         if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }          query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\     <soapenv:Header/>\         <soapenv:Body>\             <urn:RetrieveProperties>\                 <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\                 <urn:specSet>\                     <urn:propSet>\                        <urn:type>PerformanceManager</urn:type>\                        <urn:pathSet>perfCounter</urn:pathSet>\                     </urn:propSet>\                     <urn:objectSet>\                        <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\                     </urn:objectSet>\                 </urn:specSet>\             </urn:RetrieveProperties>\         </soapenv:Body>\     </soapenv:Envelope>'         resp = req.post("{$VMWARE.URL}", query);         if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }         Zabbix.log(4, 'vmware metrics=' + resp);         result = resp;          logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\         <soapenv:Header/>\         <soapenv:Body>\             <urn:Logout>\                 <urn:_this type="SessionManager">SessionManager</urn:_this>\             </urn:Logout>\         </soapenv:Body>\     </soapenv:Envelope>'          resp = req.post("{$VMWARE.URL}",logout);                  if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }      } catch (error) {         Zabbix.log(4, 'vmware call failed : '+error);         result = {};     }      return result;   Once the item is configured, press *Test* button, then press *Get value*.   ![](../../../../assets/en/manual/appendix/items/perf_counter_item1.png){width=600}  Copy received XML to any XML formatter and find the desired metric.  An example of XML for one metric:       <PerfCounterInfo xsi:type="PerfCounterInfo">         <key>6</key>         <nameInfo>             <label>Usage in MHz</label>             <summary>CPU usage in megahertz during the interval</summary>             <key>usagemhz</key>         </nameInfo>         <groupInfo>             <label>CPU</label>             <summary>CPU</summary>             <key>cpu</key>         </groupInfo>         <unitInfo>             <label>MHz</label>             <summary>Megahertz</summary>             <key>megaHertz</key>         </unitInfo>         <rollupType>average</rollupType>         <statsType>rate</statsType>         <level>1</level>         <perDeviceLevel>3</perDeviceLevel>     </PerfCounterInfo>  Use XPath to extract the counter path from received XML. For the example above, the XPath will be:  |field |xPath | value | |--|--|--| |group | //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average |  Resulting performance counter path in this case is: `cpu/usagemhz[average]`
zh-cn	### 配置  1. 使用以下参数在主要的VMware主机（存在**eventlog[]**监控项的地方）上创建禁用的脚本监控项：  ![](../../../../assets/en/manual/appendix/items/perf_counter_item.png)  - *Name*: · VMware 指标 - *Type*: 脚本 - *Key*: vmware.metrics - *Type of information*: 文本 - *Script*: 复制并粘贴下面提供的[脚本](#script) - *Timeout*: 10 - *History storage period*: 不保留历史数据 - *Enabled*: 未标记    ### 脚本    · try {  · Zabbix.log(4, 'vmware metrics script');   · var result, resp,  · req = new HttpRequest();  · req.addHeader('Content-Type: application/xml');  · req.addHeader('SOAPAction: "urn:vim25/6.0"');   · login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:Login>\  · <urn:_this type="SessionManager">SessionManager</urn:_this>\  · <urn:userName>{$VMWARE.USERNAME}</urn:userName>\  · <urn:password>{$VMWARE.PASSWORD}</urn:password>\  · </urn:Login>\  · </soapenv:Body>\  · </soapenv:Envelope>'  · resp = req.post("{$VMWARE.URL}", login);  · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }   · query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:RetrieveProperties>\  · <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\  · <urn:specSet>\  · <urn:propSet>\  · <urn:type>PerformanceManager</urn:type>\  · <urn:pathSet>perfCounter</urn:pathSet>\  · </urn:propSet>\  · <urn:objectSet>\  · <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\  · </urn:objectSet>\  · </urn:specSet>\  · </urn:RetrieveProperties>\  · </soapenv:Body>\  · </soapenv:Envelope>'  · resp = req.post("{$VMWARE.URL}", query);  · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }  · Zabbix.log(4, 'vmware metrics=' + resp);  · result = resp;   · logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:Logout>\  · <urn:_this type="SessionManager">SessionManager</urn:_this>\  · </urn:Logout>\  · </soapenv:Body>\  · </soapenv:Envelope>'   · resp = req.post("{$VMWARE.URL}",logout); ·   · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }   · } catch (error) {  · Zabbix.log(4, 'vmware call failed : '+error);  · result = {};  · }    · 返回结果;   配置监控项后，点击 *Test* 按钮，然后点击 *Get value*。  ![](../../../../assets/en/manual/appendix/items/perf_counter_item1.png){width=600}  将收到的 XML 复制到任何 XML 格式化程序并找到所需的指标。  一个指标的 XML 示例：   · <PerfCounterInfo xsi:type="PerfCounterInfo">  · <key>6</key>  · <nameInfo>  · <label>Usage in MHz</label>  · <summary>CPU usage in megahertz during the interval</summary>  · <key>usagemhz</key>  · </nameInfo>  · <groupInfo>  · <label>CPU</label>  · <summary>CPU</summary>  · <key>cpu</key>  · </groupInfo>  · <unitInfo>  · <label>MHz</label>  · <summary>Megahertz</summary>  · <key>megaHertz</key>  · </unitInfo>  · <rollupType>average</rollupType>  · <statsType>rate</statsType>  · <level>1</level>  · <perDeviceLevel>3</perDeviceLevel>  · </PerfCounterInfo>   使用 XPath 从收到的 XML 中提取计数器路径。对于上面的示例，XPath 将是：  |字段 |xPath |值 | |--|--|--| |group | //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average |  在这个例子中性能计数器路径是：`cpu/usagemhz[average]`

en-us	#### Configuration  ![](../../../../../assets/en/manual/config/visualization/maps/map_host_group.png){width="600"}  All mandatory input fields are marked with a red asterisk.  This table consists of parameters typical for *Host group* element type:  |Parameter|Description| |---------|-----------| |*Type*|Select Type of the element:<br>**Host group** - icon representing the status of all triggers of all hosts belonging to the selected group| |*Show*|Show options:<br>**Host group** - selecting this option will result as one single icon displaying corresponding information about the certain host group<br>**Host group elements** - selecting this option will result as multiple icons displaying corresponding information about every single element (host) of the certain host group| |*Area type*|This setting is available if the “Host group elements” parameter is selected:<br>**Fit to map** - all host group elements are equally placed within the map<br>**Custom size** - a manual setting of the map area for all the host group elements to be displayed| |*Area size*|This setting is available if “Host group elements” parameter and “Area type” parameter are selected:<br>**Width** - numeric value to be entered to specify map area width<br>**Height** - numeric value to be entered to specify map area height| |*Placing algorithm*|**Grid** – only available option of displaying all the host group elements| |*Label*|Icon label, any string.<br>[Macros](/manual/config/macros) and multi-line strings can be used in labels.<br>If the type of the map element is “Host group” specifying certain macros has an impact on the map view displaying corresponding information about every single host. For example, if {HOST.IP} macro is used, the edit map view will only display the macro {HOST.IP} itself while map view will include and display each host’s unique IP address|
zh-cn	#### 配置  ![](../../../../../assets/en/manual/config/visualization/maps/map_host_group.png){width="600"}  所有必填字段都标有红色星号。  此表包含 *Host group* 元素类型的典型参数：  |参数|说明| |---------|------------| |*类型*|选择元素类型:<br>**主机组** - 表示属于所选组的所有主机的所有触发器状态的图标| |*显示*|显示选项：<br>**主机组** - 选择此选项将导致单个图标显示有关特定主机组的相应信息<br>**主机组元素** - 选择此选项将结果是多个图标显示有关某个主机组的每个元素（主机）的相应信息| |*区域类型*|如果选择了“主机组元素”参数，则此设置可用：<br>**适合地图** - 所有主机组元素均等放置在地图中<br>**自定义大小* * - 手动设置要显示的所有主机组元素的地图区域| |*区域大小*|如果选择了“主机组元素”参数和“区域类型”参数，则此设置可用：<br>**宽度** - 用于指定地图区域宽度的数值<br>**高度** - 要输入以指定地图区域高度的数值| |*放置算法*|**网格** – 显示所有主机组元素的唯一可用选项| |*标签*|图标标签，任意字符串。<br>标签中可以使用[宏](/manual/config/macros)和多行字符串。<br>如果地图元素的类型是“主机组” ” 指定某些宏会对显示每个主机的相应信息的地图视图产生影响。例如，如果使用 {HOST.IP} 宏，则编辑地图视图将仅显示宏 {HOST.IP} 本身，而地图视图将包含并显示每个主机的唯一 IP 地址|

en-us	#### Configuration  Debug mode can be activated for individual users who belong to a user group:  -   when configuring a [user     group](/manual/config/users_and_usergroups/usergroup#configuration); -   when viewing configured [user     groups](//manual/web_interface/frontend_sections/administration/user_groups).  When *Debug mode* is enabled for a user group, its users will see a *Debug* button in the lower right corner of the browser window:  ![](../../../assets/en/manual/web_interface/debug_button.png)  Clicking on the *Debug* button opens a new window below the page contents which contains the SQL statistics of the page, along with a list of API calls and individual SQL statements:  ![](../../../assets/en/manual/web_interface/debug_mode.png){width="600"}  In case of performance problems with the page, this window may be used to search for the root cause of the problem.  ::: notewarning Enabled *Debug mode* negatively affects frontend performance. :::
zh-cn	#### 配置  可以为属于用户组的用户激活调试模式：  -   当配置一个[用户组](/manual/config/users_and_usergroups/usergroup#configuration); -   当查看配置的 [用户组](//manual/web_interface/frontend_sections/administration/user_groups)。  当为用户组启用 *调试模式* 时，其用户将在浏览器窗口的右下角看到一个 *调试* 按钮：  ![](../../../assets/en/manual/web_interface/debug_button.png)  单击 *调试* 按钮会在页面内容下方打开一个新窗口，其中包含页面的 SQL 统计信息，以及 API 调用和单个 SQL 语句的列表：  ![](../../../assets/en/manual/web_interface/debug_mode.png){width="600"}  如果页面出现性能问题，此窗口可用于搜索问题的根本原因。  ::: notewarning 启用 *调试模式* 会对前端性能产生负面影响。 :::

en-us	# configuration.export
zh-cn	# configuration.export

en-us	#### Configuration file  For details on configuring Zabbix agent see the configuration file options for [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) or [Windows agent](/manual/appendix/config/zabbix_agentd_win).
zh-cn	#### 配置文件  有关配置 Zabbix agent 的详细信息，请查阅  [zabbix_agentd](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/config/zabbix_agentd)  或  [Windows agent](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/config/zabbix_agentd_win)  章节。

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_proxy) options for details on configuring zabbix\_proxy.
zh-cn	##### 配置文件  另请参考 [configuration file](/manual/appendix/config/zabbix_proxy) 配置zabbix\_proxy的详细信息。

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_server) options for details on configuring zabbix\_server.
zh-cn	##### 配置文件  有关配置 Zabbix server 的详细信息，请查阅 [配置文件](/manual/appendix/config/zabbix_server) 章节。

en-us	#### Configuration file  The configuration parameters of agent 2 are mostly compatible with Zabbix agent with some exceptions.  |New parameters|Description| |--|--------| |*ControlSocket*|The runtime control socket path. Agent 2 uses a control socket for [runtime commands](#runtime_control).| |*EnablePersistentBuffer*,<br>*PersistentBufferFile*,<br>*PersistentBufferPeriod*|These parameters are used to configure persistent storage on agent 2 for active items.| |*ForceActiveChecksOnStart*|Determines whether the agent should perform active checks immediately after restart or spread evenly over time. Supported since Zabbix 6.0.2.| |*Plugins*|Plugins may have their own parameters, in the format `Plugins.<Plugin name>.<Parameter>=<value>`. A common plugin parameter is *System.Capacity*, setting the limit of checks that can be executed at the same time.| |*StatusPort*|The port agent 2 will be listening on for HTTP status request and display of a list of configured plugins and some internal parameters| |**Dropped parameters**|**Description**| |*AllowRoot*, *User*|Not supported because daemonization is not supported.| |*LoadModule*, *LoadModulePath*|Loadable modules are not supported.| |*StartAgents*|This parameter was used in Zabbix agent to increase passive check concurrency or disable them. In Agent 2, the concurrency is configured at a plugin level and can be limited by a capacity setting. Whereas disabling passive checks is not currently supported.| |*HostInterface*, *HostInterfaceItem*|Not yet supported.|  For more details see the configuration file options for [zabbix\_agent2](/manual/appendix/config/zabbix_agent2).
zh-cn	#### 配置文件  agent 2的配置参数大多与Zabbix agent 兼容，但也有一些例外。  |新的参数|描述| |--------------|-----------| |*ControlSocket*|实时控制套接字路径。 Agent 2使用控制套接字 [runtime commands](#runtime_control).| |*EnablePersistentBuffer*,<br>*PersistentBufferFile*,<br>*PersistentBufferPeriod*|这些参数用于在agent 2上为活动监控项配置持久存储.| |*ForceActiveChecksOnStart*|确定agent是否应在重新启动后立即执行主动检查或随时间均匀分布。 自 Zabbix 6.0.2 起支持。| |*Plugins*|插件可能有自己的参数, 以 `Plugins.<Plugin name>.<Parameter>=<value>`格式。 常见的插件参数是 *Capacity*, 设置可以同时执行的检查的限制。| |*StatusPort*|agent 2将监听的端口，用于HTTP状态请求和显示已配置的插件列表以及一些内部参数| |**丢弃的参数**|**描述**| |*AllowRoot*, *User*|不支持，因为守护进程不支持。| |*LoadModule*, *LoadModulePath*|不支持可加载模块。| |*StartAgents*|此参数在Zabbix agent中用于增加被动检查并发性或禁用它们。 在Agent 2,并发是在插件级别配置的，可以通过容量设置来限制。 然而，当前不支持禁用被动检查。| |*HostInterface*, *HostInterfaceItem*|不支持。|  有关详细信息，请参阅配置文件选项[zabbix\_agent2](/manual/appendix/config/zabbix_agent2).

en-us	#### Configuration  For virtual machine monitoring to work, Zabbix should be [compiled](/manual/installation/install#configure_the_sources) with the --with-libxml2 and --with-libcurl compilation options.  The following configuration file options can be used to tune the Virtual machine monitoring:  -   **StartVMwareCollectors** - the number of pre-forked vmware     collector instances.\     This value depends on the number of VMware services you are going to     monitor. For the most cases this should be:\     *servicenum < StartVMwareCollectors < (servicenum \* 2)*\     where *servicenum* is the number of VMware services. E. g. if you     have 1 VMware service to monitor set StartVMwareCollectors to 2, if     you have 3 VMware services, set it to 5. Note that in most cases     this value should not be less than 2 and should not be 2 times     greater than the number of VMware services that you monitor. Also     keep in mind that this value also depends on your VMware environment     size and *VMwareFrequency* and *VMwarePerfFrequency* configuration     parameters (see below). -   **VMwareCacheSize** -   **VMwareFrequency** -   **VMwarePerfFrequency** -   **VMwareTimeout**  For more details, see the configuration file pages for Zabbix [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy).  ::: noteimportant To support datastore capacity metrics Zabbix requires VMware configuration vpxd.stats.maxQueryMetrics parameter to be at least 64. See also the VMware knowledge base [article](https://kb.vmware.com/s/article/2107096). :::
zh-cn	#### 配置  为了使虚拟机监控可以正常工作，Zabbix 应该使用 --with-libxml2 和 --with-libcurl 编译选项进行 [编译](/manual/installation/install#configure_the_sources) 。  以下配置文件选项可用于调整虚拟机监控：  -   **StartVMwareCollectors** - 预设的 vmware collector 实例的数量。\     此值取决于您要监控的 VMware 服务的数量。在大多数情况下，这应该是：\     *servicenum < StartVMwareCollectors < (servicenum \* 2)*\     其中*servicenum* 是 VMware 服务的数量。例如，如果有 1 个要监控的 VMware 服务，请将 StartVMwareCollectors 设置为 2，如果您有 3 个 VMware 服务，请将其设置为 5。请注意，在大多数情况下，此值不应小于 2，也不应大于监控的 VMware 服务数量的 2 倍。另外，此值还取决于您的 VMware 环境大小以及 *VMwareFrequency* 和 *VMwarePerfFrequency* 配置参数（见下文）。  -   **VMwareCacheSize** -   **VMwareFrequency** -   **VMwarePerfFrequency** -   **VMwareTimeout**  有关更多详细信息，请参阅 Zabbix [server](/manual/appendix/config/zabbix_server) 和[proxy](/manual/appendix/config/zabbix_proxy) 的配置文件页面。  ::: noteimportant 为了支持数据存储容量指标，Zabbix 要求 VMware 配置 vpxd.stats.maxQueryMetrics 参数的值至少为 64。另请参阅 VMware 知识库 [文章](https://kb.vmware.com/s/article/2107096)。 :::

en-us	#### Configuration  Global notifications can be enabled per user in the *Messaging* tab of [profile configuration](/manual/web_interface/user_profile).  ![profile\_c.png](../../../../assets/en/manual/web_interface/profile_c.png)  |Parameter|Description| |--|--------| |*Frontend messaging*|Mark the checkbox to enable global notifications.| |*Message timeout*|You can set for how long the message will be displayed. By default, messages will stay on screen for 60 seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 5m, 2h, 1d.| |*Play sound*|You can set how long the sound will be played.<br>**Once** - sound is played once and fully.<br>**10 seconds** - sound is repeated for 10 seconds.<br>**Message timeout** - sound is repeated while the message is visible.| |*Trigger severity*|You can set the trigger severities that global notifications and sounds will be activated for. You can also select the sounds appropriate for various severities.<br>If no severity is marked then no messages will be displayed at all.<br>Also, recovery messages will only be displayed for those severities that are marked. So if you mark *Recovery* and *Disaster*, global notifications will be displayed for the problems and the recoveries of disaster severity triggers.| |*Show suppressed problems*|Mark the checkbox to display notifications for problems which would otherwise be suppressed (not shown) because of host maintenance.|
zh-cn	#### 配置  可以在 [用户配置设置](/manual/web_interface/user_profile) 的 *消息* 选项卡中为每个用户启用全局通知。  ![profile\_c.png](../../../../assets/en/manual/web_interface/profile_c.png)  |参数|说明| |---------|---------| |*前端消息传递*|标记复选框以启用全局通知。| |*消息超时*|您可以设置消息显示的时长。默认情况下，消息将在屏幕上停留 60 秒。<br>支持[时间后缀](/manual/appendix/suffixes)，例如30s，5m，2h，1d。| |*播放声音*|您可以设置声音的播放时间。<br>**一次** - 声音播放一次并完全播放。<br>**10 秒** - 声音重复 10 秒。 <br>**消息超时** - 消息可见时重复声音。| |*触发严重性*|您可以设置将激活全局通知和声音的触发严重性。您还可以选择适合各种严重性的声音。<br>如果未标记严重性，则根本不会显示任何消息。<br>此外，仅针对已标记的严重性显示恢复消息。因此，如果您标记 *Recovery* 和 *Disaster*，将显示全局通知以显示问题和灾难严重性触发器的恢复。| |*显示抑制的问题*|标记复选框以显示由于主机维护而被抑制（未显示）的问题的通知。|

en-us	# configuration.import
zh-cn	# configuration.import

en-us	# configuration.importcompare
zh-cn	# configuration.importcompare

en-us	 ### Configuration import  See changes in the [configuration import](/manual/introduction/whatsnew6013#configuration-import) process.
zh-cn	### 配置导入  查看 [配置导入](/manual/introduction/whatsnew6013#configuration-import) 过程中的更改。

en-us	#### Configuration  In order to enable maintenance mode, the `maintenance.inc.php` file (located in `/conf` of Zabbix HTML document directory on the web server) must be modified to uncomment the following lines:      // Maintenance mode.     define('ZBX_DENY_GUI_ACCESS', 1);      // Array of IP addresses, which are allowed to connect to frontend (optional).     $ZBX_GUI_ACCESS_IP_RANGE = array('127.0.0.1');      // Message shown on warning screen (optional).     $ZBX_GUI_ACCESS_MESSAGE = 'We are upgrading MySQL database till 15:00. Stay tuned...';
zh-cn	#### 配置  为了启用维护模式，必须修改 `maintenance.inc.php` 文件（位于网络服务器上 Zabbix HTML 文档目录的 /conf 中）以取消注释以下行：      // 维护模式。     define('ZBX_DENY_GUI_ACCESS', 1);      // IP 地址数组，允许连接到前端（可选）。     $ZBX_GUI_ACCESS_IP_RANGE = array('127.0.0.1');      // 警告屏幕上显示的消息（可选）。     $ZBX_GUI_ACCESS_MESSAGE = 'We are upgrading MySQL database till 15:00. Stay tuned...';

en-us	#### Configuration  In the *Type* field of [item configuration form](/manual/config/items/item) select Script then fill out required fields.  ![script\_item.png](../../../../../assets/en/manual/config/items/itemtypes/script_item.png)  All mandatory input fields are marked with a red asterisk.  The fields that require specific information for Script items are:  |Field|Description| |-----|-----------| |Key|Enter a unique key that will be used to identify the item.| |Parameters|Specify the variables to be passed to the script as the attribute and value pairs.<br>[Built-in macros](/manual/config/macros) {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.IP}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}, {ITEM.KEY.ORIG} and [user macros](/manual/config/macros/user_macros) are supported.| |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 must provide the logic for returning the metric value.<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>See also: [Additional JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects), [JavaScript Guide](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide).| |Timeout|JavaScript execution timeout (1-60s, default 3s).<br>Time suffixes are supported, e.g. 30s, 1m.|  
zh-cn	#### 配置  在[监控项配置表单](/manual/config/items/item)的*类型*字段选择脚本，然后填写必要字段。  ![script\_item.png](../../../../../assets/en/manual/config/items/itemtypes/script_item.png)  所有标有红色星号的为必填字段。  需要的脚本监控项特定信息的字段是：  |字段|描述| |-----|-----------| |Key|输入用于识别监控项唯一性的键。| |Parameters|指定传输给脚本的属性与值的配对。<br>支持的宏: [内建宏](/manual/config/macros) {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.IP}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}, {ITEM.KEY.ORIG} 与[用户自定义宏](/manual/config/macros/user_macros)。| |Script|在点击参数字段的空白所弹出的输入框中输入JavaScript代码（或在查看/编辑按钮后进入该输入框。代码必须提供返回指标数值的逻辑。<br>代码可以访问所有的参数，可以执行HTTP GET、POST、PUT、DELETE请求，并且可以控制HTTP标头和请求体<br>查看更多: [更多JavaScript对象](/manual/config/items/preprocessing/javascript/javascript_objects), [JavaScript Guide](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide)。| |Timeout|JavaScript执行超时时间(1-60s, 默认3s)。<br>支持时间后缀，如：30s, 1m。| 

en-us	#### Configuration  ODBC configuration is done by editing **odbcinst.ini** and **odbc.ini** files. These configuration files can be found in */etc* folder. The file **odbcinst.ini** may be missing and in this case it is necessary to create it manually.  **odbcinst.ini**      [mysql]     Description = General ODBC for MySQL     Driver      = /usr/lib64/libmyodbc5.so     Setup       = /usr/lib64/libodbcmyS.so      FileUsage   = 1  Please consider the following examples of **odbc.ini** configuration parameters.  -   An example with a connection through an IP:  ```{=html} <!-- --> ```     [TEST_MYSQL]                                                          Description = MySQL database 1                                        Driver  = mysql                                                       Port = 3306                                                           Server = 127.0.0.1  -   An example with a connection through an IP and with the use of     credentials. A Zabbix database is used by default:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED]                            Description = MySQL database 2                      Driver  = mysql                                     User = root                                         Port = 3306                                         Password = zabbix                                Database = zabbix                                  Server = 127.0.0.1                               -   An example with a connection through a socket and with the use of     credentials. A Zabbix database is used by default:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED_SOCK]                       Description = MySQL database 3                      Driver  = mysql                                     User = root                                         Password = zabbix                                Socket = /var/run/mysqld/mysqld.sock                Database = zabbix  All other possible configuration parameter options can be found in [MySQL official documentation](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html) web page.
zh-cn	### 配置  通过编辑**odbcinstn.ini**和**odbcst.ini**文件来完成ODBC配置。这些配置文件可以在*/etc*文件夹下找到。可能缺少**odbcinstn .ini**文件，在这种情况下，需要手动创建它。  **odbcinst.ini**      [mysql]     Description = General ODBC for MySQL     Driver      = /usr/lib64/libmyodbc5.so     Setup       = /usr/lib64/libodbcmyS.so      FileUsage   = 1   请考虑以下 **odbc.ini** 配置示例参数。  - 通过 IP 连接的示例：  ```{=html} <!-- --> ```     [TEST_MYSQL]                                                          Description = MySQL database 1     Driver  = mysql      Port = 3306      Server = 127.0.0.1  - 通过 IP 连接并使用凭据，默认使用 Zabbix 数据库:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED]                            Description = MySQL database 2                      Driver  = mysql                                     User = root                                         Port = 3306                                         Password = zabbix                                Database = zabbix                                  Server = 127.0.0.1    - 通过socket连接并使用凭据，默认使用 Zabbix 数据库：  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED_SOCK]                       Description = MySQL database 3                      Driver  = mysql                                     User = root                                         Password = zabbix                                Socket = /var/run/mysqld/mysqld.sock                Database = zabbix  其他配置和参数都可以参考[MySQL官方文档](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html)

en-us	### Configuration  Once you have [installed](/manual/installation/install) and [configured](/manual/appendix/config/zabbix_proxy) a proxy, it is time to configure it in the Zabbix frontend.
zh-cn	### 配置  如果你 [安装](/manual/installation/install) 和[配置](/manual/appendix/config/zabbix_proxy) 一个proxy , 下一步就是Zabbix前端配置。

en-us	#### Configuration  Overall, the process of setting up the notification should feel familiar to those who have set up alerts in Zabbix before.
zh-cn	#### 配置  总的来说，以前在Zabbix中设置过警报的同学应该熟悉设置通知的过程。

en-us	#### Configuration parameters  For Zabbix server/proxy new configuration parameters have been added for Vault authentication and retrieving database credentials:  -   VaultToken - Vault authentication token (see Zabbix     [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)     configuration file for details) -   VaultURL - Vault server HTTP\[S\] URL -   VaultDBPath - Vault path from where credentials for database will be     retrieved by keys 'password' and 'username' (for example:     secret/zabbix/database)  Zabbix server and Zabbix proxy read the Vault-related configuration parameters from zabbix\_server.conf and zabbix\_proxy.conf upon startup.  Zabbix server and Zabbix proxy will additionally read "VAULT\_TOKEN" environment variable once during startup and unset it so that it would not be available through forked scripts; it is an error if both VaultToken and VAULT\_TOKEN contain value.  ::: noteclassic Forward slash and colon are reserved symbols. Forward slash can only be used to separate mount point from path (e.g. secret/zabbix where mount point is "secret" and "zabbix" is path) and, in case of Vault macros, colon can only be used to separate path from key. It is possible to URL-encode "/" and ":" if there is need to create mount point with name that is separated by forward slash (e.g. foo/bar/zabbix where mount point is "foo/bar" and path is "zabbix" as "foo%2Fbar/zabbix") and if mount point name or path needs to contain colon. :::
zh-cn	#### 配置参数  对于 Zabbix 服务器/代理，为 Vault 身份验证和检索数据库凭据添加了新的配置参数：  - VaultToken - Vault 身份验证令牌（请参阅 Zabbix     [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy)配置文件详细） - VaultURL - Vault 服务器 HTTP\[S\] URL - VaultDBPath - 将通过密钥“密码”和“用户名”检索数据库凭据的保险库路径（例如：secret/zabbix/database）  Zabbix server 和 Zabbix proxy 在启动时会从 zabbix\_server.conf 和 zabbix\_proxy.conf 中读取 Vault 相关的配置参数。  Zabbix server 和 Zabbix proxy 会在启动时额外读取一次 "VAULT\_TOKEN" 环境变量并取消设置，使其无法通过 fork 脚本使用；如果 VaultToken 和 VAULT\_TOKEN 都包含值，则这是一个错误。  ::: noteclassic 正斜杠和冒号是保留符号。正斜杠只能用于将挂载点与路径分开（例如，secret/zabbix，其中挂载点为“secret”，“zabbix”为路径），对于 Vault 宏，冒号只能用于将路径与密钥分开。如果需要创建名称由正斜杠分隔的挂载点（例如 foo/bar/zabbix，挂载点为“foo/bar”且路径为“ zabbix" 为 "foo%2Fbar/zabbix") 并且挂载点名称或路径是否需要包含冒号。 :::

en-us	#### Configuration  Preprocessing rules are defined in the **Preprocessing** tab of the item [configuration](/manual/config/items/item#configuration) form.  ![](../../../../assets/en/manual/config/items/item_c.png){width="600"}  ::: noteimportant An item will become [unsupported](/manual/config/items/item#unsupported_items) if any of the preprocessing steps fails, unless custom error handling has been specified using a *Custom on fail* option for supported transformations.\ \ For log items, log metadata (without value) will always reset item unsupported state and make item supported again, even if the initial error occurred after receiving a log value from agent. :::  [User macros](/manual/config/macros/user_macros) and user macros with context are supported in item value preprocessing parameters, including JavaScript code.  ::: noteclassic  Context is ignored when a macro is replaced with its value. Macro value is inserted in the code as is, it is not possible to add additional escaping before placing the value in the JavaScript code. Please be advised, that this can cause JavaScript errors in some cases.  :::  |Type|<|<| |-|----------|----------------------------------------| | |*Transformation*|Description| |Text|<|<| | |*Regular expression*|Match the value to the <pattern> regular expression and replace value with <output>. The regular expression supports extraction of maximum 10 captured groups with the \\N sequence. Failure to match the input value will make the item unsupported.<br>Parameters:<br>**pattern** - regular expression<br>**output** - output formatting template. An \\N (where N=1…9) escape sequence is replaced with the Nth matched group. A \\0 escape sequence is replaced with the matched text.<br>Please refer to [regular expressions](/manual/regular_expressions#example) section for some existing examples.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value or set a specified error message.| |^|*Replace*|Find the search string and replace it with another (or nothing). All occurrences of the search string will be replaced.<br>Parameters:<br>**search string** - the string to find and replace, case-sensitive (required)<br>**replacement** - the string to replace the search string with. The replacement string may also be empty effectively allowing to delete the search string when found.<br>It is possible to use escape sequences to search for or replace line breaks, carriage return, tabs and spaces "\\n \\r \\t \\s"; backslash can be escaped as "\\\\" and escape sequences can be escaped as "\\\\n". Escaping of line breaks, carriage return, tabs is automatically done during low-level discovery.| |^|*Trim*|Remove specified characters from the beginning and end of the value.| |^|*Right trim*|Remove specified characters from the end of the value.| |^|*Left trim*|Remove specified characters from the beginning of the value.| |Structured data|<|<| | |*XML XPath*|Extract value or fragment from XML data using XPath functionality.<br>For this option to work, Zabbix server must be compiled with libxml support.<br>Examples:<br>`number(/document/item/value)` will extract `10` from `<document><item><value>10</value></item></document>`<br>`number(/document/item/@attribute)` will extract `10` from `<document><item attribute="10"></item></document>`<br>`/document/item` will extract `<item><value>10</value></item>` from `<document><item><value>10</value></item></document>`<br>Note that namespaces are not supported.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error-handling options: either to discard the value, set a specified value or set a specified error message.| |^|*JSON Path*|Extract value or fragment from JSON data using [JSONPath functionality](/manual/config/items/preprocessing/jsonpath_functionality).<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error-handling options: either to discard the value, set a specified value or set a specified error message.| |^|*CSV to JSON*|Convert CSV file data into JSON format.<br>For more information, see: [CSV to JSON preprocessing](/manual/config/items/preprocessing/csv_to_json#csv_header_processing).| |^|*XML to JSON*|Convert data in XML format to JSON.<br>For more information, see: [Serialization rules](/manual/config/items/preprocessing/javascript/javascript_objects#serialization_rules).<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error-handling options: either to discard the value, set a specified value or set a specified error message.| |Arithmetic|<|<| | |*Custom multiplier*|Multiply the value by the specified integer or floating-point value.<br>Use this option to convert values received in KB, MBps, etc into B, Bps. Otherwise Zabbix cannot correctly set [prefixes](/manual/appendix/suffixes) (K, M, G etc).<br>*Note* that if the item type of information is *Numeric (unsigned)*, incoming values with a fractional part will be trimmed (i.e. '0.9' will become '0') before the custom multiplier is applied.<br>Supported: scientific notation, for example, `1e+70` (since version 2.2); user macros and LLD macros (since version 4.0); strings that include macros, for example, `{#MACRO}e+10`, `{$MACRO1}e+{$MACRO2}`(since version 5.2.3)<br>The macros must resolve to an integer or a floating-point number.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |Change|<|<| | |*Simple change*|Calculate the difference between the current and previous value.<br>Evaluated as **value**-**prev\_value**, where<br>*value* - current value; *prev\_value* - previously received value<br>This setting can be useful to measure a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value.<br>Only one change operation per item is allowed.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Change per second*|Calculate the value change (difference between the current and previous value) speed per second.<br>Evaluated as (**value**-**prev\_value**)/(**time**-**prev\_time**), where<br>*value* - current value; *prev\_value* - previously received value; *time* - current timestamp; *prev\_time* - timestamp of previous value.<br>This setting is extremely useful to get speed per second for a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters.<br>*Note*: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to *Numeric (float)*, even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating-point values are large and may exceed the 'float' field length in which case the entire value may be lost, it is actually suggested to use *Numeric (unsigned)* and thus trim only the decimal part.<br>Only one change operation per item is allowed.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |Numeral systems|<|<| | |*Boolean to decimal*|Convert the value from boolean format to decimal. The textual representation is translated into either 0 or 1. Thus, 'TRUE' is stored as 1 and 'FALSE' is stored as 0. All values are matched in a case-insensitive way. Currently recognized values are, for:<br>*TRUE* - true, t, yes, y, on, up, running, enabled, available, ok, master<br>*FALSE* - false, f, no, n, off, down, unused, disabled, unavailable, err, slave<br>Additionally, any non-zero numeric value is considered to be TRUE and zero is considered to be FALSE.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Octal to decimal*|Convert the value from octal format to decimal.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Hexadecimal to decimal*|Convert the value from hexadecimal format to decimal.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |Custom scripts|<|<| | |*JavaScript*|Enter JavaScript code in the block that appears when clicking in the parameter field or on a pencil icon.<br>Note that available JavaScript length depends on the [database used](#custom_script_limit).<br>For more information, see: [Javascript preprocessing](/manual/config/items/preprocessing/javascript).| |Validation|<|<| | |*In range*|Define a range that a value should be in by specifying minimum/maximum values (inclusive).<br>Numeric values are accepted (including any number of digits, optional decimal part and optional exponential part, negative values). User macros and low-level discovery macros can be used. The minimum value should be less than the maximum.<br>At least one value must exist.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Matches regular expression*|Specify a regular expression that a value must match.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Does not match regular expression*|Specify a regular expression that a value must not match.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Check for error in JSON*|Check for an application-level error message located at JSONpath. Stop processing if succeeded and the message is not empty; otherwise, continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to the user as is, without adding preprocessing step information.<br>No error will be reported in case of failing to parse invalid JSON.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Check for error in XML*|Check for an application-level error message located at XPath. Stop processing if succeeded and the message is not empty; otherwise, continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to the user as is, without adding preprocessing step information.<br>No error will be reported in case of failing to parse invalid XML.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Check for error using a regular expression*|Check for an application-level error message using a regular expression. Stop processing if succeeded and the message is not empty; otherwise, continue processing with the value that was before this preprocessing step. Note that these external service errors are reported to the user as is, without adding preprocessing step information.<br>Parameters:<br>**pattern** - regular expression<br>**output** - output formatting template. An \\N (where N=1…9) escape sequence is replaced with the Nth matched group. A \\0 escape sequence is replaced with the matched text.<br>If you mark the *Custom on fail* checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.| |^|*Check for not supported value*|Check if there was an error in retrieving item value. Normally that would lead to the item turning unsupported, but you may modify that behavior by specifying the *Custom on fail* error-handling options: to discard the value, to set a specified value (in this case the item will stay supported and the value can be used in triggers) or set a specified error message. Note that for this preprocessing step, the *Custom on fail* checkbox is grayed out and always marked.<br>This step is always executed as the first preprocessing step and is placed above all others after saving changes to the item. It can be used only once.<br>Supported since 5.2.0.| |Throttling|<|<| | |*Discard unchanged*|Discard a value if it has not changed.<br>If a value is discarded, it is not saved in the database and Zabbix server has no knowledge that this value was received. No trigger expressions will be evaluated, as a result, no problems for related triggers will be created/resolved. Functions will work only based on data that is actually saved in the database. As trends are built based on data in the database, if there is no value saved for an hour then there will also be no trends data for that hour.<br>Only one throttling option can be specified for an item.<br>*Note* that it is possible for items monitored by Zabbix proxy that very small value differences (less than 0.000001) are correctly not discarded by proxy, but are stored in the history as the same value if the Zabbix server database [has not been upgraded](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values).| |^|*Discard unchanged with heartbeat*|Discard a value if it has not changed within the defined time period (in seconds).<br>Positive integer values are supported to specify the seconds (minimum - 1 second). Time suffixes can be used in this field (e.g. 30s, 1m, 2h, 1d). User macros and low-level discovery macros can be used in this field.<br>If a value is discarded, it is not saved in the database and Zabbix server has no knowledge that this value was received. No trigger expressions will be evaluated, as a result, no problems for related triggers will be created/resolved. Functions will work only based on data that is actually saved in the database. As trends are built based on data in the database, if there is no value saved for an hour then there will also be no trends data for that hour.<br>Only one throttling option can be specified for an item.<br>*Note* that it is possible for items monitored by Zabbix proxy that very small value differences (less than 0.000001) are correctly not discarded by proxy, but are stored in the history as the same value if the Zabbix server database [has not been upgraded](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values).| |Prometheus|<|<| | |*Prometheus pattern*|Use the following query to extract required data from Prometheus metrics.<br>See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for more details.| |^|*Prometheus to JSON*|Convert required Prometheus metrics to JSON.<br>See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for more details.|  ::: noteimportant  For change and throttling preprocessing steps Zabbix has to remember the last value to calculate/compare the new value as required. These previous values are handled by the preprocessing manager. If Zabbix server or proxy is restarted or there is any change made to preprocessing steps the last value of the corresponding item is reset, resulting in:  -   for *Simple change*, *Change per second* steps - the next value will     be ignored because there is no previous value to calculated change     from; -   for *Discard unchanged*. *Discard unchanged with heartbeat* steps -     the next value will never be discarded, even if it should have been     because of discarding rules.   :::  Item's *Type of information* parameter is displayed at the bottom of the tab when at least one preprocessing step is defined. If required, it is possible to change the type of information without leaving the *Preprocessing* tab. See [Creating an item](/manual/config/items/item) for the detailed parameter description.  ::: notetip If you use a custom multiplier or store value as *Change per second* for items with the type of information set to *Numeric (unsigned)* and the resulting calculated value is actually a float number, the calculated value is still accepted as a correct one by trimming the decimal part and storing the value as an integer. :::
zh-cn	 #### 配置  预处理规则在监控项的 **预处理** 标签中进行[配置](/manual/config/items/item#configuration) 。  ![](../../../../assets/en/manual/config/items/item_c.png){width="600"}  ::: noteimportant  任何预处理步骤失败都将导致监控项变成[不支持的](/manual/config/items/item#unsupported_items)，除非使用自定义失败选项（*Custom on fail*）指定自定义错误处理办法。\ \ 对于日志监控项，日志元数据(没有值)将总是重置监控项的不支持的状态，使监控项再次受到支持，即使在从agent接收到日志值后发生了初始错误。 :::  [用户宏](/manual/config/macros/user_macros) 在监控项值预处理参数中支持带有上下文的用户宏，包含JavaScript代码。  ::: noteclassic 当宏被它的值替换时，上下文将被忽略。宏值将直接插入到代码中，在将值放入JavaScript代码之前不能添加额外的转义。请注意，在某些情况下，这可能会导致JavaScript错误。 :::  |类型|<|<| |----|----|----| | |*转换动作*|描述| |文本|<|<| | |*正则表达式*|将值与 <pattern> 正则表达式匹配，并将值替换为 <output>。 正则表达式支持使用 \N 序列提取最多 10 个捕获的组。 输入值不匹配将使该监控项不受支持。<br>参数:<br>**pattern** - 正则表达式<br>**output** - 输出格式模板。 \\N（其中 N=1…9）转义序列将替换为第 N 个匹配组。 \\0 转义序列将替换为匹配的文本。<br>请参考 [正则表达式](/manual/regular_expressions#example) 部分现有示例。<br>如果你勾选了 *自定义失败* 复选框, 则在预处理步骤失败时，该监控项将不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| |^|*替换*|找到搜索字符串并将其替换为另一个（或没有）。 将替换所有出现的搜索字符串。<br>参数:<br>**search string** - 要查找和替换的字符串，区分大小写（必需）<br>**replacement** - 用于替换搜索字符串的字符串。 替换字符串也可以为空，有效地允许在找到时删除搜索字符串。<br>可以使用转义序列来搜索或替换换行符、回车符、制表符和空格“\\n \\r \\ t \\s"; 反斜杠可以转义为“\\\\”，转义序列可以转义为“\\\\n”。 在底层自动发现期间自动完成换行符、回车、制表符的转义。| |^|*截取*|从值的开头和结尾删除指定的字符。| |^|*右截取*|从值的末尾删除指定的字符。| |^|*左截取*|从值的开头删除指定的字符。| |结构化数据|<|<| | |*XML XPath*|使用 XPath 功能从 XML 数据中提取值或片段。<br>要使此选项起作用，必须在编译 Zabbix server 时使用 libxml 参数。<br>示例:<br>`number(/document/item/value)` 将从 `<document><item><value>10</value></item></document>`提取 `10` <br>`number(/document/item/@attribute)` 将从 `<document><item attribute="10"></item></document>` 提取 `10` <br>`/document/item` will extract `<item><value>10</value></item>` from `<document><item><value>10</value></item></document>`<br>注意，不支持命名空间。<br>如果您勾选了 *自定义失败* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误信息。| |^|*JSON Path*|使用 [JSONPath 功能](/manual/config/items/preprocessing/jsonpath_functionality) 从 JSON 数据中提取值或片段 。<br>如果您勾选了 *自定义失败* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误信息。| |^|*CSV to JSON*|将CSV文件数据转换为JSON格式。<br>有关更多信息，请参见: [CSV to JSON 预处理](/manual/config/items/preprocessing/csv_to_json#csv_header_processing).| |^|*XML to JSON*|将 XML 格式的数据转换为 JSON。<br>有关更多信息，请参见:  [序列化规则](/manual/config/items/preprocessing/javascript/javascript_objects#serialization_rules)。<br>如果您勾选了 *自定义失败* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误信息。| |算术|<|<| | |*自定义乘数*|将该值乘以指定的整数或浮点值。<br>使用此选项将以 KB、MBps 等形式接收的值转换为 B、Bps。 否则 Zabbix无法正确设置(K, M, G 等) [后缀](/manual/appendix/suffixes) (K, M, G etc).<br>*注意*  如果监控项类型是 _数字 (无符号)_, 在传入自定义乘法器之前带有小数部分的传入值将被裁剪 ('0.9' 将变成 '0')。<br>支持: 科学记数法, 例如, `1e+70` (从2.2开始); 用户宏和LLD宏 (从4.0版本开始); 包含宏的字符串, 例如, `{#MACRO}e+10`, `{$MACRO1}e+{$MACRO2}` (从5.2.3版本开始)<br>宏必须解析为整数或浮点数。<br>如果你使用 *自定义失败* 复选框, 在预处理步骤失败的情况下，该项不会变得不受支持，并且可以指定自定义错误处理选项:丢弃该值、设置指定值或设置指定的错误消息。| |更改|<|<| |<|*简单更改*|计算当前值与先前值的差值。<br>计算为**value**-**prev\_value**，其中<br>*value* - 当前值； *prev\_value* - 以前收到的值<br>此设置可用于衡量不断增长的值。 如果当前值小于前一个值，Zabbix 会丢弃该差异（不存储任何内容）并等待另一个值。<br>每个监控项只允许进行一次更改操作。<br>如果您选中 *Custom on fail* 复选框 ，如果预处理步骤失败，该项目将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| |^|*每秒更改*|计算每秒速度的值变化（当前值与先前值之间的差异）。<br>计算为 (**value**-**prev\_value**)/(**time**-**prev\_time **), 其中<br>*value* - 当前值； *prev\_value* - 先前收到的值； *time* - 当前时间戳； *prev\_time* - 前一个值的时间戳。<br>此设置对于获取不断增长的值的每秒速度非常有用。如果当前值小于前一个值，Zabbix 会丢弃该差异（不存储任何内容）并等待另一个值。这有助于正确处理，例如，32 位 SNMP 计数器的包装（溢出）。<br>*注意*：由于此计算可能产生浮点数，建议设置“信息类型”到 *Numeric (浮点型)*，即使传入的原始值是整数。这对于小数部分很重要的小数尤其重要。如果浮点值很大并且可能超过 'float' 字段长度，在这种情况下整个值可能会丢失，实际上建议使用 *Numeric (unsigned)* 并且只修剪小数部分。<br>每个监控项只允许进行一次更改操作。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：要么丢弃value，设置一个指定的值，或者设置一个指定的错误信息。| |数字系统|<|<| | |*布尔到十进制*|将值从布尔格式转换为十进制。 文本表示被转换为 0 或 1。因此，“TRUE”存储为 1，“FALSE”存储为 0。所有值都以不区分大小写的方式匹配。 当前识别的值为：<br>*TRUE* - true, t, yes, y, on, up, running, enabled, available, ok, master<br>*FALSE* - false, f, no, n, off, down, unused, disabled, unavailable, err, slave<br>此外，任何非零数值都被视为 TRUE，而零被视为 FALSE。<br>如果您标记 *Custom on fail* 复选框 ，如果预处理步骤失败，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| | |*八进制转十进制*|将值从八进制格式转换为十进制。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：要么丢弃 value，设置一个指定的值，或者设置一个指定的错误信息。| | |*十六进制转十进制*|将值从十六进制格式转换为十进制。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：要么丢弃 value，设置一个指定的值，或者设置一个指定的错误信息。| |自定义脚本|<|<| | |*JavaScript*|在单击参数字段或铅笔图标时出现的块中输入JavaScript代码。<br>注意, 可用的JavaScript长度取决于所使用的 [使用的数据库](#custom_script_limit).<br>有关更多信息，请参见:[Javascript 预处理](/manual/config/items/preprocessing/javascript).| |验证|<|<| | |*在范围内*|通过指定最小/最大值（包括）来定义值应在的范围。<br>接受数值（包括任意位数、可选的小数部分和可选的指数部分、负值）。 可以使用用户宏和底层自动发现宏。 最小值应小于最大值。<br>必须至少存在一个值。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项不会变得不受支持，并且有可能 指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| |^|*匹配正则表达式*|指定一个值必须匹配的正则表达式。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：要么丢弃值，设置一个指定的值，或者设置一个指定的错误信息。| |^|*不匹配正则表达式*|指定一个值不能匹配的正则表达式。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：要么 丢弃该值，设置一个指定的值，或设置一个指定的错误消息。| |^|*检查 JSON 中的错误*|检查位于 JSONpath 的应用程序级错误消息。 如果成功并且消息不为空则停止处理； 否则，使用此预处理步骤之前的值继续处理。 请注意，这些外部服务错误会按原样报告给用户，而不添加预处理步骤信息。<br>如果无法解析无效 JSON，则不会报告错误。<br>如果您选中 *Custom on fail* 复选框 ，如果预处理步骤失败，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| |^|*检查 XML 中的错误*|检查位于 XPath 的应用程序级错误消息。 如果成功并且消息不为空则停止处理； 否则，使用此预处理步骤之前的值继续处理。 请注意，这些外部服务错误将按原样报告给用户，而不添加预处理步骤信息。<br>如果无法解析无效 XML，则不会报告错误。<br>如果您选中 *Custom on fail* 复选框 ，如果预处理步骤失败，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项：丢弃值、设置指定值或设置指定错误消息。| |^|*使用正则表达式检查错误*|使用正则表达式检查应用程序级错误消息。 如果成功并且消息不为空则停止处理； 否则，使用此预处理步骤之前的值继续处理。 请注意，这些外部服务错误按原样报告给用户，无需添加预处理步骤信息。<br>参数：<br>**pattern** - 正则表达式<br>**output** - 输出格式模板。 \\N（其中 N=1…9）转义序列将替换为第 N 个匹配组。 \\0 转义序列将替换为匹配的文本。<br>如果您选中 *Custom on fail* 复选框，则在预处理步骤失败的情况下，该监控项将不会变得不受支持，并且可以指定自定义错误处理选项： 要么丢弃该值，设置一个指定的值，或者设置一个指定的错误消息。| |^|*检查不支持的值*|检查检索监控项值是否有错误。 通常这会导致监控项变得不受支持，但您可以通过指定 *Custom on fail* 错误处理选项来修改该行为：丢弃值，设置指定值（在这种情况下，监控项将保持支持并且 value 可以在触发器中使用）或设置指定的错误消息。 请注意，对于此预处理步骤，*失败时自定义*复选框灰显并始终标记。<br>此步骤始终作为第一个预处理步骤执行，并在保存对监控项的更改后置于所有其他步骤之上。 它只能使用一次。<br>从 5.2.0 开始支持。| |节流|<|<| |<|*丢弃不变*|如果一个值没有改变，则丢弃它。<br>如果一个值被丢弃，它不会保存在数据库中，并且 Zabbix 服务器不知道该值已被接收。 不会评估触发器表达式，因此不会创建/解决相关触发器的问题。 函数仅基于实际保存在数据库中的数据起作用。 由于趋势是基于数据库中的数据构建的，如果一个小时内没有保存任何值，则该小时也不会有趋势数据。<br>只能为一个监控项指定一个限制选项。<br>* 注意* Zabbix 代理监控的监控项有可能非常小的值差异（小于 0.000001）不会被代理正确丢弃，但如果 Zabbix 服务器数据库 [尚未升级](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values)，则作为相同的值存储在历史记录中| |^|*丢弃不变的心跳*|如果值在定义的时间段内（以秒为单位）未更改，则丢弃该值。<br>支持正整数值来指定秒数（最小值 - 1 秒）。该字段可以使用时间后缀（例如 30s、1m、2h、1d）。在该字段中可以使用用户宏和底层自动发现宏。<br>如果一个值被丢弃，它不会保存在数据库中，并且 Zabbix 服务器不知道该值已被接收。不会评估触发器表达式，因此不会创建/解决相关触发器的问题。函数仅基于实际保存在数据库中的数据起作用。由于趋势是基于数据库中的数据构建的，如果一个小时内没有保存任何值，则该小时也不会有趋势数据。<br>只能为一个监控项指定一个限制选项。<br>*注意* Zabbix 代理监控的监控项有可能非常小的值差异（小于 0.000001）不会被代理正确丢弃，但如果 Zabbix 服务器数据库 [尚未升级](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500#enabling_extended_range_of_numeric_float_values)，则作为相同的值存储在历史记录中。| |Prometheus|<|<| | |*Prometheus pattern*|使用以下查询从 Prometheus 指标中提取所需数据。<br>有关更多信息，请参考：[Prometheus checks](/manual/config/items/itemtypes/prometheus)| |^|*Prometheus to JSON*|将所需的 Prometheus 指标转换为 JSON。<br>有关更多信息，请参考：[Prometheus checks](/manual/config/items/itemtypes/prometheus)|  ::: noteimportant 对于更改和限制预处理步骤，需要使用以前的值来计算/比较新值。以前的值由预处理管理器处理，预处理步骤配置在进行更改或Zabbix server/proxy重新启动时重置。由于先前的值重置:  -   对于*简单改变*, *每秒更改* 步骤 - 下一个值将被忽略，因为没有先前的值来计算更改; -   对于 *丢弃没有改变的数据*. *带心跳检查丢弃不变化的数据* 步骤 - 下一个值永远不会被丢弃, 即使它应该因为丢弃规则而被丢弃，也不会丢弃。 :::   当定义了至少一个预处理步骤时，监控项的*信息类型*参数显示在选项卡的底部。 如果需要，可以在不离开 *Preprocessing* 选项卡的情况下更改信息类型。 详细参数说明见 [创建监控项](/manual/config/items/item) 。  ::: notetip 如果您对信息类型设置为 *Numeric (unsigned)* 的监控项使用自定义乘数或将值存储为 *Change per second* 并且得到的计算值实际上是一个浮点数，通过修剪小数部分并将值存储为整数，计算值仍然被接受为正确的值。 :::

en-us	 #### Configuration  Providing you have the HTTP master item configured, you need to create a [dependent item](/manual/config/items/itemtypes/dependent_items) that uses a Prometheus preprocessing step:  -   Enter general dependent item parameters in the configuration form -   Go to the Preprocessing tab -   Select a Prometheus preprocessing option (*Prometheus pattern* or     *Prometheus to JSON*)  ![](../../../../../assets/en/manual/config/items/itemtypes/prometheus_item.png)  The following parameters are specific to the *Prometheus pattern* preprocessing option:  |Parameter|Description|Examples| |--|------|------| |*Pattern*|To define the required data pattern you may use a query language that is similar to Prometheus query language (see [comparison table](#query-language-comparison)), e.g.:<br><metric name> - select by metric name<br>{\_\_name\_\_="<metric name>"} - select by metric name<br>{\_\_name\_\_=\~"<regex>"} - select by metric name matching a regular expression<br>{<label name>="<label value>",...} - select by label name<br>{<label name>=\~"<regex>",...} - select by label name matching a regular expression<br>{\_\_name\_\_=\~".\*"}==<value> - select by metric value<br>Or a combination of the above:<br><metric name>{<label1 name>="<label1 value>",<label2 name>=\~"<regex>",...}==<value><br><br>Label value can be any sequence of UTF-8 characters, but the backslash, double-quote and line feed characters have to be escaped as `\\`, `\"` and `\n` respectively; other characters shall not be escaped.|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Result processing*|Specify whether to return the value, the label or apply the appropriate function (if the pattern matches several lines and the result needs to be aggregated):<br>**value** - return metric value (error if multiple lines matched)<br>**label** - return value of the label specified in the *Label* field (error if multiple metrics are matched)<br>**sum** - return the sum of values<br>**min** - return the minimum value<br>**max** - return the maximum value<br>**avg** - return the average value<br>**count** - return the count of values<br>This field is only available for the *Prometheus pattern* option. |See also examples of using parameters below.| |*Output*|Define label name (optional). In this case the value corresponding to the label name is returned.<br>This field is only available for the *Prometheus pattern* option, if 'Label' is selected in the *Result processing* field.| |  **Examples of using parameters**  1. The most common use case is to return the **value**. To return  the value of `/var/db` from:  > `node_disk_usage_bytes{path="/var/cache"} 2.1766144e+09`<br> > `node_disk_usage_bytes{path="/var/db"} 20480`<br> > `node_disk_usage_bytes{path="/var/dpkg"} 8192`<br> > `node_disk_usage_bytes{path="/var/empty"} 4096`  use the following parameters:  * *Pattern* - `node_disk_usage_bytes{path="/var/db"}` * *Result processing* - select 'value'  2. You may also be interested in the **average** value of all  `node_disk_usage_bytes` parameters:  * *Pattern* - `node_disk_usage_bytes` * *Result processing* - select 'avg'  3. While Prometheus supports only numerical data, it is popular to use a  workaround that allows to return the relevant textual description as well.  This can be accomplished with a filter and specifying the label. So, to  return the value of the 'color' label from  > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="green"} 1`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="red"} 0`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="yellow"} 0`  use the following parameters:  * *Pattern* - `elasticsearch_cluster_health_status {cluster="elasticsearch"} == 1` * *Result processing* - select 'label' * *Label* - specify 'color'  The filter (based on the numeric value '1') will match the appropriate row, while the label will  return the health status description (currently 'green'; but potentially also 'red' or 'yellow').
zh-cn	#### 配置  已经事先正确配置了 HTTP代理类型的主要监控项，你需要创建一个 [相关监控项](/manual/config/items/itemtypes/dependent_items) 来应用Prometheus 预处理步骤：  - 在配置表单中填入一般从属监控项的参数 - 前往预处理选项卡 - 选择一个 **Prometheus** 预处理选项（*Prometheus正则匹配* or *Prometheus转JSON*）  ![](../../../../../assets/en/manual/config/items/itemtypes/prometheus_item.png)  以下参数特定于 *Prometheus正则匹配* 预处理选项：  |参数|描述|示例| |---------|-----------|--------| |*Pattern*|要定义所需数据的正则匹配规则，可以使用与PromQL（Prometheus 查询语言）十分类似的检索语言 (详见 [对比表]](#query_language_comparison)), 举个例子：<br><metric name> - 指定指标名称<br>{\_\_name\_\_=\~"<regex>"} - 根据正则表达式，匹配指标名称<br>{<label name>="<label value>",...} - 指定标签名称<br>{<label name>=\~"<regex>",...} - 根据正则表达式，匹配标签名称<br>{\_\_name\_\_=\~".\*"}==<value> - 指定指标值<br>或者将以上的条件任意组合：<br><metric name>{<label1 name>="<label1 value>",<label2 name>=\~"<regex>",...}==<value><br><br>标签名称可以是任何UTF-8字符的序列，但对于反斜杠、双引号和换行符必须使用转义，就像 `\\`，`\"`， `\n`；其他字符不应被转义。|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Result processing*| 定义如何返回处理结果，提供了**值**，**标签** 或应用适当的函数（如正则匹配的到了多行结果，需要对这些结果进行简单聚合）:<br>**值** - 返回指标的值（当匹配到多行记录时，会引发错误）<br>**标签** - 在*标签*字段中指定的标签返回值（当匹配到多个指标时，会引发错误）<br>**总和** - 返回值的总和<br>**最小值** - 返回最小值<br>**max** - 返回最大值<br>**平均值** - 返回平均值<br>**计数** - 返回值的计数<br>此参数字段仅适用于**Prometheus正则匹配**预处理步骤。 | 实际用例见表后。 | |*Output*|定义标签名称（可选）。 在这种情况下，返回与标签名称对应的值。<br>如果在 *Result processing* 字段中选择了“Label”，则此字段仅适用于 *Prometheus pattern* 选项。| |

en-us	#### Configuration  Real-time export of trigger events, item values and trends is configured by specifying a directory for the export files - see the `ExportDir` parameter in server [configuration](/manual/appendix/config/zabbix_server).  Two other parameters are available:  -   `ExportFileSize` may be used to set the maximum allowed size of an     individual export file. When a process needs to write to a file it     checks the size of the file first. If it exceeds the configured size     limit, the file is renamed by appending .old to its name and a new     file with the original name is created.  ::: noteimportant A file will be created per each process that will write data (i.e. approximately 4-30 files). As the default size per export file is 1G, keeping large export files may drain the disk space fast. :::  -   `ExportType` allows to specify which entity types (events, history,     trends) will be exported.
zh-cn	#### 配置  为导出文件指定目录来配置触发事件、监控项的值和趋势的实时导出 - 请参阅服务器中的  `ExportDir`参数 [configuration](/manual/appendix/config/zabbix_server).  另外以下两个参数可配置：  -   `ExportFileSize` 可用于设置允许导出的文件的最大值。当进程需要写入文件时，它会首先检查文件的大小。如果超出配置的大小限制，则以 .old 结尾重命名该文件，并创建一个和原名称相同的新文件。  ::: noteimportant 每个将要写入数据的进程都会创建一个文件（大约4-30个文件）。由于每个导出文件的默认大小为 1G，因此保留较大的导出文件可能会加快磁盘空间的占用。 :::  -   `ExportType` 允许指定将导出哪些实体类型（事件、历史记录、趋势）。

en-us	##### Configuration syncer  Performance of the configuration syncer has been improved.  It is recommended to increase the CacheSize on server/proxy  if there is a large amount of templates. It is also recommended  to remove unused templates.  Note that the default CacheSize on server/proxy has been increased  to 32M.
zh-cn	##### 配置同步器  配置同步器的性能得到了改进。如果有大量模板，建议增加 server/proxy 上的 CacheSize。同时建议删除未使用的模板。  请注意，server/proxy 上的默认 CacheSize 已增加到 32M。

en-us	#### Configuration  Tags can be entered in a dedicated tab, for example, in trigger configuration:  ![](../../../assets/en/manual/config/tags_trigger.png)
zh-cn	#### 配置  可以在专用选项卡中输入标签，例如在触发器配置：  ![](../../../assets/en/manual/config/tags_trigger.png)

en-us	#### Configuration  The **Host** tab contains general host attributes:  ![](../../../../assets/en/manual/config/host_a.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|<|Description| |-|----------|----------------------------------------| |*Host name*|<|Enter a unique host name. Alphanumerics, spaces, dots, dashes and underscores are allowed. However, leading and trailing spaces are disallowed.<br>*Note:* With Zabbix agent running on the host you are configuring, the agent [configuration file](/manual/appendix/config/zabbix_agentd) parameter *Hostname* must have the same value as the host name entered here. The name in the parameter is needed in the processing of [active checks](/manual/appendix/items/activepassive).| |*Visible name*|<|Enter a unique visible name for the host. If you set this name, it will be the one visible in lists, maps, etc instead of the technical host name. This attribute has UTF-8 support.| |*Templates*|<|Link [templates](/manual/config/templates) to the host. All entities (items, triggers, graphs, etc) will be inherited from the template.<br>To link a new template, start typing the template name in the *Link new templates* field. A list of matching templates will appear; scroll down to select. Alternatively, you may click on *Select* next to the field and select templates from the list in a popup window. The templates that are selected in the *Link new templates* field will be linked to the host when the host configuration form is saved or updated.<br>To unlink a template, use one of the two options in the *Linked templates* block:<br>*Unlink* - unlink the template, but preserve its items, triggers and graphs<br>*Unlink and clear* - unlink the template and remove all its items, triggers and graphs<br>Listed template names are clickable links leading to the template configuration form.| |*Groups*|<|Select host groups the host belongs to. A host must belong to at least one host group. A new group can be created and linked to the host group by adding a non-existing group name.| |*Interfaces*|<|Several host interface types are supported for a host: *Agent*, *SNMP*, *JMX* and *IPMI*.<br>No interfaces are defined by default. To add a new interface, click on *Add* in the *Interfaces* block, select the interface type and enter *IP/DNS*, *Connect to* and *Port* info.<br>*Note:* Interfaces that are used in any items cannot be removed and link *Remove* is grayed out for them.<br>See [Configuring SNMP monitoring](/manual/config/items/itemtypes/snmp#configuring_snmp_monitoring) for additional details on configuring an SNMP interface (v1, v2 and v3).| | |*IP address*|Host IP address (optional).| |^|*DNS name*|Host DNS name (optional).| |^|*Connect to*|Clicking the respective button will tell Zabbix server what to use to retrieve data from agents:<br>**IP** - Connect to the host IP address (recommended)<br>**DNS** - Connect to the host DNS name| |^|*Port*|TCP/UDP port number. Default values are: 10050 for Zabbix agent, 161 for SNMP agent, 12345 for JMX and 623 for IPMI.| |^|*Default*|Check the radio button to set the default interface.| |*Description*|<|Enter the host description.| |*Monitored by proxy*|<|The host can be monitored either by Zabbix server or one of Zabbix proxies:<br>**(no proxy)** - host is monitored by Zabbix server<br>**Proxy name** - host is monitored by Zabbix proxy "Proxy name"| |*Enabled*|<|Mark the checkbox to make the host active, ready to be monitored. If unchecked, the host is not active, thus not monitored.|  The **IPMI** tab contains IPMI management attributes.  |Parameter|Description| |--|--------| |*Authentication algorithm*|Select the authentication algorithm.| |*Privilege level*|Select the privilege level.| |*Username*|User name for authentication. User macros may be used.| |*Password*|Password for authentication. User macros may be used.|  The **Tags** tab allows you to define host-level [tags](/manual/config/tagging). All problems of this host will be tagged with the values entered here.  ![](../../../../assets/en/manual/config/host_d.png)  User macros, {INVENTORY.\*} macros, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros are supported in tags.  The **Macros** tab allows you to define host-level [user macros](/manual/config/macros/user_macros) as a name-value pairs. Note that macro values can be kept as plain text, secret text or Vault secret. Adding a description is also supported.  ![](../../../../assets/en/manual/config/host_e.png)  You may also view here template-level and global user macros if you select the *Inherited and host macros* option. That is where all defined user macros for the host are displayed with the value they resolve to as well as their origin.  ![](../../../../assets/en/manual/config/host_e2.png){width="600"}  For convenience, links to respective templates and global macro configuration are provided. It is also possible to edit a template/global macro on the host level, effectively creating a copy of the macro on the host.  The **Host inventory** tab allows you to manually enter [inventory](inventory) information for the host. You can also select to enable *Automatic* inventory population, or disable inventory population for this host.  ![](../../../../assets/en/manual/config/host_f.png)  If inventory is enabled (manual or automatic), a green dot is displayed with the tab name.
zh-cn	#### 配置   **主机** 选项卡包含常规主机属性：  ![](../../../../assets/en/manual/config/host_a.png)  所有标有红色星号的为必填字段。  |参数|<|描述| |---------|-|-----------| |*主机名*|<|输入唯一的主机名。允许使用字母、数字、空格、点、破折号和下划线。开头和结尾不允许空格。<br>*注意：* 配置正在运行的 Zabbix agent 主机时，agent [配置文件](/manual/appendix/config/zabbix_agentd) 的 *Hostname* 参数必须与此处输入的主机名相同。 [主动检查](/manual/appendix/items/activepassive) 需要依据该参数的值。| |*主机可见名*|<|输入主机的唯一标识名称。如果你设置了这个名称，主机在列表、拓扑图等场景中将显示为此名称而不是主机名字段值。此属性支持 UTF-8 。| |*模板*|<|将 [模板](/manual/config/templates) 链接到主机。所有实体（监控项、触发器、图表等）都将从模板继承。<br>要关联新模板，请开始在 *链接新模板* 字段中输入模板名称进行模糊匹配。此时系统将会跳出匹配的模板列表；向下滚动以便选择。或者，您可以单击字段旁边的 *选择* ，然后从弹出窗口的列表中选择模板。*链接新模板* 字段中选择的模板将在保存或更新主机配置表单时链接到主机。<br>取消关联模板，请使用 *链接的模板* 框中的两个选项之一：<br>*取消链接* - 取消链接模板，但保留其监控项、触发器和图表<br>*取消链接并清理* - 取消链接模板并删除其所有监控项、触发器和图表<br>列出的模板名可以点击跳转到模板配置表单。| |*主机组*|<|选择主机所属的主机组。一台主机必须至少属于一个主机组。通过添加一个不存在的组名，可以创建一个新组并将主机关联到主机组。| |*主机接口*|<|主机支持多种主机接口类型： *Agent*, *SNMP*, *JMX* 和 *IPMI*。<br>默认没有定义主机接口。要增加一个新接口，在 *主机接口* 区域点击 *添加* 并输入 *IP/DNS*, *Connect to* 和 *Port* 信息。<br>*注意：* 用在任何监控项的接口都不能被移除，并且 *移除* 链接是灰色的。<br>有关配置 SNMP 接口（v1、v2 和 v3）的更多详细信息，请参阅 [配置 SNMP 监控](/manual/config/items/itemtypes/snmp#configuring_snmp_monitoring) 。| |<|*IP地址*|主机的IP地址（可选）。| |^|*DNS名称*|主机的DNS名称（可选）。| |^|*连接到*|点击对应的按钮告诉 Zabbix server 采用哪种模式从 agent 端获取数据：<br>**IP** - 连接到主机的IP地址（推荐）<br>**DNS** - 连接到主机的DNS名称| |^|*端口*|TCP/UDP 端口。默认端口： Zabbix agent 是 10050， SNMP agent 是 161,  JMX 是 12345，IPMI 是 623。| |^|*默认*|选择单选按钮设置默认接口。| |*描述*|<|填写主机描述信息。| |*由 agent 代理程序监测*|<|主机可以被 Zabbix server 或者Zabbix proxy 监控：<br>**(no proxy)** - 主机被 Zabbix  server 监控<br>**Proxy name** - 主机被 Zabbix proxy “Proxy 名称” 监控| |*已启用*|<|选中此项激活主机，准备接受监控。如果没选中，表示主机未激活，不能被监控。|  **IPMI** 选项卡包含 IPMI 管理属性。  |参数|描述| |---------|-----------| |*认证算法*|选择认证算法。| |*权限级别*|选择权限级别。| |*用户名*|认证用户名。支持使用宏| |*密码*|认证用户密码。支持使用宏|  **Tags（标签）** 选项卡允许定义主机级别的 [标签](/manual/config/tagging)。该主机的所有问题都将使用此处输入的值进行标记。  ![](../../../../assets/en/manual/config/host_d.png)  标签中支持以下宏：用户宏、{INVENTORY.\*} 宏、{HOST.HOST}，{HOST.NAME}，{HOST.CONN}，{HOST.DNS}，{HOST.IP}，{HOST.PORT} 和 {HOST.ID} 。  **宏** 选项卡允许您将主机级别的 [用户宏](/manual/config/macros/user_macros) 定义为键值对。请注意，宏值可以保存为纯文本、加密文本或 Vault 机密。也支持添加描述。  ![](../../../../assets/en/manual/config/host_e.png)  如果选择 *继承以及主机宏* 选项，还可以在此处查看模板和全局级别的用户宏。所有为该主机定义的用户宏都显示为他们的来源以及对应的值。  ![](../../../../assets/en/manual/config/host_e2.png){width="600"}  为方便起见，页面提供了指向各个模板和全局宏配置的链接。还可以在主机级别编辑模板/全局宏，从而有效地在主机上创建宏的副本。  **主机资产记录** 选项卡允许你手动为主机输入 [资产](inventory) 信息。你还可以选择启用 *自动* 资产信息填充，或者禁用此主机的资产信息填充。  ![](../../../../assets/en/manual/config/host_f.png)  如果启用了资产记录（手动或自动），则选项卡上方会显示绿点标示。

en-us	#### Configuration  The **Item** tab contains general item attributes.  ![](../../../../assets/en/manual/config/items/item.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |--|--------| |*Name*|Item name.| |*Type*|Item type. See individual [item type](itemtypes) sections.| |*Key*|Item key (up to 2048 characters).<br>The supported [item keys](itemtypes) can be found in individual item type sections.<br>The key must be unique within a single host.<br>If key type is 'Zabbix agent', 'Zabbix agent (active)' or 'Simple check', the key value must be supported by Zabbix agent or Zabbix server.<br>See also: the correct [key format](/manual/config/items/item/key).| |*Type of information*|Type of data as stored in the database after performing conversions, if any.<br>**Numeric (unsigned)** - 64bit unsigned integer<br>**Numeric (float)** - 64bit floating point number<br>This type will allow precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of [PostgreSQL 11 and earlier versions](/manual/installation/known_issues#floating_point_values)).<br>Receiving values in scientific notation is also supported. E.g. 1.23E+7, 1e308, 1.1E-4.<br>**Character** - short text data<br>**Log** - long text data with optional log related properties (timestamp, source, severity, logeventid)<br>**Text** - long text data. See also [text data limits](#text-data-limits).<br>For item keys that return data only in one specific format, matching type of information is selected automatically.| |*Host interface*|Select the host interface. This field is available when editing an item on the host level.| |*Units*|If a unit symbol is set, Zabbix will add post processing to the received value and display it with the set unit postfix.<br>By default, if the raw value exceeds 1000, it is divided by 1000 and displayed accordingly. For example, if you set *bps* and receive a value of 881764, it will be displayed as 881.76 Kbps.<br>The [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) memory standard is used for processing **B** (byte), **Bps** (bytes per second) units, which are divided by 1024. Thus, if units are set to **B** or **Bps** Zabbix will display:<br>1 as 1B/1Bps<br>1024 as 1KB/1KBps<br>1536 as 1.5KB/1.5KBps<br>Special processing is used if the following time-related units are used:<br>**unixtime** - translated to "yyyy.mm.dd hh:mm:ss". To translate correctly, the received value must be a *Numeric (unsigned)* type of information.<br>**uptime** - translated to "hh:mm:ss" or "N days, hh:mm:ss"<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:56:04"<br>**s** - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"<br>Only 3 upper major units are shown, like "1m 15d 5h" or "2h 4m 46s". If there are no days to display, only two levels are displayed - "1m 5h" (no minutes, seconds or milliseconds are shown). Will be translated to "< 1 ms" if the value is less than 0.001.<br>*Note* that if a unit is prefixed with `!`, then no unit prefixes/processing is applied to item values. See [unit conversion](#unit_conversion).| |*Update interval*|Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>*Note*: The update interval can only be set to '0' if custom intervals exist with a non-zero value. If set to '0', and a custom interval (flexible or scheduled) exists with a non-zero value, the item will be polled during the custom interval duration.<br>*Note* that the first item poll after the item became active or after update interval change might occur earlier than the configured value.<br>An existing passive item can be polled for value immediately by pushing the *Execute now* [button](#form_buttons).| |*Custom intervals*|You can create custom rules for checking the item:<br>**Flexible** - create an exception to the *Update interval* (interval with different frequency)<br>**Scheduling** - create a custom polling schedule.<br>For detailed information see [Custom intervals](/manual/config/items/item/custom_intervals).<br>[Time suffixes](/manual/appendix/suffixes) are supported in the *Interval* field, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Scheduling is supported since Zabbix 3.0.0.<br>*Note*: Not available for Zabbix agent active items.| |*History storage period*|Select either:<br>**Do not keep history** - item history is not stored. Useful for master items if only dependent items need to keep history.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping detailed history in the database (1 hour to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 2h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green ![](../../../../assets/en/manual/config/info.png) info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (1d)*.<br>It is recommended to keep the recorded values for the smallest possible time to reduce the size of value history in the database. Instead of keeping a long history of values, you can keep longer data of trends.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Trend storage period*|Select either:<br>**Do not keep trends** - trends are not stored.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping aggregated (hourly min, max, avg, count) history in the database (1 day to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 24h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green ![](../../../../assets/en/manual/config/info.png) info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (7d)*.<br>*Note:* Keeping trends is not available for non-numeric data - character, log and text.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Value mapping*|Apply value mapping to this item. [Value mapping](/manual/config/items/mapping) does not change received values, it is for displaying data only.<br>It works with *Numeric(unsigned)*, *Numeric(float)* and *Character* items.<br>For example, "Windows service states".| |*Log time format*|Available for items of type **Log** only. Supported placeholders:<br>\* **y**: *Year (1970-2038)*<br>\* **M**: *Month (01-12)*<br>\* **d**: *Day (01-31)*<br>\* **h**: *Hour (00-23)*<br>\* **m**: *Minute (00-59)*<br>\* **s**: *Second (00-59)*<br>If left blank the timestamp will not be parsed.<br>For example, consider the following line from the Zabbix agent log file:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>It begins with six character positions for PID, followed by date, time, and the rest of the line.<br>Log time format for this line would be "pppppp:yyyyMMdd:hhmmss".<br>Note that "p" and ":" chars are just placeholders and can be anything but "yMdhms".| |*Populates host inventory field*|You can select a host inventory field that the value of item will populate. This will work if automatic [inventory](/manual/config/hosts/inventory) population is enabled for the host.<br>This field is not available if *Type of information* is set to 'Log'.| |*Description*|Enter an item description.| |*Enabled*|Mark the checkbox to enable the item so it will be processed.| |*Latest data*|Click on the link to view the latest data for the item.<br>This link is only available when editing an already existing item.|  ::: noteclassic Item type specific fields are described on [corresponding pages](itemtypes). :::   ::: noteclassic When editing an existing [template](/manual/config/templates) level item on a host level, a number of fields are read-only. You can use the link in the form header and go to the template level and edit them there, keeping in mind that the changes on a template level will change the item for all hosts that the template is linked to. :::  The **Tags** tab allows to define item-level [tags](/manual/config/tagging).  ![](../../../../assets/en/manual/config/items/item_b.png)
zh-cn	#### 配置  **监控项** 选项卡包含了常规监控项属性。  ![](../../../../assets/en/manual/config/items/item.png)  所有必填字段都用红色星号标记。  |参数|描述| |---------|-----------| |*名称*|监控项名称。| |*类型*|监控项类型。 参考单独 [监控项类型](itemtypes) 章节。| |*键值*|监控项键值 (最多2048个字符)。<br>支持的 [监控项键值](itemtypes) 能够在各个监控项类型中找到。<br>键值在单个主机中必须是唯一的。<br>如果键值类型是 'Zabbix agent', 'Zabbix agent (主动)' or '简单检查', 则这个键值必须被 Zabbix agent 或 Zabbix server支持。<br>也可以查看: 标准的 [键值格式](/manual/config/items/item/key).| |*信息类型*|执行转换后存储在数据库中的数据类型（如果有）<br>**Numeric (unsigned)** - 64位无符号整型<br>**Numeric (float)** - 64位浮点数<br>允许大约15位的精度，范围从-1.79E+308到1.79E+308 ([PostgreSQL 11 和更早的版本除外](/manual/installation/known_issues#floating_point_values))<br>也支持用科学计数法接收值。例如:1.23E+7，1e308，1.1E-4<br>**Character** - 短文本数据<br>**Log** - 具有可选日志相关属性(timestamp（时间戳），source（源），severity（严重性），logeventid（日志事件id）)的长文本数据<br>**Text** - 长文本数据。可参见 [文本数据限制](#text-data-limits)<br>针对仅返回一种指定格式数据的监控项，匹配的信息类型可以自动选择。| |*主机接口*|选择主机接口，此字段在编辑主机级别的监控项时可用| |*单位*|如果设置了单位，Zabbix在接收到数据后会进行处理，使其匹配设置的单位<br>默认情况下，如果原始值超过1000，则除以1000再显示。例如，如果将单位设置为_bps_并接收到值881764，它将显示为881.76 Kbps。<br> [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) 存储器标准,用于处理B(字节)，Bps(字节/秒)单位，它除以1024。因此，如果单位设置为B或Bps, Zabbix将显示:<br>1 为 1B/1Bps<br>1024 为 1KB/1KBps<br>1536 为 1.5KB/1.5KBps<br>如果使用以下与时间相关的单位，则使用特殊处理：<br>**unixtime** - 转换成 "yyyy.mm.dd hh:mm:ss". 想要正确转换，接收的值必须是 *Numeric (unsigned)* 类型的信息。<br>**uptime** - 转换成 "hh:mm:ss" 或 "N days, hh:mm:ss"<br>例如，如果你收到的值为881764（秒），则显示为“10天，04:56:04”<br>**s** - 转换成 "yyy mmm ddd hhh mmm sss ms"; 参数被视为秒数。<br>例如，如果您收到的值为881764（秒），则显示为“10d 4h 56m”<br>只显示3个主要单位，如“1m 15d 5h”或“2h 4m 46s”。 如果没有显示天数，则仅显示两个级别 - “1m 5h”（不显示分钟，秒或毫秒）。 如果该值小于0.001，将被转换成“<1 ms”。<br>*注意* 如果单位带有前缀“!”，单元前缀/处理不会应用到监控项的值。请参阅 [单位转换](#unit_conversion).| |*更新间隔*|每N秒获取一次这个监控项的新值。允许的最大更新间隔为86400秒（1天）<br>支持[时间后缀](/manual/appendix/suffixes) , 例如 30s, 1m, 2h, 1d.<br>支持[用户宏](/manual/config/macros/user_macros) 。<br>单个宏必须填充整个字段。不支持字段中的多个宏或文本混合的宏。<br>*注意*: 仅当自定义间隔存在非零值时，更新间隔才能设置为“ 0”。如果设置为“ 0”，并且存在自定义间隔（灵活的或计划的）且具有非零值，则将在自定义间隔持续时间内轮询该监控项。<br>*注意* 监控项成为活动后或更新间隔更改后的第一个监控项轮询可能发生在配置值之前。<br>可以通过点击 *立即执行* [按钮](#form_buttons)查询现有被动监控项的值。| |*自定义时间间隔*|你可以为检查监控项创建自定义的规则：<br>**灵活** - 为*更新间隔* (不同频率的间隔)创建一个特例<br>**调度** - 创建自定义轮询时间表。<br>详细信息请查看 [自定义时间间隔](/manual/config/items/item/custom_intervals)。<br>*间隔* 字段支持[时间后缀](/manual/appendix/suffixes) 例如，30s, 1m, 2h, 1d。<br>支持[用户宏](/manual/config/macros/user_macros) 。<br>单个宏必须填充整个字段。不支持字段中的多个宏或文本混合的宏。<br>从Zabix 3.0.0开始支持调度。<br>*注意*: 不适用于主动类型的Zabbix agent监控项。| |*历史数据存储周期*|以下可供选择：<br>**不存储历史数据** - 不存储监控项历史数据。如果只有依赖项需要保留历史记录，则对主监控项很有用。<br>此设置不能被全局管家 [设置](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**存储周期** - 指定将详细历史数据保留在数据库中的时长(1小时至25年)。 过期数据将被housekeeper管家删除。按秒存储。<br>支持[时间后缀](/manual/appendix/suffixes) 例如，2h, 1d. 支持[用户宏](/manual/config/macros/user_macros)<br>*存储周期* 的值可以被 *Administration（管理） → General（通用） → [管家](/manual/web_interface/frontend_sections/administration/general#housekeeper)*覆盖。<br>如果存在全局设置，则显示绿色告警信息 ![](../../../../assets/en/manual/config/info.png)。 当鼠标移到上面时会提示告警信息，例如：*被全局管家设置(1d)覆盖*。<br>建议保留最小可能天数的历史数据，以减轻数据库存储压力。可以保留更长的趋势数据来替代历史数据。<br>更多内容请参考 [历史与趋势](/manual/config/items/history_and_trends).| |*趋势存储时间*|以下可供选择：<br>**不存储趋势数据** - 将不会存储趋势数据。<br>此设置不能被全局管家 [设置](/manual/web_interface/frontend_sections/administration/general#housekeeper)覆盖。<br>**存储周期** - 指定在数据库中保存聚合（每小时，最大，平均，计数）历史数据的时长（1天至25年）。管家将删除较旧的数据。按秒存储。<br>支持[时间后缀](/manual/appendix/suffixes)例如2h，1d。支持[用户宏](/manual/config/macros/user_macros)。<br>*存储周期* 可以被 *Administration（管理） → General（通用） → [管家](/manual/web_interface/frontend_sections/administration/general#housekeeper)*中的设置覆盖。<br>如果存在全局设置，将显示一条绿色的警告消息 ![](../../../../assets/en/manual/config/info.png) ,当鼠标移到上面时会提示告警信息，例如：*被全局管家设置 (7d)*覆盖。<br>*注意:* 保持趋势不适用于非数字数据 - 字符、日志和文本。<br>更多信息请参考 [历史与趋势](/manual/config/items/history_and_trends).| |*值映射*|将值映射应用于此监控项。 [值映射](/manual/config/items/mapping) 不会改变收到的值，仅用于显示数据。<br>适用于 *数值型(无符号)*, *数值型(浮点型)* 和 *字符型* 监控项。<br>例如, "Windows service states".| |*日志时间格式*|仅适用于**日志** 类型的监控项。支持占位符:<br>\* **y**: *年 (1970-2038)*<br>\* **M**: *月 (01-12)*<br>\* **d**: *日 (01-31)*<br>\* **h**: *小时 (00-23)*<br>\* **m**: *分钟 (00-59)*<br>\* **s**: *秒 (00-59)*<br>如果留空，则不会解析时间戳。<br>例如，从Zabbix Agent日志文件中考虑以下几行:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>它以PID的六个字符位置开始，后跟日期，时间和行的其余部分。<br>该行的日志时间格式为"pppppp:yyyyMMdd:hhmmss".<br>注意， "p"和":" 字符只是占位符，只能是 "yMdhms".| |*填充主机资产记录字段*|你可以选择监控项的值填充的主机资产字段，如果你为主机启用了自动发现模式[资产管理](/manual/config/hosts/inventory) 。<br>该字段在*信息类型* 设置为'日志'时不可用。| |*描述*|输入监控项描述。| |*启用*|选中复选框以启用该监控项，以便对其进行处理。| |*最新数据*|点击链接查看监控项的最新数据。<br>链接仅在编辑一个已存在的监控项时可用。|  ::: noteclassic 监控项类型的特定字段在 [对应页面](itemtypes)会有描述。 :::  ::: noteclassic 当编辑主机级别上的现有[模板](/manual/config/templates) 级别的监控项时, 多个字段是只读的。你可以使用表单标题中的链接并转到模板级别并在其中进行编辑，但请记住，模板级别上的更改将更改模板链接到的所有主机的监控项。 :::  **标签** 选项卡允许定义监控项级别的 [标签](/manual/config/tagging)。  ![](../../../../assets/en/manual/config/items/item_b.png)

en-us	#### Configuration  The **Item** tab contains general item attributes.  ![](../../../../assets/en/manual/config/items/item.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Name*|Item name.| |*Type*|Item type. See individual [item type](itemtypes) sections.| |*Key*|Item key (up to 2048 characters).<br>The supported [item keys](itemtypes) can be found in individual item type sections.<br>The key must be unique within a single host.<br>If key type is 'Zabbix agent', 'Zabbix agent (active)' or 'Simple check', the key value must be supported by Zabbix agent or Zabbix server.<br>See also: the correct [key format](/manual/config/items/item/key).| |*Type of information*|Type of data as stored in the database after performing conversions, if any.<br>**Numeric (unsigned)** - 64bit unsigned integer<br>**Numeric (float)** - 64bit floating point number<br>This type will allow precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of [PostgreSQL 11 and earlier versions](/manual/installation/known_issues#floating_point_values)).<br>Receiving values in scientific notation is also supported. E.g. 1.23E+7, 1e308, 1.1E-4.<br>**Character** - short text data<br>**Log** - long text data with optional log related properties (timestamp, source, severity, logeventid)<br>**Text** - long text data. See also [text data limits](#text-data-limits).<br>For item keys that return data only in one specific format, matching type of information is selected automatically.| |*Host interface*|Select the host interface. This field is available when editing an item on the host level.| |*Units*|If a unit symbol is set, Zabbix will add post processing to the received value and display it with the set unit postfix.<br>By default, if the raw value exceeds 1000, it is divided by 1000 and displayed accordingly. For example, if you set *bps* and receive a value of 881764, it will be displayed as 881.76 Kbps.<br>The [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) memory standard is used for processing **B** (byte), **Bps** (bytes per second) units, which are divided by 1024. Thus, if units are set to **B** or **Bps** Zabbix will display:<br>1 as 1B/1Bps<br>1024 as 1KB/1KBps<br>1536 as 1.5KB/1.5KBps<br>Special processing is used if the following time-related units are used:<br>**unixtime** - translated to "yyyy.mm.dd hh:mm:ss". To translate correctly, the received value must be a *Numeric (unsigned)* type of information.<br>**uptime** - translated to "hh:mm:ss" or "N days, hh:mm:ss"<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:56:04"<br>**s** - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.<br>For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"<br>Only 3 upper major units are shown, like "1m 15d 5h" or "2h 4m 46s". If there are no days to display, only two levels are displayed - "1m 5h" (no minutes, seconds or milliseconds are shown). Will be translated to "< 1 ms" if the value is less than 0.001.<br>*Note* that if a unit is prefixed with `!`, then no unit prefixes/processing is applied to item values. See [unit conversion](#unit_conversion).| |*Update interval*|Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>*Note*: The update interval can only be set to '0' if custom intervals exist with a non-zero value. If set to '0', and a custom interval (flexible or scheduled) exists with a non-zero value, the item will be polled during the custom interval duration.<br>*Note* that the first item poll after the item became active or after update interval change might occur earlier than the configured value.<br>An existing passive item can be polled for value immediately by pushing the *Execute now* [button](#form_buttons).| |*Custom intervals*|You can create custom rules for checking the item:<br>**Flexible** - create an exception to the *Update interval* (interval with different frequency)<br>**Scheduling** - create a custom polling schedule.<br>For detailed information see [Custom intervals](/manual/config/items/item/custom_intervals).<br>[Time suffixes](/manual/appendix/suffixes) are supported in the *Interval* field, e.g. 30s, 1m, 2h, 1d.<br>[User macros](/manual/config/macros/user_macros) are supported.<br>A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Scheduling is supported since Zabbix 3.0.0.<br>*Note*: Not available for Zabbix agent active items.| |*History storage period*|Select either:<br>**Do not keep history** - item history is not stored. Useful for master items if only dependent items need to keep history.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping detailed history in the database (1 hour to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 2h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green ![](../../../../assets/en/manual/config/info.png) info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (1d)*.<br>It is recommended to keep the recorded values for the smallest possible time to reduce the size of value history in the database. Instead of keeping a long history of values, you can keep longer data of trends.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Trend storage period*|Select either:<br>**Do not keep trends** - trends are not stored.<br>This setting cannot be overridden by global housekeeper [settings](/manual/web_interface/frontend_sections/administration/general#housekeeper).<br>**Storage period** - specify the duration of keeping aggregated (hourly min, max, avg, count) history in the database (1 day to 25 years). Older data will be removed by the housekeeper. Stored in seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 24h, 1d. [User macros](/manual/config/macros/user_macros) are supported.<br>The *Storage period* value can be overridden globally in *Administration → General → [Housekeeper](/manual/web_interface/frontend_sections/administration/general#housekeeper)*.<br>If a global overriding setting exists, a green ![](../../../../assets/en/manual/config/info.png) info icon is displayed. If you position your mouse on it, a warning message is displayed, e.g. *Overridden by global housekeeper settings (7d)*.<br>*Note:* Keeping trends is not available for non-numeric data - character, log and text.<br>See also [History and trends](/manual/config/items/history_and_trends).| |*Value mapping*|Apply value mapping to this item. [Value mapping](/manual/config/items/mapping) does not change received values, it is for displaying data only.<br>It works with *Numeric(unsigned)*, *Numeric(float)* and *Character* items.<br>For example, "Windows service states".| |*Log time format*|Available for items of type **Log** only. Supported placeholders:<br>\* **y**: *Year (1970-2038)*<br>\* **M**: *Month (01-12)*<br>\* **d**: *Day (01-31)*<br>\* **h**: *Hour (00-23)*<br>\* **m**: *Minute (00-59)*<br>\* **s**: *Second (00-59)*<br>If left blank the timestamp will not be parsed.<br>For example, consider the following line from the Zabbix agent log file:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>It begins with six character positions for PID, followed by date, time, and the rest of the line.<br>Log time format for this line would be "pppppp:yyyyMMdd:hhmmss".<br>Note that "p" and ":" chars are just placeholders and can be anything but "yMdhms".| |*Populates host inventory field*|You can select a host inventory field that the value of item will populate. This will work if automatic [inventory](/manual/config/hosts/inventory) population is enabled for the host.<br>This field is not available if *Type of information* is set to 'Log'.| |*Description*|Enter an item description.| |*Enabled*|Mark the checkbox to enable the item so it will be processed.|  ::: noteclassic Item type specific fields are described on [corresponding pages](itemtypes). :::   ::: noteclassic When editing an existing [template](/manual/config/templates) level item on a host level, a number of fields are read-only. You can use the link in the form header and go to the template level and edit them there, keeping in mind that the changes on a template level will change the item for all hosts that the template is linked to. :::  The **Tags** tab allows to define item-level [tags](/manual/config/tagging).  ![](../../../../assets/en/manual/config/items/item_b.png)  
zh-cn	#### 配置  **监控项** 选项卡包含了常规监控项属性：  ![](../../../../assets/zh/manual/config/items/item_zh.png){width="600"}  所有必填输入字段都标有红色星号。  | 参数  | 描述  | |---|---| |*名称*                   |监控项名称。<br>可以使用以下宏：<br>**$1, $2...$9** - 指的是监控项的第1、2...9个参数<br>例如：$1上的可用磁盘空间<br>如果监控项的key是 "vfs.fs.size\[/,free\]", 说明将自动更改为 "Free disk space on /"| |*类型*                   |监控项类型。参考单个 [监控项类型](itemtypes) 章节.| |*键值*                   |监控项键值.<br>可支持的[监控项键值](itemtypes) 能够在各个监控项类型中找到。<br>这个键值在单个主机中必须是唯一的。<br>如果键值的类型是'Zabbix 客户端'、'Zabbix客户端(主动式)', '简单检查' 或者 'Zabbix整合', 则此key必须被 Zabbix 客户端 或者 Zabbix 服务端 支持。<br>也可以查看: 正确的 [键值的格式](/zh/manual/config/items/item/key).| |*信息类型*               |转换后存储在数据库中的数据类型（如果有）。<br>**数字(无正负)** - 64位无符号整数<br>**数字(浮点)** - 64位浮点数<br>允许大约15位的精度，范围从-1.79E+308到1.79E+308(with exception of [PostgreSQL 11和更早版本](/manual/installation/known_issues#floating_point_values)除外)<br>也支持科学计数值。例如:1.23E+7, 1e308, 1.1E-4。<br>**字符** - 短文本数据<br>**日志** - 具有可选日志相关属性的长文本数据(timestamp（时间戳）, source（源）, severity（严重性）, logeventid（日志事件id）)<br>**文本** - 长文本数据。可参见 [文本数据限制](#Text_data_limits)。<br>针对返回的数据是指定格式的监控项键值，匹配的信息类型会自动选择。| |*主机接口*               |主机接口。编辑主机级别的监控项时，此字段可用。| |*单位*                   |如果设置了单位符号，Zabbix将在收到数据后再加工处理，并使用设置单位后缀进行显示。<br>默认情况下，如果原始值超过1000，则除以1000，并相应显示。 例如，如果设置 *bps* 并接收到值为881764，则将显示为881.76 Kbps。<br> [JEDEC](https://en.wikipedia.org/wiki/JEDEC_memory_standards) 存储器标准用于处理B（字节），Bps（每秒字节数）单位，除以1024。因此，如果单位设置为B或Bps，Zabbix将显示：<br>1 为 1B/1Bps<br>1024 为 1KB/1KBps<br>1536 为 1.5KB/1.5KBps<br>如果使用以下与时间相关的单位，则使用特殊处理：<br>**unixtime** - 转换成“yyyy.mm.dd hh：mm：ss”。 要正确转换，接收的值必须是数字（无符号）类型的信息。<br>**uptime** - 转换为 "hh:mm:ss" 或者 "N days, hh:mm:ss"<br>例如，如果你收到的值为881764（秒），则显示为“10天，04:56:04”<br>**s** - 转换成“yyy mmm ddd hhh mmm sss ms”; 参数被视为秒数。<br>例如，如果您收到的值为881764（秒），则显示为“10d 4h 56m”<br>只显示3个主要单位，如“1m 15d 5h”或“2h 4m 46s”。 如果没有显示天数，则仅显示两个级别 - “1m 5h”（不显示分钟，秒或毫秒）。 如果该值小于0.001，将被转换成“<1 ms”。<br>注意，如果单位带有前缀“!”，单元前缀/处理不会应用到监控项的值，请参阅 [单位黑名单](#unit_blacklist).| |*更新间隔*               |每N秒检索一次这个项目的新值。允许的最大更新间隔为86400秒（1天）。<br>支持[时间后缀](/zh/manual/appendix/suffixes)，例如 30s，1m，2h，1d。<br>支持[用户宏](/zh/manual/config/macros/usermacros)。<br>单个宏必须填充整个字段。不支持字段中的多个宏或文本混合的宏。<br>*注意*：仅当自定义间隔存在非零值时，更新间隔才能设置为“ 0”。如果设置为“ 0”，并且存在自定义间隔（灵活的或计划的）且具有非零值，则将在自定义间隔持续时间内轮询该项目。<br>*注意* 项目成为活动后或更新间隔更改后的第一个项目轮询可能发生在配置值之前。<br>可以通过按*立即检查*[按钮](#form_buttons)立即轮询现有被动监控项的值。| |*自定义时间间隔*         |你可以创建用于检查监控项的自定义规则：<br>**Flexible**（灵活） - 为 *更新间隔* (不同频率的间隔)创建一个特例。<br>**Scheduling**（调度）- 创建自定义轮询时间表。<br>详细信息请查看 [自定义间隔](/zh/manual/config/items/item/custom_intervals)。<br>*间隔* 字段支持[时间后缀](/zh/manual/appendix/suffixes) , 例如 30s, 1m, 2h, 1d.<br>支持[用户宏](/zh/manual/config/macros/usermacros)。<br>从Zabix 3.0.0开始支持时间表。<br>*注意*: 不适用于Zabbix Agent的活动监控项。| |*历史数据保留时长*|以下可供选择：<br>**不存储历史数据** - 不存储监控项历史数据。如果只有依赖项需要保留历史记录，则对主监控项很有用。<br>此设置不能被全局管家 [设置](/zh/manual/web_interface/frontend_sections/administration/general#housekeeper)覆盖。<br>**存储时长** - 指定将详细历史数据保留在数据库中的时长(1小时至25年)。 过期数据将被housekeeper管家删除。按秒存储。<br>支持[时间后缀](/zh/manual/appendix/suffixes)，例如2h，1d。支持[用户宏](/zh/manual/config/macros/user_macros)<br> *存储时长* 可以被 *Administration（管理） → General（通用） → [管家](/zh/manual/web_interface/frontend_sections/administration/general#housekeeper)*中的值覆盖。<br>如果存在全局设置，则显示绿色告警信息，![](../../../../assets/en/manual/config/info.png)。当鼠标移到上面时会提示告警信息，例如*被全局管家设置(1d)覆盖*.<br>建议保留最小可能天数的历史数据，以减轻数据库存储压力。可以保留更长的趋势数据来替代历史数据。<br>更多内容请参考[历史与趋势](/zh/manual/config/items/history_and_trends)。| |*趋势存储时间*|以下可供选择：<br>**不存储趋势数据** - 将不会存储趋势数据。<br>此设置不能被全局管家[设置](/manual/web_interface/frontend_sections/administration/general#housekeeper)覆盖。<br>**存储时长** - 指定在数据库中保存聚合（每小时，最大，平均，计数）历史数据的时长（1天至25年）。管家将删除较旧的数据。按秒存储。<br>支持[时间后缀](/zh/manual/appendix/suffixes)，例如2h，1d。支持[用户宏](/zh/manual/config/macros/user_macros)<br>*存储时长*可以在*Administration（管理） → General（通用） → [管家](/zh/manual/web_interface/frontend_sections/administration/general#housekeeper)*中的值覆盖。<br>如果存在全局设置，将显示一条绿色的警告消息![](../../../../assets/en/manual/config/info.png)。当鼠标移到上面时会提示告警信息，例如：*被全局管家设置(7d)覆盖*.<br>*注意:* 保持趋势不适用于非数字数据 - 字符、日志和文本。<br>更多信息请参考 [历史与趋势](/zh/manual/config/items/history_and_trends).| |*值映射*|将值映射应用于此监控项。[值映射](/zh/manual/config/items/mapping) 不会改变收到的值，仅用于显示数据。<br>适用于 *数值型(无符号)*, *数值型(浮点型)* 和 *字符型* 监控项。<br>例如："Windows service states".| |*日志时间格式*           仅适用于*|日志**类型的监控项。 支持的占位符:<br>\* **y**: *年 (1970-2038)*<br>\* **M**: *月 (01-12)*<br>\* **d**: *日 (01-31)*<br>\* **h**: *小时 (00-23)*<br>\* **m**: *分钟 (00-59)*<br>\* **s**: *秒 (00-59)*<br>如果留空，则不会解析时间戳。<br>例如，从Zabbix Agent日志文件中考虑以下几行：“23480：20100328：154718.045 Zabbix代理启动。 Zabbix 1.8.2（修订11211）。“<br>它以PID的六个字符位置开始，后跟日期，时间和行的其余部分。<br>该行的日志时间格式为“pppppp：yyyyMMdd：hhmmss”。<br>注意，“p”和“:”字符只是占位符，只能是“yMdhms”。| |*主机资产纪录字段*   |你可以选择项目的值填充的主机资产字段，如果你为主机启用了自动发现模式 [资产管理](/zh/manual/config/hosts/inventory)。<br>该字段在*信息类型*字段设置为'日志'时不可用。| |*描述*                   |输入监控项描述。| |*已启用*                 |选中复选框以启用该监控项，以便对其进行处理。|  ::: noteclassic 监控项类型的特定字段在[对应页面](监控项类型)会有描述。 :::  :::  noteclassic 当编辑主机级别上的现有[模板](/zh/manual/config/templates)级别的监控项时，多个字段是只读的。你可以使用表单标题中的链接并转到模板级别并在其中进行编辑，但请记住，模板级别上的更改将更改模板链接到的所有主机的项目。 :::  **标签** 允许定义监控项级别的[标签](/zh/manual/config/tagging).  ![](../../../../assets/en/manual/config/items/item_b.png)  

en-us	#### Configuration  The low-level discovery rule should be created as a [dependent item](/manual/config/items/itemtypes/dependent_items) to the HTTP master item that collects Prometheus data.
zh-cn	#### 配置  利用低级别自动发现规则创建一个 [依赖型监控项](/manual/config/items/itemtypes/dependent_items) ，附属于采集Prometheus数据的HTTP主监控项。

en-us	#### Configuration  The options for aggregation are available in data set settings when configuring a [graph widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph).  ![](../../../../../assets/en/manual/config/visualization/aggregate_graph_options.png)  You may pick the aggregation function and the time interval. As the data set may comprise several items, there is also another option allowing to show aggregated data for each item separately or for all data set items as one aggregated value.
zh-cn	#### 配置  在配置图形小部件时，可以在数据集设置中使用聚合选项。 [图形部件]（/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph）。  ![](../../../../../assets/en/manual/config/visualization/aggregate_graph_options.png)  您可以选择聚合函数和时间间隔。作为数据集可能包含多个监控项，还有另一个选项允许分别显示每个监控项或将所有数据集监控项的聚合数据作为一个聚合值显示。

en-us	#### Configuration  The **Trigger** tab contains all the essential trigger attributes.  ![](../../../../assets/en/manual/config/triggers/trigger.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Name*|Trigger name.<br>Supported [macros](/manual/appendix/macros/supported_by_location) are: {HOST.HOST}, {HOST.NAME}, {HOST.PORT}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {ITEM.VALUE}, {ITEM.LASTVALUE}, {ITEM.LOG.\*} and {$MACRO} user macros.<br>**$1, $2...$9** macros can be used to refer to the first, second...ninth constant of the expression.<br>*Note*: $1-$9 macros will resolve correctly if referring to constants in relatively simple, straightforward expressions. For example, the name "Processor load above $1 on {HOST.NAME}" will automatically change to "Processor load above 5 on New host" if the expression is last(/New host/system.cpu.load\[percpu,avg1\])>5| |*Event name*|If defined, this name will be used to create the problem event name, instead of the trigger name.<br>The event name may be used to build meaningful alerts containing problem data (see [example](/manual/config/triggers/expression#example_17)).<br>The same set of macros is supported as in the trigger name, plus {TIME} and {?EXPRESSION} expression macros.<br>Supported since Zabbix 5.2.0.| |*Operational data*|Operational data allow to define arbitrary strings along with macros. The macros will resolve dynamically to real time data in *Monitoring* → *[Problems](/manual/web_interface/frontend_sections/monitoring/problems)*. While macros in the trigger name (see above) will resolve to their values at the moment of a problem happening and will become the basis of a static problem name, the macros in the operational data maintain the ability to display the very latest information dynamically.<br>The same set of macros is supported as in the trigger name.| |*Severity*|Set the required trigger [severity](severity) by clicking the buttons.| |*Expression*|Logical [expression](expression) used to define the conditions of a problem.<br>A problem is created after all the conditions included in the expression are met, i.e. the expression evaluates to TRUE. The problem will be resolved as soon as the expression evaluates to FALSE, unless additional recovery conditions are specified in *Recovery expression*.| |*OK event generation*|OK event generation options:<br>**Expression** - OK events are generated based on the same expression as problem events;<br>**Recovery expression** - OK events are generated if the problem expression evaluates to FALSE and the recovery expression evaluates to TRUE;<br>**None** - in this case the trigger will never return to an OK state on its own.| |*Recovery expression*|Logical [expression](expression) (optional) defining additional conditions that have to be met before the problem is resolved, after the original problem expression has already been evaluated as FALSE.<br>Recovery expression is useful for trigger [hysteresis](/manual/config/triggers/expression#hysteresis). It is **not** possible to resolve a problem by recovery expression alone if the problem expression is still TRUE.<br>This field is only available if 'Recovery expression' is selected for *OK event generation*.| |*PROBLEM event generation mode*|Mode for generating problem events:<br>**Single** - a single event is generated when a trigger goes into the 'Problem' state for the first time;<br>**Multiple** - an event is generated upon *every* 'Problem' evaluation of the trigger.| |*OK event closes*|Select if OK event closes:<br>**All problems** - all problems of this trigger<br>**All problems if tag values match** - only those trigger problems with matching event tag values| |*Tag for matching*|Enter event tag name to use for event correlation.<br>This field is displayed if 'All problems if tag values match' is selected for the *OK event closes* property and is mandatory in this case.| |*Allow manual close*|Check to allow [manual closing](/manual/config/events/manual_close) of problem events generated by this trigger. Manual closing is possible when acknowledging problem events.| |*URL*|If not empty, the URL entered here is available as a link in several frontend locations, e.g. when clicking on the problem name in *Monitoring → Problems* (*URL* option in the *Trigger* menu) and *Problems* dashboard widget.<br>The same set of macros is supported as in the trigger name, plus {EVENT.ID}, {HOST.ID} and {TRIGGER.ID}. Note that user macros with secret values will not be resolved in the URL.| |*Description*|Text field used to provide more information about this trigger. May contain instructions for fixing specific problem, contact detail of responsible staff, etc.<br>The same set of macros is supported as in the trigger name.| |*Enabled*|Unchecking this box will disable the trigger if required.<br>Problems of a disabled trigger are no longer displayed in the frontend, but are not deleted.|  The **Tags** tab allows you to define trigger-level [tags](/manual/config/tagging). All problems of this trigger will be tagged with the values entered here.  ![](../../../../assets/en/manual/config/triggers/trigger_b.png)  In addition the *Inherited and trigger tags* option allows to view tags defined on template level, if the trigger comes from that template. If there are multiple templates with the same tag, these tags are displayed once and template names are separated with commas. A trigger does not "inherit" and display host-level tags.  |Parameter|Description| |---------|-----------| |*Name/Value*|Set custom tags to mark trigger events.<br>Tags are a pair of tag name and value. You can use only the name or pair it with a value. A trigger may have several tags with the same name, but different values.<br>User macros, user macro context, low-level discovery macros and macro [functions](/manual/config/macros/macro_functions) with `{{ITEM.VALUE}}`, `{{ITEM.LASTVALUE}}` and low-level discovery macros are supported in event tags. Low-level discovery macros can be used inside macro context.<br>{TRIGGER.ID} macro is supported in trigger tag values. It may be useful for identifying triggers created from trigger prototypes and, for example, suppressing problems from these triggers during maintenance.<br>If the total length of expanded value exceeds 255, it will be cut to 255 characters.<br>See all [macros](/manual/config/tagging#macro_support) supported for event tags.<br>[Event tags](/manual/config/tagging) can be used for event correlation, in action conditions and will also be seen in *Monitoring* → *Problems* or the *Problems* widget.|  The **Dependencies** tab contains all the [dependencies](dependencies) of the trigger.  Click on *Add* to add a new dependency.  ::: noteclassic You can also configure a trigger by opening an existing one, pressing the *Clone* button and then saving under a different name. :::
zh-cn	#### 配置  **Trigger(触发器)**标签页包含了所有必要的触发器属性。  ![](../../../../assets/en/manual/config/triggers/trigger.png)  所有强制输入字段都用红色星号标记。  |参数                 |描述| |--------------------------|-| |*名称*               |触发器名称.<br>支持的 [macros（宏）](/manual/appendix/macros/supported_by_location): {HOST.HOST}, {HOST.NAME}, {HOST.PORT}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {ITEM.VALUE}, {ITEM.LASTVALUE}, {ITEM.LOG.\*} and {$MACRO}。<br>**$1, $2...$9** 宏可以用来指第一,第二...第九表达式的常量。<br>*备注*: 如果引用了相对简单的常量或明确的表达式，$1-$9宏将会正确解析。例如, 如果表达式是{New host:system.cpu.load\[percpu,avg1\].last()}>5，则"Processor load above $1 on {HOST.NAME}"将会自动更改成 "Processor load above 5 on New host"| |*事件名称*|如果定义了这个名称，将使用这个名称来创建问题事件名称，而不是触发器名称。<br>事件名称可用于构建包含问题数据的有意义的警报 (查看[示例](/manual/config/triggers/expression#example_17))。<br>支持与触发器名称相同的一组宏，加上{TIME}和{?EXPRESSION}表达式宏。<br>从Zabbix 5.2.0开始支持。| |*操作数据*|操作数据允许定义任意字符串和宏。这些宏会在*Monitoring（监控）* → *[Problems（问题）](/manual/web_interface/frontend_sections/monitoring/problems)*.中动态地解析实时数据。触发器名称中的宏将在问题发生时解析为它们的值，并成为静态问题名称的基础，而操作数据中的宏则保持动态显示最新信息的能力。<br>支持与触发器名称相同的一组宏。| |*严重性*|通过点击对应的按钮来设置所需的触发器[severity](严重性)。| |*表达式*         |定义问题条件的逻辑[表达式](expression)。当表达式中包含的所有条件都满足时，就会产生问题，即表达式的计算结果为TRUE。除非在恢复表达式中指定了额外的恢复条件，否则该问题将在表达式计算结果为FALSE时得到解决。| |*生成OK事件*      | OK 事件生成选项：<br>**Expression（表达式）** - OK事件基于与问题事件相同的表达式生成;<br>**Recovery expression（恢复表达式）** - 如果问题表达式计算为false，恢复表达式计算为true，则生成OK事件;<br>**None** - 在这种情况下，触发器将永远不会返回到OK状态。<br>从Zabbix 3.2.0开始支持| |*恢复表达式*         |逻辑[expression](表达式)]用于定义问题解决的条件。<br>只有在表达式表达式计算为FALSE之后才对恢复表达式进行评估。<br>恢复表达式有利于配置触发器[滞后](/manual/config/triggers/expression#hysteresis)。如果问题条件仍然存在，则不可能通过恢复表达式来解决问题。<br>此字段是可选的，仅在*OK 事件生成*选择恢复表达式。<br>从Zabbix 3.2.0开始支持| |*问题事件生成模式*   |生成问题事件的模式：<br>**Single（单个）** - 当触发器第一次进入‘Problem‘状态时，生成一条单个事件。<br>**Multiple（多重）** - 每一个触发器“Problem”评估都将生产一条事件。| |*事件成功关闭*       |选择 OK 事件是否关闭：<br>**All problems（所有问题）** - 此触发器的所有问题<br>**All problems if tag values match（所有问题如果标签值匹配）** - 只有那些匹配事件标签值引发的问题。<br>从Zabbix 3.2.0开始支持。| |*匹配标记*           |输入事件标签名称以用于事件关联。<br>如果在*事件成功关闭*中选择了‘所有问题如果标签值匹配’，在这种情况下是强制性的。<br>从Zabbix 3.2.0开始支持。| |*允许手动关闭*      | 检查是否允许[手动关闭](/manual/config/events/manual_close)由该触发器生成的问题事件。在确认问题事件时，手动关闭是可能的。<br>从Zabbix 3.2.0开始支持。| |*URL*|如果不为空, 在*监测 → 问题*和*问题*仪表板中点击触发器名称，这里输入的URL可以作为链接。(*URL*选项在*触发器*上下文菜单)<br>可以在触发器URL字段中使用宏，例如 {EVENT.ID}, {HOST.ID} 和 {TRIGGER.ID}。注意密文类型的宏值不能正常解析。| |*描述*               |文本字段用于提供有关此触发器的更多信息。可能包含解决具体问题的指令、负责人员的联系细节等。<br>*从Zabbix 2.2开始*, 描述可以包含与触发器名称相同的宏集。| |*已启用*            |不选中该框将禁用触发器。问题事件对应的触发器被禁用，则前端不显示该事件但不会删除。|   **Tags（标签）** 选项卡允许您定义触发级 [tags](/manual/config/tagging)。此触发器的所有问题都将使用此处输入的值进行标记。  ![](../../../../assets/en/manual/config/triggers/trigger_b.png)  此外，*Inherited and trigger tags（继承和触发器标记）* 选项允许查看在模板级定义的标记，如果触发器来自该模板。如果有多个模板使用相同的标记，这些标记只显示一次，并且用逗号分隔模板名。触发器不“继承”和显示主机级标记。  |Parameter|Description| |---------|-----------| |*Name（名称）/Value（值）*|设置自定义标记来标记触发事件。<br>标签是一对标签名和值。只能使用名称或将其与值配对。一个触发器可能有几个名称相同但值不同的标记。<br>用户宏，用户宏上下文，低级别发现宏和宏[functions(函数)](/manual/config/宏/macro_functions)带有' {{ITEM.VALUE}},{{ITEM.LASTVALUE}}和低级别发现宏。低级别发现宏可以在宏上下文中使用。<br>{TRIGGER.ID}宏。它可能有助于识别从触发器原型创建的触发器，例如，在维护期间抑制这些触发器产生的问题。当扩展值的总长度超过255时，将被截断为255个字符。<br>查看所有支持事件标签的[macros（宏）](/manual/config/tagging#macro_support)。<br>[Event tags（事件标签）](/manual/config/tagging)可以用于事件关联，在动作条件中，也可以在*Monitoring*→*Problems*或*Problems* widget中看到|   **Dependencies（依赖项）** 选项卡包含触发器的所有 [dependencies](dependencies)。  单击 *Add* 添加新的依赖项。  ::: noteclassic¶  您还可以通过打开现有触发器来配置触发器，  按下 *Clone* 按钮，然后保存在不同的位置名称。 :::

en-us	### Configuration  The Zabbix API allows you to manage the configuration of your monitoring system.
zh-cn	### 配置  Zabbix API 允许您管理监控系统的配置。

en-us	# Configuration  This class is designed to export and import Zabbix configuration data.  Available methods:\  -   [configuration.export](/manual/api/reference/configuration/export) -     exporting the configuration -   [configuration.import](/manual/api/reference/configuration/import) -     importing the configuration
zh-cn	# 配置  此类用于导入和导出 Zabbix 的配置数据。  可用方法\  -   [configuration.export](/manual/api/reference/configuration/export) - 导出配置 -   [configuration.import](/manual/api/reference/configuration/import) - 导入配置

en-us	#### Configuration  Those remote commands that are executed on Zabbix agent (custom scripts) must be first enabled in the agent [configuration](/manual/appendix/config/zabbix_agentd).  Make sure that the AllowKey=system.run[<command>,\*] parameter is added for each allowed command in agent configuration to allow specific command with nowait mode. Restart agent daemon if changing this parameter.  ::: noteimportant Remote commands do not work with active Zabbix agents. :::  Then, when configuring a new action in *Configuration → Actions*:  -   Define the appropriate conditions. In this example, set that the     action is activated upon any disaster problems with one of Apache     applications:  ![](../../../../../../assets/en/manual/config/notifications/action/conditions_restart.png)  -   In the     *[Operations](/manual/config/notifications/action/operation#configuring_an_operation)*     tab, click on Add in the Operations/Recovery operations/Update     operations block -   From the Operation dropdown field select one of the predefined     scripts  ![](../../../../../../assets/en/manual/config/notifications/action/operation_restart_webserver.png)  -   Select the target list for the script
zh-cn	#### 配置  在 Zabbix agent上执行远程命令（自定义脚本）必须先在agent[配置](/manual/appendix/config/zabbix_agentd)中启用。  必须确保添加了`AllowKey=system.run[*]`参数，并重启 agent后台驻留程序。  ::: noteimportant  Zabbix active agent上远程命令不不生效。  :::  然后，在*Configuration → Actions*配置新动作时：  -   定义适当的条件。在本例中，设置动作由Apache的任何灾难问题激活：  ![](../../../../../../assets/en/manual/config/notifications/action/conditions_restart.png)  -   在 *[Operations](/manual/config/notifications/action/operation#configuring_an_operation)*选项卡，在Operations/Recovery/Update的操作块里点击 -   从Operation下拉菜单选择一个预定义的脚本   ![](../../../../../../assets/en/manual/config/notifications/action/operation_restart_webserver.png)  -   为脚本选择目标列表

en-us	#### Configuration  Those remote commands that are executed on Zabbix agent (custom scripts) must be first enabled in the agent [configuration](/manual/appendix/config/zabbix_agentd).  Make sure that the `AllowKey=system.run[*]` parameter is added. Restart agent daemon if changing this parameter.  ::: noteimportant Remote commands do not work with active Zabbix agents. :::  Then, when configuring a new action in *Configuration → Actions*:  -   Define the appropriate conditions. In this example, set that the     action is activated upon any disaster problems with one of Apache     applications:  ![](../../../../../../assets/en/manual/config/notifications/action/conditions_restart.png)  -   In the     *[Operations](/manual/config/notifications/action/operation#configuring_an_operation)*     tab, click on Add in the Operations/Recovery operations/Update     operations block -   From the Operation dropdown field select one of the predefined     scripts  ![](../../../../../../assets/en/manual/config/notifications/action/operation_restart_webserver.png)  -   Select the target list for the script
zh-cn	#### 配置  在 Zabbix agent上执行远程命令（自定义脚本）必须先在agent[配置](/manual/appendix/config/zabbix_agentd)中启用。  必须确保添加了`AllowKey=system.run[*]`参数，并重启 agent后台驻留程序。  ::: noteimportant  Zabbix active agent上远程命令不不生效。  :::  然后，在*Configuration → Actions*配置新动作时：  -   定义适当的条件。在本例中，设置动作由Apache的任何灾难问题激活：  ![](../../../../../../assets/en/manual/config/notifications/action/conditions_restart.png)  -   在 *[Operations](/manual/config/notifications/action/operation#configuring_an_operation)*选项卡，在Operations/Recovery/Update的操作块里点击 -   从Operation下拉菜单选择一个预定义的脚本   ![](../../../../../../assets/en/manual/config/notifications/action/operation_restart_webserver.png)  -   为脚本选择目标列表

en-us	#### Configuration  To add the widget, select *Geomap* as type.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget.png)
zh-cn	#### 配置  要添加组件，请选择*Geomap* 作为类型。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget.png)

en-us	#### Configuration  To add the widget, select *Geomap* as type.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget.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 to be displayed on the map. 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 to be displayed all the map. 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 hosts 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| |*Initial view*|Comma separated center coordinates and an optional zoom level to display when the widget is initially loaded in the format `<latitude>,<longitude>,<zoom>`<br>If initial zoom is specified, the Geomap widget is loaded at the given zoom level. Otherwise, initial zoom is calculated as half of the [max zoom](/manual/web_interface/frontend_sections/administration/general#geographical_maps) for the particular tile provider.<br>The initial view is ignored if the default view is set (see below).<br>Examples:<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891|  Host markers displayed on the map have the color of the host's most serious problem and green color if a host has no problems. Clicking on the host marker allows viewing the host's visible name and the number of unresolved problems grouped by severity. Clicking on the visible name will open [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).  Hosts displayed on the map can be filtered by problem severity. Press on the filter icon in the widget's upper right corner and mark the required severities.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget_filter.png)  It is possible to zoom in and out the map by using the plus and minus buttons in the widget's upper left corner or by using the mouse scroll wheel or touchpad. To set the current view as default, right-click anywhere on the map and select *Set this view as default*. This setting will override *Initial view* widget parameter for the current user. To undo this action, right-click anywhere on the map again and select *Reset the initial view*.  When *Initial view* or *Default view* is set, you can return to this view at any time by pressing on the home icon on the left.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget3.png)  
zh-cn	#### Configuration  To add the widget, select *Geomap* as type.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget.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 to be displayed on the map. 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 to be displayed all the map. 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 hosts 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| |*Initial view*|Comma separated center coordinates and an optional zoom level to display when the widget is initially loaded in the format `<latitude>,<longitude>,<zoom>`<br>If initial zoom is specified, the Geomap widget is loaded at the given zoom level. Otherwise, initial zoom is calculated as half of the [max zoom](/manual/web_interface/frontend_sections/administration/general#geographical_maps) for the particular tile provider.<br>The initial view is ignored if the default view is set (see below).<br>Examples:<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891|  Host markers displayed on the map have the color of the host's most serious problem and green color if a host has no problems. Clicking on the host marker allows viewing the host's visible name and the number of unresolved problems grouped by severity. Clicking on the visible name will open [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).  Hosts displayed on the map can be filtered by problem severity. Press on the filter icon in the widget's upper right corner and mark the required severities.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget_filter.png)  It is possible to zoom in and out the map by using the plus and minus buttons in the widget's upper left corner or by using the mouse scroll wheel or touchpad. To set the current view as default, right-click anywhere on the map and select *Set this view as default*. This setting will override *Initial view* widget parameter for the current user. To undo this action, right-click anywhere on the map again and select *Reset the initial view*.  When *Initial view* or *Default view* is set, you can return to this view at any time by pressing on the home icon on the left.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget3.png)  

en-us	#### Configuration  To assign triggers as link indicators, do the following:  -   select a map element -   click on *Edit* in the *Links* section for the appropriate link -   click on *Add* in the *Link indicators* block and select one or more     triggers  ![](../../../../../assets/en/manual/config/visualization/map_triggers.png){width="600"}  All mandatory input fields are marked with a red asterisk.  Added triggers can be seen in the *Link indicators* list.  You can set the link type and color for each trigger directly from the list. When done, click on *Apply*, close the form and click on *Update* to save the map changes.
zh-cn	####  配置  要将触发器分配为链接指示器，请执行以下操作：  - 选择地图元素 - 单击 *链接* 部分中的 *编辑* 以获取相应的链接 - 点击*链接指标*块中的*添加*并选择一个或多个触发器  ![](../../../../../assets/en/manual/config/visualization/map_triggers.png){width="600"}  所有必填字段都标有红色星号。  在*链接指标*列表中可以看到添加的触发器。  你可以直接从列表中设置每个触发器的链接类型和颜色。完成后，点击 *应用*，关闭表格并点击 *更新*保存地图更改。

en-us	#### Configuration  To be able to send and receive notifications from Zabbix you have to:  -   [define the media](/manual/config/notifications/media) to send a     message to  ::: notewarning The default trigger severity ('Not classified') **must be** checked in user media [configuration](/manual/config/notifications/media/email#user_media) if you want to receive notifications for non-trigger events such as discovery, active agent autoregistration or internal evens. :::  -   [configure an action     operation](/manual/config/notifications/action/operation) that sends     a message to one of the defined media  ::: noteimportant Zabbix sends notifications only to those users that have at least 'read' permissions to the host that generated the event. At least one host of a trigger expression must be accessible. :::  You can configure custom scenarios for sending messages using [escalations](/manual/config/notifications/action/escalations).  To successfully receive and read e-mails from Zabbix, e-mail servers/clients must support standard 'SMTP/MIME e-mail' format since Zabbix sends UTF-8 data (If the subject contains ASCII characters only, it is not UTF-8 encoded.). The subject and the body of the message are base64-encoded to follow 'SMTP/MIME e-mail' format standard.  Message limit after all macros expansion is the same as message limit for [Remote commands](/manual/config/notifications/action/operation/remote_command).
zh-cn	#### 配置  为了能够从Zabbix发送和接收消息你必须：  -   定义发送消息的[媒体](/manual/config/notifications/media)   ::: notewarning  如果要接收非触发器事件如发现、主动代理自动注册或内部事件，**必须** 在用户媒体[配置](/manual/config/notifications/media/email#user_media) 中勾选默认触发器严重性（‘Not classified’）。  :::  -   配置发送消息到已经定义的媒体的[动作](/manual/config/notifications/action/operation)   ::: noteimportant Zabbix只向对产生事件的主机上至少一个触发器表达式有‘read’权限的用户发送消息。  :::  你可以配置自定义方案使用[升级](/manual/config/notifications/action/escalations)发送消息。  Zabbix发送的数据是UTF-8格式的（主题只包含ASCII字符不支持UTF-8编码），消息的主题和内容是遵循‘SMTP/MIME e-mail’格式采用base64编码的。为了成功从Zabbix接收和读取邮件，邮件服务器和客户端必须支持标准‘SMTP/MIME e-mail’格式。  宏扩展后的消息限制与[远程命令](/manual/config/notifications/action/operation/remote_command)消息限制相同。

en-us	#### Configuration  To configure a CSV to JSON preprocessing step:  -   Go to the Preprocessing tab in     [item](/manual/config/items/preprocessing)/[discovery     rule](/manual/discovery/low_level_discovery#preprocessing)     configuration -   Click on *Add* -   Select the *CSV to JSON* option  ![](../../../../../assets/en/manual/appendix/csv_to_json_params.png){width="600"}  The first parameter allows to set a custom delimiter. Note that if the first line of CSV input starts with "Sep=" and is followed by a single UTF-8 character then that character will be used as the delimiter in case the first parameter is not set. If the first parameter is not set and a delimiter is not retrieved from the "Sep=" line, then a comma is used as a separator.  The second optional parameter allows to set a quotation symbol.  If the *With header row* checkbox is marked, the header line values will be interpreted as column names (see [Header processing](#csv_header_processing) for more information).  If the *Custom on fail* checkbox is marked, the item will not become unsupported in case of a failed preprocessing step. Additionally custom error handling options may be set: discard the value, set a specified value or set a specified error message.
zh-cn	#### 配置  配置CSV到JSON的预处理步骤:  -   转到预处理选项 [监控项](/manual/config/items/preprocessing)/[自动发现规则](/manual/discovery/low_level_discovery#预处理) 配置 -   点击 *添加* -   选择 *CSV to JSON* 选项  ![](../../../../../assets/en/manual/appendix/csv_to_json_params.png){width="600"}  第一个参数允许设置自定义分隔符。请注意，如果CSV输入的第一行以“Sep=”开头，后跟一个UTF-8字符，则在未设置第一个参数的情况下，该字符将用作分隔符。如果未设置第一个参数，且未从“Sep=”行检索到分隔符，则使用逗号作为分隔符。  第二个可选参数允许设置引号符号。  如果勾选 *With header row* ，标题行值将被解释为列名 (详见[标题预处理](#csv_header_processing) 了解更多信息)。  如果勾选 *Custom on fail* ，那么在预处理步骤失败的情况下，该监控项项将不会不受支持。另外，可以设置自定义错误处理选项:丢弃该值，设置指定值或设置指定的错误消息。

en-us	#### Configuration  To configure a maintenance period:  -   Go to: *Configuration → Maintenance* -   Click on *Create maintenance period* (or on the name of an existing     maintenance period) -   Enter maintenance parameters in the form  ![](../../assets/en/manual/maintenance/maintenance.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Name*|Name of the maintenance period.| |*Maintenance type*|Two types of maintenance can be set:<br>**With data collection** - data will be collected by the server during maintenance, triggers will be processed<br>**No data collection** - data will not be collected by the server during maintenance| |*Active since*|The date and time when executing maintenance periods becomes active.<br>*Note*: Setting this time alone does not activate a maintenance period; for that go to the *Periods* tab.| |*Active till*|The date and time when executing maintenance periods stops being active.| |*Periods*|This block allows you to define the exact days and hours when the maintenance takes place. Clicking on ![](../../assets/en/manual/maintenance/add_link.png) opens a popup window with a flexible *Maintenance period* form where you can define maintenance schedule. See [Maintenance periods](#maintenance_periods) for a detailed description.| |*Host groups*|Select host groups that the maintenance will be activated for. The maintenance will be activated for all hosts from the specified host group(s). This field is auto-complete, so starting to type in it will display a dropdown of all available host groups.<br>Specifying a parent host group implicitly selects all nested host groups. Thus the maintenance will also be activated on hosts from nested groups.| |*Hosts*|Select hosts that the maintenance will be activated for. This field is auto-complete, so starting to type in it will display a dropdown of all available hosts.<br>| |*Tags*|If maintenance tags are specified, maintenance for the selected hosts will still be activated, but problems will only be suppressed (i.e. no actions will be taken) if their tags are a match.<br>In case of multiple tags, they are calculated as follows:<br>**And/Or** - all tags must correspond; however tags with the same tag name are calculated by the Or condition<br>**Or** - enough if one tag corresponds<br>There are two ways of matching the tag value:<br>**Contains** - case-sensitive substring match (tag value contains the entered string)<br>**Equals** - case-sensitive string match (tag value equals the entered string)| |*Description*|Description of maintenance period.|
zh-cn	#### 配置  配置维护期有以下操作步骤：  -   转到：*配置（Configuration） → 维护（Maintenance）* -   单击创建维护期（或现有维护期的名称） -   在表格中输入维护参数  ![](../../assets/en/manual/maintenance/maintenance.png)  所有必填字段都标有红色星号。  |参数|描述| |---------|-----------| |*名字（Name）*|维护期的名称。| |*维护类型（Maintenance type）*|可以设置两种维护方式：<br>**有数据采集（With data collection）** - 维护时服务器采集数据，处理触发器 <br>**无数据采集（No data collection）** - 维护时服务器不采集数据| |*启用自从（Active since）*|执行维护期的日期和时间变为活动状态。<br>*注意*：单独设置此时间不会激活维护期；为此，请转到*期间（Periods）*选项卡| |*启用直到（Active till）*|执行维护期停止活动的日期和时间。| |*时期（Periods）*|此块允许您定义进行维护的确切日期和时间。单击 ![](../../assets/en/manual/maintenance/add_link.png) 会打开一个弹窗，其中包含灵活的 * 维护期表单*，您可以在其中定义维护计划。有关详细说明，请参阅[维护期](#maintenance_periods)。| |*主机组（Host groups）*|选择将为其激活维护的主机组。将为指定主机组中的所有主机激活维护。此字段是自动完成的，因此开始输入它将显示所有可用主机组的下拉列表。<br>指定父主机组会隐式选择所有嵌套主机组。因此，维护也将在嵌套组的主机上激活。| |*主机（Hosts）*|选择将为其激活维护的主机。此字段是自动完成的，因此输入它将显示所有可用主机的下拉列表。<br>| |*标签（Tags）*|如果指定了维护标签，对选定主机的维护仍将被激活，但只有当它们的标签匹配时才会抑制问题（即不采取任何措施）。<br>如果有多个标签，则计算如下：<br>**And/Or** - 所有标签必须对应；但是标签名相同的标签由 Or 条件计算<br>**Or** - 一个标签对应即可<br>匹配标签值有两种方式：<br>**Contains** - 区分大小写的子字符串匹配（标签值包含输入的字符串）<br>**Equals** - 区分大小写字符串匹配（标签值等于输入的字符串）| |*描述（Description）*|维护期说明。|

en-us	#### Configuration  To configure a user group:  -   Go to *Administration → User groups* -   Click on *Create user group* (or on the group name to edit an     existing group) -   Edit group attributes in the form  The **User group** tab contains general group attributes:  ![](../../../../assets/en/manual/config/user_group.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |---------|-----------| |*Group name*|Unique group name.| |*Users*|To add users to the group start typing the name of an existing user. When the dropdown with matching user names appears, scroll down to select.<br>Alternatively you may click the *Select* button to select users in a popup.| |*Frontend access*|How the users of the group are authenticated.<br>**System default** - use default authentication method (set [globally](/manual/web_interface/frontend_sections/administration/authentication))<br>**Internal** - use Zabbix internal authentication (even if LDAP authentication is used globally).<br>Ignored if HTTP authentication is the global default.<br>**LDAP** - use LDAP authentication (even if internal authentication is used globally).<br>Ignored if HTTP authentication is the global default.<br>**Disabled** - access to Zabbix frontend is forbidden for this group| |*Enabled*|Status of user group and group members.<br>*Checked* - user group and users are enabled<br>*Unchecked* - user group and users are disabled| |*Debug mode*|Mark this checkbox to activate [debug mode](/manual/web_interface/debug_mode) for the users.|  The **Permissions** tab allows you to specify user group access to host group (and thereby host) data:  ![](../../../../assets/en/manual/config/user_group_permissions.png){width="600"}  Current permissions to host groups are displayed in the *Permissions* block.  If current permissions of the host group are inherited by all nested host groups, that is indicated by the *including subgroups* text in the parenthesis after the host group name.  You may change the level of access to a host group:  -   **Read-write** - read-write access to a host group; -   **Read** - read-only access to a host group; -   **Deny** - access to a host group denied; -   **None** - no permissions are set.  Use the selection field below to select host groups and the level of access to them (note that selecting *None* will remove host group from the list if the group is already in the list). If you wish to include nested host groups, mark the *Include subgroups* checkbox. This field is auto-complete so starting to type the name of a host group will offer a dropdown of matching groups. If you wish to see all host groups, click on *Select*.  Note that it is possible for Super Admin users in host group [configuration](/manual/config/hosts/host#creating_a_host_group) to enforce the same level of permissions to the nested host groups as the parent host group.  The **Tag filter** tab allows you to set tag-based permissions for user groups to see problems filtered by tag name and its value:  ![](../../../../assets/en/manual/config/user_group_tags.png)  To select a host group to apply a tag filter for, click *Select* to get the complete list of existing host groups or start to type the name of a host group to get a dropdown of matching groups. If you want to apply tag filters to nested host groups, mark the *Include subgroups* checkbox.  Tag filter allows to separate the access to host group from the possibility to see problems.  For example, if a database administrator needs to see only "MySQL" database problems, it is required to create a user group for database administrators first, than specify "Service" tag name and "MySQL" value.  ![user\_group\_tag\_filter\_2.png](../../../../assets/en/manual/config/user_group_tag_filter_2.png)  If "Service" tag name is specified and value field is left blank, corresponding user group will see all problems for selected host group with tag name "Service". If both tag name and value fields are left blank but host group selected, corresponding user group will see all problems for selected host group. Make sure a tag name and tag value are correctly specified otherwise a corresponding user group will not see any problems.  Let's review an example when a user is a member of several user groups selected. Filtering in this case will use OR condition for tags.  |   |   |   |   |   |   |   | |---|---|---|---|---|---|---| |**User group A**|<|<|**User group B**|<|<|**Visible result for a user (member) of both groups**| |*Tag filter*|<|<|<|<|<|<| |*Host group*|*Tag name*|*Tag value*|*Host group*|*Tag name*|*Tag value*|<| |Templates/Databases|Service|MySQL|Templates/Databases|Service|Oracle|Service: MySQL or Oracle problems visible| |Templates/Databases|*blank*|*blank*|Templates/Databases|Service|Oracle|All problems visible| |*not selected*|*blank*|*blank*|Templates/Databases|Service|Oracle|<Service:Oracle> problems visible|  ::: noteimportant  Adding a filter (for example, all tags in a certain host group "Templates/Databases") results in not being able to see the problems of other host groups. :::
zh-cn	####  配置  配置用户组：  - 转到*管理 → 用户组* - 点击*创建用户组*（或组名编辑现有组） - 在表单中编辑组属性  **用户组**选项卡包含常规组属性：  ![](../../../../assets/en/manual/config/user_group.png)  所有必填字段都标有红色星号。  |参数|说明| |---------|------------| |*组名*|唯一组名。| |*Users*|要将用户添加到组，请开始输入现有用户的名称。当出现匹配用户名的下拉菜单时，向下滚动以选择。<br>或者，您也可以单击 *Select* 按钮在弹出窗口中选择用户。| |*前端访问*|如何验证组的用户。<br>**系统默认** - 使用默认验证方法（设置 [全局](/manual/web_interface/frontend_sections/administration/authentication)）<br> **Internal** - 使用 Zabbix 内部身份验证（即使全局使用 LDAP 身份验证）。<br>如果 HTTP 身份验证是全局默认值，则忽略。<br>**LDAP** - 使用 LDAP 身份验证（即使内部身份验证是全局使用）。<br>如果 HTTP 身份验证是全局默认值，则忽略。<br>**禁用** - 该组禁止访问 Zabbix 前端| |*启用*|用户组和组成员的状态。<br>*选中* - 用户组和用户已启用<br>*未选中* - 用户组和用户已禁用| |*调试模式*|选中此复选框可为用户激活 [调试模式](/manual/web_interface/debug_mode)。|  **Permissions** 选项卡允许您指定用户组对主机组（以及主机）数据的访问权限：  ![](../../../../assets/en/manual/config/user_group_permissions.png){width="600"}  对主机组的当前权限显示在 *Permissions* 块中。  如果主机组的当前权限由所有嵌套主机组继承，则由主机组名称后括号中的 *包括子组* 文本指示。  您可以更改对主机组的访问级别：  - **读写** - 对主机组的读写访问； - **Read** - 对主机组的只读访问； - **拒绝** - 拒绝访问主机组； - **无** - 未设置权限。  使用下面的选择字段来选择主机组及其访问级别（请注意，如果主机组已在列表中，则选择 *None* 将从列表中删除主机组）。如果您希望包含嵌套主机组，请选中 *Include subgroups* 复选框。此字段是自动完成的，因此开始输入主机组的名称将提供匹配组的下拉列表。如果您希望查看所有主机组，请单击 *Select*。  请注意，主机组 [configuration](/manual/config/hosts/host#creating_a_host_group) 中的超级管理员用户可以对嵌套主机组强制执行与父主机组相同级别的权限。  **标签过滤器**选项卡允许您为用户组设置基于标签的权限，以查看按标签名称及其值过滤的问题：  ![](../../../../assets/en/manual/config/user_group_tags.png)  要选择要为其应用标记过滤器的主机组，请单击 *Select* 以获取现有主机组的完整列表，或开始键入主机组的名称以获取匹配组的下拉列表。如果要将标签过滤器应用于嵌套主机组，请选中 *Include subgroups* 复选框。  标签过滤器允许将对主机组的访问与查看问题的可能性分开。  例如，如果数据库管理员只需要查看“MySQL”数据库问题，则需要先为数据库管理员创建一个用户组，然后指定“Service”标签名称和“MySQL”值。  ![user\_group\_tag\_filter\_2.png](../../../../assets/en/manual/config/user_group_tag_filter_2.png)  如果指定了“服务”标签名称并且值字段留空，则相应的用户组将看到所选主机组标签名称为“服务”的所有问题。如果标签名称和值字段都留空但选择了主机组，则相应的用户组将看到所选主机组的所有问题。确保正确指定了标签名称和标签值，否则相应的用户组将看不到任何问题。  让我们回顾一个示例，当用户是多个选定用户组的成员时。在这种情况下，过滤将对标签使用 OR 条件。  | | | | | | | | |---|---|---|---|---|---|---| |**用户组 A**|<|<|**用户组 B**|<|<|**两个组的用户（成员）的可见结果**| |*标签过滤器*|<|<|<|<|<|<| |*主机组*|*标签名称*|*标签值*|*主机组*|*标签名称*|*标签值*|<| |模板/数据库|服务|MySQL|模板/数据库|服务|Oracle|服务：MySQL 或 Oracle 问题可见| |模板/数据库|*空白*|*空白*|模板/数据库|服务|Oracle|所有问题可见| |*未选择*|*空白*|*空白*|模板/数据库|服务|Oracle|<Service:Oracle> 问题可见|  ::: noteimportant  添加过滤器（例如，某个主机组“模板/数据库”中的所有标签）会导致无法看到其他主机组的问题。 :::

en-us	#### Configuration  To configure custom alertscripts as the media type:  -   Go to *Administration → Media types* -   Click on *Create media type*  The **Media type** tab contains general media type attributes:  ![](../../../../../assets/en/manual/config/notifications/media/media_script.png)  All mandatory input fields are marked with a red asterisk.  The following parameters are specific for the script media type:  |Parameter|Description| |--|--------| |*Script name*|Enter the name of the script.| |*Script parameters*|Add command-line parameters to the script.<br>{ALERT.SENDTO}, {ALERT.SUBJECT} and {ALERT.MESSAGE} [macros](/manual/appendix/macros/supported_by_location) are supported in script parameters.<br>Customizing script parameters is supported since Zabbix 3.0.|  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 an alertscript doesn't use default messages, message templates for operation types used by this media type must still be defined, otherwise a notification will not be sent.  :::  ::: noteimportant As parallel processing of media types is implemented since Zabbix 3.4.0, it is important to note that with more than one script media type configured, these scripts may be processed in parallel by alerter processes. The total number of alerter processes is limited by the StartAlerters [parameter](/manual/appendix/config/zabbix_server). :::
zh-cn	#### 配置  配置自定义告警脚本为媒介类型：  -   进入 *管理 → 媒介类型* -   点击 *创建媒介类型*  **媒介类型** 页包含一些通用的媒介类型属性如下：  ![](../../../../../assets/en/manual/config/notifications/media/media_script.png)  标红星的为必填字段。  下列参数只适用于脚本媒介类型：  |参数|说明| |---------|-----------| |*脚本名称*|输入脚本的名称| |*脚本参数*|添加脚本的命令行参数<br>脚本参数中支持{ALERT.SENDTO}, {ALERT.SUBJECT}和 {ALERT.MESSAGE} [宏](/manual/appendix/macros/supported_by_location) <br>从Zabbix 3.0版本开始，支持自定义脚本参数.|  关于如何配置默认消息及告警处理的详细内容，请参见 [通用媒介类型参数](/manual/config/notifications/media#common_parameters)   ::: notewarning 即使告警脚本没有使用默认消息，此媒介类型使用的操作类型的消息模板仍必须定义，否则通知将无法发送。 :::  ::: noteimportant 从Zabbix 3.4.0开始实现了多个告警媒介并行处理，所以需要注意的是，当配置了多个告警脚本时，这些脚本是可以被告警进程并行处理的。告警进程的进程数可以通过Zabbix Server的配置项StartAlerters[参数](/manual/appendix/config/zabbix_server)进行限制。 :::

en-us	#### Configuration  To configure event correlation rules globally:  -   Go to *Configuration* → *Event correlation* -   Click on *Create correlation* to the right (or on the correlation     name to edit an existing rule) -   Enter parameters of the correlation rule in the form  ![correlation\_rule.png](../../../../assets/en/manual/config/event_correlation/correlation_rule.png){width="600"}  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |--|--------| |*Name*|Unique correlation rule name.| |*Type of calculation*|The following options of calculating conditions are available:<br>**And** - all conditions must be met<br>**Or** - enough if one condition is met<br>**And/Or** - AND with different condition types and OR with the same condition type<br>**Custom expression** - a user-defined calculation formula for evaluating action conditions. It must include all conditions (represented as uppercase letters A, B, C, ...) and may include spaces, tabs, brackets ( ), **and** (case sensitive), **or** (case sensitive), **not** (case sensitive).| |*Conditions*|List of conditions. See below for details on configuring a condition.| |*Description*|Correlation rule description.| |*Operations*|Mark the checkbox of the operation to perform when event is correlated. The following operations are available:<br>**Close old events** - close old events when a new event happens. Always add a condition based on the old event when using the *Close old events* operation or all existing problems could be closed.<br>**Close new event** - close the new event when it happens| |*Enabled*|If you mark this checkbox, the correlation rule will be enabled.|  To configure details of a new condition, click on ![](../../../../assets/en/manual/config/add_link.png) in the Conditions block. A popup window will open where you can edit the condition details.  ![](../../../../assets/en/manual/config/event_correlation/correlation_rule_condition.png)  |Parameter|Description| |--|--------| |*New condition*|Select a condition for correlating events.<br>*Note* that if no old event condition is specified, all old events may be matched and closed. Similarly if no new event condition is specified, all new events may be matched and closed.<br>The following conditions are available:<br>**Old event tag** - specify the old event tag for matching.<br>**New event tag** - specify the new event tag for matching.<br>**New event host group** - specify the new event host group for matching.<br>**Event tag pair** - specify new event tag and old event tag for matching. In this case there will be a match if the **values** of the tags in both events match. Tag *names* need not match.<br>This option is useful for matching runtime values, which may not be known at the time of configuration (see also [Example 1](/manual/config/event_correlation/global#examples)).<br>**Old event tag value** - specify the old event tag name and value for matching, using the following operators:<br>*equals* - has the old event tag value<br>*does not equal* - does not have the old event tag value<br>*contains* - has the string in the old event tag value<br>*does not contain* - does not have the string in the old event tag value<br>**New event tag value** - specify the new event tag name and value for matching, using the following operators:<br>*equals* - has the new event tag value<br>*does not equal* - does not have the new event tag value<br>*contains* - has the string in the new event tag value<br>*does not contain* - does not have the string in the new event tag value|  ::: notewarning Because misconfiguration is possible, when similar event tags may be created for **unrelated** problems, please review the cases outlined below! :::  -   Actual tags and tag values only become visible when a trigger fires.     If the regular expression used is invalid, it is silently replaced     with an \*UNKNOWN\* string. If the initial problem event with an     \*UNKNOWN\* tag value is missed, there may appear subsequent OK     events with the same \*UNKNOWN\* tag value that may close problem     events which they shouldn't have closed.  ```{=html} <!-- --> ``` -   If a user uses the {ITEM.VALUE} macro without macro functions as the     tag value, the 255-character limitation applies. When log messages     are long and the first 255 characters are non-specific, this may     also result in similar event tags for unrelated problems.
zh-cn	#### 配置  要全局配置事件关联规则：  -   去 *配置* → *关联事件* -   在右侧点击*新建关联* （或点击关联名称编辑已有规则） -   在表单中输入关联规则的参数  ![correlation\_rule.png](../../../../assets/en/manual/config/event_correlation/correlation_rule.png){width="600"}  所有必填输入字段都标有红色星号。  |参数|描述| |---------|-----------| |*名称*|唯一的关联规则名称。| |*计算类型*|有以下计算条件的选项可供选择：<br>**And** - 必须满足所有条件<br>**Or** - 如果满足一个条件就足够了<br>**And/Or** - AND 具有不同的条件类型和 OR 具有同一条件类型<br>**自定义表达式** - 用于评估动作条件的用户定义的计算公式。它必须包括所有条件（以大写字母A、B、C、...表示），并可能包括空格、制表符、括号（）、 **and**（区分大小写）、**or**（区分大小写）、**not**（区分大小写）。| |*条件*|条件列表。有关配置条件的详细信息，请参阅下文。| |*描述*|关联规则的描述。| |*操作*|在事件关联时标记要执行的操作的复选框。可以使用以下操作：<br>**关闭旧事件** - 发生新事件时关闭旧事件。 使用*关闭旧事件*操作时，始终根据旧事件添加一个条件，否则现有的所有得问题都会关闭。<br>**关闭新事件** - 新事件发生时关闭它。| |*已启用*|如果您标记此复选框，将启用关联规则。|  要配置新条件的详细信息，请在条件模块里单击 ![](../../../../assets/en/manual/config/add_link.png) 。将打开一个弹出窗口，您可以在其中编辑条件 细节。  ![](../../../../assets/en/manual/config/event_correlation/correlation_rule_condition.png)  |参数|描述| |---------|-----------| |*新条件*|选择关联事件的条件。<br>*注意* 如果没有指定旧事件的条件，所有旧事件都可以被匹配和关闭。同样，如果没有指定新事件的条件，所有新事件都可以被匹配和关闭。<br>有以下条件选项可供选择：<br>**旧事件标签** - 指定用于匹配旧事件的标签。<br>**新事件标签** - 指定用于匹配新事件的标签。<br>**新事件主机组** - 指定要匹配新事件的主机组。<br>**事件标签对** - 指定新事件的标签和旧事件的标签以进行匹配。在这种情况下，如果两个事件的标签的**值**匹配，事件也将匹配。标签*名称*不需要匹配。<br>此选项可用于匹配运行时值，该值在配置时可能不知道（另见[示例 1](/manual/config/event_correlation/global#examples)）。<br>**旧事件标签值** - 指定用于匹配的旧事件标签名称和值，使用以下运算符： <br>*等于* - 有旧事件标签值<br>*不等于* - 没有旧事件标签值<br>*包含* - 有旧事件标签值中的字符串<br>*不包含* - 没有旧事件标签值中的字符串<br>**新事件标签标签值** - 使用以下运算符指定用于匹配的新事件标签名称和值：<br>*等于* - 有新事件的标签值<br>*不等于* - 没有新事件的标签值<br>*包含* - 有新事件标签值中的字符串<br>*不包含* - 没有新事件标签值中的字符串|  ::: notewarning 由于可能存在配置错误，当可能为**不相关**问题创建类似事件标签时，请查看下面列出的案例！ :::  - · 实际标签和标签值仅在触发器触发时才可见。 如果使用的正则表达式无效，它会自动替换为 \*UNKNOWN\* 字符串。 如果带有 \*UNKNOWN\* 标记值的初始问题事件被遗漏，可能会出现具有相同 \*UNKNOWN\* 标记值的后续正常事件，这些事件可能会关闭它们不应该关闭的问题事件。  ```{=html} <!-- --> ``` -   如果用户使用{ITEM.VALUE}宏，而不使用宏函数作为标签值，则适用255个字符的限制。日志信息时很长，且前255个字符是非特定的，这可能还会导致无关问题有类似的事件标签。

en-us	#### Configuration  To configure, select *Action log* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/action_log.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:  |   |   | |---|---| |*Sort entries by*|Sort entries by:<br>**Time** (descending or ascending)<br>**Type** (descending or ascending)<br>**Status** (descending or ascending)<br>**Recipient** (descending or ascending).| |*Show lines*|Set how many action log lines will be displayed in the widget.|
zh-cn	#### 配置  选择*动作记录*为类型来配置：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/action_log.png)  除了所有组件的[通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 参数外，您也可以设置以下选项：  |   |   | |---|---| |*排序方式*|排序方式:<br>**时间** （降序或升序）<br>**类型** （降序或升序）<br>**状态** （降序或升序）<br>**接收人** （降序或升序）.| |*显示行*|设置组件中可以显示多少行动作记录。|

en-us	#### Configuration  To configure, select *Clock* as type:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/clock.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:  |   |   | |---|---| |*Time type*|Select local, server, or specified host time.<br>Server time will be identical to the time zone set globally or for the Zabbix user.| |*Item*|Select the item for displaying time. To display host time, use the `system.localtime[local]` [item](/manual/config/items/itemtypes/zabbix_agent). This item must exist on the host.<br>This field is available only when *Host time* is selected.|
zh-cn	#### 配置  选择*时钟*为类型来配置：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/clock.png)  除了所有组件的[通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 参数外，您也可以设置以下选项：  |   |   | |---|---| |*时间类型*|选择本地、服务器、或特定主机时间。<br>服务器时间会与全局设置的时区或Zabbix用户的时区相同。| |*监控项*|选择显示的时间的监控项。要显示主机时间，使用`system.localtime[local]` [监控项](/manual/config/items/itemtypes/zabbix_agent)。此监控项必须在主机上存在。<br>此字段仅在*主机时间*被选择时可用。|