en-us	#### Map element Host group  The map element Host group object defines one host group element.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groupid|string|Host group ID|
zh-cn	####  拓扑图元素中的主机组  拓扑图元素中的主机组对象定义是一个主机组元素.  |属性|类型|说明| |--------|----|-----------| |groupid|string|主机组 ID|

en-us	#### Map element Host  The map element Host object defines one host element.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |hostid|string|Host ID|
zh-cn	####  拓扑图元素的主机  拓扑图元素中的主机对象定义是一个主机元素  |属性|类型|说明| |--------|----|-----------| |hostid|string|主机 ID|

en-us	#### Map element Map  The map element Map object defines one map element.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapid|string|Map ID|
zh-cn	#### 拓扑图元素中的拓扑图  拓扑图元素中的拓扑图对象默认是一个拓扑图元素  |属性|类型|说明| |--------|----|-----------| |sysmapid|string|拓扑图 ID|

en-us	#### Map element Trigger  The map element Trigger object defines one or more trigger elements.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |triggerid|string|Trigger ID|
zh-cn	####  拓扑图元素中的触发器  拓扑图元素中的触发器对象定义的是一个或者多个触发器元素  |属性|类型|说明| |--------|----|-----------| |triggerid|string|触发器 ID|

en-us	# map.get
zh-cn	# 获取拓扑图

en-us	#### Map listing  ![](../../../../../assets/en/manual/web_interface/map_list.png){width="600"}  Displayed data:  |Column|Description| |--|--------| |*Name*|Name of the map. Click on the name to [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) the map.| |*Width*|Map width is displayed.| |*Height*|Map height is displayed.| |*Actions*|Two actions are available:<br>**Properties** - edit general map [properties](/manual/config/visualization/maps/map#creating_a_map)<br>**Constructor** - access the grid for adding [map elements](/manual/config/visualization/maps/map#adding_elements)|  To [configure](/manual/config/visualization/maps/map#creating_a_map) a new map, click on the *Create map* button in the top right-hand corner. To import a map from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner. The user who imports the map will be set as its owner.  Two buttons below the list offer some mass-editing options:  -   *Export* - export the maps to a YAML, XML, or JSON file -   *Delete* - delete the maps  To use these options, mark the checkboxes before the respective maps, then click on the required button.
zh-cn	#### 拓扑图列表  ![](../../../../../assets/en/manual/web_interface/map_list.png){width="600"}  显示的数据：  |列|#### 描述| |------|-----------| |*名称*|拓扑图名称。单击名称可以 [查看拓扑图](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)。| |*宽度*|显示拓扑图宽度。| |*高度*|显示拓扑图高度。| |*动作*|有两个动作可以用：<br>**属性** - 编辑拓扑图通用 [属性](/manual/config/visualization/maps/map#creating_a_map)<br>**构造函数** - 通过网络化来添加[拓扑图元素](/manual/config/visualization/maps/map#adding_elements)|  要 [配置](/manual/config/visualization/maps/map#creating_a_map) 新地图，请单击右上角的的 *创建地图* 按钮。要从YAML,、XML、或JSON文件导入拓扑图，请单击右上角的 *导入* 按钮。 导入拓扑图的用户将被设置为其所有者。  列表下方的两个按钮有一些批量编辑选项：  - · *导出* - 将拓扑图导出为YAML,、XML、或JSON文件 - · *删除* - 删除拓扑图  要使用这些选项，请选中各个拓扑图之前的复选框，然后单击所需的按钮。

en-us	# > Map object  The following objects are directly related to the `map` API.
zh-cn	# > 拓扑图对象

en-us	##### Mapping LLD macros  Next you have to go to the LLD macros tab and make the following mappings:      {#VOLUME}=$.labels['volume']     {#METRIC}=$['name']     {#HELP}=$['help']
zh-cn	##### 映射LLD宏  接下来需要找到LLD宏的配置面板并做下面的映射:      {#VOLUME}=$.labels['volume']     {#METRIC}=$['name']     {#HELP}=$['help']

en-us	#### Maps  Configure maps to create detailed dynamic representations of your IT infrastructure.  [Map API](/manual/api/reference/map)
zh-cn	#### 拓扑图  配置拓扑图用于创建 IT基础架构 的详细动态展现。  [Map API](/manual/api/reference/map)

en-us	# Map  This class is designed to work with maps.  Object references:\  -   [Map](/manual/api/reference/map/object#map) -   [Map element](/manual/api/reference/map/object#map_element) -   [Map link](/manual/api/reference/map/object#map_link) -   [Map URL](/manual/api/reference/map/object#map_url) -   [Map user](/manual/api/reference/map/object#map_user) -   [Map user group](/manual/api/reference/map/object#map_user_group) -   [Map shape](/manual/api/reference/map/object#map_shapes) -   [Map line](/manual/api/reference/map/object#map_lines)  Available methods:\  -   [map.create](/manual/api/reference/map/create) - create new maps -   [map.delete](/manual/api/reference/map/delete) - delete maps -   [map.get](/manual/api/reference/map/get) - retrieve maps -   [map.update](/manual/api/reference/map/update) - update maps
zh-cn	# 拓扑图  这个接口用于设计和处理拓扑  对象引用: -   [拓扑](/manual/api/reference/map/object#map) -   [拓扑图元素](/manual/api/reference/map/object#map_element) -   [拓扑图关联](/manual/api/reference/map/object#map_link) -   [拓扑图URL](/manual/api/reference/map/object#map_url) -   [拓扑图用户](/manual/api/reference/map/object#map_user) -   [拓扑图用户组](/manual/api/reference/map/object#map_user_group) -   [拓扑图形状](/manual/api/reference/map/object#map_shapes) -   [拓扑图线](/manual/api/reference/map/object#map_lines)  可用方法:  -   `map.create` - 创建新拓扑 -   `map.delete` - 删除拓扑 -   `map.get` - 查看拓扑 -   `map.update` - 更新拓扑

en-us	# map.update
zh-cn	# 更新拓扑图

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Copy* - copy the graphs to other hosts or templates -   *Delete* - delete the graphs  To use these options, mark the checkboxes before the respective graphs, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *复制* -将图形复制到其他主机或模板中 -   *删除* -删除图形  要使用这些选项，请在需操作的图形前勾选复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Copy* - copy the graphs to other hosts or templates -   *Delete* - delete the graphs  To use these options, mark the checkboxes before the respective graphs, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *复制* -将图形复制到其他主机或模板中 -   *删除* -删除图形  要使用这些选项，请在需操作的图形前勾选复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Create enabled* - create these hosts as *Enabled* -   *Create disabled* - create these hosts as *Disabled* -   *Delete* - delete these host prototypes  To use these options, mark the checkboxes before the respective host prototypes, then click on the required button.
zh-cn	##### 批量编辑选项  列表下放的按钮提供了一些批量编辑的选项：  -   *Create enabled* - 将这些主机创建为*Enabled* -   *Create disabled* - 将这些主机创建为*Disabled* -   *Delete* - 删除这些主机原型  要使用这些选项，请在相应主机原型之前勾选复选框，然后单击所需按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Create enabled* - create these hosts as *Enabled* -   *Create disabled* - create these hosts as *Disabled* -   *Delete* - delete these host prototypes  To use these options, mark the checkboxes before the respective host prototypes, then click on the required button.
zh-cn	##### 批量编辑选项  列表下放的按钮提供了一些批量编辑的选项：  -   *Create enabled* - 将这些主机创建为*Enabled* -   *Create disabled* - 将这些主机创建为*Disabled* -   *Delete* - 删除这些主机原型  要使用这些选项，请在相应主机原型之前勾选复选框，然后单击所需按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change the action status to *Enabled* -   *Disable* - change the action status to *Disabled* -   *Delete* - delete the actions  To use these options, mark the checkboxes before the respective actions, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用* -将动作状态修改为“已监控” -   *禁用* -将动作状态修改为“未监控” -   *删除* - 删除动作  要使用这些选项，请在相应主机前勾选复选框，然后点击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change the low-level discovery rule status to *Enabled* -   *Disable* - change the low-level discovery rule status to *Disabled* -   *Delete* - delete the low-level discovery rules  To use these options, mark the checkboxes before the respective discovery rules, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用*—修改低级别发现规则的状态为“*已启用” -   *禁用* -将低级别发现规则的状态修改为“*禁用*” -   *删除* -删除低级别发现规则  要使用这些选项，请在各自的发现规则之前标记复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change the media type status to *Enabled* -   *Disable* - change the media type status to *Disabled* -   *Export* - export the media types to a YAML, XML or JSON file -   *Delete* - delete the media types  To use these options, mark the checkboxes before the respective media types, then click on the required button.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一些批量编辑选项：  - · *启用* - 将媒介类型状态更改为 *启用* - · *停用* - 将媒介类型状态更改为 *Disabled* - · *导出* - 将媒介类型导出为 YAML、XML 或 JSON 文件 - · *删除* - 删除媒介类型  要使用这些选项，请在相应媒介类型之前标记复选框，然后单击所需按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change the scenario status to *Enabled* -   *Disable* - change the scenario status to *Disabled* -   *Delete* - delete the web scenarios  To use these options, mark the checkboxes before the respective web scenarios, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用*—将场景状态修改为“*启用*” -   *禁用*—将场景状态修改为*禁用* -   *删除* -删除web场景  要使用这些选项，请在各自的web场景前标记复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change the user group status to *Enabled* -   *Disable* - change the user group status to *Disabled* -   *Enable debug mode* - enable debug mode for the user groups -   *Disable debug mode* - disable debug mode for the user groups -   *Delete* - delete the user groups  To use these options, mark the checkboxes before the respective user groups, then click on the required button.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一些批量编辑选项：  - · *启用* - 将用户组状态更改为*启用* - · *停用* - 将用户组状态更改为 *停用* - · *启用调试模式* - 为用户组启用调试模式 - · *禁用调试模式* - 禁用用户组的调试模式 - · *停用* - 删除用户组  要使用这些选项，请在相应用户组之前标记复选框，然后单击所需按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change trigger status to *Enabled*. -   *Disable* - change trigger status to *Disabled*. -   *Copy* - copy the triggers to other hosts or templates. -   *Mass update* - update several properties for a number of triggers     at once. -   *Delete* - delete the triggers.  To use these options, mark the checkboxes before the respective triggers, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  - *启用* -将触发器状态更改为*启用* - *禁用* -将触发器状态更改为*禁用* - *复制* -将触发器复制到其他主机或模板 - *批量更新* -一次更新多个触发器的几个属性 - *删除* -删除触发器  要使用这些选项，请在各个触发器前标记复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change trigger status to *Enabled* -   *Disable* - change trigger status to *Disabled* -   *Copy* - copy the triggers to other hosts or templates -   *Mass update* - update several properties for a number of triggers     at once -   *Delete* - delete the triggers  To use these options, mark the checkboxes before the respective triggers, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  - *启用* -将触发器状态更改为*启用* - *禁用* -将触发器状态更改为*禁用* - *复制* -将触发器复制到其他主机或模板 - *批量更新* -一次更新多个触发器的几个属性 - *删除* -删除触发器  要使用这些选项，请在各个触发器前标记复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable hosts* - change the status of all hosts in the group to     "Monitored" -   *Disable hosts* - change the status of all hosts in the group to     "Not monitored" -   *Delete* - delete the host groups  To use these options, mark the checkboxes before the respective host groups, then click on the required button.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一些批量编辑选项：  -   *启用主机* - 将组中所有主机的状态更改为“已监控” -   *禁用主机* - 将组中所有主机的状态更改为“未监控” -   *删除* - 删除主机组  要使用这些选项，请在相应主机组之前选中复选框，然后单击所需按钮。

en-us	##### Master item  Create an IPMI item using the following key:      ipmi.get  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_item.png)  Set the type of information to "Text" for possibly big JSON data.
zh-cn	##### 主监控项  使用下面的键创建一个IPMI监控项:      ipmi.get  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_item.png)  设置信息类型为 "文本"，用于接收可能获取的大块JSON数据。

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

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

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

en-us	# > Media type object  The following objects are directly related to the `mediatype` API.
zh-cn	 # > 媒介类型对象  以下对象与 `mediatype` API 直接相关。

en-us	# Media type  This class is designed to work with media types.  Object references:\  -   [Media type](/manual/api/reference/mediatype/object#media_type)  Available methods:\  -   [mediatype.create](/manual/api/reference/mediatype/create) -     creating new media types -   [mediatype.delete](/manual/api/reference/mediatype/delete) -     deleting media types -   [mediatype.get](/manual/api/reference/mediatype/get) - retrieving     media types -   [mediatype.update](/manual/api/reference/mediatype/update) -     updating media types
zh-cn	# 媒介类型  此类用于管理媒介类型。  对象引用：\  -   [媒介类型](/manual/api/reference/mediatype/object#媒介类型)  可用方法:\  -   [mediatype.create](/manual/api/reference/mediatype/create) - 创建新的媒介类型 -   [mediatype.delete](/manual/api/reference/mediatype/delete) - 删除媒介类型 -   [mediatype.get](/manual/api/reference/mediatype/get) - 获取媒介类型 -   [mediatype.update](/manual/api/reference/mediatype/update) - 更新媒介类型

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

en-us	#### Memory suffixes  Memory size suffixes are supported in:  -   trigger [expression](/manual/config/triggers/expression) constants     and function parameters -   constants of [calculated     item](/manual/config/items/itemtypes/calculated) formulas  For memory size you can use:  -   **K** - kilobyte -   **M** - megabyte -   **G** - gigabyte -   **T** - terabyte
zh-cn	#### 内存单位  内存大小单位支持：   -   触发器 [表达式](/manual/config/triggers/expression) 常量和函数参数 -   [计算监控项](/manual/config/items/itemtypes/calculated) 公式的常数  对于内存大小可以使用：  -   **K** - 千字节 -   **M** - 兆字节 -   **G** - 吉字节 -   **T** - 太字节

en-us	# Method reference  This section provides an overview of the functions provided by the Zabbix API and will help you find your way around the available classes and methods.
zh-cn	# 方法参考  本节概述了 Zabbix API 提供的函数，并将帮助您找到可用的类和方法。

en-us	##### Minimum weekly disk space among clusters  View the lowest disk space among clusters over a week.  -   add to the data set: hosts `cluster*`, key "Free disk space on     /data" -   select the aggregate function `min` and specify interval `1w` -   a bar graph is displayed, where each bar represents the minimum disk     space per week for each /data volume of the cluster
zh-cn	##### 集群间每周最小磁盘空间  查看一周内集群中最低的磁盘空间。  - 添加到数据集：主机`cluster*`,  "Free disk space on /data”键 - 选择聚合函数`min`并指定间隔`1w` - 显示一个条形图，其中每个条形代表每个 /data 卷的每周的最小磁盘集群空间

en-us	##### Miscellaneous aspects of escalation behavior  Let's consider what happens in different circumstances if an action contains several escalation steps.  |Situation|Behavior| |---------|--------| |*The host in question goes into maintenance after the initial problem notification is sent*|Depending on the *Pause operations for suppressed problems* setting in action [configuration](/manual/config/notifications/action/operation#configuring_an_operation), all remaining escalation steps are executed either with a delay caused by the maintenance period or without delay. A maintenance period does not cancel operations.| |*The time period defined in the **Time period** action condition ends after the initial notification is sent*|All remaining escalation steps are executed. The *Time period* condition cannot stop operations; it has effect with regard to when actions are started/not started, not operations.| |*A problem starts during maintenance and continues (is not resolved) after maintenance ends*|Depending on the *Pause operations for suppressed problems* setting in action [configuration](/manual/config/notifications/action/operation#configuring_an_operation), all escalation steps are executed either from the moment maintenance ends or immediately.| |*A problem starts during a no-data maintenance and continues (is not resolved) after maintenance ends*|It must wait for the trigger to fire, before all escalation steps are executed.| |*Different escalations follow in close succession and overlap*|The execution of each new escalation supersedes the previous escalation, but for at least one escalation step that is always executed on the previous escalation. This behavior is relevant in actions upon events that are created with EVERY problem evaluation of the trigger.| |*During an escalation in progress (like a message being sent), based on any type of event:<br>- the action is disabled<br>Based on trigger event:<br>- the trigger is disabled<br>- the host or item is disabled<br>Based on internal event about triggers:<br>- the trigger is disabled<br>Based on internal event about items/low-level discovery rules:<br>- the item is disabled<br>- the host is disabled*|The message in progress is sent and then one more message on the escalation is sent. The follow-up message will have the cancellation text at the beginning of the message body (*NOTE: Escalation canceled*) naming the reason (for example, *NOTE: Escalation canceled: action '<Action name>' disabled*). This way the recipient is informed that the escalation is canceled and no more steps will be executed. This message is sent to all who received the notifications before. The reason of cancellation is also logged to the server log file (starting from [Debug Level](/manual/appendix/config/zabbix_server) 3=Warning).<br><br>Note that the *Escalation canceled* message is also sent if operations are finished, but recovery operations are configured and are not executed yet.| |*During an escalation in progress (like a message being sent) the action is deleted*|No more messages are sent. The information is logged to the server log file (starting from [Debug Level](/manual/appendix/config/zabbix_server) 3=Warning), for example: `escalation canceled: action id:334 deleted`|
zh-cn	##### 升级行为的其他方面  让我们考虑一下在不同情况下会发生什么。  包含几个升级步骤。  |情境|行为| |---------|--------| |*在发送初始问题通知后，相关主机进入维护状态*|取决于操作[配置](/manual/config/notifications/action/operation#configuring_an_operation)中的*暂停操作抑制问题*设置，所有剩余的升级步骤都会在维护期间造成延迟的情况下或不延迟地执行。维护期不会取消操作| |*在**时间段**操作条件中定义的时间段在发送初始通知后结束*|执行所有剩余的升级步骤。*时间段*条件不能停止操作；它对操作何时启动/未启动而非操作具有影响| |*问题在维护期间开始，并在维护结束后继续(未解决)*|根据操作[配置](/manual/config/notifications/action/operation#configuring_an_operation)中的*暂停被抑制问题的操作*设置，所有升级步骤从维护结束时起或立即执行| |*问题在无数据维护期间开始，并在维护结束后继续(未解决)|必须等待触发，然后执行所有上报步骤| |*不同的升级紧随其后并重叠*|每个新升级的执行都会取代上一个升级，但至少有一个升级步骤总是在上一个升级上执行。这种行为与对触发器的每个问题评估产生的事件的操作相关| |*在升级过程中(如发送消息)，基于任何类型的事件：<br>-基于触发器事件禁用操作：<br>-禁用触发器<br>-基于内部事件禁用主机或项目关于触发器：<br>-基于内部事件关于项目/低级发现规则禁用触发器：<br>-禁用项目<br>-禁用主机*|发送正在进行的消息，然后在升级已发送。后续消息将在消息正文的开头显示取消文本(*注意：升级已取消*)以命名原因(例如，*注意：升级已取消：操作“<action name>”已禁用*)。通过这种方式，收件人将被告知升级已取消，不再执行任何步骤。此消息将发送给之前收到通知的所有人。取消的原因也会记录到服务器日志文件中(从[Debug Level]开始)(/manual/appendix/config/zabbix_server)3=警告)<br><br>请注意，如果操作已完成，但恢复操作已配置且尚未执行，则也会发送*Escalation Cancelled*消息| |*在升级过程中(如发送消息)，操作被删除*|不再发送消息。信息被记录到服务器日志文件中(从[Debug Level]开始)(/manual/appendix/config/zabbix_server)3=Warning)，例如：`escalation Cancelled:action id:334 deleted`|

en-us	#### Monitoring → Problems  The following parameters are supported:  -   `show` - filter option "Show": 1 - recent problems, 2 - all, 3 - in     problem state -   `name` - filter option "Problem": freeform string -   `severities` - filter option "Severity": array of selected     severities in a format 'severities\[\*\]=\*' (replace \* with     severity level): 0 - not classified, 1 - information, 2 - warning,     3 - average, 4 - high, 5 - disaster -   `inventory` - filter option "Host inventory": array of inventory     fields: \[field\], \[value\] -   `evaltype` - filter option "Tags", tag filtering strategy: 0 -     And/Or, 2 - Or -   `tags` - filter option "Tags": array of defined tags: \[tag\],     \[operator\], \[value\] -   `show_tags` - filter option "Show tags": 0 - none, 1 - one, 2 - two,     3 - three -   `tag_name_format` - filter option "Tag name": 0 - full name, 1 -     shortened, 2 - none -   `tag_priority` - filter option "Tag display priority":     comma-separated string of tag display priority -   `show_suppressed` - filter option "Show suppressed problems": should     be 'show\_suppressed=1' to show -   `unacknowledged` - filter option "Show unacknowledged only": should     be 'unacknowledged=1' to show -   `compact_view` - filter option "Compact view": should be     'compact\_view=1' to show -   `highlight_row` - filter option "Highlight whole row" (use problem     color as background color for every problem row): should be '1' to     highlight; can be set only when 'compact\_view' is set -   `filter_name` - filter properties option "Name": freeform string -   `filter_show_counter` - filter properties option "Show number of     records": 1 - show, 0 - do not show -   `filter_custom_time` - filter properties option "Set custom time     period": 1 - set, 0 - do not set -   `sort` - sort column: clock, host, severity, name -   `sortorder` - sort order or results: DESC - descending, ASC -     ascending -   `age_state` - filter option "Age less than": should be     'age\_state=1' to enable 'age'. Is used only when 'show' equals 3. -   `age` - filter option "Age less than": days -   `groupids` - filter option "Host groups": array of host groups IDs -   `hostids` - filter option "Hosts": array of host IDs -   `triggerids` - filter option "Triggers": array of trigger IDs -   `show_timeline` - filter option "Show timeline": should be     'show\_timeline=1' to show -   `details` - filter option "Show details": should be 'details=1' to     show -   `from` - date range start, can be 'relative' (e.g.: now-1m). Is used     only when 'filter\_custom\_time' equals 1. -   `to` - date range end, can be 'relative' (e.g.: now-1m). Is used     only when 'filter\_custom\_time' equals 1.
zh-cn	#### 监控 → 问题  支持以下参数：  -   `show` - 过滤选项“显示”：1 - 最近的问题，2 - 全部，3 - 处于问题状态 -   `name` - 过滤选项“问题”：自由格式字符串 -   `severities` - 过滤选项 "Severity": 所选严重性的数组，格式为 'severities\[\*\]=\*'（用严重性级别替换 \*）：0 - 未分类，1 - 信息，2 - 警告，3 - 一般严重，4 - 严重，5 - 灾难 -   `inventory` - 过滤选项“主机库存”：资产字段数组：\[field\]、\[value\] -   `evaltype` - 过滤选项“Tags”，标签过滤策略：0 - And/Or, 2 - Or -   `tags` - 过滤选项“标签”：定义标签的数组：\[tag\]、\[operator\]、\[value\] -   `show_tags` - 过滤选项“显示标签”：0 - 无，1 - 一，2 - 二，3 - 三 -   `tag_name_format` - 过滤选项“标签名称”：0 - 全名，1 - 缩写，2 - 无 -   `tag_priority` - 过滤选项“标签显示优先级”：标签显示优先级的逗号分隔字符串 -   `show_suppressed` - 过滤选项“显示抑制的问题”：应该是 'show\_suppressed=1' 来显示 -   `unacknowledged` - 过滤选项“仅显示未确认”：应该是 'unacknowledged=1' 才能显示 -   `compact_view` - 过滤选项“Compact view”：应该是 'compact\_view=1' 来显示 -   `highlight_row` - 过滤选项“突出显示整行”（使用问题颜色作为每个问题行的背景颜色）：应该为“1”以突出显示；只有在设置了 'compact\_view' 时才能设置 -   `filter_name` - 过滤器属性选项“名称”：自由格式字符串 -   `filter_show_counter` - 过滤属性选项“显示记录数”：1 - 显示，0 - 不显示 -   `filter_custom_time` - 过滤器属性选项“设置自定义时间段”：1 - 设置，0 - 不设置 -   `sort` - 排序列：时钟、主机、严重性、名称 -   `sortorder` - 排序顺序或结果：DESC - 降序，ASC - 升序 -   `age_state` - 过滤选项“持续时间小于”：应该是“age\_state = 1”以启用“持续时间”。仅在 'show' 等于 3 时使用。 -   `age` - 过滤选项“持续时间小于”：天 -   `groupids` - 过滤选项“主机组”：主机组 ID 数组 -   `hostids` - 过滤选项“Hosts”：主机ID数组 -   `triggerids` - 过滤选项“触发器”：触发器 ID 数组 -   `show_timeline` - 过滤选项“显示时间线”：应该是 'show\_timeline=1' 来显示 -   `details` - 过滤选项“显示详细信息”：应该是 'details=1' 来显示 -   `from` - 日期范围开始，可以是“相对”（例如：now-1m）。仅在 'filter\_custom\_time' 等于 1 时使用。 -   `to` - 日期范围结束，可以是“相对”（例如：now-1m）。仅在 'filter\_custom\_time' 等于 1 时使用。

en-us	#### More info  See [Virtual machine monitoring](/manual/vm_monitoring) for detailed information how to configure Zabbix to monitor VMware environments.
zh-cn	#### 更多信息  如何配置 Zabbix 监控 VMware 环境可以参考 [Virtual machine monitoring](/manual/vm_monitoring) 的详细信息。

en-us	 Most trigger functions are evaluated based on item value [history](/manual/config/items/history_and_trends) data, while some trigger functions for long-term analytics, e.g. **trendavg()**, **trendcount()**, etc, use trend data.
zh-cn	 大多数触发函数都是根据监控项值进行评估的[历史](/manual/config/items/history_and_trends) 数据，而一些用于长期分析的触发功能，例如 **趋势平均值()**,**trendcount()**等，使用趋势数据。

en-us	#### Moving and copy-pasting elements  Several selected elements can be **moved** to another place in the map by clicking on one of the selected elements, holding down the mouse button, and moving the cursor to the desired location.  One or more elements can be **copied** by selecting the elements, then clicking on a selected element with the right mouse button and selecting *Copy* from the menu.  ![](../../../../../assets/en/manual/config/visualization/map_copy.png){width="600"}  To paste the elements, click on a map area with the right mouse button and select *Paste* from the menu. The *Paste without external links* option will paste the elements retaining only the links that are between the selected elements.  Copy-pasting works within the same browser window. Keyboard shortcuts are not supported.
zh-cn	#### 移动和复制粘贴元素  几个选定的元素可以**移动**到地图中的另一个位置通过单击选定元素之一，按住鼠标按钮，然后将光标移动到所需位置。  一个或多个元素可以通过选择元素来**复制**，然后用鼠标右键单击选定的元素并选择*从菜单中复制*。  ![](../../../../../assets/en/manual/config/visualization/map_copy.png){width="600"}  要粘贴元素，请使用鼠标右键单击地图区域并从菜单中选择*粘贴*。 *粘贴没有外部链接*选项将粘贴元素，只保留它们之间的链接选定的元素。  复制粘贴在同一浏览器窗口中工作。不支持键盘快捷键。

en-us	#### Multiple LLD rules for the same item  Since Zabbix agent version 3.2 it is possible to define several low-level discovery rules with the same discovery item.  To do that you need to define the Alias agent [parameter](/manual/appendix/config/zabbix_agentd), allowing to use altered discovery item keys in different discovery rules, for example `vfs.fs.discovery[foo]`, `vfs.fs.discovery[bar]`, etc.
zh-cn	#### 同一监控项的多条LLD规则  从Zabbix agent 3.2版本起，可以为相同的自动发现监控项定义多条低级别自动发现规则。  要实现此功能，需要定义agent [参数](/manual/appendix/config/zabbix_agentd) 别名, 允许在不同自动发现规则中使用同一监控项的不同键, 比如 `vfs.fs.discovery[foo]`, `vfs.fs.discovery[bar]`, 等。

en-us	#### MySQL configuration  Modern versions of the database are ready out-of-the-box for 'required' [encryption mode](/manual/appendix/install/db_encrypt#terminology). A server-side certificate will be created after initial setup and launch.  Create users and roles for the main components:       mysql> CREATE USER         'zbx_srv'@'%' IDENTIFIED WITH mysql_native_password BY '<strong_password>',         'zbx_web'@'%' IDENTIFIED WITH mysql_native_password BY '<strong_password>'      REQUIRE SSL         PASSWORD HISTORY 5;       mysql> CREATE ROLE 'zbx_srv_role', 'zbx_web_role';       mysql> GRANT SELECT, UPDATE, DELETE, INSERT, CREATE, DROP, ALTER, INDEX, REFERENCES ON zabbix.* TO 'zbx_srv_role';      mysql> GRANT SELECT, UPDATE, DELETE, INSERT ON zabbix.* TO 'zbx_web_role';       mysql> GRANT 'zbx_srv_role' TO 'zbx_srv'@'%';      mysql> GRANT 'zbx_web_role' TO 'zbx_web'@'%';       mysql> SET DEFAULT ROLE 'zbx_srv_role' TO 'zbx_srv'@'%';      mysql> SET DEFAULT ROLE 'zbx_web_role' TO 'zbx_web'@'%';  Note, that the X.509 protocol is not used to check identity, but the user is configured to use only encrypted connections. See [MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/create-user.html#create-user-tls) for more details about configuring users.  Run to check connection (socket connection cannot be used to test secure connections):      $ mysql -u zbx_srv -p -h 10.211.55.9 --ssl-mode=REQUIRED   Check current status and available cipher suites:      mysql> status     --------------     mysql Ver 8.0.21 for Linux on x86_64 (MySQL Community Server - GPL)      Connection id: 62     Current database:     Current user: zbx_srv@bfdb.local     SSL: Cipher in use is TLS_AES_256_GCM_SHA384       mysql> SHOW SESSION STATUS LIKE 'Ssl_cipher_list'\G;     *************************** 1. row ***************************     Variable_name: Ssl_cipher_list     Value: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_128_CCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:DHE-RSA-AES128-SHA256:DHE-DSS-AES128-SHA256:DHE-DSS-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-DSS-AES128-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES256-SHA:CAMELLIA256-SHA:CAMELLIA128-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA     1 row in set (0.00 sec)      ERROR:     No query specified
zh-cn	#### MySQL 配置  当前版本数据库的加密模式已经可以开箱即用 [encryption mode](/manual/appendix/install/db_encrypt#terminology). 将在初始设置及启动后创建服务器端证书.  为主要组件创建用户和角色：       mysql> CREATE USER         'zbx_srv'@'%' IDENTIFIED WITH mysql_native_password BY '<strong_password>',         'zbx_web'@'%' IDENTIFIED WITH mysql_native_password BY '<strong_password>'      REQUIRE SSL         PASSWORD HISTORY 5;       mysql> CREATE ROLE 'zbx_srv_role', 'zbx_web_role';       mysql> GRANT SELECT, UPDATE, DELETE, INSERT, CREATE, DROP, ALTER, INDEX, REFERENCES ON zabbix.* TO 'zbx_srv_role';      mysql> GRANT SELECT, UPDATE, DELETE, INSERT ON zabbix.* TO 'zbx_web_role';       mysql> GRANT 'zbx_srv_role' TO 'zbx_srv'@'%';      mysql> GRANT 'zbx_web_role' TO 'zbx_web'@'%';       mysql> SET DEFAULT ROLE 'zbx_srv_role' TO 'zbx_srv'@'%';      mysql> SET DEFAULT ROLE 'zbx_web_role' TO 'zbx_web'@'%';  注意, X.509 协议不检查标识, 但会将用户设置为仅使用加密连接。配置用户的更多详细信息请参阅MySQL文档 [MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/create-user.html#create-user-tls)。  运行如下命令以检查连接（socket连接不能用于安全连接测试）:      $ mysql -u zbx_srv -p -h 10.211.55.9 --ssl-mode=REQUIRED   检查当前状态和可用的密码套件:      mysql> status     --------------     mysql Ver 8.0.21 for Linux on x86_64 (MySQL Community Server - GPL)      Connection id: 62     Current database:     Current user: zbx_srv@bfdb.local     SSL: Cipher in use is TLS_AES_256_GCM_SHA384       mysql> SHOW SESSION STATUS LIKE 'Ssl_cipher_list'\G;     *************************** 1. row ***************************     Variable_name: Ssl_cipher_list     Value: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_128_CCM_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:DHE-RSA-AES128-SHA256:DHE-DSS-AES128-SHA256:DHE-DSS-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-DSS-AES128-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES256-SHA:CAMELLIA256-SHA:CAMELLIA128-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA     1 row in set (0.00 sec)      ERROR:     No query specified

