en-us	#### Low-level discovery macros  Even though no low-level discovery macros are created in the returned JSON, these macros can be defined by the user as an additional step, using the [custom LLD macro](/manual/discovery/low_level_discovery#custom_macros) functionality with JSONPath pointing to the discovered values in the returned JSON.  The macros then can be used to create item, trigger, etc prototypes.
zh-cn	#### 低级别自动发现的宏  就算低级别自动发现返回的JSON数组中未创建任何宏，也可以使用一个额外步骤来定义宏，通过使用 [自定义LLD 宏](/manual/discovery/low_level_discovery#custom_macros)，将JSONPath指向返回的JSON值。  然后这些宏就可用于创建监控项、触发器等原型。

en-us	 #### Macros
zh-cn	#### 宏

en-us	Macros for internal actions contain the reason why an item, an LLD-rule, or a trigger became unsupported:   - {ITEM.STATE.ERROR} - for item-based internal notifications;  - {LLDRULE.STATE.ERROR} -  for LLD-rule based internal notifications;  - {TRIGGER.STATE.ERROR} - for trigger-based internal notifications.  For more details, see [Supported macros](/manual/appendix/macros/supported_by_location).
zh-cn	内部动作的宏包含监控项、LLD 规则或触发器变得不受支持的原因：   - {ITEM.STATE.ERROR} - 用于基于监控项的内部通知；  - {LLDRULE.STATE.ERROR} -  用于基于 LLD 规则的内部通知；  - {TRIGGER.STATE.ERROR} - 用于基于触发器的内部通知。  有关更多详细信息，请参阅[支持的宏](/manual/appendix/macros/supported_by_location)。

en-us	#### - Macros  This section allows to define system-wide [user macros](/manual/config/macros/user_macros) as name-value pairs. Note that macro values can be kept as plain text, secret text or Vault secret. Adding a description is also supported.  ![](../../../../../assets/en/manual/web_interface/user_macros_global.png){width="600"}
zh-cn	#### - 宏  本节允许定义系统范围的 [user macros](/manual/config/macros/user_macros) 作为名称-值对。 请注意，宏值可以保存为纯文本、机密文本或 Vault 机密。 还支持添加描述。  ![](../../../../../assets/en/manual/web_interface/user_macros_global.png){width="600"}

en-us	#### Macro support  The following macros may be used in trigger tags:  -   {ITEM.VALUE}, {ITEM.LASTVALUE}, {HOST.HOST}, {HOST.NAME},     {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros     can be used to populate the tag name or tag value -   {INVENTORY.\*}     [macros](/manual/appendix/macros/supported_by_location) can be used     to reference host inventory values from one or several hosts in a     trigger expression -   [User macros](/manual/config/macros/user_macros) and user macro     context is supported for the tag name/value. User macro context may     include low-level discovery macros -   Low-level discovery macros can be used for the tag name/value in     trigger prototypes  The following macros may be used in trigger-based notifications:  -   {EVENT.TAGS} and {EVENT.RECOVERY.TAGS} macros will resolve to a     comma separated list of event tags or recovery event tags -   {EVENT.TAGSJSON} and {EVENT.RECOVERY.TAGSJSON} macros will resolve     to a JSON array containing event tag     [objects](/manual/api/reference/event/object#event_tag) or recovery     event tag objects  The following macros may be used in template, host, item and web scenario tags:  -   {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP},     {HOST.PORT} and {HOST.ID} macros -   {INVENTORY.\*}     [macros](/manual/appendix/macros/supported_by_location) -   [User macros](/manual/config/macros/user_macros) -   Low-level discovery macros can be used in item prototype tags  The following macros may be used in host prototype tags:  -   {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP},     {HOST.PORT} and {HOST.ID} macros -   {INVENTORY.\*}     [macros](/manual/appendix/macros/supported_by_location) -   [User macros](/manual/config/macros/user_macros) -   [Low-level discovery macros](/manual/config/macros/lld_macros) will     be resolved during discovery process and then added to the     discovered host
zh-cn	#### 宏支持  以下宏可用于触发标记：  - {ITEM.VALUE}、{ITEM.LASTVALUE}、{HOST.HOST}、{HOST.NAME}、     {HOST.CONN}、{HOST.DNS}、{HOST.IP}、{HOST.PORT} 和 {HOST.ID} 宏     可用于填充标签名称或标签值 - {INVENTORY.\*}[宏](/manual/appendix/macros/supported_by_location) 可以在主机触发器表达式中引用一个或多个主机资产值 - 标签名称/值支持[用户宏]（/manual/config/macros/user_macros）和用户宏     上下文。用户宏上下文可能包括低级发现宏 - 在触发器原型中，可以使用低级别的发现宏来发现标记名/值  以下宏可用于基于触发器的通知：  - {EVENT.TAGS} 和 {EVENT.RECOVERY.TAGS} 宏将解析为逗号分隔的事件标签或恢复事件标签列表 - {EVENT.TAGSJSON} 和 {EVENT.RECOVERY.TAGSJSON} 宏将解析到包含事件标签的 JSON 数组 [对象](/manual/api/reference/event/object#event_tag) 或恢复事件标记对象  以下宏可用于模板、主机、监控项和网页场景标签：  - {HOST.HOST}、{HOST.NAME}、{HOST.CONN}、{HOST.DNS}、{HOST.IP}、     {HOST.PORT} 和 {HOST.ID} 宏 -   {INVENTORY.\*} [宏](/manual/appendix/macros/supported_by_location) - [用户宏](/manual/config/macros/user_macros) - [低级发现宏](/manual/config/macros/lld_macros)可以在监控项原型标签中使用  以下宏可用于主机原型标签：  - {HOST.HOST}、{HOST.NAME}、{HOST.CONN}、{HOST.DNS}、{HOST.IP}、     {HOST.PORT} 和 {HOST.ID} 宏 -   {INVENTORY.\*} [宏](/manual/appendix/macros/supported_by_location) - [用户宏](/manual/config/macros/user_macros) - 在发现过程中将解析[低级发现宏](/manual/config/macros/lld_macros) ，然后添加到发现主机

en-us	#### maintenance  Changes:\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`,`maintenance.delete`: added strict validation of the methods parameters.\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.get`,`maintenance.update`: dropped support for parameter `timeperiodid` of the timeperiod object.\
zh-cn	 #### 维护  变更：\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`，`maintenance.delete`：添加了对方法参数的严格校验。\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.get`，`maintenance.update`：删除对时间段对象参数`timeperiodid`的支持。\

en-us	#### maintenance  Changes:\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: the parameter `groupids` is now deprecated. Use `groups` instead.\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: the parameter `hostids` is now deprecated. Use `hosts` instead.\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: changed the type of parameters `groups`, `hosts`, `timeperiods` and `tags` from `array` to `object/array`.\
zh-cn	 #### 维护  变更：\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`groupids`现在已被弃用。改为使用`groups`。\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`hostids`现在已被弃用。改为使用`hosts`。\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`groups`，`hosts`，`timeperiods`和`tags`的类型由`array`变更为`object/array`。\

en-us	#### maintenance  Changes:\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: the parameter `groupids` is now deprecated. Use `groups` instead.\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: the parameter `hostids` is now deprecated. Use `hosts` instead.\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`, `maintenance.update`: changed the type of parameters `groups`, `hosts`, `timeperiods` and `tags` from `array` to `object/array`.\
zh-cn	 #### 维护  变更：\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`groupids`现在已被弃用。改为使用`groups`。\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`hostids`现在已被弃用。改为使用`hosts`。\ [ZBXNEXT-6890](https://support.zabbix.com/browse/ZBXNEXT-6890) `maintenance.create`，`maintenance.update`：参数`groups`，`hosts`，`timeperiods`和`tags`的类型由`array`变更为`object/array`。\

en-us	# maintenance.create
zh-cn	# 创建维护模式

en-us	# maintenance.delete
zh-cn	# 删除维护模式

en-us	# maintenance.get
zh-cn	# 获取维护期

en-us	# > Maintenance object  The following objects are directly related to the `maintenance` API.
zh-cn	# > 维护模式对象  如下对象与`维护模式`API关联。

en-us	##### Maintenance periods  The maintenance period window is for scheduling time for a recurring or a one-time maintenance. The form is dynamic with available fields changing based on the *Period type* selected.  ![](../../assets/en/manual/maintenance/maintenance_period.png)  |Period type|Description| |-----------|-----------| |*One time only*|Define the date and time, and the length of the maintenance period.| |*Daily*|*Every day(s)* - maintenance frequency: 1 (default) - every day, 2 - every two days, etc.<br>*At (hour:minute)* - time of the day when maintenance starts<br>*Maintenance period length* - for how long the maintenance will be active.| |*Weekly*|*Every week(s)* - maintenance frequency: 1 (default) - every day, 2 - every two days, etc.<br>*Day of week* - on which day the maintenance should take place.<br>*At (hour:minute)* - time of the day when maintenance starts<br>*Maintenance period length* - for how long the maintenance will be active.| |*Monthly*|*Month* - select all months during which the regular maintenance is carried out.<br>*Date*: **Day of month** - Select this option if the maintenance takes place on the same date each month (for example, every 1st day of the month). Then, select the required day in the new field that appears.<br>*Date*: **Day of week** - Select this option if the maintenance takes place only on certain days (for example, every first Monday of the month). Then, in the drop-down select the required week of the month (first, second, third, fourth, or last) and mark the checkboxes for maintenance day(s).<br>*At (hour:minute)* - time of the day when maintenance starts<br>*Maintenance period length* - for how long the maintenance will be active.|  When done, press *Add* to add the maintenance period to the *Periods* block.  Notes:  -   When *Every day/Every week* parameter is greater than 1, the     starting day or week is the day/week that the *Active since* time     falls on. For example:     -   with *Active since* set to January 1st at 12:00 and a one-hour         maintenance set for every two days at 11pm will result in the         first maintenance period starting on January 1st at 11pm, while         the second maintenance period will start on January 3rd at 11pm;     -   with the same *Active since* time and a one-hour maintenance set         for every two days at 1am, the first maintenance period will         start on January 3rd at 1am, while the second maintenance period         will start on January 5th at 1am. -   Daylight Saving Time (**DST**) changes do not affect how long the     maintenance will be. Let's say we have a two-hour maintenance that     usually starts at 1am and finishes at 3am:     -   If after one hour of maintenance (at 2am) a DST change happens         and current time changes from 2:00 to 3:00, the maintenance will         continue for one more hour till 4:00;     -   If after two hours of maintenance (at 3am) a DST change happens         and current time changes from 3:00 to 2:00, the maintenance will         stop because two hours have passed.
zh-cn	##### 维护期间  维护期间窗口用于安排定期或一次性维护的时间。该表单是动态的，可用字段根据所选的*期间类型（Period type）*而变化。  ![](../../assets/en/manual/maintenance/maintenance_period.png)  |期间类型（Period type）|描述（Description）| |-----------|-----------| |*一次性（One time only）*|定义日期和时间，以及维护期的长度。| |*每日（Daily）*|*每天（Every day(s)）* - 维护频率：1（默认） - 每天，2 - 每两天等。<br>*于（时:分）（At (hour:minute)）* - 维护开始的一天中的时间<br>*维护期长度（Maintenance period length）* - 维护将持续多长时间。| |*每周（Weekly）*|*每周（Every week(s)）* - 维护频率：1（默认） - 每天，2 - 每两天等。 <br>*星期几（Day of week）* - 应该在哪一天进行维护。<br>*在（时:分）（At (hour:minute)）* - 维护开始的一天中的时间<br>*维护期长度（Maintenance period length）* - 维护将持续多长时间。| |*每月（Monthly）*|*月（Month）* - 选择进行定期维护的所有月份。<br>*日期（Date）*: **月的指定天（Day of month）** - 如果维护发生在每个月的同一日期（例如，每月的第一天），请选择此选项。然后，在出现的新字段中选择所需的日期。<br>*日期（Date）*: **星期几（Day of week）** - 如果仅在特定日期（例如，每月的第一个星期一）进行维护，请选择此选项。然后，在下拉列表中选择每月所需的一周（第一、第二、第三、第四或最后一周）并标记维护日的复选框。<br>*于（时:分）（At (hour:minute)）* - 一天中开始维护的时间<br>*维护期长度（Maintenance period length）* - 维护将持续多长时间。|  完成后，点击 *Add* 将维护期添加到 *期间（Periods）*块。  注意：  -   当 *Every day/Every week* 参数大于 1 时，起始日或周为 *Active since* 时间所在的日/周。例如：     -   将 *Active since* 设置为 1 月 1 日 12:00 且 每两天晚上 11 点设置一小时维护，将导致第一个维护期从 1 月 1 日晚上 11 点开始，而第二个维护期将从 1 月 3 日晚上 11 点开始;     -   在相同的 *Active since* 时间和每两天凌晨 1 点设置一小时维护的情况下，第一个维护期将从 1 月 3 日凌晨 1 点开始，而第二个维护期将从 1 月 5 日凌晨 1 点开始。  -   夏令时 (**DST**) 更改不会影响维护时间。假设我们有两个小时的维护，通常从凌晨 1 点开始，到凌晨 3 点结束：     -   如果在维护一小时后（凌晨 2 点）发生 DST 更改并且当前时间从 2:00 更改为 3:00，则维护将再持续一小时直到 4:00；     -   如果在维护两个小时后（凌晨 3 点）发生 DST 更改并且当前时间从 3:00 更改为 2:00，则维护将停止，因为两个小时已过。

en-us	### Maintenance  The maintenance object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |maintenanceid|string|*(readonly)* ID of the maintenance.| |**name**<br>(required)|string|Name of the maintenance.| |**active\_since**<br>(required)|timestamp|Time when the maintenance becomes active.| |**active\_till**<br>(required)|timestamp|Time when the maintenance stops being active.| |description|string|Description of the maintenance.| |maintenance\_type|integer|Type of maintenance.<br><br>Possible values:<br>0 - *(default)* with data collection;<br>1 - without data collection.| |tags\_evaltype|integer|Problem tag evaluation method.<br><br>Possible values:<br>0 - *(default)* And/Or;<br>2 - Or.|  
zh-cn	### Maintenance 维护模式  The maintenance object has the following properties. 维护模式对象有如下属性。  |Property|Type|Description| |--------|----|-----------| |maintenanceid|string|*(readonly)* ID of the maintenance. 维护模式的ID。| |**name**<br>(required)|string|Name of the maintenance. 维护模式的名称。| |**active\_since**<br>(required)|timestamp|Time when the maintenance becomes active. 维护模式生效的时刻。| |**active\_till**<br>(required)|timestamp|Time when the maintenance stops being active. 维护模式失效的时刻。| |description|string|Description of the maintenance. 维护模式说明。| |maintenance\_type|integer|Type of maintenance. 维护模式类型。<br><br>Possible values: 可能的值：<br>0 - *(default)* with data collection;<br>1 - without data collection.|  

en-us	### Maintenance  The maintenance object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |maintenanceid|string|*(readonly)* ID of the maintenance.| |**name**<br>(required)|string|Name of the maintenance.| |**active\_since**<br>(required)|timestamp|Time when the maintenance becomes active.<br><br>The given value will be rounded down to minutes.| |**active\_till**<br>(required)|timestamp|Time when the maintenance stops being active.<br><br>The given value will be rounded down to minutes.| |description|string|Description of the maintenance.| |maintenance\_type|integer|Type of maintenance.<br><br>Possible values:<br>0 - *(default)* with data collection;<br>1 - without data collection.| |tags\_evaltype|integer|Problem tag evaluation method.<br><br>Possible values:<br>0 - *(default)* And/Or;<br>2 - Or.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	###  维护  维护对象有如下属性。  |属性|类型|描述| |--------|----|-----------| |maintenanceid|string|*(只读)*  维护周期的ID。| |**name**<br>(必需)|string|维护周期的名称。| |**active\_since**<br>(必需)|timestamp| 维护周期生效的开始时间。| |**active\_till**<br>(必需)|timestamp| 维护周期结束时间。| |description|string| 维护周期说明。| |maintenance\_type|integer|维护周期类型.<br><br>可选值:<br>0 - *(默认)* 收集数据;<br>1 - 不收集数据.| |tags\_evaltype|integer|问题标签多条件逻辑.<br><br>可选值:<br>0 - *(默认)* And/Or;<br>2 - Or.| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Maintenance  This class is designed to work with maintenances.  Object references:\  -   [Maintenance](/manual/api/reference/maintenance/object#maintenance) -   [Time period](/manual/api/reference/maintenance/object#time_period)  Available methods:\  -   [maintenance.create](/manual/api/reference/maintenance/create) -     creating new maintenances -   [maintenance.delete](/manual/api/reference/maintenance/delete) -     deleting maintenances -   [maintenance.get](/manual/api/reference/maintenance/get) -     retrieving maintenances -   [maintenance.update](/manual/api/reference/maintenance/update) -     updating maintenances
zh-cn	# 维护  此类用于维护. 对象引用:\  -   [维护](/manual/api/reference/maintenance/object#维护模式) -   [时间段](/manual/api/reference/maintenance/object#时间段)  可用方法:\  -   [maintenance.create](/manual/api/reference/maintenance/create)创建维护 -   [maintenance.delete](/manual/api/reference/maintenance/delete) 删除维护 -   [maintenance.get](/manual/api/reference/maintenance/get)检索维护 -   [maintenance.update](/manual/api/reference/maintenance/update)更新维护

en-us	# maintenance.update
zh-cn	# 更新维护期设置

en-us	 ### Makefile targets  Loadable plugins provided by Zabbix have simple makefiles with the following targets:  |Target|Description| |--|--------| |make|Build plugin.| |make clean|Delete all files that are normally created by building the plugin.| |make check|Perform self-tests. A real PostgreSQL database is required.| |make style|Check Go code style with 'golangci-lint'.| |make format|Format Go code with 'go fmt'.| |make dist|Create an archive containing the plugin sources and sources of all packages needed to build the plugin and its self-tests.|
zh-cn	 ### 生成文件目标  Zabbix 提供的可加载插件具有具有以下目标的简单 makefile：  |目标|描述| |--|--------| |make|构建插件。| |make clean|删除通常通过构建插件创建的所有文件。| |make check|进行自检。 需要一个真正的 PostgreSQL 数据库。| |make style|使用“golangci-lint”检查 Go 代码风格。| |make format|使用“go fmt”格式化 Go 代码。| |make dist|创建一个存档，其中包含构建插件及其自测所需的所有包的插件源和源。|

en-us	### Managing HA cluster  The current status of the HA cluster can be managed using the dedicated [runtime control](/manual/concepts/server#runtime_control) options:  -   `ha_status` - log HA cluster status in the Zabbix server log (and to stdout) -   `ha_remove_node=target` - remove an HA node identified by its     \<target\> - number of the node in the list (the number can be     obtained from the output of running ha\_status), e.g.:  ``` zabbix_server -R ha_remove_node=2 ```  Note that active/standby nodes cannot be removed.  -   `ha_set_failover_delay=delay` - set HA failover delay (between 10 seconds and 15 minutes; time     suffixes are supported, e.g. 10s, 1m)  Node status can be monitored:  -   in *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)* -   in the *System information* dashboard widget -   using the `ha_status` runtime control option of the server (see     above).  The `zabbix[cluster,discovery,nodes]` internal item can be used for node discovery, as it returns a JSON with the high-availability node information.
zh-cn	### 管理 HA 集群  可以使用专用的 [运行时控制](/manual/concepts/server#runtime_control) 选项管理 HA 集群的当前状态：  - · `ha_status` - 在 Zabbix 服务器日志中记录 HA 集群状态（并输出到标准输出） - · `ha_remove_node=target` - 删除由其 \<target\> 标识的 HA 节点 - 列表中节点的编号（该编号可以从运行 ha\_status 的输出中获得），例如：  ``` zabbix_server -R ha_remove_node=2 ```  请注意，主备节点不能被删除。  - · `ha_set_failover_delay=delay` - 设置 HA 故障转移延迟（10 秒到 15 分钟之间；支持时间后缀，例如 10s、1m）  可以监控节点状态：  - · 在*报告* → *[系统信息](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)* - · 在*系统信息*仪表板小部件中 - · 使用服务器的 `ha_status` 运行时控制选项（见上文）。  `zabbix[cluster,discovery,nodes]` 内部监控项可用于节点发现，因为它返回具有高可用性节点信息的 JSON。

en-us	##### - Mandatory interface  The only mandatory function is **zbx\_module\_api\_version()**:  ``` {.c} int zbx_module_api_version(void); ```  This function should return the API version implemented by this module and in order for the module to be loaded this version must match module API version supported by Zabbix. Version of module API supported by Zabbix is ZBX\_MODULE\_API\_VERSION. So this function should return this constant. Old constant ZBX\_MODULE\_API\_VERSION\_ONE used for this purpose is now defined to equal ZBX\_MODULE\_API\_VERSION to preserve source compatibility, but it's usage is not recommended.
zh-cn	#### - 强制接口  唯一的强制函数是**zbx\_module\_api\_version()**:\  ``` {.c} int zbx_module_api_version(void); ```  此函数应该返回实现这个模块的API版本，并且为了模块能被加载，这个版本必须与ZABBIX支持的模块API版本相匹配。Zabbix支持的模块API的版本为ZBX\_MODULE\_API\_VERSION。所以这个函数应该返回这个常量。为了保持源代码兼容性，现在将旧常量ZBX\_MODULE\_API\_VERSION\_ONE，替换成ZBX\_MODULE\_API\_VERSION，但不建议使用它。\

en-us	##### Manifest preparation  Each module is expected to have a manifest.json file with the following fields in JSON format:  |Parameter|Required|Type|Default|Description| |---------|--------|----|-------|-----------| |manifest\_version|Yes|Double|\-|Manifest version of the module. Currently supported version is **1**.| |id|Yes|String|\-|Module ID. Only one module with given ID can be enabled at the same time.| |name|Yes|String|\-|Module name as displayed in the Administration section.| |version|Yes|String|\-|Module version as displayed in the Administration section.| |namespace|Yes|String|\-|PHP namespace for Module.php and action classes.| |author|No|String|""|Module author as displayed in the Administration section.| |url|No|String|""|Module URL as displayed in the Administration section.| |description|No|String|""|Module description as displayed in the Administration section.| |actions|No|Object|{}|Actions to register with this module. See Actions.| |config|No|Object|{}|Module configuration.|  For reference, please see an example of manifest.json in the [Reference](#reference) section.
zh-cn	 ##### 清单准备  每个模块都应该有一个 manifest.json 文件，其中包含以下 JSON 格式的字段：  |参数|必填|类型|默认值|描述| |---------|--------|----|-------|-----------| |manifest\_version|是|Double|\-|模块的清单版本。当前支持的版本为 **1**。| |id|是|String|\-|模块标识。只能同时启用一个具有给定 ID 的模块。| |name|是|String|\-|“管理”部分中显示的模块名称。| |version|是|String|\-|“管理”部分中显示的模块版本。| |namespace|是|String|\-|Module.php和操作类的 PHP 命名空间。| |author|否|String|""|“管理”部分中显示的模块作者。| |url|否|String|""|“管理”部分中显示的模块URL。| |description|否|String|""|“管理”部分中显示的模块描述。| |actions|否|Object|{}|注册此模块的操作。查看“动作”| |config|否|Object|{}|模块配置|  有关参考，请参阅 [Reference](#reference)部分中 manifest.json 的示例。

en-us	##### Manual mode  When [configuring a host](host), in the *Host inventory* tab you can enter such details as the type of device, serial number, location, responsible person, etc - data that will populate inventory information.  If a URL is included in host inventory information and it starts with 'http' or 'https', it will result in a clickable link in the *Inventory* section.
zh-cn	##### 手动模式  当[配置主机](host)时，在 *Host inventory（资产记录）*选项卡中，你可以输入设备类型、序列号、位置、负责人等详细信息 - 这些数据将填充资产信息。  如果主机资产信息中包含URL，并以'http'或'https'开头，则会在 *Inventory* 中呈现为可点击的链接。

en-us	# map.create
zh-cn	# 拓扑图创建

en-us	# map.delete
zh-cn	# 拓扑图删除

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 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 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 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  The map element object defines an object displayed on a map. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |selementid|string|*(readonly)* ID of the map element.| |**elements**<br>(required)|array|Element data object. Required for host, host group, trigger and map type elements.| |**elementtype**<br>(required)|integer|Type of map element.<br><br>Possible values:<br>0 - host;<br>1 - map;<br>2 - trigger;<br>3 - host group;<br>4 - image.| |**iconid\_off**<br>(required)|string|ID of the image used to display the element in default state.| |areatype|integer|How separate host group hosts should be displayed.<br><br>Possible values:<br>0 - *(default)* the host group element will take up the whole map;<br>1 - the host group element will have a fixed size.| |elementsubtype|integer|How a host group element should be displayed on a map.<br><br>Possible values:<br>0 - *(default)* display the host group as a single element;<br>1 - display each host in the group separately.| |evaltype|integer|Map element tag filtering condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>2 - OR.| |height|integer|Height of the fixed size host group element in pixels.<br><br>Default: 200.| |iconid\_disabled|string|ID of the image used to display disabled map elements. Unused for image elements.| |iconid\_maintenance|string|ID of the image used to display map elements in maintenance. Unused for image elements.| |iconid\_on|string|ID of the image used to display map elements with problems. Unused for image elements.| |label|string|Label of the element.| |label\_location|integer|Location of the map element label.<br><br>Possible values:<br>-1 - *(default)* default location;<br>0 - bottom;<br>1 - left;<br>2 - right;<br>3 - top.| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|*(readonly)* ID of the map that the element belongs to.| |urls|array|Map element URLs.<br><br>The map element URL object is [described in detail below](object#map_element_url).| |use\_iconmap|integer|Whether icon mapping must be used for host elements.<br><br>Possible values:<br>0 - do not use icon mapping;<br>1 - *(default)* use icon mapping.| |viewtype|integer|Host group element placing algorithm.<br><br>Possible values:<br>0 - *(default)* grid.| |width|integer|Width of the fixed size host group element in pixels.<br><br>Default: 200.| |x|integer|X-coordinates of the element in pixels.<br><br>Default: 0.| |y|integer|Y-coordinates of the element in pixels.<br><br>Default: 0.|
zh-cn	### 拓扑图元素  拓扑图元素对象定义了在拓扑图上显示的对象.它有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |selementid|string|*(readonly)* 拓扑图元素的 ID.| |**元素**<br>（必需）|array|元素数据对象.主机、主机组、触发器和映射类型元素是必需的.| |**elementtype**<br>（必需）|integer|拓扑图元素的类型.<br><br>参考值：<br>0 - 主机；<br>1 - 拓扑图；<br>2 - 触发器； <br>3 - 主机组；<br>4 - 图片.| |**iconid\_off**<br>（必需）|string|用于在默认状态下显示元素的图像的 ID.| |areatype|integer|应如何显示单独的主机组主机.<br><br>参考值：<br>0 - *（默认）* 主机组元素将占据整个拓扑图；<br>1 -主机组元素将具有固定大小.| |elementsubtype|integer|主机组元素应如何显示在拓扑图上.<br><br>参考值：<br>0 - *（默认）* 将主机组显示为单个元素；<br>1 - | 分别显示组中的每个主机. |evaltype|integer|拓扑图元素标签过滤条件评估方法.<br><br>可用值：<br>0 - *(默认)* AND / OR;<br>2 - OR.| |height|integer|固定大小的主机组元素的高度，以像素为单位.<br><br>默认值：200.| |iconid\_disabled|string|用于显示禁用拓扑图元素的图像 ID.未用于图像元素.| |iconid\_maintenance|string|用于在维护中显示拓扑图元素的图像 ID.未用于图像元素.| |iconid\_on|string|用于显示有问题的拓扑图元素的图像 ID.未用于图像元素.| |label|string|元素的标签.| |label\_location|integer|拓扑图元素标签的位置.<br><br>参考值：<br>-1 - *（默认）* 默认位置；<br>0 - 底部；<br>1 - 左侧;<br>2 - 右;<br>3 - 顶部.| |permission|integer|权限级别的类型.<br><br>参考值：<br>-1 - 无；<br>2 - 只读；<br>3 - 读写.| |sysmapid|string|*(readonly)* 元素所属映射的 ID.| |urls|array|拓扑图元素 URL.<br><br>拓扑图元素 URL 对象是[详细描述如下](object#map_element_url).| |use\_iconmap|integer|是否必须对宿主元素使用图标映射.<br><br>参考值：<br>0 - 不使用图标映射；<br>1 - *（默认）* 使用图标映射.| |viewtype|integer|主机组元素放置算法.<br><br>参考值：<br>0 - *（默认）*网格.| |width|integer|固定大小的主机组元素的宽度，以像素为单位.<br><br>默认值：200.| |x|integer|元素的 X 坐标，以像素为单位.<br><br>默认值：0.| |y|integer|元素的 Y 坐标，以像素为单位.<br><br>默认值：0.|

en-us	### Map element  The map element object defines an object displayed on a map. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |selementid|string|*(readonly)* ID of the map element.| |**elements**<br>(required)|array|Element data object. Required for host, host group, trigger and map type elements.| |**elementtype**<br>(required)|integer|Type of map element.<br><br>Possible values:<br>0 - host;<br>1 - map;<br>2 - trigger;<br>3 - host group;<br>4 - image.| |**iconid\_off**<br>(required)|string|ID of the image used to display the element in default state.| |areatype|integer|How separate host group hosts should be displayed.<br><br>Possible values:<br>0 - *(default)* the host group element will take up the whole map;<br>1 - the host group element will have a fixed size.| |elementsubtype|integer|How a host group element should be displayed on a map.<br><br>Possible values:<br>0 - *(default)* display the host group as a single element;<br>1 - display each host in the group separately.| |evaltype|integer|Map element tag filtering condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>2 - OR.| |height|integer|Height of the fixed size host group element in pixels.<br><br>Default: 200.| |iconid\_disabled|string|ID of the image used to display disabled map elements. Unused for image elements.| |iconid\_maintenance|string|ID of the image used to display map elements in maintenance. Unused for image elements.| |iconid\_on|string|ID of the image used to display map elements with problems. Unused for image elements.| |label|string|Label of the element.| |label\_location|integer|Location of the map element label.<br><br>Possible values:<br>-1 - *(default)* default location;<br>0 - bottom;<br>1 - left;<br>2 - right;<br>3 - top.| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|*(readonly)* ID of the map that the element belongs to.| |urls|array|Map element URLs.<br><br>The map element URL object is [described in detail below](object#map_element_url).| |use\_iconmap|integer|Whether icon mapping must be used for host elements.<br><br>Possible values:<br>0 - do not use icon mapping;<br>1 - *(default)* use icon mapping.| |viewtype|integer|Host group element placing algorithm.<br><br>Possible values:<br>0 - *(default)* grid.| |width|integer|Width of the fixed size host group element in pixels.<br><br>Default: 200.| |x|integer|X-coordinates of the element in pixels.<br><br>Default: 0.| |y|integer|Y-coordinates of the element in pixels.<br><br>Default: 0.|
zh-cn	### 拓扑图元素  拓扑图元素对象定义了在拓扑图上显示的对象.它有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |selementid|string|*(readonly)* 拓扑图元素的 ID.| |**元素**<br>（必需）|array|元素数据对象.主机、主机组、触发器和映射类型元素是必需的.| |**elementtype**<br>（必需）|integer|拓扑图元素的类型.<br><br>参考值：<br>0 - 主机；<br>1 - 拓扑图；<br>2 - 触发器； <br>3 - 主机组；<br>4 - 图片.| |**iconid\_off**<br>（必需）|string|用于在默认状态下显示元素的图像的 ID.| |areatype|integer|应如何显示单独的主机组主机.<br><br>参考值：<br>0 - *（默认）* 主机组元素将占据整个拓扑图；<br>1 -主机组元素将具有固定大小.| |elementsubtype|integer|主机组元素应如何显示在拓扑图上.<br><br>参考值：<br>0 - *（默认）* 将主机组显示为单个元素；<br>1 - | 分别显示组中的每个主机. |evaltype|integer|拓扑图元素标签过滤条件评估方法.<br><br>可用值：<br>0 - *(默认)* AND / OR;<br>2 - OR.| |height|integer|固定大小的主机组元素的高度，以像素为单位.<br><br>默认值：200.| |iconid\_disabled|string|用于显示禁用拓扑图元素的图像 ID.未用于图像元素.| |iconid\_maintenance|string|用于在维护中显示拓扑图元素的图像 ID.未用于图像元素.| |iconid\_on|string|用于显示有问题的拓扑图元素的图像 ID.未用于图像元素.| |label|string|元素的标签.| |label\_location|integer|拓扑图元素标签的位置.<br><br>参考值：<br>-1 - *（默认）* 默认位置；<br>0 - 底部；<br>1 - 左侧;<br>2 - 右;<br>3 - 顶部.| |permission|integer|权限级别的类型.<br><br>参考值：<br>-1 - 无；<br>2 - 只读；<br>3 - 读写.| |sysmapid|string|*(readonly)* 元素所属映射的 ID.| |urls|array|拓扑图元素 URL.<br><br>拓扑图元素 URL 对象是[详细描述如下](object#map_element_url).| |use\_iconmap|integer|是否必须对宿主元素使用图标映射.<br><br>参考值：<br>0 - 不使用图标映射；<br>1 - *（默认）* 使用图标映射.| |viewtype|integer|主机组元素放置算法.<br><br>参考值：<br>0 - *（默认）*网格.| |width|integer|固定大小的主机组元素的宽度，以像素为单位.<br><br>默认值：200.| |x|integer|元素的 X 坐标，以像素为单位.<br><br>默认值：0.| |y|integer|元素的 Y 坐标，以像素为单位.<br><br>默认值：0.|

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 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 element URL  The map element URL object defines a clickable link that will be available for a specific map element. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapelementurlid|string|*(readonly)* ID of the map element URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |selementid|string|ID of the map element that the URL belongs to.|
zh-cn	### 拓扑图元素URL  拓扑图元素URL对象定义了一个可点击的链接,可用于拓扑图上特定类型的所有元素.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapurlid|string|*(只读)* 拓扑图URL ID| |**name**<br>(required)|string |链接标题. | |**url**<br>(required)|string |链接URL | |elementtype      |integer      |可以使用在URL上的拓扑图元素类型.<br><br>请参考 [拓扑图元素"类型"属性](object#map_element)  拓扑图元素可用URL类型<br><br>默认：0| |sysmapid|string|所属URL的拓扑图ID|

en-us	#### Map element URL  The map element URL object defines a clickable link that will be available for a specific map element. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |sysmapelementurlid|string|*(readonly)* ID of the map element URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |selementid|string|ID of the map element that the URL belongs to.|
zh-cn	### 拓扑图元素URL  拓扑图元素URL对象定义了一个可点击的链接,可用于拓扑图上特定类型的所有元素.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapurlid|string|*(只读)* 拓扑图URL ID| |**name**<br>(required)|string |链接标题. | |**url**<br>(required)|string |链接URL | |elementtype      |integer      |可以使用在URL上的拓扑图元素类型.<br><br>请参考 [拓扑图元素"类型"属性](object#map_element)  拓扑图元素可用URL类型<br><br>默认：0| |sysmapid|string|所属URL的拓扑图ID|

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

en-us	#### Map lines  Create a map line.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map API lines",         "width": 500,         "height": 500,         "lines": [             {                 "x1": 30,                 "y1": 10,                 "x2": 100,                 "y2": 50,                 "line_type": 1,                 "line_width": 10,                 "line_color": "009900"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "11"         ]     },     "id": 1 } ```
zh-cn	#### 拓扑图线  创建拓扑图线。  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map API lines",         "width": 500,         "height": 500,         "lines": [             {                 "x1": 30,                 "y1": 10,                 "x2": 100,                 "y2": 50,                 "line_type": 1,                 "line_width": 10,                 "line_color": "009900"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "11"         ]     },     "id": 1 } ```

en-us	### Map lines  The map line object defines a line displayed on a map. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmap\_shapeid|string|*(readonly)* ID of the map shape element.| |x1|integer|X-coordinates of the line point 1 in pixels.<br><br>Default: 0.| |y1|integer|Y-coordinates of the line point 1 in pixels.<br><br>Default: 0.| |x2|integer|X-coordinates of the line point 2 in pixels.<br><br>Default: 200.| |y2|integer|Y-coordinates of the line point 2 in pixels.<br><br>Default: 200.| |line\_type|integer|Type of the lines.<br><br>Possible values:<br>0 - none;<br>1 - `—————`;<br>2 - `·····`;<br>3 - `- - -`.<br><br>Default: 0.| |line\_width|integer|Width of the lines in pixels.<br><br>Default: 0.| |line\_color|string|Line color.<br><br>Default: '000000'.| |zindex|integer|Value used to order all shapes and lines (z-index).<br><br>Default: 0.|
zh-cn	### 拓扑图线  该对象定义在拓扑图上显示的线.它有以下属性：  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|--------|--------| |sysmap\_shapeid|string|*(只读)* 拓扑图形状元素的 ID.| |x1|integer|线点 1 的 X 坐标，以像素为单位.<br><br>默认值：0.| |y1|integer|线点 1 的 Y 坐标，以像素为单位.<br><br>默认值：0.| |x2|integer|线点 2 的 X 坐标，以像素为单位.<br><br>默认值：200.| |y2|integer|线点 2 的 Y 坐标，以像素为单位.<br><br>默认值：200.| |line\_type|integer|线的类型.<br><br>参考值：<br>0 - 无；<br>1 - `—————`;<br>2 - `··· ··`;<br>3 - `- - -`.<br><br>默认值：0.| |line\_width|integer|线条的宽度，以像素为单位.<br><br>默认值：0.| |line\_color|string|线条颜色.<br><br>默认值：'000000'.| |zindex|integer|用于对所有形状和线条进行排序的值 (z-index).<br><br>默认值：0.|

en-us	### Map link  The map link object defines a link between two map elements. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |linkid|string|*(readonly)* ID of the map link.| |**selementid1**<br>(required)|string|ID of the first map element linked on one end.| |**selementid2**<br>(required)|string|ID of the first map element linked on the other end.| |color|string|Line color as a hexadecimal color code.<br><br>Default: `000000`.| |drawtype|integer|Link line draw style.<br><br>Possible values:<br>0 - *(default)* line;<br>2 - bold line;<br>3 - dotted line;<br>4 - dashed line.| |label|string|Link label.| |linktriggers|array|Map link triggers to use as link status indicators.<br><br>The map link trigger object is [described in detail below](object#map_link_trigger).| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|ID of the map the link belongs to.|
zh-cn	### 拓扑图链接  拓扑图链接对象定义了两个拓扑图元素之间的链接.它有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |linkid|string|*(readonly)* 拓扑图链接的 ID.| |**selementid1**<br>（必需）|string|连接在一端的第一个拓扑图元素的 ID.| |**selementid2**<br>（必需）|string|连接到另一端的第一个拓扑图元素的 ID.| |color|string|作为十六进制颜色代码的线条颜色.<br><br>默认值：`000000`.| |drawtype|integer|链接线绘制样式.<br><br>参考值：<br>0 - *（默认）* 线；<br>2 - 粗线；<br>3 - 虚线；<br> 4 - 虚线.| |label|string|链接标签.| |linktriggers|array|拓扑图链接触发器用作链接状态指示器.<br><br>拓扑图链接触发器对象[详细描述如下](object#map_link_trigger).| |permission|integer|权限级别的类型.<br><br>参考值：<br>-1 - 无；<br>2 - 只读；<br>3 - 读写.| |sysmapid|string|链接所属拓扑图的ID.|

en-us	### Map link  The map link object defines a link between two map elements. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |linkid|string|*(readonly)* ID of the map link.| |**selementid1**<br>(required)|string|ID of the first map element linked on one end.| |**selementid2**<br>(required)|string|ID of the first map element linked on the other end.| |color|string|Line color as a hexadecimal color code.<br><br>Default: `000000`.| |drawtype|integer|Link line draw style.<br><br>Possible values:<br>0 - *(default)* line;<br>2 - bold line;<br>3 - dotted line;<br>4 - dashed line.| |label|string|Link label.| |linktriggers|array|Map link triggers to use as link status indicators.<br><br>The map link trigger object is [described in detail below](object#map_link_trigger).| |permission|integer|Type of permission level.<br><br>Possible values:<br>-1 - none;<br>2 - read only;<br>3 - read-write.| |sysmapid|string|ID of the map the link belongs to.|
zh-cn	### 拓扑图链接  拓扑图链接对象定义了两个拓扑图元素之间的链接.它有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |linkid|string|*(readonly)* 拓扑图链接的 ID.| |**selementid1**<br>（必需）|string|连接在一端的第一个拓扑图元素的 ID.| |**selementid2**<br>（必需）|string|连接到另一端的第一个拓扑图元素的 ID.| |color|string|作为十六进制颜色代码的线条颜色.<br><br>默认值：`000000`.| |drawtype|integer|链接线绘制样式.<br><br>参考值：<br>0 - *（默认）* 线；<br>2 - 粗线；<br>3 - 虚线；<br> 4 - 虚线.| |label|string|链接标签.| |linktriggers|array|拓扑图链接触发器用作链接状态指示器.<br><br>拓扑图链接触发器对象[详细描述如下](object#map_link_trigger).| |permission|integer|权限级别的类型.<br><br>参考值：<br>-1 - 无；<br>2 - 只读；<br>3 - 读写.| |sysmapid|string|链接所属拓扑图的ID.|

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 shapes  Create a map with map name title.  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Host map",         "width": 600,         "height": 600,         "shapes": [             {                 "type": 0,                 "x": 0,                 "y": 0,                 "width": 600,                 "height": 11,                 "text": "{MAP.NAME}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "10"         ]     },     "id": 1 } ```
zh-cn	#### 拓扑图形状  创建一个带有主题的拓扑图  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Host map",         "width": 600,         "height": 600,         "shapes": [             {                 "type": 0,                 "x": 0,                 "y": 0,                 "width": 600,                 "height": 11,                 "text": "{MAP.NAME}"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "10"         ]     },     "id": 1 } ```

en-us	### Map shapes  The map shape object defines a geometric shape (with or without text) displayed on a map. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmap\_shapeid|string|*(readonly)* ID of the map shape element.| |**type** (required)|integer|Type of map shape element.<br><br>Possible values:<br>0 - rectangle;<br>1 - ellipse.<br><br>Property is required when new shapes are created.| |x|integer|X-coordinates of the shape in pixels.<br><br>Default: 0.| |y|integer|Y-coordinates of the shape in pixels.<br><br>Default: 0.| |width|integer|Width of the shape in pixels.<br><br>Default: 200.| |height|integer|Height of the shape in pixels.<br><br>Default: 200.| |text|string|Text of the shape.| |font|integer|Font of the text within shape.<br><br>Possible values:<br>0 - Georgia, serif<br>1 - “Palatino Linotype”, “Book Antiqua”, Palatino, serif<br>2 - “Times New Roman”, Times, serif<br>3 - Arial, Helvetica, sans-serif<br>4 - “Arial Black”, Gadget, sans-serif<br>5 - “Comic Sans MS”, cursive, sans-serif<br>6 - Impact, Charcoal, sans-serif<br>7 - “Lucida Sans Unicode”, “Lucida Grande”, sans-serif<br>8 - Tahoma, Geneva, sans-serif<br>9 - “Trebuchet MS”, Helvetica, sans-serif<br>10 - Verdana, Geneva, sans-serif<br>11 - “Courier New”, Courier, monospace<br>12 - “Lucida Console”, Monaco, monospace<br><br>Default: 9.| |font\_size|integer|Font size in pixels.<br><br>Default: 11.| |font\_color|string|Font color.<br><br>Default: '000000'.| |text\_halign|integer|Horizontal alignment of text.<br><br>Possible values:<br>0 - center;<br>1 - left;<br>2 - right.<br><br>Default: 0.| |text\_valign|integer|Vertical alignment of text.<br><br>Possible values:<br>0 - middle;<br>1 - top;<br>2 - bottom.<br><br>Default: 0.| |border\_type|integer|Type of the border.<br><br>Possible values:<br>0 - none;<br>1 - `—————`;<br>2 - `·····`;<br>3 - `- - -`.<br><br>Default: 0.| |border\_width|integer|Width of the border in pixels.<br><br>Default: 0.| |border\_color|string|Border color.<br><br>Default: '000000'.| |background\_color|string|Background color (fill color).<br><br>Default: `(empty)`.| |zindex|integer|Value used to order all shapes and lines (z-index).<br><br>Default: 0.|
zh-cn	### 拓扑图形状  拓扑图形状对象定义了在拓扑图上显示的几何形状（有或没有文本）， 它具有以下属性  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |sysmap\_shapeid|string|*(只读)* 拓扑图形状元素的 ID.| |**type**（必填）|integer|拓扑图形状元素的类型.<br><br>参考值：<br>0 - 矩形；<br>1 - 椭圆.<br><br>需要属性创建新形状时.| |x|integer|以像素为单位的形状的 X 坐标.<br><br>默认值：0.| |y|integer|以像素为单位的形状的 Y 坐标.<br><br>默认值：0.| |width|integer|形状的宽度，以像素为单位.<br><br>默认值：200.| |height|integer|形状的高度，以像素为单位.<br><br>默认值：200.| |text|string|形状的文本.| |font|integer|形状内文本的字体.<br><br>参考值:<br>0 - Georgia, serif<br>1 - “Palatino Linotype”, “Book Antiqua”, Palatino, serif<br>2 - “Times New Roman”, Times, serif<br>3 - Arial, Helvetica, sans-serif<br>4 - “Arial Black”, Gadget, sans-serif<br>5 - “Comic Sans MS”, cursive, sans-serif<br>6 - Impact, Charcoal, sans-serif<br>7 - “Lucida Sans Unicode”, “Lucida Grande”, sans-serif<br>8 - Tahoma, Geneva, sans-serif<br>9 - “Trebuchet MS”, Helvetica, sans-serif<br>10 - Verdana, Geneva, sans-serif<br>11 - “Courier New”, Courier, monospace<br>12 - “Lucida Console”, Monaco, monospace<br><br>Default: 9.| |font\_size|integer|字体大小，以像素为单位.<br><br>默认值：11.| |font\_color|string|字体颜色.<br><br>默认值：'000000'.| |text\_halign|integer|文本的水平对齐方式.<br><br>参考值：<br>0 - 居中；<br>1 - 左；<br>2 - 右.<br><br>默认值： 0.| |text\_valign|integer|文本的垂直对齐方式.<br><br>参考值：<br>0 - 中间；<br>1 - 顶部；<br>2 - 底部.<br><br>默认值： 0.| |border\_type|integer|边框的类型.<br><br>参考值：<br>0 - 无；<br>1 - `————`;<br>2 - `··· ··`;<br>3 - `- - -`.<br><br>默认值：0.| |border\_width|integer|以像素为单位的边框宽度.<br><br>默认值：0.| |border\_color|string|边框颜色.<br><br>默认值：'000000'.| |background\_color|string|背景颜色（填充颜色）.<br><br>默认值：`（空）`.| |zindex|integer|用于对所有形状和线条进行排序的值 (z-index).<br><br>默认值：0.|