en-us	#### MySQL  -   CR\_CONN\_HOST\_ERROR -   CR\_SERVER\_GONE\_ERROR -   CR\_CONNECTION\_ERROR -   CR\_SERVER\_LOST -   CR\_UNKNOWN\_HOST -   ER\_SERVER\_SHUTDOWN -   ER\_ACCESS\_DENIED\_ERROR -   ER\_ILLEGAL\_GRANT\_FOR\_TABLE -   ER\_TABLEACCESS\_DENIED\_ERROR -   ER\_UNKNOWN\_ERROR
zh-cn	#### MySQL  -   CR\_CONN\_HOST\_ERROR -   CR\_SERVER\_GONE\_ERROR -   CR\_CONNECTION\_ERROR -   CR\_SERVER\_LOST -   CR\_UNKNOWN\_HOST -   ER\_SERVER\_SHUTDOWN -   ER\_ACCESS\_DENIED\_ERROR -   ER\_ILLEGAL\_GRANT\_FOR\_TABLE -   ER\_TABLEACCESS\_DENIED\_ERROR -   ER\_UNKNOWN\_ERROR

en-us	### MySQL  Export and import must be performed in tmux/screen to ensure that the session isn't dropped.  See also: [Important notes](#important-notes)
zh-cn	### MySQL  导出和导入必须在 tmux/screen 中执行，以确保会话不会被丢弃。  另请参阅：[重要说明](#important-notes)

en-us	#### MySQL  If a value contains a non-ASCII character in non UTF8 encoding - this character and the following will be discarded when the database stores this value. No warning messages will be written to the *zabbix\_server.log*.\ Relevant for at least MySQL version 5.1.61
zh-cn	#### MySQL  如果一个值在非UTF8编码中包含非ascii字符，那么当数据库存储此值时，该字符及该字符后的值将被丢弃。没有警告信息写入 *zabbix\_server.log*.   Relevant for at least MySQL version 5.1.61

en-us	## NAME  zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC}

en-us	## NAME  zabbix\_agentd - Zabbix agent daemon [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_agentd - Zabbix agent 守护进程 [ ]{#lbAC}

en-us	## NAME  zabbix\_get - Zabbix get utility [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_get - Zabbix get 实用程序 [ ]{#lbAC}

en-us	## NAME  zabbix\_js - Zabbix JS utility [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_js - Zabbix JS 实用程序 [ ]{#lbAC}

en-us	## NAME  zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_proxy - Zabbix proxy 守护进程 [ ]{#lbAC}

en-us	## NAME  zabbix\_sender - Zabbix sender utility [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_sender - Zabbix sender 实用程序 [ ]{#lbAC}

en-us	## NAME  zabbix\_server - Zabbix server daemon [ ]{#lbAC}
zh-cn	 ## 名字  zabbix\_server - Zabbix server 守护进程 [ ]{#lbAC}

en-us	## NAME  zabbix\_web\_service - Zabbix web service [ ]{#lbAC}
zh-cn	## 名称  zabbix\_web\_service - Zabbix web 服务 [ ]{#lbAC}

en-us	##### Naming and location of persistent files  Zabbix agent distinguishes active checks by their keys. For example, logrt\[/home/zabbix/test.log\] and logrt\[/home/zabbix/test.log,\] are different items.  Modifying the item logrt\[/home/zabbix/test.log,,,10\] in frontend to logrt\[/home/zabbix/test.log,,,20\] will result in deleting the item logrt[/home/zabbix/test.log,,,10] from the agent's list of active checks and creating logrt\[/home/zabbix/test.log,,,20\] item \(some attributes are carried across modification in frontend/server, not in agent\).  The file name is composed of MD5 sum of item key with item key length appended to reduce possibility of collisions.  For example, the state of logrt\[/home/zabbix50/test.log,,,,,,,,/home/zabbix50/agent_private\] item will be kept in persistent file c963ade4008054813bbc0a650bb8e09266.  Multiple log items can use the same value of **persistent\_dir**.  **persistent\_dir** is specified by taking into account specific file system layouts, mount points and mount options and storage mirroring configuration - the persistent file should be on the same mirrored filesystem as the monitored log file.  If **persistent\_dir** directory cannot be created or does not exist, or access rights for Zabbix agent does not allow to create/write/read/delete files the log item becomes NOTSUPPORTED.
zh-cn	##### 持久文件的命名和位置 Zabbix agent 通过他们的键来区分活动检查。例如：logrt\[/home/zabbix/test.log\] 和 logrt\[/home/zabbix/test.log,\] 是不同的监控项。将前端的项logrt\[/home/zabbix/test.log,,,10\]修改为 logrt\[/home/zabbix/test.log,,,20\] 会导致 logrt[/home/zabbix/test.log,,,10]项从代理的活动检查清单中删除并创建logrt\[/home/zabbix/test.log,,,20\] 监控项 \(某些属性在前端/服务器中进行修改，而不是在代理中\)。  文件名由监控项密钥的 MD5 和加上监控项密钥长度组成，以减少冲突的可能性。例如， logrt\[/home/zabbix50/test.log,,,,,,,,/home/zabbix50/agent_private\] 监控项的状态将保存在持久文件c963ade4008054813bbc0a650bb8e09266中。  多个日志项可以使用相同的值 **persistent\_dir**。  **persistent\_dir** 是通过考虑特定文件系统布局、挂载点和挂载选项以及存储镜像配置来指定的 - 持久文件应该与受监控的日志文件位于同一镜像文件系统上。  如果 **persistent\_dir** 目录无法创建或不存在，或者Zabbix agent 的访问权限不允许创建/写入/读取/删除文件，则日志项将变为 NOTSUPPORTED。

en-us	#### Negative problem duration  It is actually possible in some common situations to have negative problem duration i.e. when the problem resolution time is earlier than problem creation time, e. g.:  -   If some host is monitored by proxy and a network error happens,     leading to no data received from the proxy for a while, the     nodata(/host/key) trigger will be fired by the server. When the     connection is restored, the server will receive item data from the     proxy having a time from the past. Then, the nodata(/host/key)     problem will be resolved and it will have a negative problem     duration; -   When item data that resolve the problem event are sent by Zabbix     sender and contain a timestamp earlier than the problem creation     time, a negative problem duration will also be displayed.  ::: noteclassic Negative problem duration is not affecting [SLA calculation](/manual/it_services) or [Availability report](/manual/web_interface/frontend_sections/reports/availability) of a particular trigger in any way; it neither reduces nor expands problem time. :::
zh-cn	#### 问题持续时间为负 在某些常见情况下，可能会出现持续时间为负数，即问题解决时间早于问题创建时间时，例如：  - · 如果某个主机被代理监视并且发生了网络错误，导致在一段时间内没有接收到来自代理的数据，则服务器将触发 nodata(/host/key)触发器。当连接恢复时，服务器将从具有过去时间的代理接收项目数据。然后，nodata (/host/key)问题将被解决，并且会出现问题持续时间为负数。 - · 当恢复问题事件的监控项数据由 Zabbix Sender发送并且数据时间戳早于问题创建时间，也将显示问题持续时间为负数。  ::: noteclassic 问题持续时间为负数，不会影响 [SLA 计算](/manual/it_services) 或特定触发器的 [可用性报告](/manual/web_interface/frontend_sections/reports/availability) ；它既不会减少也不会延长问题时间。  :::

en-us	#### NetBSD 8.0 and newer  Various Zabbix processes may randomly crash on startup on the NetBSD versions 8.X and 9.X. That is due to the too small default stack size (4MB), which must be increased by running:      ulimit -s 10240  For more information, please see the related problem report: [ZBX-18275](https://support.zabbix.com/browse/ZBX-18275).
zh-cn	#### NetBSD 8.0 及更新版本  在 NetBSD 8.X 和 9.X 上， Zabbix 各种进程可能会在启动时随机崩溃。这是由于默认堆栈大小（4MB）太小，需要执行以下命令来增加：      ulimit -s 10240  点击 [ZBX-18275](https://support.zabbix.com/browse/ZBX-18275) 查看相关问题报告。

en-us	#### Network discovery  In a [network discovery rule](/manual/discovery/network_discovery/rule), user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Update interval|<|no| |*SNMP v1, v2*|<|<| | |SNMP community|yes| |^|SNMP OID|yes| |*SNMP v3*|<|<| | |Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |^|SNMP OID|yes|
zh-cn	#### 网络发现  在 [网络发现规则](/manual/discovery/network_discovery/rule)中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |更新间隔|<|不支持| |*SNMP v1, v2*|<|<| | |SNMP 团体名|支持| |^|SNMP OID|支持| |*SNMP v3*|<|<| | |上下文名称|支持| |^|安全名称|支持| |^|身份验证密码|支持| |^|隐私密码|支持| |^|SNMP OID|支持|

en-us	#### Network discovery  Manage network-level discovery rules to automatically find and monitor new hosts. Gain full access to information about discovered services and hosts.  [Discovery rule API](/manual/api/reference/drule) | [Discovery check API](/manual/api/reference/dcheck) | [Discovered host API](/manual/api/reference/dhost) | [Discovered service API](/manual/api/reference/dservice)
zh-cn	#### 网络发现  管理网络级发现规则以自动查找和监控新主机。获得对所发现的服务和主机的信息的完全访问。  [Discovery rule API](/manual/api/reference/drule) | [Discovery check API](/manual/api/reference/dcheck) | [Discovered host API](/manual/api/reference/dhost) | [Discovered service API](/manual/api/reference/dservice)

en-us	##### Non-primitive data types  Since Zabbix 4.0.0 it is possible to work with custom MBeans returning non-primitive data types, which override the **toString()** method.
zh-cn	##### 非基本数据类型  从 Zabbix 4.0.0 开始，可以使用返回的自定义 MBean 覆盖 **toString()** 方法的非基本数据类型。

en-us	### Notation
zh-cn	 ### 注释

en-us	 ::: noteclassic If installing from [Zabbix Git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), you need to run the following command prior to proceeding to the next steps: <br><br> `$ make dbschema` :::
zh-cn	::: noteclassic 如果从 [Zabbix Git 存储库](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse) 安装 Zabbix，在进行下一步操作之前需要执行以下命令： <br><br> `$ make dbschema` :::

en-us	##### Notes on connection termination  If IPMI checks are not performed (by any reason: all host IPMI items disabled/notsupported, host disabled/deleted, host in maintenance etc.) the IPMI connection will be terminated from Zabbix server or proxy in 3 to 4 hours depending on the time when Zabbix server/proxy was started.
zh-cn	 ##### 连接终止注意事项  如果不执行IPMI检查（由于任何原因：所有主机IPMI监控项禁用/不支持、主机已禁用/已删除、主机维护等），IPMI连接将从Zabbix server 或  proxy  终止3到4小时，具体时间取决于Zabbix server/proxy 何时启动。

en-us	##### Notes on discrete sensor names in OpenIPMI-2.0.16, 2.0.17, 2.0.18 and 2.0.19  Names of discrete sensors in OpenIPMI-2.0.16, 2.0.17 and 2.0.18 often have an additional "`0`" (or some other digit or letter) appended at the end. For example, while `ipmitool` and OpenIPMI-2.0.19 display sensor names as "`PhysicalSecurity`" or "`CATERR`", in OpenIPMI-2.0.16, 2.0.17 and 2.0.18 the names are "`PhysicalSecurity0`" or "`CATERR0`", respectively.  When configuring an IPMI item with Zabbix server using OpenIPMI-2.0.16, 2.0.17 and 2.0.18, use these names ending with "0" in the *IPMI sensor* field of IPMI agent items. When your Zabbix server is upgraded to a new Linux distribution, which uses OpenIPMI-2.0.19 (or later), items with these IPMI discrete sensors will become "NOT SUPPORTED". You have to change their *IPMI sensor* names (remove the '0' in the end) and wait for some time before they turn "Enabled" again.
zh-cn	##### 关于OpenIPMI-2.0.16,2.0.17,2.0.18和2.0.19中离散传感器名称的注释  OpenIPMI-2.0.16,2.0.17和2.0.18中的离散传感器的名称通常在附近附加一个额外的 "`0`" （或其它数字或字母）。例如，当 `ipmitool` 和OpenIPMI-2.0.19将传感器名称显示为 "`PhysicalSecurity`" 或 "`CATERR`"时，在OpenIPMI-2.0.16,2.0.17和2.0.18中，名称分别为 "`PhysicalSecurity0`" 或 "`CATERR0`"。  当使用OpenIPMI-2.0.16, 2.0.17和2.0.18配置 IPMI 监控项时，请在IPMI代理监控项的*IPMI 传感器*字段中使用以“0”结尾的名称。当你的Zabbix服务器升级到使用OpenIPMI-2.0.19（或更高版本）的新Linux发行版时，具有这些IPMI离散传感器的监控项将变为“不支持”。你必须更改其*IPMI 传感器*名称（最后删除“0”），并等待一段时间才能再次转为"Enabled"。

en-us	#### Notes on handling 'copytruncate' log file rotation  `logrt` with the `copytruncate` option assumes that different log files have different records (at least their timestamps are different), therefore MD5 sums of initial blocks (up to the first 512 bytes) will be different. Two files with the same MD5 sums of initial blocks means that one of them is the original, another - a copy.  `logrt` with the `copytruncate` option makes effort to correctly process log file copies without reporting duplicates. However, things like producing multiple log file copies with the same timestamp, log file rotation more often than logrt\[\] item update interval, frequent restarting of agent are not recommended. The agent tries to handle all these situations reasonably well, but good results cannot be guaranteed in all circumstances.
zh-cn	#### 处理“copytruncate”日志文件轮换的注意事项  带有`copytruncate` 选项的`logrt`假定不同的日志文件有不同的记录(至少它们的时间戳不同)，因此初始块的MD5(最多512字节)将不同。两个具有相同的MD5初始块和的文件意味着其中一个是原始块，另一个是副本。  使用`copytruncate`选项的`logrt`将努力正确处理日志文件副本，而不报告副本。但是，与logrt\[\]监控项更新间隔相比，生成具有相同时间戳的多个日志文件副本、日志文件轮询频率更高、不建议频繁重新启动代理。代理试图合理地处理所有这些情况，但是在所有情况下都不能保证良好的结果。

en-us	#### Notes on inclusion  If the `Include` parameter is used for including a file, the file must be readable.  If the `Include` parameter is used for including a directory:  - All files in the directory must be readable. - No particular order of inclusion should be assumed (e.g. files are not included in alphabetical order). Therefore do not define one parameter in several ''Include'' files (e.g. to override a general setting with a specific one). - All files in the directory are included into configuration. - Beware of file backup copies automatically created by some text editors. For example, if editing the ''include/my_specific.conf'' file produces a backup copy ''include/my_specific_conf.BAK'' then both files will be included. Move ''include/my_specific.conf.BAK'' out of the "Include" directory. On Linux, contents of the ''Include'' directory can be checked with a ''ls -al'' command for unnecessary files.  If the `Include` parameter is used for including files using a pattern:  - All files matching the pattern must be readable. - No particular order of inclusion should be assumed (e.g. files are not included in alphabetical order). Therefore do not define one parameter in several ''Include'' files (e.g. to override a general setting with a specific one).
zh-cn	#### 关于包含的说明  如果`Include`参数用于包含文件，则该文件必须要可读。  如果 `Include`参数用于包含目录：  - 目录中的所有文件必须要可读。 - 不应假定特定的包含顺序（例如，文件不按字母顺序包含）。因此，不要在多个“Include”文件中定义一个参数（例如，用特定参数覆盖常规设置）。 - 目录中的所有文件都包含在配置中。 - 小心一些文本编辑器自动创建的文件备份副本。例如，如果编辑“include/my_specific.conf“文件生成一个备份副本“include/my_specific_conf.BAK”，那么两个文件都会被包含。将“include/my_specific_conf.BAK”文件从“Include”目录中删除。 在Linux中, 可以使用“ls -al”命令检查“Include”目录的内容，以查找不必要的文件。  如果 `Include`参数用于包含使用模式匹配的文件：  - 所有匹配到的文件必须要可读 - 不应假定特定的包含顺序（例如，文件不按字母顺序包含）。因此，不要在多个“Include”文件中定义一个参数（例如，用特定参数覆盖常规设置）。

en-us	#### Notes on IPMI discrete sensors  To find sensors on a host start Zabbix server with **DebugLevel=4** enabled. Wait a few minutes and find sensor discovery records in Zabbix server logfile:      $ grep 'Added sensor' zabbix_server.log     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR'     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp'     8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH'  To decode IPMI sensor types and states, get a copy of IPMI 2.0 specifications at <http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html> (At the time of writing the newest document was <http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf>)  The first parameter to start with is "reading\_type". Use "Table 42-1, Event/Reading Type Code Ranges" from the specifications to decode "reading\_type" code. Most of the sensors in our example have "reading\_type:0x1" which means "threshold" sensor. "Table 42-3, Sensor Type Codes" shows that "type:0x1" means temperature sensor, "type:0x2" - voltage sensor, "type:0x4" - Fan etc. Threshold sensors sometimes are called "analog" sensors as they measure continuous parameters like temperature, voltage, revolutions per minute.  Another example - a sensor with "reading\_type:0x3". "Table 42-1, Event/Reading Type Code Ranges" says that reading type codes 02h-0Ch mean "Generic Discrete" sensor. Discrete sensors have up to 15 possible states (in other words - up to 15 meaningful bits). For example, for sensor 'CATERR' with "type:0x7" the "Table 42-3, Sensor Type Codes" shows that this type means "Processor" and the meaning of individual bits is: 00h (the least significant bit) - IERR, 01h - Thermal Trip etc.  There are few sensors with "reading\_type:0x6f" in our example. For these sensors the "Table 42-1, Event/Reading Type Code Ranges" advises to use "Table 42-3, Sensor Type Codes" for decoding meanings of bits. For example, sensor 'Power Unit Stat' has type "type:0x9" which means "Power Unit". Offset 00h means "PowerOff/Power Down". In other words if the least significant bit is 1, then server is powered off. To test this bit, the **bitand** [function](/manual/appendix/functions) with mask '1' can be used. The trigger expression could be like      bitand(last(/www.example.com/Power Unit Stat,#1),1)=1  to warn about a server power off.
zh-cn	#### 关于 IPMI 离散传感器的注意事项  要在主机上找到传感器记录需要在启动Zabbix服务器上配置 **DebugLevel=4**。等待几分钟，并在Zabbix服务器日志文件中查找传感器发现记录:      $ grep 'Added sensor' zabbix_server.log     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR'     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp'     8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH'  要解码 IPMI 传感器类型和状态请在<http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html> 获取 IPMI 2.0 规范的副本 (在撰写本文时最新的文件是<http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf>)。  开始的第一个参数是“reading\_type”。 使用规范中的“Table 42-1，事件/读数类型代码范围”来解码“reading\_type”代码。 我们示例中的大多数传感器都有“reading\_type:0x1”，这意味着“阈值”传感器。 “Table 42-3，传感器类型代码”显示“类型：0x1”表示温度传感器，“类型：0x2” - 电压传感器，“类型：0x4” - 风扇等。阈值传感器有时被称为“模拟”传感器，因为它们测量连续参数，如温度、电压、每分钟转数。  另一个例子——带有“reading\_type:0x3”的传感器。 “Table 42-1，事件/读取类型代码范围”表示读取类型代码 02h-0Ch 表示“通用离散”传感器。 离散传感器有多达 15 种可能的状态（换句话说 - 多达 15 个有意义的位）。 例如，对于“类型：0x7”的传感器“CATERR”，“Table 42-3，传感器类型代码”显示此类型表示“处理器”，各个位的含义为：00h（最低有效位）- IERR , 01h - 热跳闸等  在我们的示例中，几乎没有带有“reading\_type:0x6f”的传感器。 对于这些传感器，“Table 42-1，事件/读数类型代码范围”建议使用“Table 42-3，传感器类型代码”来解码位的含义。 例如，传感器“Power Unit Stat”的类型为“type:0x9”，意思是“Power Unit”。 偏移量 00h 表示“PowerOff/Power Down”。 换句话说，如果最低有效位为 1，则服务器关闭。 要测试该位，可以使用掩码为“1”的 **bitand** [function](/manual/appendix/functions)。 触发表达式可能像：      bitand(last(/www.example.com/Power Unit Stat,#1),1)=1  to warn about a server power off.

en-us	##### Notes on threshold and discrete sensor simultaneous availability  Some IPMI agents provide both a threshold sensor and a discrete sensor under the same name. In Zabbix versions prior to 2.2.8 and 2.4.3, the first provided sensor was chosen. Since versions 2.2.8 and 2.4.3, preference is always given to the threshold sensor.
zh-cn	 ##### 关于阈值和离散传感器同时可用的注意事项  一些 IPMI Agent 提供了相同名称的阈值传感器和离散传感器。在2.2.8和2.4.3之前的Zabbix版本中，选择了第一个提供的传感器。从2.2.8和2.4.3版本以后，偏向于阈值传感器。

en-us	 ::: notetip After enabling a trigger (changing its configuration status from *Disabled* to *Enabled*), the trigger expression is evaluated as soon as an item in it receives a value or the time to handle a time-based function comes. :::
zh-cn	 ::: notetip 启用触发器后（将其配置状态从 *禁用* 更改为 *启用*），触发器表达式会在其中的监控项收到值或处理基于时间的函数的时间到来时立即求值。 :::

en-us	#### Numeric representation  Windows maintains numeric representations (indexes) for object and performance counter names. Zabbix supports these numeric representations as parameters to the `perf_counter`, `perf_counter_en` item keys and in `PerfCounter`, `PerfCounterEn` configuration parameters.  However, it's not recommended to use them unless you can guarantee your numeric indexes map to correct strings on specific hosts. If you need to create portable items that work across different hosts with various localized Windows versions, you can use the `perf_counter_en` key or `PerfCounterEn` configuration parameter which allow to use English names regardless of system locale.  To find out the numeric equivalents, run **regedit**, then find *HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*.  The registry entry contains information like this:      1     1847     2     System     4     Memory     6     % Processor Time     10     File Read Operations/sec     12     File Write Operations/sec     14     File Control Operations/sec     16     File Read Bytes/sec     18     File Write Bytes/sec     ....  Here you can find the corresponding numbers for each string part of the performance counter, like in '\\System\\% Processor Time':      System → 2     % Processor Time → 6  Then you can use these numbers to represent the path in numbers:      \2\6
zh-cn	#### 数字表示  由于性能计数器的命名在不同的Windows服务器上可能不同，这取决于服务器的地区设置。因此，在创建用于监控具有不同地区设置的多台Windows设备的模板时，会引发一定的问题。\  同时，每个新能计数器也可以通过其数字形式来引用，无论如何，数字形式都是唯一的，因此你可以使用数字表示而不是字符串。\  为了找到同义的数字，需要运行 **regedit**，然后找到*HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*这个注册表。\  注册表中包含形如下面所示的信息：       · 1      · 1847      · 2      · System      · 4      · Memory      · 6      · % Processor Time      · 10      · File Read Operations/sec      · 12      · File Write Operations/sec      · 14      · File Control Operations/sec      · 16      · File Read Bytes/sec      · 18      · File Write Bytes/sec      · ....  这样你就可以找到性能计数器每个字符串对应的数字，例如：       · System → 2      · % Processor Time → 6  然后你就可以使用这些数字来表示性能计数器路径：       · \2\6

en-us	#### Obtaining sensor names  Sensor labels, as printed by the *sensors* command, cannot always be used directly because the naming of labels may be different for each sensor chip vendor. For example, *sensors* output might contain the following lines:      $ sensors     in0:         +2.24 V  (min =  +0.00 V, max =  +3.32 V)        Vcore:       +1.15 V  (min =  +0.00 V, max =  +2.99 V)        +3.3V:       +3.30 V  (min =  +2.97 V, max =  +3.63 V)        +12V:       +13.00 V  (min =  +0.00 V, max = +15.94 V)     M/B Temp:    +30.0°C  (low  = -127.0°C, high = +127.0°C)  Out of these, only one label may be used directly:      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in0]     2.240000  Attempting to use other labels (like *Vcore* or *+12V*) will not work.      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,Vcore]     ZBX_NOTSUPPORTED  To find out the actual sensor name, which can be used by Zabbix to retrieve the sensor readings, run *sensors -u*. In the output, the following may be observed:      $ sensors -u     ...     Vcore:       in1_input: 1.15       in1_min: 0.00       in1_max: 2.99       in1_alarm: 0.00     ...         +12V:       in4_input: 13.00       in4_min: 0.00       in4_max: 15.94       in4_alarm: 0.00     ...  So *Vcore* should be queried as *in1*, and *+12V* should be queried as *in4*.[^1]      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in1]     1.301000  Not only voltage (in), but also current (curr), temperature (temp) and fan speed (fan) readings can be retrieved by Zabbix.  [^1]: According to     [specification](https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface)     these are voltages on chip pins and generally speaking may need     scaling.
zh-cn	 #### 获取传感器的名字  传感器标签，由 sensors 命令打印，不能总是被直接使用，因为标签的命名对于每个传感器芯片供应商来说可能是不同的。 例如,   sensors  输出可能包含以下几行:      $ sensors     in0:         +2.24 V  (min =  +0.00 V, max =  +3.32 V)        Vcore:       +1.15 V  (min =  +0.00 V, max =  +2.99 V)        +3.3V:       +3.30 V  (min =  +2.97 V, max =  +3.63 V)        +12V:       +13.00 V  (min =  +0.00 V, max = +15.94 V)     M/B Temp:    +30.0°C  (low  = -127.0°C, high = +127.0°C)  在这些情况下，只有一个标签可以直接使用:      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in0]     2.240000  尝试使用其他标签 (像   Vcore   或   +12V ) 是不会起作用的。      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,Vcore]     ZBX_NOTSUPPORTED  为了找到实际的Zabbix可以使用它来检索读数的传感器名称，运行   sensors -u 命令。 在输出中，可以看到到以下内容:      $ sensors -u     ...     Vcore:       in1_input: 1.15       in1_min: 0.00       in1_max: 2.99       in1_alarm: 0.00     ...         +12V:       in4_input: 13.00       in4_min: 0.00       in4_max: 15.94       in4_alarm: 0.00     ...  所有 Vcore  应该检索   in1 , +12V  应该检索  in4.[1]      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in1]     1.301000  不止 电压 (in), 还有 电流 (curr), 温度 (temp) 和 风扇转速 (fan) 的读数都可以被Zabbix 检索到。  [^1]:  根据  [声明](https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface)  这些是芯片引脚上的电压，一般来说可能需要缩放。

en-us	#### Older XML protocol  ::: noteclassic Zabbix will take up to 16 MB of XML Base64-encoded data, but a single decoded value should be no longer than 64 KB otherwise it will be truncated to 64 KB while decoding. :::
zh-cn	#### 较旧的 XML 协议  ::: noteclassic Zabbix将占用16 MB的XML base64编码的数据, 但单个解码值应该不超过64kb，否则，在解码时将被截断到64 KB。 :::

en-us	#### One side connects with certificate but other side accepts only PSK or vice versa  In any log (with *GnuTLS*):      failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\         -21 Could not negotiate a supported cipher suite.  In any log (with *OpenSSL* 1.0.2c):      failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\         file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\         TLS write fatal alert "handshake failure"
zh-cn	#### 一端使用证书连接，但另一端仅接受 PSK，反之亦然  在任意日志当中有如下显示 (对于 *GnuTLS*)：      failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\         -21 Could not negotiate a supported cipher suite.  在任意日志当中有如下显示 (对于 *OpenSSL* 1.0.2c)：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\         file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\         TLS write fatal alert "handshake failure"

en-us	#### One side connects with PSK but other side uses LibreSSL or has been compiled without encryption support  LibreSSL does not support PSK.  In connecting-side log:      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success  In accepting-side log:      ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in  In Zabbix frontend:      Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success
zh-cn	#### 一端使用 PSK 连接，但另一端使用 LibreSSL 或已编译为无加密支持  LibreSSL 不支持 PSK。  在发起连接端的日志中有如下显示：      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success  在接受连接端的日志中：      ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in  在Zabbix前端有如下显示：      Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success

en-us	#### One side connects with PSK but other side uses OpenSSL with PSK support disabled  In connecting-side log:      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure"  In accepting-side log:      ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure"
zh-cn	#### 一端使用 PSK 连接，但另一端使用禁用 PSK 支持的 OpenSSL  在发起连接端的日志中有如下显示：      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure"  在接受连接端的日志中有如下显示：      ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure"

en-us	##### On Linux 2.4:  (Sensor readings are obtained from /proc/sys/dev/sensors directory)  -   **device** - device name (if <mode> is used, it is a regular     expression); -   **sensor** - sensor name (if <mode> is used, it is a regular     expression); -   **mode** - possible values: avg, max, min (if this parameter is     omitted, device and sensor are treated verbatim).  Example key: sensor\[w83781d-i2c-0-2d,temp1\]  Prior to Zabbix 1.8.4, the sensor\[temp1\] format was used.
zh-cn	##### 当 Linux 2.4:  (传感器读数从/proc/sys/dev/sensor目录获得)  -   **device**  - 设备名字 (如果使用了<mode>， 则是正则表达式); -   **sensor**  - 传感器名字 (如果使用了<mode>， 则是正则表达式); -   **mode**  - 可能的值: avg, max, min (如果忽略了这个参数，设备和传感器将逐字处理)。  例子: sensor[w83781d-i2c-0-2d,temp1]  在Zabbix 1.8.4之前，使用了sensor[temp1]格式。

en-us	##### On Linux 2.6+:  (Sensor readings are obtained from /sys/class/hwmon directory)  -   **device** - device name (non regular expression). The device name     could be the actual name of the device (e.g 0000:00:18.3) or the     name acquired using sensors program (e.g. k8temp-pci-00c3). It is up     to the user to choose which name to use; -   **sensor** - sensor name (non regular expression); -   **mode** - possible values: avg, max, min (if this parameter is     omitted, device and sensor are treated verbatim).  Example key:  sensor\[k8temp-pci-00c3,temp,max\] or sensor\[0000:00:18.3,temp1\]  sensor\[smsc47b397-isa-0880,in,avg\] or sensor\[smsc47b397.2176,in1\]
zh-cn	##### 当 Linux 2.6+: (传感器读数从/sys/class/hwmon目录获得)  -   **device**  - 设备名称(非正则表达式)。 设备名称可以是设备的实际名称(e.g 0000:00:18.3)或使用传感器程序获取得的名称(例如:k8temp-pci-00c3)，这由用户决定使用哪个名称; -   **sensor**  - 传感器名称(非正则表达式); -   **mode**  - 可能的值: avg, max, min (如果忽略了这个参数，设备和传感器将逐字处理)。  例如:  sensor[k8temp-pci-00c3,temp, max] 或 sensor[0000:00:18.3,temp1]  sensor[smsc47b397-isa-0880,in, avg] 或 sensor[smsc47b397.2176,in1]

en-us	#### OpenSSL used with CRLs and for some CA in the certificate chain its CRL is not included in `TLSCRLFile`  In TLS server log in case of *OpenSSL* peer:      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \         TLS write fatal alert "unknown CA"  In TLS server log in case of *GnuTLS* peer:      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\         block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin
zh-cn	#### OpenSSL 与 CRL 一起使用，对于证书链中的某些 CA，其 CRL 不包括在 "TLSCRLFile" 中  在 *OpenSSL* 对端的情况下，在 TLS 服务器日志中，会有如下显示：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \         TLS write fatal alert "unknown CA"  在 *GnuTLS* 对端的情况下，在 TLS 服务器日志中，会有如下显示：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\         block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix agent in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
zh-cn	 ## 选项  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-f**, **--foreground**   在前台运行Zabbix agent。  **-R**, **--runtime-control** *runtime-option*   根据*runtime-option*执行管理功能。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix proxy in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
zh-cn	 ## OPTIONS  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-f**, **--foreground**   在前台运行Zabbix proxy。  **-R**, **--runtime-control** *runtime-option*   根据*runtime-option*执行管理功能。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
zh-cn	## 选项  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.
zh-cn	 ## 选项  **-c**, **--config** *config-file*   使用指定的 *配置文件*而不是默认文件。  **-R**, **--runtime-control** *runtime-option*   根据 *运行时选项* 执行管理功能。

en-us	 #### Options  |Parameter|Description| |---------|-----------| |-V --version|Print the plugin version and license information.| |-h --help|Print help information (shorthand).|
zh-cn	#### 选项  |参数|描述| |---------|-----------| |-V --version|打印插件版本及license信息。| |-h --help|打印帮助信息（简化版）。|

en-us	## OPTIONS  **-s**, **--host** *host-name-or-IP*   Specify host name or IP address of a host.  **-p**, **--port** *port-number*   Specify port number of agent running on the host. Default is 10050.  **-I**, **--source-address** *IP-address*   Specify source IP address.  **-t**, **--timeout** *seconds*   Specify timeout. Valid range: 1-30 seconds (default: 30)  **-k**, **--key** *item-key*   Specify key of item to retrieve value for.  **--tls-connect** *value*   How to connect to agent. Values:  [ ]{#lbAF}
zh-cn	 ## 选项  **-s**, **--host** *host-name-or-IP*   指定主机的主机名或IP地址。  **-p**, **--port** *port-number*   指定主机上运行的agent的端口号。默认值为10050。  **-I**, **--source-address** *IP-address*   指定源IP地址。  **-t**, **--timeout** *seconds*   指定超时。有效范围：1-30秒（默认值：30）  **-k**, **--key** *item-key*   指定要为其检索值的项的key。  **--tls-connect** *value*   如何连接到agent。值  [ ]{#lbAF}

en-us	## OPTIONS  **-s**, **--script** *script-file*   Specify the file name of the script to execute. If '-' is specified as file name, the script will be read from stdin.  **-p**, **--param** *input-param*   Specify the input parameter.  **-i**, **--input** *input-file*   Specify the file name of the input parameter. If '-' is specified as file name, the input will be read from stdin.  **-l**, **--loglevel** *log-level*   Specify the log level.  **-t**, **--timeout** *timeout*   Specify the timeout in seconds. Valid range: 1\-60 seconds (default: 10)  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
zh-cn	## OPTIONS  **-s**, **--script** *script-file*   指定要执行的脚本的文件名。如果将“-”指定为文件名，则将从标准输入读取脚本。  **-p**, **--param** *input-param*   指定输入参数。  **-i**, **--input** *input-file*   指定输入参数的文件名。如果将“-”指定为文件名，则将从准输入读取输入。  **-l**, **--loglevel** *log-level*   指定日志级别。  **-t**, **--timeout** *timeout*   以秒为单位指定超时。有效范围：1\-60 秒（默认值：10）  **-h**, **--help**   显示此帮助并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAF}

en-us	 ### Oracle  Export and import must be performed in tmux/screen to ensure that the session isn't dropped. Zabbix server should be down during the upgrade.  See also: [Important notes](#important-notes)  #### Table upgrade  * Install Oracle Data Pump (available in the [Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html)).   See Oracle Data Pump [documentation](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for performance tips.  * Rename tables using `history_pk_prepare.sql`.  ``` {.bash} cd /usr/share/zabbix/zabbix-sql-scripts/database/oracle sqlplus zabbix/password@oracle_host/service sqlplus> @history_pk_prepare.sql ```
zh-cn	### Oracle  导出和导入必须在 tmux/screen 中执行，以确保会话不会被丢弃。Zabbix 服务器应该在升级期间关闭。  另请参阅：[重要说明](#important-notes)  #### 表升级  * 安装 Oracle 数据泵（在 [即时客户端工具包](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) 中可用）。  有关性能提示，请参阅 Oracle Data Pump [文档](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html)。  * 使用 `history_pk_prepare.sql` 重命名表。  ``` {.bash} cd /usr/share/zabbix/zabbix-sql-scripts/database/oracle sqlplus zabbix/password@oracle_host/service sqlplus> @history_pk_prepare.sql ```

en-us	#### Ordering shapes and lines  To bring one shape in front of the other (or vice versa) click on the shape with the right mouse button bringing up the map shape menu.  ![](../../../../../assets/en/manual/config/visualization/map_shape_menu.png)
zh-cn	#### 排序形状和线条  要将一个形状放在另一个形状前面（反之亦然），请用鼠标单击右键调出地图形状菜单。  ![](../../../../../assets/en/manual/config/visualization/map_shape_menu.png)

en-us	#### Other agent options  It is possible to run multiple instances of the agent on a host. A single instance can use the default configuration file or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).  The following command line parameters can be used with Zabbix agent:  |Parameter|Description| |--|--------| |**UNIX and Windows agent**|<| |-c --config <config-file>|Path to the configuration file.<br>You may use this option to specify a configuration file that is not the default one.<br>On UNIX, default is /usr/local/etc/zabbix\_agentd.conf or as set by [compile-time](/manual/installation/install#installing_zabbix_daemons) variables *--sysconfdir* or *--prefix*<br>On Windows, default is c:\\zabbix\_agentd.conf| |-p --print|Print known items and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-t --test <item key>|Test specified item and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-h --help|Display help information| |-V --version|Display version number| |**UNIX agent only**|<| |-R --runtime-control <option>|Perform administrative functions. See [runtime control](/manual/concepts/agent#runtime_control).| |**Windows agent only**|<| |-m --multiple-agents|Use multiple agent instances (with -i,-d,-s,-x functions).<br>To distinguish service names of instances, each service name will include the Hostname value from the specified configuration file.| |**Windows agent only (functions)**|<| |-i --install|Install Zabbix Windows agent as service| |-d --uninstall|Uninstall Zabbix Windows agent service| |-s --start|Start Zabbix Windows agent service| |-x --stop|Stop Zabbix Windows agent service|  Specific **examples** of using command line parameters:  -   printing all built-in agent items with values -   testing a user parameter with "mysql.ping" key defined in the     specified configuration file -   installing a "Zabbix Agent" service for Windows using the default     path to configuration file c:\\zabbix\_agentd.conf -   installing a "Zabbix Agent \[Hostname\]" service for Windows using     the configuration file zabbix\_agentd.conf located in the same     folder as agent executable and make the service name unique by     extending it by Hostname value from the config file  ```{=html} <!-- --> ```     shell> zabbix_agentd --print     shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf     shell> zabbix_agentd.exe -i     shell> zabbix_agentd.exe -i -m -c zabbix_agentd.conf
zh-cn	#### 其它 agent 选项  您可以在主机上运行单个或多个 Agent 实例。 单个实例可以使用默认配置文件或命令行中指定的配置文件。 如果是多个实例，则每个 Agent 程序实例必须具有自己的配置文件（其中一个实例可以使用默认配置文件）。  以下命令参数可以在 Zabbix agent 中使用：  |**参数**|**描述**| |-------------|---------------| |**UNIX and Windows agent**|<| |-c --config <config-file>|配置文件的绝对路径。您可以使用此选项来制定配置文件，而不是使用默认文件。在 UNIX 上，默认的配置文件是 /usr/local/etc/zabbix_agentd.conf 或 由编译时的 --sysconfdir 或 --prefix 变量来确定。在 Windows上, 默认的配置文件是 c:\\zabbix\_agentd.conf| |-p --print|输出已知的监控项并退出。  _注意_： 要返回 [用户自定义参数](https://www.zabbix.com/documentation/5.0/zh/manual/config/items/userparameters) 的结果，您必须指定配置文件（如果它不在默认路径下）。| |-t --test <item key>|测试指定的监控项并退出。  _注意_：要返回 [用户自定义参数](https://www.zabbix.com/documentation/5.0/zh/manual/config/items/userparameters) 的结果，您必须指定配置文件（如果它不在默认路径下）。| |-h --help| 显示帮助信息| |-V --version| 显示版本信息| |**仅 UNIX agent**|<| |-R --runtime-control <option>|执行管理功能。请参阅 [运行时机制的控制](https://www.zabbix.com/documentation/5.0/zh/manual/concepts/agent#runtime-control)。| |**仅 Windows agent**|<| |-m --multiple-agents|使用多个 Agent 实例（使用 -i、-d、-s、-x）。  为了区分实例的服务名称，每项服务名都会包涵来自配置文件里的 Hostname 值。| |** 仅 Windows agent （功能）**|<| |-i --install|以服务的形式安装 Zabbix Windows agent。| |-d --uninstall|卸载 Zabbix Windows agent 服务。| |-s --start|启动 Zabbix Windows agent 服务。| |-x --stop|停止 Zabbix Windows agent 服务。|  使用命令行参数的具体**示例**：  -   打印输出所有内置监控项和它们的值。 -   使用指定的配置文件中的“mysql.ping”键值来测试用户自定义参数。 -   在 Windows 下使用默认路径下的配置文件 c:\\zabbix\_agentd.conf 安装 Zabbix agent 服务。 -   使用位于与 agent 可执行文件同一文件夹中的配置文件 zabbix\_agentd.conf 为 Windows 安装“Zabbix Agent [Hostname]”服务，并通过从配置文件中的唯一 Hostname 值扩来为命名。  ```{=html} <!-- --> ```    shell> zabbix_agentd --print    shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf    shell> zabbix_agentd.exe -i    shell> zabbix_agentd.exe -i -m -c zabbix_agentd.conf

en-us	##### Other expressions  Function parameters may contain other expressions, as in the following syntax:      min(min(/host/key,1h),min(/host2/key2,1h)*10)  Note that other expressions may not be used, if the function references item history. For example, the following syntax is not allowed:  ~~`min(/host/key,#5*10)`~~
zh-cn	##### 其他表达式  函数参数可能包含其他表达式，如下所示 语法:      min(min(/host/key,1h),min(/host2/key2,1h)*10)  请注意，如果函数引用，则可能不会使用其他表达式 监控项历史。例如，不允许使用以下语法：  ~~`min(/host/key,#5*10)`~~

en-us	### Other types of discovery  More detail and how-tos on other types of out-of-the-box discovery is available in the following sections:  -   discovery of [network     interfaces](/manual/discovery/low_level_discovery/examples/network_interfaces); -   discovery of [CPUs and CPU     cores](/manual/discovery/low_level_discovery/examples/cpu); -   discovery of [SNMP     OIDs](/manual/discovery/low_level_discovery/examples/snmp_oids); -   discovery of [JMX     objects](/manual/discovery/low_level_discovery/examples/jmx); -   discovery using [ODBC SQL     queries](/manual/discovery/low_level_discovery/examples/sql_queries); -   discovery of [Windows     services](/manual/discovery/low_level_discovery/examples/windows_services); -   discovery of [host     interfaces](/manual/discovery/low_level_discovery/examples/host_interfaces)     in Zabbix.  For more detail on the JSON format for discovery items and an example of how to implement your own file system discoverer as a Perl script, see [creating custom LLD rules](#creating_custom_lld_rules).
zh-cn	### 其它类型的自动发现  如果想立刻上手熟悉其它类型的自动发现，更多信息和如何实现(how-to)方面可参阅以下章节:  -   [网络接口](/manual/discovery/low_level_discovery/examples/network_interfaces)的自动发现; -   [CPU 和 CPU     核心](/manual/discovery/low_level_discovery/examples/cpu)的自动发现; -   [SNMP     OID](/manual/discovery/low_level_discovery/examples/snmp_oids)的自动发现; -   [JMX     对象](/manual/discovery/low_level_discovery/examples/jmx)的自动发现; -   使用[ODBC SQL     查询](/manual/discovery/low_level_discovery/examples/sql_queries)的自动发现; -   [Windows     服务](/manual/discovery/low_level_discovery/examples/windows_services)的自动发现; -   Zabbix [主机接口](/manual/discovery/low_level_discovery/examples/host_interfaces)的自动发现。   更多关于JSON格式的自动发现和关于如何使用Perl脚本对文件系统做自动发现，请参阅 [创建自定义LLD规则](#creating_custom_lld_rules)。

en-us	#### Other uses  Unit symbols are also used for a human-readable representation of data in the frontend.  In both Zabbix server and frontend these symbols are supported:  -   **K** - kilo -   **M** - mega -   **G** - giga -   **T** - tera  When item values in B, Bps are displayed in the frontend, base 2 is applied (1K = 1024). Otherwise a base of 10 is used (1K = 1000).  Additionally the frontend also supports the display of:  -   **P** - peta -   **E** - exa -   **Z** - zetta -   **Y** - yotta
zh-cn	#### 其他用途  单位符号也用于前端数据可读的表示法。  Zabbix server 和前端都支持这些符号：  -   **K** - 千 -   **M** - 兆 -   **G** - 吉 -   **T** - 太  当监控项值在前端显示为B、Bps时, 是基于二进制的(1K = 1024)。其他情况基于十进制(1K = 1000)。  此外，前端还支持显示：  -   **P** - 拍 -   **E** - 艾 -   **Z** - 泽 -   **Y** - 尧

en-us	#### Override  The **Override** tab allows setting rules to modify the list of item, trigger, graph and host prototypes or their attributes for discovered objects that meet given criteria.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_e.png)  Overrides (if any) are displayed in a reorderable drag-and-drop list and executed in the order in which they are defined.  To configure details of a new override, click on ![](../../../assets/en/manual/config/add_link.png) in the *Overrides* block. To edit an existing override, click on the override name. A popup window will open allowing to edit the override rule details.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override.png)  All mandatory parameters are marked with red asterisks.  |Parameter|Description| |--|--------| |*Name*|A unique (per LLD rule) override name.| |*If filter matches*|Defines whether next overrides should be processed when filter conditions are met:<br>**Continue overrides** - subsequent overrides will be processed.<br>**Stop processing** - operations from preceding (if any) and this override will be executed, subsequent overrides will be ignored for matched LLD rows.| |*Filters*|Determines to which discovered entities the override should be applied. Override filters are processed after discovery rule [filters](low_level_discovery#filter) and have the same functionality.| |*Operations*|Override operations are displayed with these details:<br>**Condition** - an object type (item prototype/trigger prototype/graph prototype/host prototype) and a condition to be met (equals/does not equal/contains/does not contain/matches/does not match)<br>**Action** - links for editing and removing an operation are displayed.|  **Configuring an operation**  To configure details of a new operation, click on ![](../../../assets/en/manual/config/add_link.png) in the Operations block. To edit an existing operation, click on ![](../../../assets/en/manual/config/edit_link.png) next to the operation. A popup window where you can edit the operation details will open.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override_op.png)  |Parameter|<|<|Description| |-|-|----------|----------------------------------------| |*Object*|<|<|Four types of objects are available:<br>Item prototype<br>Trigger prototype<br>Graph prototype<br>Host prototype| |*Condition*|<|<|Allows filtering entities to which the operation should be applied.| | |Operator|<|Supported operators:<br>**equals** - apply to this prototype<br>**does not equal** - apply to all prototypes, except this<br>**contains** - apply, if prototype name contains this string<br>**does not contain** - apply, if prototype name does not contain this string<br>**matches** - apply, if prototype name matches regular expression<br>**does not match** - apply, if prototype name does not match regular expression<br>| |^|Pattern|<|A [regular expression](/manual/regular_expressions) or a string to search for.| |^|Object: *Item prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original item prototype settings:<br>*Yes* - the item will be added in an enabled state.<br>*No* - the item will be added to a discovered entity but in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original item prototype settings:<br>*Yes* - the item will be added.<br>*No* - the item will not be added.| |^|^|*Update interval*|When the checkbox is marked, two options will appear, allowing to set different interval for the item:<br>*Delay* - Item update interval. [User macros](/manual/config/macros/user_macros) and [time suffixes](/manual/appendix/suffixes) (e.g. 30s, 1m, 2h, 1d) are supported. Should be set to 0 if *Custom interval* is used.<br>*Custom interval* - click ![](../../../assets/en/manual/config/add_link.png) to specify flexible/scheduling intervals. For detailed information see [Custom intervals](/manual/config/items/item/custom_intervals).| |^|^|*History storage period*|When the checkbox is marked, the buttons will appear, allowing to set different history storage period for the item:<br>*Do not keep history* - if selected, the history will not be stored.<br>*Storage period* - if selected, an input field for specifying storage period will appear to the right. [User macros](/manual/config/macros/user_macros) and [LLD macros](/manual/config/macros/lld_macros) are supported.| |^|^|*Trend storage period*|When the checkbox is marked, the buttons will appear, allowing to set different trend storage period for the item:<br>*Do not keep trends* - if selected, the trends will not be stored.<br>*Storage period* - if selected, an input field for specifying storage period will appear to the right. [User macros](/manual/config/macros/user_macros) and [LLD macros](/manual/config/macros/lld_macros) are supported.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the item prototype, even if the tag names match.| |^|Object: *Trigger prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original trigger prototype settings:<br>*Yes* - the trigger will be added in an enabled state.<br>*No* - the trigger will be added to a discovered entity, but in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original trigger prototype settings:<br>*Yes* - the trigger will be added.<br>*No* - the trigger will not be added.| |^|^|*Severity*|When the checkbox is marked, trigger severity buttons will appear, allowing to modify trigger severity.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the trigger prototype, even if the tag names match.| |^|Object: *Graph prototype*|<|<| |^| |*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original graph prototype settings:<br>*Yes* - the graph will be added.<br>*No* - the graph will not be added.| |^|Object: *Host prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original host prototype settings:<br>*Yes* - the host will be created in an enabled state.<br>*No* - the host will be created in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original host prototype settings:<br>*Yes* - the host will be discovered.<br>*No* - the host will not be discovered.| |^|^|*Link templates*|When the checkbox is marked, an input field for specifying templates will appear. Start typing the template name or click on *Select* next to the field and select templates from the list in a popup window.<br>All templates linked to a host prototype will be replaced by templates from this override.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the host prototype, even if the tag names match.| |^|^|*Host inventory*|When the checkbox is marked, the buttons will appear, allowing to select different inventory [mode](/manual/config/hosts/inventory) for the host prototype:<br>*Disabled* - do not populate host inventory<br>*Manual* - provide details manually<br>*Automated* - auto-fill host inventory data based on collected metrics.|
zh-cn	#### 覆盖  **覆盖** 选项卡允许设置规则来修改监控项，触发器、图形和主机原型或它们的属性以用于发现满足给定条件的对象。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_e.png)  覆盖（如果有）在可重新排序的拖放列表中显示，并且按照定义的顺序执行。 配置一个新的覆盖，在 *覆盖*选项卡单击 ![](../../../assets/en/manual/config/add_link.png) 。要编辑现有覆盖，请单击覆盖名称。在弹出窗口中编辑覆盖规则详细信息。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override.png)  所有强制参数都标有红色星号。  |参数|描述| |---------|-----------| |*名称*|唯一的（根据 LLD 规则）覆盖名称。| |*如果过滤器匹配*|当下面条件满足时，下一个覆盖是否需要执行:<br>**继续覆盖** - 后续覆盖会执行。<br>**停止处理** - 前面的操作 (如果有) 和当前操作会执行, 后续覆盖会忽略。| |*过滤器*|定义了覆盖会应用到哪些已发现实体上。覆盖过滤器在自动发现规则的[过滤器](low_level_discovery#filter) 之后执行，其和自动发现规则的过滤器功能相同。| |*操作*|覆盖操作包含下列内容:<br>**条件** - 一个对象类型 (监控项原型/触发器原型/图表原型/主机原型) 和一个需要满足的条件(等于/不等于/包含/不包含/匹配/不匹配)<br>**动作** - 编辑和移除操作的链接。|  **配置一个操作**  要配置一个新操作, 点击操作面板上的 ![](../../../assets/en/manual/config/add_link.png) 。编辑现有操作, 点击操作旁边的 ![](../../../assets/en/manual/config/edit_link.png) 。点击编辑按钮会出现弹窗。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override_op.png)  |参数|<|<|描述| |---------|-----------| |*对象*|<|<|可使用四种对象:<br>监控项原型<br>触发器原型<br>图表原型<br>主机原型| |*条件*|<|<|允许过滤执行操作的目标实体。| |<|操作|<|可用操作:<br>**等于** - 应用到此原型<br>**不等于** - 应用到所有原型, 此原型除外<br>**包含** - 如果原型名称包含此字符串，则应用<br>**不包含** - 如果原型名称不包含此字符串，则应用<br>**匹配** - 如果原型名称匹配正则表达式，则应用<br>**不匹配** - 如果原型名称不匹配正则表达式，则应用<br>| |^|模式|<|A [正则表达式](/manual/regular_expressions) 或 需要搜索的字符串。| |<|对象: *监控项原型*|<|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮, 允许覆盖原始监控项原型设置:<br>*是* - 添加监控项，并且监控项处于启用状态。<br>*否* - 添加监控项到已发现的实体，但处于禁用状态。| |^|*发现*|如果选取检查框, 会出现按钮, 允许覆盖原始监控项原型设置:<br>*是* - 添加监控项。<br>*否* - 不添加监控项。| |^|*更新间隔*|如果选取检查框, 会出现两个选项, 允许为监控项设置不同的间隔:<br>*延迟* - 监控项更新间隔。支持[用户宏](/manual/config/macros/user_macros) 和 [时间后缀](/manual/appendix/suffixes) (如 30s, 1m, 2h, 1d)。如果使用了 *自定义间隔* 则更新间隔应设置为0。<br>*自定义间隔* - 点击 ![](../../../assets/en/manual/config/add_link.png) 指定 灵活/计划的时间间隔。 更多信息请参阅 [自定义间隔](/manual/config/items/item/custom_intervals).| |^|*历史保存周期*|如果选取检查框, 会出现按钮, 允许给监控项设置不同的历史保存周期:<br>*不保存历史* - 如果选择，那么历史数据不会保存。<br>*保存周期* - 如果选择, 右侧会出现输入框，可以输入保存周期。支持[用户宏](/manual/config/macros/user_macros) 和[LLD宏](/manual/config/macros/lld_macros)。| |^|*趋势数据保存周期*|如果选取检查框, 会出现按钮, 允许给监控项设置不同的趋势数据保存周期:<br>*不保存趋势数据* - 如果选择, 趋势数据不会保存。<br>*保存周期* - 如果选择, 右侧会出现输入框。支持[用户宏](/manual/config/macros/user_macros)和[LLD宏](/manual/config/macros/lld_macros)。| |^|*标签*|如果选取检查框, 会出现一个面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到监控项原型的标签末尾。| |<|对象: *触发器原型*|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮, 允许覆盖原始触发器原型设置:<br>*是* - 添加触发器，并且处于启用状态。<br>*否* - 添加触发器到已发现的实体中，但触发器是禁用的。| |^|*发现*|如果选取检查框, 会出现按钮,允许覆盖原始触发器原型设置 :<br>*是* - 添加触发器。<br>*否* - 不会添加触发器。| |^|*严重性*|如果选取检查框, 会出现触发器严重性按钮, 允许修改触发器的严重性级别。| |^|*标签*|如果选取检查框,会出现一个新面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到监控项原型的标签末尾。| |<|对象: *图形原型*|<|<| |^|*发现*|如果选取检查框, 会出现按钮, 允许覆盖原始图形原型设置:<br>*是* - 添加图形。<br>*否* - 不添加图形。| |<|对象: *主机原型*|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮,允许覆盖原始主机原型设置 :<br>*是* - 创建主机，主机处于启用状态。<br>*否* - 创建主机，主机处于禁用状态。| |^|*发现*|如果选取检查框,会出现按钮,允许覆盖原始的主机原型设置:<br>*是* - 主机将被发现。<br>*否* - 主机不会被发现。| |^|*链接模板*|如果选取检查框,会出现一个输入框，用于指定模板。 输入模板名称，或点击输入框旁边的 *选择* 然后从弹窗列表中选择模板。<br>所有链接到主机原型的模板均会被替换为此覆盖中配置的模板。| |^|*标签*|如果选取检查框,会出现一个面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到主机原型的标签后面。| |^|*主机资产*|如果选取检查框,会出现按钮,允许基于主机原型选择不同的资产[模式](/manual/config/hosts/inventory) :<br>*禁用* - 不添加主机资产数据。<br>*手工* - 手工输入主机资产数据。<br>*自动* - 基于收集的数据自动添加主机资产数据。|

en-us	#### Overview  Additional files or directories can be included into server/proxy/agent configuration using the `Include` parameter.
zh-cn	#### 概述  可以使用该`Include`参数将其他文件或目录包含到 server/proxy/agent 配置中。

en-us	#### Overview  Aggregate calculations are a [calculated item](/manual/config/items/itemtypes/calculated)  type allowing to collect information from several items by Zabbix server and  then calculate an aggregate, depending on the aggregate function used.  Only unsigned integer and float values (type of information) are supported for aggregate calculation  items.  Aggregate calculations do not require any agent running on the host being monitored.
zh-cn	#### 概述  聚合计算是一种 [计算监控项](/manual/config/items/itemtypes/calculated) 类型，允许 Zabbix 服务器从多个项目中收集信息，然后根据使用的聚合函数计算聚合。  聚合计算项仅支持无符号整数和浮点值（信息类型）。  聚合计算不需要在被监控的主机上运行任何agent。

en-us	#### Overview  All users in Zabbix access the Zabbix application through the web-based frontend. Each user is assigned a unique login name and a password.  All user passwords are encrypted and stored in the Zabbix database. Users cannot use their user id and password to log directly into the UNIX server unless they have also been set up accordingly to UNIX. Communication between the web server and the user browser can be protected using SSL.  With a flexible [user permission schema](/manual/config/users_and_usergroups/permissions) you can restrict and differentiate rights to:  -   access administrative Zabbix frontend functions -   perform certain actions in the frontend -   access monitored hosts in hostgroups -   use specific API methods
zh-cn	#### 概述  Zabbix 中的所有用户都通过基于 web 的方式访问 Zabbix 应用程序前端。每个用户都被分配了一个唯一的登录名和密码。  所有用户密码都经过加密并存储在 Zabbix 数据库中。用户不能使用自己的用户名和密码直接登录。除非它们也已针对 UNIX 设置相应的 UNIX 服务器。Web 服务器和用户浏览器之间的通信可以使用 SSL 保护。  具有灵活的[用户权限架构](/manual/config/users_and_usergroups/permissions) 你可以限制和区分以下权利：  - 访问管理 Zabbix 前端功能 - 在前端执行某些操作 - 访问主机组中的受监控主机 - 使用特定的 API 方法

en-us	#### Overview  An optional context can be used in [user macros](/manual/config/macros/user_macros), allowing to override the default value with a context-specific one.  The context is appended to the macro name; the syntax depends on whether the context is a static text value:      {$MACRO:"static text"}  or a regular expression:      {$MACRO:regex:"regular expression"}   Note that a macro with regular expression context can only be defined in user macro configuration. If the `regex:` prefix is used elsewhere as user macro context, like in a trigger expression, it will be treated as static context.  Context quoting is optional (see also [important notes](#important_notes)).  Macro context examples:  |Example|Description| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|User macro without context.| |`{$LOW_SPACE_LIMIT:/tmp}`|User macro with context (static string).| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|User macro with context (regular expression). Same as `{$LOW_SPACE_LIMIT:/tmp}`.| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|User macro with context (regular expression). Matches all strings prefixed with /var/log/.|
zh-cn	#### 概述  可选上下文可用于 [user宏]（/manual/config/macros/user_macros），允许覆盖具有特定于上下文的默认值。  上下文附加到宏名称；语法取决于是否上下文是一个静态文本值：      {$MACRO:"静态文本"}  或正则表达式：      {$MACRO:regex:"正则表达式"}  请注意，具有正则表达式上下文的宏只能在用户宏配置。如果 `regex:` 前缀在其他地方被用作用户宏上下文，就像在触发器表达式中一样，它将被视为静态上下文。  上下文引用是可选的（另见 [重要注释]（#important_notes））。  宏上下文示例：  |示例|说明| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|没有上下文的用户宏。| |`{$LOW_SPACE_LIMIT:/tmp}`|带有上下文的用户宏（静态字符串）。| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|带有上下文的用户宏（正则表达式）。与`{$LOW_SPACE_LIMIT:/tmp}`相同。| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|带有上下文的用户宏（正则表达式）。匹配所有以 /var/log/ 为前缀的字符串。|

en-us	#### Overview  Assuming that we have configured some items and triggers and now are getting some events happening as a result of triggers changing state, it is time to consider some actions.  To begin with, we would not want to stare at the triggers or events list all the time. It would be much better to receive notification if something significant (such as a problem) has happened. Also, when problems occur, we would like to see that all the people concerned are informed.  That is why sending notifications is one of the primary actions offered by Zabbix. Who and when should be notified upon a certain event can be defined.  To be able to send and receive notifications from Zabbix you have to:  -   [define some media](/manual/config/notifications/media) -   [configure an action](/manual/config/notifications/action) that     sends a message to one of the defined media  Actions consist of *conditions* and *operations*. Basically, when conditions are met, operations are carried out. The two principal operations are sending a message (notification) and executing a remote command.  For discovery and autoregistration created events, some additional operations are available. Those include adding or removing a host, linking a template etc.
zh-cn	####  概述  在配置了诸多监控项和触发器，并且在触发器状态发生变化的情况下，用户已经接收到了一些告警信息，那么接下来就要考虑通过配置动作（actions）来响应事件的发生。  值得强调的是，用户不可能一直观察触发器或者事件的状态变化。更好的解决办法是，当发生明显的变化时（例如出现紧急问题）用户可以接收到系统发送的通知。当然，问题发生时，所有相关人员都可以接收到该事件通知是最好的。  可以说，事件通知是 Zabbix 首要的动作配置之一。该配置可以细致到对特定事件所要通知的对象和时间进行定义。  开启 Zabbix 事件通知的发送和接收功能，您需要做到：  -   [定义媒介](/manual/config/notifications/media) -   [配置动作](/manual/config/notifications/action) 向指定的定义媒介发送消息  标准的动作由 *条件* 和 *操作* 两个元素构成。基本上，每当设定的条件达成时，就会执行相对应的设定操作。最重要的两个操作分别为：发送消息（事件提醒）和执行远程命令。  对于发现和自动注册所创建的事件，用户可以配置一些额外的操作。这些操作包括添加或删除主机，链接一个监控模板等。