en-us	#### Map sharing  Create a map with two types of sharing (user and user group).  Request:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map sharing",         "width": 600,         "height": 600,         "users": [             {                 "userid": "4",                 "permission": "3"             }         ],         "userGroups": [             {                 "usrgrpid": "7",                 "permission": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "9"         ]     },     "id": 1 } ```
zh-cn	#### 拓扑图分享  创建具有两种共享类型（用户和用户组）的拓扑图。  请求:  ```json {     "jsonrpc": "2.0",     "method": "map.create",     "params": {         "name": "Map sharing",         "width": 600,         "height": 600,         "users": [             {                 "userid": "4",                 "permission": "3"             }         ],         "userGroups": [             {                 "usrgrpid": "7",                 "permission": "2"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "sysmapids": [             "10"         ]     },     "id": 1 } ```

en-us	### Map  The map object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapid|string|*(readonly)* ID of the map.| |**height**<br>(required)|integer|Height of the map in pixels.| |**name**<br>(required)|string|Name of the map.| |**width**<br>(required)|integer|Width of the map in pixels.| |backgroundid|string|ID of the image used as the background for the map.| |expand\_macros|integer|Whether to expand macros in labels when configuring the map.<br><br>Possible values:<br>0 - *(default)* do not expand macros;<br>1 - expand macros.| |expandproblem|integer|Whether the problem trigger will be displayed for elements with a single problem.<br><br>Possible values:<br>0 - always display the number of problems;<br>1 - *(default)* display the problem trigger if there's only one problem.| |grid\_align|integer|Whether to enable grid aligning.<br><br>Possible values:<br>0 - disable grid aligning;<br>1 - *(default)* enable grid aligning.| |grid\_show|integer|Whether to show the grid on the map.<br><br>Possible values:<br>0 - do not show the grid;<br>1 - *(default)* show the grid.| |grid\_size|integer|Size of the map grid in pixels.<br><br>Supported values: 20, 40, 50, 75 and 100.<br><br>Default: 50.| |highlight|integer|Whether icon highlighting is enabled.<br><br>Possible values:<br>0 - highlighting disabled;<br>1 - *(default)* highlighting enabled.| |iconmapid|string|ID of the icon map used on the map.| |label\_format|integer|Whether to enable advanced labels.<br><br>Possible values:<br>0 - *(default)* disable advanced labels;<br>1 - enable advanced labels.| |label\_location|integer|Location of the map element label.<br><br>Possible values:<br>0 - *(default)* bottom;<br>1 - left;<br>2 - right;<br>3 - top.| |label\_string\_host|string|Custom label for host elements.<br><br>Required for maps with custom host label type.| |label\_string\_hostgroup|string|Custom label for host group elements.<br><br>Required for maps with custom host group label type.| |label\_string\_image|string|Custom label for image elements.<br><br>Required for maps with custom image label type.| |label\_string\_map|string|Custom label for map elements.<br><br>Required for maps with custom map label type.| |label\_string\_trigger|string|Custom label for trigger elements.<br><br>Required for maps with custom trigger label type.| |label\_type|integer|Map element label type.<br><br>Possible values:<br>0 - label;<br>1 - IP address;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing.| |label\_type\_host|integer|Label type for host elements.<br><br>Possible values:<br>0 - label;<br>1 - IP address;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_hostgroup|integer|Label type for host group elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_image|integer|Label type for host group elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>4 - nothing;<br>5 - custom.| |label\_type\_map|integer|Label type for map elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |label\_type\_trigger|integer|Label type for trigger elements.<br><br>Possible values:<br>0 - label;<br>2 - *(default)* element name;<br>3 - status only;<br>4 - nothing;<br>5 - custom.| |markelements|integer|Whether to highlight map elements that have recently changed their status.<br><br>Possible values:<br>0 - *(default)* do not highlight elements;<br>1 - highlight elements.| |severity\_min|integer|Minimum severity of the triggers that will be displayed on the map.<br><br>Refer to the [trigger "severity" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.| |show\_unack|integer|How problems should be displayed.<br><br>Possible values:<br>0 - *(default)* display the count of all problems;<br>1 - display only the count of unacknowledged problems;<br>2 - display the count of acknowledged and unacknowledged problems separately.| |userid|string|Map owner user ID.| |private|integer|Type of map sharing.<br><br>Possible values:<br>0 - public map;<br>1 - *(default)* private map.| |show\_suppressed|integer|Whether suppressed problems are shown.<br><br>Possible values:<br>0 - *(default)* hide suppressed problems;<br>1 - show suppressed problems.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 拓扑图 拓扑图对象具有以下属性.  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |sysmapid|string|*(只读)* 拓扑图 ID.| |**height**<br>（必需）|整数|拓扑图的高度，以像素为单位.| |**name**<br>（必填）|字符串|拓扑图名称.| |**width**<br>（必需）|整数|拓扑图的宽度，以像素为单位.| |backgroundid|字符串|用作拓扑图背景的图像ID.| |expand\_macros|整数|配置拓扑图时是否在标签中展开宏.<br><br>参考值:<br>0 - *（默认）*不展开宏；<br>1 - 展开宏. | |expandproblem|整数|是否为具有单个问题的元素显示问题触发器.<br><br>参考值：<br>0 - 始终显示问题的数量；<br>1 - *（默认） * 如果只有一个问题，则显示问题触发器.| |grid\_align|整数|是否启用网格对齐.<br><br>参考值：<br>0 - 禁用网格对齐；<br>1 - *（默认）* 启用网格对齐.| |grid\_show|整数|是否在拓扑图上显示网格.<br><br>参考值：<br>0 - 不显示网格；<br>1 - *（默认）* 显示网格. | |grid\_size|整数|拓扑图网格的大小（以像素为单位）.<br><br>支持的值：20、40、50、75 和 100.<br><br>默认值：50.| |highlight|整数|是否启用图标突出显示.<br><br>参考值：<br>0 - 突出显示禁用；<br>1 - *（默认）* 突出显示启用.| |iconmapid|字符串|拓扑图上使用的图标拓扑图的ID.| |label\_format|整数|是否启用高级标签.<br><br>参考值：<br>0 - *（默认）* 禁用高级标签；<br>1 - 启用高级标签.| |label\_location|整数|拓扑图元素标签的位置.<br><br>参考值：<br>0 - *（默认）* 底部；<br>1 - 左；<br>2 - 右；< br>3 - 顶部.| |label\_string\_host|字符串|主机元素的自定义标签.<br><br>对于具有自定义主机标签类型的拓扑图是必需的.| |label\_string\_hostgroup|字符串|主机组元素的自定义标签.<br><br>对于具有自定义主机组标签类型的拓扑图是必需的.| |label\_string\_image|字符串|图像元素的自定义标签.<br><br>对于具有自定义图像标签类型的拓扑图是必需的.| |label\_string\_map|字符串|拓扑图元素的自定义标签.<br><br>对于具有自定义拓扑图标签类型的拓扑图是必需的.| |label\_string\_trigger|字符串|触发器元素的自定义标签.<br><br>对于具有自定义触发器标签类型的拓扑图是必需的.| |label\_type|整数|映射元素标签类型.<br><br>参考值：<br>0 - 标签；<br>1 - IP 地址；<br>2 - *（默认）* 元素名称；< br>3 - 仅状态；<br>4 - 无.| |label\_type\_host|整数|主机元素的标签类型.<br><br>参考值：<br>0 - 标签；<br>1 - IP 地址；<br>2 - *（默认）* 元素名称；<br>3 - 仅状态；<br>4 - 无；<br>5 - 自定义.| |label\_type\_hostgroup|整数|主机组元素的标签类型.<br><br>参考值：<br>0 - 标签；<br>2 - *（默认）* 元素名称；<br>3 -仅状态；<br>4 - 无；<br>5 - 自定义.| |label\_type\_image|整数|主机组元素的标签类型.<br><br>参考值：<br>0 - 标签；<br>2 - *（默认）* 元素名称；<br>4 -什么都没有；<br>5 - 自定义.| |label\_type\_map|整数|拓扑图元素的标签类型.<br><br>参考值：<br>0 - 标签；<br>2 - *（默认）*元素名称；<br>3 - 状态仅；<br>4 - 无；<br>5 - 自定义.| |label\_type\_trigger|整数|触发器元素的标签类型.<br><br>参考值：<br>0 - 标签；<br>2 - *（默认）*元素名称；<br>3 - 状态仅；<br>4 - 无；<br>5 - 自定义.| |markelements|整数|是否突出显示最近更改状态的拓扑图元素.<br><br>参考值：<br>0 - *（默认）* 不突出显示元素；<br>1 - 突出显示元素.| |severity\_min|整数|将在拓扑图上显示的触发器的最小严重性.<br><br>请参阅[触发器“严重性”属性](/manual/api/reference/trigger/object#trigger)获取支持的触发器严重性列表.| |show\_unack|整数|应该如何显示问题.<br><br>参考值：<br>0 - *（默认）* 显示所有问题的计数；<br>1 - 仅显示未确认的计数问题；<br>2 - 分别显示已确认和未确认问题的计数.| |userid|string|映射所有者用户 ID.| |private|integer|拓扑图共享的类型.<br><br>参考值：<br>0 - 公共拓扑图；<br>1 - *（默认）* 私人拓扑图.| |show\_suppressed|整数|是否显示抑制的问题.<br><br>参考值：<br>0 - *（默认）* 隐藏抑制的问题；<br>1 - 显示抑制的问题.| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

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	### Map URL  The map URL object defines a clickable link that will be available for all elements of a specific type on the map. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapurlid|string|*(readonly)* ID of the map URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |elementtype|integer|Type of map element for which the URL will be available.<br><br>Refer to the [map element "type" property](object#map_element) for a list of supported types.<br><br>Default: 0.| |sysmapid|string|ID of the map that the URL belongs to.|
zh-cn	### 拓扑图URL  拓扑图URL对象定义了一个可点击的链接,可用于映射上特定类型的所有元素.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapurlid|string|*(只读)* 拓扑图URL ID| |**name**<br>(required)|string |链接标题. | |**url**<br>(required)|string |链接URL | |elementtype      |integer      |可以使用在URL上的拓扑图元素类型.<br><br>请参考 [拓扑图元素"类型"属性](object#map_element)  拓扑图元素可用URL类型<br><br>默认：0| |sysmapid|string|所属URL的拓扑图ID|

en-us	### Map URL  The map URL object defines a clickable link that will be available for all elements of a specific type on the map. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |sysmapurlid|string|*(readonly)* ID of the map URL.| |**name**<br>(required)|string|Link caption.| |**url**<br>(required)|string|Link URL.| |elementtype|integer|Type of map element for which the URL will be available.<br><br>Refer to the [map element "type" property](object#map_element) for a list of supported types.<br><br>Default: 0.| |sysmapid|string|ID of the map that the URL belongs to.|
zh-cn	### 拓扑图URL  拓扑图URL对象定义了一个可点击的链接,可用于映射上特定类型的所有元素.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapurlid|string|*(只读)* 拓扑图URL ID| |**name**<br>(required)|string |链接标题. | |**url**<br>(required)|string |链接URL | |elementtype      |integer      |可以使用在URL上的拓扑图元素类型.<br><br>请参考 [拓扑图元素"类型"属性](object#map_element)  拓扑图元素可用URL类型<br><br>默认：0| |sysmapid|string|所属URL的拓扑图ID|

en-us	### Map user group  List of map permissions based on user groups. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapusrgrpid|string|*(readonly)* ID of the map user group.| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 拓扑图用户组  基于用户组的拓扑图权限列表.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapusrgrpid|string|*(只读)* 拓扑图用户组的ID| |**usrgrpid**<br>(必须)|string |用户组 ID. | |**permission**<br>(必须)    |integer     |权限等级类型<br>  参考值： <br> 2 - 只读 <br> 3 - 可读可写|

en-us	### Map user group  List of map permissions based on user groups. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |sysmapusrgrpid|string|*(readonly)* ID of the map user group.| |**usrgrpid**<br>(required)|string|User group ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 拓扑图用户组  基于用户组的拓扑图权限列表.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapusrgrpid|string|*(只读)* 拓扑图用户组的ID| |**usrgrpid**<br>(必须)|string |用户组 ID. | |**permission**<br>(必须)    |integer     |权限等级类型<br>  参考值： <br> 2 - 只读 <br> 3 - 可读可写|

en-us	### Map user  List of map permissions based on users. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |sysmapuserid|string|*(readonly)* ID of the map user.| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 拓扑图用户  基于用户的拓扑图权限列表.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapuserid|string|*(只读)* 拓扑图用户ID| |**userid**<br>(必须)|string |用户 ID. | |**permission**<br>(必须)    |integer     |权限等级类型<br>  参考值： <br> 2 - 只读 <br> 3 - 可读可写|

en-us	### Map user  List of map permissions based on users. It has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |sysmapuserid|string|*(readonly)* ID of the map user.| |**userid**<br>(required)|string|User ID.| |**permission**<br>(required)|integer|Type of permission level.<br><br>Possible values:<br>2 - read only;<br>3 - read-write;|
zh-cn	### 拓扑图用户  基于用户的拓扑图权限列表.它具有以下特性:  |属性|类型|说明| |--------|----|-----------| |sysmapuserid|string|*(只读)* 拓扑图用户ID| |**userid**<br>(必须)|string |用户 ID. | |**permission**<br>(必须)    |integer     |权限等级类型<br>  参考值： <br> 2 - 只读 <br> 3 - 可读可写|

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

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

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

en-us	 #### MariaDB/MySQL 8.0+ without mysqlsh  This upgrade method takes more time and should be used only if an upgrade with *mysqlsh* is not possible.  ##### Table upgrade  * Log in to MySQL console as root (recommended) or any user with FILE privileges.   * Start MySQL with [local_infile](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_local_infile) variable enabled.  * Rename old tables and create new tables by running `history_pk_prepare.sql`:  ``` {.bash} mysql -uzabbix -p<password> zabbix < /usr/share/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  ##### Migration with stopped server  *max_execution_time* must be disabled before migrating data to avoid timeout during migration.  ``` {.sql} SET @@max_execution_time=0;  INSERT IGNORE INTO history SELECT * FROM history_old; INSERT IGNORE INTO history_uint SELECT * FROM history_uint_old; INSERT IGNORE INTO history_str SELECT * FROM history_str_old; INSERT IGNORE INTO history_log SELECT * FROM history_log_old; INSERT IGNORE INTO history_text SELECT * FROM history_text_old; ```  Follow [post-migration instructions](#after-migration) to drop the old tables.  ##### Migration with running server  Check for which paths import/export is enabled:  ``` {.sql} mysql> SELECT @@secure_file_priv; +-----------------------+ | @@secure_file_priv    | +-----------------------+ | /var/lib/mysql-files/ | +-----------------------+ ```  If *secure_file_priv* value is a path to a directory, export/import will be performed for  files in that directory. In this case, edit paths to files in queries accordingly or set the *secure_file_priv* value to an empty string for the upgrade time.   If *secure_file_priv* value is empty, export/import  can be performed from any location.    If *secure_file_priv* value is NULL, set it to the path that contains exported table data ('/var/lib/mysql-files/' in the example above).   For more information, see  [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv).   *max_execution_time* must be disabled before exporting data to avoid timeout during export.  ``` {.sql} SET @@max_execution_time=0;  SELECT * INTO OUTFILE '/var/lib/mysql-files/history.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_old; LOAD DATA INFILE '/var/lib/mysql-files/history.csv' IGNORE INTO TABLE history FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_uint.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_uint_old; LOAD DATA INFILE '/var/lib/mysql-files/history_uint.csv' IGNORE INTO TABLE history_uint FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_str.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_str_old; LOAD DATA INFILE '/var/lib/mysql-files/history_str.csv' IGNORE INTO TABLE history_str FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_log.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_log_old; LOAD DATA INFILE '/var/lib/mysql-files/history_log.csv' IGNORE INTO TABLE history_log FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_text.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_text_old; LOAD DATA INFILE '/var/lib/mysql-files/history_text.csv' IGNORE INTO TABLE history_text FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n'; ```  Follow [post-migration instructions](#after-migration) to drop the old tables.
zh-cn	#### 没有 mysqlsh 的 MariaDB/MySQL 8.0+  这种升级方法需要更多时间，只有在无法使用 *mysqlsh* 进行升级时才应使用。  ##### 表升级  * 以 root（推荐）或任何具有 FILE 权限的用户身份登录 MySQL 控制台。  * 启用 [local_infile](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_local_infile) 变量启动 MySQL。  * 通过运行 `history_pk_prepare.sql` 重命名旧表并创建新表：  ``` {.bash} mysql -uzabbix -p<password> zabbix < /usr/share/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  ##### 停止服务器的迁移  *max_execution_time* 必须在迁移数据之前禁用以避免迁移期间超时。  ``` {.sql} SET @@max_execution_time=0;  INSERT IGNORE INTO history SELECT * FROM history_old; INSERT IGNORE INTO history_uint SELECT * FROM history_uint_old; INSERT IGNORE INTO history_str SELECT * FROM history_str_old; INSERT IGNORE INTO history_log SELECT * FROM history_log_old; INSERT IGNORE INTO history_text SELECT * FROM history_text_old; ```  Follow [post-migration instructions](#after-migration) to drop the old tables.  ##### Migration with running server  Check for which paths import/export is enabled:  ``` {.sql} mysql> SELECT @@secure_file_priv; +-----------------------+ | @@secure_file_priv · | +-----------------------+ | /var/lib/mysql-files/ | +-----------------------+ ```  如果 *secure_file_priv* 值是目录路径，则将对该目录中的文件执行导出/导入。 在这种情况下，相应地编辑查询中文件的路径或将*secure_file_priv* 值设置为升级时间的空字符串。  如果 *secure_file_priv* 值为空，则可以从任何位置执行导出/导入。  如果 *secure_file_priv* 值为 NULL，将其设置为包含导出表数据的路径（上例中的“/var/lib/mysql-files/”）。  有关详细信息，请参阅 [MySQL 文档](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv)。  *max_execution_time* 必须在导出数据之前禁用以避免导出期间超时。  ``` {.sql} SET @@max_execution_time=0;  SELECT * INTO OUTFILE '/var/lib/mysql-files/history.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_old; LOAD DATA INFILE '/var/lib/mysql-files/history.csv' IGNORE INTO TABLE history FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_uint.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_uint_old; LOAD DATA INFILE '/var/lib/mysql-files/history_uint.csv' IGNORE INTO TABLE history_uint FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_str.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_str_old; LOAD DATA INFILE '/var/lib/mysql-files/history_str.csv' IGNORE INTO TABLE history_str FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_log.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_log_old; LOAD DATA INFILE '/var/lib/mysql-files/history_log.csv' IGNORE INTO TABLE history_log FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_text.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_text_old; LOAD DATA INFILE '/var/lib/mysql-files/history_text.csv' IGNORE INTO TABLE history_text FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n'; ```  按照 [迁移后说明](#after-migration) 删除旧表。

en-us	##### Mass editing options  A button below the list offers one mass-editing option:  -   *Delete* - delete the maintenance periods  To use this option, mark the checkboxes before the respective maintenance periods and click on *Delete*.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一个批量编辑选项:  - · *删除* - 删除维护期  若要使用此选项，请在相应的维护期之前标记复选框，并单击*删除*。