en-us	### Overview  A Zabbix proxy can collect performance and availability data on behalf of the Zabbix server. This way, a proxy can take on itself some of the load of collecting data and offload the Zabbix server.  Also, using a proxy is the easiest way of implementing centralized and distributed monitoring, when all agents and proxies report to one Zabbix server and all data is collected centrally.  A Zabbix proxy can be used to:  -   Monitor remote locations -   Monitor locations having unreliable communications -   Offload the Zabbix server when monitoring thousands of devices -   Simplify the maintenance of distributed monitoring  ![](../../../assets/en/manual/proxies/proxy.png){width="500"}  The proxy requires only one TCP connection to the Zabbix server. This way it is easier to get around a firewall as you only need to configure one firewall rule.  ::: noteimportant Zabbix proxy must use a separate database. Pointing it to the Zabbix server database will break the configuration. :::  All data collected by the proxy is stored locally before transmitting it over to the server. This way no data is lost due to any temporary communication problems with the server. The *ProxyLocalBuffer* and *ProxyOfflineBuffer* parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) control for how long the data are kept locally.  ::: noteimportant It may happen that a proxy, which receives the latest configuration changes directly from Zabbix server database, has a more up-to-date configuration than Zabbix server whose configuration may not be updated as fast due to the value of [CacheUpdateFrequency](/manual/appendix/config/zabbix_server). As a result, proxy may start gathering data and send them to Zabbix server that ignores these data. :::  Zabbix proxy is a data collector. It does not calculate triggers, process events or send alerts. For an overview of what proxy functionality is, review the following table:  |Function|<|Supported by proxy| |--------|-|------------------| |Items|<|<| |<|*Zabbix agent checks*|**Yes**| |^|*Zabbix agent checks (active)*|**Yes** ^1^| |^|*Simple checks*|**Yes**| |^|*Trapper items*|**Yes**| |^|*SNMP checks*|**Yes**| |^|*SNMP traps*|**Yes**| |^|*IPMI checks*|**Yes**| |^|*JMX checks*|**Yes**| |^|*Log file monitoring*|**Yes**| |^|*Internal checks*|**Yes**| |^|*SSH checks*|**Yes**| |^|*Telnet checks*|**Yes**| |^|*External checks*|**Yes**| |^|*Dependent items*|**Yes**| |^|*Script items*|**Yes**| |Built-in web monitoring|<|**Yes**| |Item value preprocessing|<|**Yes**| |Network discovery|<|**Yes**| |Active agent autoregistration|<|**Yes**| |Low-level discovery|<|**Yes**| |Remote commands|<|**Yes**| |Calculating triggers|<|*No*| |Processing events|<|*No*| |Event correlation|<|*No*| |Sending alerts|<|*No*|  ::: noteclassic \[1\] To make sure that an agent asks the proxy (and not the server) for active checks, the proxy must be listed in the **ServerActive** parameter in the agent configuration file. :::
zh-cn	 #### 概览  Zabbix Proxy可以代表Zabbix server收集性能和可用性数据。 通过这种方式，proxy可以自己承担一些收集数据的负载，并减轻Zabbix Server的负担。  此外，当所有agents和proxy都向一个Zabbix server报告并且所有数据都集中收集时，使用Proxy代理是实现集中式和分布式监控的最简单方法。  Zabbix proxy 可以被使用作为:  -   监控远程位置 -   监控通信不可靠的位置 -   在监视数千个设备时卸载Zabbix服务器 -   简化分布式监控的维护  ![](../../../assets/en/manual/proxies/proxy.png){width="600"}  proxy 只需要一个到Zabbix server的TCP连接。 这样就可以更容易地绕过防火墙，因为您只需要配置一条防火墙规则。  ::: noteimportant Zabbix proxy代理必须使用单独的数据库。将其指向Zabbix server数据库将破坏配置。 :::  proxy收集的所有数据在传输到server之前都存储在本地。这种方式不会因为与server之间的任何临时通信问题而丢失数据。*ProxyLocalBuffer*和*ProxyOfflineBuffer*参数在[proxy配置文件](/manual/appendix/config/zabbix_proxy)控制数据在本地保存多长时间。  ::: noteimportant 可能会出现这样的情况:直接从Zabbix server数据库接收最新配置更改的proxy代理拥有比Zabbix server更最新的配置，而Zabbix server的配置可能因为[CacheUpdateFrequency](/manual/appendix/config/zabbix_server)的值而不能快速更新。因此，proxy代理可能会开始收集数据并将它们发送到忽略这些数据的Zabbix server。 :::  Zabbix proxy代理是一个数据收集器。 它不计算触发器、处理事件或发送警报。 有关什么是proxy代理功能的概述，请查看下表：  |功能|<|proxy支持列表| |--------|-|------------------| |Items|<|<| |<|*Zabbix agent checks*|**Yes**| |^|*Zabbix agent checks (active)*|**Yes** ^1^| |^|*Simple checks*|**Yes**| |^|*Trapper items*|**Yes**| |^|*SNMP checks*|**Yes**| |^|*SNMP traps*|**Yes**| |^|*IPMI checks*|**Yes**| |^|*JMX checks*|**Yes**| |^|*Log file monitoring*|**Yes**| |^|*Internal checks*|**Yes**| |^|*SSH checks*|**Yes**| |^|*Telnet checks*|**Yes**| |^|*External checks*|**Yes**| |^|*Dependent items*|**Yes**| |^|*Script items*|**Yes**| |Built-in web monitoring|<|**Yes**| |Item value preprocessing|<|**Yes**| |Network discovery|<|**Yes**| |Active agent autoregistration|<|**Yes**| |Low-level discovery|<|**Yes**| |Remote commands|<|**Yes**| |Calculating triggers|<|*No*| |Processing events|<|*No*| |Event correlation|<|*No*| |Sending alerts|<|*No*|  ::: 常见注意事项 \[1\] 为确保agent请求proxy(而不是server)进行活动检查，proxy代理必须被列于**ServerActive** 配置文件中的参数。 :::

en-us	#### Overview  By default, Zabbix provides a number of predefined themes. You may follow the step-by-step procedure provided here in order to create your own. Feel free to share the result of your work with Zabbix community if you created something nice.
zh-cn	#### 概述  默认情况下，Zabbix 提供了许多预定义的主题。您可以按照此处提供的分步程序来创建您自己的。如果您创建了一些不错的东西，请随时与 Zabbix 社区分享您的工作成果。

en-us	##### Overview by item type  In this screen it is easy to locate if the problem is related to one or several item types.  ![](../../../../../assets/en/manual/web_interface/queue.png){width="600"}  Each line contains an item type. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively.
zh-cn	##### 监控项类型概览  在此屏幕中，很容易找到问题是否与一种或多种监控项类型有关。  ![](../../../../../assets/en/manual/web_interface/queue.png){width="600"}  每行包含一个监控项类型。每列显示等待监控项的数量 - 分别等待 5-10 秒/10-30 秒/30-60 秒/1-5 分钟/5-10 分钟或超过 10 分钟。

en-us	##### Overview by proxy  In this screen it is easy to locate if the problem is related to one of the proxies or the server.  ![](../../../../../assets/en/manual/web_interface/queue_proxy.png){width="600"}  Each line contains a proxy, with the server last in the list. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively.
zh-cn	##### proxy概览  在此屏幕中，很容易找到问题是否与poxy、server之一有关。  ![](../../../../../assets/en/manual/web_interface/queue_proxy.png){width="600"}  每行包含一个proxy，server位于列表的最后。每列显示等待监控项的数量 - 分别等待 5-10 秒/10-30 秒/30-60 秒/1-5 分钟/5-10 分钟或超过 10 分钟。

en-us	#### Overview  Configuring a template requires that you first create a template by defining its general parameters and then you add entities (items, triggers, graphs, etc.) to it.
zh-cn	#### 概述  配置模板需要首先通过定义一些常规参数来创建模板，然后添加实体（监控项，触发器，图表等）。

en-us	#### Overview  Custom graphs, as the name suggests, offer customization capabilities.  While simple graphs are good for viewing data of a single item, they do not offer configuration capabilities.  Thus, if you want to change graph style or the way lines are displayed or compare several items, for example, incoming and outgoing traffic in a single graph, you need a custom graph.  Custom graphs are configured manually.  They can be created for a host or several hosts or for a single template.
zh-cn	#### 概述  顾名思义，自定义图表提供自定义功能。  虽然简单的图表有利于查看单个项目的数据，但它们不支持配置功能。  因此，如果您想更改图形样式或线条的显示方式或比较几个监控项，例如，单个图表展示接收和转发的流量，您需要一个自定义图表。  自定义图表是手动配置的。  它们可以为一台主机或多台主机或单个主机创建模板。

en-us	#### Overview  Data provided in Prometheus line format can be used for low-level discovery.  See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for details how Prometheus data querying is implemented in Zabbix.
zh-cn	#### 概述  Prometheus中的数据格式适用于低级别自动发现。  关于Zabbix如何执行Prometheus数据的查询，请参考 [Prometheus检查](/manual/config/items/itemtypes/prometheus)。

en-us	#### Overview  Debug mode may be used to diagnose performance problems with frontend pages.
zh-cn	#### 概述  调试模式可用于诊断前端页面的性能问题。

en-us	#### Overview  Each pre-shared key (PSK) in Zabbix actually is a pair of:  -   non-secret PSK identity string, -   secret PSK string value.  PSK identity string is a non-empty UTF-8 string. For example, "PSK ID 001 Zabbix agentd". It is a unique name by which this specific PSK is referred to by Zabbix components. Do not put sensitive information in PSK identity string - it is transmitted over the network unencrypted.  PSK value is a hard to guess string of hexadecimal digits, for example, "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9".
zh-cn	#### 概述  Zabbix中的每个预共享密钥（PSK）实际上是一对：  - 非秘密 PSK 标识字符串， - 秘密 PSK 字符串值。  PSK 标识字符串是非空 UTF-8 字符串。例如，"PSK ID 001 Zabbix agentd"。它是一个唯一的名称，Zabbix组件通过该名称引用此特定PSK。不要将敏感信息放在 PSK 标识字符串中 - 它是通过未加密的网络传输的。  PSK 值是一个难以猜测的十六进制数字字符串，例如， "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9"。

en-us	#### Overview  Event correlation allows to correlate problem events to their resolution in a manner that is very precise and flexible.  Event correlation can be defined:  -   [on trigger level](/manual/config/event_correlation/trigger) - one     trigger may be used to relate separate problems to their solution -   [globally](/manual/config/event_correlation/global) - problems can     be correlated to their solution from a different trigger/polling     method using global correlation rules
zh-cn	#### 概述  事件关联允许以非常精确灵活地方式关联问题事件和它们的解决方法。  事件关联可以被定义为：  -   [触发器级别](/manual/config/event_correlation/trigger)——不同的问题和解决方法可以关联同一个触发器 -   [全局](/manual/config/event_correlation/global)——使用全局关联规则可以通过不同的触发器轮询方法将问题和它们的解决方法关联起来

en-us	#### Overview  External check is a check executed by Zabbix server by [running a shell script](/manual/appendix/command_execution) or a binary. However, when hosts are monitored by a Zabbix proxy, the external checks are executed by the proxy.  External checks do not require any agent running on a host being monitored.  The syntax of the item key is:      script[<parameter1>,<parameter2>,...]  Where:  |ARGUMENT|DEFINITION| |--------|----------| |**script**|Name of a shell script or a binary.| |**parameter(s)**|Optional command line parameters.|  If you don't want to pass any parameters to the script you may use:      script[] or     script  Zabbix server will look in the directory defined as the location for external scripts (parameter 'ExternalScripts' in [Zabbix server configuration file](/manual/appendix/config/zabbix_server)) and execute the command. The command will be executed as the user Zabbix server runs as, so any access permissions or environment variables should be handled in a wrapper script, if necessary, and permissions on the command should allow that user to execute it. Only commands in the specified directory are available for execution.  ::: notewarning Do not overuse external checks! As each script requires starting a fork process by Zabbix server, running many scripts can decrease Zabbix performance a lot. :::
zh-cn	#### 概述  外部检查是 Zabbix server 通过[运行shell脚本](/manual/appendix/command_execution)或二进制执行的检查。但是当主机被 Zabbix proxy 接管时，外部检查则由 Zabbix proxy 执行。  外部检查不需要在被监控的主机上运行任何代理  监控项键的语法是：     script[<parameter1>,<parameter2>,...]  参数：  |字段|描述| |--------|----------| |**script**|shell 脚本或二进制文件的名称.| |**parameter(s)**|可选的命令行参数.|  如果您不想将任何参数传递给脚本,您可以使用：     script[] or    script  Zabbix Server 将查找外部脚本位置的目录([Zabbix Server配置文件](/manual/appendix/config/zabbix_server)中的“ExternalScripts”参数定义的位置)并执行该命令。该命令将以Zabbix Server服务运行的用户身份执行*script*，任何访问权限或环境变量都应该在封装在脚本中处理，该命令的权限应该只允许该用户在指定的目录下执行它。  ::: notewarning 不要过度使用外部检查！因为每个脚本都需要Zabbix Server启动一个fork出来的进程，所以运行很多脚本会大幅度的降低Zabbix的性能。 :::

en-us	#### Overview  Global event correlation allows to reach out over all metrics monitored by Zabbix and create correlations.  It is possible to correlate events created by completely different triggers and apply the same operations to them all. By creating intelligent correlation rules it is actually possible to save yourself from thousands of repetitive notifications and focus on root causes of a problem!  Global event correlation is a powerful mechanism, which allows you to untie yourself from one-trigger based problem and resolution logic. So far, a single problem event was created by one trigger and we were dependent on that same trigger for the problem resolution. We could not resolve a problem created by one trigger with another trigger. But with event correlation based on event tagging, we can.  For example, a log trigger may report application problems, while a polling trigger may report the application to be up and running. Taking advantage of event tags you can tag the log trigger as *Status: Down* while tag the polling trigger as *Status: Up*. Then, in a global correlation rule you can relate these triggers and assign an appropriate operation to this correlation such as closing the old events.  In another use, global correlation can identify similar triggers and apply the same operation to them. What if we could get only one problem report per network port problem? No need to report them all. That is also possible with global event correlation.  Global event correlation is configured in **correlation rules**. A correlation rule defines how the new problem events are paired with existing problem events and what to do in case of a match (close the new event, close matched old events by generating corresponding OK events). If a problem is closed by global correlation, it is reported in the *Info* column of *Monitoring* → *Problems*.  Configuring global correlation rules is available to Super Admin level users only.  ::: noteimportant Event correlation must be configured very carefully, as it can negatively affect event processing performance or, if misconfigured, close more events than was intended (in the worst case even all problem events could be closed). :::  To configure global correlation **safely**, observe the following important tips:  -   Reduce the correlation scope. Always set a unique tag for the new     event that is paired with old events and use the *New event tag*     correlation condition; -   Add a condition based on the old event when using the *Close old     event* operation (or else all existing problems could be closed); -   Avoid using common tag names that may end up being used by different     correlation configurations; -   Keep the number of correlation rules limited to the ones you really     need.  See also: [known issues](/manual/installation/known_issues#global_event_correlation).
zh-cn	#### 概述  全局事件关联允许覆盖Zabbix监控的所有指标并创建关联性。  可以关联由完全不同的触发器创建的事件，并对它们应用相同的操作。 通过创建智能关联规则，实际上可以避免数以千计的重复通知，并专注于问题的根本原因！  全局事件关联是一种强大的机制，它可以让您从基于单个触发的问题和解决逻辑中解开自己。 到目前为止，单个问题事件是由一个触发器创建的，我们依赖于相同的问题解决触发器。 我们无法用另一个触发器解决一个触发器创建的问题。 但是基于事件标记的事件关联，我们可以。  例如，日志触发器可以报告应用程序问题，而轮询触发器可以报告应用程序启动并运行。 利用事件标记，您可以将日志触发器标记为*状态：Down*，而将轮询触发器标记为*状态：Up*。 然后，在全局关联规则中，您可以关联这些触发器并为此关联分配适当的操作，例如关闭旧事件。  在另一种用途中，全局关联可以识别类似的触发器并对它们应用相同的操作。 如果我们每个网络端口问题只能获得一个问题报告怎么办？ 无需全部报告。 通过全局事件关联也是能够实现的。  全局事件关联在**关联规则**中配置。 关联规则定义新问题事件如何与现有问题事件配对以及在匹配情况下要执行的操作（关闭新事件，通过生成相应的OK事件来关闭匹配的旧事件）。 如果问题被全局关联关闭，则会在*监控* - > *问题*的*消息*列中报告。  配置全局关联规则仅适用于Zabbix超级管理员级别用户。  ::: noteimportant 必须非常仔细地配置事件关联，因为它会对事件处理性能产生负面影响，或者如果配置错误，会关闭比预期更多的事件（在最坏的情况下，甚至可以关闭所有问题事件）。:::  要安全地配置全局关联，请遵循以下重要提示：  -   减少相关范围。     始终为与旧事件配对的新事件设置唯一标记，并使用*新事件标记*关联条件; -   使用*关闭旧事件*操作时，根据旧事件添加条件（或者可以关闭所有现有问题）; -   避免使用可能最终被不同关联配置使用的常见标记名称; -   保持关联规则的数量仅限于您真正需要的数量。  可参考: [known issues](/manual/installation/known_issues#global_event_correlation).

en-us	#### Overview  Global notifications are a way of displaying issues that are currently happening right on the screen you're at in Zabbix frontend.  Without global notifications, working in some other location than *Problems* or the *Dashboard* would not show any information regarding issues that are currently happening. Global notifications will display this information regardless of where you are.  Global notifications involve both showing a message and [playing a sound](sound).  ::: noteimportant The auto play of sounds may be disabled in recent browser versions by default. In this case, you need to change this setting manually. :::
zh-cn	#### 概述  全局通知是一种在 Zabbix 前端屏幕上显示当前正在发生的问题的方式。  如果没有全局通知，在 *问题* 或 *仪表板* 以外的其他位置工作将不会显示有关当前正在发生的问题的任何信息。 无论您身在何处，全局通知都会显示此信息。  全局通知涉及显示消息和[播放声音]（声音）。  ::: noteimportant 默认情况下，最近的浏览器版本可能会禁用声音的自动播放。 在这种情况下，您需要手动更改此设置。 :::

en-us	#### Overview  Having to use some large numbers, for example '86400' to represent the number of seconds in one day, is both difficult and error-prone. This is why you can use some appropriate unit symbols (or suffixes) to simplify Zabbix trigger expressions and item keys.  Instead of '86400' for the number of seconds you can simply enter '1d'. Suffixes function as multipliers.
zh-cn	#### 概述  当必须使用一些大数字，例如“86400”来表示一天中的秒数，既困难又容易出错。这就需要使用一些单位符号来简化 Zabbix 触发器表达式和监控项键。  可以简单地输入“1d”，而不是“86400”秒。后缀起到乘数的作用。

en-us	### Overview  High availability (HA) is typically required in critical infrastructures  that can afford virtually no downtime. So for any service that  may fail there must be a failover option in place to take over should the current service fail.  Zabbix offers a **native** high-availability solution that is easy to  set up and does not require any previous HA expertise. Native Zabbix HA  may be useful for an extra layer of protection against software/hardware  failures of Zabbix server or to have less downtime due to maintenance.  In the Zabbix high availability mode multiple Zabbix servers are run as  nodes in a cluster. While one Zabbix server in the cluster is active,  others are on standby, ready to take over if necessary.  ![](../../../../assets/en/manual/config/zabbix_ha.png)  Switching to Zabbix HA is non-committal. You may switch back to standalone  operation at any point.  See also: [Implementation details](#implementation-details)
zh-cn	### 概述  通常高可用性(HA)需要在几乎不需要停机的关键基础设施中使用。为了在服务出现任何失败故障时进行故障转移，进行接管。  Zabbix提供了一个**本地**的高可用性解决方案，方便设置，不需要任何HA专业知识也可以完成。本地Zabbix HA对于防止Zabbix server的软件/硬件故障或减少维护停机时间是有用的。  Zabbix高可用模式下，多台Zabbix server作为集群中的节点运行。 当集群中的一个Zabbix server 处于active 时，其他服务器处于standy，随时准备在必要时接管。  ![](../../../../assets/en/manual/config/zabbix_ha.png)  切换到Zabbix HA还不确定。 您可以在任何时候切换回standalone状态。  参见: [实施详细](#implementation-details)

en-us	#### Overview  History and trends are the two ways of storing collected data in Zabbix.  Whereas history keeps each collected value, trends keep averaged information on hourly basis and therefore are less resource-hungry.
zh-cn	#### 概述  历史数据（history）和趋势数据（trends）是Zabbix中存储收集到的数据的两种方式。  历史数据：每一个收集到的监控数据， 趋势数据：按小时统计计算的平均值数据。

en-us	#### Overview  If you have a network to look after, you may want to have an overview of your infrastructure somewhere. For that purpose, you can create maps in Zabbix - of networks and of anything you like.  All users can create network maps. The maps can be public (available to all users) or private (available to selected users).  Proceed to [configuring a network map](/manual/config/visualization/maps/map).
zh-cn	#### 概述  当你在维护一个网络的时候，你可能想看下整体基础设施的网络拓扑结构。 这种情况下，你可以在Zabbix中创建一个拓扑图来实现，可以是网络和任何相关节点。  所有用户都可以配置网络拓扑图. 拓扑图可以是公开的 (所有用户可见) 或者私有的 (部分用户可见)。  请参照[配置网络拓扑](/manual/config/visualization/maps/map)。

en-us	#### Overview  In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover Windows services.
zh-cn	#### 概述  与 [文件系统](/manual/discovery/low_level_discovery#configuring_low-level_discovery)自动发现相似，Windows服务同样可被Zabbix自动发现.

en-us	#### Overview  In message subjects and message text you can use macros for more efficient problem reporting.  In addition to a number of built-in macros, [user macros](/manual/config/macros/user_macros) and [expression macros](/manual/config/macros/expression_macros) are also supported. A [full list of macros](/manual/appendix/macros/supported_by_location) supported by Zabbix is available.
zh-cn	#### 概述  在消息主题和消息文本中，您可以使用宏来更有效地报告问题。  除了许多内置宏外，还支持 [用户宏](/manual/config/macros/user_macros) 和 [表达式宏](/manual/config/macros/expression_macros)。 Zabbix 支持可用的[宏的完整列表](/manual/appendix/macros/supported_by_location) 。

en-us	#### Overview  In order to use any other language than English in Zabbix web interface, its locale should be installed on the web server. Additionally, the PHP gettext extension is required for the translations to work.
zh-cn	#### 概述  为了在Zabbix Web界面中使用英语以外的任何其他语言，其区域设置应安装在Web服务器上。此外，翻译工作还需要 PHP gettext 扩展。

en-us	#### Overview  In *Reports → Availability report* you can see what proportion of time each trigger has been in problem/ok state. The percentage of time for each state is displayed.  Thus it is easy to determine the availability situation of various elements on your system.  ![](../../../../../assets/en/manual/web_interface/availability_host.png){width="600"}  From the drop-down in the upper right corner, you can choose the selection mode - whether to display triggers by hosts or by triggers belonging to a template.  ![](../../../../../assets/en/manual/web_interface/availability_trigger.png){width="600"}  The name of the trigger is a link to the latest events of that trigger.
zh-cn	 #### 概览  在*报表→ 可用性报表*中，您可以看到每个触发器处于问题/正常状态的时间比例。显示每个状态的时间百分比。  因此，很容易确定系统中各种元素的可用性情况。  ![](../../../../../assets/en/manual/web_interface/availability_host.png){width="600"}  从右上角的下拉列表中，可以选择选择模式-是按主机显示触发器，还是按属于模板的触发器显示触发器。  ![](../../../../../assets/en/manual/web_interface/availability_trigger.png){width="600"}  触发器的名称是指向该触发器最新事件的链接。

en-us	#### Overview  In the *Inventory → Hosts* section [inventory data](/manual/config/hosts/inventory) of hosts are displayed.  You can filter the hosts by host group(s) and by any inventory field to display only the hosts you are interested in.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered.png){width="600"}  To display all host inventories, select no host group in the filter, clear the comparison field in the filter and press "Filter".  While only some key inventory fields are displayed in the table, you can also view all available inventory information for that host. To do that, click on the host name in the first column.
zh-cn	#### 概览  在 *资产记录→ 主机* 将显示主机的 [资产记录信息](/manual/config/hosts/inventory) 。  您可以按主机组和任何资产字段过滤主机，来显示您感兴趣的主机。  ![](../../../../../assets/en/manual/web_interface/inventory_filtered.png){width="600"}  要显示所有主机清单，在组下拉列表中不选择任何主机组，清除过滤器中的比较字段，然后按“过滤器”。  虽然表中只显示了一些关键的资产记录字段，但您也可以查看该主机的所有可用资产信息。如果想这么查看请单击列表中第一列主机名。

en-us	#### Overview  In the *Monitoring → Discovery* section results of [network discovery](/manual/discovery/network_discovery) are shown. Discovered devices are sorted by the discovery rule.  ![](../../../../../assets/en/manual/web_interface/discovery_status0.png){width="600"}  If a device is already monitored, the host name will be listed in the *Monitored host* column, and the duration of the device being discovered or lost after previous discovery is shown in the *Uptime/Downtime* column.  After that follow the columns showing the state of individual services for each discovered device (red cells show services that are down). Service uptime or downtime is included within the cell.  ::: noteimportant Only those services that have been found on at least one device will have a column showing their state. :::
zh-cn	#### 概览  在 *监控→ 自动发现* 这部分，显示[网络发现](/manual/discovery/network_discovery) 的结果。发现的设备按发现规则排序。 ![](../../../../../assets/en/manual/web_interface/discovery_status0.png){width="600"}  如果设备已被监控，主机名将列在 *监控的主机*  列中，以及在_正常运行/停机时间_列中显示发现设备的 *持续时间/发现后的丢失时间*。  之后，请按照列显示每个发现的设备的各个服务的状态(红色单元格显示已关闭的服务)。服务正常运行时间或停机时间都包含在单元中。  ::: noteimportant 这些服务中至少有一个在设备中被发现，才会有显示其状态的列。 :::

en-us	#### Overview  In the *Monitoring → Maps* section you can configure, manage and view [network maps](/manual/config/visualization/maps).  When you open this section, you will either see the last map you accessed or a listing of all maps you have access to.  All maps can be either public or private. Public maps are available to all users, while private maps are accessible only to their owner and the users the map is shared with.
zh-cn	#### 概览  在 监测→ 拓扑图 部分，您可以配置，管理和查看[网络拓扑图](/manual/config/visualization/maps)。  当您打开此部分时，您将看到您访问的最后一张拓扑图或您可以访问的所有拓扑图的列表。 拓扑图列表可以按名称过滤。  所有拓扑图都可以是公共的或私有的。 所有用户都可以使用公共拓扑图，而私有拓扑图只能由其所有者和对其共享的用户访问。

en-us	#### Overview  In the *Reports → Notifications* section a report on the number of notifications sent to each user is displayed.  From the dropdowns in the top right-hand corner you can choose the media type (or all), period (data for each day/week/month/year) and year for the notifications sent.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/reports/notifications.png){width="600"}  Each column displays totals per one system user.
zh-cn	 #### 概览  在*报表 → 通知*部分，将显示发送给每个用户的通知数量的报告。  从右上角的下拉列表中，您可以选择发送通知的媒体类型（或全部）、周期（每天/周/月/年的数据）和年份。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/reports/notifications.png){width="600"}  每列显示每个系统用户的总数。

en-us	#### Overview  In this section we will perform an SNMP [discovery](/manual/discovery/low_level_discovery) on a switch.
zh-cn	#### 概述  本章中会演示如何对交换机执行一次SNMP的 [自动发现](/manual/discovery/low_level_discovery) 。

en-us	#### Overview  In this section you can learn the meaning of some terms commonly used in Zabbix.
zh-cn	#### 概览  在本节中，您可以了解 Zabbix 中一些常用术语的含义。

en-us	#### Overview  In this section, you will learn how to log in and set up a system user in Zabbix.
zh-cn	#### 概述  本章你会学习如何登录Zabbix，以及在Zabbix内创建一个系统用户。

en-us	#### Overview  In this section you will learn how to set up a new host.  A host in Zabbix is a networked entity (physical, virtual) that you wish to monitor. The definition of what can be a "host" in Zabbix is quite flexible. It can be a physical server, a network switch, a virtual machine or some application.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的主机。  Zabbix中的主机是一个你想要监控的网络实体（物理的，或者虚拟的）。Zabbix中，对于主机的定义非常灵活。它可以是一台物理服务器，一个网络交换机，一个虚拟机或者某些应用程序。

en-us	#### Overview  In this section, you will learn how to set up an item.  Items are the basis of gathering data in Zabbix. Without items, there is no data - because only an item defines a single metric or what kind of data to collect from a host.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的监控项。  监控项是Zabbix中采集数据的基础。没有监控项，就没有数据——因为一个主机中只有监控项定义了单一的指标或者需要获得的数据。

en-us	#### Overview  In this section you will learn how to set up a template.  Previously we learned how to set up an item, a trigger and how to get a problem notification for the host.  While all of these steps offer a great deal of flexibility in themselves, it may appear like a lot of steps to take if needed for, say, a thousand hosts. Some automation would be handy.  This is where templates come to help. Templates allow to group useful items, triggers and other entities so that those can be reused again and again by applying to hosts in a single step.  When a template is linked to a host, the host inherits all entities of the template. So, basically a pre-prepared bunch of checks can be applied very quickly.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的模板。  之前我们学习了如何创建监控项、触发器以及如何获取主机的问题通知。  虽然这些步骤提供了很大的灵活性，但仍然需要很多步骤才能完成。如果我们需要配置上千台主机，一些自动化操作会带来更多便利性。  模版功能可以实现这一点。模版允许对有用的监控项、触发器和其他对象进行分组，只需要一步就可以对监控主机应用模版，以达到重复使用的目的。  当一个模版链接到一个主机后，主机会继承这个模版中的所有对象。简单而言，一组预先定义好的检查会被快速应用到主机上。

en-us	#### Overview  In this section you will learn how to set up a trigger.  Items only collect data. To automatically evaluate incoming data we need to define triggers. A trigger contains an expression that defines a threshold of what is an acceptable level for the data.  If that level is surpassed by the incoming data, a trigger will "fire" or go into a 'Problem' state - letting us know that something has happened that may require attention. If the level is acceptable again, trigger returns to an 'Ok' state.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的触发器。  监控项只是用于收集数据. 如果需要自动评估收到的数据，我们需要定义触发器。触发器包含了一个表达式，这个表达式定义了数据的可接受的阈值级别。  如果收到的数据超过了这个定义好的级别，触发器将被“触发”，或者进入“问题”状态——从而引起我们的注意，让我们知道有问题发生。如果数据再次恢复到合理的范围，触发器将返回“ok”状态。

en-us	 ### Overview   In Zabbix 6.0, [service monitoring](/manual/it_services) functionality has been reworked significantly (see [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction/whatsnew600#services) for the list of changes).   This page describes how services and SLAs, defined in earlier Zabbix versions, are changed during an upgrade to Zabbix 6.0 or newer.
zh-cn	 ### 概览   在 Zabbix 6.0 中，[服务监控](/manual/it_services) 功能进行了重大修改（参见 [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction /whatsnew600#services）以获取更改列表）。  此页面描述了在升级到 Zabbix 6.0 或更新版本期间如何更改早期 Zabbix 版本中定义的服务和 SLA。

en-us	#### Overview  It is possible to automatically discover IPMI sensors.  To do that, you may use a combination of:  -   the `ipmi.get` IPMI item (supported since Zabbix **5.0.0**) as the     master item -   dependent low-level discovery rule and item prototypes
zh-cn	#### 概述  IPMI传感器可被自动发现.  要实现此功能, 可结合使用:  -   IPMI监控项 `ipmi.get`  (从Zabbix **5.0.0**起支持) 作为主监控项 -   依赖型的低级别自动发现规则和低级别自动发现监控项原型

en-us	#### Overview  It is possible to create custom rules regarding the times when an item is checked. The two methods for that are *Flexible intervals*, which allow to redefine the default update interval, and *Scheduling*, whereby an item check can be executed at a specific time or sequence of times.
zh-cn	#### 概述  有两种方法可以创建检查监控项的时间的自定义规则。 *灵活间隔*，允许重新定义默认更新间隔；*调度*，可以在特定时间或时间序列执行监控项检查。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) all interfaces configured in Zabbix frontend for a host.
zh-cn	#### 概述  在Zabbix前端页面中配置的所有主机接口都可以[自动发现](/manual/discovery/low_level_discovery)。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) all JMX MBeans or MBean attributes or to specify a pattern for the discovery of these objects.  It is mandatory to understand the difference between an MBean and MBean attributes for discovery rule configuration. An MBean is an object which can represent a device, an application, or any resource that needs to be managed.  For example, there is an MBean which represents a web server. Its attributes are connection count, thread count, request timeout, http file cache, memory usage, etc. Expressing this thought in human comprehensive language we can define a coffee machine as an MBean which has the following attributes to be monitored: water amount per cup, average consumption of water for a certain period of time, number of coffee beans required per cup, coffee beans and water refill time, etc.
zh-cn	#### 概述   可以 [自动发现](/manual/discovery/low_level_discovery) 所有 JMX MBean或MBean属性，也可以为这些对象的自动发现指定一个样式。  有必要理解自动发现规则配置中的MBean和MBean属性之间的区别。MBean是一个对象，代表一个设备、一个应用程序或任何需要管理的资源。  例如，有一个MBean，用来表示一个web服务器。其属性有连接数、线程数、请求超时时间、HTTP文件缓存大小、内存使用率等。用通俗语言来类比一下，可以把一台咖啡机定义成一个MBean，有这些属性会被监控：每杯的水量、某段时间平均消耗水量、每杯所需咖啡豆数量、咖啡豆和水的重新装填时间等。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery#configuring_low-level_discovery) object instances of Windows performance counters. This is useful for multi-instance performance counters.
zh-cn	#### 概述  支持对Windows性能计数器的实例进行[自动发现](/manual/discovery/low_level_discovery#configuring_low-level_discovery)。 此特性对于多实例性能计数器很有用。

en-us	### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) systemd units (services, by default) with Zabbix.
zh-cn	#### 概述  系统单元 (服务, 默认设置)可被Zabbix [自动发现](/manual/discovery/low_level_discovery).

en-us	#### Overview  It is possible to make some internal metrics of Zabbix server and proxy accessible remotely by another Zabbix instance or a third-party tool. This can be useful so that supporters/service providers can monitor their client Zabbix servers/proxies remotely or, in organizations where Zabbix is not the main monitoring tool, that Zabbix internal metrics can be monitored by a third-party system in an umbrella-monitoring setup.  Zabbix internal stats are exposed to a configurable set of addresses listed in the new 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter. Requests will be accepted only from these addresses.
zh-cn	#### 概述  可以通过另一个 Zabbix 实例或第三方工具远程访问 Zabbix 服务器和代理的一些内部指标。这可能很有用，以便支持者/服务提供商可以远程监控他们的客户端 Zabbix 服务器/代理，或者在组织中 Zabbix 不是主要的监控工具，Zabbix 内部指标可以在伞式监控设置中由第三方系统监控。  Zabbix 内部统计信息暴露给新的“StatsAllowedIP”[server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 参数中列出的一组可配置地址。 仅接受来自这些地址的请求。

en-us	#### Overview  JMX monitoring can be used to monitor JMX counters of a Java application.  JMX monitoring has native support in Zabbix in the form of a Zabbix daemon called "Zabbix Java gateway", introduced since Zabbix 2.0.  To retrieve the value of a particular JMX counter on a host, Zabbix server queries the Zabbix **Java gateway**, which in turn uses the [JMX management API](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/) to query the application of interest remotely.  For more details and setup see the [Zabbix Java gateway](/manual/concepts/java) section.  ::: notewarning Communication between Java gateway and the monitored JMX application should not be firewalled. :::
zh-cn	#### 概述  JMX监控端可用于监控Java应用程序的JMX计数器。  从zabbix 2.0开始，JMX监控端以Zabbix守护进程的形式运行，称为“Zabbix Java gateway”。  为了检索主机上特定JMX计数器的值，Zabbix服务器查询Zabbix **Java gateway**，网关使用[JMX管理API](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/)远程查询指定的应用程序，将结果返回给zabbix server。  有关更多细节和设置，请参考 [Zabbix Java gateway](/manual/concepts/java)。  ::: notewarning Java gateway和JMX应用程序之间的通信应该在防火墙上放行。 :::

en-us	#### Overview  Kerberos authentication can be used in web monitoring and HTTP items in Zabbix since version 4.4.0.  This section describes an example of configuring Kerberos with Zabbix server to perform web monitoring of `www.example.com` with user 'zabbix'.
zh-cn	#### 概述  zabbix 4.4.0之后版本，Kerberos身份验证可用于Zabbix中的web监视和HTTP监控项。  这部分Kerberos配置描述Zabbix server使用'zabbix'用户对`www.example.com`进行web监控

en-us	#### Overview  Macro functions offer the ability to customize [macro](/manual/config/macros) values.  Sometimes a macro may resolve to a value that is not necessarily easy to work with. It may be long or contain a specific substring of interest that you would like to extract. This is where macro functions can be useful.  The syntax of a macro function is:      {<macro>.<func>(<params>)}  where:  -   <macro> - the macro to customize (for example {ITEM.VALUE} or     {\#LLDMACRO}) -   <func> - the function to apply -   <params> - a comma-delimited list of function parameters.     Parameters must be quoted if they start with '' '' (space), `"` or     contain `)`, `,`.  For example:      {{TIME}.fmttime(format,time_shift)}     {{ITEM.VALUE}.regsub(pattern, output)}     {{#LLDMACRO}.regsub(pattern, output)}
zh-cn	#### 概述  宏函数提供自定义[Macro]（/manual/config/macros）值的功能。  有时宏可能解析为一个不一定容易使用的值。它可能很长，或者包含您想要提取的特定感兴趣的子字符串。这就是宏函数可以发挥作用的地方。  宏函数的语法是：      {<macro>.<func>(<params>)}  其中：  - <macro> - 要自定义的宏（例如{ITEM.VALUE}或{\#LLDMACRO}） - <func> - 要应用的函数 - <params> - 以逗号分隔的函数参数列表。如果参数以“'”（空格）、“或包含”开头，则必须将其引用。  例如：      {{TIME}.fmttime(format,time_shift)}     {{ITEM.VALUE}.regsub(pattern, output)}     {{#LLDMACRO}.regsub(pattern, output)}

en-us	#### Overview  Media types are [exported](/manual/xml_export_import) with all related objects and object relations.
zh-cn	#### 概述  媒介类型是与所有相关对象和对象关系一起[导出](/manual/xml_export_import)的

en-us	#### Overview  Most Zabbix web interface pages support various HTTP GET parameters that control what will be displayed. They may be passed by specifying parameter=value pairs after the URL, separated from the URL by a question mark (?) and from each other by ampersands (&).
zh-cn	#### 概述  大多数 Zabbix Web 界面页面都支持各种 HTTP GET 参数来控制显示的内容。 它们可以通过在 URL 之后指定“参数=值“对来传递，通过问号 (?) 与 URL 隔开，并通过与号 (&) 彼此隔开。

en-us	#### Overview  ODBC monitoring corresponds to the *Database monitor* item type in the Zabbix frontend.  ODBC is a C programming language middle-ware API for accessing database management systems (DBMS). The ODBC concept was developed by Microsoft and later ported to other platforms.  Zabbix may query any database, which is supported by ODBC. To do that, Zabbix does not directly connect to the databases, but uses the ODBC interface and drivers set up in ODBC. This function allows for more efficient monitoring of different databases for multiple purposes - for example, checking specific database queues, usage statistics and so on. Zabbix supports unixODBC, which is one of the most commonly used open source ODBC API implementations.  ::: noteimportant See also the [known issues](/manual/installation/known_issues#odbc_checks) for ODBC checks. :::
zh-cn	#### 概述  ODBC监控对应于Zabbix前端中的 *数据库监控* 监控项类型。  ODBC是C语言编写的中间件API，用于访问数据库管理系统(DBMS)。 ODBC是由Microsoft开发的，后来被移植到了其它平台。  Zabbix可以查询任何支持ODBC的数据库。实现这个目标，Zabbix不直接连接数据库，而是使用ODBC接口并在ODBC中设置的驱动程序。该功能允许出于多种目的，更加有效地监视不同的数据库。例如，检测特定的数据库队列、使用统计信息等。Zabbix支持unixODBC，是最常用的开源ODBC API实现之一。  ::: noteimportant 更多信息请查看 ODBC检查的 [已知问题](/manual/installation/known_issues#odbc_checks) 。 :::

en-us	#### Overview  [Perl Compatible Regular Expressions](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE, PCRE2) are supported in Zabbix.  There are two ways of using regular expressions in Zabbix:  -   manually entering a regular expression -   using a global regular expression created in Zabbix
zh-cn	#### 概述  Zabbix支持 [Perl兼容正则表达式](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions)（PCRE, PCRE2）。  Zabbix 中使用正则表达式有两种方式：  -   手动输入正则表达式 -   使用在 Zabbix 中创建的全局正则表达式

en-us	#### Overview  Receiving SNMP traps is the opposite to querying SNMP-enabled devices.  In this case, the information is sent from an SNMP-enabled device and is collected or "trapped" by Zabbix.  Usually, traps are sent upon some condition change and the agent connects to the server on port 162 (as opposed to port 161 on the agent side that is used for queries). Using traps may detect some short problems that occur amidst the query interval and may be missed by the query data.  Receiving SNMP traps in Zabbix is designed to work with **snmptrapd** and one of the mechanisms for passing the traps to Zabbix - either a Bash or Perl script or SNMPTT.  ::: noteclassic The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT are often missing in modern distributions and require more complex configuration. However, this solution uses a script configured as `traphandle`. For better performance on production systems, use the embedded Perl solution (either script with `do perl` option or SNMPTT). :::  The workflow of receiving a trap:  1.  `snmptrapd` receives a trap 2.  `snmptrapd` passes the trap to the receiver script (Bash, Perl)      or SNMPTT 3.  The receiver parses, formats and writes the trap to     a file 4.  Zabbix SNMP trapper reads and parses the trap file 5.  For each trap Zabbix finds all "SNMP trapper" items with host     interfaces matching the received trap address. Note that only the     selected "IP" or "DNS" in host interface is used during the     matching. 6.  For each found item, the trap is compared to regexp in     `snmptrap[regexp]`. The trap is set as the value of **all**     matched items. If no matching item is found and there is an     `snmptrap.fallback` item, the trap is set as the value of that. 7.  If the trap was not set as the value of any item, Zabbix by default     logs the unmatched trap. (This is configured by "Log unmatched SNMP     traps" in Administration → General → Other.)
zh-cn	#### 概述  接收 SNMP 陷阱与查询启用 SNMP 的设备相反。  在这种情况下，信息是从支持 SNMP 的设备发送的，并且是被 Zabbix 收集或“捕获”。  通常，在某些条件更改时会发送陷阱，并且客户端的 162端口 连接到服务器（与用于查询客户端的端口 161 不同）。使用陷阱可能会检测到在查询间隔中发生的一些短期问题，并且可能会遗漏查询数据。  在 Zabbix 中接收 SNMP 陷阱要与 **snmptrapd** 一起使用，以及将snmp陷阱传递给 Zabbix 的机制之一，Bash 或 Perl 脚本或 SNMPTT 。  ::: noteclassic 配置Zabbix后设置trap监控最简单的方法是使用Bash脚本方案，因为Perl和SNMPTT在现代发行版中经常缺失，需要更复杂的配置。但是，该方案使用配置为`traphandle`的脚本。为了在生产系统上获得更好的性能，请使用嵌入式 Perl 解决方案（带有“do perl”选项的脚本或 SNMPTT）。 ::::  接收陷阱的工作流程：  1. `snmptrapd` 收到陷阱 2. `snmptrapd` 将陷阱传递给接收器脚本（Bash、Perl）或 SNMPTT 3. 接收方解析、格式化并将trap写入文件 4. Zabbix SNMP trapper读取并解析trap文件 5. 对于每个陷阱，Zabbix 会找到主机接口与接收到的陷阱地址匹配的所有“SNMP trapper”监控项。 请注意，在匹配过程中，只会使用在主机界面中选择的“IP”或“DNS”。 6. 对于每个找到的项目，将陷阱与 `snmptrap[regexp]` 中的正则表达式进行比较。陷阱设置为 **all** 的匹配的监控项值。如果没有找到匹配的监控项并且有“snmptrap.fallback”监控项，陷阱设置为那个值。 7. 如果陷阱没有设置为任何项的值，Zabbix 默认记录不匹配的陷阱。 （这是通过管理 → 一般 → 其他中的“记录不匹配的 SNMP 陷阱”配置的。）

en-us	### Overview  Recovery operations allow you to be notified when problems are resolved.  Both messages and remote commands are supported in recovery operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously.
zh-cn	### 概述  恢复操作允许您在问题得到解决时收到通知。  恢复操作支持消息和远程命令。 虽然可以添加多个操作，但不支持升级 - 所有操作都分配给一个步骤，因此将同时执行。

en-us	#### Overview  Server - proxy data exchange is based on JSON format.  Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen).
zh-cn	#### 概述  Server - proxy 数据交换基于 JSON 格式.  请求和响应消息必须以[header头部与数据长度](/manual/appendix/protocols/header_datalen)开头.

en-us	#### Overview  Several configuration [parameters](/manual/appendix/config/zabbix_server) define how Zabbix server should behave when an agent check (Zabbix, SNMP, IPMI, JMX) fails and a host interface becomes unreachable.
zh-cn	#### 概述  当agent检查(Zabbix, SNMP, IPMI, JMX)失败并且主机变得不可达时，一些配置  [参数](/manual/appendix/config/zabbix_server) 定义了 Zabbix server 作何反应。

en-us	#### Overview  Simple graphs are provided for the visualization of data gathered by items.  No configuration effort is required on the user part to view simple graphs. They are freely made available by Zabbix.  Just go to *Monitoring → Latest data* and click on the Graph link for the respective item and a graph will be displayed.  ![](../../../../../assets/en/manual/config/simple_graph.png){width="600"}  ::: noteclassic Simple graphs are provided for all numeric items. For textual items, a link to History is available in *Monitoring → Latest data*. :::
zh-cn	#### 概览  提供了简单的图表，用于可视化监控项收集的数据。  用户部分无需配置工作即可查看简单图表。它们由 Zabbix 免费提供。  只需转到 *监控→ 最新数据* 并单击图表 链接将显示相应的监控项和图表。  ![](../../../../../assets/en/manual/config/simple_graph.png){width="600"}  ::: noteclassic 为所有数值型监控项提供了简单的图表。为了文本监控项，历史链接在 *监控 → 最新数据*中是可用的。 :::

en-us	### Overview  Since Zabbix 6.0, primary keys are used for all tables in  new installations.  This section provides instructions for manually upgrading the history tables in existing installations to primary keys.  Instructions are available for:  * [MySQL](#mysql) * [PostgreSQL](#postgresql) * [TimescaleDB](#postgresql-timescaledb) * [Oracle](#oracle)
zh-cn	#### 概述  自Zabbix 6.0起，主键会应用于新安装 Zabbix 数据库的所有表。  在这之前安装过的Zabbix，本章节将提供手动升级所有表主键的说明。  此章节适用于如下数据库:  * [MySQL](#mysql) * [PostgreSQL](#postgresql) * [TimescaleDB](#postgresql-timescaledb) * [Oracle](#oracle)

en-us	#### Overview  Some new items are automatically added for monitoring when web scenarios are created.  All items inherit tags from the web scenario.
zh-cn	#### 概述  创建 Web 场景时会自动添加一些新的监控项以进行监控。  所有监控项都从 Web 场景继承标签。

en-us	#### Overview  Sometimes you may want to change some attribute for a number of items at once. Instead of opening each individual item for editing, you may use the mass update function for that.
zh-cn	#### 概览  有时你可能想要一次更改多个监控项的某些属性。你可以使用批量更新功能，而不是打开每个独立的监控项进行编辑。\

en-us	#### Overview  Sometimes you may want to change some attribute for a number of templates at once. Instead of opening each individual template for editing, you may use the mass update function for that.
zh-cn	 #### 概览  有时您可能想要同时更改多个模板的某些属性。您可以使用批量更新功能，无需打开每个模板进行独立编辑。

en-us	#### Overview  Telnet checks are performed as agent-less monitoring. Zabbix agent is not needed for Telnet checks.
zh-cn	#### 概述  Telnet检查不需要安装Zabbix agent，可对未安装代理的主机进行监控。

en-us	#### Overview  The *Administration → General* section contains a number of subsections for setting frontend-related defaults and customizing Zabbix.  The list of available subsections appears upon pressing on *General* in the *Administration* menu section. It is also possible to switch between subsections by using the title dropdown in the top left corner.
zh-cn	#### 概述  *Administration → General* 部分包含许多子部分，用于设置与前端相关的默认值和自定义 Zabbix。  按下 *Administration* 菜单部分中的 *General* 后，可用子部分的列表出现。 也可以使用左上角的标题下拉菜单在小节之间切换。

en-us	#### Overview  The expressions used in [triggers](/manual/config/triggers) are very flexible. You can use them to create complex logical tests regarding monitored statistics.  A simple expression uses a **function** that is applied to the item with some parameters. The function returns a result that is compared to the threshold, using an operator and a constant.  The syntax of a simple useful expression is `function(/host/key,parameter)<operator><constant>`.  For example:        min(/Zabbix server/net.if.in[eth0,bytes],5m)>100K  will trigger if the number of received bytes during the last five minutes was always over 100 kilobytes.  While the syntax is exactly the same, from the functional point of view there are two types of trigger expressions:  -   problem expression - defines the conditions of the problem -   recovery expression (optional) - defines additional conditions of     the problem resolution  When defining a problem expression alone, this expression will be used both as the problem threshold and the problem recovery threshold. As soon as the problem expression evaluates to TRUE, there is a problem. As soon as the problem expression evaluates to FALSE, the problem is resolved.  When defining both problem expression and the supplemental recovery expression, problem resolution becomes more complex: not only the problem expression has to be FALSE, but also the recovery expression has to be TRUE. This is useful to create [hysteresis](#hysteresis) and avoid trigger flapping.
zh-cn	 #### 概览  [triggers(触发器)](/manual/config/triggers) 中使用的表达式非常灵活。 您可以使用它们来创建复杂的逻辑测试 监控统计。  一个简单的表达式使用 **function（函数）** 应用于监控项的 一些参数。该函数返回一个与阈值比较后的结果，使用运算符和常数。  一个简单有用的表达式的语法是 `function(/host/key,parameter)<operator><constant>`.  例如:        min(/Zabbix server/net.if.in[eth0,bytes],5m)>100K 如果在最后五分钟期间接收到的网络字节数最小值超过 100 KB 将触发。  虽然语法完全相同，但从功能的角度来看 有两种类型的触发器表达式：  -  问题表达 - 定义问题的条件 -  恢复表达式（可选） - 定义附加条件 问题解决  当单独定义问题表达式时，该表达式将同时用作问题阈值和问题恢复阈值。只要问题表达式的计算结果为TRUE，就会出现问题。只要问题表达式的计算结果为FALSE，问题就解决了。  当定义问题表达式和补充恢复表达式时，问题解决将变得更加复杂:不仅问题表达式必须为FALSE，而且恢复表达式也必须为TRUE。这对于创建[hysteresis滞后](#hysteresis)和避免触发器振荡非常有用。

en-us	#### Overview  The header is present in all request and response messages between Zabbix components.  It is required to determine the message length, if it is compressed or not, if it is a large packet or not.  Zabbix communications protocol has 1GB packet size limit per connection. The limit of 1GB  is applied to both the received packet data length and the uncompressed data length.  When sending configuration to Zabbix proxy, the packet size limit is increased to 4GB to allow  syncing large configurations. When data length before compression exceeds 4GB, Zabbix server automatically  starts using the large packet format (0x04 flag) which increases the packet size limit to 16GB.  Note that while a large packet format can be used for sending any data, currently only the Zabbix proxy  configuration syncer can handle packets that are larger than 1GB.
zh-cn	#### 概述  标头存在于Zabbix组件之间的所有请求和响应消息中。需要确定消息长度，是否压缩，是否为大数据包。  Zabbix 通信协议每个连接的数据包大小限制为 1GB。 1GB 的限制适用于接收到的数据包数据长度和未压缩的数据长度。  将配置发送到 Zabbix 代理时，数据包大小限制增加到 4GB 以允许同步大型配置。 当压缩前的数据长度超过 4GB 时，Zabbix 服务器自动开始使用大数据包格式（0x04 标志），将数据包大小限制增加到 16GB。  请注意，虽然大数据包格式可用于发送任何数据，但目前只有 Zabbix 代理配置同步器可以处理大于 1GB 的数据包。

en-us	#### Overview  The Inventory menu features sections providing an overview of host inventory data by a chosen parameter as well as the ability to view host inventory details.
zh-cn	#### 概览  "资产清单"菜单的特点是，通过选择的参数提供主机资产数据的概览，以及查看主机资产详细信息的能力。

en-us	#### Overview  The *Inventory → Overview* section provides ways of having an overview of [host inventory](/manual/config/hosts/inventory) data.  For an overview to be displayed, choose host groups (or none) and the inventory field by which to display data. The number of hosts corresponding to each entry of the chosen field will be displayed.  ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  The completeness of an overview depends on how much inventory information is maintained with the hosts.  Numbers in the *Host count* column are links; they lead to these hosts being filtered out in the *Host Inventories* table.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}
zh-cn	#### 概览 *资产记录 →  概览*部分提供了有关[主机资产](/manual/config/hosts/inventory)数据概览的方法。  要显示的概览，请选择一个主机组（或所有组）和显示数据的资产字段。将显示与所选字段的每个条目相对应的主机数量。 ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  概览的完整性取决于维护了多少主机资产信息。  *主机计数* 列中的数字是链接; 它们导致这些主机在 *主机资产* 表中被过滤掉。 ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}

en-us	#### Overview  The **memtype** parameter is supported on Linux, AIX, FreeBSD, and Solaris platforms.  Three common values of 'memtype' are supported on all of these platforms: `pmem`, `rss` and `vsize`. Additionally, platform-specific 'memtype' values are supported on some platforms.
zh-cn	#### 概述  Linux, AIX, FreeBSD 和 Solaris 都支持**memtype**参数。  'memtype' 参数的三个常用值  `pmem`,  `rss`  和  `vsize`在所有系统中都适用。另外, 在一些系统中只支持该系统下的 'memtype' 值。

en-us	#### Overview  The Monitoring menu is all about displaying data. Whatever information Zabbix is configured to gather, visualize and act upon, it will be displayed in the various sections of the Monitoring menu.
zh-cn	#### 概述  监测菜单的作用是显示数据。任何Zabbix采集、可视化和操作的信息都会在监测菜单的各个部件中显示。

en-us	#### Overview  The queue displays items that are waiting for a refresh. The queue is just a **logical** representation of data. There is no IPC queue or any other queue mechanism in Zabbix.  Items monitored by proxies are also included in the queue - they will be counted as queued for the proxy history data update period.  Only items with scheduled refresh times are displayed in the queue. This means that the following item types are excluded from the queue:  -   log, logrt and event log active Zabbix agent items -   SNMP trap items -   trapper items -   web monitoring items -   dependent items  Statistics shown by the queue is a good indicator of the performance of Zabbix server.  The queue is retrieved directly from Zabbix server using JSON protocol. The information is available only if Zabbix server is running.
zh-cn	#### 概览  队列显示正在等待刷新的监控项。队列只是数据的一种 **逻辑**上表现。ZABBIX中并没有IPC队列或者其它任何队列的机制。\  由Proxy们监控的监控项也会被包含在队列中 -这些监控项将按Proxy历史数据更新周期被计数为队列。  只有具有刷新时间计划的监控项才会记录在队列中。也就是说队列中将不包含以下的监控项类型：  -   log, logrt 和event log (Active Agent) -   SNMP trap 监控项 -   trapper 监控项 -   web监控监控项 -   有依赖的监控项  队列显示的统计信息是ZABBIX Server是否健康的指标。  使用JSON协议直接从ZABBIX Server 检索队列。这个页面的信息只在ZABBIX Server运行时可用。

en-us	#### Overview  There are situations when one item gathers multiple metrics at a time or it even makes more sense to collect related metrics simultaneously, for example:  -   CPU utilization of individual cores -   Incoming/outgoing/total network traffic  To allow for bulk metric collection and simultaneous use in several related items, Zabbix supports dependent items. Dependent items depend on the master item that collects their data simultaneously, in one query. A new value for the master item automatically populates the values of the dependent items. Dependent items cannot have a different update interval than the master item.  Zabbix preprocessing options can be used to extract the part that is needed for the dependent item from the master item data.  Preprocessing is managed by a `preprocessing manager` process, which has been added in Zabbix 3.4, along with workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is used between data gatherers (pollers, trappers, etc) and the preprocessing process.  Zabbix server or Zabbix proxy (if host is monitored by proxy) are performing preprocessing steps and processing dependent items.  Item of any type, even dependent item, can be set as master item. Additional levels of dependent items can be used to extract smaller parts from the value of an existing dependent item.
zh-cn	#### 概述  有时一个监控项一次会收集多个指标，或者同时收集相关的指标会更有意义，例如：  -   单个内核的CPU利用率 -   输入/输出的总网络流量  为了允许进行批量指标收集和同时使用几个相关监控项，Zabbix支持从属监控项。从属监控项依赖于主要监控项包含从属监控项的一次查询，主要监控项的新值会用于自动填充从属监控项的值。从属监控项的更新间隔与主要监控项相同且不可变。  Zabbix预处理选项可用于从主要监控项的数据中，提取从属监控项所需部分的值。  预处理是由一个“预处理管理器”进程管理的，它被添加于Zabbix 3.4版本中，与worker进程一起执行预处理步骤。所有来自不同数据收集器的值（不管是否有预处理步骤），在添加到历史缓存之前，都要经过预处理管理器。基于套接字的IPC连接用于数据收集器(pollers, trappers等)和预处理进程之间的通讯。  只有Zabbix server 或 Zabbix proxy ( 如果主机被Zabbix proxy 监控) 执行预处理步骤，并处理从属监控项。  任何类型的监控项，甚至是从属监控项，都可以设置为主要监控项。额外级别的从属监控项可以被用来从现有的从属监控项中提取出更小的值。

en-us	#### Overview  There is an option to tag various entities in Zabbix. Tags can be defined for:  -   templates -   hosts -   items -   web scenarios -   triggers -   services -   template items and triggers -   host, item and trigger prototypes  Tags have several uses, most notably, to mark events. If entities are tagged, the corresponding new events get marked accordingly:  -   with tagged templates - any host problems created by relevant     entities (items, triggers, etc) from this template will be marked -   with tagged hosts - any problem of the host will be marked -   with tagged items, web scenarios - any data/problem of this item or     web scenario will be marked -   with tagged triggers - any problem of this trigger will be marked  A problem event inherits all tags from the whole chain of templates, hosts, items, web scenarios, triggers. Completely identical `tag:value` combinations (after resolved macros) are merged into one rather than being duplicated, when marking the event.  Having custom event tags allows for more flexibility. Importantly, events can be [correlated](/manual/config/event_correlation) based on event tags. In other uses, actions can be defined based on tagged events. Item problems can be grouped based on tags. Problem tags can also be used to map problems to [services](/manual/it_services/service_tree#problem-tags).  Tagging is realized as a pair of *tag name* and *value*. You can use only the name or pair it with a value:      MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High   An entity (template, host, item, web scenario, trigger or event) may be tagged with the same name, but different values - these tags will not be considered 'duplicates'. Similarly, a tag without value and the same tag with value can be used simultaneously.
zh-cn	#### 概览  Zabbix 中有一个选项可以标记各种实体。标签可以定义为：  - 模板 - 主机 -  监控项 - 网络场景 - 触发器 - 模板项目和触发器 - 主机、监控项和触发器原型  标签有多种用途，最明显的是标记事件。如果实体被标记，相应的新事件也会被标记：  - 带有标记的模板 - 所有由此模板相关实例(监控项、触发器等)创建的主机问题都会被标记。 - 带有标记的主机 - 主机的所有问题都将被标记 - 带有标记的项目、网络场景 - 该监控项的所有数据/问题或web场景将被标记 - 带有标记的触发器 - 此触发器的所有问题都将被标记  一个问题事件继承了整个模板链中的所有标签，主机、监控项、Web 场景、触发器。当标记事件时，完全相同的`tag:value`组合（在解析宏之后）合并为一个而不是被复制。  拥有自定义事件标签可以提供更大的灵活性。特别是事件可以基于 [相关](/manual/config/event_correlation)事件标签。在其他用途中，可以根据标记定义操作事件。监控项问题可以根据标签进行分组。  标记实现为一对 *tag name* 和 *value*。您可以仅使用名称或将其与值配对：     MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High  一个实体（模板、主机、监控项、Web 场景、触发器或事件）可能是使用相同名称但值不同的标签 - 这些标签不会被认为是“重复”。同样，一个没有值的标签和同一个标签值可以同时使用。

en-us	#### Overview  The Reports menu features several sections that contain a variety of predefined and user-customizable reports focused on displaying an overview of such parameters as system information, triggers and gathered data.
zh-cn	#### 概览  “报表”菜单包含多个部分，其中包含各种预定义和用户可自定义的报告，这些报告侧重于显示系统信息，触发器和收集数据等参数的概括。

en-us	#### Overview  The Services menu is for the [service monitoring](/manual/it_services) functions of Zabbix.
zh-cn	#### 概述  本菜单是展示 Zabbix  Services [service monitoring](/manual/it_services) 功能。