en-us	##### Mass editing options  A button below the list offers one mass-editing option:  -   *Delete* - delete the scripts  To use this option, mark the checkboxes before the respective scripts and click on *Delete*.
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	##### 批量编辑选项  列表下方的按钮提供了批量编辑的选项：  -   *创建时启用* - 创建这些主机为 *启用* -   *创建时禁用* - 创建这些主机为 *禁用* -   *删除* - 删除主机原型  要使用这些选项，请在相应的主机原型之前勾选复选框，然后单击所需按钮。

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 items as *Enabled* -   *Create disabled* - create these items as *Disabled* -   *Mass update* - mass update these item prototypes -   *Delete* - delete these item prototypes  To use these options, mark the checkboxes before the respective item prototypes, 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 items as *Enabled* -   *Create disabled* - create these items as *Disabled* -   *Mass update* - mass update these item prototypes -   *Delete* - delete these item prototypes  To use these options, mark the checkboxes before the respective item prototypes, then click on the required button.
zh-cn	##### 批量编辑选项  列表下的按钮提供了一批量编辑选择：  -   *Create enabled* - 将监控项创建为 *Enabled* -   *Create disabled* - 将监控项创建为*Disabled* -   *Mass update* - 批量更新监控项原型 -   *Delete* - 删除监控项原型  要使用这些选项，在相应的监控项原型之前勾选复选框，然后点击所需的按钮。

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

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Create enabled* - create these triggers as *Enabled* -   *Create disabled* - create these triggers as *Disabled* -   *Mass update* - mass update these trigger prototypes -   *Delete* - delete these trigger prototypes  To use these options, mark the checkboxes before the respective trigger prototypes, then click on the required button.
zh-cn	##### 批量编辑选项 列表之下的按钮提供了一些批量编辑选项：  -   *启用创建* - 创建*启用*状态触发器 -   *禁用创建* - 创建*禁用*状态触发器 -   *批量更新* - 批量更新触发器原型 -   *删除* - 删除触发器原型  要使用这些选项，勾选对应的触发器原型之前的复选框，然后在所需按钮上点击。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Delete* - delete these graph prototypes  To use these options, mark the checkboxes before the respective graph prototypes, then click on the required button.
zh-cn	##### 批量编辑选项  列表下的按钮提供了一些批量编辑的选项：  -   *Delete* - 删除这些图形原型  要使用这些选项，请在相应的图形原型之前标记复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Delete* - delete these graph prototypes  To use these options, mark the checkboxes before the respective graph prototypes, then click on the required button.
zh-cn	##### 批量编辑选项  批量编辑选项列表下面的按钮提供了一些批量编辑的选项：  -   *删除* - 删除这些图形原型。  要使用这些选项，请在相应的图形原型之前标记复选框，然后单击所需按钮。   

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change host status to *Monitored* -   *Disable* - change host status to *Not monitored* -   *Export* - export the hosts to a YAML, XML or JSON file -   *Mass update* - [update several     properties](/manual/config/hosts/hostupdate) for a number of hosts     at once -   *Delete* - delete the hosts  To use these options, mark the checkboxes before the respective hosts, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用* -将主机状态修改为“已监控” -   *禁用* -将主机状态修改为“未监控” -   *导出* -导出主机到YAML, XML或JSON文件 -   *批量更新* - 一次为多个主机[更新多个属性](/manual/config/hosts/hostupdate) -   *删除*—删除主机  要使用这些选项，请在相应主机前勾选复选框， 然后点击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change item status to *Enabled*. -   *Disable* - change item status to *Disabled*. -   *Copy* - copy the items to other hosts or templates. -   *Mass update* - [update several     properties](/manual/config/items/itemupdate) for a number of items     at once. -   *Delete* - delete the items.  To use these options, mark the checkboxes before the respective items, then click on the required button.
zh-cn	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  - *启用* - 把监控项状态设为*启用*。 - *禁用* -把监控项状态设为*禁用*。 - *拷贝* -把监控项拷贝到其他主机或模板中。 - *批量更新* -一次为多个监控项[更新多个属性](/manual/config/items/itemupdate）。 - *删除* -删除监控项。  要使用这些选项，请在相应监控项前勾选复选框， 然后点击所需的按钮。

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 correlation rule status to *Enabled* -   *Disable* - change the correlation rule status to *Disabled* -   *Delete* - delete the correlation rules  To use these options, mark the checkboxes before the respective correlation 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 discovery rule status to *Enabled* -   *Disable* - change the discovery rule status to *Disabled* -   *Delete* - delete the 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 low-level discovery rule status to *Enabled*. -   *Disable* - change the low-level discovery rule status to     *Disabled*. -   *Check now* - perform discovery based on the discovery rules     immediately. See [more details](/manual/config/items/check_now).     Note that when performing discovery immediately, the configuration     cache is not updated, thus the result will not reflect very recent     changes to discovery rule configuration. -   *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	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用* -将主机状态修改为“已监控” -   *禁用* -将主机状态修改为“未监控” -   *现在检查* -立即执行检查新项目的值。仅支持**被动**检查(请参阅[更多细节](/manual/config/items/check_now))。请注意，当立即检查值时，配置缓存不会更新，因此这些值不会反映监控项配置的最新的更改。 -   *删除*—删除监控项  要使用这些选项，请在各自的发现规则之前标记复选框，然后单击所需的按钮。

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	##### 批量编辑选项  下面的按钮提供了一些批量编辑选项:  -   *启用* -将主机状态修改为“已监控” -   *禁用* -将主机状态修改为“未监控” -   *复制* -将触发器复制到其他主机或模板。 -   *批量更新* - 一次为多个主机[更新多个属性](/manual/config/hosts/hostupdate) -   *删除*—删除主机  要使用这些选项，请在相应主机前勾选复选框，然后点击所需的按钮。

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	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable hosts* - change the status of hosts monitored by the proxy     to *Monitored* -   *Disable hosts* - change the status of hosts monitored by the proxy     to *Not monitored* -   *Delete* - delete the proxies  To use these options, mark the checkboxes before the respective proxies, then click on the required button.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一些批量编辑选项：  - *启用主机* - 将proxy监控的主机状态更改为*已监控* -  *禁用主机* - 将proxy监控的主机状态更改为*未监控* -  *Delete* - 删除proxy  要使用这些选项，请在相应proxy之前标记复选框，然后单击所需按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Export* - export the template to a YAML, XML or JSON file -   *Mass update* - [update several     properties](/manual/config/templates/mass) for a number of templates     at once -   *Delete* - delete the template while leaving its linked entities     (items, triggers etc.) with the hosts -   *Delete and clear* - delete the template and its linked entities     from the hosts  To use these options, mark the checkboxes before the respective templates, then click on the required button.
zh-cn	##### 批量编辑选项  列表下方的按钮提供了一些批量编辑选项：  -   *导出* - 将模板导出成YAML，XML，或者JSON 文件 -   *批量更新* -一次为多个模板 [更新多个属性](/manual/config/templates/mass)  -   *删除* - 删除模板，模板与主机链接的实体（监控项，触发器等）不变 -   *删除时并清理* - 删除模板及其与主机链接的实体  要使用这些选项，请在勾上相应模板前的复选框，然后单击所需的按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Mass update* - update the selected problems by navigating to the     [problem update](/manual/acknowledges#updating_problems) screen  To use this option, mark the checkboxes before the respective problems, then click on the *Mass update* button.
zh-cn	##### 批量编辑选项  下面的按钮提供了批量编辑选项：   - · *批量更新* - 通过导航到 · [problem update](/manual/acknowledges#updating_problems) 页面来更新选择的问题。        要使用此选项，请选中相应问题之前的复选框，然后单击 *批量更新*按钮。

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Unblock* - re-enable system access to blocked users -   *Delete* - delete the users  To use these options, mark the check-boxes before the respective users, 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	##### Master item  Create a Zabbix agent item using the following key:      vfs.fs.get  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_item.png)  Set the type of information to "Text" for possibly big JSON data.  The data returned by this item will contain something like the following for a mounted filesystem:  ``` {.java} {   "fsname": "/",   "fstype": "rootfs",   "bytes": {     "total": 1000,     "free": 500,     "used": 500,     "pfree": 50.00,     "pused": 50.00   },   "inodes": {     "total": 1000,     "free": 500,     "used": 500,     "pfree": 50.00,     "pused": 50.00   } } ```
zh-cn	##### 主监控项  使用下面的键创建Zabbix agent监控项:      vfs.fs.get  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_item.png)  设置信息类型为 "Text"，为了识别大块JSON数据。  用于已挂载文件系统的监控项返回的数据会包含类似下面的信息:  ``` {.java} {   "fsname": "/",   "fstype": "rootfs",   "bytes": {     "total": 1000,     "free": 500,     "used": 500,     "pfree": 50.00,     "pused": 50.00   },   "inodes": {     "total": 1000,     "free": 500,     "used": 500,     "pfree": 50.00,     "pused": 50.00   } } ```

en-us	### Media  The media object has the following properties.  |Property|Type|Description| |--------|----|-----------| |**mediatypeid**<br>(required)|string|ID of the media type used by the media.| |**sendto**<br>(required)|string/array|Address, user name or other identifier of the recipient.<br><br>If type of [Media type](/manual/api/reference/mediatype/object#mediatype) is e-mail, values are represented as array. For other types of [Media types](/manual/api/reference/mediatype/object#mediatype), value is represented as a string.| |**active**|integer|Whether the media is enabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |**severity**|integer|Trigger severities to send notifications about.<br><br>Severities are stored in binary form with each bit representing the corresponding severity. For example, 12 equals 1100 in binary and means, that notifications will be sent from triggers with severities warning and average.<br><br>Refer to the [trigger object page](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.<br><br>Default: 63| |**period**|string|Time when the notifications can be sent as a [time period](/manual/appendix/time_period) or user macros separated by a semicolon.<br><br>Default: 1-7,00:00-24:00|
zh-cn	### 媒介  媒介对象具有如下属性.  |属性|属性类型|描述| |--------|----|-----------| |**mediatypeid**<br>(required)|string|被使用的媒介类型ID.| |**sendto**<br>(required)|string/array|地址, 用户名或者其他接收标识符.<br><br>如果 [媒介类型](/manual/api/reference/mediatype/object#mediatype) 是邮件, 值被定义为数组. 如果 [媒介类型](/manual/api/reference/mediatype/object#mediatype) 是其他类型, 值被定义为字符串.| |**active**|integer|是否启用媒介.<br><br>可用值:<br>0 - *(default)* 启用;<br>1 - 禁用.| |**severity**|integer|触发媒介发送告警的告警级别.<br><br>每一位数字代表一个告警级别，并以二进制形式存储. 例如, 12 相当于二进制的 1100, 它表示告警级别为警告和一般严重的告警将触发告警媒介.<br><br>参阅 [触发器对象](/manual/api/reference/trigger/object#trigger) 查看告警级别列表.<br><br>默认: 63| |**period**|string|时间窗口: 能够发送告警通知的 [时间段](/manual/appendix/time_period) 或者以分号分隔的用户宏.<br><br>默认: 1-7,00:00-24:00|

en-us	#### mediatype  Changes:\ [ZBXNEXT-6755](https://support.zabbix.com/browse/ZBXNEXT-6755) message template object: added support of `conditiontype` value: 4 - *(event created on service status update)*.\
zh-cn	 #### 媒介类型  变更：\ [ZBXNEXT-6755](https://support.zabbix.com/browse/ZBXNEXT-6755) 消息模板对象：添加对`conditiontype`值为`4`（服务状态更新时创建的事件）的支持。\

en-us	#### mediatype  Changes:\ [ZBXNEXT-6755](https://support.zabbix.com/browse/ZBXNEXT-6755) message template object: added support of `conditiontype` value `4` (event created on service status update).\
zh-cn	 #### 媒介类型  变更：\ [ZBXNEXT-6755](https://support.zabbix.com/browse/ZBXNEXT-6755) 消息模板对象：添加对`conditiontype`值为`4`（服务状态更新时创建的事件）的支持。\

en-us	#### mediatype  Changes:\ [ZBXNEXT-6885](https://support.zabbix.com/browse/ZBXNEXT-6885) `mediatype.create`, `mediatype.update`: added strict validation of the methods parameters.\
zh-cn	 #### 媒介类型  变更：\ [ZBXNEXT-6885](https://support.zabbix.com/browse/ZBXNEXT-6885) `mediatype.create`，`mediatype.update`：添加了对方法参数的严格校验。\

en-us	#### mediatype  Changes:\ [ZBXNEXT-6885](https://support.zabbix.com/browse/ZBXNEXT-6885) `mediatype.create`, `mediatype.update`: added strict validation of the methods parameters.\
zh-cn	 #### 媒介类型  变更：\ [ZBXNEXT-6885](https://support.zabbix.com/browse/ZBXNEXT-6885) `mediatype.create`，`mediatype.update`：添加了对方法参数的严格校验。\

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  The media type object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |mediatypeid|string|*(readonly)* ID of the media type.| |**name**<br>(required)|string|Name of the media type.| |**type**<br>(required)|integer|Transport used by the media type.<br><br>Possible values:<br>0 - email;<br>1 - script;<br>2 - SMS;<br>4 - Webhook.| |exec\_path|string|For script media types `exec_path` contains the name of the executed script.<br><br>Required for script media types.| |gsm\_modem|string|Serial device name of the GSM modem.<br><br>Required for SMS media types.| |passwd|string|Authentication password.<br><br>Used for email media types.| |smtp\_email|string|Email address from which notifications will be sent.<br><br>Required for email media types.| |smtp\_helo|string|SMTP HELO.<br><br>Required for email media types.| |smtp\_server|string|SMTP server.<br><br>Required for email media types.| |smtp\_port|integer|SMTP server port to connect to.| |smtp\_security|integer|SMTP connection security level to use.<br><br>Possible values:<br>0 - None;<br>1 - STARTTLS;<br>2 - SSL/TLS.| |smtp\_verify\_host|integer|SSL verify host for SMTP.<br><br>Possible values:<br>0 - No;<br>1 - Yes.| |smtp\_verify\_peer|integer|SSL verify peer for SMTP.<br><br>Possible values:<br>0 - No;<br>1 - Yes.| |smtp\_authentication|integer|SMTP authentication method to use.<br><br>Possible values:<br>0 - None;<br>1 - Normal password.| |status|integer|Whether the media type is enabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |username|string|User name.<br><br>Used for email media types.| |exec\_params|string|Script parameters.<br><br>Each parameter ends with a new line feed.| |maxsessions|integer|The maximum number of alerts that can be processed in parallel.<br><br>Possible values for SMS:<br>1 - *(default)*<br><br>Possible values for other media types:<br>0-100| |maxattempts|integer|The maximum number of attempts to send an alert.<br><br>Possible values:<br>1-100<br><br>Default value:<br>3| |attempt\_interval|string|The interval between retry attempts. Accepts seconds and time unit with suffix.<br><br>Possible values:<br>0-1h<br><br>Default value:<br>10s| |content\_type|integer|Message format.<br><br>Possible values:<br>0 - plain text;<br>1 - *(default)* html.| |script|string|Media type webhook script javascript body.| |timeout|string|Media type webhook script timeout. Accepts seconds and time unit with suffix.<br><br>Possible values:<br>1-60s<br><br>Default value:<br>30s| |process\_tags|integer|Defines should the webhook script response to be interpreted as tags and these tags should be added to associated event.<br><br>Possible values:<br>0 - *(default)* Ignore webhook script response.<br>1 - Process webhook script response as tags.| |show\_event\_menu|integer|Show media type entry in `problem.get` and `event.get` property `urls`.<br><br>Possible values:<br>0 - *(default)* Do not add `urls` entry.<br>1 - Add media type to `urls` property.| |event\_menu\_url|string|Define `url` property of media type entry in `urls` property of `problem.get` and `event.get`.| |event\_menu\_name|string|Define `name` property of media type entry in `urls` property of `problem.get` and `event.get`.| |parameters|array|Array of [webhook input parameters](/manual/api/reference/mediatype/object#webhook-parameters).| |description|string|Media type description.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 媒介类型  媒介类型对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |mediatypeid|string|*（只读）* 媒介类型ID。| |**名称**<br>（必需）|string|媒介类型名称。| |**type**<br>（必需）|integer|媒介类型使用的传输方式。<br><br>可用值：<br>0 - 电子邮件；<br>1 - 脚本；<br>2 - SMS；<br>4 - Webhook。| |exec\_path|string|对于脚本媒介类型，`exec_path` 包含执行脚本的名称。<br><br>对于脚本媒介类型是必需的。| |gsm\_modem|string|GSM 调制解调器的串行设备名称。<br><br>对于 SMS 媒介类型是必需的。| |passwd|string|身份验证密码。<br><br>用于电子邮件媒介类型。| |smtp\_email|string|用于发送通知的电子邮件地址。<br><br>电子邮件媒介类型所必需的。| |smtp\_helo|string|SMTP HELO。<br><br>对于电子邮件媒介类型是必需的。| |smtp\_server|string|SMTP 服务器。<br><br>对于电子邮件媒介类型是必需的。| |smtp\_port|integer|要连接的 SMTP 服务器端口。| |smtp\_security|integer|要使用的 SMTP 连接安全级别。<br><br>可用值：<br>0 - 无；<br>1 - STARTTLS；<br>2 - SSL/TLS。| |smtp\_verify\_host|integer|用于 SMTP 的 SSL 验证主机。<br><br>可用值：<br>0 - 否；<br>1 - 是。| |smtp\_verify\_peer|integer|用于 SMTP 的 SSL 验证对等点。<br><br>可用值：<br>0 - 否；<br>1 - 是。| |smtp\_authentication|integer|要使用的 SMTP 身份验证方法。<br><br>可用值：<br>0 - 无；<br>1 - 普通密码。| |status|integer|媒介类型是否启用。<br><br>可用值：<br>0 - *（默认）*启用；<br>1 - 禁用。| |username|string|用户名。<br><br>用于电子邮件媒介类型。| |exec\_params|string|脚本参数。<br><br>每个参数都以新的换行符结尾。| |maxsessions|integer|可以并行处理的最大警报数。<br><br>SMS 的可用值：<br>1 - *（默认）*<br><br>其他媒介类型的可用值：<br>0-100| |maxattempts|integer|尝试发送警报的最大次数。<br><br>可用值：<br>1-100<br><br>默认值：<br>3| |attempt\_interval|string|重试尝试之间的间隔。接受秒和带后缀的时间单位。<br><br可用值：<br>0-1h<br><br>默认值：<br>10s| |content\_type|integer|消息格式。<br><br>可用值：<br>0 - 纯文本；<br>1 - *（默认）* html。| |script|string|媒介类型 webhook 脚本 javascript 正文。| |timeout|string|媒介类型 webhook 脚本超时。接受秒和带后缀的时间单位。<br><br>可用值：<br>1-60s<br><br>默认值：<br>30s| |process\_tags|integer|定义 webhook 脚本响应是否应被解释为标签，并且这些标签应添加到相关事件中。<br><br>可用值：<br>0 - *（默认）* 忽略 webhook 脚本响应.<br>1 - 将 webhook 脚本响应作为标签处理。| |show\_event\_menu|integer|在 `problem.get` 和 `event.get` 属性 `urls` 中显示媒介类型条目。<br><br>可用值：<br>0 - *（默认）* 不添加为 `urls` 条目。<br>1 - 将媒介类型添加到 `urls` 属性。| |event\_menu\_url|string|在 `problem.get` 和 `event.get` 的 `urls` 属性中定义媒介类型条目的 `url` 属性。| |event\_menu\_name|string|在 `problem.get` 和 `event.get` 的 `urls` 属性中定义媒介类型条目的 `name` 属性。| |parameters|array|[webhook 输入参数](/manual/api/reference/mediatype/object#webhook-参数)的数组。| |description|string|媒介类型描述。|  注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

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	 ### Memcached  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |memcached.ping\[connString,<user>,<password>\]|<|<|<| |Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.| | |memcached.stats\[connString,<user>,<password>,<type>\]|<|<|<| |Gets the output of the STATS command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**user, password** - Memcached login credentials.<br>**type** - stat type to be returned: *items*, *sizes*, *slabs* or *settings* (empty by default, returns general statistics).| |
zh-cn	 ### Memchached  |键值|<|<|<| |---|---|---|---| |**描述**|**回值**|**参数**|**注释**| |memcached.ping\[connString,<user>,<password>\]|<|<|<| |测试连接是否存活.|1 - 连接存活<br><br>0 - 连接断开 (如果出现包括认证和配置问题的错误提示)|**connString** - URI 或者 session name.| | |memcached.stats\[connString,<user>,<password>,<type>\]|<|<|<| |获取 Stats 命令的输出.|JSON - 输出序列化为 JSON 格式|**connString** - URI 或者 session name.<br>**user, password** - Memchached 登陆凭证.<br>**type** - 返回的类型: *items*, *sizes*, *slabs* 或者 *settings* (默认为空, 返回常规统计数据).| |

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	##### Memory  Zabbix requires both physical and disk memory. 128 MB of physical memory and 256 MB of free disk space could be a good starting point. However, the amount of required disk memory obviously depends on the number of hosts and parameters that are being monitored. If you're planning to keep a long history of monitored parameters, you should be thinking of at least a couple of gigabytes to have enough space to store the history in the database. Each Zabbix daemon process requires several connections to a database server. The amount of memory allocated for the connection depends on the configuration of the database engine.   ::: noteclassic The more physical memory you have, the faster the database (and therefore Zabbix) works!  :::
zh-cn	##### 内存和磁盘  Zabbix 运行需要物理内存和磁盘空间。如果刚接触 Zabbix，128 MB 的物理内存和 256 MB 的可用磁盘空间可能是一个很好的起点。 然而，所需的内存和磁盘空间显然取决于被监控的主机数量和配置参数。 如果您计划调整参数以保留较长的历史数据，那么您应该考虑至少有几 GB 磁盘空间，以便有足够的磁盘空间将历史数据存储在数据库中。  每个 Zabbix 守护程序进程都需要与数据库服务器建立多个连接。 为连接分配的内存量取决于数据库引擎的配置。  ::: noteclassic 您拥有的物理内存越多，数据库（以及 Zabbix ）的工作速度就越快！ :::

en-us	### Message template  The message template object defines a template that will be used as a default message for action operations to send a notification. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**eventsource**<br>(required)|integer|Event source.<br><br>Possible values:<br>0 - triggers;<br>1 - discovery;<br>2 - autoregistration;<br>3 - internal;<br>4 - services.| |**recovery**<br>(required)|integer|Operation mode.<br><br>Possible values:<br>0 - operations;<br>1 - recovery operations;<br>2 - update operations.| |subject|string|Message subject.| |message|string|Message text.|
zh-cn	### 消息模板  消息模板对象定义了一个模板，该模板将用作动作操作发送通知的默认消息。具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**eventsource**<br>（必需）|integer|事件源。<br><br>可用值：<br>0 - 触发器；<br>1 - 自动发现；<br>2 - 自动注册；<br>3 - 采集器；<br>4 - 服务端。| |**recovery**<br>（必需）|integer|操作模式。<br><br>可用值：<br>0 - 自动操作；<br>1 - 恢复操作；<br>2 - 更新操作。| |subject|string|消息主题。| |message|string|消息文本。|

en-us	### Message template  The message template object defines a template that will be used as a default message for action operations to send a notification. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**eventsource**<br>(required)|integer|Event source.<br><br>Possible values:<br>0 - triggers;<br>1 - discovery;<br>2 - autoregistration;<br>3 - internal;<br>4 - services.| |**recovery**<br>(required)|integer|Operation mode.<br><br>Possible values:<br>0 - operations;<br>1 - recovery operations;<br>2 - update operations.| |subject|string|Message subject.| |message|string|Message text.|
zh-cn	### 消息模板  消息模板对象定义了一个模板，该模板将用作动作操作发送通知的默认消息。具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**eventsource**<br>（必需）|integer|事件源。<br><br>可用值：<br>0 - 触发器；<br>1 - 自动发现；<br>2 - 自动注册；<br>3 - 采集器；<br>4 - 服务端。| |**recovery**<br>（必需）|integer|操作模式。<br><br>可用值：<br>0 - 自动操作；<br>1 - 恢复操作；<br>2 - 更新操作。| |subject|string|消息主题。| |message|string|消息文本。|

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	 #### Migration with running server  * Export current history, import it to the temp table,  then insert the data into new tables while ignoring duplicates:  ``` {.sql} \copy history_old TO '/tmp/history.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history (     itemid                   bigint                                    NOT NULL,     clock                    integer         DEFAULT '0'               NOT NULL,     value                    DOUBLE PRECISION DEFAULT '0.0000'          NOT NULL,     ns                       integer         DEFAULT '0'               NOT NULL ); \copy temp_history FROM '/tmp/history.csv' DELIMITER ',' CSV INSERT INTO history SELECT * FROM temp_history ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_uint_old TO '/tmp/history_uint.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_uint (     itemid                   bigint                                    NOT NULL,     clock                    integer         DEFAULT '0'               NOT NULL,     value                    numeric(20)     DEFAULT '0'               NOT NULL,     ns                       integer         DEFAULT '0'               NOT NULL ); \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_str_old TO '/tmp/history_str.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_str (     itemid                   bigint                                    NOT NULL,     clock                    integer         DEFAULT '0'               NOT NULL,     value                    varchar(255)    DEFAULT ''                NOT NULL,     ns                       integer         DEFAULT '0'               NOT NULL ); \copy temp_history_str FROM '/tmp/history_str.csv' DELIMITER ',' CSV INSERT INTO history_str (itemid,clock,value,ns) SELECT * FROM temp_history_str ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_log_old TO '/tmp/history_log.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_log (     itemid                   bigint                                    NOT NULL,     clock                    integer         DEFAULT '0'               NOT NULL,     timestamp                integer         DEFAULT '0'               NOT NULL,     source                   varchar(64)     DEFAULT ''                NOT NULL,     severity                 integer         DEFAULT '0'               NOT NULL,     value                    text            DEFAULT ''                NOT NULL,     logeventid               integer         DEFAULT '0'               NOT NULL,     ns                       integer         DEFAULT '0'               NOT NULL ); \copy temp_history_log FROM '/tmp/history_log.csv' DELIMITER ',' CSV INSERT INTO history_log SELECT * FROM temp_history_log ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_text_old TO '/tmp/history_text.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_text (     itemid                   bigint                                    NOT NULL,     clock                    integer         DEFAULT '0'               NOT NULL,     value                    text            DEFAULT ''                NOT NULL,     ns                       integer         DEFAULT '0'               NOT NULL ); \copy temp_history_text FROM '/tmp/history_text.csv' DELIMITER ',' CSV INSERT INTO history_text SELECT * FROM temp_history_text ON CONFLICT (itemid,clock,ns) DO NOTHING; ``` * Follow [post-migration instructions](#after-migration) to drop the old tables.
zh-cn	#### 迁移正在运行的服务器  * 导出当前历史，将其导入临时表，然后将数据插入新表，同时忽略重复项：  ``` {.sql} \copy history_old TO '/tmp/history.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history (  · itemid · bigint · NOT NULL,  · clock · integer · DEFAULT '0' · NOT NULL,  · value · DOUBLE PRECISION DEFAULT '0.0000' · NOT NULL,  · ns · integer · DEFAULT '0' · NOT NULL ); \copy temp_history FROM '/tmp/history.csv' DELIMITER ',' CSV INSERT INTO history SELECT * FROM temp_history ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_uint_old TO '/tmp/history_uint.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_uint (  · itemid · bigint · NOT NULL,  · clock · integer · DEFAULT '0' · NOT NULL,  · value · numeric(20) · DEFAULT '0' · NOT NULL,  · ns · integer · DEFAULT '0' · NOT NULL ); \copy temp_history_uint FROM '/tmp/history_uint.csv' DELIMITER ',' CSV INSERT INTO history_uint SELECT * FROM temp_history_uint ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_str_old TO '/tmp/history_str.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_str (  · itemid · bigint · NOT NULL,  · clock · integer · DEFAULT '0' · NOT NULL,  · value · varchar(255) · DEFAULT '' · NOT NULL,  · ns · integer · DEFAULT '0' · NOT NULL ); \copy temp_history_str FROM '/tmp/history_str.csv' DELIMITER ',' CSV INSERT INTO history_str (itemid,clock,value,ns) SELECT * FROM temp_history_str ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_log_old TO '/tmp/history_log.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_log (  · itemid · bigint · NOT NULL,  · clock · integer · DEFAULT '0' · NOT NULL,  · timestamp · integer · DEFAULT '0' · NOT NULL,  · source · varchar(64) · DEFAULT '' · NOT NULL,  · severity · integer · DEFAULT '0' · NOT NULL,  · value · text · DEFAULT '' · NOT NULL,  · logeventid · integer · DEFAULT '0' · NOT NULL,  · ns · integer · DEFAULT '0' · NOT NULL ); \copy temp_history_log FROM '/tmp/history_log.csv' DELIMITER ',' CSV INSERT INTO history_log SELECT * FROM temp_history_log ON CONFLICT (itemid,clock,ns) DO NOTHING;  \copy history_text_old TO '/tmp/history_text.csv' DELIMITER ',' CSV CREATE TEMP TABLE temp_history_text (  · itemid · bigint · NOT NULL,  · clock · integer · DEFAULT '0' · NOT NULL,  · value · text · DEFAULT '' · NOT NULL,  · ns · integer · DEFAULT '0' · NOT NULL ); \copy temp_history_text FROM '/tmp/history_text.csv' DELIMITER ',' CSV INSERT INTO history_text SELECT * FROM temp_history_text ON CONFLICT (itemid,clock,ns) DO NOTHING; ```  * 按照 [post-migration instructions](#after-migration) 删除旧表。

en-us	##### MikroTik  -   *MikroTik CCR1009-7G-1C-1S+ SNMP* - monitoring of MikroTik     CCR1009-7G-1C-1S+ ethernet routers via SNMP; -   *MikroTik CCR1009-7G-1C-1S+PC SNMP* - monitoring of MikroTik     CCR1009-7G-1C-1S+PC ethernet routers via SNMP; -   *MikroTik CCR1009-7G-1C-PC SNMP* - monitoring of MikroTik     CCR1009-7G-1C-PC ethernet routers via SNMP; -   *MikroTik CCR1016-12G SNMP* - monitoring of MikroTik CCR1016-12G     ethernet routers via SNMP; -   *MikroTik CCR1016-12S-1S+ SNMP* - monitoring of MikroTik     CCR1016-12S-1S+ ethernet routers via SNMP; -   *MikroTik CCR1036-12G-4S-EM SNMP* - monitoring of MikroTik     CCR1036-12G-4S-EM ethernet routers via SNMP; -   *MikroTik CCR1036-12G-4S SNMP* - monitoring of MikroTik     CCR1036-12G-4S ethernet routers via SNMP; -   *MikroTik CCR1036-8G-2S+ SNMP* - monitoring of MikroTik     CCR1036-8G-2S+ ethernet routers via SNMP; -   *MikroTik CCR1036-8G-2S+EM SNMP* - monitoring of MikroTik     CCR1036-8G-2S+EM ethernet routers via SNMP; -   *MikroTik CCR1072-1G-8S+ SNMP* - monitoring of MikroTik     CCR1072-1G-8S+ ethernet routers via SNMP; -   *MikroTik CCR2004-16G-2S+ SNMP* - monitoring of MikroTik     CCR2004-16G-2S+ ethernet routers via SNMP; -   *MikroTik CCR2004-1G-12S+2XS SNMP* - monitoring of MikroTik     CCR2004-1G-12S+2XS ethernet routers via SNMP; -   *MikroTik CRS106-1C-5S SNMP* - monitoring of MikroTik CRS106-1C-5S     switches via SNMP; -   *MikroTik CRS109-8G-1S-2HnD-IN SNMP* - monitoring of MikroTik     CRS109-8G-1S-2HnD-IN switches via SNMP; -   *MikroTik CRS112-8G-4S-IN SNMP* - monitoring of MikroTik     CRS112-8G-4S-IN switches via SNMP; -   *MikroTik CRS112-8P-4S-IN SNMP* - monitoring of MikroTik     CRS112-8P-4S-IN switches via SNMP; -   *MikroTik CRS125-24G-1S-2HnD-IN SNMP* - monitoring of MikroTik     CRS125-24G-1S-2HnD-IN switches via SNMP; -   *MikroTik CRS212-1G-10S-1S+IN SNMP* - monitoring of MikroTik     CRS212-1G-10S-1S+IN switches via SNMP; -   *MikroTik CRS305-1G-4S+IN SNMP* - monitoring of MikroTik     CRS305-1G-4S+IN switches via SNMP; -   *MikroTik CRS309-1G-8S+IN SNMP* - monitoring of MikroTik     CRS309-1G-8S+IN switches via SNMP; -   *MikroTik CRS312-4C+8XG-RM SNMP* - monitoring of MikroTik     CRS312-4C+8XG-RM switches via SNMP; -   *MikroTik CRS317-1G-16S+RM SNMP* - monitoring of MikroTik     CRS317-1G-16S+RM switches via SNMP; -   *MikroTik CRS326-24G-2S+IN SNMP* - monitoring of MikroTik     CRS326-24G-2S+IN switches via SNMP; -   *MikroTik CRS326-24G-2S+RM SNMP* - monitoring of MikroTik     CRS326-24G-2S+RM switches via SNMP; -   *MikroTik CRS326-24S+2Q+RM SNMP* - monitoring of MikroTik     CRS326-24S+2Q+RM switches via SNMP; -   *MikroTik CRS328-24P-4S+RM SNMP* - monitoring of MikroTik     CRS328-24P-4S+RM switches via SNMP; -   *MikroTik CRS328-4C-20S-4S+RM SNMP* - monitoring of MikroTik     CRS328-4C-20S-4S+RM switches via SNMP; -   *MikroTik CRS354-48G-4S+2Q+RM SNMP* - monitoring of MikroTik     CRS354-48G-4S+2Q+RM switches via SNMP; -   *MikroTik CRS354-48P-4S+2Q+RM SNMP* - monitoring of MikroTik     CRS354-48P-4S+2Q+RM switches via SNMP; -   *MikroTik CSS326-24G-2S+RM SNMP* - monitoring of MikroTik     CSS326-24G-2S+RM switches via SNMP; -   *MikroTik CSS610-8G-2S+IN SNMP* - monitoring of MikroTik     CSS610-8G-2S+IN switches via SNMP; -   *MikroTik FiberBox SNMP* - monitoring of MikroTik FiberBox switches     via SNMP; -   *MikroTik hEX lite SNMP* - monitoring of MikroTik hEX lite ethernet     routers via SNMP; -   *MikroTik hEX PoE lite SNMP* - monitoring of MikroTik hEX PoE lite     ethernet routers via SNMP; -   *MikroTik hEX PoE SNMP* - monitoring of MikroTik hEX PoE ethernet     routers via SNMP; -   *MikroTik hEX S SNMP* - monitoring of MikroTik hEX S ethernet     routers via SNMP; -   *MikroTik hEX SNMP* - monitoring of MikroTik hEX ethernet routers     via SNMP; -   *MikroTik netPower 15FR SNMP* - monitoring of MikroTik netPower 15FR     switches via SNMP; -   *MikroTik netPower 16P SNMP* - monitoring of MikroTik netPower 16P     switches via SNMP; -   *MikroTik netPower Lite 7R SNMP* - monitoring of MikroTik netPower     Lite 7R switches via SNMP; -   *MikroTik PowerBox Pro SNMP* - monitoring of MikroTik PowerBox Pro     ethernet routers via SNMP; -   *MikroTik PowerBox SNMP* - monitoring of MikroTik PowerBox ethernet     routers via SNMP; -   *MikroTik RB1100AHx4 Dude Edition SNMP* - monitoring of MikroTik     RB1100AHx4 Dude Edition ethernet routers via SNMP; -   *MikroTik RB1100AHx4 SNMP* - monitoring of MikroTik RB1100AHx4     ethernet routers via SNMP; -   *MikroTik RB2011iL-IN SNMP* - monitoring of MikroTik RB2011iL-IN     ethernet routers via SNMP; -   *MikroTik RB2011iL-RM SNMP* - monitoring of MikroTik RB2011iL-RM     ethernet routers via SNMP; -   *MikroTik RB2011iLS-IN SNMP* - monitoring of MikroTik RB2011iLS-IN     ethernet routers via SNMP; -   *MikroTik RB2011UiAS-IN SNMP* - monitoring of MikroTik RB2011UiAS-IN     ethernet routers via SNMP; -   *MikroTik RB2011UiAS-RM SNMP* - monitoring of MikroTik RB2011UiAS-RM     ethernet routers via SNMP; -   *MikroTik RB260GS SNMP* - monitoring of MikroTik RB260GS switches     via SNMP; -   *MikroTik RB3011UiAS-RM SNMP* - monitoring of MikroTik RB3011UiAS-RM     ethernet routers via SNMP; -   *MikroTik RB4011iGS+RM SNMP* - monitoring of MikroTik RB4011iGS+RM     ethernet routers via SNMP; -   *MikroTik RB5009UG+S+IN SNMP* - monitoring of MikroTik RB5009UG+S+IN     ethernet routers via SNMP; -   *Mikrotik SNMP* - a generic template for monitoring MikroTik     devices.  You can get these templates:  -   In *Configuration* → *Templates* in new installations; -   When upgrading from previous versions, the latest templates can be     downloaded from the [Zabbix Git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)     and manually imported into Zabbix in the *Configuration* →     *Templates* section. If a template with the same name already     exists, check the *Delete missing* option before importing to     achieve a clean import. This way the items that have been excluded     from the updated template will be removed (note, that history of the     deleted items will be lost).  
zh-cn	### Frontend  

en-us	##### Mikrotik  -   *MikroTik \<device model> SNMP* - 53 new model-specific templates for monitoring various models of MikroTik     ethernet routers and switches, see [full list](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/mikrotik); -   *Mikrotik SNMP* - a generic template for monitoring MikroTik     devices.
zh-cn	##### Mikrotik  -   *MikroTik \<device model> SNMP* - 53 新型号特定模板，用于监控各种型号的 MikroTik 以太网路由器和交换机，请参阅 [完整列表](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/mikrotik);https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/mikrotik)； -   *Mikrotik SNMP* - 用于监控 MikroTik 设备的通用模板。

en-us	##### Mikrotik routers  Use SNMP agent provided by Mikrotik. See <http://www.mikrotik.com> for more information.
zh-cn	##### Mikrotik 路由器  使用 Mikrotik 提供的 SNMP 代理。有关详细信息，请参阅 <http://www.mikrotik.com> 。

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	##### Miscellaneous  -   The default language of Zabbix web interface has been changed from     British to American English. Support of British English has been     dropped. -   The Share link in the main menu has been replaced by an Integrations     link, leading to the     [Integrations](https://www.zabbix.com/integrations) page on the     Zabbix website. -   If Zabbix web interface is opened in one of the languages available     on the Zabbix website, clicking the Integrations link will open the     Integrations page in the appropriate language. For all other     languages, including English, the Integrations page will be opened     in English. -   A custom expression, used in [action configuration](/manual/config/notifications/action/#configuring-an-action) for calculating conditions, now can be up to 1024 characters long (previously 255). -   *Monitoring->Hosts* section now shows link to host problems screen even if no problems are currently open. 
zh-cn	##### 杂项  -   Zabbix Web 界面的默认语言已从英式英语更改为美式英语。已放弃对英式英语的支持。 -   主菜单中的 Share 链接已被 Integrations 链接取代，指向 Zabbix 网站上的 [Integrations](https://www.zabbix.com/integrations) 页面。 -   如果 Zabbix Web 界面以 Zabbix 网站上可用的语言之一打开，单击集成链接将以适当的语言打开集成页面。对于所有其他语言，包括英语，集成页面将以英语打开。 -   用于计算条件的 [动作配置](/manual/config/notifications/action/#configuring-an-action)  中的自定义表达式现在最多可包含 1024 个字符（之前为 255 个）。 -   *Monitoring->Hosts* 部分现在显示指向主机问题屏幕的链接，即使当前没有打开任何问题。

en-us	#### Mismatch counting  Count the number of hosts whose names do not contain the substring "ubuntu"  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "countOutput": true,         "search": {             "host": "ubuntu"         },         "excludeSearch": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": "44",     "id": 1 } ```
zh-cn	#### 不匹配统计  统计名称中不包含“ubuntu”的主机数量。  请求：  ```json {     "jsonrpc": "2.0",     "method": "host.get",     "params": {         "countOutput": true,         "search": {             "host": "ubuntu"         },         "excludeSearch": true     },     "auth": "766b71ee543230a1182ca5c44d353e36",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": "44",     "id": 1 } ```

en-us	 ##### Modbus data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**modbus.get**\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<| |Reads Modbus data.|JSON object|**endpoint** - endpoint defined as `protocol://connection_string`<br>**slave id** - slave ID<br>**function** - Modbus function<br>**address** - address of first registry, coil or input<br>**count** - number of records to read<br>**type** - type of data<br>**endianness** - endianness configuration<br>**offset** - number of registers, starting from 'address', the results of which will be discarded.<br><br>See a [detailed description](/manual/appendix/items/modbus) of parameters.|Supported since Zabbix 5.2.0.|
zh-cn	##### Modbus 数据  |键值|<|<|<| |--|--|------|------| |描述|返回值|参数|注释| |**modbus.get**\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<| |读取Modbus数据|JSON 对象|**endpoint** - 终端定义为 `protocol://connection_string`<br>**slave id** - 从机 ID<br>**function** - Modbus 函数<br>**address** - 第一个注册地址, 线圈或输入<br>**count** - 读取的记录数量<br>**type** - 数据类型<br>**endianness** - 字节序配置<br>**offset** - 寄存器数, 从 '地址'开始, 其结果将被丢弃。<br><br>参阅参数的[详细描述](/manual/appendix/items/modbus) 。|自 Zabbix 5.2.0后开始支持|

en-us	##### - Modes  (**forecast** only)\ Every time a trigger function is evaluated it gets data from the specified history period and fits a specified function to the data. So, if the data is slightly different the fitted function will be slightly different. If we simply calculate the value of the fitted function at a specified time in the future you will know nothing about how the analyzed item is expected to behave between now and that moment in the future. For some `fit` options (like *polynomial*) a simple value from the future may be misleading.  |`mode`|**forecast** result| |------|-------------------| |*value*|f(now + `time`)| |*max*|max~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*min*|min~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*delta*|*max* - *min*| |*avg*|average of f(t) (now <= t <= now + `time`) according to [definition](https://en.wikipedia.org/wiki/Mean_of_a_function)|
zh-cn	##### 2.5 模式  (仅限**forecast** )\ 每次评估触发函数时，它都会从指定的历史期间获取数据，并将指定的函数拟合到数据中。 因此，如果数据略有不同，拟合函数也会略有不同。如果我们只是简单地计算未来某个特定时间拟合函数的值，那么将一无所获对于分析监控项在现在和未来那个时刻之间的预期行为。对于某些 `fit` 选项 (例如 *polynomial*) 未来的简单值可能会产生误导。  |`模式`|**forecast** 结果| |------|-------------------| |*值*|f(now + `time`)| |*最大值*|max~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*最小值*|min~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*增量*|*max* - *min*| |*平均值*|average of f(t) (now <= t <= now + `time`) 参考[定义](https://en.wikipedia.org/wiki/Mean_of_a_function)|

en-us	 ### Modifying existing services  :::noteclassic The buttons described below are visible only when *Services* section is in the Edit mode. :::  To edit an existing service, press the pencil icon next to the service.   To clone an existing service, press the pencil icon to open its configuration and then press Clone button. When a service is cloned, its parent links are preserved, while the child links are not.  To delete a service, press on the `x` icon next to it. When you delete a parent service, its child services will not be deleted and will move one level higher in the service tree (1st level children will get the same level as the deleted parent service).   Two buttons below the list of services offer some mass-editing options:  -   *Mass update* - mass update service properties -   *Delete* - delete the services  To use these options, mark the checkboxes before the respective services, then click on the required button.
zh-cn	### 修改现有服务  :::noteclassic 以下描述的按钮仅在 *Services* 部分处于编辑模式时可见。 :::  要编辑现有服务，请按服务旁边的铅笔图标。  要克隆现有服务，请按铅笔图标打开其配置，然后按克隆按钮。克隆服务时，会保留其父链接，而不会保留子链接。  要删除服务，请按服务旁边的`x`图标。删除父服务时，其子服务将不会被删除，并将在服务树中向上移动一级（第一级子服务将获得与删除的父服务相同的级别）。  服务列表下方的两个按钮提供了一些批量编辑选项：  -   *Mass update* - 批量更新服务属性 -   *Delete* - 删除服务  要使用这些选项，请在相应服务之前勾选复选框，然后单击所需按钮。

en-us	#### - Module API  In order for a shared library to be treated as a Zabbix module, it should implement and export several functions. There are currently six functions in the Zabbix module API, only one of which is mandatory and the other five are optional.
zh-cn	#### - 模块 API  为了将共享库视作ZABBIX模块，它应该实现并导出一些函数。目前，ZABBIX 模块API 中由六个函数，其中一个是强制性的，另外五个是可选的。\

en-us	#### - Modules  This section allows to administer custom [frontend modules](/manual/modules).  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_modules.png){width="600"}  Click on *Scan directory* to register/unregister any custom modules. Registered modules will appear in the list, along with their details. Unregistered modules will be removed from the list.  You may filter modules by name or status (enabled/disabled). Click on the module status in the list to enable/disable a module. You may also mass enable/disable modules by selecting them in the list and then clicking on the *Enable/Disable* buttons below the list.
zh-cn	#### - 模块  本节允许管理自定义 [前端模块](/manual/modules)。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_modules.png){width="600"}  单击 *Scan directory* 以注册/取消注册任何自定义模块。已注册的模块及其详细信息将显示在列表中。 未注册的模块将从列表中删除。  您可以按名称或状态（启用/禁用）过滤模块。 单击列表中的模块状态以启用/禁用模块。 您还可以通过在列表中选择模块然后单击列表下方的*启用/禁用*按钮来批量启用/禁用模块。

en-us	##### Module structure  Each module is a directory (placed within the `modules` directory) with sub-directories containing controllers, views and any other code:      example_module_directory/           (required)         manifest.json                   (required)  Metadata and action definition.         Module.php                                  Module initialization and event handling.         actions/                                    Action controller files.             SomethingView.php             SomethingCreate.php             SomethingDelete.php             data_export/                                                  ExportAsXml.php                 ExportAsExcel.php         views/                                      View files.             example.something.view.php             example.something.delete.php             js/                                     JavaScript files used in views.                 example.something.view.js.php         partials/                                   View partial files.             example.something.reusable.php             js/                                     JavaScript files used in partials.                 example.something.reusable.js.php  As you can see, the only mandatory file within the custom module directory is `manifest.json`. The module will not register without this file. `Module.php` is responsible for registering menu items and processing events such as 'onBeforeAction' and 'onTerminate'. The *actions*, *views* and *partials* directories contain PHP and JavaScript code needed for module actions.
zh-cn	 ##### 模块结构  每个模块都是一个目录（位于`modules`目录中），其子目录包含控制器，视图和任何其他代码：      example_module_directory/           (必需的)         manifest.json                   (必需的)  元数据和动作定义。         Module.php                                  模块初始化和事件处理。         actions/                                    动作控制器文件。             SomethingView.php             SomethingCreate.php             SomethingDelete.php             data_export/                                                  ExportAsXml.php                 ExportAsExcel.php         views/                                      视图文件。             example.something.view.php             example.something.delete.php             js/                                     视图中使用的JavaScript文件。                 example.something.view.js.php         partials/                                   部分视图文件。             example.something.reusable.php             js/                                     部分视图中使用的JavaScript文件。                 example.something.reusable.js.php  如您所见，自定义模块目录中唯一必需的文件是`manifest.json`。如果没有此文件，模块将无法注册。`Module.php`负责注册菜单项和处理诸如'onBeforeAction'和'onTerminate'之类的事件。*actions*、*views* 和 *partials* 目录包含模块操作所需的 PHP 和 JavaScript 代码。

en-us	### Module  The module object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**moduleid**<br>(required)|string|ID of the module.| |status|integer|Whether access to the module is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	### 模块  模块对象拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**moduleid**<br>(必要)|字符串|模块ID。| |status|整数|是否允许访问模块信息。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *(缺省值)* 开启。|

en-us	### Module  The module object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**moduleid**<br>(required)|string|ID of the module.| |status|integer|Whether access to the module is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	### 模块  模块对象拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**moduleid**<br>(必要)|字符串|模块ID。| |status|整数|是否允许访问模块信息。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *(缺省值)* 开启。|

en-us	 ### MongoDB  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mongodb.collection.stats\[connString,<user>,<password>,<database>,collection\]|<|<|<| |Returns a variety of storage statistics for a given collection.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).<br>**collection** — collection name.| | |mongodb.collections.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered collections. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.collections.usage\[connString,<user>,<password>\]|<|<|<| |Returns usage statistics for collections.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.connpool.stats\[connString,<user>,<password>\]|<|<|<| |Returns information regarding the open outgoing connections from the current database instance to other members of the sharded cluster or replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.db.stats\[connString,<user>,<password>,<database>\]|<|<|<| |Returns statistics reflecting a given database system state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).| | |mongodb.db.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.jumbo\_chunks.count\[connString,<user>,<password>\]|<|<|<| |Returns count of jumbo chunks.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.oplog.stats\[connString,<user>,<password>\]|<|<|<| |Returns a status of the replica set, using data polled from the oplog.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.ping\[connString,<user>,<password>\]|<|<|<| |Tests if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.rs.config\[connString,<user>,<password>\]|<|<|<| |Returns a current configuration of the replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.rs.status\[connString,<user>,<password>\]|<|<|<| |Returns a replica set status from the point of view of the member where the method is run.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.server.status\[connString,<user>,<password>\]|<|<|<| |Returns database state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| | |mongodb.sh.discovery\[connString,<user>,<password>\]|<|<|<| |Returns a list of discovered shards present in the cluster.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.| |
zh-cn	### MongoDB  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |mongodb.collection.stats\[connString,<user>,<password>,<database>,collection\]|<|<|<| |返回一个给定的集合，包含各种存储的统计信息.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.<br>**database** - 数据库名称 (缺省值: admin).<br>**collection** — 集合名称.| | |mongodb.collections.discovery\[connString,<user>,<password>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd) 返回发现的集合列表.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.collections.usage\[connString,<user>,<password>\]|<|<|<| |返回集合的使用统计信息.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.connpool.stats\[connString,<user>,<password>\]|<|<|<| |返回有关从当前数据库实例到分片集群或副本集的其他成员的开放外向连接的信息。.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.db.stats\[connString,<user>,<password>,<database>\]|<|<|<| |返回给定数据库系统状态的统计信息.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.<br>**database** - database name (default: admin).| | |mongodb.db.discovery\[connString,<user>,<password>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd) 返回一个发现的数据库列表.|JSON 对象|**connString** - URI or session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.jumbo\_chunks.count\[connString,<user>,<password>\]|<|<|<| |返回 jumbo chunks 的计数.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.oplog.stats\[connString,<user>,<password>\]|<|<|<| |使用从 oplog 轮询的数据返回副本集的状态.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.ping\[connString,<user>,<password>\]|<|<|<| |测试连接是否存活.|1 - 连接存活<br><br>0 - 连接断开 (如果出现包括认证和配置问题的错误提示).|**connString** - URI or session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.rs.config\[connString,<user>,<password>\]|<|<|<| |返回当前副本集的配置.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.rs.status\[connString,<user>,<password>\]|<|<|<| |从运行方法的 member 的角度返回副本集状态.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.server.status\[connString,<user>,<password>\]|<|<|<| |返回数据库的状态.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| | |mongodb.sh.discovery\[connString,<user>,<password>\]|<|<|<| |返回集群中已发现的分片的列表.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - MongoDB 登陆凭证.| |

en-us	 #### Monitoring → Latest data updated The Latest data section now shows the time since last check (for example, 1m 20s) instead of the last item execution time. Additionally, it is now possible  to view a raw value of an item without units or value mapping applied by hovering over the last value.   
zh-cn	## Breaking changes  

en-us	##### Monitoring → Overview removed  The Overview section in the Monitoring menu has been removed completely. The same functionality can be still accessed by using the *Data overview* and *Trigger overview* dashboard [widgets](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets).
zh-cn	##### 移除 Monitoring（监控） → Overview（概览）  监控菜单中的概览部分已被完全移除。使用仪表板 [小部件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets)  *Data overview（数据概览）* and *Trigger overview（触发器概览）* 可以实现相同的功能。

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	##### Monitoring server availability  At least three methods (or combination of all methods) may be used in order to monitor availability of a server.  -   ICMP ping ("icmpping" key) -   "zabbix\[host,agent,available\]" item -   trigger function nodata() for monitoring the availability of hosts     that use active checks only
zh-cn	#####  监控服务器可用性  为了监控服务器的可用性，可以使用至少三种方法（或所有方法的组合）。  -   ICMP ping ("icmpping" 键值) -   "zabbix\[host,agent,available\]"监控项 -   触发器函数nodata() 仅使用主动检查的主机可用性

en-us	#### Monitoring specific applications
zh-cn	#### 监控特定应用

en-us	### Monitoring  The Zabbix API allows you to access history and other data gathered during monitoring.
zh-cn	### 监控  Zabbix API 允许您访问在监控期间收集的历史记录和其他数据。

en-us	##### Monotonic change  It is now possible to check for monotonic increase or decrease in item values using the new **monoinc()** or **monodec()** [history functions](/manual/appendix/functions/history).
zh-cn	##### 单调变化  现在可以使用新的 **monoinc()** 或 **monodec()** [历史函数](/manual/appendix/functions/history) 检查监控项值的单调增加或减少。

en-us	 ### Month abbreviated with capital letter  A "month" is now abbreviated with the capital "M" in the frontend.  Previously it was abbreviated with the small "m", overlapping  with the abbreviation of a minute.
zh-cn	### 月份用大写字母缩写  “月”现在缩写为前端的大写字母“M”。 以前它被缩写为小写的“m”，与分钟的缩写重叠。

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	 ### MQTT  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<| |Subscribes to a specific topic or topics (with wildcards) of the provided broker and waits for publications.|Depending on topic content.<br><br>If wildcards are used, returns topic content as JSON.|**broker\_url** - MQTT broker URL (if empty, *localhost* with port 1883 is used).<br>**topic** - MQTT topic (mandatory). Wildcards (+,\#) are supported.<br>**username,password** - authentication credentials (if required)|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (active)' item type).<br><br>TLS encryption certificates can be used by saving them into a default location (e.g. `/etc/ssl/certs/` directory for Ubuntu). For TLS, use the `tls://` scheme.|
zh-cn	### MQTT  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<| |可以使用通配符订阅所提供代理的一个或多个特定 topic，并等待发布.|依赖 topic 内容.<br><br>如果使用通配符返回的 topic 内容是 JSON 格式.|**broker\_url** - MQTT broker URL (如果为空, *localhost* 会使用 1883 端口).<br>**topic** - MQTT topic (必选参数). 支持通配符 (+,\#) .<br>**username,password** - 身份认证凭据 (如果需要)|该项必须配置为 [active check](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (主动)' 监控项类型).<br><br>TLS加密证书可通过将其保存到默认位置来使用 (比如 Ubuntu 系统使用 `/etc/ssl/certs/` 目录). 对于 TLS, 使用 `tls://` scheme.|

en-us	##### Multiple HTTP requests  Collect the content of both *https://www.example.com* and *https://www.example.com/release\_notes*:  -   Create an item with type "Script".\ -   In the *Script* field, enter the following code:  ``` {.java} var request = new HttpRequest(); return request.get("https://www.example.com") + request.get("https://www.example.com/release_notes"); ```
zh-cn	##### 多个HTTP请求  同时从 *https://www.example.com* 和 *https://www.example.com/release\_notes*两个站点收集数据:  - 创建一个监控项，类型选择”脚本“。  - 在*脚本*字段填写下面的代码：  ``` {.java} var request = new HttpRequest(); return request.get("https://www.example.com") + request.get("https://www.example.com/release_notes"); ```

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 8.0+ with mysqlsh  This method can be used with a running Zabbix server, but it is recommended to stop the server for the time of the upgrade. The MySQL Shell (*mysqlsh*) must be [installed](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-install-linux-quick.html) and able to connect to the DB.   * Log in to MySQL console as root (recommended) or as any user with FILE privileges.   * Start MySQL with [local_infile](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_local_infile) variable enabled.  * Rename old tables and create new tables by running `history_pk_prepare.sql`.  ``` mysql -uzabbix -p<password> zabbix < /usr/share/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  * Export and import data.  Connect via mysqlsh. If using a socket connection, specifying the path might be required.      sudo mysqlsh -uroot -S /run/mysqld/mysqld.sock --no-password -Dzabbix  Run (CSVPATH can be changed as needed):  ``` {.javascript} CSVPATH="/var/lib/mysql-files";  util.exportTable("history_old", CSVPATH + "/history.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history.csv", {"dialect": "csv", "table": "history" });  util.exportTable("history_uint_old", CSVPATH + "/history_uint.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_uint.csv", {"dialect": "csv", "table": "history_uint" });  util.exportTable("history_str_old", CSVPATH + "/history_str.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_str.csv", {"dialect": "csv", "table": "history_str" });  util.exportTable("history_log_old", CSVPATH + "/history_log.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_log.csv", {"dialect": "csv", "table": "history_log" });  util.exportTable("history_text_old", CSVPATH + "/history_text.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_text.csv", {"dialect": "csv", "table": "history_text" }); ```  * Follow [post-migration instructions](#after-migration) to drop the old tables.
zh-cn	#### MySQL 8.0+ 和 mysqlsh  此方法可用于正在运行的 Zabbix 服务器，但建议在升级时停止服务器。 MySQL Shell (*mysqlsh*) 必须 [已安装](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-install-linux-quick.html) 并且能够连接到数据库。  * 以 root（推荐）或任何具有 FILE 权限的用户身份登录 MySQL 控制台。  * 启用 [local_infile](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_local_infile) 变量启动 MySQL。  * 通过运行 `history_pk_prepare.sql` 重命名旧表并创建新表。  ``` mysql -uzabbix -p<password> zabbix < /usr/share/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  * 导出和导入数据。  通过 mysqlsh 连接。 如果使用套接字连接，可能需要指定路径。    · sudo mysqlsh -uroot -S /run/mysqld/mysqld.sock --no-password -Dzabbix  运行（CSVPATH可根据需要更改）：  ``` {.javascript} CSVPATH="/var/lib/mysql-files";  util.exportTable("history_old", CSVPATH + "/history.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history.csv", {"dialect": "csv", "table": "history" });  util.exportTable("history_uint_old", CSVPATH + "/history_uint.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_uint.csv", {"dialect": "csv", "table": "history_uint" });  util.exportTable("history_str_old", CSVPATH + "/history_str.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_str.csv", {"dialect": "csv", "table": "history_str" });  util.exportTable("history_log_old", CSVPATH + "/history_log.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_log.csv", {"dialect": "csv", "table": "history_log" });  util.exportTable("history_text_old", CSVPATH + "/history_text.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_text.csv", {"dialect": "csv", "table": "history_text" }); ```  * 按照 [post-migration instructions](#after-migration) 删除旧表。

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 custom error codes  If Zabbix is used with MySQL installation on Azure, an unclear error message *\[9002\] Some errors occurred* may appear in Zabbix logs. This generic error text is sent to Zabbix server or proxy by the database. To get more information about the cause of the error, check Azure logs.
zh-cn	#### MySQL 自定义错误代码  如果在 Azure 上安装 Zabbix 和  MySQL，Zabbix 日志中可能会出现不明确的报错信息 *\[9002\] Some errors occurred* 。这种通用错误文本由数据库发送到 Zabbix server 或 proxy。若要获取有关错误原因的详细信息，请查看 Azure 日志。

en-us	#### MySQL  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### MySQL 5.7+/8.0+  * Rename old tables, create new tables by running `history_pk_prepare.sql`.  ``` mysql -uzabbix -p<password> zabbix < /usr/share/doc/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  * Export and import data  mysqlsh should be [installed](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-install-linux-quick.html).  mysqlsh should be able to connect to the DB. If connection is done  through socket, it could be needed to explicitly state a path to it.  Connect via mysqlsh:      sudo mysqlsh -uroot -S /run/mysqld/mysqld.sock --no-password -Dzabbix  Run (CSVPATH should/could be tweaked according to needs):  ``` CSVPATH="/var/lib/mysql-files";  util.exportTable("history_old", CSVPATH + "/history.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history.csv", {"dialect": "csv", "table": "history" });  util.exportTable("history_uint_old", CSVPATH + "/history_uint.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_uint.csv", {"dialect": "csv", "table": "history_uint" });  util.exportTable("history_str_old", CSVPATH + "/history_str.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_str.csv", {"dialect": "csv", "table": "history_str" });  util.exportTable("history_log_old", CSVPATH + "/history_log.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_log.csv", {"dialect": "csv", "table": "history_log" });  util.exportTable("history_text_old", CSVPATH + "/history_text.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_text.csv", {"dialect": "csv", "table": "history_text" }); ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### MySQL <5.7, MariaDB (or if mysqlsh cannot be used for some reason)  This option is slower and more time consuming, use only if  there is a reason not to use mysqlsh.  * Rename old tables, create new tables by running `history_pk_prepare.sql`.  ``` mysql -uzabbix -p<password> zabbix < /usr/share/doc/zabbix-sql-scripts/mysql/history_pk_prepare.sql ```  * Export and import data  Check if import/export is enabled only for files in the specific path:  ``` mysql> SELECT @@secure_file_priv; +-----------------------+ | @@secure_file_priv    | +-----------------------+ | /var/lib/mysql-files/ | +-----------------------+ ```  If the value is a path to directory, export/import could be performed for  files in that directory. In this case paths to files in queries should be  edited accordingly. Alternatively, secure_file_priv could be disabled  (set to empty string) during upgrade. If the value is empty, export/import  could be performed to/from files that could be located anywhere.  *max_execution_time* should be disabled before exporting data to avoid timeout during export.  ``` SET @@max_execution_time=0;  SELECT * INTO OUTFILE '/var/lib/mysql-files/history.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_old; LOAD DATA INFILE '/var/lib/mysql-files/history.csv' IGNORE INTO TABLE history FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_uint.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_uint_old; LOAD DATA INFILE '/var/lib/mysql-files/history_uint.csv' IGNORE INTO TABLE history_uint FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_str.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_str_old; LOAD DATA INFILE '/var/lib/mysql-files/history_str.csv' IGNORE INTO TABLE history_str FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_log.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_log_old; LOAD DATA INFILE '/var/lib/mysql-files/history_log.csv' IGNORE INTO TABLE history_log FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_text.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_text_old; LOAD DATA INFILE '/var/lib/mysql-files/history_text.csv' IGNORE INTO TABLE history_text FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n'; ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### Improving performance  Additional hints for improving performance in both cases:   * Increase bulk_insert_buffer_size buffer in the configuration  file inside [mysqld] section or set it before import with SET:  ``` [mysqld] bulk_insert_buffer_size=256M  mysql cli > SET SESSION bulk_insert_buffer_size= 1024 * 1024 * 256;  mysql cli > ... import queries ...  ```  * See "Optimizing InnoDB bulk data loading": ([MySQL 5.7]([https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-bulk-data-loading.html]),  [MySQL 8.0]([https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-bulk-data-loading.html]))  * Disable binary logging (should not be used in case of a slave servers,  since will not replicate data):  ``` mysql cli > SET SESSION SQL_LOG_BIN=0; mysql cli > ... import queries ... ```  
zh-cn	#### MySQL  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### MySQL 5.7+/8.0+  * Rename old tables, create new tables by running [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/b3e90f1b9574a655e43c6045cf7a5568b1cc1a3b)  * Export and import data  mysqlsh should be [installed](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-install-linux-quick.html).  mysqlsh should be able to connect to the DB. If connection is done  through socket, it could be needed to explicitly state a path to it.  Connect via mysqlsh:      sudo mysqlsh -uroot -S /run/mysqld/mysqld.sock --no-password -Dzabbix  Run (CSVPATH should/could be tweaked according to needs):  ``` CSVPATH="/var/lib/mysql-files";  util.exportTable("history_old", CSVPATH + "/history.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history.csv", {"dialect": "csv", "table": "history" });  util.exportTable("history_uint_old", CSVPATH + "/history_uint.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_uint.csv", {"dialect": "csv", "table": "history_uint" });  util.exportTable("history_str_old", CSVPATH + "/history_str.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_str.csv", {"dialect": "csv", "table": "history_str" });  util.exportTable("history_log_old", CSVPATH + "/history_log.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_log.csv", {"dialect": "csv", "table": "history_log" });  util.exportTable("history_text_old", CSVPATH + "/history_text.csv", { dialect: "csv" }); util.importTable(CSVPATH + "/history_text.csv", {"dialect": "csv", "table": "history_text" }); ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### MySQL <5.7, MariaDB (or if mysqlsh cannot be used for some reason)  This option is slower and more time consuming, use only if  there is a reason not to use mysqlsh.  * Rename old tables, create new tables by running [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/b3e90f1b9574a655e43c6045cf7a5568b1cc1a3b)  * Export and import data  Check if import/export is enabled only for files in the specific path:  ``` mysql> SELECT @@secure_file_priv; +-----------------------+ | @@secure_file_priv    | +-----------------------+ | /var/lib/mysql-files/ | +-----------------------+ ```  If the value is a path to directory, export/import could be performed for  files in that directory. In this case paths to files in queries should be  edited accordingly. Alternatively, secure_file_priv could be disabled  (set to empty string) during upgrade. If the value is empty, export/import  could be performed to/from files that could be located anywhere.  *max_execution_time* should be disabled before exporting data to avoid timeout during export.  ``` SET @@max_execution_time=0;  SELECT * INTO OUTFILE '/var/lib/mysql-files/history.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_old; LOAD DATA INFILE '/var/lib/mysql-files/history.csv' IGNORE INTO TABLE history FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_uint.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_uint_old; LOAD DATA INFILE '/var/lib/mysql-files/history_uint.csv' IGNORE INTO TABLE history_uint FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_str.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_str_old; LOAD DATA INFILE '/var/lib/mysql-files/history_str.csv' IGNORE INTO TABLE history_str FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_log.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_log_old; LOAD DATA INFILE '/var/lib/mysql-files/history_log.csv' IGNORE INTO TABLE history_log FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n';  SELECT * INTO OUTFILE '/var/lib/mysql-files/history_text.csv' FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n' FROM history_text_old; LOAD DATA INFILE '/var/lib/mysql-files/history_text.csv' IGNORE INTO TABLE history_text FIELDS TERMINATED BY ',' ESCAPED BY '"' LINES TERMINATED BY '\n'; ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### Improving performance  Additional hints for improving performance in both cases:   * Increase bulk_insert_buffer_size buffer in the configuration  file inside [mysqld] section or set it before import with SET:  ``` [mysqld] bulk_insert_buffer_size=256M  mysql cli > SET SESSION bulk_insert_buffer_size= 1024 * 1024 * 256;  mysql cli > ... import queries ...  ```  * See "Optimizing InnoDB bulk data loading": ([MySQL 5.7]([https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-bulk-data-loading.html]),  [MySQL 8.0]([https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-bulk-data-loading.html]))  * Disable binary logging (should not be used in case of a slave servers,  since will not replicate data):  ``` mysql cli > SET SESSION SQL_LOG_BIN=0; mysql cli > ... import queries ... ```  

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	 ### MySQL  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |mysql.db.discovery\[connString,<username>,<password>\]|<|<|<| |List of MySQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show databases" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.db.size\[connString,<username>,<password>,dbName\]|<|<|<| |Database size in bytes.|Result of the "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" SQL query for specific database in bytes.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**dbName** - Database name.| | |mysql.get\_status\_variables\[connString,<username>,<password>\]|<|<|<| |Values of global status variables.|Result of the "show global status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.ping\[connString,<username>,<password>\]|<|<|<| |Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.replication.discovery\[connString,<username>,<password>\]|<|<|<| |List of MySQL replications. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show slave status" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| | |mysql.replication.get\_slave\_status\[connString,<username>,<password>,<masterHost>\]|<|<|<| |Replication status.|Result of the "show slave status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**masterHost** - Replication master host name.| | |mysql.version\[connString,<username>,<password>\]|<|<|<| |MySQL version.|String with MySQL instance version.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.| |
zh-cn	### MySQL  |键值|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**备注**| |mysql.db.discovery\[connString, <username>, <password>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)给出 MySQL 数据库列表.|使用 "show databases" SQL 语句在 LLD 查询的结果并且以 JSON 格式输出.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.| | |mysql.db.size\[connString, <username>, <password>,dbName\]|<|<|<| |数据库大小，单位是 byte.|使用 "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" SQL 语句查询特定的数据大小的结果，单位是 byte.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.<br>**dbName** - 数据库名称.| | |mysql.get\_status\_variables\[connString, <username>, <password>\]|<|<|<| |全局状态的变量的值.|使用 "show global status" SQL 语句查询的结果并且以 JSON 格式输出.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.| | |mysql.ping\[connString, <username>, <password>\]|<|<|<| |测试连接是否存活.|1 - 连接存活<br><br>0 - 连接断开 (如果出现包括认证和配置问题的错误提示).|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.| | |mysql.replication.discovery\[connString, <username>, <password>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)列出 MySQL 的 Replication 列表.|使用 "show slave status" SQL 语句在 LLD 中查询的结果并且以 JSON 格式输出.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.| | |mysql.replication.get\_slave\_status\[connString, <username>, <password>, <masterHost>\]|<|<|<| |Replication 状态.|使用 "show slave status" SQL 语句查询的结果并且以 JSON 格式输出.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.<br>**masterHost** - Replication 中 master 的主机名.| | |mysql.version\[connString, <username>, <password>\]|<|<|<| |MySQL 版本.|以字符串的形式输出 MySQL 实例的版本信息.|**connString** - URI 或者 session name.<br>**username, password** - MySQL 登陆凭证.| |

en-us	#### MySQL/MariaDB  **1.** Check the database character set and collation.  For example:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | latin2                   | latin2 _general_ci   |     +--------------------------+----------------------+  As we see, the character set here is not 'utf8' and collation is not 'utf8\_bin', so we need to fix them.  **2.** Stop Zabbix.  **3.** Create a backup copy of the database!  **4.** Fix the character set and collation on database level:      alter database <your DB name> character set utf8 collate utf8_bin;  Fixed values:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8                     | utf8_bin             |     +--------------------------+----------------------+   **5.** Load the [script](https://support.zabbix.com/secure/attachment/113858/113858_utf8_convert.sql) to fix character set and collation on table and column level:      mysql <your DB name> < utf8_convert.sql  **6.** Execute the script:                     SET @ZABBIX_DATABASE = '<your DB name>';     If MariaDB →  set innodb_strict_mode = OFF;                            CALL zbx_convert_utf8();     If MariaDB →  set innodb_strict_mode = ON;                       drop procedure zbx_convert_utf8;  Note that data encoding will be changed on disk. For example, when converting characters like Æ, Ñ, Ö from 'latin1' to 'utf8' they will go from 1 byte to 2 bytes. Thus the repaired database may require more space than before.  **7.** If no errors - you may want to create a database backup copy with the fixed database.  **8.** Start Zabbix.  
zh-cn	#### MySQL/MariaDB  **1.** Check the database character set and collation.  For example:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | latin2                   | latin2 _general_ci   |     +--------------------------+----------------------+  As we see, the character set here is not 'utf8' and collation is not 'utf8\_bin', so we need to fix them.  **2.** Stop Zabbix.  **3.** Create a backup copy of the database!  **4.** Fix the character set and collation on database level:      alter database <your DB name> character set utf8 collate utf8_bin;  Fixed values:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8                     | utf8_bin             |     +--------------------------+----------------------+   **5.** Load the [script](https://support.zabbix.com/secure/attachment/113858/113858_utf8_convert.sql) to fix character set and collation on table and column level:      mysql <your DB name> < utf8_convert.sql  **6.** Execute the script:                     SET @ZABBIX_DATABASE = '<your DB name>';     If MariaDB →  set innodb_strict_mode = OFF;                            CALL zbx_convert_utf8();     If MariaDB →  set innodb_strict_mode = ON;                       drop procedure zbx_convert_utf8;  Note that data encoding will be changed on disk. For example, when converting characters like Æ, Ñ, Ö from 'latin1' to 'utf8' they will go from 1 byte to 2 bytes. Thus the repaired database may require more space than before.  **7.** If no errors - you may want to create a database backup copy with the fixed database.  **8.** Start Zabbix.  

en-us	#### MySQL/MariaDB  Historically, MySQL and derivatives used 'utf8' as an alias for utf8mb3 - MySQL's own 3-byte implementation of the standard UTF8, which is 4-byte. Starting from MySQL 8.0.28 and MariaDB 10.6.1, 'utf8mb3' character set is deprecated and at some point its support will be dropped while 'utf8' will become a reference to 'utf8mb4'. Since Zabbix 6.0, 'utf8mb4' is supported. To avoid future problems, it is highly recommended to use 'utf8mb4'. Another advantage of switching to 'utf8mb4' is support of supplementary Unicode characters.  ::: notewarning As versions before Zabbix 6.0 are not aware of utf8mb4, make sure to first upgrade  Zabbix server and DB schema to 6.0.x before executing utf8mb4 conversion. :::  **1.** Check the database character set and collation.  For example:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | latin2                   | latin2 _general_ci   |     +--------------------------+----------------------+  Or:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8                     | utf8_bin             |     +--------------------------+----------------------+  As we see, the character set here is not 'utf8mb4' and collation is not 'utf8mb4\_bin', so we need to fix them.  **2.** Stop Zabbix.  **3.** Create a backup copy of the database!  **4.** Fix the character set and collation on database level:      alter database <your DB name> character set utf8mb4 collate utf8mb4_bin;  Fixed values:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8mb4                  | utf8mb4_bin          |     +--------------------------+----------------------+   **5.** Load the [script](../../../../assets/en/manual/appendix/install/utf8mb4_convert.sql) to fix character set and collation on table and column level:      mysql <your DB name> < utf8mb4_convert.sql  **6.** Execute the script:                     SET @ZABBIX_DATABASE = '<your DB name>';     If MariaDB →  set innodb_strict_mode = OFF;                            CALL zbx_convert_utf8();     If MariaDB →  set innodb_strict_mode = ON;                       drop procedure zbx_convert_utf8;  Please note that 'utf8mb4' is expected to consume slightly more disk space.  **7.** If no errors - you may want to create a database backup copy with the fixed database.  **8.** Start Zabbix.
zh-cn	#### MySQL/MariaDB  历史版本中, MySQL 及其衍生产品中使用的 UTF8（utf8mb3） 只能实现最长 3 个字节的字符存储，那 4 个字节呢。从 MySQL 8.0.28 及 MariaDB 10.6.1 的版本之后, 'utf8mb3' 被弃用，并会在未来某个时候被删除，而 'utf8mb4' 将被新版本中 'utf8' 字符集引用。在Zabbix  6.0 中 'utf8mb4' 字符集也得到了支持，为了避免将来发生未知的问题，我们强烈建议您使用 'utf8mb4' 字符集。 并且支持的Unicode字符也是切换到 'utf8mb4' 的另一个优点。  ::: notewarning 由于Zabbix 6.0之前的版本不兼容utf8mb4，在执行utf8mb4转换之前，请确保首先升级Zabbix server和DB schema 为6.0。 :::  **1.** 检测数据库的字符集及字符序。  例:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | latin2                   | latin2 _general_ci   |     +--------------------------+----------------------+  或者:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8                     | utf8_bin             |     +--------------------------+----------------------+  当我们看到此处的字符集不是 'utf8mb4\_bin' 时，我们则需要更改它。  **2.** 停止 Zabbix 服务。  **3.** 将数据库进行备份！  **4.** 使用如下命令修复数据库的字符集及字符序:      alter database <your DB name> character set utf8mb4 collate utf8mb4_bin;  再次检测:      mysql> SELECT @@character_set_database, @@collation_database;     +--------------------------+----------------------+     | @@character_set_database | @@collation_database |     +--------------------------+----------------------+     | utf8mb4                  | utf8mb4_bin          |     +--------------------------+----------------------+   **5.** 导入下面的 sql 来修复每张表中各个列的字符集 [script](../../../../assets/en/manual/appendix/install/utf8mb4_convert.sql)     mysql <your DB name> < utf8mb4_convert.sql  **6.** 执行如下命令:                    SET @ZABBIX_DATABASE = '<your DB name>';     If MariaDB →  set innodb_strict_mode = OFF;                           CALL zbx_convert_utf8();     If MariaDB →  set innodb_strict_mode = ON;                      drop procedure zbx_convert_utf8;  请注意，“utf8mb4” 会占用您相对较多的磁盘空间。  **7.** 如果没有错误信息 - 您可能希望备份一个修复过后的数据库。  **8.** 启动 Zabbix 服务.

en-us	##### MySQL  Several user parameters can be used for the monitoring of MySQL in the agent configuration file: /usr/local/etc/zabbix\_agentd.conf      ### Set of parameters for monitoring MySQL server (v3.23.42 and later)     ### Change -u and add -p if required     #UserParameter=mysql.ping,mysqladmin -uroot  ping|grep alive|wc -l     #UserParameter=mysql.uptime,mysqladmin -uroot status|cut -f2 -d":"|cut -f2 -d" "     #UserParameter=mysql.threads,mysqladmin -uroot status|cut -f3 -d":"|cut -f2 -d" "     #UserParameter=mysql.questions,mysqladmin -uroot status|cut -f4 -d":"|cut -f2 -d" "     #UserParameter=mysql.slowqueries,mysqladmin -uroot status|cut -f5 -d":"|cut -f2 -d" "     #UserParameter=mysql.qps,mysqladmin -uroot status|cut -f9 -d":"|cut -f2 -d" "     #UserParameter=mysql.version,mysql -V  -   *mysql.ping*  Check whether MySQL is alive.          Result: 0 - not started 1 - alive  -   *mysql.uptime*  Number of seconds MySQL is running.  -   *mysql.threads*  Number of MySQL threads.  -   *mysql.questions*  Number of processed queries.  -   *mysql.slowqueries*  Number of slow queries.  -   *mysql.qps*  Queries per second.  -   *mysql.version*  Version of MySQL. For example: mysql Ver 14.14 Distrib 5.1.53, for pc-linux-gnu (i686)  For additional information see also the userparameter\_mysql.conf file in conf/zabbix\_agentd directory.
zh-cn	##### MySQL  代理配置文件/usr/local/etc/zabbix\_agentd.conf中有几个用户参数可以用来监控MySQL      ### Set of parameters for monitoring MySQL server (v3.23.42 and later)     ### Change -u and add -p if required     #UserParameter=mysql.ping,mysqladmin -uroot  ping|grep alive|wc -l     #UserParameter=mysql.uptime,mysqladmin -uroot status|cut -f2 -d":"|cut -f2 -d" "     #UserParameter=mysql.threads,mysqladmin -uroot status|cut -f3 -d":"|cut -f2 -d" "     #UserParameter=mysql.questions,mysqladmin -uroot status|cut -f4 -d":"|cut -f2 -d" "     #UserParameter=mysql.slowqueries,mysqladmin -uroot status|cut -f5 -d":"|cut -f2 -d" "     #UserParameter=mysql.qps,mysqladmin -uroot status|cut -f9 -d":"|cut -f2 -d" "     #UserParameter=mysql.version,mysql -V  -   *mysql.ping*  检查 MySQL 是否存活。          Result: 0 - not started 1 - alive  -   *mysql.uptime*  MySQL 运行的秒数。  -   *mysql.threads*  MySQL 线程数。  -   *mysql.questions*  已处理的查询数。  -   *mysql.slowqueries*  慢查询的数量。  -   *mysql.qps*  每秒查询数。  -   *mysql.version*  MySQL的版本。例如： mysql Ver 14.14 Distrib 5.1.53，适用于pc-linux-gnu (i686)  有关其他信息，另请参阅 conf/zabbix\_agentd目录中的userparameter\_mysql.conf 文件。

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	##### Naming convention  Before you create a module, it is important to agree on the naming convention for different module items such as directories and files so that we could keep things well organized. You can also find examples above, in the [Module structure](#module_structure) section.  |Item|Naming rules|Example| |----|------------|-------| |*Module directory*|Lowercase \[a-z\], underscore and decimal digits|example\_v2| |*Action subdirectories*|Lowercase \[a-z\] and underscore character|data\_export| |*Action files*|CamelCase, ending with action type|SomethingView.php| |*View and partial files*|Lowercase \[a-z\]<br>Words separated with dot<br>Prefixed by `module.` followed by module name<br>Ending with action type and .php file extension|module.example.something.view.php| |*Javascript files*|The same rules apply as for view and partial files, except the .js.php file extension.|module.example.something.view.js.php|  Note that the 'module' prefix and name inclusion is mandatory for view and partial file names, unless you need to override Zabbix core views or partials. This rule, however, does not apply to action file names.
zh-cn	 ##### 命名约定  在创建模块之前，重要的是要就不同模块项（如目录和文件）的命名约定达成一致，以便我们可以保持良好的组织状态。您也可以在上面的 [模块结构](#module_structure) 部分找到示例。  |项目|命名规则|示例| |----|------------|-------| |*模块目录*|小写字母 \[a-z\], 下划线和小数|example\_v2| |*动作子目录*|小写字母 [a-z], 下划线和小数|data\_export| |*动作文件*|骆驼拼写法，以动作类型结尾|SomethingView.php| |*视图和部分文件*|小写字母 \[a-z\]<br>用点分隔的单词<br>前缀为`module.`后跟模块名称<br>结尾，显示操作类型和.php文件扩展名|module.example.something.view.php| |*Javascript 文件*|与视图文件和部分文件的规则相同，但文件扩展名.js.php除外。|module.example.something.view.js.php|  请注意，'module'前缀和名称包含对于视图和部分文件名是必需的，除非您需要覆盖Zabbix核心视图或部分视图。但是，此规则不适用于操作文件名。

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 data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**net.dns**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |Checks if DNS service is up.|0 - DNS is down (server did not respond or DNS resolution failed)<br><br>1 - DNS is up|**ip** - IP address of DNS server (leave empty for the default DNS server, on Windows supported for Zabbix agent 2, ignored for Zabbix agent)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - number of tries for the request (default is 2)<br>**protocol** (since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (not supported for Zabbix agent on Windows, Zabbix agent 2 on all OS), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns*| |**net.dns.record**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |Performs a DNS query.|Character string with the required type of information|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows, unless using Zabbix agent 2 version 6.0.1 or newer) - number of tries for the request (default is 2)<br>**protocol**(since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (not supported for Zabbix agent on Windows, Zabbix agent 2 on all OS), *HINFO*, *MINFO*, *TXT*, *AAAA*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns.query*| |**net.if.collisions**\[if\]|<|<|<| |Number of out-of-window collisions.|Integer|**if** - network interface name| | |**net.if.discovery**|<|<|<| |List of network interfaces. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>On FreeBSD, OpenBSD and NetBSD supported since Zabbix 2.2.<br><br>Some Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names.| |**net.if.in**\[if,<mode>\]|<|<|<| |Incoming traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*frame* - the number of packet framing errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver<br>*multicast* - the number of multicast frames received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix 1.8.6.<br><br>Examples:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |**net.if.out**\[if,<mode>\]|<|<|<| |Outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*collisions (colls)* - the number of collisions detected on the interface<br>*carrier* - the number of carrier losses detected by the device driver<br>*compressed* - the number of compressed packets transmitted by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix agent 1.8.6 version.<br><br>Examples:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |**net.if.total**\[if,<mode>\]|<|<|<| |Sum of incoming and outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Examples:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.<br><br>Note that dropped packets are supported only if both net.if.in and net.if.out work for dropped packets on your platform.| |**net.tcp.listen**\[port\]|<|<|<| |Checks if this TCP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - TCP port number|Example:<br>=> net.tcp.listen\[80\]<br><br>On Linux supported since Zabbix 1.8.4<br><br>Since Zabbix 3.0.0, on Linux kernels 2.6.14 and above, information about listening TCP sockets is obtained from the kernel's NETLINK interface, if possible. Otherwise, the information is retrieved from /proc/net/tcp and /proc/net/tcp6 files.| |**net.tcp.port**\[<ip>,port\]|<|<|<| |Checks if it is possible to make TCP connection to specified port.|0 - cannot connect<br><br>1 - can connect|**ip** - IP or DNS name (default is 127.0.0.1)<br>**port** - port number|Example:<br>=> net.tcp.port\[,80\] → can be used to test availability of web server running on port 80.<br><br>For simple TCP performance testing use net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).| |**net.tcp.service**\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.port for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |**net.tcp.service.perf**\[service,<ip>,<port>\]|<|<|<| |Checks performance of TCP service.|0 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,<port>\] for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |**net.tcp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.tcp.socket.count\[,80,,,established\] → check if local TCP port 80 is in "established" state<br><br>This item is supported since Zabbix 6.0.| |**net.udp.listen**\[port\]|<|<|<| |Checks if this UDP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - UDP port number|Example:<br>=> net.udp.listen\[68\]<br><br>On Linux supported since Zabbix 1.8.4| |**net.udp.service**\[service,<ip>,<port>\]|<|<|<| |Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |**net.udp.service.perf**\[service,<ip>,<port>\]|<|<|<| |Checks performance of UDP service.|0 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |**net.udp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *unconn*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → check if any UDP socket is in "listening" state<br><br>This item is supported since Zabbix 6.0.|
zh-cn	##### 网络数据  |键值|<|<|<| |---|---|---|---| |描述|返回值|参数|注释| |**net.dns**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |检查DNS服务是否启动|0 - DNS 已关闭 (服务器并没有响应或DNS解析失败)<br><br>1 - DNS 已启动|**ip** - DNS服务器IP地址 (默认DNS服务器上的IP留空,在Windows上忽略)<br>**name** -要查询的DNS名称<br>**type** - 要查询的记录类型 (默认为 *SOA*)<br>**timeout** (在Windows上忽略) -请求超时秒数 (默认是 1 秒)<br>**count** (在在Windows上忽略) -请求的尝试次数 (默认是 2)<br>**protocol** (自版本3.0后) - 用于执行 DNS 查询的协议: *udp* (默认) 或 *tcp*|例如:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>可能的值 `type` 是:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (Windows除外), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>不支持国际化域名，请改用 IDNA 编码名称。<br><br>从 Zabbix 1.8.6 (Unix) 和 2.0.0 (Windows) 开始支持 SRV 记录类型.<br><br>Zabbix 2.0 之前的命名（仍然支持）: *net.tcp.dns*| |**net.dns.record**\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<| |执行 DNS 查询。|具有所需信息类型的字符串|**ip** - DNS 服务器的 IP 地址（默认 DNS 服务器留空，在 Windows 上忽略）<br>**name** - 要查询的 DNS 名称<br>**type** - 要查询的记录类型(默认为 *SOA*)<br>**timeout** (在 Windows 上忽略) - 请求超时秒数 (默认是 1 秒)<br>**count** (在 Windows 上忽略) - 请求的尝试次数(默认是2)<br>**protocol**(自 3.0 版起) - 用于执行 DNS 查询的协议: *udp* (默认) 或 *tcp*|例如:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>可能的值 `type` 是:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (Windows除外), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>不支持国际化域名，请改用 IDNA 编码名称。<br><br>从 Zabbix 1.8.6 (Unix) 和 2.0.0 (Windows) 开始支持 SRV 记录类型。<br><br>Zabbix 2.0 之前的命名（仍然支持）: *net.tcp.dns.query*| |**net.if.collisions**\[if\]|<|<|<| |Number of out-of-window collisions.|整型|**if** - 网络接口名称| | |**net.if.discovery**|<|<|<| |网络接口列表.用于低级别的发现。|JSON 对象| |自 Zabbix 2.0后支持<br><br>在 FreeBSD, OpenBSD 和 NetBSD 上从 Zabbix 2.2后开始支持<br><br>某些Windows版本 (如 Server 2008)可能需要安装最新更新以支持接口名称中的非ASCII 字符。| |**net.if.in**\[if,<mode>\]|<|<|<| |网络接口的传入流量统计|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** - 可能的值:<br>*bytes* - 字节数 (默认)<br>*packets* - 包数<br>*errors* - 错误数<br>*dropped* - 丢弃的数据包数量<br>*overruns (fifo)* - FIFO 缓冲错误数<br>*frame* - 数据包帧错误数<br>*compressed* - 设备驱动程序发送或接收的压缩数据包数<br>*multicast* - 设备驱动程序接收的多播帧数|在Windows上, 该监控项从64位计数器中获取值（如果可用），Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent将使用 32 位计数器。 <br><br>从 Zabbix 1.8.6 开始支持 Windows 上的多字节接口名称<br><br>例如:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>您可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。| |**net.if.out**\[if,<mode>\]|<|<|<| |网络接口的传出流量统计|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** - 可能的值:<br>*bytes* - 字节数 (默认)<br>*packets* -包数<br>*errors* - 错误数<br>*dropped* - 丢弃的包的数量<br>*overruns (fifo)* -  FIFO 缓冲错误数 <br>*collisions (colls)* - 接口上检测到的冲突数<br>*carrier* - 在设备驱动程序检测到的载体丢失数<br>*compressed* -设备驱动程序传输的压缩数据包数|在 Windows 上，该监控项从 64 位计数器中获取值（如果可用）。Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent将使用 32 位计数器。<br><br>从 Zabbix agent 1.8.6 版本开始支持 Windows 上的多字节接口名称。<br><br>例如:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>您可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。| |**net.if.total**\[if,<mode>\]|<|<|<| |网络接口上传入和传出流量统计的总和。|整型|**if** - 网络接口名称 (Unix); 网络接口完整描述或 IPv4 地址；或者，如果在大括号内，网络接口GUID（窗口）<br>**mode** -可能值:<br>*bytes* - 字节数 (默认)<br>*packets* - 包数<br>*errors* - 错误数<br>*dropped* - 丢弃的数据包数量<br>*overruns (fifo)* -  FIFO缓冲错误数<br>*compressed* - 设备驱动程序发送或接收的压缩数据包数|在 Windows 上，该监控项从 64 位计数器中获取值（如果可用）。Windows Vista 和 Windows Server 2008 中引入了 64 位接口统计计数器。如果 64 位计数器不可用，agent将使用 32 位计数器。<br><br>例如:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>Y您可以使用 net.if.discovery 或 net.if.list 项获取 Windows 上的网络接口描述。<br><br>可以将此键与预处理每秒更改步骤一起使用，以获取每秒字节数统计信息。<br><br>请注意，仅当 net.if.in 和 net.if.out 都在您平台上的丢弃数据包时，才支持丢弃数据包。| |**net.tcp.listen**\[port\]|<|<|<| |检查TCP端口是否处于监听状态|0 - 它不处于监听状态<br><br>1 - 它处于监听状态|**port** - TCP端口号|例如:<br>=> net.tcp.listen\[80\]<br><br> 自 Zabbix 1.8.4后在Linux上支持<br><br>自 Zabbix 3.0.0后, 在 Linux 内核 2.6.14及以上,如果可能，从内核的 NETLINK 接口获取有关侦听 TCP 套接字的信息. 否则，将从 /proc/net/tcp 和 /proc/net/tcp6 文件中检索信息。| |**net.tcp.port**\[<ip>,port\]|<|<|<| |检查是否可以与指定端口建立 TCP 连接。|0 -不能连接<br><br>1 - 能连接|**ip** - IP 或 DNS 名称 (默认是 127.0.0.1)<br>**port** - 端口号|例如:<br>=> net.tcp.port\[,80\] → 可用于测试在端口80上运行Web 服务的可用性<br><br>对于简单的TCP性能测试，使用 net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>请注意，这些检查可能会导致增加系统守护程序日志文件中的额外信息（通常会记录SMTP和SSH会话）。| |**net.tcp.service**\[service,<ip>,<port>\]|<|<|<| |检查服务是否正在运行并接受 TCP 连接。|0 - 服务关闭<br><br>1 - 服务正在运行|**service** - 任意一个:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (另见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是 127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例如:<br>=> net.tcp.service\[ftp,,45\] → 用于测试在tcp端口45上的FTP服务的可用性.<br><br>请注意，这些检查可能会导致系统守护程序日志文件中出现额外消息（SMTP 和 SSH 会话正在通常记录）。<br><br>目前不支持检查加密协议（如端口 993 上的 IMAP 或端口 995 上的 POP）。作为一种解决方法，请使用 net.tcp.port 进行此类检查。<br><br>仅 Zabbix agent 2 支持在 Windows 上检查 LDAP 和 HTTPS。<br><br>请注意，telnet 检查会查找登录提示（末尾为“：”）。<br><br>请你参阅[已知问题](/manual/installation/known_issues#https_checks)用于检查HTTPS服务。<br><br>从Zabbix2.0后开始支持*https* 和 *telnet* 服务。| |**net.tcp.service.perf**\[service,<ip>,<port>\]|<|<|<| |检查TCP服务的性能。|0 - 服务已关闭<br><br>seconds - 连接到服务花费的时间（秒）|**service** -以下任意一个:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (见 [详细](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是 127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例如:<br>=> net.tcp.service.perf\[ssh\] → 可用于测试来自 SSH 服务器的初始响应速度。<br><br>目前不支持检查加密协议（如端口 993 上的 IMAP 或端口 995 上的 POP）。作为一种解决方法，请使用 net.tcp.service.perf\[tcp,<ip>,<port>\] 进行此类检查。<br><br>仅 Zabbix 代理 2 支持在 Windows 上检查 LDAP 和 HTTPS。<br><br>请注意，telnet 检查会查找登录提示（末尾为“：”）。<br><br>请你参阅[已知问题](/manual/installation/known_issues#https_checks)用于检查HTTPS服务。<br><br>从Zabbix2.0后开始支持*https* 和 *telnet* 服务。| |**net.tcp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |返回与参数匹配的套接字数|整型|**laddr** - 本地 IPv4/6 地址 或 CIDR 子网<br>**lport** - 本地的端口号或服务名称<br>**raddr** - 远程 IPv4/6 地址或CIDR子网<br>**rport** - 远程端口号或服务名称<br>**state** - 连接状态(*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|Zabbix agent和Zabbix agent 2均在Linux上支持此项，64位 Windows在Zabbix agent 2上支持此项<br><br>例如:<br>=> net.tcp.socket.count\[,80,,,established\] →检查本地 TCP 端口 80 是否处于“已建立”状态<br><br>从 Zabbix 6.0后开始支持此项| |**net.udp.listen**\[port\]|<|<|<| |检查UDP端口是否处于监听状态|0 - 它不处于监听状态<br><br>1 -它处于监听状态|**port** - UDP端口号|例如:<br>=> net.udp.listen\[68\]<br><br>在Linux上自Zabbix 1.8.4后支持| |**net.udp.service**\[service,<ip>,<port>\]|<|<|<| |检查服务是否正在运行并响应 UDP 请求。|0 - 服务已关闭<br><br>1 - 服务正在运行|**service** - *ntp* (见 [详情](/manual/appendix/items/service_check_details))<br>**ip** -IP地址 (默认是 127.0.0.1)<br>**port** - 端口号(默认为标准服务使用端口号)|例:<br>=> net.udp.service\[ntp,,45\] → 可用于测试 UDP 45 端口 NTP 服务的可用性。<br><br> Zabbix 3.0.0后开始支持此项, 但*ntp* 服务可用于以前版本的 net.tcp.service\[\]监控项中| |**net.udp.service.perf**\[service,<ip>,<port>\]|<|<|<| |检查UDP服务性能。|0 - 服务已关闭<br><br>seconds - 等待服务响应秒数|**service** - *ntp* (见 [详情](/manual/appendix/items/service_check_details))<br>**ip** - IP地址 (默认是127.0.0.1)<br>**port** - 端口号 (默认为标准服务使用端口号)|例:<br>=> net.udp.service.perf\[ntp\] → 可用于测试来自 NTP 服务的响应时间。<br><br>自 Zabbix 3.0.0后开始支持该项，但 *ntp* 服务可用于以前版本的net.tcp.service\[\]监控项中| |**net.udp.socket.count**\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<| |返回与参数匹配的 TCP 套接字数。|整型|**laddr** -本地IPv4/6地址或CIDR子网地址<br>**lport** -本地端口号或服务名称<br>**raddr** - 远程IPv4/6地址或CIDR子网<br>**rport** - 远程端口号或服务名称<br>**state** - 连接状态 (*established*, *unconn*)|Zabbix agent和Zabbix agent 2均在Linux上支持此项，64位 Windows在Zabbix agent 2上支持此项。<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → 检查是否有任何 UDP 套接字处于“监听”状态<br><br>从 Zabbix 6.0 开始支持此项|

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	#### New action  Delivering notifications is one of the things [actions](/manual/config/notifications/action) do in Zabbix. Therefore, to set up a notification, go to *Configuration → Actions* and click on *Create action*.\ ![](../../../assets/en/manual/quickstart/new_action.png)  All mandatory input fields are marked with a red asterisk.  In this form, enter a name for the action.  In the most simple case, if we do not add any more specific [conditions](/manual/config/notifications/action/conditions), the action will be taken upon any trigger change from 'Ok' to 'Problem'.  We still should define what the action should do - and that is done in the *Operations* tab. Click on *Add* in the Operations block, which opens a new operation form.  ![](../../../assets/en/manual/quickstart/new_operation.png)  All mandatory input fields are marked with a red asterisk.  Here, click on *Add* in the *Send to Users* block and select the user ('user') we have defined. Select 'Email' as the value of *Send only to*. When done with this, click on *Add*, and the operation should be added:  ![](../../../assets/en/manual/quickstart/operation_list.png){width="600"}  That is all for a simple action configuration, so click *Add* in the action form.
zh-cn	#### 新建动作  发送通知是Zabbix中[动作](/manual/config/notifications/action)执行的操作之一。因此，为了建立一个通知，前往*配置 → 动作*，然后点击*创建动作*。  ![](../../../assets/en/manual/quickstart/new_action.png)  所有必填字段均标有红色星号。  在这个表单中，为动作输入一个名称。  在最简单的情况下，如果我们不添加任何更具体的[条件](/manual/config/notifications/action/conditions)，动作 将在从“Ok”到“Problem”的任何触发器状态更改时被执行。  我们还需要定义这个动作具体要做什么 —— 即在 *操作*标签页中执行的操作。点击操作块中的*添加*，将会打开一个操作表单。  ![](../../../assets/en/manual/quickstart/new_operation.png)  所有必填字段均标有红色星号。  这里，在*Send to users*块中点击*添加*并选择我们之前定义的用户('user')。在*仅送到*中选择*Email*。在完成后，点击*添加*，这个操作将会被添加：  ![](../../../assets/en/manual/quickstart/operation_list.png){width="600"}  这就是一个简单的动作配置，最后点击动作表单中的*添加*。

en-us	##### New and updated items  Several new items have been added to Zabbix agent/agent 2:  -   **agent.hostmetadata** - return host metadata -   **kernel.openfiles** - return the number of open file descriptors -   **net.tcp.socket.count\[\]** - return the number of TCP sockets that     match parameters -   **net.udp.socket.count\[\]** - return the number of UDP sockets that     match parameters -   **vfs.dir.get\[\]** - return list of directory files as JSON -   **vfs.file.get\[\]** - return information about a file as JSON -   **vfs.file.owner\[\]** - return the ownership of a file -   **vfs.file.permissions\[\]** - return a 4-digit string containing     octal number with Unix permissions  Additionally:  -   **vfs.file.cksum\[\]** now supports a second `mode` parameter     (*crc32*, *md5*, *sha256*) -   **vfs.file.size\[\]** now supports a second `mode` parameter     (*bytes* or *lines*) -   **vfs.fs.discovery** and **vfs.fs.get** now return an {\#FSLABEL}     macro on Windows (with volume names)  For more details see [agent items](/manual/config/items/itemtypes/zabbix_agent).
zh-cn	##### 新的和更新的监控项  Zabbix agent/agent 2 中添加了几个新监控项：  -   **agent.hostmetadata** - 返回主机元数据 -   **kernel.openfiles** - 返回打开文件描述符的数量 -   **net.tcp.socket.count\[\]** - 返回匹配参数的 TCP 套接字数 -   **net.udp.socket.count\[\]** - 返回匹配参数的 UDP 套接字数 -   **vfs.dir.get\[\]** - 以 JSON 格式返回目录文件列表 -   **vfs.file.get\[\]** - 以 JSON 格式返回有关文件的信息 -   **vfs.file.owner\[\]** - 返回文件的所有权 -   **vfs.file.permissions\[\]** - 返回一个 4 位字符串，其中包含具有 Unix 权限的八进制数  此外：  -   **vfs.file.cksum\[\]** 支持第二个 `mode` 参数（*crc32*, *md5*, *sha256*） -   **vfs.file.size\[\]** 支持第二个mode参数（*bytes* or *lines*） -   **vfs.fs.discovery** 和 **vfs.fs.get** 在 Windows 上返回一个 {\#FSLABEL} 宏（带有卷名）  有关详细信息，请参阅[agent监控项](/manual/config/items/itemtypes/zabbix_agent)。

en-us	### New functions  
zh-cn	### Items  

en-us	#### New macros    New macros are now supported for trigger expression debugging and internal actions.   Expression debugging macros simplify the process of debugging trigger expressions:  -   {TRIGGER.EXPRESSION.EXPLAIN},     {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} - resolve to a partially     evaluated trigger or recovery expression, where only item-based     functions are applied; -   {FUNCTION.VALUE<1-9>}, {FUNCTION.RECOVERY.VALUE<1-9>} -     resolve to the results of the Nth item-based function at the time of     the event.  
zh-cn	### Positional macros no longer supported  The support for positional macros in item name ($1, $2...$9), deprecated since Zabbix 4.0, has been fully removed.  

en-us	##### New macros    New macros are now supported for trigger expression debugging and internal actions.   Expression debugging macros simplify the process of debugging trigger expressions:  -   {TRIGGER.EXPRESSION.EXPLAIN},     {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} - resolve to a partially     evaluated trigger or recovery expression, where only item-based     functions are applied; -   {FUNCTION.VALUE<1-9>}, {FUNCTION.RECOVERY.VALUE<1-9>} -     resolve to the results of the Nth item-based function at the time of     the event.
zh-cn	##### 新增宏    新增用于触发器表达式调试和内部动作的宏。  表达式调试宏简化了触发器表达式的调试过程：  -   {TRIGGER.EXPRESSION.EXPLAIN},{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} - 解析为部分评估的触发器或恢复表达式，其中仅应用基于监控项的函数； -   {FUNCTION.VALUE<1-9>}、{FUNCTION.RECOVERY.VALUE<1-9>} - 解析为事件发生时第 N 个基于监控项的函数的结果。

en-us	##### New templates  See the list of [new templates](/manual/introduction/whatsnew600#new_templates) in Zabbix 6.0.0
zh-cn	##### 新模版  详情查阅Zabbix 6.0.0中的[new templates](/manual/introduction/whatsnew600#new_templates)

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 Please be aware that after upgrading some third-party software integrations in Zabbix might be affected, if the external software is not compatible with the upgraded Zabbix version. :::
zh-cn	::: noteclassic 请注意，在升级后，如果外部软件与升级后的 Zabbix 版本不兼容，Zabbix 中的某些第三方软件集成可能会受到影响。 :::

en-us	   ::: noteimportant For SourceIP support in LDAP simple checks (e.g. `net.tcp.service[ldap]`), OpenLDAP version 2.6.1 or above is required. SourceIP is supported in LDAP simple checks since Zabbix 6.0.1. :::
zh-cn	 ·  ::: noteimportant 对于 LDAP 简单检查（例如 `net.tcp.service[ldap]`）中的 SourceIP 支持，需要 OpenLDAP 2.6.1 或更高版本。 从 Zabbix 6.0.1 开始，LDAP 简单检查支持 SourceIP。 :::

en-us	 ::: noteimportant The instructions provided on this page are designed for advanced users. Note that these instructions might need to be adjusted for your specific configuration. :::
zh-cn	::: noteimportant 此页面上提供的说明专为高级用户设计。请注意，这些说明可能需要根据您的特定配置进行调整。 :::

en-us	 ::: noteimportant When creating a maintenance period, the [time zone](/manual/web_interface/time_zone) of the user who creates it is used. However, when recurring maintenance periods (*Daily*, *Weekly*, *Monthly*) are scheduled, the time zone of the Zabbix server is used. To ensure predictable behavior of recurring maintenance periods, it is required to use a common time zone for all parts of Zabbix. :::
zh-cn	::: noteimportant 创建维护期时，使用创建它的用户的[时区](/manual/web_interface/time_zone)。但是，当定期维护期（*Daily*、*Weekly*、*Monthly*）被安排时， 使用 Zabbix 服务器的时区。为了确保重复维护周期的可预测行为，需要为 Zabbix 的所有部分使用一个公共时区。 ::::

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 installation  See [installation instructions](https://www.zabbix.com/download?zabbix=5.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [Running agent as root](https://www.zabbix.com/documentation/5.0/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.  
zh-cn	### 安装注意事项  请参考 [installation instructions](https://www.zabbix.com/download?zabbix=5.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) 中的介绍:  -   安装存储库 -   安装 server/agent/前端 -   创建初始数据库，导入初始数据 -   为Zabbix server配置数据库 -   为Zabbix前端配置PHP -   启动 server/agent 进程 -   配置 Zabbix 前端  如你希望以根用户运行 Zabbix agent，请参考 [Running agent as root](https://www.zabbix.com/documentation/5.0/manual/appendix/install/run_agent_as_root).  Zabbix网络服务进程，用于[scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled)， 需要安装 Google Chrome 浏览器。浏览器的安装包不包含，需另行手动安装。   

en-us	### Notes on installation  See [installation instructions](https://www.zabbix.com/download?zabbix=5.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.  
zh-cn	### 安装注意事项  参见不同平台下载页面的 [安装说明](https://www.zabbix.com/download?zabbix=5.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) ：  -   安装存储库 -   安装server/agent/前端 -   创建初始数据库，导入初始数据 -   为Zabbix server配置数据库 -   为Zabbix前端配置PHP  -   启动server/agent进程 -   配置Zabbix前端  如果要以根用户身份运行Zabbix agent，请参见 [Running agent as root](/manual/appendix/install/run_agent_as_root). Zabbix网络服务进程，用于 [计划报告生成(/manual/web_interface/frontend_sections/reports/scheduled)，需要Google浏览器。浏览器不包含在软件包中，必须手动单独安装。  

en-us	### Notes on installation  See [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.
zh-cn	### 安装注意事项  请参阅下载页面中每个平台的[安装说明](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)：  - · 安装存储库 - · 安装服务器/代理/前端 - · 创建初始数据库，导入初始数据 - ·为Zabbix服务器配置数据库 - · 为 Zabbix 前端配置 PHP - · 启动服务器/代理进程 - · 配置 Zabbix 前端  如果您想以 root 身份运行 Zabbix agent，请参阅 [Running agent as root](/manual/appendix/install/run_agent_as_root)。  Zabbix web服务进程，用于[计划报告生成]（/manual/web_interface/frontend_sections/reports/scheduled）， 需要谷歌浏览器。 浏览器不包含在包中，必须手动安装。

en-us	### Notes on installation  See [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [Running agent as root](/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.
zh-cn	 ### 安装注意事项  参见不同平台下载页面的[安装说明](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)：  -   安装软件源 -   安装server/agent/前端 -   创建初始数据库，导入初始数据 -   为Zabbix server配置数据库 -   为Zabbix前端配置PHP  -   启动server/agent进程 -   配置Zabbix前端  如果要以root用户身份运行Zabbix agent，请参见 [以root用户运行agent](/manual/appendix/install/run_agent_as_root)。  Zabbix web service进程用于生成[定时报表](/manual/web_interface/frontend_sections/reports/scheduled)，需要Google浏览器。在软件包中不包含浏览器，必须手动单独安装。

en-us	### Notes on installation  See the [installation instructions](https://www.zabbix.com/download?zabbix=5.0&os_distribution=debian&os_version=10_buster&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [running agent as root](/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.  
zh-cn	### 安装注意事项  请查阅 [installation instructions](https://www.zabbix.com/download?zabbix=5.0&os_distribution=debian&os_version=10_buster&db=mysql) 下载页面中的介绍：  -   安装存储库 -   安装server/agent/前端 -   创建初始数据库，导入初始数据 -   为Zabbix server配置数据库 -   为Zabbix前端配置PHP -   启动server/agent进程 -   配置 Zabbix前端  如你希望以根用户运行 Zabbix agent，请参考 [running agent as root](/manual/appendix/install/run_agent_as_root)。  Zabbix网络服务进程，用于[scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), 需要安装 Google Chrome 浏览器。浏览器的安装包不包含，需另行手动安装。

en-us	### Notes on installation  See the [installation instructions](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql) per platform in the download page for:  -   installing the repository -   installing server/agent/frontend -   creating initial database, importing initial data -   configuring database for Zabbix server -   configuring PHP for Zabbix frontend -   starting server/agent processes -   configuring Zabbix frontend  If you want to run Zabbix agent as root, see [running agent as root](/manual/appendix/install/run_agent_as_root).  Zabbix web service process, which is used for [scheduled report generation](/manual/web_interface/frontend_sections/reports/scheduled), requires Google Chrome browser. The browser is not included into packages and has to be installed manually.
zh-cn	 ### 安装注意事项  参见不同平台下载页面的[安装说明](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql) per platform in the download page for:  -   安装软件源 -   安装server/agent/前端 -   创建初始数据库，导入初始数据 -   为Zabbix server配置数据库 -   为Zabbix前端配置PHP  -   启动server/agent进程 -   配置Zabbix前端  如果要以root用户身份运行Zabbix agent，请参见 [以root用户运行agent](/manual/appendix/install/run_agent_as_root)。  Zabbix web service进程用于生成[定时报表](/manual/web_interface/frontend_sections/reports/scheduled)，需要Google浏览器。在软件包中不包含浏览器，必须手动单独安装。

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 persistent files for log\*\[\] items  
zh-cn	#### 关于持久文件的 log\*\[\] 监控项的注释

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	 ::: notetip Mostly the `maintenance.inc.php` file is located in `/conf` of Zabbix HTML document directory on the web server. However, the location of the directory may differ depending on the operating system and a web server it uses.   For example, the location for:  -  SUSE and RedHat is `/etc/zabbix/web/maintenance.inc.php`. -  Debian-based systems is `/usr/share/zabbix/conf/`.  See also [Copying PHP files](/manual/installation/install#copying-php-files).  :::  |Parameter|Details| |--|--------| |**ZBX\_DENY\_GUI\_ACCESS**|Enable maintenance mode:<br>1 – maintenance mode is enabled, disabled otherwise| |**ZBX\_GUI\_ACCESS\_IP\_RANGE**|Array of IP addresses, which are allowed to connect to frontend (optional).<br>For example:<br>`array('192.168.1.1', '192.168.1.2')`| |**ZBX\_GUI\_ACCESS\_MESSAGE**|A message you can enter to inform users about the maintenance (optional).|
zh-cn	   ::: notetip  大多数情况下，“maintenance.inc.php”文件位于 Web 服务器上 Zabbix HTML 文档目录的“/conf”中。 但是，目录的位置可能因操作系统和它使用的 Web 服务器而异。  例如，位置：  - · SUSE and RedHat is `/etc/zabbix/web/maintenance.inc.php`. - · Debian-based systems is `/usr/share/zabbix/conf/`.  可以参见[Copying PHP files](/manual/installation/install#copying-php-files).   |参数|详情| |---------|--------| |**ZBX\_DENY\_GUI\_ACCESS**|启用维护模式：<br>1 – 启用维护模式，否则禁用| |**ZBX\_GUI\_ACCESS\_IP\_RANGE**|IP地址数组，允许连接到前端（可选）。<br>例如：<br>`array('192.168.1.1', ' 192.168.1.2')`| |**ZBX\_GUI\_ACCESS\_MESSAGE**|您可以输入一条消息来通知用户有关维护的信息（可选）。|

en-us	##### Notification about canceled escalations  When configuring [action operations](/manual/config/notifications/action/operation#configuring-an-operation), it is now possible to cancel notifications about canceled escalations by unmarking the checkbox of the corresponding option.
zh-cn	##### 关于取消升级的通知  在配置 [动作操作](/manual/config/notifications/action/operation#configuring-an-operation)时，可以通过取消选中相应选项的复选框来取消有关取消升级的通知。