en-us	### Overview  The VMware performance counter path has the `group/counter[rollup]` format where:  -   `group` - the performance counter group, for example *cpu* -   `counter` - the performance counter name, for example *usagemhz* -   `rollup` - the performance counter rollup type, for example     *average*  So the above example would give the following counter path: `cpu/usagemhz[average]`  The performance counter group descriptions, counter names and rollup types can be found in [VMware documentation](https://developer.vmware.com/apis/968).  It is possible to obtain internal names and create custom performance counter names by using script item in Zabbix.
zh-cn	### 概述  VMware 性能计数器路径具有`group/counter[rollup]` 格式，其中：  - `group` - 性能计数器组，例如 *cpu* - `counter` - 性能计数器名称，例如 *usagemhz* - `rollup` - 性能计数器汇总类型，例如 *平均*  所以上面的例子会给出以下计数器路径： `cpu/usagemhz[average]`  性能计数器组描述、计数器名称和汇总类型可以在 [VMware文档](https://developer.vmware.com/apis/968)中找到。  可以通过使用 Zabbix 中的脚本监控项来获取内部名称并创建自定义性能计数器名称。

en-us	### Overview  This section allows to view and [configure](/manual/it_services/sla) SLAs.
zh-cn	 ### 概述  本节允许查看和 [配置](/manual/it_services/sla) SLA。

en-us	#### Overview  This section contains a list of locations, where [user-definable](/manual/config/macros/user_macros) macros are supported.  ::: noteclassic  Only global-level user macros are supported for *Actions*, *Network discovery*, *Proxies* and all locations listed under *Other locations* section of this page. In the mentioned locations, host-level and template-level macros will not be resolved.  :::
zh-cn	#### 概述  [用户自定义](/manual/config/macros/user_macros) 宏可以用于以下场景。  ::: noteclassic  *动作*、*网络发现*、*Proxies*以及本页 *其他位置*下列出的内容仅支持全局级用户宏。在这些提到的位置，主机级和模板级宏将不会被解析。 :::

en-us	#### Overview  This section contains descriptions of configuration file parameters for Zabbix agent 2 plugins. Please use the sidebar to access information about the specific plugin.
zh-cn	#### 概述  本节包含Zabbix agent 2插件配置文件参数的说明。请使用侧边栏访问有关特定插件的信息。

en-us	#### Overview  This section contains instructions for creating Oracle database and configuring connections between the database and Zabbix server, proxy, and frontend.
zh-cn	#### 概述  本节包含有关创建 Oracle 数据库以及配置数据库与 Zabbix server、proxy 和 agent 之间的连接的说明。

en-us	### Overview  This section describes a simple setup for monitoring Zabbix high availability cluster as a service.
zh-cn	### 概述  此章节展示了监控Zabbix高可用集群作为服务的一个简单配置示例。

en-us	#### Overview  This section lists parameters supported in the Ceph Zabbix agent 2 plugin configuration file (ceph.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了Zabbix agent 2的Ceph插件配置文件(ceph.conf)中所有支持的参数。请注意：  -   默认值表示的是进程默认值，而不是附带的配置文件中的值； -   Zabbix仅支持UTF-8编码格式的配置文件，不支持 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark)； -   只支持在行首以“\#”开头来注释。

en-us	#### Overview  This section lists parameters supported in the Docker Zabbix agent 2 plugin configuration file (docker.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了Zabbix agent 2的Docker插件配置文件(docker.conf)中所有支持的参数。请注意：  -   默认值表示的是进程默认值，而不是附带的配置文件中的值； -   Zabbix仅支持UTF-8编码格式的配置文件，不支持 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark)； -   只支持在行首以“\#”开头来注释。

en-us	#### Overview  This section lists parameters supported in the Memcached Zabbix agent 2 plugin configuration file (memcached.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了 Memcached Zabbix agent 2 插件配置文件 (memcached.conf) 中支持的参数。注意：  - 默认值反映的是进程默认值，而不是附带的配置文件中的值； - Zabbix 仅支持不带[BOM](https://en.wikipedia.org/wiki/Byte_order_mark)的 UTF-8 编码的配置文件； - 仅支持在行首以"\#"开头的注释。

en-us	#### Overview  This section lists parameters supported in the Modbus Zabbix agent 2 plugin configuration file (modbus.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了Zabbix agent 2的Modbus插件配置文件(modbus.conf)中所有支持的参数。请注意：  - 默认值表示的是进程默认值，而不是附带的配置文件中的值； - Zabbix 仅支持不带[BOM](https://en.wikipedia.org/wiki/Byte_order_mark)的 UTF-8 编码的配置文件； - 仅支持在行首以"\#"开头的注释。

en-us	#### Overview  This section lists parameters supported in the MQTT Zabbix agent 2 plugin configuration file (mqtt.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了Zabbix agent 2的MQTT插件配置文件(mqtt.conf)中所有支持的参数。请注意：  - 默认值表示的是进程默认值，而不是附带的配置文件中的值； - Zabbix 仅支持不带[BOM](https://en.wikipedia.org/wiki/Byte_order_mark)的 UTF-8 编码的配置文件； - 仅支持在行首以"\#"开头的注释。

en-us	#### Overview  This section lists parameters supported in the MySQL Zabbix agent 2 plugin configuration file (mysql.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  本节列出了Zabbix agent 2的MySQL插件配置文件(mysql.conf)中所有支持的参数。请注意：  - 默认值表示的是进程默认值，而不是附带的配置文件中的值； - Zabbix 仅支持不带[BOM](https://en.wikipedia.org/wiki/Byte_order_mark)的 UTF-8 编码的配置文件； - 仅支持在行首以"\#"开头的注释。

en-us	#### Overview  This section presents a step-by-step real-life example of how web monitoring can be used.  Let's use Zabbix web monitoring to monitor the web interface of Zabbix. We want to know if it is available, provides the right content and how quickly it works. To do that we also must log in with our user name and password.
zh-cn	#### 概述  本节介绍使用 Web 监控的分步真实示例。  让我们使用 Zabbix web 监控来监控 Zabbix 的 web 界面。我们想知道它是否可用、是否提供正确的内容以及它的运行速度。为此，我们必须使用我们的用户名和密码登录。

en-us	#### Overview  This section provides details of supported JSONPath functionality in item value preprocessing steps.  JSONPath consists of segments separated with dots. A segment can be either a simple word like a JSON value name, `*` or a more complex construct enclosed within square brackets `[` `]`. The separating dot before bracket segment is optional and can be omitted. For example:  |Path|Description| |----|-----------| |`$.object.name`|Return the object.name contents.| |`$.object['name']`|Return the object.name contents.| |`$.object.['name']`|Return the object.name contents.| |`$["object"]['name']`|Return the object.name contents.| |`$.['object'].["name"]`|Return the object.name contents.| |`$.object.history.length()`|Return the number of object.history array elements.| |`$[?(@.name == 'Object')].price.first()`|Return the price field of the first object with name 'Object'.| |`$[?(@.name == 'Object')].history.first().length()`|Return the number of history array elements of the first object with name 'Object'.| |`$[?(@.price > 10)].length()`|Return the number of objects with price being greater than 10.|  See also: [Escaping special characters from LLD macro values in JSONPath](/manual/config/items/preprocessing/jsonpath_functionality/escaping_lld_macros).
zh-cn	#### 概述  本部分提供监控项值预处理步骤中支持的JSONPath功能的详细信息。  JSONPath由用点分隔的段组成。 段可以是一个简单的词，如 JSON 值名称、`*`，也可以是括在方括号 `[` `]` 中的更复杂的构造。 括号段前的分隔点是可选的，可以省略。 例如：  |路径|描述| |----|-----------| |`$.object.name`|返回object.name的内容。| |`$.object['name']`|返回object.name的内容。| |`$.object.['name']`|返回object.name的内容。| |`$["object"]['name']`|返回object.name的内容。| |`$.['object'].["name"]`|返回object.name的内容。| |`$.object.history.length()`|返回object.history数组元素的个数。| |`$[?(@.name == 'Object')].price.first()`|返回第一个名为'Object'的对象的价格字段。| |`$[?(@.name == 'Object')].history.first().length()`|返回第一个名为'Object'的对象的历史数组元素个数。| |`$[?(@.price > 10)].length()`|返回price大于10的对象个数。|  参考: [从 JSONPath 中的 LLD 宏值中转义特殊字符](/manual/config/items/preprocessing/jsonpath_functionality/escaping_lld_macros).

en-us	#### Overview  This section provides details on passive and active checks performed by [Zabbix agent](/manual/config/items/itemtypes/zabbix_agent).  Zabbix uses a JSON based communication protocol for communicating with Zabbix agent.  See also: [Zabbix agent 2](/manual/appendix/protocols/zabbix_agent2)  protocol details.
zh-cn	#### 概述  本节提供有关 [Zabbix agent](/manual/config/items/itemtypes/zabbix_agent) 执行的被动和主动检查的详细信息。  Zabbix 使用基于 JSON 的通信协议与 Zabbix agent进行通信。  另请参阅：[Zabbix agent 2] (/manual/appendix/protocols/zabbix_agent2) 协议详细信息。

en-us	### Overview  This section provides several encryption configuration examples for CentOS 8.2 and MySQL 8.0.21 and can be used as a quickstart guide for encrypting the connection to the database.    ::: noteimportant  If MySQL host is set to localhost, encryption options will not be available. In this case a connection between Zabbix frontend and the database uses a socket file (on Unix) or shared memory (on Windows) and cannot be encrypted. :::   ::: noteclassic  List of encryption combinations is not limited to the ones listed on this page. There are a lot more combinations available.  :::
zh-cn	### 概述  本文将以CentOS 8.2和MySQL 8.0.21为例，介绍如何配置数据库加密连接。  ::: noteimportant 如果MySQL主机设置为localhost，加密选项将是不可用，这种情况下，Zabbix前端和数据库之间使用socket文件连接(在Unix上)或共享内存(在Windows上)，所以不能加密。 :::   ::: noteclassic 加密组合列表不限于本页列出的。还有更多组合可供选择。 :::

en-us	### Overview  This section provides several encryption configuration examples for CentOS 8.2 and PostgreSQL 13.  ::: noteclassic  Connection between Zabbix frontend and PostgreSQL cannot be encrypted (parameters in GUI are disabled), if the value of *Database host* field begins with a slash or the field is empty.  :::
zh-cn	### 概述  本节提供了几个对 CentOS 8.2 和 PostgreSQL 13 的加密配置示例。  ::: noteclassic 如果数据库主机字段的值以斜杠开头或该字段为空，则Zabbix前端和PostgreSQL之间的连接无法加密（GUI中的参数被禁用）。 :::

en-us	#### Overview  This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using SQL queries, whose results get automatically transformed into a JSON object suitable for low-level discovery.
zh-cn	#### 概述  此类低级别[自动发现](/manual/discovery/low_level_discovery) 通过使用SQL查询实现，其结果自动转换成一个匹配低级别自动发现的JSON格式的JSON对象。

en-us	#### Overview  Trapper items accept incoming data instead of querying for it.  It is useful for any data you might want to "push" into Zabbix.  To use a trapper item you must:  -   have a trapper item set up in Zabbix -   send in the data into Zabbix
zh-cn	#### 概述  采集器监控项接收传入的数据，它不会去主动采集数据。  它接受任何形式的推送到zabbix server的数据。  要使用采集器监控项，你需要：  -   在Zabbix中建立一个采集器监控项 -   将数据发送到Zabbix server

en-us	#### Overview  User macros are supported in Zabbix for greater flexibility, in addition to the macros [supported](/manual/appendix/macros/supported_by_location) out-of-the-box.  User macros can be defined on global, template and host level. These macros have a special syntax:      {$MACRO}  Zabbix resolves macros according to the following precedence:  1.  host level macros (checked first) 2.  macros defined for first level templates of the host (i.e.,     templates linked directly to the host), sorted by template ID 3.  macros defined for second level templates of the host, sorted by     template ID 4.  macros defined for third level templates of the host, sorted by     template ID, etc. 5.  global macros (checked last)  In other words, if a macro does not exist for a host, Zabbix will try to find it in the host templates of increasing depth. If still not found, a global macro will be used, if exists.  ::: notewarning If a macro with the **same name** exists on multiple linked templates of the same level, the macro from the template with the lowest ID will be used. Thus having macros with the same name in multiple templates is a configuration risk. :::  If Zabbix is unable to find a macro, the macro will not be resolved.  ::: noteimportant Macros (including user macros) are left unresolved in the Configuration section (for example, in the trigger list) by design to make complex configuration more transparent. :::  User macros can be used in:  -   item key parameter -   item update intervals and flexible intervals -   trigger name and description -   trigger expression parameters and constants (see     [examples](#examples)) -   many other locations - see the [full     list](/manual/appendix/macros/supported_by_location_user)
zh-cn	#### 概述  除了开箱即用的宏[supported](/manual/appendix/macros/supported_by_location)之外，Zabbix还支持用户宏，以提高灵活性。  用户宏可以在全局、模板和主机级别定义。这些宏有一种特殊的语法：      {$MACRO}  Zabbix根据以下优先级解析宏： 1.主机级宏（先选中） 2.为主机的一级模板（即直接链接到主机的模板）定义的宏，按模板ID排序 3.为主机二级模板定义的宏，按模板ID排序 4.为主机的三级模板定义的宏，按模板ID等排序。 5.全局宏（最后选中）  换句话说，如果主机不存在宏，Zabbix将尝试在深度不断增加的主机模板中找到它。如果仍然找不到，将使用全局宏（如果存在）。  ::: notewarning 如果同一级别的多个链接模板上存在具有**相同名称**的宏，则将使用ID最低的模板中的宏。因此，在多个模板中使用相同名称的宏是一种配置风险。 :::  如果Zabbix找不到宏，宏将无法解析。  ::: noteimportant 宏（包括用户宏）在配置部分（例如，在触发器列表中）被设计为不可解析，以使复杂的配置更加透明。 :::  用户宏可用于： - 项目关键参数 - 项目更新间隔和灵活间隔 - 触发器名称和描述 - 触发器表达式参数和常量(参见[示例](#示例)) - 许多其他位置-请参阅[完整列表](/manual/appendix/macros/supported_by_location_user)

en-us	#### Overview  When monitoring systems using an agent, a good practice is to obtain metrics from the host on which the agent is installed. To use the principle of least privilege, it is necessary to determine what metrics are obtained from the agent.  The table in this document allows you to select the minimum rights for guaranteed correct operation of Zabbix agent.  If a different user is selected for the agent to work, rather than 'LocalSystem', then for the operation of agent as a Windows service, the new user must have the rights "Log on as a service" from "Local Policy→User Rights Assignment" and the right to create, write and delete the Zabbix agent log file. An Active Directory user must be added to the *Performance Monitor Users* group.  ::: noteclassic When working with the rights of an agent based on the "minimum technically acceptable" group, prior provision of rights to objects for monitoring is required. :::
zh-cn	#### 概述  使用 agent 监控系统时，一种最佳实践是从安装代理的主机上获取指标。要使用最小权限原则，有必要确定哪些指标是从agent 那里获得的。  本文档中的表格允许您选择最低权限，保证 Zabbix agent 的正确运行。  如果选择了其他用户才能使 agent 工作，而不是"LocalSystem"，则要使 agent 作为Windows服务运行，新用户必须具有“本地策略→用户权限分配"中的"作为服务登录”权限分配”以及创建、写入和删除 Zabbix 代理日志文件的权利。必须将 Active Directory 用户添加到性能监视器用户组。  ::: noteclassic 基于 agent 的权限处理问题上，需要给出 "技术上可接受的最低要求 "的权限组，并且事先为监控对象提供权限。 :::

en-us	#### Overview  While a [simple graph](simple) is great for accessing data of one item and [custom graphs](custom) offer customization options, none of the two allow to quickly create a comparison graph for multiple items with little effort and no maintenance.  To address this issue, since Zabbix 2.4 it is possible to create ad-hoc graphs for several items in a very quick way.
zh-cn	#### 概览  虽然 [简单图表](../../../../../assets/en/manual/config/visualization/graphs/simple)非常适合访问单个监控项的数据，而 [自定义图表](../../../../../assets/en/manual/config/visualization/graphs/custom) 提供定制化选择，但是这两种图表都没法很轻松的快速创建多个监控项的比较图表。  为了解决这个问题，从 Zabbix 2.4 开始可以创建 ad-hoc以非常快速的方式绘制多个监控项的图表。

en-us	#### Overview  With escalations you can create custom scenarios for sending notifications or executing remote commands.  In practical terms it means that:  -   Users can be informed about new problems immediately. -   Notifications can be repeated until the problem is resolved. -   Sending a notification can be delayed. -   Notifications can be escalated to another "higher" user group. -   Remote commands can be executed immediately or when a problem is not     resolved for a lengthy period.  Actions are escalated based on the **escalation step**. Each step has a duration in time.  You can define both the default duration and a custom duration of an individual step. The minimum duration of one escalation step is 60 seconds.  You can start actions, such as sending notifications or executing commands, from any step. Step one is for immediate actions. If you want to delay an action, you can assign it to a later step. For each step, several actions can be defined.  The number of escalation steps is not limited.  Escalations are defined when [configuring an operation](operation#configuring_an_operation). Escalations are supported for problem operations only, not recovery.
zh-cn	#### 概述  通过Escalations，您可以创建发送通知或执行远程命令的自定义场景。  实际应用中，这意味着：  -   用户可以立即收到新问题通知 -   通知可以重复，直到问题解决 -   发送通知可以延时 -   通知可以升级到另一个“较高”的用户组 -   可以立即执行远程命令，或者长时间不解决问题  操作会根据升级步骤进行通知升级。 每一步都有一段时间。  您可以定义默认持续时间和单个步骤的自定义持续时间。一个升级步骤的最短持续时间为60秒。  您可以从任何步骤开始执行操作，例如发送通知或执行命令。 第一步是立即采取行动。 如果要延迟操作，可以将其分配给稍后的步骤。 对于每个步骤，可以定义几个操作。  通知升级步骤的数量不受限制。  [配置操作](operation#configuring_an_operation)是即可定义Escalations. Escalations仅对问题操作支持，而不是恢复。

en-us	#### Overview  With remote commands you can define that a certain pre-defined command is automatically executed on the monitored host upon some condition.  Thus remote commands are a powerful mechanism for smart pro-active monitoring.  In the most obvious uses of the feature you can try to:  -   Automatically restart some application (web server, middleware, CRM)     if it does not respond -   Use IPMI 'reboot' command to reboot some remote server if it does     not answer requests -   Automatically free disk space (removing older files, cleaning /tmp)     if running out of disk space -   Migrate a VM from one physical box to another depending on the CPU     load -   Add new nodes to a cloud environment upon insufficient CPU (disk,     memory, whatever) resources  Configuring an action for remote commands is similar to that for sending a message, the only difference being that Zabbix will execute a command instead of sending a message.  Remote commands can be executed by Zabbix server, proxy or agent. Remote commands on Zabbix agent can be executed directly by Zabbix server or through Zabbix proxy. Both on Zabbix agent and Zabbix proxy remote commands are disabled by default. They can be enabled by:  -   adding an `AllowKey=system.run[*]` parameter in agent configuration; -   setting the EnableRemoteCommands parameter to '1' in proxy     configuration.  Remote commands executed by Zabbix server are run as described in [Command execution](/manual/appendix/command_execution) including exit code checking.  Remote commands are executed even if the target host is in maintenance.
zh-cn	#### 概述  使用远程命令，您可以预定义在某些情况下会在受监控主机上自动执行的命令。  因此远程命令是智能主动监控的强大机制。  在该功能最显而易见的用途中，你可以尝试：  -   自动重启某些没有响应的应用（web服务器、中间件、CRM）  -   使用IPMI 'reboot'命令重启某些确实无法响应的服务器。  -   磁盘空间不足时自动释放（删除旧文件、清理）      -   根据CPU负载将VM从一台物理机迁移到另一台      -   CPU（磁盘、内存或其他）资源不足时向云环境添加新节点  为远程命令配置操作与发送消息类似，唯一的区别是 Zabbix 将执行一个命令而不是发送消息。  远程命令可以由Zabbix Server、Proxy 或agent执行。Zabbix agent上的远程命令可以由Zabbix Server或通过 Proxy 执行。Zabbix agent和Zabbix Proxy上的远程命令默认都是禁用的。 它们可以通过以下方式启用：  -   在agent的配置中添加一个`AllowKey=system.run[*]` 参数；  -   在代理的配置中将`EnableRemoteCommands`参数设为‘1’。   由 Zabbix服务器执行的远程命令按照[命令执行](/manual/appendix/command_execution)所述运行，包括退出代码检查。  即使目标主机在维护状态，远程命令也会执行。

en-us	#### Overview  [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) is a powerful interface in Windows that can be used for retrieving various information about Windows components, services, state and software installed.  It can be used for physical disk discovery and their performance data collection, network interface discovery, Hyper-V guest discovery, monitoring Windows services and many other things in Windows OS.  This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using WQL queries whose results get automatically transformed into a JSON object suitable for low-level discovery.
zh-cn	#### 概述  [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) 是一种Windows中的接口，功能强大，可用于获取各种信息，比如Windows组件、服务、状态和安装的软件。  WMI可用于物理硬盘的自动发现和相关性能数据的采集、网络接口的自动发现、Hyper-V guest的自动发现、监控Windows操作系统中的服务和其它实体。  此类低级别 [自动发现](/manual/discovery/low_level_discovery) 通过使用WQL查询实现，其结果会自动转换成一个匹配低级别自动发现的JSON格式的JSON对象。

en-us	#### Overview  You can assign some triggers to a [link](/manual/config/visualization/maps/map#linking_elements) between elements in a network map. When these triggers go into a problem state, the link can reflect that.  When you configure a link, you set the default link type and color. When you assign triggers to a link, you can assign different link types and colors with these triggers.  Should any of these triggers go into a problem state, their link style and color will be displayed on the link. So maybe your default link was a green line. Now, with the trigger in the problem state, your link may become bold red (if you have defined it so).
zh-cn	#### 概述  你可以将一些触发器[链接](/manual/config/visualization/maps/map#linking_elements)网络地图中的元素。当这些触发器进入问题状态时，该链接可以查看相关内容。  在配置链接时，可以设置默认链接类型和颜色。当你将触发器关联到链接时，你可以根据这些触发器来分配不同的链接类型和颜色。  如果这些触发器中的任何一个进入问题状态，它们的连接样式和颜色将显示在链接上。所以你的默认链接可能是一条绿线。现在，由于触发器处于问题状态，你的链接可能变为粗体红色（如果你这样定义的话）。

en-us	#### Overview  You can effectively monitor Windows performance counters using the *perf\_counter\[\]* key.  For example:      perf_counter["\Processor(0)\Interrupts/sec"]  or      perf_counter["\Processor(0)\Interrupts/sec", 10]  For more information on using this key or its English-only equivalent `perf_counter_en`, see [Windows-specific item keys](/manual/config/items/itemtypes/zabbix_agent/win_keys).  In order to get a full list of performance counters available for monitoring, you may run:      typeperf -qx  You may also use low-level discovery to discover multiple [object instances](/manual/discovery/low_level_discovery/examples/windows_perf_instances) of Windows performance counters and automate the creation of perf\_counter items for multiple instance objects.
zh-cn	#### 概览  你可以使用 *perf\_counter\[\]* 这个key有效的监控Windows性能计数器。\  例如：      perf_counter["\Processor(0)\Interrupts/sec"]  或      perf_counter["\Processor(0)\Interrupts/sec", 10]  有关使用此key的更多信息请参阅[Windows专用监控项](/zh/manual/config/items/itemtypes/zabbix_agent/win_keys)。  为了获取可用于监控的新能计数器完整列表，你可以运行：      typeperf -qx  可以通过低级别发现来发现windows性能计数器的多[对象实例](/manual/discovery/low_level_discovery/examples/windows_perf_instances),并自动创建多实例对象的性能计数器监控项。

en-us	#### Overview  You can monitor the health and availability of Intelligent Platform Management Interface (IPMI) devices in Zabbix. To perform IPMI checks Zabbix server must be initially [configured](/manual/installation/install#configure_the_sources) with IPMI support.  IPMI is a standardized interface for remote "lights-out" or "out-of-band" management of computer systems. It allows to monitor hardware status directly from the so-called "out-of-band" management cards, independently from the operating system or whether the machine is powered on at all.  Zabbix IPMI monitoring works only for devices having IPMI support (HP iLO, DELL DRAC, IBM RSA, Sun SSP, etc).  Since Zabbix 3.4, a new IPMI manager process has been added to schedule IPMI checks by IPMI pollers. Now a host is always polled by only one IPMI poller at a time, reducing the number of open connections to BMC controllers. With those changes it's safe to increase the number of IPMI pollers without worrying about BMC controller overloading. The IPMI manager process is automatically started when at least one IPMI poller is started.  See also [known issues](/manual/installation/known_issues#ipmi_checks) for IPMI checks.
zh-cn	#### 概述  你可以在Zabbix中监控智能平台管理接口（IPMI）设备的运行状况和可用性。要执行IPMI检查，Zabbix服务器必须首先[配置](/zh/manual/installation/install#from_the_sources)IPMI支持。  IPMI是计算机系统的远程"关闭"或“带外”管理的标准接口。它可以独立于操作系统直接从所谓的“带外”管理卡监视硬件状态。  Zabbix IPMI监控仅适用于支持IPMI的设备(HP iLO, DELL DRAC, IBM RSA, Sun SSP, 等等).  从Zabbix 3.4开始，添加了一个新的IPMI管理器进程来安排IPMI轮询器进行IPMI检查。现在，主机始终只由一个IPMI轮询器轮询，从而减少了与BMC控制器的打开连接数。通过这些更改，可以安全地增加IPMI轮询器的数量，而无需担心BMC控制器过载。 启动至少一个IPMI轮询器时，将自动启动IPMI管理器进程。  也可以参考IPMI检查的[已知问题](/zh/manual/installation/known_issues#ipmi_checks)。

en-us	#### Overview  Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics, etc.).  The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server can actively alert the administrators of the particular machine that reported the failure.  Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information.
zh-cn	#### 概述 Zabbix agent 部署在被监控目标上，以主动监控本地资源和应用程序（硬盘、内存、处理器统计信息等）。  Zabbix agent 收集本地的操作信息并将数据报告给 Zabbix server 用于进一步处理。一旦出现异常 (例如硬盘空间已满或者有崩溃的服务进程)，Zabbix server 会主动警告管理员指定机器上的异常。  Zabbix agents 的极高效率缘于它可以利用本地系统调用来完成统计数据的采集。

en-us	#### Overview  Zabbix can be used for centralized monitoring and analysis of log files with/without log rotation support.  Notifications can be used to warn users when a log file contains certain strings or string patterns.  To monitor a log file you must have:  -   Zabbix agent running on the host -   log monitoring item set up  ::: noteimportant The size limit of a monitored log file depends on [large file support](/manual/appendix/items/large_file_support). :::
zh-cn	#### 概述  Zabbix 可用于有/无日志轮询支持的日志文件的集中监控和分析。  当日志文件包含某些字符串或字符串模式时，可以使用通知来警告用户。  要监控日志文件，必须具有如下：  -   主机上已运行Zabbix agent -   设置日志监控项  ::: noteimportant 被监控日志文件的大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。 :::

en-us	#### Overview  Zabbix can query metrics exposed in the Prometheus line format.  Two steps are required to start gathering Prometheus data:  -   an [HTTP master item](/manual/config/items/itemtypes/http) pointing     to the appropriate data endpoint, e.g.     `https://<prometheus host>/metrics` -   dependent items using a Prometheus preprocessing option to query     required data from the metrics gathered by the master item  There are two Prometheus data preprocessing options:  -   *Prometheus pattern* - used in normal items to query Prometheus data -   *Prometheus to JSON* - used in normal items and for low-level     discovery. In this case queried Prometheus data are returned in a     JSON format.
zh-cn	#### 概述  Zabbix 可以采集符合 Prometheus行协议格式的监控数据。  采集数据需要配置以下两步：  - 创建一个作为主要监控项的[HTTP监控项](/manual/config/items/itemtypes/http) 指向合适的站点批量采集数据。例如：`https://<prometheus host>/metrics` - 配置使用Prometheus 预处理选项的从属监控项，来从主要监控项中获取需要的数据  Zabbix 有两个Prometheus 预处理选项：  - *Prometheus正则匹配* - 可以应用于一般监控项中，用来从查询Prometheus行协议中提取数据 - *Prometheus转JSON* - 可以应用于一般监控项或低级别自动发现监控项。使用这个预处理步骤，将会将采集到的Prometheus 数据转化为JSON格式返回给监控项

en-us	#### Overview  Zabbix offers automatic network discovery functionality that is effective and very flexible.  With network discovery properly set up you can:  -   speed up Zabbix deployment -   simplify administration -   use Zabbix in rapidly changing environments without excessive     administration  Zabbix network discovery is based on the following information:  -   IP ranges -   Availability of external services (FTP, SSH, WEB, POP3, IMAP, TCP,     etc) -   Information received from Zabbix agent (only unencrypted mode is     supported) -   Information received from SNMP agent  It does NOT provide:  -   Discovery of network topology  Network discovery basically consists of two phases: discovery and actions.
zh-cn	#### 概述  Zabbix提供高效灵活的网络自动发现功能。  网络发现的优势：  -   加快部署速度 -   简化管理 -   在快速变化的环境中避免过度管理  Zabbix网络发现依赖于以下信息：  -   IP地址范围 -   可用的外部服务 (FTP, SSH, WEB, POP3, IMAP, TCP等) -   来自Zabbix agent的信息(仅支持未加密模式) -   来自SNMP agent的信息  不支持：  -   网络拓扑发现  网络发现主要包含两个步骤：发现和动作。

en-us	#### Overview  Zabbix provides an effective and reliable way of monitoring a distributed IT infrastructure using Zabbix [proxies](/manual/distributed_monitoring/proxies).  Proxies can be used to collect data locally on behalf of a centralized Zabbix server and then report the data to the server.
zh-cn	#### 概览  Zabbix提供了一种使用Zabbix [proxies](/manual/distributed_monitoring/proxies). 监视分布式IT基础设施的有效和可靠的方法   Proxy代理可以用来代表中央Zabbix server在本地收集数据，然后将数据报告给Zabbix server。

en-us	#### Overview  Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.  Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry.  A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators.  Zabbix proxy requires a separate database.  ::: noteimportant Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle is at your own risk and may contain some limitations as, for example, in [return values](/manual/discovery/low_level_discovery#overview) of low-level discovery rules. :::  See also: [Using proxies in a distributed environment](/manual/distributed_monitoring/proxies)
zh-cn	#### 概述  Zabbix proxy 是一个可以从一个或多个受监控设备采集监控数据并将信息发送到 Zabbix server 的进程，主要是代表 Zabbix server 工作。 所有收集的数据都在本地缓存，然后传输到 proxy 所属的 Zabbix server。  部署Zabbix proxy 是可选的，但可能非常有利于分担单个 Zabbix server 的负载。 如果只有代理采集数据，则 Zabbix server 上会减少 CPU 和磁盘 I/O 的开销。  Zabbix proxy 是无需本地管理员即可集中监控远程位置、分支机构和网络的理想解决方案。  Zabbix proxy 需要使用独立的数据库。  ::: noteimportant 值得注意的是，Zabbix proxy 支持 SQLite、MySQL和PostgreSQL 作为数据库。使用 Oracle 或 DB2 需要您承担一定的风险，例如，在自动发现规则中的遇到问题 [返回值](/manual/discovery/low_level_discovery#overview) 。 :::  详见：[在分布式环境中使用 Zabbix proxy](/manual/distributed_monitoring/proxies)。

en-us	#### Overview  Zabbix server is the central process of Zabbix software.  The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.  The server is the central repository in which all configuration, statistical and operational data is stored, and it is the entity in Zabbix that will actively alert administrators when problems arise in any of the monitored systems.  The functioning of a basic Zabbix server is broken into three distinct components; they are: Zabbix server, web frontend and database storage.  All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section.
zh-cn	#### 概述  Zabbix server 是整个 Zabbix 软件的核心程序。  Zabbix Server负责执行数据的主动轮询和被动获取，计算触发器条件，向用户发送通知。它是Zabbix Agent 和 Proxy 报告系统可用性和完整性数据的核心组件。Server自身可以通过简单服务远程检查网络服务（如Web服务器和邮件服务器）。  Zabbix Server是所有配置、统计和操作数据的中央存储中心，也是Zabbix监控系统的告警中心。在监控的系统中出现任何异常，将发出通知给管理员。  基本的 Zabbix Server 的功能分解成为三个不同的组件。他们是：Zabbix server、Web前端和数据库。  Zabbix 的所有配置信息都存储在 Server和Web前端进行交互的数据库中。例如，当你通过Web前端（或者API）新增一个监控项时，它会被添加到数据库的监控项表里。然后，Zabbix server 以每分钟一次的频率查询监控项表中的有效项，接着将它存储在 Zabbix server 中的缓存里。这就是为什么 Zabbix前端所做的任何更改需要花费两分钟左右才能显示在最新的数据段的原因。

en-us	#### Overview  Zabbix server uses a JSON- based communication protocol for receiving data from Zabbix sender with the help of [trapper item](/manual/config/items/itemtypes/trapper).  Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen).
zh-cn	#### 概述  Zabbix server使用基于JSON的通信协议，在[trapper item](/manual/config/items/itemtypes/trapper)的帮助下从Zabbix sender接收数据。  请求和响应消息必须以[header and data length](/manual/appendix/protocols/header_datalen)开头。

en-us	#### Overview  Zabbix supports a number of built-in macros which may be used in various situations. These macros are variables, identified by a specific syntax:      {MACRO}   Macros resolve to a specific value depending on the context.  Effective use of macros allows to save time and make Zabbix configuration more transparent.  In one of typical uses, a macro may be used in a template. Thus a trigger on a template may be named "Processor load is too high on {HOST.NAME}". When the template is applied to the host, such as Zabbix server, the name will resolve to "Processor load is too high on Zabbix server" when the trigger is displayed in the Monitoring section.  Macros may be used in item key parameters. A macro may be used for only a part of the parameter, for example `item.key[server_{HOST.HOST}_local]`. Double-quoting the parameter is not necessary as Zabbix will take care of any ambiguous special symbols, if present in the resolved macro.  There are other types of macros in Zabbix.  Zabbix supports the following macros:  -   `{MACRO}` - built-in macro (see [full list](/manual/appendix/macros/supported_by_location)) -   `{<macro>.<func>(<params>)}` - macro [functions](/manual/config/macros/macro_functions) -   `{$MACRO}` - [user-defined macro](/manual/config/macros/user_macros), optionally [with context](/manual/config/macros/user_macros_context) -   `{#MACRO}` - macro for [low-level discovery](/manual/config/macros/lld_macros) -   `{?EXPRESSION}` - [expression macro](/manual/config/macros/expression_macros)
zh-cn	#### 概述  Zabbix支持许多内置宏，可用于各种情况。这些宏是由特定语法标识的变量：      {MACRO}   宏根据上下文解析为特定值。  有效使用宏可以节省时间，并使Zabbix配置更加透明。  在一种典型用途中，宏可以用于模板中。因此，模板上的触发器可能被命名为“{HOST.NAME}上的处理器负载过高”。当模板应用于主机(如Zabbix服务器)时，当触发器显示在监控部分时，名称将解析为“Zabbix服务器上的处理器负载过高”。  宏可用于监控项键参数。宏只能用于参数的一部分，例如`item.key[server_{HOST.HOST}_local]`。不需要双引号引用参数，因为如果解析宏中存在任何不明确的特殊符号，Zabbix将处理这些符号。  除了内置宏之外，Zabbix还支持用户定义宏、带有上下文的用户定义宏和用于低级发现的宏。  另见： - · `{MACRO}` - 内置宏（参见 [完整列表](/manual/appendix/macros/supported_by_location)） - · `{<macro>.<func>(<params>)}` - 宏[函数](/manual/config/macros/macro_functions) - · `{$MACRO}` - [用户定义的宏](/manual/config/macros/user_macros)，可选的[上下文](/manual/config/macros/user_macros_context) - · `{#MACRO}` - 用于[底层自动发现]的宏（/manual/config/macros/lld_macros） - · `{?EXPRESSION}` - [表达式宏](/manual/config/macros/expression_macros)

en-us	#### Overview  Zabbix supports encrypted communications between Zabbix components using Transport Layer Security (TLS) protocol v.1.2 and 1.3 (depending on the crypto library). Certificate-based and pre-shared key-based encryption is supported.  Encryption can be configured for connections:  -   Between Zabbix server, Zabbix proxy, Zabbix agent, zabbix\_sender     and zabbix\_get utilities -   To Zabbix database [from Zabbix frontend and     server/proxy](/manual/appendix/install/db_encrypt)  Encryption is optional and configurable for individual components:  -   Some proxies and agents can be configured to use certificate-based     encryption with the server, while others can use pre-shared     key-based encryption, and yet others continue with unencrypted     communications (as before) -   Server (proxy) can use different encryption configurations for     different hosts  Zabbix daemon programs use one listening port for encrypted and unencrypted incoming connections. Adding an encryption does not require opening new ports on firewalls.
zh-cn	 #### 概述  Zabbix支持使用TLS协议v.1.2和1.3(取决于加密库)在Zabbix组件之间进行加密通信。支持证书加密和预共享密钥加密。  可以为连接配置加密:  -   Zabbix server，Zabbix proxy，Zabbix agent，Zabbix \_sender和Zabbix \_get工具 -   到Zabbix数据库[从zabbix前端和server/proxy](/manual/appendix/install/db_encrypt)  加密是可选和可配置的单个组件:  -   一些proxy代理和agent代理可以配置为使用服务器的基于证书的加密，而其他的可以使用基于预共享密钥的加密，而其他的则继续使用未加密的通信(与前面一样) -   Server (proxy) 可以为不同的主机使用不同的加密配置。  Zabbix守护程序为传入的加密和非加密连接使用一个侦听端口。 添加加密并不需要在防火墙上打开新的端口。

en-us	#### Overview  Zabbix supports TimescaleDB, a PostgreSQL-based database solution of automatically partitioning data into time-based chunks to support faster performance at scale.  ::: notewarning Currently TimescaleDB is not supported by Zabbix proxy. :::  Instructions on this page can be used for creating TimescaleDB database or migrating from existing PostgreSQL tables to TimescaleDB.
zh-cn	#### 概述  Zabbix支持TimescaleDB，这是一种基于PostgreSQL的数据库解决方案，可自动将数据分为基于时间的块，以支持更快的大规模性能。  ::: notewarning 目前，Zabbix代理不支持 TimescaleDB 。 ::: 此章节会介绍创建 TimescaleDB 数据库或从现有的 PostgreSQL 表迁移到 TimescaleDB

en-us	#### Overview  Zabbix web frontend can be temporarily disabled in order to prohibit access to it. This can be useful for protecting the Zabbix database from any changes initiated by users, thus protecting the integrity of database.  Zabbix database can be stopped and maintenance tasks can be performed while Zabbix frontend is in maintenance mode.  Users from defined IP addresses will be able to work with the frontend normally during maintenance mode.
zh-cn	#### 概述  可以暂时禁用 Zabbix Web 前端以禁止对其进行访问。这对于保护 Zabbix 数据库免受用户发起的任何更改非常有用，从而保护数据库的完整性。  当 Zabbix 前端处于维护模式时，可以停止 Zabbix 数据库并执行维护任务。  用户使用已定义IP 地址将能够在维护模式下正常访问前端。

en-us	#### Parameter - array  If the key parameter is an array, it is again enclosed in square brackets, where individual parameters come in line with the rules and syntax of specifying multiple parameters.  ![](../../../../../assets/en/manual/config/key_param_array.png)  ::: noteimportant Multi-level parameter arrays, e.g. `[a,[b,[c,d]],e]`, are not allowed. :::
zh-cn	#### 参数 - 数组  如果key参数是一个数组，它需要包含在方括号中，其中各个参数需要列为一行且符合多个参数的规则和语法。  ![](../../../../../assets/en/manual/config/key_param_array.png)  ::: noteimportant 多级参数数组, 例如 `[a,[b,[c,d]],e]`，是不受支持的。 :::

en-us	### Parameters  `(array)` IDs of hosts to delete.
zh-cn	 ### 参数  `(array)` 要删除主机的ID。

en-us	### Parameters  `(array)` IDs of items to clear.
zh-cn	 ### 参数  `(array)`需要删除历史数据的监控项ID。

en-us	### Parameters  `(array)` IDs of proxies to delete.
zh-cn	### 参数  `(array)` 要删除的proxy IDs。

en-us	### Parameters  `(array)` IDs of the actions to delete.
zh-cn	### 参数  `(array)` 要删除动作的 ID。

en-us	### Parameters  `(array)` IDs of the correlations to delete.
zh-cn	### 参数  `(array)` 要删除的关联 ID。

en-us	### Parameters  `(array)` IDs of the dashboards to delete.
zh-cn	### 参数  `(array)`要删除的仪表盘ID。

en-us	### Parameters  `(array)` IDs of the discovery rules to delete.
zh-cn	 ### 参数  `(array)` 要删除的发现规则的ID。

en-us	### Parameters  `(array)` IDs of the global macros to delete.
zh-cn	### 参数  `(array)` 需要删除的全局宏ID.

en-us	### Parameters  `(array)` IDs of the graph prototypes to delete.
zh-cn	 ### 参数  `(array)` 要删除的图表原型的ID。

en-us	### Parameters  `(array)` IDs of the graphs to delete.
zh-cn	### 参数  `(array)` 要删除的图表的ID。

en-us	### Parameters  `(array)` IDs of the host groups to delete.
zh-cn	 ### 参数  要删除主机组的`(数组)`ID。

en-us	### Parameters  `(array)` IDs of the host interfaces to delete.
zh-cn	### 参数  要删除主机接口的`(数组)`ID。

en-us	### Parameters  `(array)` IDs of the host macros to delete.
zh-cn	### 参数  `(array)` 需要删除主机宏的ID.

en-us	### Parameters  `(array)` IDs of the host prototypes to delete.
zh-cn	### 参数  `(array)` 要删除主机原型的ID。

en-us	### Parameters  `(array)` IDs of the icon maps to delete.
zh-cn	### 参数  `(array)` 要删除的多个图标映射的 ID。

en-us	### Parameters  `(array)` IDs of the images to delete.
zh-cn	### 参数  `(array)` 指定删除图像的 ID。

en-us	### Parameters  `(array)` IDs of the item prototypes to delete.
zh-cn	### 参数  删除可通过监控项原型的ID（数组）。

en-us	### Parameters  `(array)` IDs of the items to delete.
zh-cn	### 参数  `(array)` 删除目标监控项 ID。

en-us	### Parameters  `(array)` IDs of the LLD rules to delete.
zh-cn	### 参数  `(array)` 要删除的 LLD 规则的 ID。

en-us	### Parameters  `(array)` IDs of the maintenance periods to delete.
zh-cn	### 参数  `(array)`要删除的维护周期的IDs。

en-us	### Parameters  `(array)` IDs of the maps to delete.
zh-cn	### 参数  `(array)` 要删除的拓扑图的id列表.

en-us	### Parameters  `(array)` IDs of the media types to delete.
zh-cn	### 参数  `(array)` 要删除的媒介类型的ID。

en-us	### Parameters  `(array)` IDs of the regular expressions to delete.
zh-cn	### 参数  `(array)` 代表计划删除的正则表达式的ID号。

en-us	### Parameters  `(array)` IDs of the roles to delete.
zh-cn	### 参数  `(array)` 要删除的角色用户ID号。

en-us	### Parameters  `(array)` IDs of the scheduled reports to delete.
zh-cn	### 参数  `(array)` 将要删除的规划报告ID。

en-us	### Parameters  `(array)` IDs of the scripts to delete.
zh-cn	###  参数  `(数组)` 要删除的脚本ID。

en-us	### Parameters  `(array)` IDs of the services to delete.
zh-cn	 ### 参数  `(数组)` 要删除的服务ID。

en-us	### Parameters  `(array)` IDs of the template dashboards to delete.
zh-cn	### 参数 `(array)` 需要删除的模板仪表盘ID。

en-us	### Parameters  `(array)` IDs of the templates to delete.
zh-cn	### 参数  `(array)` 要删除的模板的ID。

en-us	### Parameters  `(array)` IDs of the tokens to delete.
zh-cn	### 参数  `(array)` 要删除的令牌的 ID。

en-us	### Parameters  `(array)` IDs of the tokens to generate.
zh-cn	### 参数  `(array)` 要生成的令牌的ID。

en-us	### Parameters  `(array)` IDs of the trigger prototypes to delete.
zh-cn	### 参数  `(array)`要删除的触发器原型的 ID.

en-us	### Parameters  `(array)` IDs of the triggers to delete.
zh-cn	### 参数  `(array)` 要删除的触发器ID列表.

en-us	### Parameters  `(array)` IDs of the user groups to delete.
zh-cn	### 参数  `(array)` 需要删除的用户组ID.

en-us	### Parameters  `(array)` IDs of the value maps to delete.
zh-cn	### 参数  `(array)` 需要删除的值映射的ID。

en-us	### Parameters  `(array)` IDs of the web scenarios to delete.
zh-cn	 ### 参数  `(array)` 需要被删除的Web场景的ID。

en-us	### Parameters  `(array)` IDs of users to delete.
zh-cn	### 参数  `(array)` 要删除用户的ID.

en-us	### Parameters  `(array)` IDs of users to unblock.
zh-cn	### 参数  `(array)` 需要解锁用户的ID.

en-us	### Parameters  `(array)` The method accepts an empty array.
zh-cn	### 参数  `(array)` 此方法接受一个空数组.

en-us	### Parameters  `(array)` The method accepts an empty array.
zh-cn	### 参数  `(array)` 该方法接受一个空的数组。

en-us	### Parameters  `(object/array)` Actions to create.  Additionally to the [standard action properties](object#action), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object for the action.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to create for the action.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to create for the action.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to create for the action.|
zh-cn	 ### 参数  `(object/array)` 要创建的动作 。  此外，还有 [标准动作参数](object#动作)，方法接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |--|--|------| |filter|object|动作的动作[过滤](/manual/api/reference/action/object#动作过滤) 对象。| |operations|array|为这个动作创建的动作[操作](/manual/api/reference/action/object#动作操作) 。| |recovery\_operations|array|为这个动作创建的动作[恢复操作](/manual/api/reference/action/object#动作恢复操作)。| |update\_operations|array|为这个动作创建的动作[更新操作](/manual/api/reference/action/object#动作更新操作)。|

en-us	### Parameters  `(object/array)` Correlation properties to be updated.  The `correlationid` property must be defined for each correlation, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object to replace the current filter.| |operations|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to replace existing operations.|
zh-cn	 ### 参数  `(object/array)` 需要更新的关联属性。  必须为每个关联定义 `correlationid` 属性，其它的属性都是可选的。只有传递的属性会被更新，其它属性都将保持不变。  除了[标准关联属性](object#关联)以外，此方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |filter|object|替换当前过滤器的关联[过滤](/manual/api/reference/correlation/object#关联过滤) 对象。| |operations|array|替换现有操作的关联[操作](/manual/api/reference/correlation/object#关联操作)。|

en-us	### Parameters  `(object/array)` Discovery rule properties to be updated.  The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.|
zh-cn	 ### 参数  `(object/array)` 要更新的发现规则属性。  必须为每个发现规则定义“druleid”属性，所有其他属性是可选的。 只有传递的属性将被更新，所有其他属性将保持不变。  除了[标准发现规则属性](object#发现规则)，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |dchecks|array|发现[checks](/manual/api/reference/dcheck/object) 以替换现有的检查。|

en-us	### Parameters  `(object/array)` [Global macro properties](object#global_macro) to be updated.  The `globalmacroid` property must be defined for each global macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 需要更新的 [Global macro properties](object#全局宏) .  每个全局宏必须定义 `globalmacroid` 参数, 其他参数均为可选的. 只有通过的属性才会被更新，其他属性保持不变.

en-us	### Parameters  `(object/array)` Global macros to create.  The method accepts global macros with the [standard global macro properties](object#global_macro).
zh-cn	### 参数  `(object/array)` 需要创建的全局宏.  此方法接受具有 [标准全局宏属性 ](object#global_macro)的全局宏.

en-us	### Parameters  `(object/array)` Graph properties to be updated.  The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph properties](object#graph) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	### 参数  `(object/array)` 要更新的图表属性。  必须为每个图表定义 "graphid "属性，所有其他的属性是可选的。只有传递的属性会被更新，所有其他的属性将保持不变。  除了[标准图形属性](object#图表)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|图表[监控项](/manual/api/reference/graphitem/object)来替换现有的图表监控项。如果一个图表监控项有定义`gitemid`属性，它将被更新，否则将创建一个新的图表监控项。|

en-us	### Parameters  `(object/array)` Graph prototype properties to be updated.  The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	 ### 参数  `(object/array)` 要更新的图新原型属性。  `graphid`属性必须为每个图表原型定义，所有其他属性是可选的。只有通过的属性将被更新，所有其他的将保持不变。  除了[标准图形原型属性](object#graph_prototype)，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|[图表项目](/manual/api/reference/graphitem/object)将替换现有的图表项目。如果一个图表项目定义了 `gitemid` 属性，它将会被更新，否则会创建一个新的图表项目。|

en-us	### Parameters  `(object/array)` [Host group properties](object#host_group) to be updated.  The `groupid` property must be defined for each host group, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
zh-cn	 ### 参数  `(对象/数组)` [主机组属性](object#host_group) 将被更新。  `groupid` 属性必须为每个主机组定义，所有其他属性都是可选的。只有给定的属性将被更新，其他所有属性将保持不变。

en-us	### Parameters  `(object/array)` [Host interface properties](object#host_interface) to be updated.  The `interfaceid` property must be defined for each host interface, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 要更新的[主机接口属性](object#host_interface)   必须为每个主机接口定义`interfaceid`属性，所有其他属性都是可选的。 只有给定的属性将被更新，所有其他属性将保持不变。

en-us	### Parameters  `(object/array)` [Host macro properties](object#host_macro) to be updated.  The `hostmacroid` property must be defined for each host macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 需要更新的[Host macro properties](object#主机宏) .  每个主机宏必须定义 `hostmacroid` 参数, 其他参数均为可选的. 只有通过的属性才会被更新，其他属性保持不变.

en-us	### Parameters  `(object/array)` Host macros to create.  The method accepts host macros with the [standard host macro properties](object#host_macro).
zh-cn	### 参数  `(object/array)` 要创建主机宏.  此方法接受具有 [标准主机宏属性](object#host_macro)的主机宏.

en-us	### Parameters  `(object/array)` Host properties to be updated.  The `hostid` property must be defined for each host, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.  Note, however, that updating the host technical name will also update the host's visible name (if not given or empty) by the host's technical name value.  Additionally to the [standard host properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object#host_group) to replace the current host groups the host belongs to.<br><br>The host groups must have the `groupid` property defined. All host groups that are not listed in the request will be unlinked.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces.<br><br>All interfaces that are not listed in the request will be removed.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag) to replace the current host tags.<br><br>All tags that are not listed in the request will be removed.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros.<br><br>All macros that are not listed in the request will be removed.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. All templates that are not listed in the request will be only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the host.<br><br>The templates must have the `templateid` property defined.|  ::: notetip As opposed to the Zabbix frontend, when `name` (visible host name) is the same as `host` (technical host name), updating `host` via API will not automatically update `name`. Both properties need to be updated explicitly. :::
zh-cn	 ### 参数  `(对象/数组)` 待更新的主机属性。  `hostid` 属性必须为每台主机定义，其他属性都是可选的。只有给定的属性将被更新，其他所有属性将保持不变。  但是，请注意，更新主机技术名称也将根据主机的技术名称值更新主机的可见名称(如果没有给出或为空)。  除了[标准主机属性](object#host)以外，此方法接受如下参数:  |参数|[类](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |groups|对象/数组|更换主机所属的主机[组](/manual/api/reference/hostgroup/object#host_group)。<br><br>主机组必须已定义 `groupid` 属性。所有未在请求中列出的主机组将被解除链接。| |interfaces|对象/数组|主机[接口](/manual/api/reference/hostinterface/object)用于替换当前主机接口。 <br><br>所有未在请求中列出的接口将被删除。| |tags|对象/数组|主机[标签](/manual/api/reference/host/object#host_tag)替换当前主机标签。<br><br>所有未在请求中列出的标签将被删除。| |inventory|object|主机[清单](/manual/api/reference/host/object#host_inventory)属性。| |macros|对象/数组|[用户宏](/manual/api/reference/usermacro/object)替换当前用户宏。<br><br>所有未在请求中列出的宏将被删除。| |templates|对象/数组|[模板](/manual/api/reference/template/object)替换当前链接的模板。所有未在请求中列出的模板只会被解除链接。<br><br>模板必须定义了 `templateid` 属性。| |templates\_clear|对象/数组|[模板](/manual/api/reference/template/object)取消与主机的链接并清除。<br><br>模板必须定义了 `templateid` 属性。|  ::: notetip 与Zabbix前端不同，当 `name` (可见主机名)与 `host` (技术主机名)相同时，通过API更新 `host` 不会自动更新 `name` 。这两个属性都需要显式更新。 :::

en-us	### Parameters  `(object/array)` Icon map properties to be updated.  The `iconmapid` property must be defined for each icon map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard icon map properties](object#icon_map), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |mappings|array|[Icon mappings](/manual/api/reference/iconmap/object#icon_mapping) to replace the existing icon mappings.|
zh-cn	 ### 参数  `(object/array)` 要更新的图标映射的属性。  每个图标映射的 `iconmapid` 属性都必需被定义，所有其它属性都是可选的。只有传递的属性会被更新，其余的都会保持不变。  除了[标准的图标映射属性](object#icon_map)之外，此方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |----|---------------------------------------------------|----| |**mappings**<br>（必需）|数组|用来替换现有图标映射关系的[图标映射](/manual/api/reference/iconmap/object#icon_mapping)。|

en-us	### Parameters  `(object/array)` Items to create.  Additionally to the [standard item properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Item [preprocessing](/manual/api/reference/item/object#item_preprocessing) options.| |tags|array|Item [tags](/manual/api/reference/item/object#item_tag).|
zh-cn	### 参数  `(object/array)` 创建目标监控项。  除了 [标准监控项属性](object#host) 之外，此方法同样适用以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|说明| |---------|---------------------------------------------------|-----------| |preprocessing|array|监控项 [预处理](/manual/api/reference/item/object#item_preprocessing) 选项。| |tags|array|监控项 [标签](/manual/api/reference/item/object#item_tag) 。|

en-us	### Parameters  `(object/array)` Map properties to be updated.  The `mapid` property must be defined for each map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard map properties](object#map), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|Map [links](/manual/api/reference/map/object#map_link) to replace the existing links.| |selements|array|Map [elements](/manual/api/reference/map/object#map_element) to replace the existing elements.| |urls|array|Map [URLs](/manual/api/reference/map/object#map_url) to replace the existing URLs.| |users|array|Map [user](/manual/api/reference/map/object#map_user) shares to replace the existing elements.| |userGroups|array|Map [user group](/manual/api/reference/map/object#map_user_group) shares to replace the existing elements.| |shapes|array|Map [shapes](/manual/api/reference/map/object#map_shapes) to replace the existing shapes.| |lines|array|Map [lines](/manual/api/reference/map/object#map_lines) to replace the existing lines.|  ::: notetip To create map links between new map elements you'll need to set an element's `selementid` to an arbitrary value and then use this value to reference this element in the links `selementid1` or `selementid2` properties. When the element is created, this value will be replaced with the correct ID generated by Zabbix. [See example for map.create.](create#create_a_host_map) :::
zh-cn	### 参数  `(object/array)` 要更新的拓扑图属性。  必须为每个地图定义“mapid”属性，所有其他属性是可选的。只有传递的属性会被更新，所有其他的将保持不变。  除了 [标准地图属性](object#map)，该方法 接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|说明| |---------|---------------------------------------------------|-----------| |links|array|Map [links](/manual/api/reference/map/object#map_link) 来替换现有的链接。| |selements|array|Map [elements](/manual/api/reference/map/object#map_element) 替换现有元素。| |urls|array|拓扑图 [URLs](/manual/api/reference/map/object#map_url) 以替换现有的 URL。| |users|array|Map [user](/manual/api/reference/map/object#map_user) 共享以替换现有元素。| |userGroups|array|拓扑图 [用户组](/manual/api/reference/map/object#map_user_group) 共享以替换现有元素。| |shapes|array|Map [shapes](/manual/api/reference/map/object#map_shapes) 来替换现有的形状。| |lines|array|Map [lines](/manual/api/reference/map/object#map_lines) 来替换现有的行。|  :::noteclassic 要创建地图链接，您需要将地图元素 selementid 设置为任意值，然后使用此值在链接 selementid1 或 selementid2 属性中引用此元素。 创建元素时，该值将替换为 Zabbix 生成的正确 ID, [参考](create#create_a_host_map) :::

en-us	### Parameters  `(object/array)` Maps to create.  Additionally to the [standard map properties](object#map), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |links|array|Map [links](/manual/api/reference/map/object#map_link) to be created on the map.| |selements|array|Map [elements](/manual/api/reference/map/object#map_element) to be created on the map.| |urls|array|Map [URLs](/manual/api/reference/map/object#map_url) to be created on the map.| |users|array|Map [user](/manual/api/reference/map/object#map_user) shares to be created on the map.| |userGroups|array|Map [user group](/manual/api/reference/map/object#map_user_group) shares to be created on the map.| |shapes|array|Map [shapes](/manual/api/reference/map/object#map_shapes) to be created on the map.| |lines|array|Map [lines](/manual/api/reference/map/object#map_lines) to be created on the map.|  ::: notetip To create map links you'll need to set a map element `selementid` to an arbitrary value and then use this value to reference this element in the links `selementid1` or `selementid2` properties. When the element is created, this value will be replaced with the correct ID generated by Zabbix. [See example.](create#create_a_host_map) :::
zh-cn	### 参数  `(object/array)` 要创建的拓扑图。  除了[标准拓扑图](object#map)属性外，该方法还接受以下参数  |参数|[类型](/manual/api/reference_commentary#data_types)|说明| |---------|---------------------------------------------------|-----------| |links|array|要在拓扑图上创建的拓扑图 [links](/manual/api/reference/map/object#map_link)。| |selements|array|要在拓扑图上创建的拓扑图 [元素](/manual/api/reference/map/object#map_element)。| |urls|array|要在拓扑图上创建的拓扑图 [URLs](/manual/api/reference/map/object#map_url)。| |users|array|要在拓扑图上创建的拓扑图共享 [user](/manual/api/reference/map/object#map_user) 。| |userGroups|array|要在拓扑图上创建的拓扑图 [用户组](/manual/api/reference/map/object#map_user_group) 共享。| |shapes|array|要在拓扑图上创建的拓扑图 [shapes](/manual/api/reference/map/object#map_shapes)。| |lines|array|要在拓扑图上创建的拓扑图 [lines](/manual/api/reference/map/object#map_lines)。|  :::noteclassic 要创建地图链接，您需要将地图元素 selementid 设置为任意值，然后使用此值在链接 selementid1 或 selementid2 属性中引用此元素。 创建元素时，该值将替换为 Zabbix 生成的正确 ID, [参考](create#create_a_host_map) :::

en-us	### Parameters  `(object/array)` Role properties to be updated.  The `roleid` property must be defined for each role, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard role properties](object#role) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rules|array|Access [rules](object#role_rules) to replace the current access rules assigned to the role.|
zh-cn	### 参数  `(object/array)` 要更新的职责属性。  The `reportid` 该属性为必要配置参数，需要为每个规划报告定义，其它属性则为可选配置。只有符合要求的属性更改才会更新，其它属性则会保持不变。  除此之外，根据[标准规划报告属性](object#report)，该方法接受如下参数。   |参数|[类型](zh/manual/api/reference_commentary#data_types)|说明| |---------|---------------------------------------------------|-----------| |rules|数组|将当前赋予该职责用户的访问规则修改为新的访问[规则](object#role_rules)。|

en-us	### Parameters  `(object/array)` Roles to create.  Additionally to the [standard role properties](object#role), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rules|array|Role [rules](object#role_rules) to be created for the role.|
zh-cn	### 参数  `(object/array)` 要创建的角色用户。  除此之外，根据[标准用户角色特性](object#role), 该方式接受下列参数配置。  |参数|[类型](zh/manual/api/reference_commentary#data_types)|说明| |---------|---------------------------------------------------|-----------| |rules|数组|角色 [角色规则](object#role_rules)用于创建新的角色用户。|

en-us	### Parameters  `(object/array)` [Script properties](object#script) to be updated.  The `scriptid` property must be defined for each script, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged. An exception is `type` property change from 5 (Webhook) to other: the `parameters` property will be cleaned.
zh-cn	### 参数 `(object/array)` 待更新的[脚本属性](object#脚本) 。 所有脚本必须定义`scriptid`属性，其他所有属性都是可选的。只有被传递的属性会被更新，其他所有属性保持不变。例外是`type`属性会从5（Webhook）变成其他：`parameters`属性会被清除。

en-us	### Parameters  `(object/array)` Scripts to create.  The method accepts scripts with the [standard script properties](/manual/api/reference/script/object#script).
zh-cn	### 参数  `(对象/数组)` 要创建的脚本。  此方法接受具有[标准脚本属性](/manual/api/reference/script/object#脚本)的脚本。

en-us	### Parameters  `(object/array)` Template dashboard properties to be updated.  The `dashboardid` property must be specified for each dashboard, all other properties are optional. Only the specified properties will be updated.  Additionally to the [standard template dashboard properties](object#template_dashboard), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |pages|array|Template dashboard [pages](object#template_dashboard_page) to replace the existing dashboard pages.<br><br>Dashboard pages are updated by the `dashboard_pageid` property. New dashboard pages will be created for objects without `dashboard_pageid` property and the existing dashboard pages will be deleted if not reused. Dashboard pages will be ordered in the same order as specified. Only the specified properties of the dashboard pages will be updated. At least one dashboard page object is required for `pages` property.|
zh-cn	### 参数  `(object/array)` 要更新的模板仪表盘属性。  必须为每个仪表盘指定`dashboardid`属性，其他所有属性都是可选的。只会更新指定的属性。  除了[标准模版仪表盘属性](object#template_dashboard)外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |--|--|------| |pages|array|模板仪表盘[页面](object#template_dashboard_page)以替换现有仪表盘页面。<br><br>仪表盘页面按`dashboard_pageid`属性更新。将为没有`dashboard_pageid`属性的对象创建新的仪表盘页面，如果不重用，现有的仪表盘页面将被删除。仪表盘页面将按指定的顺序排序。只会更新仪表盘页面的指定属性。`pages`属性至少需要一个仪表盘页面对象。|

en-us	### Parameters  `(object/array)` Token properties to be updated.  The `tokenid` property must be defined for each token, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  The method accepts tokens with the [standard token properties](object).
zh-cn	### 参数  `(object/array)` 要更新的令牌属性。  必须为每个令牌定义 `tokenid` 属性，所有其他属性都是可选的。只有被传递的属性会被更新，所有其他的将保持不变。  此方法接受具有[标准的令牌属性](object)的的令牌。

en-us	### Parameters  `(object/array)` Tokens to create.  The method accepts tokens with the [standard token properties](object).
zh-cn	### 参数  `(object/array)` 要创建的令牌。  此方法接受令牌带有规范的令牌属性[standard token properties](object)。

en-us	### Parameters  `(object/array)` Trigger properties to be updated.  The `triggerid` property must be defined for each trigger, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard trigger properties](object#trigger) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers that the trigger is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger [tags.](/manual/api/reference/trigger/object#trigger_tag)|  ::: noteimportant The trigger expression has to be given in its expanded form. :::
zh-cn	### 参数  `(object/array)` 需要更新的触发器属性.  `triggerid`属性必须在每个应用集中已定义，其他所有属性为可选项。只有传递过去的属性会被更新，其他所有属性仍然保持不变.  除了 [标准触发器属性](object#trigger) 之外， 该方法还接受以下参数.  | 参数         | [类型](/manual/api/reference_commentary#data_types) | 描述                                                         | | ------------ | --------------------------------------------------- | ------------------------------------------------------------ | | dependencies | array                                               | 依赖触发的触发器.<br><br>触发器必须已定义`triggerid`属性.    | | tags         | array                                               | 触发器 [标签.](/manual/api/reference/trigger/object#trigger_tag) |  ::: noteimportant 指定的触发器表达式必须为展开式. :::

en-us	### Parameters  `(object/array)` Trigger prototypes to create.  Additionally to the [standard trigger prototype properties](object#trigger_prototype) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers and trigger prototypes that the trigger prototype is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger prototype [tags](/manual/api/reference/triggerprototype/object#trigger_prototype_tag).|  ::: noteimportant The trigger expression has to be given in its expanded form and must contain at least one item prototype. :::
zh-cn	### 参数  `(object/array)` 创建触发器原型.  除了 [标准触发器原型属性](object#trigger_prototype) 此方法还接受以下参数.  | 参数         | [类型](/manual/api/reference_commentary#data_types) | 描述                                                         | | ------------ | --------------------------------------------------- | ------------------------------------------------------------ | | dependencies | array                                               | 触发器原型所依赖的触发器和触发器原型.<br><br>触发器必须已定义`triggerid`属性. | | tags         | array                                               | 触发器 [标签](/manual/api/reference/triggerprototype/object#trigger_prototype_tag). |  ::: noteimportant 指定的触发器表达式必须为展开式，并且必须包含至少一个监控项原型. :::

en-us	### Parameters  `(object/array)` Triggers to create.  Additionally to the [standard trigger properties](object#trigger) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dependencies|array|Triggers that the trigger is dependent on.<br><br>The triggers must have the `triggerid` property defined.| |tags|array|Trigger [tags.](/manual/api/reference/trigger/object#trigger_tag)|  ::: noteimportant The trigger expression has to be given in its expanded form. :::
zh-cn	### 参数  `(object/array)` 要创建的触发器.  除了 [标准触发器属性](object#trigger) 之外，该方法还接受以下参数.  | 参数         | [类型](/manual/api/reference_commentary#data_types) | 描述                                                         | | ------------ | --------------------------------------------------- | ------------------------------------------------------------ | | dependencies | array                                               | 目的触发器.<br><br>目的触发器必须存在且已定义`triggerid`属性. | | tags         | array                                               | 触发器标签 [标签.](/manual/api/reference/trigger/object#trigger_tag) |  ::: noteimportant 触发器表达式必须以扩展形式给出. :::

en-us	### Parameters  `(object/array)` [Value map properties](object#value_map) to be updated.  The `valuemapid` property must be defined for each value map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.
zh-cn	 ### 参数  `(object/array)` [Value map properties](object#值映射) 更新。  每个值映射必须要定义`valuemapid`属性，其他属性都是可选的。只会更新传递的属性，其他的属性保持不变。

en-us	### Parameters  `(object/array)` Value maps to create.  The method accepts value maps with the [standard value map properties](object#value_map).
zh-cn	### 参数  `(object/array)` 需要创建的值映射。  此方法接受具有 [standard value map properties](object#值映射)的值映射。

en-us	### Parameters  `(object/array)` Web scenario properties to be updated.  The `httptestid` property must be defined for each web scenario, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard web scenario properties](object#web_scenario), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |steps|array|Scenario [steps](/manual/api/reference/httptest/object#scenario_step) to replace existing steps.| |tags|array|Web scenario [tags](/manual/api/reference/httptest/object#web_scenario_tag).|
zh-cn	 ### 参数  `(object/array)` 需要被更新的Web场景属性。  每个Web场景必须定义`httptestid`属性，其他的所有属性是可选的。只有通过的属性将被更新，其他的属性保持不变。  除了[standard web scenario properties](object#web场景)以外，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |steps|array|场景[步骤](/manual/api/reference/httptest/object#场景步骤)用于替换现有步骤。| |tags|array|Web场景[标签](/manual/api/reference/httptest/object#web场景标签)。|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
zh-cn	### 参数  `(object)` 定义所需输出的参数  该方法仅支持一个参数  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |output|查询|该参数对于[参考注释](/manual/api/reference_commentary#common_get_method_parameters)中所有 `get`方法都适用。|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
zh-cn	 ### 参数  `(object)` 定义需要输出的参数。  此方法只支持一个参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |output|query|此参数对于所有`get`方法都是通用的，在[参考说明](/manual/api/reference_commentary#通用get方法参数)中有描述。|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
zh-cn	### 参数  `(object)` 定义所需输出的参数。  这个方法只支持一个参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |output|query|这个参数对于所有 `get` 方法都是通用的，在 [参考说明](/manual/api/reference_commentary#通用get方法参数) 进行了描述。|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
zh-cn	 ### 参数  `(对象)` 定义期望输出的参数。  此方法只支持一个参数。  |参数|[类型](/manual/api/reference_commentary#数据_类型)|描述| |---------|---------------------------------------------------|-----------| |output|query|此参数与所有 `get`方法相同，描述见[reference commentary](/manual/api/reference_commentary#共同_获取_方法_参数)。|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemids|string/array|Return only trends with the given item IDs.| |time\_from|timestamp|Return only values that have been collected after or at the given time.| |time\_till|timestamp|Return only values that have been collected before or at the given time.| |countOutput|boolean|Count the number of retrieved objects.| |limit|integer|Limit the amount of retrieved objects.| |output|query|Set fields to output.|
zh-cn	### 参数  `(object)` 定义期望输出的参数.  该方法支持以下参数.  | 参数        | [类型](/manual/api/reference_commentary#data_types) | 描述                                      | | ----------- | --------------------------------------------------- | ----------------------------------------- | | itemids     | string/array                                        | 仅返回指定监控项ID的趋势.                 | | time\_from  | timestamp                                           | 仅返回在给定时间之后或在给定时间收集的值. | | time\_till  | timestamp                                           | 仅返回在给定时间之前或在给定时间收集的值. | | countOutput | boolean                                             | 统计检索到的对象的数量.                   | | limit       | integer                                             | 限制检索对象的数量.                       | | output      | query                                               | 设置要输出的字段.                         |

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |taskids|string/array|Return only tasks with the given IDs.| |output|query|These parameters being common for all `get` methods are described in detail in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).| |preservekeys|boolean|^|
zh-cn	### 参数  `(object)` 定义所需输出的参数。  该方法支持以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |taskids|string/array|仅返回具有给定ID的任务。| |output|query|这些参数对于所有`get`方法都是通用的，在[reference commentary](/manual/api/reference_commentary#common_get_method_parameters)中有详细描述。| |preservekeys|boolean|^|

en-us	### Parameters  `(object)` Parameters defining the LLD rules to copy and the target hosts.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |discoveryids|array|IDs of the LLD rules to be copied.| |hostids|array|IDs of the hosts to copy the LLD rules to.|
zh-cn	### 参数  `(object)` 定义要复制的 LLD 规则和目标主机的参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |discoveryids|array|要复制的 LLD 规则的 ID。| |hostids|array|将 LLD 规则复制到的主机的 ID。|

en-us	#### Parameters  |Parameter|Description|Defaults|Example| |--|------|--|---| |*endpoint*|Protocol and address of the endpoint, defined as `protocol://connection_string`<br><br>Possible protocol values: *rtu*, *ascii* (Agent 2 only), *tcp*<br><br>Connection string format:<br><br>with *tcp* - `address:port`<br>with serial line: *rtu*, *ascii* - `port_name:speed:params`<br>where<br>'speed' - 1200, 9600 etc<br>'params' - data bits (5,6,7 or 8), parity (n,e or o for none/even/odd), stop bits (1 or 2)|protocol: none<br><br>*rtu/ascii* protocol:<br>port\_name: none<br>speed: 115200<br>params: 8n1<br><br>*tcp* protocol:<br>address: none<br>port: 502|tcp://192.168.6.1:511<br>tcp://192.168.6.2<br>tcp://\[::1\]:511<br>tcp://::1<br>tcp://localhost:511<br>tcp://localhost<br>rtu://COM1:9600:8n<br>ascii://COM2:1200:7o2<br>rtu://ttyS0:9600<br>ascii://ttyS1| |*slave id*|Modbus address of the device it is intended for (1 to 247), see [MODBUS Messaging Implementation Guide](https://modbus.org/docs/Modbus_Messaging_Implementation_Guide_V1_0b.pdf) (page 23)<br><br>tcp device (not GW) will ignore the field|serial: 1<br><br>tcp: 255 (0xFF)|2| |*function*|Empty or value of a supported function:<br><br>1 - Read Coil,<br>2 - Read Discrete Input,<br>3 - Read Holding Registers,<br>4 - Read Input Registers|empty|3| |*address*|Address of the first registry, coil or input.<br><br>If 'function' is empty, then 'address' should be in range for:<br>Coil - 00001 - 09999<br>Discrete input - 10001 - 19999<br>Input register - 30001 - 39999<br>Holding register - 40001 - 49999<br><br>If 'function' is not empty, the 'address' field will be from 0 till 65535 and used without modification (PDU)|empty function: 00001<br><br>non-empty function: 0|9999| |*count*|Count of sequenced 'type' which will be read from device, where:<br><br>for Coil or Discrete input the 'type' = 1 bit<br>for other cases: (count\*type)/2 = real count of registers for reading<br>If 'offset' is not 0, the value will be added to 'real count'<br>Acceptable range for 'real count' is 1:65535|1|2| |*type*|Data type:<br><br>for Read Coil and Read Discrete Input - *bit*<br><br>for Read Holding Registers and Read Input Registers:<br>*int8* - 8bit<br>*uint8* - 8bit (unsigned)<br>*int16* - 16bit<br>*uint16* - 16bit (unsigned)<br>*int32* - 32bit<br>*uint32* - 32bit (unsigned)<br>*float* - 32bit<br>*uint64* - 64bit (unsigned)<br>*double* - 64bit|bit<br>uint16|uint64| |*endianness*|Endianness type:<br>*be* - Big Endian<br>*le* - Little Endian<br>*mbe* - Mid-Big Endian<br>*mle* - Mid-Little Endian<br><br>Limitations:<br>for 1 bit - be<br>for 8 bits - be,le<br>for 16 bits - be,le|be|le| |*offset*|Number of registers, starting from 'address', the result of which will be discarded.<br><br>The size of each register is 16bit (needed to support equipment that does not support random read access).|0|4|
zh-cn	#### 参数  |参数|说明|默认值|示例| |--|------|--|---| |*endpoint*|端点的协议和地址，定义为 `protocol://connection_string`<br><br>可能的协议值：*rtu*、*ascii*（仅限 Agent 2）、*tcp*<br> <br>连接字符串格式：<br><br>with *tcp* - `address:port`<br>with serial line: *rtu*, *ascii* - `port_name:speed:params`<br>where< br>“速度”- 1200、9600 等<br>“参数”- 数据位（5、6、7 或 8）、奇偶校验（n、e 或 o 表示无/偶数/奇数）、停止位（1 或 2 )|协议：无<br><br>*rtu/ascii* 协议：<br>端口\_名称：无<br>速度：115200<br>参数：8n1<br><br>*tcp* 协议：< br>地址：无<br>端口：502|tcp://192.168.6.1:511<br>tcp://192.168.6.2<br>tcp://\[::1\]:511<br> tcp://::1<br>tcp://localhost:511<br>tcp://localhost<br>rtu://COM1:9600:8n<br>ascii://COM2:1200:7o2< br>rtu://ttyS0:9600<br>ascii://ttyS1| |*slave id*|设备的 Modbus 地址（1 到 247），参见 [MODBUS 消息传递实施指南](https://modbus.org/docs/Modbus_Messaging_Implementation_Guide_V1_0b.pdf)（第 23 页）<br> <br>tcp 设备（不是 GW）将忽略字段|serial: 1<br><br>tcp: 255 (0xFF)|2| |*function*|支持函数的空值或值：<br><br>1 - 读取线圈，<br>2 - 读取离散输入，<br>3 - 读取保持寄存器，<br>4 - 读取输入寄存器 |空|3| |*address*|第一个注册表、线圈或输入的地址。<br><br>如果“函数”为空，则“地址”应在以下范围内：<br>线圈 - 00001 - 09999<br>离散输入 - 10001 - 19999<br>输入寄存器 - 30001 - 39999<br>保持寄存器 - 40001 - 49999<br><br>如果'函数'不为空，'地址'字段将从 0 到 65535 并使用无修改 (PDU)|空函数：00001<br><br>非空函数：0|9999| |*count*|将从设备读取的序列“类型”的计数，其中：<br><br>对于线圈或离散输入，“类型”= 1 位<br>对于其他情况：（计数\*类型 )/2 = 用于读取的寄存器的实际计数<br>如果'offset'不为0，则该值将添加到'real count'<br>'real count'的可接受范围是1:65535|1|2| |*type*|数据类型：<br><br>用于读取线圈和读取离散输入 - *位*<br><br>用于读取保持寄存器和读取输入寄存器：<br>*int8* - 8 位<br >*uint8* - 8 位（无符号）<br>*int16* - 16 位<br>*uint16* - 16 位（无符号）<br>*int32* - 32 位<br>*uint32* - 32 位（无符号）<br> *float* - 32 位<br>*uint64* - 64 位（无符号）<br>*double* - 64 位|位<br>uint16|uint64| |*endianness*|字节序类型：<br>*be* - Big Endian<br>*le* - Little Endian<br>*mbe* - Mid-Big Endian<br>*mle* - Mid-Little Endian<br ><br>限制：<br>1 位 - be<br>8 位 - be,le<br>16 位 - be,le|be|le| |*offset*|寄存器个数，从'address'开始，其结果将被丢弃。<br><br>每个寄存器的大小为16bit（需要支持不支持随机读访问的设备）。 |0|4|

en-us	#### Parameters  Parameters in this file that could be of interest to users:  -   ZBX\_MIN\_PERIOD  Minimum graph period, in seconds. One minute by default.  -   GRAPH\_YAXIS\_SIDE\_DEFAULT  Default location of Y axis in simple graphs and default value for drop down box when adding items to custom graphs. Possible values: 0 - left, 1 - right.  Default: 0  -   ZBX\_SESSION\_NAME (available since 4.0.0)  String used as the name of the Zabbix frontend session cookie.  Default: zbx\_sessionid  -   ZBX\_DATA\_CACHE\_TTL (available since 5.2.0)  TTL timeout in seconds used to invalidate data cache of [Vault response](/manual/config/secrets). Set 0 to disable Vault response caching.  Default: 60  -   SUBFILTER\_VALUES\_PER\_GROUP (available since 6.0.5)  Number of subfilter values per group (For example, in the [latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) subfilter).  Default: 1000
zh-cn	#### 参数  此文件中用户可能感兴趣的参数：  -   ZBX\_MIN\_PERIOD  最小图表周期，以秒为单位。 默认为一分钟。  -   GRAPH\_YAXIS\_SIDE\_DEFAULT  向自定义图表添加项目时，简单图表中 Y 轴的默认位置和下拉框的默认值。 可能的值：0 - 左，1 - 右。  默认值：0  -   ZBX\_SESSION\_NAME（自 4.0.0 起可用）  用作 Zabbix 前端会话 cookie 名称的字符串。  默认值：zbx\_sessionid  -   ZBX\_DATA\_CACHE\_TTL（从 5.2.0 开始可用）  用于使 [Vault 响应](/manual/config/secrets) 的数据缓存无效的 TTL 超时秒数。 设置 0 以禁用 Vault 响应缓存。  默认值：60  -   SUBFILTER\_VALUES\_PER\_GROUP (自 6.0.5 起可用)  每组子过滤值的数量（例如，[最新数据](/manual/web_interface/frontend_sections/monitoring/latest_data)的子过滤）。  默认值：1000

en-us	### Parameters  `(string/array)` IDs of hosts to return scripts for.
zh-cn	### 参数 `(字符串/数组)` 用于检索脚本的主机ID。

en-us	#### Parameter - unquoted string  If the key parameter is an unquoted string, any Unicode character is allowed except comma and right square bracket (\]). Unquoted parameter cannot start with left square bracket (\[).  ![](../../../../../assets/en/manual/config/key_param_unquoted_string.png)
zh-cn	#### 参数 - 不带引号的字符串  如果键值的参数是一个不带引号的字符串，可使用除逗号和右方括号（\]）之外的任何 Unicode 字符。不带引号的参数不能以左方括号（\[）开头。  ![](../../../../../assets/en/manual/config/key_param_unquoted_string.png)

en-us	##### Passive and active checks  Zabbix agents can perform passive and active checks.  In a [passive check](/manual/appendix/items/activepassive#passive_checks) the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result.  [Active checks](/manual/appendix/items/activepassive#active_checks) require more complex processing. The agent must first retrieve a list of items from Zabbix server for independent processing. Then it will periodically send new values to the server.  Whether to perform passive or active checks is configured by selecting the respective monitoring [item type](/manual/config/items/itemtypes/zabbix_agent). Zabbix agent processes items of type 'Zabbix agent' or 'Zabbix agent (active)'.
zh-cn	##### 被动和主动检查  Zabbix agent 可以运行被动检查和主动检查。  在[被动检查](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/items/activepassive#passive-checks)  模式中 agent 应答数据请求。Zabbix server（或 proxy）询求数据，例如 CPU load，然后 Zabbix agent 返还结果。  [主动检查](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/items/activepassive#active-checks)  处理过程将相对复杂。Agent 必须首先从 Zabbix sever 索取监控项列表以进行独立处理，然后会定期发送采集到的新值给 Zabbix server。  是否执行被动或主动检查是通过选择相应的[监控项类型](https://www.zabbix.com/documentation/5.0/zh/manual/config/items/itemtypes/zabbix_agent)来配置的。 Zabbix agent 处理“Zabbix agent”或“Zabbix agent（active）”类型的监控项。

en-us	#### Passive checks  A passive check is a simple data request. Zabbix server or proxy asks for some data (for example, CPU load) and Zabbix agent sends back the result to the server.  **Server request**  For definition of header and data length please refer to [protocol details](/manual/appendix/protocols/header_datalen).      <item key>  **Agent response**      <DATA>[\0<ERROR>]  Above, the part in square brackets is optional and is only sent for not supported items.  For example, for supported items:  1.  Server opens a TCP connection 2.  Server sends **<HEADER><DATALEN>agent.ping** 3.  Agent reads the request and responds with     **<HEADER><DATALEN>1** 4.  Server processes data to get the value, '1' in our case 5.  TCP connection is closed  For not supported items:  1.  Server opens a TCP connection 2.  Server sends **<HEADER><DATALEN>vfs.fs.size\[/nono\]** 3.  Agent reads the request and responds with     **<HEADER><DATALEN>ZBX\_NOTSUPPORTED\\0Cannot obtain     filesystem information: \[2\] No such file or directory** 4.  Server processes data, changes item state to not supported with the     specified error message 5.  TCP connection is closed
zh-cn	#### 被动检查  被动检查是一个简单的数据请求。Zabbix服务器或proxy请求一些数据(例如，CPU负载)，Zabbix agent将结果发送回服务器。  **Server 请求** 头部和数据长度的定义请参考[协议详细信息](/manual/appendix/protocols/header_datalen)      <item key>  **Agent 响应**      <DATA>[\0<ERROR>]  在上面，方括号中的部分是可选的，只发送到不受支持的监控项。  例如, 对于支持的监控项:  1.  Server 打开一个TCP连接 2.  Server 发送 **<HEADER><DATALEN>agent.ping** 3.  Agent 读取请求并响应 **<HEADER><DATALEN>1** 4.  Server 处理数据以获取值, 例如'1'  5.  TCP连接关闭  对于不支持的监控项:  1.  Server 打开一个TCP连接 2.  Server 发送 **<HEADER><DATALEN>vfs.fs.size\[/nono\]** 3.  Agent 读取请求并响应     **<HEADER><DATALEN>ZBX\_NOTSUPPORTED\\0Cannot obtain     filesystem information: \[2\] No such file or directory** 4.  Server 处理数据, 更改监控项状态为不支持并显示指定的错误消息 5.  TCP连接关闭

en-us	#### Passive proxy
zh-cn	#### 被动代理

en-us	#### Pattern examples  |Pattern|Description|Matches|No match| |--|------|--|--| |*\**|Matches all possible keys with or without parameters.|Any|None| |*vfs.file.contents*|Matches `vfs.file.contents` without parameters.|vfs.file.contents|vfs.file.contents\[/etc/passwd\]| |*vfs.file.contents\[\]*|Matches `vfs.file.contents` with empty parameters.|vfs.file.contents\[\]|vfs.file.contents| |*vfs.file.contents\[\*\]*|Matches `vfs.file.contents` with any parameters; will not match `vfs.file.contents` without square brackets.|vfs.file.contents\[\]<br>vfs.file.contents\[/path/to/file\]|vfs.file.contents| |*vfs.file.contents\[/etc/passwd,\*\]*|Matches `vfs.file.contents` with first parameters matching /etc/passwd and all other parameters having any value (also empty).|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd,utf8\]|vfs.file.contents\[/etc/passwd\]<br>vfs.file.contents\[/var/log/zabbix\_server.log\]<br>vfs.file.contents\[\]| |*vfs.file.contents\[\*passwd\*\]*|Matches `vfs.file.contents` with first parameter matching \*passwd\* and no other parameters.|vfs.file.contents\[/etc/passwd\]|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd, utf8\]| |*vfs.file.contents\[\*passwd\*,\*\]*|Matches `vfs.file.contents` with only first parameter matching \*passwd\* and all following parameters having any value (also empty).|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd, utf8\]|vfs.file.contents\[/etc/passwd\]<br>vfs.file.contents\[/tmp/test\]| |*vfs.file.contents\[/var/log/zabbix\_server.log,\*,abc\]*|Matches `vfs.file.contents` with first parameter matching /var/log/zabbix\_server.log, third parameter matching 'abc' and any (also empty) second parameter.|vfs.file.contents\[/var/log/zabbix\_server.log,,abc\]<br>vfs.file.contents\[/var/log/zabbix\_server.log,utf8,abc\]|vfs.file.contents\[/var/log/zabbix\_server.log,,abc,def\]| |*vfs.file.contents\[/etc/passwd,utf8\]*|Matches `vfs.file.contents` with first parameter matching /etc/passwd, second parameter matching 'utf8' and no other arguments.|vfs.file.contents\[/etc/passwd,utf8\]|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd,utf16\]| |*vfs.file.\**|Matches any keys starting with `vfs.file.` without any parameters.|vfs.file.contents<br>vfs.file.size|vfs.file.contents\[\]<br>vfs.file.size\[/var/log/zabbix\_server.log\]| |*vfs.file.\*\[\*\]*|Matches any keys starting with `vfs.file.` with any parameters.|vfs.file.size.bytes\[\]<br>vfs.file.size\[/var/log/zabbix\_server.log, utf8\]|vfs.file.size.bytes| |*vfs.\*.contents*|Matches any key starting with `vfs.` and ending with `.contents` without any parameters.|vfs.mount.point.file.contents<br>vfs..contents|vfs.contents|
zh-cn	#### 模式示例  |模式|描述|匹配|不匹配| |-------|-----------|--------|--------| |*\**|匹配所有可能的带或不带参数的键。|任何|无| |*vfs.file.contents*|匹配不带参数的`vfs.file.contents`。|vfs.file.contents|vfs.file.contents\[/etc/passwd\]| |*vfs.file.contents\[\]*|匹配带有空参数的`vfs.file.contents`。|vfs.file.contents\[\]|vfs.file.contents| |*vfs.file.contents\[\*\]*|匹配 `vfs.file.contents` 和任何参数；不匹配没有方括号的 `vfs.file.contents`。|vfs.file.contents\[\]<br>vfs.file.contents\[/path/to/file\]|vfs.file.contents| |*vfs.file.contents\[/etc/passwd,\*\]*|匹配 `vfs.file.contents` 与第一个参数匹配 /etc/passwd 和所有其他参数具有任何值（也可以为空）。|vfs .file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd,utf8\]|vfs.file.contents\[/etc/passwd\]<br>vfs. file.contents\[/var/log/zabbix\_server.log\]<br>vfs.file.contents\[\]| |*vfs.file.contents\[\*passwd\*\]*|匹配 `vfs.file.contents`，第一个参数匹配 \*passwd\* 而没有其他参数。|vfs.file.contents\[/etc /passwd\]|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd, utf8\]| |*vfs.file.contents\[\*passwd\*,\*\]*|匹配 `vfs.file.contents`，只有第一个参数匹配 \*passwd\* 和所有后续参数具有任何值（也可以为空）。|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd, utf8\]|vfs.file.contents\[/etc/passwd\]<br >vfs.file.contents\[/tmp/test\]| |*vfs.file.contents\[/var/log/zabbix\_server.log,\*,abc\]*|匹配 `vfs.file.contents` 与第一个参数匹配 /var/log/zabbix\_server.log , 第三个参数匹配 'abc' 和任何（也可以为空）第二个参数。|vfs.file.contents\[/var/log/zabbix\_server.log,,abc\]<br>vfs.file.contents\[/ var/log/zabbix\_server.log,utf8,abc\]|vfs.file.contents\[/var/log/zabbix\_server.log,,abc,def\]| |*vfs.file.contents\[/etc/passwd,utf8\]*|匹配 `vfs.file.contents`，第一个参数匹配 /etc/passwd，第二个参数匹配 'utf8'，没有其他参数。|vfs. file.contents\[/etc/passwd,utf8\]|vfs.file.contents\[/etc/passwd,\]<br>vfs.file.contents\[/etc/passwd,utf16\]| |*vfs.file.\**|匹配任何以 `vfs.file.` 开头且不带任何参数的键。|vfs.file.contents<br>vfs.file.size|vfs.file.contents\[\]< br>vfs.file.size\[/var/log/zabbix\_server.log\]| |*vfs.file.\*\[\*\]*|匹配任何以 `vfs.file.` 开头的键和任何参数。|vfs.file.size.bytes\[\]<br>vfs.file.大小\[/var/log/zabbix\_server.log, utf8\]|vfs.file.size.bytes| |*vfs.\*.contents*|匹配任何以 `vfs.` 开头并以 `.contents` 结尾且不带任何参数的键。|vfs.mount.point.file.contents<br>vfs..contents|vfs.contents|

en-us	#### Performance counter parameters  You can deploy some PerfCounter parameters for the monitoring of Windows performance counters.  For example, you can add these to the Zabbix agent configuration file:         PerfCounter=UserPerfCounter1,"\Memory\Page Reads/sec",30        or        PerfCounter=UserPerfCounter2,"\4\24",30  With such parameters in place, you can then simply use *UserPerfCounter1* or *UserPerfCounter2* as the keys for creating the respective items.  Remember to restart Zabbix agent after making changes to the configuration file.
zh-cn	#### 性能计数器参数  你可以部署一些PerfCounter参数，来完成通过Windows性能计数器监控。\  例如，你可以将下面的内容添加到ZABBIX代理配置文件中：         PerfCounter=UserPerfCounter1,"\Memory\Page Reads/sec",30        或        PerfCounter=UserPerfCounter2,"\4\24",30  配置了这些参数后，你就可以简单的使用 *UserPerfCounter1* 或*UserPerfCounter2* 作为key来创建相应的监控项。\  当然，别忘了在更改配置文件后重新启动ZABBIX Agent。\

en-us	#### PostgreSQL  If a value contains a non-ASCII character in non UTF8 encoding - this will lead to a failed SQL query (PGRES\_FATAL\_ERROR:ERROR invalid byte sequence for encoding) and data will not be stored. An appropriate warning message will be written to the *zabbix\_server.log*.\ Relevant for at least PostgreSQL version 9.1.3
zh-cn	#### PostgreSQL  如果一个值在非UTF8编码中包含非ascii字符—这将导致一个失败的SQL查询(PGRES\_FATAL\_ERROR:编码的无效字节序列)和数据将不会被存储。会向*zabbix\_server.log*中写入一个适当的警告消息.\ Relevant for at least PostgreSQL version 9.1.3

en-us	 ### Post-migration  For all databases, once the migration is completed, do the following:  * Verify that everything works as expected.  * Drop old tables:  ``` {.sql} DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```
zh-cn	### 迁移后  对于所有数据库，迁移完成后，执行以下操作：  * 验证一切是否按预期工作。  * 删除旧表：  ``` {.sql} DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```

en-us	#### - Potential errors  Functions return -1 in such situations:  -   specified evaluation period contains no data;  ```{=html} <!-- --> ``` -   result of mathematical operation is not defined[^3];  ```{=html} <!-- --> ``` -   numerical complications (unfortunately, for some sets of input data     range and precision of double-precision floating-point format become     insufficient)[^4].  ::: notetip No warnings or errors are flagged if chosen fit poorly describes provided data or there is just too few data for accurate prediction. :::
zh-cn	#### 4 潜在错误  在如下情况，函数返回 -1:  -   指定的评估期不包含数据；  ```{=html} <!-- --> ``` -   数学运算的结果未定义[^3];  ```{=html} <!-- --> ``` -   数值复杂性（不幸的是，对于某些输入数据集的双精度浮点格式的范围和精度变得不够）[^4]。  ::: notetip 如果选择的拟合不能很好地描述所提供的数据，或者无法准确预测的数据太少，则不会标记警告或错误。 :::

en-us	##### Preparation  Zabbix agent is distributed as a zip archive. After you download the archive you need to unpack it. Choose any folder to store Zabbix agent and the configuration file, e. g.      C:\zabbix  Copy bin\\zabbix\_agentd.exe and conf\\zabbix\_agentd.conf files to c:\\zabbix.  Edit the c:\\zabbix\\zabbix\_agentd.conf file to your needs, making sure to specify a correct "Hostname" parameter.
zh-cn	 ##### 准备  Zabbix agent 作为 zip 压缩文件分发。下载该文件后，您需要将其解压缩。 选择任何文件夹来存储Zabbix代理和配置文件，例如：     C:\zabbix  复制二进制文件 bin\\zabbix\_agentd.exe 和配置文件 conf\\zabbix\_agentd.conf 到 c:\\zabbix 下。  按需编辑 c:\\zabbix\\zabbix\_agentd.conf 配置文件，确保指定了正确的 "Hostname" 参数。