en-us	#### Action filter condition  The action filter condition object defines a specific condition that must be checked before running the action operations.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |conditionid|string|*(readonly)* ID of the action condition.| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values for trigger actions:<br>0 - host group;<br>1 - host;<br>2 - trigger;<br>3 - trigger name;<br>4 - trigger severity;<br>6 - time period;<br>13 - host template;<br>16 - problem is suppressed;<br>25 - event tag;<br>26 - event tag value.<br><br>Possible values for discovery actions:<br>7 - host IP;<br>8 - discovered service type;<br>9 - discovered service port;<br>10 - discovery status;<br>11 - uptime or downtime duration;<br>12 - received value;<br>18 - discovery rule;<br>19 - discovery check;<br>20 - proxy;<br>21 - discovery object.<br><br>Possible values for autoregistration actions:<br>20 - proxy;<br>22 - host name;<br>24 - host metadata.<br><br>Possible values for internal actions:<br>0 - host group;<br>1 - host;<br>13 - host template;<br>23 - event type;<br>25 - event tag;<br>26 - event tag value.<br><br>Possible values for service actions:<br>25 - event tag;<br>26 - event tag value;<br>27 - service;<br>28 - service name.| |**value**<br>(required)|string|Value to compare with.| |value2<br>|string|Secondary value to compare with. Required for trigger actions when condition type is *26*.| |actionid|string|*(readonly)* ID of the action that the condition belongs to.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* equals;<br>1 - does not equal;<br>2 - contains;<br>3 - does not contain;<br>4 - in;<br>5 - is greater than or equals;<br>6 - is less than or equals;<br>7 - not in;<br>8 - matches;<br>9 - does not match;<br>10 - Yes;<br>11 - No.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [action.get](get#retrieve_discovery_actions) and [action.create](create#using_a_custom_expression_filter) method pages. :::  The following operators and values are supported for each condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |0|Host group|equals,<br>does not equal|Host group ID.| |1|Host|equals,<br>does not equal|Host ID.| |2|Trigger|equals,<br>does not equal|Trigger ID.| |3|Trigger name|contains,<br>does not contain|Trigger name.| |4|Trigger severity|equals,<br>does not equal,<br>is greater than or equals,<br>is less than or equals|Trigger severity. Refer to the [trigger "severity" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.| |5|Trigger value|equals|Trigger value. Refer to the [trigger "value" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger values.| |6|Time period|in, not in|Time when the event was triggered as a [time period](/manual/appendix/time_period).| |7|Host IP|equals,<br>does not equal|One or several IP ranges to check separated by commas. Refer to the [network discovery configuration](/manual/discovery/network_discovery/rule) section for more information on supported formats of IP ranges.| |8|Discovered service type|equals,<br>does not equal|Type of discovered service. The type of service matches the type of the discovery check used to detect the service. Refer to the [discovery check "type" property](/manual/api/reference/dcheck/object#discovery_check) for a list of supported types.| |9|Discovered service port|equals,<br>does not equal|One or several port ranges separated by commas.| |10|Discovery status|equals|Status of a discovered object.<br><br>Possible values:<br>0 - host or service up;<br>1 - host or service down;<br>2 - host or service discovered;<br>3 - host or service lost.| |11|Uptime or downtime duration|is greater than or equals,<br>is less than or equals|Time indicating how long has the discovered object been in the current status in seconds.| |12|Received values|equals,<br>does not equal,<br>is greater than or equals,<br>is less than or equals,<br>contains,<br>does not contain|Value returned when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.| |13|Host template|equals,<br>does not equal|Linked template ID.| |16|Problem is suppressed|Yes, No|No value required: using the "Yes" operator means that problem must be suppressed, "No" - not suppressed.| |18|Discovery rule|equals,<br>does not equal|ID of the discovery rule.| |19|Discovery check|equals,<br>does not equal|ID of the discovery check.| |20|Proxy|equals,<br>does not equal|ID of the proxy.| |21|Discovery object|equals|Type of object that triggered the discovery event.<br><br>Possible values:<br>1 - discovered host;<br>2 - discovered service.| |22|Host name|contains,<br>does not contain,<br>matches,<br>does not match|Host name.<br>Using a regular expression is supported for operators *matches* and *does not match* in autoregistration conditions.| |23|Event type|equals|Specific internal event.<br><br>Possible values:<br>0 - item in "not supported" state;<br>1 - item in "normal" state;<br>2 - LLD rule in "not supported" state;<br>3 - LLD rule in "normal" state;<br>4 - trigger in "unknown" state;<br>5 - trigger in "normal" state.| |24|Host metadata|contains,<br>does not contain,<br>matches,<br>does not match|Metadata of the auto-registered host.<br>Using a regular expression is supported for operators *matches* and *does not match*.| |25|Tag|equals,<br>does not equal,<br>contains,<br>does not contain|Event tag.| |26|Tag value|equals,<br>does not equal,<br>contains,<br>does not contain|Event tag value.| |27|Service|equals,<br>does not equal|Service ID.| |28|Service name|equals,<br>does not equal|Service name.|  
zh-cn	### Action filter  The action filter object defines a set of conditions that must be met to perform the configured action operations. It has the following properties.  |Property|Type|Description| |--------|----|-----------| |**conditions**<br>(required)|array|Set of filter conditions to use for filtering results.| |**evaltype**<br>(required)|integer|Filter condition evaluation method.<br><br>Possible values:<br>0 - and/or;<br>1 - and;<br>2 - or;<br>3 - custom expression.| |eval\_formula|string|*(readonly)* Generated expression that will be used for evaluating filter conditions. The expression contains IDs that reference specific filter conditions by its `formulaid`. The value of `eval_formula` is equal to the value of `formula` for filters with a custom expression.| |formula|string|User-defined expression to be used for evaluating conditions of filters with a custom expression. The expression must contain IDs that reference specific filter conditions by its `formulaid`. The IDs used in the expression must exactly match the ones defined in the filter conditions: no condition can remain unused or omitted.<br><br>Required for custom expression filters.|  #### Action filter condition  The action filter condition object defines a specific condition that must be checked before running the action operations.  |Property|Type|Description| |--------|----|-----------| |conditionid|string|*(readonly)* ID of the action condition.| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values for trigger actions:<br>0 - host group;<br>1 - host;<br>2 - trigger;<br>3 - trigger name;<br>4 - trigger severity;<br>6 - time period;<br>13 - host template;<br>15 - application;<br>16 - maintenance status;<br>25 - event tag;<br>26 - event tag value.<br><br>Possible values for discovery actions:<br>7 - host IP;<br>8 - discovered service type;<br>9 - discovered service port;<br>10 - discovery status;<br>11 - uptime or downtime duration;<br>12 - received value;<br>18 - discovery rule;<br>19 - discovery check;<br>20 - proxy;<br>21 - discovery object.<br><br>Possible values for auto-registration actions:<br>20 - proxy;<br>22 - host name;<br>24 - host metadata.<br><br>Possible values for internal actions:<br>0 - host group;<br>1 - host;<br>13 - host template;<br>15 - application;<br>23 - event type.| |**value**<br>(required)|string|Value to compare with.| |value2<br>|string|Secondary value to compare with. Requried for trigger actions when condition type is *26*.| |actionid|string|*(readonly)* ID of the action that the condition belongs to.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =;<br>1 - <>;<br>2 - like;<br>3 - not like;<br>4 - in;<br>5 - >=;<br>6 - <=;<br>7 - not in.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [action.get](get#retrieve_discovery_actions) and [action.create](create#using_a_custom_expression_filter) method pages. :::  The following operators and values are supported for each condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |0|Host group|=, <>|Host group ID.| |1|Host|=, <>|Host ID.| |2|Trigger|=, <>|Trigger ID.| |3|Trigger name|like, not like|Trigger name.| |4|Trigger severity|=, <>, >=, <=|Trigger severity. Refer to the [trigger "severity" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.| |5|Trigger value|=|Trigger value. Refer to the [trigger "value" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger values.| |6|Time period|in, not in|Time when the event was triggered as a [time period](/manual/appendix/time_period).| |7|Host IP|=, <>|One or several IP ranges to check separated by commas. Refer to the [network discovery configuration](/manual/discovery/network_discovery/rule) section for more information on supported formats of IP ranges.| |8|Discovered service type|=, <>|Type of discovered service. The type of service matches the type of the discovery check used to detect the service. Refer to the [discovery check "type" property](/manual/api/reference/dcheck/object#discovery_check) for a list of supported types.| |9|Discovered service port|=, <>|One or several port ranges separated by commas.| |10|Discovery status|=|Status of a discovered object.<br><br>Possible values:<br>0 - host or service up;<br>1 - host or service down;<br>2 - host or service discovered;<br>3 - host or service lost.| |11|Uptime or downtime duration|>=, <=|Time indicating how long has the discovered object been in the current status in seconds.| |12|Received values|=, <>, >=, <=, like, not like|Value returned when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.| |13|Host template|=, <>|Linked template ID.| |15|Application|=, like, not like|Name of the application.| |16|Maintenance status|in, not in|No value required: using the "in" operator means that the host must be in maintenance, "not in" - not in maintenance.| |18|Discovery rule|=, <>|ID of the discovery rule.| |19|Discovery check|=, <>|ID of the discovery check.| |20|Proxy|=, <>|ID of the proxy.| |21|Discovery object|=|Type of object that triggered the discovery event.<br><br>Possible values:<br>1 - discovered host;<br>2 - discovered service.| |22|Host name|like, not like|Host name.| |23|Event type|=|Specific internal event.<br><br>Possible values:<br>0 - item in "not supported" state;<br>1 - item in "normal" state;<br>2 - LLD rule in "not supported" state;<br>3 - LLD rule in "normal" state;<br>4 - trigger in "unknown" state;<br>5 - trigger in "normal" state.| |24|Host metadata|like, not like|Metadata of the auto-registered host.| |25|Tag|=, <>, like, not like|Event tag.| |26|Tag value|=, <>, like, not like|Event tag value.|  The following objects are directly related to the `action` API.  ### Action  The action object has the following properties.  |Property|Type|Description| |--------|----|-----------| |actionid|string|*(readonly)* ID of the action.| |**esc\_period**<br>(required)|string|Default operation step duration. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro.| |**eventsource**<br>(required)|integer|*(constant)* Type of events that the action will handle.<br><br>Refer to the [event "source" property](/manual/api/reference/event/object#event) for a list of supported event types.| |**name**<br>(required)|string|Name of the action.| |def\_longdata|string|Problem message text.| |def\_shortdata|string|Problem message subject.| |r\_longdata|string|Recovery message text.| |r\_shortdata|string|Recovery message subject.| |ack\_longdata|string|Acknowledge operation message text.| |ack\_shortdata|string|Acknowledge operation message subject.| |status|integer|Whether the action is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |pause\_suppressed|integer|Whether to pause escalation during maintenance periods or not.<br><br>Possible values:<br>0 - Don't pause escalation;<br>1 - *(default)* Pause escalation.|  ### Action operation  The action operation object defines an operation that will be performed when an action is executed. It has the following properties.  |Property|Type|Description| |--------|----|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - remote command;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.| |actionid|string|ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing the data about the command run by the operation.<br><br>The operation command object is [described in detail below](/manual/api/reference/action/object#action_operation_command).<br><br>Required for remote command operations.| |opcommand\_grp|array|Host groups to run remote commands on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for remote command operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run remote commands on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for remote command operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.|  #### Action operation command  The operation command object contains data about the command that will be run by the operation.  |Property|Type|Description| |--------|----|-----------| |operationid|string|*(readonly)* ID of the operation.| |command|string|Command to run. Required when type IN (0,1,2,3)| |**type**<br>(required)|integer|Type of operation command.<br><br>Possible values:<br>0 - custom script;<br>1 - IPMI;<br>2 - SSH;<br>3 - Telnet;<br>4 - global script.| |authtype|integer|Authentication method used for SSH commands.<br><br>Possible values:<br>0 - password;<br>1 - public key.<br><br>Required for SSH commands.| |execute\_on|integer|Target on which the custom script operation command will be executed.<br><br>Possible values:<br>0 - Zabbix agent;<br>1 - Zabbix server;<br>2 - Zabbix server (proxy).<br><br>Required for custom script commands.| |password|string|Password used for SSH commands with password authentication and Telnet commands.| |port|string|Port number used for SSH and Telnet commands.| |privatekey|string|Name of the private key file used for SSH commands with public key authentication.<br><br>Required for SSH commands with public key authentication.| |publickey|string|Name of the public key file used for SSH commands with public key authentication.<br><br>Required for SSH commands with public key authentication.| |scriptid|string|ID of the script used for global script commands.<br><br>Required for global script commands.| |username|string|User name used for authentication.<br><br>Required for SSH and Telnet commands.|  #### Action operation message  The operation message object contains data about the message that will be sent by the operation.  |Property|Type|Description| |--------|----|-----------| |operationid|string|*(readonly)* ID of the action operation.| |default\_msg|integer|Whether to use the default action message text and subject.<br><br>Possible values:<br>0 - *(default)* use the data from the operation;<br>1 - use the data from the action.| |mediatypeid|string|ID of the media type that will be used to send the message.| |message|string|Operation message text.| |subject|string|Operation message subject.|  #### Action operation condition  The action operation condition object defines a condition that must be met to perform the current operation. It has the following properties.  |Property|Type|Description| |--------|----|-----------| |opconditionid|string|*(readonly)* ID of the action operation condition| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>14 - event acknowledged.| |**value**<br>(required)|string|Value to compare with.| |operationid|string|*(readonly)* ID of the operation.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =.|  The following operators and values are supported for each operation condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |14|Event acknowledged|=|Whether the event is acknowledged.<br><br>Possible values:<br>0 - not acknowledged;<br>1 - acknowledged.|  #### Action filter condition  The action filter condition object defines a specific condition that must be checked before running the action operations.  |Property|Type|Description| |--------|----|-----------| |conditionid|string|*(readonly)* ID of the action condition.| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values for trigger actions:<br>0 - host group;<br>1 - host;<br>2 - trigger;<br>3 - trigger name;<br>4 - trigger severity;<br>6 - time period;<br>13 - host template;<br>15 - application;<br>16 - maintenance status;<br>25 - event tag;<br>26 - event tag value.<br><br>Possible values for discovery actions:<br>7 - host IP;<br>8 - discovered service type;<br>9 - discovered service port;<br>10 - discovery status;<br>11 - uptime or downtime duration;<br>12 - received value;<br>18 - discovery rule;<br>19 - discovery check;<br>20 - proxy;<br>21 - discovery object.<br><br>Possible values for auto-registration actions:<br>20 - proxy;<br>22 - host name;<br>24 - host metadata.<br><br>Possible values for internal actions:<br>0 - host group;<br>1 - host;<br>13 - host template;<br>15 - application;<br>23 - event type.| |**value**<br>(required)|string|Value to compare with.| |value2<br>|string|Secondary value to compare with. Requried for trigger actions when condition type is *26*.| |actionid|string|*(readonly)* ID of the action that the condition belongs to.| |formulaid|string|Arbitrary unique ID that is used to reference the condition from a custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =;<br>1 - <>;<br>2 - like;<br>3 - not like;<br>4 - in;<br>5 - >=;<br>6 - <=;<br>7 - not in.|  ::: notetip To better understand how to use filters with various types of expressions, see examples on the [action.get](get#retrieve_discovery_actions) and [action.create](create#using_a_custom_expression_filter) method pages. :::  The following operators and values are supported for each condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |0|Host group|=, <>|Host group ID.| |1|Host|=, <>|Host ID.| |2|Trigger|=, <>|Trigger ID.| |3|Trigger name|like, not like|Trigger name.| |4|Trigger severity|=, <>, >=, <=|Trigger severity. Refer to the [trigger "severity" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger severities.| |5|Trigger value|=|Trigger value. Refer to the [trigger "value" property](/manual/api/reference/trigger/object#trigger) for a list of supported trigger values.| |6|Time period|in, not in|Time when the event was triggered as a [time period](/manual/appendix/time_period).| |7|Host IP|=, <>|One or several IP ranges to check separated by commas. Refer to the [network discovery configuration](/manual/discovery/network_discovery/rule) section for more information on supported formats of IP ranges.| |8|Discovered service type|=, <>|Type of discovered service. The type of service matches the type of the discovery check used to detect the service. Refer to the [discovery check "type" property](/manual/api/reference/dcheck/object#discovery_check) for a list of supported types.| |9|Discovered service port|=, <>|One or several port ranges separated by commas.| |10|Discovery status|=|Status of a discovered object.<br><br>Possible values:<br>0 - host or service up;<br>1 - host or service down;<br>2 - host or service discovered;<br>3 - host or service lost.| |11|Uptime or downtime duration|>=, <=|Time indicating how long has the discovered object been in the current status in seconds.| |12|Received values|=, <>, >=, <=, like, not like|Value returned when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.| |13|Host template|=, <>|Linked template ID.| |15|Application|=, like, not like|Name of the application.| |16|Maintenance status|in, not in|No value required: using the "in" operator means that the host must be in maintenance, "not in" - not in maintenance.| |18|Discovery rule|=, <>|ID of the discovery rule.| |19|Discovery check|=, <>|ID of the discovery check.| |20|Proxy|=, <>|ID of the proxy.| |21|Discovery object|=|Type of object that triggered the discovery event.<br><br>Possible values:<br>1 - discovered host;<br>2 - discovered service.| |22|Host name|like, not like|Host name.| |23|Event type|=|Specific internal event.<br><br>Possible values:<br>0 - item in "not supported" state;<br>1 - item in "normal" state;<br>2 - LLD rule in "not supported" state;<br>3 - LLD rule in "normal" state;<br>4 - trigger in "unknown" state;<br>5 - trigger in "normal" state.| |24|Host metadata|like, not like|Metadata of the auto-registered host.| |25|Tag|=, <>, like, not like|Event tag.| |26|Tag value|=, <>, like, not like|Event tag value.|  

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

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

en-us	##### Action for active agent autoregistration  When server receives an autoregistration request from an agent it calls an [action](/manual/config/notifications/action). An action of event source "Autoregistration" must be configured for agent autoregistration.  ::: noteclassic Setting up [network discovery](network_discovery) is not required to have active agents autoregister. :::  In the Zabbix frontend, go to *Configuration → Actions*, select *Autoregistration* as the event source and click on *Create action*:  -   In the Action tab, give your action a name -   Optionally specify     [conditions](/manual/config/notifications/action/conditions#autoregistration_actions).     You can do a substring match or regular expression match in the     conditions for host name/host metadata. If you are going to use the     "Host metadata" condition, see the next section. -   In the Operations tab, add relevant operations, such as - 'Add     host', 'Add to host group' (for example, *Discovered hosts*), 'Link     to templates', etc.  ::: notetip If the hosts that will be autoregistering are likely to be supported for active monitoring only (such as hosts that are firewalled from your Zabbix server) then you might want to create a specific template like *Template\_Linux-active* to link to. :::  Created hosts are added to the *Discovered hosts* group (by default, configurable in *Administration* → *General* → *[Other](/manual/web_interface/frontend_sections/administration/general#other_parameters)*). If you wish hosts to be added to another group, add a *Remove from host group* operation (specifying "Discovered hosts") and also add an *Add to host group* operation (specifying another host group), because a host must belong to a host group.
zh-cn	##### active agent自动注册动作   一旦收到从agent发来的自动注册请求，Zabbix server会调用[动作](/manual/config/notifications/action)。为了实现agent自动注册，必须配置 "自动注册" 这个事件源的动作。  ::: noteclassic 设置 [网络发现](network_discovery)无需active agent自动注册参与。 :::  在Zabbix界面上, 转到 *配置→ 动作*, 选择 *自动注册* 作为事件源并点击 *创建动作*:  -   在动作(Action)选项卡中, 给动作设置一个名称 -   [条件](/manual/config/notifications/action/conditions#autoregistration_actions)为可选设置。     可以对主机名称/主机元数据设置字符串匹配或正则表达式匹配。如果使用 "主机元数据"作为条件，参照下一小节。 -   在操作(Operations)选项卡中，添加相关操作，比如 - '添加主机'，'添加主机组' (比如 *发现的主机* 这个组)，'链接到模板' 等。  ::: notetip 如果待自动注册的主机只支持主动模式(active)监控(比如主机防火墙策略阻挡了Zabbix server向agent发起请求)，那么可以为主机创建这样的模板 *Template\_Linux-active*。 :::  新建的主机会添加到  *发现的主机* 组(默认可在这里配置：*管理* → *通用* → *[其它](/manual/web_interface/frontend_sections/administration/general#other_parameters)* 如果想添加主机到其它组，可以先执行一个 *从主机组中移除* 操作(指定主机组 "发现的主机")，然后再执行 *添加到主机组* 操作(指定另一个主机组)，因为一个主机必须属于一个主机组。

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

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

en-us	#### Action operation condition  The action operation condition object defines a condition that must be met to perform the current operation. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |opconditionid|string|*(readonly)* ID of the action operation condition| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>14 - event acknowledged.| |**value**<br>(required)|string|Value to compare with.| |operationid|string|*(readonly)* ID of the operation.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =.|  The following operators and values are supported for each operation condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |14|Event acknowledged|=|Whether the event is acknowledged.<br><br>Possible values:<br>0 - not acknowledged;<br>1 - acknowledged.|
zh-cn	#### 动作操作条件  动作操作条件对象定义执行当前操作时必须满足的条件。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |opconditionid|string|*（只读）* 动作操作条件 ID。| |**conditiontype**<br>（必需）|integer| 条件类型。<br><br>可用值：<br>14 - 事件确认。| |**value**<br>（必需）|string| 与之比较的值。| |operationid|string|*（只读）* 操作 ID。 | |operator|integer|条件运算符。<br><br>可用值：<br>0 - *（默认）* =。|  每个操作条件类型都支持以下运算符和值。  |条件|条件名|支持的运算|期望值| |---------|--------------|-------------------|--------------| |14|事件确认|=|事件是否被确认。<br><br>可用值：<br>0 - 未确认；<br>1 - 已确认。|

en-us	#### Action operation condition  The action operation condition object defines a condition that must be met to perform the current operation. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |opconditionid|string|*(readonly)* ID of the action operation condition| |**conditiontype**<br>(required)|integer|Type of condition.<br><br>Possible values:<br>14 - event acknowledged.| |**value**<br>(required)|string|Value to compare with.| |operationid|string|*(readonly)* ID of the operation.| |operator|integer|Condition operator.<br><br>Possible values:<br>0 - *(default)* =.|  The following operators and values are supported for each operation condition type.  |Condition|Condition name|Supported operators|Expected value| |---------|--------------|-------------------|--------------| |14|Event acknowledged|=|Whether the event is acknowledged.<br><br>Possible values:<br>0 - not acknowledged;<br>1 - acknowledged.|
zh-cn	#### 动作操作条件  动作操作条件对象定义执行当前操作时必须满足的条件。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |opconditionid|string|*（只读）* 动作操作条件 ID。| |**conditiontype**<br>（必需）|integer| 条件类型。<br><br>可用值：<br>14 - 事件确认。| |**value**<br>（必需）|string| 与之比较的值。| |operationid|string|*（只读）* 操作 ID。 | |operator|integer|条件运算符。<br><br>可用值：<br>0 - *（默认）* =。|  每个操作条件类型都支持以下运算符和值。  |条件|条件名|支持的运算|期望值| |---------|--------------|-------------------|--------------| |14|事件确认|=|事件是否被确认。<br><br>可用值：<br>0 - 未确认；<br>1 - 已确认。|

en-us	#### Action operation message  The operation message object contains data about the message that will be sent by the operation.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |default\_msg|integer|Whether to use the default action message text and subject.<br><br>Possible values:<br>0 - use the data from the operation;<br>1 - *(default)* use the data from the media type.| |mediatypeid|string|ID of the media type that will be used to send the message.| |message|string|Operation message text.| |subject|string|Operation message subject.|
zh-cn	#### 动作操作消息  操作消息对象包含有关操作将发送的消息的数据。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |default\_msg|integer|是否使用默认 action message 文本和主题。<br><br>可用值：<br>0 - 使用动作中的数据；<br>1 - *（默认）* 使用 媒介类型中的数据。| |mediatypeid|string|将用于发送消息的媒介类型 ID。| |message|string|操作消息文本。| |subject|string|操作消息主题。|

en-us	#### Action operation message  The operation message object contains data about the message that will be sent by the operation.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |default\_msg|integer|Whether to use the default action message text and subject.<br><br>Possible values:<br>0 - use the data from the operation;<br>1 - *(default)* use the data from the media type.| |mediatypeid|string|ID of the media type that will be used to send the message.| |message|string|Operation message text.| |subject|string|Operation message subject.|
zh-cn	#### 动作操作消息  操作消息对象包含有关操作将发送的消息的数据。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |default\_msg|integer|是否使用默认 action message 文本和主题。<br><br>可用值：<br>0 - 使用动作中的数据；<br>1 - *（默认）* 使用 媒介类型中的数据。| |mediatypeid|string|将用于发送消息的媒介类型 ID。| |message|string|操作消息文本。| |subject|string|操作消息主题。|

en-us	### Action operation  The action operation object defines an operation that will be performed when an action is executed. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - global script;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.<br><br>Note that only types '0' and '1' are supported for trigger actions, only '0' is supported for internal actions. All types are supported for discovery and autoregistration actions.| |actionid|string|ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing data on global script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.|  
zh-cn	### 动作操作  动作操作对象定义执行动作时执行的操作。它具有以下属性。  |属性                 类|描述|<| |--------------------------|------|-| |operationid|string|*(readonly)* 动作操作的 ID。| |**operationtype**<br>(required)|integer|操作类型<br><br>可能的值：<br>0 - 发送消息;<br>1 - 远程命令;<br>2 - 添加主机;<br>3 - 删除主机;<br>4 - 添加到主机组;<br>5 - 从主机组删除;<br>6 - 链接到模板;<br>7 - 取消与模板的关联;<br>8 - 启用主机;<br>9 - 禁用主机;<br>10 - 设置主机库存模式。| |actionid|string|操作所属的动作的 ID。| |esc\_period|string|以秒为单位的升级步骤的持续时间。必须大于 60 秒。接受秒，时间单位后缀和用户宏。如果设置为 0 或0s，则将使用默认的动作升级周期。<br><br>默认: 0s.| |esc\_step\_from|integer|步骤开始升级。<br><br>默认: 1.| |esc\_step\_to|integer|步骤结束升级。<br><br>默认: 1.| |evaltype|integer|运行状态计算方法。<br><br>可能的值:<br>0 - *(默认)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|包含操作所运行的命令的数据。<br><br>操作命令对象是 [described in detail below](/zh/manual/api/reference/action/object#action_operation_command).<br><br>远程命令操作所需的。| |opcommand\_grp|array|运行远程命令的主机组。<br><br>每个对象具有以下属性：<br>`opcommand_grpid` - *(string, readonly)* 对象的 ID;<br>`operationid` - *(string)* 操作 ID；<br>`groupid` - *(string)* 主机组的 ID。<br><br>如果没有设置 `opcommand_hst`，则需要远程命令操作。| |opcommand\_hst|array|主机上运行远程命令。<br><br>每个对象具有以下属性：<br>`opcommand_hstid` - *(string, readonly)* 对象的 ID;<br>`operationid` - *(string)* 操作 ID;<br>`hostid` - *(string)* 主机 ID; 如果设置为 0，则命令将在当前主机上运行。<br><br>如果没有设置 `opcommand_grp`，则需要远程命令操作。| |opconditions|array|用于触发动作的操作条件<br><br>操作条件对象是 [下面详细描述](/zh/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|用于添加主机的主机组。<br><br>每个对象都具有以下属性:<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* 主机组的 ID。<br><br>`添加到主机组` 和 `从主机组中删除` 操作所必需的。| |opmessage|object|包含有关操作发送的消息的数据的对象。<br><br>操作消息对象是 [下面详细描述](/zh/manual/api/reference/action/object#action_operation_message).<br><br>消息操作必需。| |opmessage\_grp|array|要发送消息的用户组。<br><br>每个对象都具有以下属性：<br>`operationid` - *(string)* 操作 ID;<br>`usrgrpid` - *(string)* 用户组的ID。<br><br>如果未设置 `opmessage_usr`，则消息操作必需。| |opmessage\_usr|array|发送消息给的用户。<br><br>每个对象都具有以下属性：<br>`operationid` - *(string)* 操作 ID;<br>`userid` - *(string)* 用户的ID。<br><br>如果未设置 `opmessage_grp`，则消息操作必需。| |optemplate|array|用于将主机链接到的模板。<br><br>每个对象都具有以下属性：<br>`operationid` - *(string)* 操作 ID;<br>`templateid` - *(string)* 模板 ID.<br><br>必须有 "link to template" 和 "unlink from template" 操作| |opinventory|object|库存模式设置主机。<br><br>每个对象都具有以下属性:<br>`operationid` - *(string)* 操作 ID;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>需要有 "Set host inventory mode" 操作。|  

en-us	### Action operation  The action operation object defines an operation that will be performed when an action is executed. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - global script;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.<br><br>Note that only types '0' and '1' are supported for trigger and service actions, only '0' is supported for internal actions. All types are supported for discovery and autoregistration actions.| |actionid|string|*(readonly)* ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing data on global script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.|
zh-cn	### 动作操作  动作操作对象定义执行动作时执行的操作。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |operationid|string|*（只读）*动作操作的 ID。| |**operationtype**<br>（必需）|integer|操作类型。<br><br>可用值：<br>0 - 发送信息；<br>1 - 全局脚本；<br>2 - 添加主机；<br>3 - 删除主机；<br>4 -添加到主机组；<br>5 - 从主机组删除；<br>6 - 链接到模板；<br>7 - 取消与模板的关联；<br>8 - 启用主机；<br>9 - 禁用主机；<br>10 -设置主机资产模式。<br><br>请注意，触发器和服务动作只支持类型 '0' 和 '1' ，内部动作只支持类型 '0'。 发现和自动注册操作支持所有类型。| |actionid|string|*（只读）* 动作操作所属的动作 ID。| |esc\_period|string|以秒为单位的升级步骤的持续时间。必须大于 60 秒。接受秒、带后缀的时间单位和用户宏。如果设置为 0 或0s，则将使用默认的 动作 升级周期。<br><br>默认： 0s。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |esc\_step\_from|integer|开始升级的 Step 。<br><br>默认：1。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |esc\_step\_to|integer|结束升级的 Step。<br><br>默认：1。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |evaltype|integer| 操作条件计算方法。<br><br>可用值：<br>0 - *（默认）* AND / OR；<br>1 - AND；<br>2 - OR。| |opcommand|object|对象包含操作运行的全局脚本上的数据。<br><br>每个对象具有以下属性：`scriptid` - *（字符串）* 脚本的 ID。<br><br>被全局脚本操作所需要。| |opcommand\_grp|array|要在其上运行全局脚本的主机组。<br><br>每个对象具有以下属性：<br>`opcommand_grpid` - *（字符串，只读）* 对象 ID；<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`groupid` - *（字符串）* 主机组 ID。<br><br>在 `opcommand_hst` 未被设置的情况下，被全局脚本操作所需要。| |opcommand\_hst|array|要在其上运行全局脚本的主机。<br><br>每个对象具有以下属性：<br>`opcommand_hstid` - *（字符串，只读）* 对象 ID；<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`hostid` - *（字符串）* 主机 ID；如果设置为 0 命令将运行在当前主机。<br><br>在 `opcommand_grp`未被设置的情况下，被全局脚本操作所需要。 | |opconditions|array|用于触发 动作 的操作条件。<br><br>动作操作条件 [ 如下所述 ](/manual/api/reference/action/object#动作操作条件)。| |opgroup|array|用于添加主机的主机组。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID ；<br>`groupid` - *（字符串）* 主机组 ID 。<br><br>被 "添加到主机组" 和 "从主机组删除" 操作所需要。| |opmessage|object|包含有关操作发送的消息的数据的对象。<br><br> 动作操作消息 对象 [ 如下所述 ](/manual/api/reference/action/object#动作操作消息)。<br><br> 被消息操作所需要。| |opmessage\_grp|array| 要向其发送消息的用户组。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`usrgrpid` - *（字符串）* 用户组 ID。<br><br>在 `opmessage_usr` 未被设置的情况下，被全局脚本操作所需要。| |opmessage\_usr|array|要向其发送消息的用户。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串）* 操作 ID；<br>`userid` - *（字符串）* 用户 ID。<br><br>在 `opmessage_grp` 未被设置的情况下，被全局脚本操作所需要。| |optemplate|array|要将主机链接到的模板。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`templateid` - *（字符串）* 模板 ID 。<br><br>被 "链接到模板" 和 "取消与模板的关联" 操作所需要。| |opinventory|object|要将主机设置的资产模式。<br><br>对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`inventory_mode` - *（字符串）* 资产模式。<br><br>被 "设置主机资产模式" 操作所需要。|

en-us	### Action operation  The action operation object defines an operation that will be performed when an action is executed. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values:<br>0 - send message;<br>1 - global script;<br>2 - add host;<br>3 - remove host;<br>4 - add to host group;<br>5 - remove from host group;<br>6 - link to template;<br>7 - unlink from template;<br>8 - enable host;<br>9 - disable host;<br>10 - set host inventory mode.<br><br>Note that only types '0' and '1' are supported for trigger and service actions, only '0' is supported for internal actions. All types are supported for discovery and autoregistration actions.| |actionid|string|*(readonly)* ID of the action that the operation belongs to.| |esc\_period|string|Duration of an escalation step in seconds. Must be greater than 60 seconds. Accepts seconds, time unit with suffix and user macro. If set to 0 or 0s, the default action escalation period will be used.<br><br>Default: 0s.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_from|integer|Step to start escalation from.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |esc\_step\_to|integer|Step to end escalation at.<br><br>Default: 1.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |evaltype|integer|Operation condition evaluation method.<br><br>Possible values:<br>0 - *(default)* AND / OR;<br>1 - AND;<br>2 - OR.| |opcommand|object|Object containing data on global script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string, readonly)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opconditions|array|Operation conditions used for trigger actions.<br><br>The operation condition object is [described in detail below](/manual/api/reference/action/object#action_operation_condition).| |opgroup|array|Host groups to add hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for "add to host group" and "remove from host group" operations.| |opmessage|object|Object containing the data about the message sent by the operation.<br><br>The operation message object is [described in detail below](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.| |optemplate|array|Templates to link the hosts to.<br><br>Each object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`templateid` - *(string)* ID of the template.<br><br>Required for "link to template" and "unlink from template" operations.| |opinventory|object|Inventory mode set host to.<br><br>Object has the following properties:<br>`operationid` - *(string, readonly)* ID of the operation;<br>`inventory_mode` - *(string)* Inventory mode.<br><br>Required for "Set host inventory mode" operations.|
zh-cn	### 动作操作  动作操作对象定义执行动作时执行的操作。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |operationid|string|*（只读）*动作操作的 ID。| |**operationtype**<br>（必需）|integer|操作类型。<br><br>可用值：<br>0 - 发送信息；<br>1 - 全局脚本；<br>2 - 添加主机；<br>3 - 删除主机；<br>4 -添加到主机组；<br>5 - 从主机组删除；<br>6 - 链接到模板；<br>7 - 取消与模板的关联；<br>8 - 启用主机；<br>9 - 禁用主机；<br>10 -设置主机资产模式。<br><br>请注意，触发器和服务动作只支持类型 '0' 和 '1' ，内部动作只支持类型 '0'。 发现和自动注册操作支持所有类型。| |actionid|string|*（只读）* 动作操作所属的动作 ID。| |esc\_period|string|以秒为单位的升级步骤的持续时间。必须大于 60 秒。接受秒、带后缀的时间单位和用户宏。如果设置为 0 或0s，则将使用默认的 动作 升级周期。<br><br>默认： 0s。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |esc\_step\_from|integer|开始升级的 Step 。<br><br>默认：1。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |esc\_step\_to|integer|结束升级的 Step。<br><br>默认：1。<br><br>请注意，仅触发器、内部和服务操作支持升级，问题恢复和更新操作不支持升级。| |evaltype|integer| 操作条件计算方法。<br><br>可用值：<br>0 - *（默认）* AND / OR；<br>1 - AND；<br>2 - OR。| |opcommand|object|对象包含操作运行的全局脚本上的数据。<br><br>每个对象具有以下属性：`scriptid` - *（字符串）* 脚本的 ID。<br><br>被全局脚本操作所需要。| |opcommand\_grp|array|要在其上运行全局脚本的主机组。<br><br>每个对象具有以下属性：<br>`opcommand_grpid` - *（字符串，只读）* 对象 ID；<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`groupid` - *（字符串）* 主机组 ID。<br><br>在 `opcommand_hst` 未被设置的情况下，被全局脚本操作所需要。| |opcommand\_hst|array|要在其上运行全局脚本的主机。<br><br>每个对象具有以下属性：<br>`opcommand_hstid` - *（字符串，只读）* 对象 ID；<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`hostid` - *（字符串）* 主机 ID；如果设置为 0 命令将运行在当前主机。<br><br>在 `opcommand_grp`未被设置的情况下，被全局脚本操作所需要。 | |opconditions|array|用于触发 动作 的操作条件。<br><br>动作操作条件 [ 如下所述 ](/manual/api/reference/action/object#动作操作条件)。| |opgroup|array|用于添加主机的主机组。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID ；<br>`groupid` - *（字符串）* 主机组 ID 。<br><br>被 "添加到主机组" 和 "从主机组删除" 操作所需要。| |opmessage|object|包含有关操作发送的消息的数据的对象。<br><br> 动作操作消息 对象 [ 如下所述 ](/manual/api/reference/action/object#动作操作消息)。<br><br> 被消息操作所需要。| |opmessage\_grp|array| 要向其发送消息的用户组。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`usrgrpid` - *（字符串）* 用户组 ID。<br><br>在 `opmessage_usr` 未被设置的情况下，被全局脚本操作所需要。| |opmessage\_usr|array|要向其发送消息的用户。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串）* 操作 ID；<br>`userid` - *（字符串）* 用户 ID。<br><br>在 `opmessage_grp` 未被设置的情况下，被全局脚本操作所需要。| |optemplate|array|要将主机链接到的模板。<br><br>每个对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`templateid` - *（字符串）* 模板 ID 。<br><br>被 "链接到模板" 和 "取消与模板的关联" 操作所需要。| |opinventory|object|要将主机设置的资产模式。<br><br>对象具有以下属性：<br>`operationid` - *（字符串，只读）* 操作 ID；<br>`inventory_mode` - *（字符串）* 资产模式。<br><br>被 "设置主机资产模式" 操作所需要。|

en-us	### Action recovery operation  The action recovery operation object defines an operation that will be performed when a problem is resolved. Recovery operations are possible for trigger actions and internal actions. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger actions:<br>0 - send message;<br>1 - global script;<br>11 - notify all involved.<br><br>Possible values for internal actions:<br>0 - send message;<br>11 - notify all involved.| |actionid|string|ID of the action that the recovery operation belongs to.| |opcommand|object|Object containnig data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the recovery operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.|  
zh-cn	#### 动作操作条件  动作操作条件对象定义了一个必须满足的条件来执行当前操作。它具有以下属性。  |属性                 类|说明|<| |--------------------------|------|-| |opconditionid|string|*(readonly)* 动作操作条件的 ID| |**conditiontype**<br>(required)|integer|条件的类型。<br><br>可能的值:<br>14 - event acknowledged.| |**value**<br>(required)|string|与之比较的值。| |operationid|string|*(readonly)* 动作操作的 ID| |operator|integer|条件运算符<br><br>可能的值：<br>0 - *(default)* =.|  每个操作条件类型都支持以下运算符和值。  |条件   条|名称             支持的运算|期望值|<| |------------|----------------------------------|---------|-| |14|Event acknowledged|=|件是否被确认。<br><br>可能的值:<br>0 - 没有确认;<br>1 - 已确认。|  

en-us	#### Actions and alerts  Define actions and operations to notify users about certain events or automatically execute remote commands. Gain access to information about generated alerts and their receivers.  [Action API](/manual/api/reference/action) | [Alert API](/manual/api/reference/alert)
zh-cn	#### 动作和警报  定义动作和报警，以通知用户某些事件或自动执行远程命令。获取有关生成的警报及其接收者的信息。  [Action API](/manual/api/reference/action) | [Alert API](/manual/api/reference/alert)

en-us	#### Actions disabled due to deleted objects  If a certain object (host, template, trigger, etc.) used in an action condition/operation is deleted, the condition/operation is removed and the action is disabled to avoid incorrect execution of the action. The action can be re-enabled by the user.  This behavior takes place when deleting:  -   host groups ("host group" condition, "remote command" operation on a     specific host group); -   hosts ("host" condition, "remote command" operation on a specific     host); -   templates ("template" condition, "link to template" and "unlink from     template" operations); -   triggers ("trigger" condition); -   discovery rules (when using "discovery rule" and "discovery check"     conditions).  *Note*: If a remote command has many target hosts, and we delete one of them, only this host will be removed from the target list, the operation itself will remain. But, if it's the only host, the operation will be removed, too. The same goes for "link to template" and "unlink from template" operations.  Actions are not disabled when deleting a user or user group used in a "send message" operation.
zh-cn	 #### 由于对象被删除导致动作被禁用的情况  如果在动作条件/操作中使用的某个对象（主机，模板，触发器等）被删除了，那么对应的条件/操作也会被删除，并且该动作将被禁用，以避免错误地执行该动作。用户可以重新启用动作。  当删除以下对象时会发生这种情况：  -   主机组（“主机组”条件，特定主机组上的“远程命令”操作将被删除）； -   主机（“主机”条件，特定主机上的“远程命令”操作将被删除）； -   模板（“模板”条件，“链接到模板”和“从模板中取消链接”操作将被删除）； -   触发器（“触发器”条件将被删除）； -   自动发现规则（使用“自动发现规则”和“自动发现检查”条件时将被删除）。  *注意*: 如果远程命令有多个目标主机，我们删除了其中的一个，那么只有该主机将从目标列表中删除，操作本身将保留。但是，如果它是唯一的主机，那么操作也将被删除。"链接到模板"和"从模板取消链接"的操作也是一样。  当删除"发送消息"操作中使用的用户或用户组时，动作不会被禁用。

en-us	#### Actions  Discovery events can be the basis of relevant [actions](/manual/config/notifications/action), such as:  -   Sending notifications -   Adding/removing hosts -   Enabling/disabling hosts -   Adding hosts to a group -   Removing hosts from a group -   Linking hosts to/unlinking from a template -   Executing remote scripts  These actions can be configured with respect to the device type, IP, status, uptime/downtime, etc. For full details on configuring actions for network-discovery based events, see action [operation](/manual/config/notifications/action/operation) and [conditions](/manual/config/notifications/action/conditions) pages.  ::: noteclassic Linking a discovered host to templates will fail collectively if any of the linkable templates has a unique entity (e.g. item key) that is the same as a unique entity (e.g. item key) already existing on the host or on another of the linkable templates. :::
zh-cn	#### 动作  发现事件可触发相关[动作](/manual/config/notifications/action)，例如：  -   发送通知 -   添加/删除主机 -   启用/禁用主机 -   添加主机到组 -   从组中移除主机 -   链接/取消链接主机到模板 -   执行远程脚本  这些动作可基于设备类型、IP、状态、运行时长(uptime)/停机时长(downtime)等条件来配置。欲了解如何配置这些动作，参阅动作的[操作](/manual/config/notifications/action/operation) 和[条件](/manual/config/notifications/action/conditions) 页面获取完整细节。  ::: noteclassic 通过网络发现添加的主机，如果其链接的模板中有一个唯一属性(如监控项的键)与该主机上的唯一属性相同，或与该模板链接的其它主机上的唯一属性相同，则这台主机上的所有模板均会链接失败。 :::

en-us	#### Actions if communication fails between agent and server  Each matching line from `log[]` and `logrt[]` item and a result of each `log.count[]` and `logrt.count[]` item check requires a free slot in the designated 50% area in the agent send buffer. The buffer elements are regularly sent to server (or proxy) and the buffer slots are free again.  While there are free slots in the designated log area in the agent send buffer and communication fails between agent and server (or proxy) the log monitoring results are accumulated in the send buffer. This helps to mitigate short communication failures.  During longer communication failures all log slots get occupied and the following actions are taken:  -   `log[]` and `logrt[]` item checks are stopped. When communication is     restored and free slots in the buffer are available the checks are     resumed from the previous position. No matching lines are lost, they     are just reported later. -   `log.count[]` and `logrt.count[]` checks are stopped if     `maxdelay = 0` (default). Behavior is similar to `log[]` and     `logrt[]` items as described above. Note that this can affect     `log.count[]` and `logrt.count[]` results: for example, one check     counts 100 matching lines in a log file, but as there are no free     slots in the buffer the check is stopped. When communication is     restored the agent counts the same 100 matching lines and also 70     new matching lines. The agent now sends count = 170 as if they were     found in one check. -   `log.count[]` and `logrt.count[]` checks with `maxdelay > 0`: if     there was no "jump" during the check, then behavior is similar to     described above. If a "jump" over log file lines took place then the     position after "jump" is kept and the counted result is discarded.     So, the agent tries to keep up with a growing log file even in case     of communication failure.
zh-cn	#### 代理和服务器之间通信失败时的操作  来自`log[]`和`logrt[]`监控项的每个匹配行以及每个`log.count[]` 和 `logrt.count[]`监控项检查的结果都需要代理发送缓冲区中指定的50％区域中的空闲时隙。缓冲区元素定期发送到服务器（或代理服务器），缓冲区可以再次释放。  虽然代理发送缓冲区中的指定日志区域中有空闲时隙，并且代理和服务器（或代理服务器）之间的通信失败，但是日志监控结果在发送缓冲区中累积。这有助于缓解短暂的通信故障。  在较长的通信失败期间，所有日志槽都被占用，并采取以下操作：  -   `log[]`和`logrt[]`监控项检查已停止。当通信恢复并且缓冲器中的空闲插槽可用时，从先前的位置恢复检查。若没有匹配的行丢失，稍后再报告. -   如果`maxdelay = 0`（默认），则`log.count[]`和`logrt.count[]`监控被停止。     这种行为类似于上述的`log[]` 和`logrt[]`监控项。     请注意，这可能会影响`log.count[]`]和`logrt.count[]`结果：例如，一次检查计算出日志文件中有100个匹配行，但是由于缓冲区中没有空闲插槽，因此停止检查。     当通信恢复时，代理将计数相同的100条匹配行，还有70条新的匹配行。代理会发送count=170，就像它们在一次检查中发现的一样。 -    `log.count[]` 和`logrt.count[]`]检查与`maxdelay > 0`：如果在检查期间没有“跳转”，则行为类似于上述。     如果在日志文件行上发生“跳转”，则保留“跳转”之后的位置，同时计算结果被丢弃。     因此，即使在通信失败的情况下，代理也试图跟上日志文件的增长速度。

en-us	#### Actions  In [actions](/manual/config/notifications/action), user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Trigger-based notifications and commands|<|yes| |Trigger-based internal notifications|<|yes| |Problem update notifications|<|yes| |Service-based notifications and commands|<|yes| |Service update notifications|<|yes| |Time period condition|<|no| |*Operations*|<|<| | |Default operation step duration|no| |^|Step duration|no|
zh-cn	#### 动作  在 [动作](/manual/config/notifications/action)中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |基于触发器的通知和命令|<|支持| |基于触发器的内部通知|<|支持| |问题更新通知|<|支持| |基于服务的通知和命令|<|支持| |服务更新通知|<|支持| |时间段条件|<|不支持| |*操作*|<|<| | |默认操作步骤持续时间|不支持| |^|步骤持续时间|不支持|

en-us	### Action  The action object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |actionid|string|*(readonly)* ID of the action.| |**esc\_period**<br>(required)|string|Default operation step duration. Must be at least 60 seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Note that escalations are supported only for trigger and internal actions. In trigger actions, escalations are not supported in problem recovery and update operations.| |**eventsource**<br>(required)|integer|*(constant)* Type of events that the action will handle.<br><br>Refer to the [event "source" property](/manual/api/reference/event/object#event) for a list of supported event types.| |**name**<br>(required)|string|Name of the action.| |status|integer|Whether the action is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |pause\_suppressed|integer|Whether to pause escalation during maintenance periods or not.<br><br>Possible values:<br>0 - Don't pause escalation;<br>1 - *(default)* Pause escalation.<br><br>Note that this parameter is valid for trigger actions only.| |notify\_if\_canceled|integer|Whether to notify when escalation is canceled.<br><br>Possible values:<br>0 - Don't notify when escalation is canceled;<br>1 - *(default)* Notify when escalation is canceled.<br><br>Note that this parameter is valid for trigger actions only.|  
zh-cn	### 动作  动作对象具有以下属性。  |属性                类|描述|<| |-------------------------|------|-| |actionid|string|*(readonly)* 动作的 ID。| |**esc\_period**<br>(required)|string|默认操作步骤持续时间。必须大于 60 秒。接受秒，带后缀的时间单位和用户宏。| |**eventsource**<br>(required)|integer|*(constant)* 动作将处理的事件的类型。<br><br>参见 [event "source" property](/zh/manual/api/reference/event/object#event) 以获取支持的事件类型列表。| |**name**<br>(required)|string|动作的名称。| |def\_longdata|string|异常消息文本。| |def\_shortdata|string|异常消息主题。| |r\_longdata|string|恢复消息文本。| |r\_shortdata|string|恢复消息主题。| |ack\_longdata|string|确认操作消息文本。| |ack\_shortdata|string|确认操作消息主题。| |status|integer|动作是启动还是禁用。<br><br>取值：<br>0 - *(默认)* 启用；<br>1 - 禁用。| |pause\_suppressed|integer|是否在维护期间暂停升级。<br><br>可能的值：<br>0 - 不要暂停升级;<br>1 - *(默认)* 暂停升级。|  

en-us	### Action  The action object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |actionid|string|*(readonly)* ID of the action.| |**esc\_period**<br>(required)|string|Default operation step duration. Must be at least 60 seconds. Accepts seconds, time unit with suffix and user macro.<br><br>Note that escalations are supported only for trigger, internal and service actions, and only in normal operations.| |**eventsource**<br>(required)|integer|*(constant)* Type of events that the action will handle.<br><br>Refer to the [event "source" property](/manual/api/reference/event/object#event) for a list of supported event types.| |**name**<br>(required)|string|Name of the action.| |status|integer|Whether the action is enabled or disabled.<br><br>Possible values:<br>0 - *(default)* enabled;<br>1 - disabled.| |pause\_suppressed|integer|Whether to pause escalation during maintenance periods or not.<br><br>Possible values:<br>0 - Don't pause escalation;<br>1 - *(default)* Pause escalation.<br><br>Note that this parameter is valid for trigger actions only.| |notify\_if\_canceled|integer|Whether to notify when escalation is canceled.<br><br>Possible values:<br>0 - Don't notify when escalation is canceled;<br>1 - *(default)* Notify when escalation is canceled.<br><br>Note that this parameter is valid for trigger actions only.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 动作  动作对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |actionid|字符|*（只读）* 动作 ID。| |**esc\_period**<br>（必需）|字符|默认操作步骤持续时间。必须至少为 60 秒。接受秒、带后缀的时间单位和用户宏。<br><br>请注意，仅对触发器、内部和服务动作支持升级，问题恢复和更新操作不支持升级。 | |**eventsource**<br>（必需）|整数|*（常量）* 动作将处理的事件的类型。<br><br>参见 [event "source" 属性](/manual/api/reference/event/object#事件) 以获取支持的事件类型列表。| |**name**<br>（必需）|字符| 动作名称。| |status|整数| 动作是启用还是禁用。<br><br>可用值：<br>0 - *（默认）* 启用；<br>1 - 禁用。| |pause\_suppressed|整数|是否在维护期间暂停升级。<br><br>可用值：<br>0 - 不要暂停升级；<br>1 - *（默认）* 暂停升级。<br><br>请注意，此参数仅对触发器动作有效。| |notify\_if\_canceled|整数|取消升级时是否通知。<br><br>可用值：<br>0 - 取消升级时不通知；<br>1 - *（默认）* 取消升级时通知。<br><br>请注意，此参数仅对触发器动作有效。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	### Action  The action object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**name**<br>(required)|string|Name of the action.<br><br>Possible values for users of any type:<br>`edit_dashboards` - Create and edit dashboards;<br>`edit_maps` - Create and edit maps;<br>`add_problem_comments` - Add problem comments;<br>`change_severity` - Change problem severity;<br>`acknowledge_problems` - Acknowledge problems;<br>`close_problems` - Close problems;<br>`execute_scripts` - Execute scripts;<br>`manage_api_tokens` - Manage API tokens.<br><br>Possible values only for users of *Admin* and *Super admin* user types:<br>`edit_maintenance` - Create and edit maintenances;<br>`manage_scheduled_reports` - Manage scheduled reports.| |status|integer|Whether access to perform the action is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	### 动作  动作对象拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**name**<br>(必要)|字符串|动作名称。<br><br>对所有类型用户可配置的参数包括：<br>`edit_dashboards` - 创建和编辑仪表板；<br>`edit_maps` - 创建和编辑拓扑图；<br>`add_problem_comments` - 添加问题描述；<br>`change_severity` - 修改问题级别；<br>`acknowledge_problems` - 确认问题；<br>`close_problems` - 关闭问题；<br>`execute_scripts` - 运行脚本；<br>`manage_api_tokens` - 管理API令牌。<br><br>*管理员* 和 *超级管理员* 用户类型可配置的参数包括：<br>`edit_maintenance` - 创建和编辑维护；<br>`manage_scheduled_reports` - 管理规划报告。| |status|整数|是否允许访问运行的动作信息。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *(缺省值)* 开启。|

en-us	### Action  The action object has the following properties:  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**name**<br>(required)|string|Name of the action.<br><br>Possible values for users of any type:<br>`edit_dashboards` - Create and edit dashboards;<br>`edit_maps` - Create and edit maps;<br>`add_problem_comments` - Add problem comments;<br>`change_severity` - Change problem severity;<br>`acknowledge_problems` - Acknowledge problems;<br>`close_problems` - Close problems;<br>`execute_scripts` - Execute scripts;<br>`manage_api_tokens` - Manage API tokens.<br><br>Possible values only for users of *Admin* and *Super admin* user types:<br>`edit_maintenance` - Create and edit maintenances;<br>`manage_scheduled_reports` - Manage scheduled reports.| |status|integer|Whether access to perform the action is enabled.<br><br>Possible values:<br>0 - Disabled;<br>1 - *(default)* Enabled.|
zh-cn	### 动作  动作对象拥有下列属性特征：  |属性|[类型](zh/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**name**<br>(必要)|字符串|动作名称。<br><br>对所有类型用户可配置的参数包括：<br>`edit_dashboards` - 创建和编辑仪表板；<br>`edit_maps` - 创建和编辑拓扑图；<br>`add_problem_comments` - 添加问题描述；<br>`change_severity` - 修改问题级别；<br>`acknowledge_problems` - 确认问题；<br>`close_problems` - 关闭问题；<br>`execute_scripts` - 运行脚本；<br>`manage_api_tokens` - 管理API令牌。<br><br>*管理员* 和 *超级管理员* 用户类型可配置的参数包括：<br>`edit_maintenance` - 创建和编辑维护；<br>`manage_scheduled_reports` - 管理规划报告。| |status|整数|是否允许访问运行的动作信息。<br><br>可配置的参数包括：<br>0 - 关闭；<br>1 - *(缺省值)* 开启。|

en-us	# Action  This class is designed to work with actions.  Object references:\  -   [Action](/manual/api/reference/action/object#action) -   [Action     condition](/manual/api/reference/action/object#action_condition) -   [Action     operation](/manual/api/reference/action/object#action_operation)  Available methods:\  -   [action.create](/manual/api/reference/action/create) - create new     actions -   [action.delete](/manual/api/reference/action/delete) - delete     actions -   [action.get](/manual/api/reference/action/get) - retrieve actions -   [action.update](/manual/api/reference/action/update) - update     actions
zh-cn	# 动作  这个类用于操作动作。  对象引用：\  -   [动作](/manual/api/reference/action/object#动作) -   [动作条件](/manual/api/reference/action/object#动作条件) -   [动作操作](/manual/api/reference/action/object#动作操作)  可用方法：\  -   [action.create](/manual/api/reference/action/create) - 创建新的动作 -   [action.delete](/manual/api/reference/action/delete) - 删除动作 -   [action.get](/manual/api/reference/action/get) - 获取动作 -   [action.update](/manual/api/reference/action/update) - 更新动作

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

en-us	### Action update operation  The action update operation object defines an operation that will be performed when a problem is updated (commented upon, acknowledged, severity changed, or manually closed). Update operations are possible for trigger actions. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger actions:<br>0 - send message;<br>1 - global script;<br>12 - notify all involved.| |opcommand|object|Object containing data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the update operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required only for `send message` operations if `opmessage_usr` is not set.<br>Is ignored for `send update message` operations.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`userid` - *(string)* ID of the user.<br><br>Required only for `send message` operations if `opmessage_grp` is not set.<br>Is ignored for `send update message` operations.|  
zh-cn	### Action recovery operation  The action recovery operation object defines an operation that will be performed when a problem is resolved. Recovery operations are possible for trigger actions and internal actions. It has the following properties.  |Property|Type|Description| |--------|----|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger actions:<br>0 - send message;<br>1 - remote command;<br>11 - notify all involved.<br><br>Possible values for internal actions:<br>0 - send message;<br>11 - notify all involved.| |actionid|string|ID of the action that the recovery operation belongs to.| |opcommand|object|Object containing the data about the command run by the recovery operation.<br><br>The operation command object is [described in detail above](/manual/api/reference/action/object#action_operation_command).<br><br>Required for remote command operations.| |opcommand\_grp|array|Host groups to run remote commands on.<br><br>Each object has the following properties:<br>`opcommand_grpid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`groupid` - *(string)* ID of the host group.<br><br>Required for remote command operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run remote commands on.<br><br>Each object has the following properties:<br>`opcommand_hstid` - *(string, readonly)* ID of the object;<br>`operationid` - *(string)* ID of the operation;<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for remote command operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the recovery operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).<br><br>Required for message operations.| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required for message operations if `opmessage_usr` is not set.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`operationid` - *(string)* ID of the operation;<br>`userid` - *(string)* ID of the user.<br><br>Required for message operations if `opmessage_grp` is not set.|  

en-us	### Action update operation  The action update operation object defines an operation that will be performed when a problem is updated (commented upon, acknowledged, severity changed, or manually closed). Update operations are possible for trigger and service actions. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger and service actions:<br>0 - send message;<br>1 - global script;<br>12 - notify all involved.| |opcommand|object|Object containing data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the update operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required only for `send message` operations if `opmessage_usr` is not set.<br>Is ignored for `send update message` operations.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`userid` - *(string)* ID of the user.<br><br>Required only for `send message` operations if `opmessage_grp` is not set.<br>Is ignored for `send update message` operations.|
zh-cn	### 动作更新操作  动作更新操作对象定义在问题更新（注释、确认、严重性更改或手动关闭）时将执行的操作。更新操作可用于 触发器 和 服务动作。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |operationid|string|*（只读）*动作操作 ID。| |**operationtype**<br>（必需）|integer|操作类型。<br><br>在 触发器 和 服务 动作 的情况下可能的值：<br>0 - 发送消息；<br>1 - 全局脚本；<br>12 - 通知所有相关人员。| |opcommand|object|对象包含运行的全局操作类型脚本操作的数据。<br><br>每个对象都有以下属性： `scriptid` - *（字符串）*动作类型脚本 ID。<br><br>被全局脚本操作所需要。| |opcommand\_grp|array|要在其上运行全局脚本的主机组。<br><br>每个对象都具有以下属性：<br>`groupid` - *（字符串）* 主机组 ID<br><br> 在 `opcommand_hst` 未被设置的情况下，被全局脚本操作所需要。| |opcommand\_hst|array|要在其上运行全局脚本的主机。<br><br>每个对象都具有以下属性：<br>`hostid` - *（字符串）* 主机 ID； 如果设置为 0 命令将运行在当前主机。<br><br>在 `opcommand_grp`未被设置的情况下，被全局脚本操作所需要。| |opmessage|object|对象包含有关更新操作发送的消息的数据。<br><br> 操作消息 对象 [ 如上所述 ](/manual/api/reference/action/object#动作操作消息)。| |opmessage\_grp|array| 要向其发送消息的用户组。<br><br>每个对象都具有以下属性：<br>`usrgrpid` - *（字符串）* 用户组 ID。<br><br>在 `opmessage_usr` 未被设置的情况下，仅被 `发送消息` 操作所需要。<br>被 `发送更新消息` 操作所忽略。| |opmessage\_usr|array|要向其发送消息的用户。<br><br>每个对象都具有以下属性：<br>`userid` - *（字符串）* 用户 ID。<br><br>在 `opmessage_grp`未被设置的情况下，仅被 `发送消息` 操作所需要。<br>被 `发送更新消息` 操作所忽略。|

en-us	### Action update operation  The action update operation object defines an operation that will be performed when a problem is updated (commented upon, acknowledged, severity changed, or manually closed). Update operations are possible for trigger and service actions. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |operationid|string|*(readonly)* ID of the action operation.| |**operationtype**<br>(required)|integer|Type of operation.<br><br>Possible values for trigger and service actions:<br>0 - send message;<br>1 - global script;<br>12 - notify all involved.| |opcommand|object|Object containing data on global action type script run by the operation.<br><br>Each object has one following property: `scriptid` - *(string)* ID of the action type script.<br><br>Required for global script operations.| |opcommand\_grp|array|Host groups to run global scripts on.<br><br>Each object has the following properties:<br>`groupid` - *(string)* ID of the host group.<br><br>Required for global script operations if `opcommand_hst` is not set.| |opcommand\_hst|array|Host to run global scripts on.<br><br>Each object has the following properties:<br>`hostid` - *(string)* ID of the host; if set to 0 the command will be run on the current host.<br><br>Required for global script operations if `opcommand_grp` is not set.| |opmessage|object|Object containing the data about the message sent by the update operation.<br><br>The operation message object is [described in detail above](/manual/api/reference/action/object#action_operation_message).| |opmessage\_grp|array|User groups to send messages to.<br><br>Each object has the following properties:<br>`usrgrpid` - *(string)* ID of the user group.<br><br>Required only for `send message` operations if `opmessage_usr` is not set.<br>Is ignored for `send update message` operations.| |opmessage\_usr|array|Users to send messages to.<br><br>Each object has the following properties:<br>`userid` - *(string)* ID of the user.<br><br>Required only for `send message` operations if `opmessage_grp` is not set.<br>Is ignored for `send update message` operations.|
zh-cn	### 动作更新操作  动作更新操作对象定义在问题更新（注释、确认、严重性更改或手动关闭）时将执行的操作。更新操作可用于 触发器 和 服务动作。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |operationid|string|*（只读）*动作操作 ID。| |**operationtype**<br>（必需）|integer|操作类型。<br><br>在 触发器 和 服务 动作 的情况下可能的值：<br>0 - 发送消息；<br>1 - 全局脚本；<br>12 - 通知所有相关人员。| |opcommand|object|对象包含运行的全局操作类型脚本操作的数据。<br><br>每个对象都有以下属性： `scriptid` - *（字符串）*动作类型脚本 ID。<br><br>被全局脚本操作所需要。| |opcommand\_grp|array|要在其上运行全局脚本的主机组。<br><br>每个对象都具有以下属性：<br>`groupid` - *（字符串）* 主机组 ID<br><br> 在 `opcommand_hst` 未被设置的情况下，被全局脚本操作所需要。| |opcommand\_hst|array|要在其上运行全局脚本的主机。<br><br>每个对象都具有以下属性：<br>`hostid` - *（字符串）* 主机 ID； 如果设置为 0 命令将运行在当前主机。<br><br>在 `opcommand_grp`未被设置的情况下，被全局脚本操作所需要。| |opmessage|object|对象包含有关更新操作发送的消息的数据。<br><br> 操作消息 对象 [ 如上所述 ](/manual/api/reference/action/object#动作操作消息)。| |opmessage\_grp|array| 要向其发送消息的用户组。<br><br>每个对象都具有以下属性：<br>`usrgrpid` - *（字符串）* 用户组 ID。<br><br>在 `opmessage_usr` 未被设置的情况下，仅被 `发送消息` 操作所需要。<br>被 `发送更新消息` 操作所忽略。| |opmessage\_usr|array|要向其发送消息的用户。<br><br>每个对象都具有以下属性：<br>`userid` - *（字符串）* 用户 ID。<br><br>在 `opmessage_grp`未被设置的情况下，仅被 `发送消息` 操作所需要。<br>被 `发送更新消息` 操作所忽略。|

en-us	#### Active checks  Active checks require more complex processing. The agent must first retrieve from the server(s) a list of items for independent processing.  The servers to get the active checks from are listed in the 'ServerActive' parameter of the agent [configuration file](/manual/appendix/config/zabbix_agentd). The frequency of asking for these checks is set by the 'RefreshActiveChecks' parameter in the same configuration file. However, if refreshing active checks fails, it is retried after hardcoded 60 seconds.  The agent then periodically sends the new values to the server(s).  ::: notetip If an agent is behind the firewall you might consider using only Active checks because in this case you wouldn't need to modify the firewall to allow initial incoming connections. :::
zh-cn	 #### 主动检查  主动检查需要更复杂的处理，agent 必须首先从server端检索独立处理监控项的列表。  The servers 主动检查的列表在agent [配置文件](/manual/appendix/config/zabbix_agentd)中的 'ServerActive' 参数中列出， 请求这些检查的频率是由相同配置文件中的'RefreshActiveChecks' 参数设置的。 然而，如果刷新主动检查失败，则在60秒后重试。  agent然后定期向服务器发送新值。   ::: notetip 如果代理位于防火墙后面，您可能会考虑 仅使用主动检查，因为在这种情况下您不需要 修改防火墙以允许初始传入连接。 :::

en-us	 ### Active checks request  The active checks request is used to obtain the active checks to be processed by agent. This request is sent by the agent upon start and then with *RefreshActiveChecks* inervals.  | Field | Type | Mandatory | Value | |-|-|-|--------| | request | _string_ | yes | `active checks` | | host | _string_ | yes | Host name. | | version | _string_ | yes | The agent version: \<major>.\<minor>. | | host_metadata | _string_ | no | The configuration parameter HostMetadata or HostMetadataItem metric value. | | interface | _string_ | no | The configuration parameter HostInterface or HostInterfaceItem metric value. | | ip | _string_ | no | The configuration parameter ListenIP first IP if set. | | port | _number_ | no | The configuration parameter ListenPort value if set and not default agent listening port. |  Example: ```json {   "request": "active checks",   "host": "Zabbix server",   "version": "6.0",   "host_metadata": "mysql,nginx",   "hostinterface": "zabbix.server.lan",   "ip": "159.168.1.1",   "port": 12050 } ```
zh-cn	### 主动检查请求  主动检查请求用于获取agent要处理的主动检查。 此请求由agent在启动时发送，然后以 *RefreshActiveChecks* 间隔发送。  | 字段 | 类型 | 必填 | 值 | |-|-|-|--------| | request | _字符串_ | 是 | `主动检查` | | host | _字符串_ | 是 | 主机名。 | | version | _字符串_ | 是 | agent版本：\<major>.\<minor>。 | | host_metadata | _字符串_ | 没有 | 配置参数 HostMetadata 或 HostMetadataItem 度量值。 | | interface | _字符串_ | 没有 | 配置参数 HostInterface 或 HostInterfaceItem 度量值。 | | ip | _字符串_ | 没有 | 如果设置了配置参数 ListenIP 第一个 IP。 | | port | _编号_ | 没有 | 配置参数 ListenPort 值（如果已设置）而不是默认监听端口。 |  示例: ```json {  · "request": "active checks",  · "host": "Zabbix server",  · "version": "6.0",  · "host_metadata": "mysql,nginx",  · "hostinterface": "zabbix.server.lan",  · "ip": "159.168.1.1",  · "port": 12050 } ```

en-us	#### Active proxy
zh-cn	#### 主动代理

en-us	#### Add a trigger dependency  Make trigger "14092" dependent on trigger "13565."  Request:  ```json {     "jsonrpc": "2.0",     "method": "trigger.adddependencies",     "params": {         "triggerid": "14092",         "dependsOnTriggerid": "13565"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "14092"         ]     },     "id": 1 } ```
zh-cn	#### 添加触发器依赖  使触发器“14092”依赖于触发器“13565”.  请求:  ```json {     "jsonrpc": "2.0",     "method": "trigger.adddependencies",     "params": {         "triggerid": "14092",         "dependsOnTriggerid": "13565"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "triggerids": [             "14092"         ]     },     "id": 1 } ```

en-us	#### Adding a filter to an LLD rule  Add a filter so that the contents of the *{\#FSTYPE}* macro would match the *\@File systems for discovery* regexp.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#FSTYPE}",                     "value": "@File systems for discovery"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```
zh-cn	#### LLD 规则添加过滤器  添加一个过滤器，以便 *{\#FSTYPE}* 宏的内容与 *\@File systems for discovery* 正则表达式匹配。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#FSTYPE}",                     "value": "@File systems for discovery"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```

en-us	#### Adding a filter to an LLD rule  Add a filter so that the contents of the *{\#FSTYPE}* macro would match the *\@File systems for discovery* regexp.  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#FSTYPE}",                     "value": "@File systems for discovery"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```
zh-cn	#### LLD 规则添加过滤器  添加一个过滤器，以便 *{\#FSTYPE}* 宏的内容与 *\@File systems for discovery* 正则表达式匹配。  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "filter": {             "evaltype": 1,             "conditions": [                 {                     "macro": "{#FSTYPE}",                     "value": "@File systems for discovery"                 }             ]         }     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```

en-us	#### Adding a scheduled downtime  Add a downtime for service with ID "4" scheduled weekly from Monday 22:00 till Tuesday 10:00.  Request:  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "serviceid": "4",         "times": [             {                 "type": "1",                 "ts_from": "165600",                 "ts_to": "201600"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "4"         ]     },     "id": 1 } ```
zh-cn	#### 增加关机计划  给ID为“4”的服务增加每周一22:00到周二10:00的关机计划。  请求：  ```json {     "jsonrpc": "2.0",     "method": "service.update",     "params": {         "serviceid": "4",         "times": [             {                 "type": "1",                 "ts_from": "165600",                 "ts_to": "201600"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ```json {     "jsonrpc": "2.0",     "result": {         "serviceids": [             "4"         ]     },     "id": 1 } ```

en-us	#### Adding elements  To add an element, click on *Add* next to `Map element`. The new element will appear at the top left corner of the map. Drag and drop it wherever you like.  Note that with the Grid option "On", elements will always align to the grid (you can pick various grid sizes from the dropdown, also hide/show the grid). If you want to put elements anywhere without alignment, turn the option to "Off". (Random elements can later again be aligned to the grid with the *Align map elements* button.)  Now that you have some elements in place, you may want to start differentiating them by giving names, etc. By clicking on the element, a form is displayed and you can set the element type, give a name, choose a different icon, etc.  ![](../../../../../assets/en/manual/config/visualization/map_element.png){width="600"}  Map element attributes:  |Parameter|Description| |---------|-----------| |*Type*|Type of the element:<br>**Host** - icon representing status of all triggers of the selected host<br>**Map** - icon representing status of all elements of a map<br>**Trigger** - icon representing status of one or more triggers<br>**[Host group](/manual/config/visualization/maps/host_groups)** - icon representing status of all triggers of all hosts belonging to the selected group<br>**Image** - an icon, not linked to any resource| |*Label*|Icon label, any string.<br>Macros and multi-line strings can be used.<br>Expression [macros](/manual/appendix/macros/supported_by_location) are supported in this field, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).<br>For a full list of supported macros, see [supported macros](/manual/appendix/macros/supported_by_location) and search for 'map element labels'.| |*Label location*|Label location in relation to the icon:<br>**Default** - map's default label location<br>**Bottom** - beneath the icon<br>**Left** - to the left<br>**Right** - to the right<br>**Top** - above the icon| |*Host*|Enter the host if the element type is 'Host'. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove the selected.| |*Map*|Select the map, if the element type is 'Map'.| |*Triggers*|If the element type is 'Trigger', select one or more triggers in the *New triggers* field below and click on *Add*.<br>The order of selected triggers can be changed, but only within the same severity of triggers. Multiple trigger selection also affects {HOST.\*} macro resolution both in the construction and view modes.<br>// 1 In construction mode// the first displayed {HOST.\*} macros will be resolved depending on the first trigger in the list (based on trigger severity).<br>// 2 View mode// depends on the [Display problems](/manual/config/visualization/maps/map#creating_a_map) parameter in General map attributes.<br>\* If *Expand single problem* mode is chosen the first displayed {HOST.\*} macros will be resolved depending on the latest detected problem trigger (not mattering the severity) or the first trigger in the list (in case no problem detected);<br>\* If *Number of problems and expand most critical one* mode is chosen the first displayed {HOST.\*} macros will be resolved depending on the trigger severity.<br>| |*Host group*|Enter the host group if the element type is 'Host group'. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove the selected.| |*Tags*|Specify tags to limit the number of problems displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met<br>This field is available for host and host group element types.| |*Automatic icon selection*|In this case an icon mapping will be used to determine which icon to display.| |*Icons*|You can choose to display different icons for the element in these cases: default, problem, maintenance, disabled.| |*Coordinate X*|X coordinate of the map element.| |*Coordinate Y*|Y coordinate of the map element.| |*URLs*|Element-specific URLs can be set for the element. These will be displayed as links when a user clicks on the element in the map viewing mode. If the element has its own URLs and there are map level URLs for its type defined, they will be combined in the same menu.<br>Macros can be used in map element names and values. For a full list, see [supported macros](/manual/appendix/macros/supported_by_location) and search for 'map URL names and values'.|  ::: noteimportant Added elements are not automatically saved. If you navigate away from the page, all changes may be lost.  Therefore it is a good idea to click on the **Update** button in the top right corner. Once clicked, the changes are saved regardless of what you choose in the following popup.  Selected grid options are also saved with each map. :::
zh-cn	#### 添加元素  要添加元素，请单击“地图元素”旁边的*添加*。新元素将出现在地图的左上角。拖放到任何你喜欢的地方。  请注意，使用 Grid 选项“On”，元素将始终与网格（您可以从下拉列表中选择各种网格大小，也可以隐藏/显示网格）。如果您想将元素放置在任何位置而不对齐，请转“关闭”选项。 （随机元素稍后可以再次对齐到带有*对齐地图元素*按钮的网格。）  现在你已经有了一些元素，你可能想要开始通过给出名称等来区分它们。通过单击元素显示表单，您可以设置元素类型，命名，选择不同的图标等  ![](../../../../../assets/en/manual/config/visualization/map_element.png){width="600"}  地图元素属性：  |参数|说明| |---------|------------| |*类型*|元素类型：<br>**Host** - 表示所选主机的所有触发器状态的图标<br>**Map** - 表示地图所有元素状态的图标<br> **触发器** - 表示一个或多个触发器状态的图标<br>**[主机组](/manual/config/visualization/maps/host_groups)** - 表示属于选定组<br>**图片** - 一个图标，未链接到任何资源| |*标签*|图标标签，任何字符串。<br>可以使用宏和多行字符串。<br>该字段支持表达式[宏](/manual/appendix/macros/supported_by_location)，但只能与`avg`、`last`、`min` 和 `max` 函数，以时间作为参数（例如，`{?avg(/host/key,1h)}`）。<br>查看支持的完整列表宏，请参阅 [支持的宏](/manual/appendix/macros/supported_by_location) 并搜索“地图元素标签”。| |*标签位置*|与图标相关的标签位置：<br>**默认** - 地图的默认标签位置<br>**底部** - 图标下方<br>**左** - 到左侧<br>**右侧** - 右侧<br>**顶部** - 图标上方| |*主机*|如果元素类型为“Host”，请输入主机。此字段是自动完成的，因此开始输入主机名将提供匹配主机的下拉列表。向下滚动以选择。单击“x”以删除所选内容。| |*地图*|选择地图，如果元素类型是'Map'。| |*触发器*|如果元素类型是“触发器”，请在下面的*New triggers* 字段中选择一个或多个触发器，然后单击*Add*。<br>可以更改所选触发器的顺序，但只能在触发的严重程度相同。多个触发器选择还会影响构造模式和视图模式下的 {HOST.\*} 宏分辨率。<br>// 1 在构造模式中// 第一个显示的 {HOST.\*} 宏将根据第一个触发器进行解析在列表中（基于触发严重性）。<br>// 2 查看模式// 取决于通用地图属性中的 [显示问题](/manual/config/visualization/maps/map#creating_a_map) 参数。<br> \* 如果选择 *Expand single problem* 模式，第一个显示的 {HOST.\*} 宏将根据最新检测到的问题触发器（与严重性无关）或列表中的第一个触发器（如果未检测到问题）得到解决);<br>\* 如果选择了*Number of questions and expand most critical one* 模式，第一个显示的 {HOST.\*} 宏将根据触发器的严重性得到解决。<br>| |*主机组*|如果元素类型为“主机组”，请输入主机组。此字段是自动完成的，因此开始输入组的名称将提供匹配组的下拉列表。向下滚动以选择。单击“x”以删除所选内容。| |*标签*|指定标签以限制小部件中显示的问题数量。可以包括和排除特定的标签和标签值。可以设置几个条件。标签名称匹配始终区分大小写。<br>每个条件都有多个可用的运算符：<br>**Exists** - 包括指定的标签名称<br>**Equals** - 包括指定的标签名称和值（区分大小写）<br>**包含** - 包含指定的标签名称，其中标签值包含输入的字符串（子字符串匹配，不区分大小写）<br>**不存在** - 排除指定的标签名称<br>**不等于** - 排除指定的标签名称和值（区分大小写）<br>**不包含** - 排除标签值包含输入字符串的指定标签名称（子字符串匹配，不区分大小写）<br>条件有两种计算类型：<br>**And/Or** - 必须满足所有条件，标签名相同的条件将按Or条件分组<br >**或** - 如果满足一个条件就足够了<br>此字段可用于主机和主机组元素类型。| |*自动图标选择*|在这种情况下，将使用图标映射来确定要显示的图标。| |*图标*|在这些情况下，您可以选择为元素显示不同的图标：默认、问题、维护、禁用。| |*坐标X*|地图元素的X坐标。| |*坐标Y*|地图元素的Y坐标。| |*URLs*|可以为元素设置特定于元素的 URL。当用户在地图查看模式下单击元素时，这些将显示为链接。如果元素有自己的 URL，并且定义了其类型的地图级 URL，它们将组合在同一个菜单中。<br>宏可用于地图元素名称和值。有关完整列表，请参阅 [支持的宏](/manual/appendix/macros/supported_by_location) 并搜索“映射 URL 名称和值”。|  ::: 注意重要 添加的元素不会自动保存。如果你离开页面，所有更改都可能丢失。  因此，最好单击顶部的 **Update** 按钮右上角。单击后，无论您使用什么，更改都会保存在以下弹出窗口中选择。  选定的网格选项也与每个地图一起保存。 :::

en-us	##### Adding host  Hosts are added during the discovery process, as soon as a host is discovered, rather than at the end of the discovery process.  ::: notetip As network discovery can take some time due to many unavailable hosts/services having patience and using reasonable IP ranges is advisable. :::  When adding a host, its name is decided by the standard **gethostbyname** function. If the host can be resolved, resolved name is used. If not, the IP address is used. Besides, if IPv6 address must be used for a host name, then all ":" (colons) are replaced by "\_" (underscores), since colons are not allowed in host names.  ::: noteimportant If performing discovery by a proxy, currently hostname lookup still takes place on Zabbix server. :::  ::: noteimportant If a host already exists in Zabbix configuration with the same name as a newly discovered one, versions of Zabbix prior to 1.8 would add another host with the same name. Zabbix 1.8.1 and later adds **\_N** to the hostname, where **N** is increasing number, starting with 2. :::
zh-cn	##### 添加主机  主机在发现过程中中添加，一旦发现立即添加，而非在发现过程结束后添加。  ::: notetip 网络发现会因为太多不可达的主机或服务而用时很长，请耐心等待或使用合理IP地址范围。 :::  添加主机时，其名称由标准的** gethostbyname **函数决定。如果可以解析主机，则使用解析名称。如果没有，则使用IP地址。此外，如果必须使用IPv6地址作为主机名，则所有“：”（冒号）将被替换为“\_”（下划线），因为主机名中不允许冒号。  ::: noteimportant 如果通过代理执行发现，当前主机名查找仍然发生在Zabbix服务器上。 :::  ::: noteimportant 如果一个新发现的主机与Zabbix的配置中已有的主机同名，1.8之前的版本将添加一个同名的主机。Zabbix 1.8.1及更高版本将** \_ N **添加到主机名中，** N**是从2开始递增的正整数。 :::

en-us	#### Adding host  Information about configured hosts in Zabbix is available in *Configuration → Hosts* and *Monitoring* → *Hosts*. There is already one pre-defined host, called "Zabbix server", but we want to learn adding another.  To add a new host, click on *Create host*. This will present us with a host configuration form.\ ![](../../../assets/en/manual/quickstart/new_host.png)  All mandatory input fields are marked with a red asterisk.  The bare minimum to enter here is:  ***Host name***  -   Enter a host name. Alphanumerics, spaces, dots, dashes and     underscores are allowed.  ***Groups***  -   Select one or several existing groups by clicking *Select* button or     enter a non-existing group name to create a new group.  ::: noteclassic All access permissions are assigned to host groups, not individual hosts. That is why a host must belong to at least one group. :::  ***Interfaces: IP address***  -   Although not a required field technically, you may want to enter the     IP address of the host. Note that if this is the Zabbix server IP     address, it must be specified in the Zabbix agent configuration file     'Server' directive.  [Other options](/manual/config/hosts/host#configuration) will suit us with their defaults for now.  When done, click *Add*. Your new host should be visible in the host list.  ![](../../../assets/en/manual/quickstart/host_list.png){width="600"}  The Availability column contains indicators of host availability per each interface. We have defined a Zabbix agent interface, so we can use the agent availability icon (with 'ZBX' on it) to understand host availability:  -   ![icon\_zbx\_gray.png](../../../assets/en/manual/quickstart/icon_zbx_gray.png) -     host status has not been established; no metric check has happened     yet -   ![icon\_zbx\_green.png](../../../assets/en/manual/quickstart/icon_zbx_green.png) -     host is available, a metric check has been successful -   ![icon\_zbx\_red.png](../../../assets/en/manual/quickstart/icon_zbx_red.png) -     host is unavailable, a metric check has failed (move your mouse     cursor over the icon to see the error message). There might be some     error with communication, possibly caused by incorrect interface     credentials. Check that Zabbix server is running, and try refreshing     the page later as well.
zh-cn	#### 添加主机  Zabbix中，可以通过*配置 → 主机*或者*监测* → *主机*，查看已配置的主机信息。默认已有一个名为'Zabbix server'的预先定义好的主机。但我们需要学习如何添加另一个。  点击*创建主机*来新增一台主机。将会展示出一个主机配置表。\ ![](../../../assets/en/manual/quickstart/new_host.png)  所有必填字段均标有红色星号。  至少需要提供以下信息：  ***主机名***  -   输入一个主机名。允许使用大小写字母、数字、空格、点、破折号和下划线。  ***主机组***  -   通过单击*选择*按钮选择一个或多个现有组，或输入不存在的主机组名以创建新组。  ::: noteclassic 所有访问权限都是分配给主机组的，而不是单个主机。这就是为什么一个主机必须至少属于一个主机组。 :::  ***接口: IP地址***  -   虽然技术上它不是必填字段，但您可能希望输入主机的IP地址。请注意，如果这是Zabbix server的IP地址，必须在Zabbix agent配置文件中指定'Server'参数值。  [其他选项](/manual/config/hosts/host#configuration) 我们暂时使用默认值。  当完成后，点击*添加*。你可以在主机列表中看到你新添加的主机。  ![](../../../assets/en/manual/quickstart/host_list.png){width="600"}  可用性列包含每个接口的主机可用性指标。 我们已经定义了Zabbix代理接口，因此我们可以使用代理可用性图标(上面有‘ZBX’)来判断主机可用性：  -   ![icon\_zbx\_gray.png](../../../assets/en/manual/quickstart/icon_zbx_gray.png) -     表示主机状态尚未建立，尚未发生监控指标检查 -   ![icon\_zbx\_green.png](../../../assets/en/manual/quickstart/icon_zbx_green.png) -     表示主机可用，监控指标检查已成功 -   ![icon\_zbx\_red.png](../../../assets/en/manual/quickstart/icon_zbx_red.png) -     表示主机不可用，监控指标检查失败（将鼠标光标移动到图标上以查看错误消息）。可能是由于接口凭证不正确造成了通信问题。检查zabbix server是否正在运行，并稍后尝试刷新页面。

en-us	#### Adding hosts to host groups  Add two hosts to host groups with IDs 5 and 6.  Request:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.massadd",     "params": {         "groups": [             {                 "groupid": "5"             },             {                 "groupid": "6"             }         ],         "hosts": [             {                 "hostid": "30050"             },             {                 "hostid": "30001"             }         ]     },     "auth": "f223adf833b2bf2ff38574a67bba6372",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "5",             "6"         ]     },     "id": 1 } ```
zh-cn	#### 给主机组添加主机  给ID为5和6的主机组添加两个主机。  请求:  ```json {     "jsonrpc": "2.0",     "method": "hostgroup.massadd",     "params": {         "groups": [             {                 "groupid": "5"             },             {                 "groupid": "6"             }         ],         "hosts": [             {                 "hostid": "30050"             },             {                 "hostid": "30001"             }         ]     },     "auth": "f223adf833b2bf2ff38574a67bba6372",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "groupids": [             "5",             "6"         ]     },     "id": 1 } ```

en-us	#### Adding item  All items are grouped around hosts. That is why to configure a sample item we go to *Configuration → Hosts* and find the "New host" we have created.  Click on the *Items* link in the row of "New host", and then click on *Create item*. This will present us with an item definition form.  ![](../../../assets/en/manual/quickstart/new_item.png)  All mandatory input fields are marked with a red asterisk.  For our sample item, the essential information to enter is:  ***Name***  -   Enter *CPU load* as the value. This will be the item name displayed     in lists and elsewhere.  ***Key***  -   Manually enter *system.cpu.load* as the value. This is the technical     name of an item that identifies the type of information that will be     gathered. The particular key is just one of [pre-defined     keys](/manual/config/items/itemtypes/zabbix_agent) that come with     Zabbix agent.  ***Type of information***  -   This attribute defines the format of the expected data. For the     *system.cpu.load* key, this field will be automatically set to     *Numeric (float)*.  ::: noteclassic You may also want to reduce the number of days [item history](/manual/config/items/history_and_trends) will be kept, to 7 or 14. This is good practice to relieve the database from keeping lots of historical values. :::  [Other options](/manual/config/items/item#configuration) will suit us with their defaults for now.  When done, click *Add*. The new item should appear in the item list. Click on *Details* above the list to view what exactly was done.  ![](../../../assets/en/manual/quickstart/item_created.png)
zh-cn	#### 添加监控项  所有的监控项都是依赖于主机的。这就是为什么我们要配置一个监控项时，先要进入*配置 → 主机*页面查找到新建的主机。  在"新主机"行中，点击*监控项*这个链接，然后点击*创建监控项*，将会展示一个监控项配置表。  ![](../../../assets/en/manual/quickstart/new_item.png)  所有必填字段均标有红色星号。  对于我们的示例，需要提供以下信息:  ***名称***  -   输入*CPU load* 作为值. 在列表和其他地方，都会显示这个值作为监控项名称。  ***键值***  -   手动输入 system.cpu.load 作为值。 这是监控项的一个技术上的名称，用于识别获取信息的类型。这个特定值需要是Zabbix agent[预定义键值](/manual/config/items/itemtypes/zabbix_agent)的其中一种。  ***信息类型***  -   此属性定义预期数据的格式。对于键值     *system.cpu.load* , 这个字段会自动设置成     *浮点数*.  ::: noteclassic 您可能还希望减少[监控项历史数据](/manual/config/items/history_and_trends)的保留天数为7天或14天。这是一种很好的做法，可以避免数据库保存大量的历史数据。 :::  [其他选项](/manual/config/items/item#configuration) 我们暂时使用默认值。  当完成后，点击*添加*。新的监控项将出现在监控项列表中。点击列表中的详细以查看具体细节。  ![](../../../assets/en/manual/quickstart/item_created.png)

en-us	#### Adding item to template  To add an item to the template, go to the item list for 'New host'. In *Configuration → Hosts* click on *Items* next to 'New host'.  Then:  -   mark the checkbox of the 'CPU Load' item in the list -   click on *Copy* below the list -   select the template to copy item to  ![](../../../assets/en/manual/quickstart/copy_to_template.png)  All mandatory input fields are marked with a red asterisk.  -   click on *Copy*  If you now go to *Configuration → Templates*, 'New template' should have one new item in it.  We will stop at one item only for now, but similarly you can add any other items, triggers or other entities to the template until it's a fairly complete set of entities for given purpose (monitoring OS, monitoring single application).
zh-cn	#### 在模版中添加监控项  在模版中添加监控项，前往“新建主机“的监控项列表。在*配置 → 主机*，点击“新建主机“旁边的*监控项*。  然后：  -   选中列表中“CPU 负载”监控项的选择框 -   点击列表下方的*复制* -   选择要复制这个监控项的目标模版  ![](../../../assets/en/manual/quickstart/copy_to_template.png)  所有必填字段均标有红色星号。  -   点击*复制*  你现在可以前往*配置 → 模版*，"新模板"模版中会有一个新的监控项。  我们目前只创建了一个监控项，但你可以用同样的方法在模版中添加其他的监控项，触发器以及其他对象，直到满足特定需求（如监控操作系统，监控单个应用）的完整的对象组合。

en-us	##### Adding JMX agent item  For each JMX counter you are interested in you add **JMX agent** item attached to that interface.\  The key in the screenshot below says `jmx["java.lang:type=Memory","HeapMemoryUsage.used"]`.  ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_item.png)  All mandatory input fields are marked with a red asterisk.  The fields that require specific information for JMX items are:  |   |   | |--|--------| |*Type*|Set **JMX agent** here.| |*Key*|The `jmx[]` item key contains three parameters:<br>**object name** - the object name of an MBean<br>**attribute name** - an MBean attribute name with optional composite data field names separated by dots<br>**unique short description** - a unique description that allows multiple JMX items with the same object name and attribute name on the host (optional)<br>See below for more detail on JMX item keys.<br>Since Zabbix 3.4, you may discover MBeans and MBean attributes using a `jmx.discovery[]` [low-level discovery](/manual/discovery/low_level_discovery/examples/jmx) item.| |*JMX endpoint*|You may specify a custom JMX endpoint. Make sure that JMX endpoint connection parameters match the JMX interface. This can be achieved by using {HOST.\*} macros as done in the default JMX endpoint.<br>This field is supported since 3.4.0. {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) and user macros are supported.| |*User name*|Specify the user name, if you have configured authentication on your Java application.<br>User macros are supported.| |*Password*|Specify the password, if you have configured authentication on your Java application.<br>User macros are supported.|  If you wish to monitor a Boolean counter that is either "true" or "false", then you specify type of information as "Numeric (unsigned)" and select "Boolean to decimal" preprocessing step in the Preprocessing tab. Server will store Boolean values as 1 or 0, respectively.
zh-cn	##### 添加 JMX 代理监控项  对于您感兴趣的每个 JMX 计数器，您添加附加到该接口的 **JMX 代理** 监控项。\  下面屏幕截图中的键表示 `jmx["java.lang:type=Memory","HeapMemoryUsage.used"]`。  ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_item.png)  所有必填输入字段都标有红色星号。   JMX 监控项需要的特定信息字段是：  | · | · | |--|--------| |*类型*|在这里设置**JMX代理**。| |*键值*|`jmx[]` 监控项键包含三个参数：<br>**对象名称** - MBean 的对象名称<br>**属性名称** - 一个 MBean 属性名称，带有由点分隔的可选复合数据字段名称<br>**唯一简短描述** - 允许主机上具有相同对象名称和属性名称的多个 JMX 监控项的唯一描述（可选）<br>有关 JMX 监控项的更多详细信息，请参见下文 <br>从 Zabbix 3.4 开始，您可以使用 `jmx.discovery[]` [低级发现](/manual/discovery/low_level_discovery/examples/jmx) 项来发现 MBean 和 MBean 属性。| |*JMX 端点*|您可以指定自定义 JMX 端点。 确保 JMX 端点连接参数与 JMX 接口匹配。 这可以通过在默认 JMX 端点中使用 {HOST.\*} 宏来实现。<br>此字段自 3.4.0 起受支持。 {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) 和用户宏被支持。| |*用户名*|如果您在 Java 应用程序上配置了身份验证，请指定用户名。<br>支持用户宏。| |*密码*|指定密码，如果您已在 Java 应用程序上配置身份验证。<br>支持用户宏。|  如果您希望监视“真”或“假”的布尔计数器，则将信息类型指定为“数字（无符号）”并在“预处理”选项卡中选择“布尔到十进制”预处理步骤。 服务器将布尔值分别存储为 1 或 0。

en-us	#### Adding lines  In addition to shapes, it is also possible to add some lines. Lines can be used to link elements or shapes in a map.  To add a line, click on *Add* next to Shape. A new shape will appear at the top left corner of the map. Select it and click on *Line* in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, color, etc.  ![map\_line.png](../../../../../assets/en/manual/config/visualization/map_line.png){width="600"}
zh-cn	#### 添加行  除了形状之外，还可以添加一些线。线可以用于链接地图中的元素或形状。  要添加线，请单击形状旁边的*添加*。一个新的形状将出现在地图的左上角。选择它并点击*线*编辑表格以将形状更改为线条。然后调整线属性，例如线型、宽度、颜色等。  ![map\_line.png](../../../../../assets/en/manual/config/visualization/map_line.png){width="600"}

en-us	#### Adding LLD macro paths  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.json.path"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```
zh-cn	#### 添加LLD宏路径  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.json.path"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```

en-us	#### Adding LLD macro paths  Request:  ```json {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.json.path"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```
zh-cn	#### 添加LLD宏路径  请求：  ``` {.java} {     "jsonrpc": "2.0",     "method": "discoveryrule.update",     "params": {         "itemid": "22450",         "lld_macro_paths": [             {                 "lld_macro": "{#MACRO1}",                 "path": "$.json.path"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应：  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "itemids": [             "22450"         ]     },     "id": 1 } ```

en-us	#### Adding macros  Add two new macros to two hosts.  Request:  ```json {     "jsonrpc": "2.0",     "method": "host.massadd",     "params": {         "hosts": [             {                 "hostid": "10160"             },             {                 "hostid": "10167"             }         ],         "macros": [             {                 "macro": "{$TEST1}",                 "value": "MACROTEST1"             },             {                 "macro": "{$TEST2}",                 "value": "MACROTEST2",                 "description": "Test description"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10160",             "10167"         ]     },     "id": 1 } ```
zh-cn	#### 添加宏  向两个主机添加两个新的宏。  请求:  ```json {     "jsonrpc": "2.0",     "method": "host.massadd",     "params": {         "hosts": [             {                 "hostid": "10160"             },             {                 "hostid": "10167"             }         ],         "macros": [             {                 "macro": "{$TEST1}",                 "value": "MACROTEST1"             },             {                 "macro": "{$TEST2}",                 "value": "MACROTEST2",                 "description": "Test description"             }         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "hostids": [             "10160",             "10167"         ]     },     "id": 1 } ```

en-us	#### Adding pages  To add a new page to a dashboard:  -   Make sure the dashboard is in the [editing     mode](#viewing_and_editing_a_dashboard) -   Click on the arrow next to the *Add* button and select the *Add     page* option  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_add.png)  -   Fill the general page parameters and click on *Apply*. If you leave     the name empty, the page will be added with a `Page N` name where     'N' is the incremental number of the page. The page display period     allows to customize how long a page is displayed in a slideshow.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_properties.png)  A new page will be added, indicated by a new tab (*Page 2*).  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_new.png)  The pages can be reordered by dragging-and-dropping the page tabs. Reordering maintains the original page naming. It is always possible to go to each page by clicking on its tab.  When a new page is added, it is empty. You can add widgets to it as described above.
zh-cn	#### 添加页面  要添加新页面到仪表盘：  -   确保仪表盘在[编辑模式](#viewing_and_editing_a_dashboard) -   点击*添加*按钮旁边的箭头，再选择*添加页面*选项  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_add.png)  -   填充通用页面参数并点击*应用*。如果您将名称留空，页面会以`页面N`为名称添加，'N'是递增的页数。页面显示时间范围允许自定义页面在滑动显示中显示的时间。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_properties.png)  新页面会被添加，并显示在一个新标签页（*页面2*）中。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_new.png)  这些页面可在页面标签上拖动进行重新排序。重新排序维持原页面名称。 一直可通过点击标签页进入页面。  当新页面被添加时，它是空的，您可以按之前的描述添加组件。

en-us	##### Adding permissions  By default, a new user has no permissions to access hosts. To grant the user rights, click on the group of the user in the *Groups* column (in this case - 'Zabbix administrators'). In the group properties form, go to the *Permissions* tab.  ![](../../../assets/en/manual/quickstart/group_permissions.png){width="600"}  This user is to have read-only access to *Linux servers* group, so click on *Select* next to the user group selection field.  ![](../../../assets/en/manual/quickstart/add_permissions.png)  In this pop-up, mark the checkbox next to 'Linux servers', then click *Select*. *Linux servers* should be displayed in the selection field. Click the 'Read' button to set the permission level and then *Add* to add the group to the list of permissions. In the user group properties form, click *Update*.  ::: noteimportant In Zabbix, access rights to hosts are assigned to [user groups](/manual/config/users_and_usergroups/usergroup), not individual users. :::  Done! You may try to log in using the credentials of the new user.
zh-cn	##### 添加权限  默认情况下，一个新的用户没有权限访问主机。要授予用户权限，请单击*组*列中的用户组（在本例中为“Zabbix administrators”）。在“用户群组”窗口中，转到“权限”选项卡。  ![](../../../assets/en/manual/quickstart/group_permissions.png){width="600"}  该用户需要以只读方式访问*Linux Server*主机组，因此请单击用户组选择字段旁边的*选择*。  ![](../../../assets/en/manual/quickstart/add_permissions.png)  在此弹出框中，选中在“Linux servers”旁边的复选框，然后单击*选择*。*Linux servers*就会显示在选择清单中。 单击“Read”按钮设置权限级别，然后添加到权限列表中。 在用户组属性表单中，单点击*更新*。  ::: noteimportant 在Zabbix中，主机的访问权限被分配给 [用户组](/manual/config/users_and_usergroups/usergroup), 而不是单独的用户。 :::  权限设置完成了！ 您可以尝试使用新用户的凭据登录。

en-us	##### Adding proxies  To configure a proxy in Zabbix frontend:  -   Go to: *Administration → Proxies* -   Click on *Create proxy*  ![](../../../assets/en/manual/distributed_monitoring/proxy.png){width="600"}  |Parameter|<|Description| |---------|-|-----------| |*Proxy name*|<|Enter the proxy name. It must be the same name as in the *Hostname* parameter in the proxy configuration file.| |*Proxy mode*|<|Select the proxy mode.<br>**Active** - the proxy will connect to the Zabbix server and request configuration data<br>**Passive** - Zabbix server connects to the proxy<br>*Note* that without encrypted communications (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data if authentication does not take place or proxy addresses are not limited in the *Proxy address* field.| |*Proxy address*|<|If specified then active proxy requests are only accepted from this list of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of active Zabbix proxy.<br>This field is only available if an active proxy is selected in the *Proxy mode* field. Macros are not supported.<br>This option is supported since Zabbix 4.0.0.| |*Interface*|<|Enter interface details for the passive proxy.<br>This field is only available if a passive proxy is selected in the *Proxy mode* field.| |<|*IP address*|IP address of the passive proxy (optional).| |^|*DNS name*|DNS name of the passive proxy (optional).| |^|*Connect to*|Clicking the respective button will tell Zabbix server what to use to retrieve data from proxy:<br>**IP** - Connect to the proxy IP address (recommended)<br>**DNS** - Connect to the proxy DNS name| |^|*Port*|TCP/UDP port number of the passive proxy (10051 by default).| |*Description*|<|Enter the proxy description.|  The **Encryption** tab allows you to require encrypted connections with the proxy.  |Parameter|Description| |---------|-----------| |*Connections to proxy*|How the server connects to the passive proxy: no encryption (default), using PSK (pre-shared key) or certificate.| |*Connections from proxy*|Select what type of connections are allowed from the active proxy. Several connection types can be selected at the same time (useful for testing and switching to other connection type). Default is "No encryption".| |*Issuer*|Allowed issuer of certificate. Certificate is first validated with CA (certificate authority). If it is valid, signed by the CA, then the *Issuer* field can be used to further restrict allowed CA. This field is optional, intended to use if your Zabbix installation uses certificates from multiple CAs.| |*Subject*|Allowed subject of certificate. Certificate is first validated with CA. If it is valid, signed by the CA, then the *Subject* field can be used to allow only one value of *Subject* string. If this field is empty then any valid certificate signed by the configured CA is accepted.| |*PSK identity*|Pre-shared key identity string.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |*PSK*|Pre-shared key (hex-string). Maximum length: 512 hex-digits (256-byte PSK) if Zabbix uses GnuTLS or OpenSSL library, 64 hex-digits (32-byte PSK) if Zabbix uses mbed TLS (PolarSSL) library. Example: 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952|
zh-cn	##### 添加一个proxy代理  在Zabbix前端中配置proxy：  -   前往: *Administration → Proxies* -   点击 *创建proxy*  ![](../../../assets/en/manual/distributed_monitoring/proxy.png){width="600"}  |参数|<|描述| |---------|-|-----------| |*Proxy name*|<|输入proxy名称。 必须与proxy配置文件中的“*Hostname*”保持一致。| |*Proxy mode*|<|选择proxy模式。<br>**主动** - proxy将连接到Zabbix server并请求配置数据<br>**被动** - -   Zabbix server连接到proxy<br>*Note* 没有加密的通信(敏感的)proxy配置数据可能会成为可以访问Zabbix服务器的端口时，使用一个主动的proxy。这是可能的，因为任何人都可以假装是一个活动的proxy并请求配置数据，如果身份验证没有发生或proxy地址不受限制在*Proxy 地址*字段。| |*Proxy address*|<|如果指定了，那么主动的proxy请求只接受这个以逗号分隔的IP地址列表(可选的CIDR标记)，或者主动 Zabbix proxy的DNS名称。<br>该字段仅在“*Proxy 模式*”字段中选择了active proxy时有效。 宏是不支持的。<br>从Zabbix 4.0.0开始就支持这个选项。| |*Interface*|<|输入被动proxy的接口详细信息。<br>该字段仅在“*Proxy模式*”字段中选择被动proxy时有效。| |<|*IP address*|被动proxy的IP地址(可选)。| |^|*DNS name*|被动proxy的DNS名称(可选)。| |^|*Connect to*|点击相应的按钮将告诉Zabbix server使用什么来从proxy检索数据:<br>**IP** -连接proxyIP地址(推荐)<br>**DNS** -连接到proxy DNS名称| |^|*Port*|被动proxy的TCP/UDP端口号(默认为10051)。| |*Description*|<|输入proxy描述信息。|  **加密**选项卡允许您要求与proxy的加密连接。  |参数|描述| |---------|-----------| |*Connections to proxy*|服务器如何连接到被动proxy: 不加密(默认)，使用PSK(预共享密钥)或证书。| |*Connections from proxy*|选择从活动proxy中允许的连接类型。 可以同时选择几种连接类型(这对于测试和切换到其他连接类型很有用)。 默认为“不加密”。| |*Issuer*|允许的证书颁发者。 证书首先由CA(证书颁发机构)验证。 如果它是有效的，由CA签名，那么*Issuer*字段可以用于进一步限制所允许的CA。此字段是可选的，用于Zabbix安装使用来自多个CA的证书时。| |*Subject*|证书允许的主题。 证书首先由CA验证。如果它是有效的，由CA签名，那么*Subject*字段可以用来只允许一个值的*Subject*字符串。 如果此字段为空，则接受由配置的CA签名的任何有效证书。| |*PSK identity*|-   预共享密钥标识字符串。<br>不要把敏感信息放在PSK身份中，它在网络上未经加密传输，以通知接收方使用哪个PSK。| |*PSK*|Pre-shared关键(hex-string)。最大长度: 512十六进制数字(256字节PSK) 如果Zabbix使用GnuTLS或OpenSSL库，64十六进制数字(32字节PSK)如果Zabbix使用mbed TLS (PolarSSL)库。 例如： 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952|

en-us	#### Adding shapes  In addition to map elements, it is also possible to add some shapes. Shapes are not map elements; they are just a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Rectangle and ellipse shapes can be added.  To add a shape, click on *Add* next to Shape. The new shape will appear at the top left corner of the map. Drag and drop it wherever you like.  A new shape is added with default colors. By clicking on the shape, a form is displayed and you can customize the way a shape looks, add text, etc.  ![](../../../../../assets/en/manual/config/visualization/map_shape.png){width="600"}  To select shapes, select one and then hold down *Ctrl* to select the others. With several shapes selected, common properties can be mass updated, similarly as with elements.  Text can be added in the shapes. Expression [macros](/manual/appendix/macros/supported_by_location) are supported in the text, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).  To display text only the shape can be made invisible by removing the shape border (select 'None' in the *Border* field). For example, take note of how the {MAP.NAME} macro, visible in the screenshot above, is actually a rectangle shape with text, which can be seen when clicking on the macro:  ![](../../../../../assets/en/manual/config/visualization/map_name_macro.png)  {MAP.NAME} resolves to the configured map name when viewing the map.  If hyperlinks are used in the text, they become clickable when viewing the map.  Line wrapping for text is always "on" within shapes. However, within an ellipse, the lines are wrapped as though the ellipse were a rectangle. Word wrapping is not implemented, so long words (words that do not fit the shape) are not wrapped, but are masked (constructor page) or clipped (other pages with maps).
zh-cn	#### 添加形状  除了地图元素，还可以添加一些形状。形状不是地图元素；它们只是一种视觉表现。例如，可以使用矩形作为背景来分组一些主机。可以添加矩形和椭圆形。  要添加形状，请单击形状旁边的*添加*。新形状将出现在地图的左上角。将其拖放到您喜欢的任何位置。  添加了具有默认颜色的新形状。通过单击形状，窗体显示，您可以自定义形状的外观，添加文本，等等。  ![](../../../../../assets/en/manual/config/visualization/map_shape.png){width="600"}  要选择形状，请选择一个，然后按住 *Ctrl* 选择其他。选择几种形状后，常见的属性可以是质量更新，与元素类似。  可以在形状中添加文本。表达[宏](/manual/appendix/macros/supported_by_location) 支持文本，但只有 `avg`、`last`、`min` 和 `max` 函数，有时间作为参数（例如，`{?avg(/host/key,1h)}`）。  要仅显示文本，可以通过删除形状边框（在 *边框* 字段中选择“无”）。例如，取请注意上面屏幕截图中可见的 {MAP.NAME} 宏是如何实现的实际上是一个带有文本的矩形形状，单击时可以看到宏：  ![](../../../../../assets/en/manual/config/visualization/map_name_macro.png)  {MAP.NAME} 在查看地图时解析为配置的地图名称。  如果文本中使用了超链接，则它们在查看时变为可点击的地图。  文本的换行始终在形状内“开启”。然而，在一椭圆，线条被包裹起来，好像椭圆是一个矩形。没有实现自动换行，所以长词（不适合的词形状）没有被包裹，而是被屏蔽（构造器页面）或被剪裁（其他页面有地图）。

en-us	#### Adding template  To start working with templates, we must first create one. To do that, in *Configuration → Templates* click on *Create template*. This will present us with a template configuration form.\ ![](../../../assets/en/manual/quickstart/new_template.png)  All mandatory input fields are marked with a red asterisk.  The required parameters to enter here are:  ***Template name***  -   Enter a template name. Alpha-numericals, spaces and underscores are     allowed.  ***Groups***  -   Select one or several groups by clicking *Select* button. The     template must belong to a group.  When done, click *Add*. Your new template should be visible in the list of templates.  ![](../../../assets/en/manual/quickstart/template_list.png){width="600"}  As you may see, the template is there, but it holds nothing in it - no items, triggers or other entities.
zh-cn	#### 添加模板  在开始使用模版之前，你必须先创建一个。在*配置 → 模版*中，点击*创建模版*。将会展示出一个模版配置表。  ![](../../../assets/en/manual/quickstart/new_template.png)  所有必填字段均标有红色星号。  此处需要输入的参数包括：  ***模板名称***  -   输入一个模板名称。允许使用大小写字母、数字、空格和下划线。  ***主机组***  -   通过单击*选择*按钮选择一个或多个现有组。模板必须属于某个主机组。  完成后，点击*添加*。你可以在模板列表中看到你新添加的模板。  ![](../../../assets/en/manual/quickstart/template_list.png){width="600"}  你可以在这看到模版信息，但里面什么都没有——没有监控项、触发器或其他其他对象。

en-us	#### Adding trigger  To configure a trigger for our item, go to *Configuration → Hosts*, find 'New host' and click on *Triggers* next to it and then on *Create trigger*. This presents us with a trigger definition form.\ ![](../../../assets/en/manual/quickstart/new_trigger.png)  For our trigger, the essential information to enter here is:  *Name*  -   Enter *CPU load too high on 'New host' for 3 minutes* as the value.     This will be the trigger name displayed in lists and elsewhere.  *Expression*  -   Enter: avg(/New host/system.cpu.load,3m)>2  This is the trigger expression. Make sure that the expression is entered right, down to the last symbol. The item key here (system.cpu.load) is used to refer to the item. This particular expression basically says that the problem threshold is exceeded when the CPU load average value for 3 minutes is over 2. You can learn more about the [syntax of trigger expressions](/manual/config/triggers/expression).  When done, click *Add*. The new trigger should appear in the trigger list.
zh-cn	#### 添加触发器  为监控项配置触发器，前往*配置 → 主机*，找到”新增的主机“，点击旁边的*触发器* ，然后点击*创建触发器*。将会展示一个触发器配置表。 ![](../../../assets/en/manual/quickstart/new_trigger.png)  对于我们的触发器，需要提供以下信息：  *名称*  -   输入*CPU load too high on 'New host' for 3 minutes* 作为值。     在列表和其他地方，都会显示这个值作为触发器名称。  *表达式*  -   输入: avg(/New host/system.cpu.load,3m)>2  这个是触发器的表达式。确认这个表达式输入正确，直到最后一个符号。这个监控项键值(system.cpu.load)用于指出具体的监控项。这个特定的表达式大致是说如果3分钟内，CPU负载的平均值超过2，那么就触发了问题的阈值。你可以查看更多的 [触发器表达式语法](/manual/config/triggers/expression)。  完成后，点击*添加*。新的触发器将会显示在触发器列表中。

en-us	#### Adding web scenarios  To add web scenarios to a template in *Configuration → Templates*, do the following:  -   Click on *Web* in the row of the template -   Configure a web scenario following the usual method of [configuring     web scenarios](/manual/web_monitoring#configuring_a_web_scenario)
zh-cn	 #### 添加Web场景  在模板的*配置 → 模板*中添加Web场景，请执行以下操作：  -   点击模板行中的*Web* -   按照[配置Web场景](/manual/web_monitoring#configuring_a_web_scenario)的通常方式配置Web场景

en-us	#### Adding widgets  To add a widget to a dashboard:  -   Click on the     ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_add_button.png)     button or the *Add widget* option in the action menu that can be     opened by clicking on the arrow. Fill the widget configuration form.     The widget will be created in its default size and placed after the     existing widgets (if any);  Or  -   Move your mouse to the desired empty spot for the new widget. Notice     how a placeholder appears, on mouseover, on any empty slot on the     dashboard. Then click to open the widget configuration form. After     filling the form the widget will be created in its default size or,     if its default size is bigger than is available, take up the     available space. Alternatively, you may click and drag the     placeholder to the desired widget size, then release, and then fill     the widget configuration form. (Note that when there is a widget     copied onto the clipboard, you will be first prompted to select     between *Add widget* and *Paste widget* options to create a widget.)  ![](../../../../../assets/en/manual/web_interface/dashboard_click.png)  ![](../../../../../assets/en/manual/web_interface/dashboard_select.png)  In the widget configuration form:  -   Select the *Type* of widget -   Enter widget parameters -   Click on *Add*  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/widget_add.png)  #### Widgets  The following widgets can be added to a dashboard:  -   [Action     log](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/action_log) -   [Clock](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/clock) -   [Data     overview](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/data_overview) -   [Discovery     status](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/discovery_status) -   [Favorite     graphs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/favorite_graphs) -   [Favorite     maps](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/favorite_maps) -   [Geomap](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/geomap) -   [Graph](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph) -   [Graph     (classic)](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph_classic) -   [Graph     prototype](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph_prototype) -   [Host     availability](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/host_availability) -   [Item value](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value) -   [Map](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/map) -   [Map navigation     tree](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/map_tree) -   [Plain     text](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/plain_text) -   [Problem     hosts](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problem_hosts) -   [Problems](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problems) -   [System     information](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/system) -   [Problems by     severity](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problems_severity) -   [Trigger     overview](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/trigger_overview) -   [URL](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/url) -   [Web     monitoring](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/web_monitoring)  In dashboard editing mode widgets can be resized and moved around the dashboard by clicking on the widget title bar and dragging it to a new location. Also, you can click on the following buttons in the top-right corner of the widget to:  -   ![](../../../../../assets/en/manual/web_interface/widget_edit.png) -     edit a widget; -   ![](../../../../../assets/en/manual/web_interface/button_widget_menu.png) -     access the [widget menu](#widget_menu)  Click on *Save changes* for the dashboard to make any changes to the widgets permanent.  
zh-cn	#### 动态小构件  在 [配置](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets) 一些小部件的时:  -   图形 (或者简单图形) -   纯文本 -   URL  还有一个特别的选项 *动态监控项*。 如果你勾选此项，便可以根据选择不同的主机展示不同的内容，或者持续展示更新最新的数据信息。  当你勾选动态监控后，在保存仪表板时，您会注意到仪表板上方出现了两个新的下拉列表，用于选择主机组/主机:  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dynamic_dropdowns.png)  因此，您有一个窗口小构件，它可以显示基于下拉列表中所选主机的数据的内容。 这样做的好处是您不需要创建额外的小构件，例如，您希望看到包含来自不同主机的数据的相同图形。  

en-us	##### Additional parameters  A third optional parameter is supported by the *bucket\_rate\_foreach* function:      bucket_rate_foreach(item filter,time period,<parameter number>)  where <parameter number> is the position of the "bucket" value in the item key. For example, if the "bucket" value in myItem\[aaa,0.2\] is '0.2', then its position is 2.  The default value of <parameter number> is '1'.
zh-cn	##### 附加参数  *bucket\_rate\_foreach* 支持第三个可选参数 功能：      bucket_rate_foreach(item filter,time period,<parameter number>)  其中 <parameter number> 是“bucket”值在 监控项键。例如，如果 myItem\[aaa,0.2\] 中的“bucket”值为 '0.2'，则其位置为 2。  <parameter number> 的默认值为“1”。

en-us	### Administration  With the Zabbix API you can change administration settings of your monitoring system.
zh-cn	### 管理  使用 Zabbix API，您可以更改监控系统的管理设置。

en-us	#### Advanced configuration  Advanced configuration options become available if the *Advanced  configuration* checkbox is marked (see screenshot) and only for  those elements that are selected in the *Show* field (see above).  Additionally, advanced configuration allows to change the background  color for the whole widget.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_advanced.png)  |   |   | |---|---| |_**Description**_ |Enter the item description. This description may override the default item name. Multiline descriptions are supported. A combination of text and supported macros is possible.<br>{HOST.\*}, {ITEM.\*}, {INVENTORY.\*} and user macros are supported. | |*Horizontal position* |Select horizontal position of the item description - left, right or center. | |*Vertical position* |Select vertical position of the item description - top, bottom or middle. | |*Size* |Enter font size height for the item description (in percent relative to total widget height). | |*Bold* |Mark the checkbox to display item description in bold type. | |*Color* |Select the item description color from the color picker.<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker. | |_**Value**_ | | |*Decimal places* |Select how many decimal places will be displayed with the value. This value will affect only float items. | |*Size* |Enter font size height for the decimal places (in percent relative to total widget height). | |*Horizontal position* |Select horizontal position of the item value - left, right or center. | |*Vertical position* |Select vertical position of the item value - top, bottom or middle. | |*Size* |Enter font size height for the item value (in percent relative to total widget height).<br>*Note* that the size of item value is prioritised; other elements have to concede space for the value. With the change indicator though, if the value is too large, it will be truncated to show the change indicator. | |*Bold* |Mark the checkbox to display item value in bold type. | |*Color* |Select the item value color from the color picker.<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker. | |*Units* |Mark the checkbox to display units with the item value. If you enter a unit name, it will override the unit from item configuration. | |*Position* |Select the item unit position - above, below, before or after the value. | |*Size* |Enter font size height for the item unit (in percent relative to total widget height). | |*Bold* |Mark the checkbox to display item unit in bold type. | |*Color* |Select the item unit color from the color picker.<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker. | |_**Time**_ |Time is the clock value from item history. | |*Horizontal position* |Select horizontal position of the time - left, right or center. | |*Vertical position* |Select vertical position of the time - top, bottom or middle. | |*Size* |Enter font size height for the time (in percent relative to total widget height). | |*Bold* |Mark the checkbox to display time in bold type. | |*Color* |Select the time color from the color picker.<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker. | |_**Change indicator**_ |Select the color of change indicators from the color picker. The change indicators are as follows:<br>**↑** - item value is up (for numeric items)<br>**↓** - item value is down (for numeric items)<br>**↕** - item value has changed (for string items and items with value mapping)<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker.<br>Vertical size of the change indicator is equal to the size of the value (integer part of the value for numeric items).<br>*Note* that up and down indicators are not shown with just one value. | |_**Background color**_ |Select the background color for the whole widget from the color picker.<br>`D` stands for default color (depends on the frontend theme). To return to the default value, click the *Use default* button in the color picker. |  *Note* that multiple elements cannot occupy the same space; if they are placed in the same space, an error message will be displayed.
zh-cn	#### 高级配置  如果 "高级配置 "复选框被选中（如下图），高级配置选项就可用，而且只适用于那些在 "显示 "区域被选中的元素（见上文）。  此外，高级配置允许改变整个组件的背景颜色。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_advanced.png)  | | | |---|---| |_**描述**_ |输入监控项描述。该描述可以覆盖默认的监控项名称。支持多行描述。可以使用文本和支持的变量的组合。<br>支持{HOST.\*}、{ITEM.\*}、{INVENTORY.\*}和用户变量。| |*水平位置* |选择监控项显示的水平位置--左边、右边或居中。| |*垂直位置* |选择监控项显示的垂直位置--顶部、底部或居中。 | |*大小* |输入监控项数据的字体大小高度（相对于组件总高度的百分比）。 | |*粗体* |选中复选框，粗体显示监控项数据。。 | |*颜色* |从颜色选择器中选择监控项数据字体的颜色。<br>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。 | |_**数据**_ | | |*小数位数* |此选项设置数据显示的小数点位数。此选项只影响浮点值。 | |*尺寸* |此选项为小数点后数字字体设置尺寸高度（相对于小组件总高度的百分比）| |*水平位置* |选择监控项显示的水平位置--左边、右边或居中。 | |*垂直位置* |选择监控项显示的垂直位置--顶部、底部或居中。 | |*大小* |输入项目值的字体大小高度（相对于小部件总高度的百分比）。<br>请注意，监控项数据的位置是优先考虑的；其他元素必须为该值让出空间。不过对于变化指示器，如果数值太大，它将被截断以显示变化指示器。 | |*粗体* |选中复选框，粗体显示监控项数据。 | |*颜色* | 从颜色选择器中选择监控项数据字体的颜色。<br>>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。 | |*单位* |选中复选框设置监控项的单位。如果你输入一个单位名称，它将覆盖监控项的单位。| |*位置* |选择监控项单位的位置--在数值的上方、下方、前面或后面。 | |*大小* |输入监控项数据的字体大小高度（相对于组件总高度的百分比）。| |*粗体* |选中复选框，粗体显示监控项。 | |*颜色* | 从颜色选择器中选择监控项数据单位字体的颜色。<br>>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。 | |_**时间**_ |监控项历史数据的时间。 | |*水平位置* |选择时间显示的水平位置--左边、右边或居中。 | |*垂直位置* |选择时间显示的垂直位置--顶部、底部或居中。 | |*大小* |输入时间的字体大小高度（相对于小部件总高度的百分比）。 | |*粗体* |选中复选框以粗体显示时间。 | |*颜色* |从颜色选择器中选择时间颜色。<br>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。 | |_**变化指标**_ |从颜色选择器中选择变化指标的颜色。变化指标如下：<br>**↑** - 监控项数据值增大（对于监控项数值）<br>**↓** - 监控项数据值降低（对于监控项数值）<br>**↕* * - 监控项数据值内容产生变化（对于监控项数值以及文本）<br>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。<br>变化指示器的垂直大小等于值的大小（对于监控项数值的整数部分）。<br> *注意* 只有一个值时，不会显示向上和向下的指示器。 | |_**背景颜色**_ |从颜色选择器中选择整个组件的背景颜色。<br>`D`代表默认颜色（取决于前端主题）。如需恢复默认值，请单击颜色选择器中的 *Use default* 按钮。 |  *注意*多个元素不能部署在同一空间；如果它们被放在同一空间，将显示一个错误信息。

en-us	 #### Advanced configuration  ![](../../../assets/en/manual/web_interface/service_a.png){width=600}  |Parameter|Description| |---------|-----------| |_**Additional rules**_|Click on *Add* to define additional status calculation rules.| |*Set status to*|Set service status to either *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster* in case of a condition match.| |*Condition*|Select the condition for direct child services:<br>**if at least (N) child services have (Status) status or above**<br>**if at least (N%) of child services have (Status) status or above**<br>**if less than (N) child services have (Status) status or below**<br>**if less than (N%) of child services have (Status) status or below**<br>**if weight of child services with (Status) status or above is at least (W)**<br>**if weight of child services with (Status) status or above is at least (N%)**<br>**if weight of child services with (Status) status or below is less than (W)**<br>**if weight of child services with (Status) status or below is less than (N%)** <br><br> If several conditions are specified and the situation matches more than one condition, the highest severity will be set.| |*N (W)*|Set the value of N or W (1-100000), or N% (1-100) in the condition.| |*Status*|Select the value of *Status* in the condition: *OK* (default), *Not classified*, *Information*, *Warning*, *Average*, *High* or *Disaster*.| |_**Status propagation rule**_|Rule for propagating the service status to the parent service:<br>**As is** - the status is propagated without change<br>**Increase by** - you may increase the propagated status by 1 to 5 severities<br>**Decrease by** - you may decrease the propagated status by 1 to 5 severities<br>**Ignore this service** - the status is not propagated to the parent service at all<br>**Fixed status** - the status is propagated statically, i.e. as always the same| |_**Weight**_|Weight of the service (integer in the range from 0 (default) to 1000000).|  :::noteclassic Additional status calculation rules can only be used to increase severity level over the level calculated according to the main *Status calculation rule* parameter. If according to additional rules the status should be Warning, but according to the *Status calculation rule* the status is Disaster - the service will have status Disaster.  :::
zh-cn	#### 高级配置  ![](../../../assets/en/manual/web_interface/service_a.png){width=600}  |参数|说明| |---------|-----------| |_**Additional rules**_|单击 *Add* 以定义其他状态计算规则。| |*Set status to*|如果 condition 匹配，则将服务状态设置为*OK*（默认）、*Not classified*、*Information*、*Warning*、*Average*、*High* 或 *Disaster*。| |*Condition*|选择子服务的条件：<br>**如果至少 (N) 个子服务具有 (Status) 表示的状态或以上状态**<br>**如果至少 (N%) 的子服务具有 (Status) 表示的状态或以上状态**<br>**如果少于 (N) 个子服务具有 (Status) 表示的状态或以下状态**<br>**如果少于 (N%) 的子服务具有 (Status) 表示的状态或以下状态**<br>**如果具有 (Status) 状态的子服务的权重至少为 (W)**<br>**如果具有 (Status) 状态的子服务的权重至少为 (N%)**<br>**如果具有 (Status) 状态的子服务的权重小于 (W)**<br>**如果具有 (Status) 状态的子服务的权重少于 (N%)** <br><br> 如果指定了多个条件，并且情况与多个条件匹配，则将设置最高的严重性。| |*N (W)*|在 condition 中设置 N 或 W (1-100000) 或 N% (1-100) 的值。| |*Status*|选择 condition 中 *Status* 的值：*OK* (默认)、*Not classified*、*Information*、*Warning*、*Average*、*High* 或 *Disaster*。| |_**Status propagation rule**_|将服务状态传播到父服务的规则：<br>**As is** - 传播状态没有变化<br>**Increase by** - 您可以将传播的状态增加 1 到 5 个严重性<br>**Decrease by** - 您可以将传播的状态减少 1 到 5 个严重性<br>**Ignore this service** - 状态根本不会传播到父服务<br>**Fixed status** - 状态以静态方式传播，即始终保持不变| |_**Weight**_|服务的权重（0（默认）到1000000之间的整数）。|  :::noteclassic 附加状态计算规则只能用于将严重级别提高到根据 *Status calculation rule* 参数计算的级别之上。如果根据 additional rules，状态应为警告，但 *Status calculation rule* 状态为灾难 - 服务将具有灾难状态。 :::

en-us	##### Advanced settings  Additional SAML parameters can be configured in the Zabbix frontend configuration file (*zabbix.conf.php*):  -   $SSO\['SP\_KEY'\] = '<path to the SP private key file>'; -   $SSO\['SP\_CERT'\] = '<path to the SP cert file>'; -   $SSO\['IDP\_CERT'\] = '<path to the IDP cert file>'; -   $SSO\['SETTINGS'\]  ::: noteclassic  Zabbix uses [OneLogin's SAML PHP Toolkit](https://github.com/onelogin/php-saml/tree/3.4.1) library (version 3.4.1). The structure of $SSO\['SETTINGS'\] section should be similar to the structure used by the library. For the description of configuration options, see official library [documentation](https://github.com/onelogin/php-saml/tree/3.4.1/#user-content-settings).  :::  Only the following options can be set as part of $SSO\['SETTINGS'\]:  -   *strict* -   *baseurl* -   *compress* -   *contactPerson* -   *organization* -   *sp* (only options specified in this list)     -   *attributeConsumingService*     -   *x509certNew* -   *idp* (only options specified in this list)     -   *singleLogoutService* (only one option)         -   *responseUrl*     -   *certFingerprint*     -   *certFingerprintAlgorithm*     -   *x509certMulti* -   *security* (only options specified in this list)     -   *signMetadata*     -   *wantNameId*     -   *requestedAuthnContext*     -   *requestedAuthnContextComparison*     -   *wantXMLValidation*     -   *relaxDestinationValidation*     -   *destinationStrictlyMatches*     -   *rejectUnsolicitedResponsesWithInResponseTo*     -   *signatureAlgorithm*     -   *digestAlgorithm*     -   *lowercaseUrlencoding*  All other options will be taken from the database and cannot be overridden. The *debug* option will be ignored.  In addition, if Zabbix UI is behind a proxy or a load balancer, the custom *use\_proxy\_headers* option can be used:  -   *false* (default) - ignore the option; -   *true* - use X-Forwarded-\* HTTP headers for building the base URL.    If using a load balancer to connect to Zabbix instance, where the load balancer uses TLS/SSL and Zabbix does not, you must indicate 'baseurl', 'strict' and 'use_proxy_headers' parameters as follows:      $SSO_SETTINGS=['strict' => false, 'baseurl' => "https://zabbix.example.com/zabbix/", 'use_proxy_headers' => true]   **Configuration example:**      $SSO['SETTINGS'] = [         'security' => [             'signatureAlgorithm' => 'http://www.w3.org/2001/04/xmldsig-more#rsa-sha384'             'digestAlgorithm' => 'http://www.w3.org/2001/04/xmldsig-more#sha384',             // ...         ],         // ...     ];
zh-cn	#### 高级设置  可以在 Zabbix 前端配置文件 (*zabbix.conf.php*) 中配置额外的 SAML 参数：  - $SSO\['SP\_KEY'\] = '<SP 私钥文件的路径>'; - $SSO\['SP\_CERT'\] = '<SP 证书文件的路径>'; - $SSO\['IDP\_CERT'\] = '<IDP 证书文件的路径>'; -  $SSO\['设置'\]  ::: noteclass  Zabbix 使用 [OneLogin 的 SAML PHP Toolkit](https://github.com/onelogin/php-saml/tree/3.4.1) 库（版本 3.4.1）。 $SSO\['SETTINGS'\] 部分的结构应该与库使用的结构相似。配置选项的说明见官方库[文档](https://github.com/onelogin/php-saml/tree/3.4.1/#user-content-settings)。  :::  只有以下选项可以设置为 $SSO\['SETTINGS'\] 的一部分：  -  *strict* - *baseurl* - *compress* - *contactPerson* - *organization* - *sp*（仅在此列表中指定的选项）  - *attributeConsumingService*  - *x509certNew* - *idp*（仅在此列表中指定的选项）   - *singleLogoutService*（只有一个选项）   -  *responseUrl*   - *certFingerprint*   -  *certFingerprintAlgorithm*   - *x509certMulti* - *security*（仅在此列表中指定的选项）  -  *signMetadata*  · - *wantNameId*   - *requestedAuthnContext*  - *requestedAuthnContextComparison*  - *wantXMLValidation*  - *relaxDestinationValidation*  - *destinationStrictlyMatches*  - *rejectUnsolicitedResponsesWithInResponseTo*  - *签名算法*  - *digestAlgorithm*  - *小写Urlencoding*  所有其他选项将从数据库中获取并且不能被覆盖。 *debug* 选项将被忽略。  此外，如果 Zabbix UI 位于代理或负载均衡器之后，则可以使用自定义 *use\_proxy\_headers* 选项：  - *false* (默认) - 忽略该选项； - *true* - 使用 X-Forwarded-\* HTTP 标头来构建基本 URL。  如果使用负载均衡器连接到 Zabbix 实例，其中负载均衡器使用 TLS/SSL 而 Zabbix 不使用，您必须指明 'baseurl'、'strict' 和 'use_proxy_headers' 参数，如下所示：    $SSO_SETTINGS=['strict' => false, 'baseurl' => "https://zabbix.example.com/zabbix/", 'use_proxy_headers' => true] **配置示例：**    $SSO['SETTINGS'] = [   'security' => [   'signatureAlgorithm' => 'http://www.w3.org/2001/04/xmldsig-more#rsa-sha384'   'digestAlgorithm' => 'http://www.w3.org/2001/04/xmldsig-more#sha384',   // ...  ],   // ...  ];

en-us	After receiving a list of active checks the agent marks obsolete persistent files for removal. A persistent file becomes obsolete if: 1) the corresponding log item is no longer monitored, 2) a log item is reconfigured with a different **persistent\_dir** location than before.  Removing is done with delay 24 hours because log files in NOTSUPPORTED state are not included in the list of active checks but they may become SUPPORTED later and their persistent files will be useful.  If the agent is stopped before 24 hours expire, then the obsolete files will not be deleted as Zabbix agent is not getting info about their location from Zabbix server anymore.  ::: notewarning Reconfiguring a log item's **persistent\_dir** back to the old **persistent\_dir** location while the agent is stopped, without deleting the old persistent file by user - will cause restoring the agent state from the old persistent file resulting in missed messages or false alerts. :::  
zh-cn	在收到活动检查列表后，代理会将过时的持久文件标记为删除。如果出现以下情况，则持久文件将过时：1) 不再监视相应的日志项，2) 使用与以前不同的**persistent\_dir**位置重新配置日志项  删除会延迟 24 小时完成，因为处于 NOTSUPPORTED 状态的日志文件不包含在活动检查列表中，但它们可能会在稍后变为 SUPPORTED，并且它们的持久文件将很有用。  如果代理在 24 小时到期之前停止，则不会删除过时的文件，因为 Zabbix agent不再从 Zabbix server获取有关其位置的信息。   ::: 注意 在代理停止时，将日志项 **persistent\_dir** 重新配置回旧的 **persistent\_dir** 位置，用户没有删除就的持久文件 - 将导致从旧的持久化文件中恢复代理状态，从而导致丢失消息或错误告警。 :::

en-us	##### Agent 2  |Requirement|Status|Description| |-----------|------|-----------| |*libpcre*|Mandatory|PCRE library is required for [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) support.<br>The naming may differ depending on the GNU/Linux distribution, for example 'libpcre3' or 'libpcre1'. PCRE v8.x and PCRE2 v10.x (from Zabbix 6.0.0) are supported. | |*OpenSSL*|Optional|Required when using encryption.<br>OpenSSL 1.0.1 or later is required on UNIX platforms.<br>The OpenSSL library must have PSK support enabled. LibreSSL is not supported.<br>On Microsoft Windows systems OpenSSL 1.1.1 or later is required.|
zh-cn	##### Agent 2  |需求|状态|描述| |-----------|------|-----------| |*libpcre*|强制|PCRE 库 被 [Perl 兼容正则表达式](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) 支持 所需要。<br> 命名可能因 GNU/Linux 发行版而异，例如 'libpcre3' 或 'libpcre1'。(Zabbix 6.0.0)支持 PCRE v8.x 及 PCRE2 v10.x。| |*OpenSSL*|可选|当使用加密时需要。<br>UNIX 平台上需要 OpenSSL 1.0.1 或更高版本。<br>OpenSSL 库必须启用 PSK 支持。不支持 LibreSSL。<br> 在 Microsoft Windows 系统上需要 OpenSSL 1.1.1 及以上版本。|

en-us	##### Agent configuration  HA cluster nodes (servers) must be listed in the configuration of  Zabbix agent or Zabbix agent 2.  ![](../../../../assets/en/manual/config/zabbix_ha_agent.png)  To enable passive checks, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_agentd), separated by a **comma**.  ``` Server=zabbix-node-01,zabbix-node-02 ```  To enable active checks, the node names must be listed in the ServerActive [parameter](/manual/appendix/config/zabbix_agentd). Note that for  active checks the nodes must be separated by a comma from any other  servers, while the nodes themselves must be separated by a **semicolon**, e.g.:  ``` ServerActive=zabbix-node-01;zabbix-node-02 ```
zh-cn	 ##### Agent 配置  Zabbix agent 或者 Zabbix agent 2.必须将HA 集群节点列入配置文件。  ![](../../../../assets/en/manual/config/zabbix_ha_agent.png)  启用被动检查agent, 节点名称必须列入Server[参数](/manual/appendix/config/zabbix_agentd), 使用**逗号**分隔.  ``` Server=zabbix-node-01,zabbix-node-02 ```  启用主动检查agent, 节点名称必须列入ServerActive[参数](/manual/appendix/config/zabbix_agentd). 注意，对于主动检查agent，节点与其他server之间必须用逗号分隔，而节点本身必须用**分号**分隔，例如:  ``` ServerActive=zabbix-node-01;zabbix-node-02 ```

en-us	 ### Agent data request  The agent data request contains the gathered item values.  | Field |<| Type | Mandatory | Value | |-|------|--|-|-----------------------| | request |<| _string_ | yes | `agent data` | | host |<| _string_ | yes | Host name. | | version |<| _string_ | yes | The agent version: \<major>.\<minor>. | | session |<| _string_ | yes | Unique session identifier generated each time when agent is started. | | data |<| _array of objects_ | yes | Item values. | | | id | _number_ | yes | The value identifier (incremental counter used for checking duplicated values in the case of network problems). | |^| itemid | _number_ | yes | Item identifier. | |^| value | _string_ | no | The item value. | |^| lastlogsize | _number_ | no | The item lastlogsize. | |^| mtime | _number_ | no | The item mtime. | |^| state | _number_ | no | The item state. | |^| source | _string_ | no | The value event log source. | |^| eventid | _number_ | no | The value event log eventid. | |^| severity | _number_ | no | The value event log severity. | |^| timestamp | _number_ | no | The value event log timestamp. | |^| clock | _number_ | yes | The value timestamp (seconds since Epoch). | |^| ns | _number_ | yes | The value timestamp nanoseconds. |  Example: ```json {   "request": "agent data",   "data": [     {       "id": 1,       "itemid": 5678,       "value": "2.4.0",       "clock": 1400675595,       "ns": 76808644     },     {       "id": 2,       "itemid": 1234,       "lastlogsize": 112,       "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).",       "clock": 1400675595,       "ns": 77053975     }   ],   "host": "Zabbix server",   "version": "6.0",   "session": "1234456akdsjhfoui" } ```
zh-cn	### Agent数据请求  Agent数据请求包含收集的监控项值。  | 字段|<| 类型 | 必填 | 值 | |-|------|--|-|------------------------| | request |<| _字符串_ | 是 | `agent数据` | | host|<| _字符串_ | 是 | 主机名。 | | version|<| _字符串_ | 是 | agent版本：\<major>.\<minor>。 | | session|<| _字符串_ | 是 | 每次启动agent时生成的唯一会话标识符。 | | data |<| _对象数组_ | 是 | 监控项值。 | | | id | 数字 | 是 | 值标识符（用于在出现网络问题时检查重复值的增量计数器）。 | |^| itemid | 数字 | 是 | 监控项标识符。 | |^| value | _字符串_ | 否 | 物品价值。 | |^| lastlogsize | 数字 | 否 | 该监控项最后日志大小。 | |^| mtime | 数字 | 否 | 监控项时间。 | |^| state | 数字 | 否 | 监控项状态。 | |^| source | _字符串_ | 否 | 事件日志源。 | |^| eventid | 数字 | 否 | 事件日志eventid。 | |^| severity | 数字 | 否 | 事件日志严重性。 | |^| timestamp | 数字 | 否 | 事件日志时间戳。 | |^| clock | 数字 | 是 | 时间戳（自纪元以来的秒数）。 | |^| ns | 数字 | 是 | 时间戳纳秒。 |  示例： ```json {  · "request": "agent data",  · "data": [  · {  · "id": 1,  · "itemid": 5678,  · "value": "2.4.0",  · "clock": 1400675595,  · "ns": 76808644  · },  · {  · "id": 2,  · "itemid": 1234,  · "lastlogsize": 112,  · "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).",  · "clock": 1400675595,  · "ns": 77053975  · }  · ],  · "host": "Zabbix server",  · "version": "6.0",  · "session": "1234456akdsjhfoui" } ```

en-us	 ### Agent data response  The agent data response is sent by the server back to agent after processing the agent data request.  | Field | Type | Mandatory | Value | |-|-|-|--------| | response | _string_ | yes | `success` \| `failed` | | info | _string_ | yes | Item processing results. |  Example: ```json {   "response": "success",   "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ```
zh-cn	### Agent数据响应  agent数据响应在处理agent数据请求后由服务器发送回agent。  | 字段 | 类型 | 必填 | 值 | |-|-|-|--------| | response | _字符串_ | 是 | `成功`\| `失败` | | info | _字符串_ | 是 | 监控项处理结果。 |  例子： ```json {  · "response": "success",  · "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ```

en-us	#### Agent on UNIX-like systems  Zabbix agent on UNIX-like systems is run on the host being monitored.
zh-cn	#### 类 UNIX 系统上的 Agent  类 UNIX 系统上的 Zabbix agent 运行在被监控的主机上。

en-us	#### Agent on Windows systems  Zabbix agent on Windows runs as a Windows service.
zh-cn	 #### Windows 系统上的 Agent  Windows 系统上的 Zabbix agent 作为一个Windows服务运行。

en-us	##### Agent operation with persistent file  On startup Zabbix agent knows nothing about persistent files. Only after receiving a list of active checks from Zabbix server \(proxy\) the agent sees that some log items should be backed by persistent files under specified directories.  During agent operation the persistent files are opened for writing (with fopen(filename, "w")) and overwritten with the latest data.  The chance of losing persistent file data if the overwriting and file system mirror split happen at the same time is very small, no special handling for it.  Writing into persistent file is NOT followed by enforced synchronization to storage media \(fsync\(\) is not called\).  Overwriting with the latest data is done after successful reporting of matching log file record or metadata \(processed log size and modification time\) to Zabbix server. That may happen as often as every item check if log file keeps changing.  No special actions during agent shutdown.
zh-cn	##### 持久文件的代理操作  在启动时 Zabbix agent 对持久文件一无所知。只有在收到来自 Zabbix server \(proxy\)的活动检查列表后，代理才会看到某些日志项应该由指定目录下的持久文件支持。  在代理操作期间，持久文件被打开以进行写入（使用 fopen(filename, "w")）并用最新数据覆盖。如果同时发生覆盖和文件系统镜像拆分，丢失持久文件数据的机会非常小，无需特殊处理。写入持久文件后不会强制同步到存储介质（不调用  \(fsync\(\)\)。  在成功向 Zabbix server报告匹配的日志文件记录或元数据\(处理的日志大小和修改时间\)后，使用最新数据覆盖。这可能与每个监控项检查日志文件是否不断变化一样频繁。  代理关闭期间没有特殊操作。

en-us	#### Agent process types  -   `active checks` - process for performing active checks -   `collector` - process for data collection -   `listener` - process for listening to passive checks  The agent log file can be used to observe these process types.
zh-cn	 #### Agent 进程类型  -   `active checks` - 执行主动检查的进程 -   `collector` - 执行数据收集的进程 -   `listener` - 执行被动监控监听的进程  Agent日志文件可用于观察这些进程类型。

en-us	##### Agent  |Requirement|Status|Description| |-----------|------|-----------| |*libpcre*|Mandatory|PCRE library is required for [Perl Compatible Regular Expression](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) support.<br>The naming may differ depending on the GNU/Linux distribution, for example 'libpcre3' or 'libpcre1'. PCRE v8.x and PCRE2 v10.x (from Zabbix 6.0.0) are supported.| |*GnuTLS*, *OpenSSL* or *LibreSSL*|Optional|Required when using [encryption](/manual/encryption#compiling_zabbix_with_encryption_support).<br>On Microsoft Windows systems OpenSSL 1.1.1 or later is required.|  ::: noteclassic  Starting from version 5.0.3, Zabbix agent will not work on AIX platforms below versions 6.1 TL07 / AIX 7.1 TL01.  :::
zh-cn	##### Agent  |需求|状态|描述| |-----------|------|-----------| |*libpcre*|强制|PCRE 库 被 [Perl 兼容正则表达式](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE) 支持 所需要。<br> 命名可能因 GNU/Linux 发行版而异，例如 'libpcre3' 或 'libpcre1'。(Zabbix 6.0.0)支持 PCRE v8.x 及 PCRE2 v10.x。| |*GnuTLS*, *OpenSSL* or *LibreSSL*|可选|当使用 [加密](/manual/encryption#compiling_zabbix_with_encryption_support) 时需要。<br>在 Microsoft Windows 系统上需要 OpenSSL 1.1.1 及以上版本。|  ::: noteclassic 从 5.0.3 版本开始，Zabbix agent 将不再支持低于 6.1 TL07 / AIX 7.1 TL01 版本的 AIX 平台。 :::

en-us	#### Agent upgrade process  ::: noteimportant Upgrading agents is not mandatory. You only need to upgrade agents if it is required to access the new functionality. :::  The upgrade procedure described in this section may be used for upgrading both the Zabbix agent and the Zabbix agent 2.
zh-cn	#### Agent 升级步骤  ::: noteimportant 升级 agent 不是强制性的。只有在需要使用新功能时才需要升级 agent。 :::  本节的升级过程适用于升级 Zabbix agent 和 Zabbix agent2。

en-us	#### Agent upgrade process  ::: noteimportant Upgrading agents is not mandatory. You only need to upgrade agents if it is required to access the new functionality. :::  The upgrade procedure described in this section may be used for upgrading both the Zabbix agent and the Zabbix agent 2.  
zh-cn	#### Agent 升级步骤  ::: noteimportant 升级 agent 不是强制性的。只有在需要使用新功能时才需要升级 agent。 :::  本节的升级过程适用于升级 Zabbix agent 和 Zabbix agent2。

en-us	##### Agent  Zabbix agents are deployed on monitoring targets to actively monitor local resources and applications and report the gathered data to Zabbix server. Since Zabbix 4.4, there are two types of agents available: the [Zabbix agent](/manual/concepts/agent) (lightweight, supported on many platforms, written in C) and the [Zabbix agent 2](/manual/concepts/agent) (extra-flexible, easily extendable with plugins, written in Go).
zh-cn	##### Agent  Zabbix agent 部署在被监控目标上，以主动监控本地资源和应用程序，并将收集到的数据报告给 Zabbix server。从 Zabbix 4.4 开始，有两种类型的 agent 可用：[Zabbix agent](/manual/concepts/agent) （轻量级，在许多平台上支持，用 C 编写）和 [Zabbix agent 2](/manual/concepts/agent) （非常灵活，易于使用插件扩展，用 Go 编写）。

en-us	#### Aggregate functions  |FUNCTION|<|<|<| |--------|-|-|-| |<|**Description**|**Function-specific parameters**|**Comments**| |**avg** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Average value of an item within the defined evaluation period.|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Examples:<br>=> **avg**(/host/key,**1h**) → average value for the last hour until [now](/manual/config/triggers#evaluation_period)<br>=> **avg**(/host/key,**1h:now-1d**) → average value for an hour from 25 hours ago to 24 hours ago from [now](/manual/config/triggers#evaluation_period)<br>=> **avg**(/host/key,**\#5**) → average value of the five latest values<br>=> **avg**(/host/key,**\#5:now-1d**) → average value of the five latest values excluding the values received in the last 24 hours<br><br>Time shift is useful when there is a need to compare the current average value with the average value some time ago.| |**bucket\_percentile** (item filter,time period,percentage)|<|<|<| |<|Calculates the percentile from the buckets of a histogram.|**item filter** - see [item filter](/manual/appendix/functions/aggregate/foreach#item_filter)<br>**time period** - see [time period](/manual/appendix/functions/aggregate/foreach#time_period)<br>**percentage** - percentage (0-100)|Supported only in calculated items.<br><br>This function is an alias for `histogram_quantile(percentage/100, bucket_rate_foreach(item filter, time period, 1))`| |**count** (func\_foreach(item filter,<time period>))|<|<|<| |<|Count of values in an array returned by a foreach function.|**func\_foreach** - foreach function for which the number of returned values should be counted (with supported arguments). See [foreach functions](/manual/appendix/functions/aggregate/foreach) for details.|Supported value type: int<br><br>Example:<br>=> **count**(max\_foreach(/\*/net.if.in\[\*\],1h)) → number of net.if.in items that received data in the last hour until [now](/manual/config/triggers#evaluation_period)<br><br>Note that using **count()** with a history-related foreach function (max\_foreach, avg\_foreach, etc.) may lead to performance implications, whereas using **exists\_foreach()**, which works only with configuration data, will not have such effect.| |**histogram\_quantile** (quantile,bucket1,value1,bucket2,value2,...)|<|<|<| |<|Calculates the φ-quantile from the buckets of a histogram.|**quantile** - 0 ≤ φ ≤ 1<br>**bucketN, valueN** - manually entered pairs (>=2) of parameters or response of [bucket\_rate\_foreach](/manual/appendix/functions/aggregate/foreach)|Supported only in calculated items.<br><br>Functionally corresponds to '[histogram\_quantile](https://prometheus.io/docs/prometheus/latest/querying/functions/#histogram_quantile)' of PromQL.<br><br>Example:<br>=> **histogram\_quantile**(0.75,1.0,last(/host/rate\_bucket\[1.0\]),"+Inf",last(/host/rate\_bucket\[Inf\])<br>=> **histogram\_quantile**(0.5,bucket\_rate\_foreach(//item\_key,30s))| |**item\_count** (item filter)|<|<|<| |<|Count of existing items in configuration that match filter criteria.|**item filter** - criteria for item selection, allows referencing by host group, host, item key, and tags. Wildcards are supported. See [item filter](/manual/appendix/functions/aggregate/foreach#item_filter) for more details.|Supported value type: int<br><br>Works as an alias for the *count(exists\_foreach(item\_filter))* function.<br><br>Example:<br>=> **item\_count**(/\*/agent.ping?\[group="Host group 1"\]) → number of hosts with the *agent.ping* item in the "Host group 1"| |**kurtosis** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|"Tailedness" of the probability distribution in collected values within the defined evaluation period.<br><br>See also: [Kurtosis](https://en.wikipedia.org/wiki/Kurtosis)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **kurtosis**(/host/key,**1h**) → kurtosis for the last hour until [now](/manual/config/triggers#evaluation_period)| |**mad** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Median absolute deviation in collected values within the defined evaluation period.<br><br>See also: [Median absolute deviation](https://en.wikipedia.org/wiki/Median_absolute_deviation)|See [common-parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **mad**(/host/key,**1h**) → median absolute deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**max** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Highest value of an item within the defined evaluation period.|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **max**(/host/key,**1h**) - **min**(/host/key,**1h**) → calculate the difference between the maximum and minimum values within the last hour until [now](/manual/config/triggers#evaluation_period) (delta of values)| |**min** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Lowest value of an item within the defined evaluation period.|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **max**(/host/key,**1h**) - **min**(/host/key,**1h**) → calculate the difference between the maximum and minimum values within the last hour until [now](/manual/config/triggers#evaluation_period) (delta of values)| |**skewness** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Asymmetry of the probability distribution in collected values within the defined evaluation period.<br><br>See also: [Skewness](https://en.wikipedia.org/wiki/Skewness)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **skewness**(/host/key,**1h**) → skewness for the last hour until [now](/manual/config/triggers#evaluation_period)| |**stddevpop** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Population standard deviation in collected values within the defined evaluation period.<br><br>See also: [Standard deviation](https://en.wikipedia.org/wiki/Standard_deviation)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **stddevpop**(/host/key,**1h**) → population standard deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**stddevsamp** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sample standard deviation in collected values within the defined evaluation period.<br><br>See also: [Standard deviation](https://en.wikipedia.org/wiki/Standard_deviation)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>At least two data values are required for this function to work.<br><br>Example:<br>=> **stddevsamp**(/host/key,**1h**) → sample standard deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**sum** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sum of collected values within the defined evaluation period.|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **sum**(/host/key,**1h**) → sum of values for the last hour until [now](/manual/config/triggers#evaluation_period)| |**sumofsquares** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|The sum of squares in collected values within the defined evaluation period.|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **sumofsquares**(/host/key,**1h**) → sum of squares for the last hour until [now](/manual/config/triggers#evaluation_period)| |**varpop** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Population variance of collected values within the defined evaluation period.<br><br>See also: [Variance](https://en.wikipedia.org/wiki/Variance)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>Example:<br>=> **varpop**(/host/key,**1h**) → population variance for the last hour until [now](/manual/config/triggers#evaluation_period)| |**varsamp** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sample variance of collected values within the defined evaluation period.<br><br>See also: [Variance](https://en.wikipedia.org/wiki/Variance)|See [common parameters](#common-parameters).|Supported value types: float, int<br><br>At least two data values are required for this function to work.<br><br>Example:<br>=> **varsamp**(/host/key,**1h**) → sample variance for the last hour until [now](/manual/config/triggers#evaluation_period)|  
zh-cn	#### Aggregate functions  |FUNCTION|<|<|<| |--------|-|-|-| |<|**Description**|**Function-specific parameters**|**Comments**| |**avg** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Average value of an item within the defined evaluation period.|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Examples:<br>=> **avg**(/host/key,**1h**) → average value for the last hour until [now](/manual/config/triggers#evaluation_period)<br>=> **avg**(/host/key,**1h:now-1d**) → average value for an hour from 25 hours ago to 24 hours ago from [now](/manual/config/triggers#evaluation_period)<br>=> **avg**(/host/key,**\#5**) → average value of the five latest values<br>=> **avg**(/host/key,**\#5:now-1d**) → average value of the five latest values excluding the values received in the last 24 hours<br><br>Time shift is useful when there is a need to compare the current average value with the average value some time ago.| |**bucket\_percentile** (item filter,time period,percentage)|<|<|<| |<|Calculates the percentile from the buckets of a histogram.|**item filter** - see [item filter](/manual/appendix/functions/aggregate/foreach#item_filter)<br>**time period** - see [time period](/manual/appendix/functions/aggregate/foreach#time_period)<br>**percentage** - percentage (0-100)|Supported only in calculated items.<br><br>This function is an alias for `histogram_quantile(percentage/100, bucket_rate_foreach(item filter, time period, 1))`| |**count** (func\_foreach(item filter,<time period>))|<|<|<| |<|Count of values in an array returned by a foreach function.|**func\_foreach** - foreach function for which the number of returned values should be counted (with supported arguments). See [foreach functions](/manual/appendix/functions/aggregate/foreach) for details.|Supported value type: int<br><br>Example:<br>=> **count**(max\_foreach(/\*/net.if.in\[\*\],1h)) → number of net.if.in items that received data in the last hour until [now](/manual/config/triggers#evaluation_period)<br><br>Note that using **count()** with a history-related foreach function (max\_foreach, avg\_foreach, etc.) may lead to performance implications, whereas using **exists\_foreach()**, which works only with configuration data, will not have such effect.| |**histogram\_quantile** (quantile,bucket1,value1,bucket2,value2,...)|<|<|<| |<|Calculates the φ-quantile from the buckets of a histogram.|**quantile** - 0 ≤ φ ≤ 1<br>**bucketN, valueN** - manually entered pairs (>=2) of parameters or response of [bucket\_rate\_foreach](/manual/appendix/functions/aggregate/foreach)|Supported only in calculated items.<br><br>Functionally corresponds to '[histogram\_quantile](https://prometheus.io/docs/prometheus/latest/querying/functions/#histogram_quantile)' of PromQL.<br><br>Example:<br>=> **histogram\_quantile**(0.75,1.0,last(/host/rate\_bucket\[1.0\]),"+Inf",last(/host/rate\_bucket\[Inf\])<br>=> **histogram\_quantile**(0.5,bucket\_rate\_foreach(//item\_key,30s))| |**item\_count** (item filter)|<|<|<| |<|Count of existing items in configuration that match filter criteria.|**item filter** - criteria for item selection, allows referencing by host group, host, item key, and tags. Wildcards are supported. See [item filter](/manual/appendix/functions/aggregate/foreach#item_filter) for more details.|Supported value type: int<br><br>Works as an alias for the *count(exists\_foreach(item\_filter))* function.<br><br>Example:<br>=> **item\_count**(/\*/agent.ping?\[group="Host group 1"\]) → number of hosts with the *agent.ping* item in the "Host group 1"| |**kurtosis** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|"Tailedness" of the probability distribution in collected values within the defined evaluation period.<br><br>See also: [Kurtosis](https://en.wikipedia.org/wiki/Kurtosis)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **kurtosis**(/host/key,**1h**) → kurtosis for the last hour until [now](/manual/config/triggers#evaluation_period)| |**mad** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Median absolute deviation in collected values within the defined evaluation period.<br><br>See also: [Median absolute deviation](https://en.wikipedia.org/wiki/Median_absolute_deviation)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **mad**(/host/key,**1h**) → median absolute deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**max** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Highest value of an item within the defined evaluation period.|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **max**(/host/key,**1h**) - **min**(/host/key,**1h**) → calculate the difference between the maximum and minimum values within the last hour until [now](/manual/config/triggers#evaluation_period) (delta of values)| |**min** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Lowest value of an item within the defined evaluation period.|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **max**(/host/key,**1h**) - **min**(/host/key,**1h**) → calculate the difference between the maximum and minimum values within the last hour until [now](/manual/config/triggers#evaluation_period) (delta of values)| |**skewness** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Asymmetry of the probability distribution in collected values within the defined evaluation period.<br><br>See also: [Skewness](https://en.wikipedia.org/wiki/Skewness)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **skewness**(/host/key,**1h**) → skewness for the last hour until [now](/manual/config/triggers#evaluation_period)| |**stddevpop** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Population standard deviation in collected values within the defined evaluation period.<br><br>See also: [Standard deviation](https://en.wikipedia.org/wiki/Standard_deviation)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **stddevpop**(/host/key,**1h**) → population standard deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**stddevsamp** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sample standard deviation in collected values within the defined evaluation period.<br><br>See also: [Standard deviation](https://en.wikipedia.org/wiki/Standard_deviation)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>At least two data values are required for this function to work.<br><br>Example:<br>=> **stddevsamp**(/host/key,**1h**) → sample standard deviation for the last hour until [now](/manual/config/triggers#evaluation_period)| |**sum** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sum of collected values within the defined evaluation period.|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **sum**(/host/key,**1h**) → sum of values for the last hour until [now](/manual/config/triggers#evaluation_period)| |**sumofsquares** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|The sum of squares in collected values within the defined evaluation period.|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **sumofsquares**(/host/key,**1h**) → sum of squares for the last hour until [now](/manual/config/triggers#evaluation_period)| |**varpop** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Population variance of collected values within the defined evaluation period.<br><br>See also: [Variance](https://en.wikipedia.org/wiki/Variance)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>Example:<br>=> **varpop**(/host/key,**1h**) → population variance for the last hour until [now](/manual/config/triggers#evaluation_period)| |**varsamp** (/host/key,(sec\|\#num)<:time shift>)|<|<|<| |<|Sample variance of collected values within the defined evaluation period.<br><br>See also: [Variance](https://en.wikipedia.org/wiki/Variance)|See [common parameters](#common parameters).|Supported value types: float, int<br><br>At least two data values are required for this function to work.<br><br>Example:<br>=> **varsamp**(/host/key,**1h**) → sample variance for the last hour until [now](/manual/config/triggers#evaluation_period)|  

en-us	##### AIX, HP-UX  If `watch` command is not available, one can try      while [ 1 ]; do ps -fu zabbix; sleep 1; clear; done
zh-cn	##### AIX, HP-UX  如果`watch` 命令不可用，可以尝试      while [ 1 ]; do ps -fu zabbix; sleep 1; clear; done

en-us	#### AIX  See values supported for 'memtype' parameter on AIX in the table.  |Supported value|Description|Source in procentry64 structure|Tries to be compatible with| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|pi\_size| | |pmem|Percentage of real memory|pi\_prm|ps -o pmem| |rss|Resident set size|pi\_trss + pi\_drss|ps -o rssize| |size|Size of process (code + data)|pi\_dvm|"ps gvw" SIZE column| |dsize|Data size|pi\_dsize|<| |tsize|Text (code) size|pi\_tsize|"ps gvw" TSIZ column| |sdsize|Data size from shared library|pi\_sdsize|<| |drss|Data resident set size|pi\_drss| | |trss|Text resident set size|pi\_trss| |
zh-cn	#### AIX  请参阅表中 AIX 上“memtype”参数支持的值。  |支持值|说明|procentry64结构中来源|尽量兼容| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|虚拟内存大小|pi\_size| | |pmem|实际内存百分比|pi\_prm|ps -o pmem| |rss|常驻集大小|pi\_trss + pi\_drss|ps -o rssize| |size|进程大小（代码 + 数据）|pi\_dvm|“ps gvw”SIZE column| |dsize|数据大小|pi\_dsize|<| |tsize|文本（代码）大小|pi\_tsize|“ps gvw” TSIZ column| |sdsize|共享库的数据大小|pi\_sdsize|<| |drss|数据常驻集大小|pi\_drss| | |trss|文本常驻集大小|pi\_trss| |

en-us	#### Alerter process crash in Centos/RHEL 7  Instances of a Zabbix server alerter process crash have been encountered in Centos/RHEL 7. Please see [ZBX-10461](https://support.zabbix.com/browse/ZBX-10461) for details.
zh-cn	#### Alerter 进程在 Centos/RHEL 7 中崩溃  在 Centos/RHEL 7 中遇到了 Zabbix server 的 alerter 进程崩溃的情况。有关详细信息，请参阅 [ZBX-10461](https://support.zabbix.com/browse/ZBX-10461) 。

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

en-us	##### Alerting on service status change  It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes.  A new [service action](/manual/config/notifications/action) type has been added, similar to other actions in Zabbix. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem [escalation](/manual/config/notifications/action/escalations) scenarios.  New message templates *Service*, *Service recovery*, and *Service update* have been added to [media types](/manual/config/notifications/media#common_parameters) and should be defined to enable correct sending of notifications for service actions.
zh-cn	##### 服务状态变化告警  现在可以接收有关服务状态更改的自动警报，类似于有关触发器状态更改的警报。  添加了一种新的 [服务动作](/manual/config/notifications/action) 类型，类似于 Zabbix 中的其他动作。服务可能动作包括与服务相关的问题、恢复和更新动作的步骤。可以配置两种类型的动作：向指定的收件人发送消息和在 Zabbix server 上执行远程命令。与触发动作类似，服务动作支持问题 [升级](/manual/config/notifications/action/escalations)场景。  新的消息模板 *Service*、*Service recovery* 和 *Service update* 已添加到 [媒体类型](/manual/config/notifications/media#common_parameters) 中，应该定义为能够正确发送服务动作的通知。

en-us	##### Alerting on service status change  It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes.  A new [service action](/manual/config/notifications/action) type has been added to the *Actions* menu. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem [escalation](/manual/config/notifications/action/escalations) scenarios.  New message templates *Service*, *Service recovery*, and *Service update* have been added to [media types](/manual/config/notifications/media#common_parameters) and should be defined to enable correct sending of notifications for service actions.  
zh-cn	#### Alerting on service status change  It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes.  A new [service action](/manual/config/notifications/action) type has been added to the *Actions* menu. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem [escalation](/manual/config/notifications/action/escalations) scenarios.  New message templates *Service*, *Service recovery*, and *Service update* have been added to [media types](/manual/config/notifications/media#common_parameters) and should be defined to enable correct sending of notifications for service actions.  

en-us	### Alert  ::: noteclassic Alerts are created by the Zabbix server and cannot be modified via the API. :::  The alert object contains information about whether certain action operations have been executed successfully. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |alertid|string|ID of the alert.| |actionid|string|ID of the action that generated the alert.| |alerttype|integer|Alert type.<br><br>Possible values:<br>0 - message;<br>1 - remote command.| |clock|timestamp|Time when the alert was generated.| |error|string|Error text if there are problems sending a message or running a command.| |esc\_step|integer|Action escalation step during which the alert was generated.| |eventid|string|ID of the event that triggered the action.| |mediatypeid|string|ID of the media type that was used to send the message.| |message|text|Message text. Used for message alerts.| |retries|integer|Number of times Zabbix tried to send the message.| |sendto|string|Address, user name or other identifier of the recipient. Used for message alerts.| |status|integer|Status indicating whether the action operation has been executed successfully.<br><br>Possible values for message alerts:<br>0 - message not sent.<br>1 - message sent.<br>2 - failed after a number of retries.<br>3 - new alert is not yet processed by alert manager.<br><br>Possible values for command alerts:<br>0 - command not run.<br>1 - command run.<br>2 - tried to run the command on the Zabbix agent but it was unavailable.| |subject|string|Message subject. Used for message alerts.| |userid|string|ID of the user that the message was sent to.| |p\_eventid|string|ID of problem event, which generated the alert.| |acknowledgeid|string|ID of acknowledgment, which generated the alert.|
zh-cn	### 告警  ::: noteclassic 告警是由 Zabbix server 创建，无法通过 API 修改。 :::  告警对象包含有关某些动作操作是否已成功执行的信息。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |alertid|string|告警 ID。| |actionid|string|生成告警的动作 ID。| |alerttype|integer|告警类型。<br><br>可用值：<br>0 - 消息；<br>1 - 远程命令。| |clock|timestamp|告警生成的时间。| |error|string|发送消息或运行命令时出现问题时的错误文本。| |esc\_step|integer|告警生成期间的动作升级步骤。| |eventid|string|触发动作的事件 ID。| |mediatypeid|string|用于发送消息的媒体类型 ID。| |message|text|消息文本。用于消息告警。| |retries|integer| Zabbix 尝试发送消息的次数。| |sendto|string|地址，用户名或接收者的其他标识符。用于消息 alert。| |status|integer|指示动作操作是否已成功执行的状态。<br><br>消息告警的可用值：<br>0 - 消息未发送。<br>1 - 消息已发送。<br>2 - 经多次重试后失败。<br>3 - 告警管理员尚未处理的新告警。<br><br>命令告警可用值：<br>0 - 命令没有运行。<br>1 - 命令运行成功。<br>2 - 尝试在 Zabbix agent 上运行命令但不可用。| |subject|string|消息主题。用于消息告警。| |userid|string|消息发送到的用户的 ID。| |p\_eventid|string|生成告警的问题事件的 ID。| |acknowledgeid|string|生成告警的确认 ID。|

en-us	### Alert  ::: noteclassic Alerts are created by the Zabbix server and cannot be modified via the API. :::  The alert object contains information about whether certain action operations have been executed successfully. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |alertid|string|ID of the alert.| |actionid|string|ID of the action that generated the alert.| |alerttype|integer|Alert type.<br><br>Possible values:<br>0 - message;<br>1 - remote command.| |clock|timestamp|Time when the alert was generated.| |error|string|Error text if there are problems sending a message or running a command.| |esc\_step|integer|Action escalation step during which the alert was generated.| |eventid|string|ID of the event that triggered the action.| |mediatypeid|string|ID of the media type that was used to send the message.| |message|text|Message text. Used for message alerts.| |retries|integer|Number of times Zabbix tried to send the message.| |sendto|string|Address, user name or other identifier of the recipient. Used for message alerts.| |status|integer|Status indicating whether the action operation has been executed successfully.<br><br>Possible values for message alerts:<br>0 - message not sent.<br>1 - message sent.<br>2 - failed after a number of retries.<br>3 - new alert is not yet processed by alert manager.<br><br>Possible values for command alerts:<br>0 - command not run.<br>1 - command run.<br>2 - tried to run the command on the Zabbix agent but it was unavailable.| |subject|string|Message subject. Used for message alerts.| |userid|string|ID of the user that the message was sent to.| |p\_eventid|string|ID of problem event, which generated the alert.| |acknowledgeid|string|ID of acknowledgment, which generated the alert.|
zh-cn	### 告警  ::: noteclassic 告警是由 Zabbix server 创建，无法通过 API 修改。 :::  告警对象包含有关某些动作操作是否已成功执行的信息。它具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |alertid|string|告警 ID。| |actionid|string|生成告警的动作 ID。| |alerttype|integer|告警类型。<br><br>可用值：<br>0 - 消息；<br>1 - 远程命令。| |clock|timestamp|告警生成的时间。| |error|string|发送消息或运行命令时出现问题时的错误文本。| |esc\_step|integer|告警生成期间的动作升级步骤。| |eventid|string|触发动作的事件 ID。| |mediatypeid|string|用于发送消息的媒体类型 ID。| |message|text|消息文本。用于消息告警。| |retries|integer| Zabbix 尝试发送消息的次数。| |sendto|string|地址，用户名或接收者的其他标识符。用于消息 alert。| |status|integer|指示动作操作是否已成功执行的状态。<br><br>消息告警的可用值：<br>0 - 消息未发送。<br>1 - 消息已发送。<br>2 - 经多次重试后失败。<br>3 - 告警管理员尚未处理的新告警。<br><br>命令告警可用值：<br>0 - 命令没有运行。<br>1 - 命令运行成功。<br>2 - 尝试在 Zabbix agent 上运行命令但不可用。| |subject|string|消息主题。用于消息告警。| |userid|string|消息发送到的用户的 ID。| |p\_eventid|string|生成告警的问题事件的 ID。| |acknowledgeid|string|生成告警的确认 ID。|

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

en-us	# Alert  This class is designed to work with alerts.  Object references:\  -   [Alert](/manual/api/reference/alert/object#alert)  Available methods:\  -   [alert.get](/manual/api/reference/alert/get) - retrieve alerts
zh-cn	# 告警  这个对象用于操作告警。  对象参考：\  -   [Alert](/manual/api/reference/alert/object#告警)  可用方法：\  -   [alert.get](/manual/api/reference/alert/get) - 获取告警

en-us	 All of these parameters can be changed in *Administration* → *General* → *Housekeeping* after the installation.  ::: notetip You may want to run the timescaledb-tune tool provided by TimescaleDB to optimize PostgreSQL configuration parameters in your `postgresql.conf`. :::
zh-cn	安装后，所有这些参数都可以在 *Administration* → *General* → *Housekeeping* 中更改。  ::: notetip 您可能需要运行 TimescaleDB 提供的 timescaledb-tune 工具来优化 `postgresql.conf` 中的 PostgreSQL 配置参数。 ::::

en-us	##### Allow specific check, deny others  -   Whitelist specific checks with AllowKey parameters, deny others with     `DenyKey=*`  For example:      # Allow reading logs:     AllowKey=vfs.file.*[/var/log/*]      # Allow localtime checks     AllowKey=system.localtime[*]      # Deny all other keys     DenyKey=*
zh-cn	##### 允许特定检查，拒绝其他检查  - 使用 AllowKey 参数将特定检查列入白名单，使用DenyKey=*拒绝其他检查     `DenyKey=*`  例如：      # 允许阅读日志：     AllowKey=vfs.file.*[/var/log/*]      # 允许本地时间检查     AllowKey=system.localtime[*]      # 拒绝所有其他键     DenyKey=*

en-us	 ### AND/OR evaluation in LLD filters  The evaluation of AND/OR expressions in the low-level discovery filters/overrides may fail in this version. Fixed in Zabbix 6.0.12.
zh-cn	### AND/OR 评估 LLD 过滤器  在此版本中，底层发现过滤器/覆盖中的 AND/OR 表达式的评估可能会失败。 在 Zabbix 6.0.12 中修复。

en-us	 ##### Anomaly detection  Zabbix 5.2 introduced new trend functions useful for baseline monitoring. However, they still require defining relative thresholds (e.g. check that web traffic in September, 2021 is less than 2x higher compared to September, 2020). There are use cases when such thresholds are hard to define. For instance, the web traffic of a new but highly popular web site can organically grow many times over a year but the growth rate is unknown. Yet, a sudden traffic spike due to DDOS attack must generate an alert regardless of organic traffic growth.  Anomaly detection algorithms do exactly this - find data that doesn't look normal (outliers) in a context of other values.  New [history function](/manual/appendix/functions/history) trendstl() has been added which uses 'decomposition' method to calculate the anomaly rate. It splits a single time series sequence into three other sequences:  -   trend sequence that only contains big changes in the original data (e.g. website traffic shows growth) -   season sequence that only contains seasonal changes (e.g. less website traffic in summer, more in autumn) -   remainder sequence that only contains residual values that can not be interpreted as parts of trend or season  ![](../../../assets/en/manual/introduction/stl_data.png)  Anomaly detection works with remainder sequence and checks if there are values that are too far from the majority of remainder values. "Far" means that the absolute value from the remainder sequence is N times greater than the standard or mean deviation.
zh-cn	##### 异常检测  Zabbix 5.2 引入了对基线监控有用的新趋势函数。但是，它们仍然需要定义相对阈值（例如，检查 2021 年 9 月的网络流量是否比 2020 年 9 月高出不到 2 倍）。存在难以定义此类阈值的用例。例如，一个新的但非常受欢迎的网站的网络流量可以在一年内自然增长很多倍，但增长速度是未知的。然而，无论自然流量增长如何，由于 DDOS 攻击导致的突然流量激增都必须生成警报。  异常检测算法正是这样做的——在其他值的上下文中查找看起来不正常的数据（异常值）。  添加了新的 [历史函数](/manual/appendix/functions/history) trendstl()，它使用 '分解' 方法来计算异常率。它将单个时间序列拆分为其他三个序列：  -   仅包含原始数据发生较大变化的趋势序列（例如网站流量显示增长） -   仅包含季节性变化的season序列（例如夏季网站流量较少，秋季较多） -   仅包含不能被解释为趋势或season的一部分的剩余值的剩余序列  ![](../../../assets/en/manual/introduction/stl_data.png)  异常检测与余数序列一起工作，并检查是否存在与大多数余数相差太远的值。"远" 表示余数序列的绝对值比标准差或平均差大 N 倍。

en-us	##### Another example with an inline regex modifier  Use of the following regular expression including multiple inline modifiers to match the characters after a specific line:      (?<=match (?i)everything(?-i) after this line\n)(?sx).*# we add s modifier to allow . match newline characters  ![regexp\_expr\_4\_new.png](../../assets/en/manual/regular_expressions/regexp_expr_4_new.png)  Chosen Expression type: "Result is TRUE". Characters after a specific line are matched.  ::: noteimportant  **g** modifier can't be specified in line. The list of available modifiers can be found in [pcresyntax man page](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16). For more information about PCRE syntax please refer to [PCRE HTML documentation](https://www.pcre.org/original/doc/html/pcrepattern.html).  :::
zh-cn	##### 另一个使用内联正则表达式修饰符的示例  使用以下包含多个内联修饰符的正则表达式来匹配特定行之后的字符：      (?<=match (?i)everything(?-i) after this line\n)(?sx).*# we add s modifier to allow . match newline characters  ![regexp\_expr\_4\_new.png](../../assets/en/manual/regular_expressions/regexp_expr_4_new.png)  选择的表达式类型："Result is TRUE（结果为真）"。匹配特定行之后的字符。  ::: noteimportant  **g** 修饰符不能在行中指定。可用修饰符列表可以参考 [pcresyntax 手册页](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16)。有关 PCRE 语法的更多信息，请参阅 [PCRE HTML文档](https://www.pcre.org/original/doc/html/pcrepattern.html)。 :::

en-us	##### API changes  See the list of [API changes](/manual/api/changes_5.4_-_6.0) in Zabbix 6.0.0.
zh-cn	##### API 更改  参阅Zabbix 6.0.0中的 [API changes](/manual/api/changes_5.4_-_6.0) 。

en-us	### API information  Retrieve the version of the Zabbix API so that your application could use version-specific features.  [API info API](/manual/api/reference/apiinfo)
zh-cn	### API 信息  检索Zabbix API的版本，以便应用程序可以使用特定于版本的功能。  [API info API](/manual/api/reference/apiinfo)

en-us	# API info  This class is designed to retrieve meta information about the API.  Available methods:\  -   [apiinfo.version](/manual/api/reference/apiinfo/version) -     retrieving the version of the Zabbix API
zh-cn	# API 信息  此类用于检索有关 API 的元信息。  可用方法：\  -   [apiinfo.version](/manual/api/reference/apiinfo/version) - 检索 Zabbix API 版本

en-us	# apiinfo.version
zh-cn	# 版本

en-us	#### API login  A large number of open user sessions can be created when using custom scripts with the `user.login` [method](/manual/api/reference/user/login) without a following `user.logout`.
zh-cn	#### API 登录  使用自定义脚本[方式](/manual/api/reference/user/login) 进行 `user.login` 登录而不执行  `user.logout`，会创建大量打开的用户会话。

en-us	#### API login  A large number of open user sessions can be created when using custom scripts with the `user.login` [method](/manual/api/reference/user/login) without a following `user.logout`.  
zh-cn	#### API 登录  使用自定义脚本[方式](/manual/api/reference/user/login) 进行 `user.login` 登录而不执行  `user.logout`，会创建大量打开的用户会话。

en-us	#### - API tokens  API tokens section allows to view tokens assigned to the user, edit token details and [create new tokens](/manual/web_interface/frontend_sections/administration/general#api_tokens). This section is only available to a user if *Manage API tokens* action is allowed in the [user role](/manual/web_interface/frontend_sections/administration/user_roles) settings.  ![](../../../assets/en/manual/web_interface/user_tokens.png){width="600"}  You may filter API tokens by name, expiry date, or status (enabled/disabled). Click on the token status in the list to quickly enable/disable a token. You may also mass enable/disable tokens by selecting them in the list and then clicking on the Enable/Disable buttons below the list.   ::: noteimportant  Users cannot view *Auth token* value of the tokens assigned to them in Zabbix. *Auth token* value is displayed only once - immediately after creating a token. If it has been lost, the token has to be regenerated.  :::
zh-cn	#### API 令牌  API 令牌部分允许查看分配给用户的令牌、编辑令牌详细信息和 [创建新令牌](/manual/web_interface/frontend_sections/administration/general#api_tokens)。 只有在 [用户角色](/manual/web_interface/frontend_sections/administration/user_roles) 设置中允许 *管理API令牌* 操作时，此部分才对用户可用。  ![](../../../assets/en/manual/web_interface/user_tokens.png){width="600"}  您可以按名称、到期日期或状态（启用/禁用）过滤 API 令牌。 单击列表中的令牌状态可快速启用/禁用令牌。 您还可以通过在列表中选择令牌然后单击列表下方的启用/禁用按钮来批量启用/禁用令牌。  ::: noteimportant   用户无法在 Zabbix 中查看分配给他们的令牌的 *Auth token* 值。 *Auth token* 值仅显示一次 - 在创建令牌后立即显示。 如果它已经丢失，则必须重新生成令牌。 :::

en-us	#### API Tokens  Manage authorization tokens.  [Token API](/manual/api/reference/token)
zh-cn	#### API Tokens  管理认证 tokens.  [Token API](/manual/api/reference/token)

en-us	#### - API tokens  This section allows to create and manage API tokens.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_tokens.png){width="600"}  You may filter API tokens by name, users to whom the tokens are assigned, expiry date, users that created tokens, or status (enabled/disabled). Click on the token status in the list to quickly enable/disable a token. You may also mass enable/disable tokens by selecting them in the list and then clicking on the *Enable/Disable* buttons below the list.  To create a new token, press *Create API token* button at the top right corner, then fill out the required fields in the token configuration screen:  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_token_conf.png)  |Parameter|Description| |---------|-----------| |Name|Token's visible name.| |User|User the token should be assigned to. To quickly select a user, start typing the username, first or last name, then select the required user from the auto-complete list. Alternatively, you can press the Select button and select a user from the full user list. A token can be assigned only to one user.| |Description|Optional token description.| |Set expiration date and time|Unmark this checkbox if a token should not have an expiry date.| |Expiry date|Click on the calendar icon to select token expiry date or enter the date manually in a format YYYY-MM-DD hh:mm:ss| |Enabled|Unmark this checkbox if you need to create a token in a disabled state.|  Press Add to create a token. On the next screen, copy and save in a safe place *Auth token* value **before closing the page**, then press Close. The token will appear in the list.  ::: notewarning  *Auth token* value cannot be viewed again later. It is only available immediately after creating a token. If you lose a saved token you will have to regenerate it and doing so will create a new authorization string.  :::  Click on the token name to edit the name, description, expiry date settings, or token status. Note, that it is not possible to change to which user the token is assigned. Press Update button to save changes. If a token has been lost or exposed, you may press Regenerate button to generate new token value. A confirmation dialog box will appear, asking you to confirm this operation since after proceeding the previously generated token will become invalid.  Users without access to the *Administration* menu section can see and modify details of tokens assigned to them in the *User profile → API tokens* [section](/manual/web_interface/user_profile#api_tokens) only if *Manage API tokens* is allowed in their [user role](/manual/web_interface/frontend_sections/administration/user_roles) permissions.
zh-cn	#### - API 令牌  此部分允许创建和管理 API 令牌。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_tokens.png){width="600"}  您可以按名称、分配令牌的用户、到期日期、创建令牌的用户或状态（启用/禁用）过滤 API 令牌。单击列表中的令牌状态可快速启用/禁用令牌。您还可以通过在列表中选择令牌然后单击列表下方的*启用/禁用*按钮来批量启用/禁用令牌。  要创建新令牌，请按右上角的 *Create API token* 按钮，然后在令牌配置屏幕中填写必填字段：  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_token_conf.png)  |参数|说明| |---------|------------| |名称|令牌的可见名称。| |User|应将令牌分配给的用户。要快速选择用户，请开始输入用户名、名字或姓氏，然后从自动完成列表中选择所需的用户。或者，您可以按选择按钮并从完整用户列表中选择一个用户。一个令牌只能分配给一个用户。| |描述|可选的令牌描述。| |设置到期日期和时间|如果令牌不应有到期日期，请取消标记此复选框。| |到期日期|单击日历图标选择令牌到期日期或手动输入日期，格式为 YYYY-MM-DD hh:mm:ss| |启用|如果您需要在禁用状态下创建令牌，请取消选中此复选框。|  按添加以创建令牌。在下一个屏幕上，复制并保存在安全的地方 *Auth token* 值**在关闭页面之前**，然后按关闭。令牌将出现在列表中。  ::: notewarning  *Auth token* 值以后无法再次查看。它仅在创建令牌后立即可用。如果您丢失了保存的令牌，您将不得不重新生成它，这样做会创建一个新的授权字符串。 :::  单击令牌名称以编辑名称、描述、到期日期设置或令牌状态。请注意，无法更改令牌分配给哪个用户。按更新按钮保存更改。如果令牌丢失或暴露，您可以按 Regenerate 按钮生成新的令牌值。将出现一个确认对话框，询问您确认此操作，因为在此操作之后生成的令牌将变得无效。  仅当在其 [用户角色](/manual/web_interface/frontend_sections/administration/user_roles)权限中允许*管理 API 令牌* 时，无法访问 *管理* 菜单部分的用户才能在 *用户配置文件 → API 令牌* [部分](/manual/web_interface/user_profile#api_tokens)中查看和修改分配给他们的令牌的详细信息。

en-us	### API versions  To simplify API versioning, since Zabbix 2.0.4, the version of the API matches the version of Zabbix itself. You can use the [apiinfo.version](/manual/api/reference/apiinfo/version) method to find out the version of the API you're working with. This can be useful for adjusting your application to use version-specific features.  We guarantee feature backward compatibility inside of a major version. When making backward incompatible changes between major releases, we usually leave the old features as deprecated in the next release, and only remove them in the release after that. Occasionally, we may remove features between major releases without providing any backward compatibility. It is important that you never rely on any deprecated features and migrate to newer alternatives as soon as possible.  ::: notetip You can follow all of the changes made to the API in the [API changelog](/manual/api/changes_5.4_-_6.0). :::
zh-cn	### API 版本  为了简化API版本控制，自 Zabbix 2.0.4 开始，API 的版本与 Zabbix 本身的版本相匹配。你可以使用 [apiinfo.version](/manual/api/reference/apiinfo/version) 方法查找你正在使用的 API 的版本。 这对于调整应用程序以使用特定于版本的功能非常有用。  我们保证在主要版本内部具有向后兼容性。在主要版本之间进行向后不兼容的更改时，通常会在下一个版本中保留旧功能，并在之后的版本中将其删除。有时，我们可能会在不提供任何向后兼容性的情况下删除主要版本之间的功能。重要的是，永远不要依赖任何已弃用的功能，并尽快迁移到较新的替代项。  ::: notetip 你可以在 [API changelog](/manual/api/changes_3.4_-_4.0)  中跟踪对API所做的所有更改。 :::

en-us	# Appendix 1. Reference commentary
zh-cn	 # 附录 1. 参考说明

en-us	# Appendix 2. Changes from 5.4 to 6.0
zh-cn	 # 附录2. 从5.4到6.0的变更记录

en-us	#### Architecture  Zabbix consists of several major software components. Their responsibilities are outlined below.
zh-cn	#### 结构体系  Zabbix 由几个主要的软件组件组成。他们的职责概述如下。

en-us	#### A real life scenario  In this example, we would like to set up network discovery for the local network having an IP range of 192.168.1.1-192.168.1.254.  In our scenario we want to:  -   discover those hosts that have Zabbix agent running -   run discovery every 10 minutes -   add a host to monitoring if the host uptime is more than 1 hour -   remove hosts if the host downtime is more than 24 hours -   add Linux hosts to the "Linux servers" group -   add Windows hosts to the "Windows servers" group -   use the template *Linux* for Linux hosts -   use the template *Windows* for Windows hosts
zh-cn	#### 一个真实场景  在这个例子中，会演示如何给本地IP地址范围192.168.1.1-192.168.1.254设置网络发现规则。  需要在这个场景中实现：  -   发现运行了Zabbix agent的主机 -   每十分钟执行一次发现 -   如果主机运行时长大于一小时，添加该主机到监控中 -   如果主机停机时长大于二十四小时，则删除主机 -   添加Linux主机到"Linux服务器"组中 -   添加Windows主机到"Windows服务器"组中 -   给Linux主机使用 *Linux* 模板 -   给Windows主机使用 *Windows* 模板

en-us	##### AS/400  IBM AS/400 platform can be monitored using SNMP. More information is available at <http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg244504.html?Open>.
zh-cn	##### AS/400  IBM AS/400 平台可以使用 SNMP 进行监控。如需更多信息，请访问 <http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg244504.html?Open>。

en-us	#### Assigning different hosts  Replace the hosts currently assigned to maintenance "3" with two different ones.  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "maintenance.update",     "params": {         "maintenanceid": "3",         "hostids": [             "10085",             "10084"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```  
zh-cn	#### Assigning different hosts 指定不同的主机  Replace the hosts currently assigned to maintenance "3" with two different ones. 用两个不同的主机替换当前分配给维护“3”的主机。  Request:  ``` {.java} {     "jsonrpc": "2.0",     "method": "maintenance.update",     "params": {         "maintenanceid": "3",         "hostids": [             "10085",             "10084"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```  

en-us	#### Assigning different hosts  Replace the hosts currently assigned to maintenance with two different ones.  Request:  ```json {     "jsonrpc": "2.0",     "method": "maintenance.update",     "params": {         "maintenanceid": "3",         "hosts": [             {"hostid": "10085"},             {"hostid": "10084"}         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```
zh-cn	#### 指定不同的主机  用两个不同的主机替换当前分配给维护周期“3”的主机。  请求:  ```json {     "jsonrpc": "2.0",     "method": "maintenance.update",     "params": {         "maintenanceid": "3",         "hostids": [             "10085",             "10084"         ]     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": {         "maintenanceids": [             "3"         ]     },     "id": 1 } ```

en-us	#### Attempting to use Zabbix sender compiled with TLS support to send data to Zabbix server/proxy compiled without TLS
zh-cn	#### 尝试使用使用 TLS 支持编译的 Zabbix sender将数据发送到在没有 TLS 的情况下编译的 Zabbix Server/proxy

en-us	##### Attributes returning composite data  It becomes more complicated when your attribute returns composite data. For example: your attribute name is "apple" and it returns a hash representing its parameters, like "weight", "color" etc. Your key may look like this:      jmx[com.example:Type=Hello,apple.weight]  This is how an attribute name and a hash key are separated, by using a dot symbol. Same way, if an attribute returns nested composite data the parts are separated by a dot:      jmx[com.example:Type=Hello,fruits.apple.weight]
zh-cn	##### 属性返回复合数据  当您的属性返回复合数据时，它变得更加复杂。 例如：您的属性名称是"apple"，它返回一个表示其参数的哈希，如“重量”、“颜色”等。您的密钥可能看起来像这样：      jmx[com.example:Type=Hello,apple.weight]  这就是使用"."符号将属性名称和哈希键是如何分隔开。同样，如果一个属性返回嵌套的复合数据，那部分由"."分隔：      jmx[com.example:Type=Hello,fruits.apple.weight]

en-us	##### Attributes returning tabular data  Tabular data attributes consist of one or multiple composite attributes. If such an attribute is specified in the attribute name parameter then this item value will return the complete structure of the attribute in JSON format. The individual element values inside the tabular data attribute can be retrieved using preprocessing.  Tabular data attribute example:       jmx[com.example:type=Hello,foodinfo]  Item value:  ``` {.javascript} [   {     "a": "apple",     "b": "banana",     "c": "cherry"   },   {     "a": "potato",     "b": "lettuce",     "c": "onion"   } ] ```
zh-cn	##### 返回表格数据的属性  表格数据属性由一个或多个复合属性组成。 如果在属性名参数中指定了这样一个属性，那么这个监控项值将以JSON格式返回该属性的完整结构。 表格数据属性中的单个元素值可以使用预处理来检索。  表格数据属性示例:       jmx[com.example:type=Hello,foodinfo]  监控项值示例:  ``` {.javascript} [   {     "a": "apple",     "b": "banana",     "c": "cherry"   },   {     "a": "potato",     "b": "lettuce",     "c": "onion"   } ] ```

en-us	### Audit log  Audit log functionality has been reworked significantly. The updated Audit log contains records of all configuration changes of Zabbix objects and has an improved filter, which allows to view records grouped by frontend operation. Logging can be switched on or off in the *Administration→General* menu section. In order to implement these changes, the previously existing database structure had to be reworked. During an upgrade DB tables `auditlog` and `auditlog_details` will be replaced by the new table `auditlog` with a different format. **Existing audit log records will be deleted.**  
zh-cn	##### User macros in item name no longer supported  The support for user macros in item names (including discovery rule names), deprecated since Zabbix 4.0, has been fully removed.  

en-us	#### audit log  Changes:\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of property `note`.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `resourcetype` values `2` (Configuration of Zabbix) and `7` (Graph element).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `action` values `5` (Enable) and `6` (Disable).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`: dropped support of parameter `selectDetails`.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) Audit log object: dropped support of `action` value `3` (Login).\
zh-cn	 #### 审计日志  变更：\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对属性`note`的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对`resourcetype`值为 `2`（Zabbix 配置）和值为`7`（Graph 元素）的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对`action`值为`5`（可用） 和值 `6`（不可用）的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`：删除对参数 `selectDetails`的支持。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 审计日志对象：删除对`action`值为`3`（登录）的支持。\

en-us	#### audit log  Changes:\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of property `note`.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `resourcetype` values `2`(Configuration of Zabbix) and `7`(Graph element).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `action` values `5`(Enable) and `6`(Disable).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`: dropped support of parameter `selectDetails`.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) Audit log object: dropped support of `action` value `3` (Login).\  
zh-cn	#### audit log  Changes:\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of property `note`.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `resourcetype` values `2`(Configuration of Zabbix) and `7`(Graph element).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: dropped support of `action` values `5`(Enable) and `6`(Disable).\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`: dropped support of parameter `selectDetails`.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) Audit log object: dropped support of `action` value `3` (Login).\  

en-us	#### auditlog  Changes:\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) dropped support of property `note`.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) dropped support of `resourcetype` values *(2 - Configuration of Zabbix, 7 - Graph element)*.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) dropped support of `action` values *(5 - Enable, 6 - Disable)*.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) dropped support of `action` value *(3 - Login)*.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`: dropped support of parameter `selectDetails`.\
zh-cn	 #### 审计日志  变更：\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对属性`note`的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对`resourcetype`值为 `2`（Zabbix 配置）和值为`7`（Graph 元素）的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：删除对`action`值为`5`（可用） 和值 `6`（不可用）的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) `auditlog.get`：删除对参数 `selectDetails`的支持。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 审计日志对象：删除对`action`值为`3`（登录）的支持。\

en-us	#### auditlog Changes:\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) added new `resourcetype` *(48 - SLA)*.\ [ZBXNEXT-6923](https://support.zabbix.com/browse/ZBXNEXT-6923) added new `resourcetype` *(47 - High availability node)*.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) added support of `action` values *(8 - Login, 9 - Failed login, 10 - History clear)*.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) added support of properties: `username`, `recordsetid`, `details`.\
zh-cn	 #### 审计日志  变更：\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) 添加对`sla`资源的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：添加对属性`username`，`recordsetid`，`details`的支持。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 审计日志对象：添加对`action`值为`8`（登录），`9`（登录失败）和`10`（历史清除）的支持。\

en-us	#### audit log  Changes:\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) Added support for `sla` resource.\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) Audit log object: added support of properties `username`, `recordsetid`, `details`.\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) Audit log object: added support of `action` values `8` (Login), `9` (Failed login) and `10` (History clear).\
zh-cn	 #### 审计日志  变更：\ [ZBXNEXT-6999](https://support.zabbix.com/browse/ZBXNEXT-6999) 添加对`sla`资源的支持。\ [ZBXNEXT-6715](https://support.zabbix.com/browse/ZBXNEXT-6715) 审计日志对象：添加对属性`username`，`recordsetid`，`details`的支持。\ [ZBXNEXT-6718](https://support.zabbix.com/browse/ZBXNEXT-6718) 审计日志对象：添加对`action`值为`8`（登录），`9`（登录失败）和`10`（历史清除）的支持。\

en-us	 ### Audit log filter  Multiple actions now can be selected in the audit log filter in *Reports* -> *[Audit](/manual/web_interface/frontend_sections/reports/audit)*:  ![](../../../assets/en/manual/introduction/audit_log_filter_new.png){width="600"}  This is useful to see all related actions (for example, successful and failed logins into the frontend)  in the audit list.
zh-cn	### 审计日志过滤器  现在可以在  *报告* -> *[审计](/manual/web_interface/frontend_sections/reports/audit)*的审计日志过滤器中选择多个操作:  ![](../../../assets/en/manual/introduction/audit_log_filter_new.png){width="600"}  这有助于在审计列表中查看所有相关操作(例如，前端登录的成功和失败记录)。

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

en-us	### Audit log  In order to implement the changes in [audit log functionality](#audit-log), the  previously existing database structure had to be reworked. During the upgrade `auditlog` and `auditlog_details` DB tables will be replaced by the new table `auditlog` with a different format. **Existing audit log records will be deleted.**
zh-cn	### 审计日志  为了实现 [审计日志](#audit-log) 功能的变化，以前存在的数据库结构必须重新设计。在升级过程中`auditlog` ，`auditlog_details` 数据库表将被具有不同格式的新表 `auditlog` 替换。*现有的审核日志记录将被删除**。

en-us	 ##### Audit log  In order to improve audit logging in Zabbix and make the Audit log complete and reliable, the previously existing database structure had to be reworked. During an upgrade DB tables `auditlog` and `auditlog_details` will be replaced by the new table `auditlog` with a different format. **Old audit records will not be preserved.**  New [section](/manual/web_interface/frontend_sections/administration/general#audit_log) *Audit log* has been added to the *Administration→General* menu allowing to enable (default) or disable audit logging. Housekeeping settings for audit, previously located under the *Housekeeper* menu section, have also been moved to the new *Audit log* section. Existing housekeeping settings will be saved.
zh-cn	##### 审计日志  为了改进 Zabbix 中的审计日志，并使审计日志完整可靠，必须重新设计以前存在的数据库结构。在升级数据库表期间 `auditlog` 、`auditlog_details` 将被具有不同格式的新表 `auditlog` 取代。**旧的审计记录不会被保留**。  新的 *Audit log（审计日志）*  [单元](/manual/web_interface/frontend_sections/administration/general#audit_log)已添加到 *Administration（管理）→General（常规）* 菜单中，允许启用（默认）或禁用审计日志。以前位于 *Housekeeper（管家）* 菜单下的用于审计的管家设置也已移至新的 *Audit log（审计日志）* 单元。现有的管家设置将被保存。

en-us	# > Audit log object  The following objects are directly related to the `auditlog` API.
zh-cn	# > 审计日志对象  以下对象与 `auditlog` API 直接相关。

en-us	# Audit log  This class is designed to work with audit log.  Object references:\  -   [Audit log object](/manual/api/reference/auditlog/object)  Available methods:\  -   [auditlog.get](/manual/api/reference/auditlog/get) - retrieve audit     log records
zh-cn	# 审计日志  这个类用于操作审计日志。  对象参考：\  -   [Audit log object](/manual/api/reference/auditlog/object)  可用方法：\  -   [auditlog.get](/manual/api/reference/auditlog/get) - 获取审计日志记录

en-us	#### - Audit log  This section allows configuring audit log settings.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/audit_log.png)  The following parameters are available:  |Parameter|Description| |---------|-----------| |Enable audit logging|Enable/disable audit logging. Marked by default.| |Enable internal housekeeping|Enable/disable internal housekeeping for audit. Marked by default.| |Data storage period|Amount of days audit records should be kept for before being removed by the housekeeper. Mandatory if housekeeping is enabled. Default: 365 days.|
zh-cn	#### - 审计日志  此部分允许配置审核日志设置。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/audit_log.png)  以下参数可用：  |参数|说明| |---------|------------| |启用审计日志|启用/禁用审计日志。 默认选中。| |启用内部管理|启用/禁用内部管理以进行审计。 默认选中。| |数据存储期限|审核记录在被管家删除之前应保留的天数。 如果启用了管家服务，则为必需项。 默认值：365 天。|

en-us	##### Audit settings  New [section](/manual/web_interface/frontend_sections/administration/general#audit_log) *Audit log* has been added to the *Administration→General* menu allowing to enable or disable audit logging. Housekeeping settings for audit, previously located under the *Housekeeper* section, have also been moved to the new *Audit log* section.
zh-cn	##### 审计设置  新的 *Audit log*  [部分](/manual/web_interface/frontend_sections/administration/general#audit_log) 已添加到 *Administration→General* 菜单，允许启用或禁用审计日志。以前位于 *Housekeeper* 部分下的用于审核的管家设置也已移至新的 *Audit log* 部分。

en-us	#### Authenticating a user  Authenticate a user.  Request:  ```json {     "jsonrpc": "2.0",     "method": "user.login",     "params": {         "username": "Admin",         "password": "zabbix"     },     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": "0424bd59b807674191e7d77572075f33",     "id": 1 } ```
zh-cn	#### 单用户认证  单用户认证.  请求:  ```json {     "jsonrpc": "2.0",     "method": "user.login",     "params": {         "username": "Admin",         "password": "zabbix"     },     "id": 1 } ```  返回:  ```json {     "jsonrpc": "2.0",     "result": "0424bd59b807674191e7d77572075f33",     "id": 1 } ```

en-us	#### Authentication  Before you can access any data inside of Zabbix you'll need to log in and obtain an authentication token. This can be done using the [user.login](/manual/api/reference/user/login) method. Let us suppose that you want to log in as a standard Admin user. Then your JSON request will look like this:  ```json {     "jsonrpc": "2.0",     "method": "user.login",     "params": {         "user": "Admin",         "password": "zabbix"     },     "id": 1,     "auth": null } ```  Let's take a closer look at the request object. It has the following properties:  -   `jsonrpc` - the version of the JSON-RPC protocol used by the API;     the Zabbix API implements JSON-RPC version 2.0; -   `method` - the API method being called; -   `params` - parameters that will be passed to the API method; -   `id` - an arbitrary identifier of the request; -   `auth` - a user authentication token; since we don't have one yet,     it's set to `null`.  If you provided the credentials correctly, the response returned by the API will contain the user authentication token:  ```json {     "jsonrpc": "2.0",     "result": "0424bd59b807674191e7d77572075f33",     "id": 1 } ```  The response object in turn contains the following properties:  -   `jsonrpc` - again, the version of the JSON-RPC protocol; -   `result` - the data returned by the method; -   `id` - identifier of the corresponding request.
zh-cn	#### 认证  在访问 Zabbix 中的任何数据之前，你需要登录并获取身份认证 token。这可以使用 [user.login](/manual/api/reference/user/login) 方法完成。我们假设你想要以标准 Zabbix Admin 用户身份登录。那么，你的 JSON 请求将如下所示：  ``` {.json} {     "jsonrpc": "2.0",     "method": "user.login",     "params": {         "user": "Admin",         "password": "zabbix"     },     "id": 1,     "auth": null } ```  让我们仔细看看示例请求对象。它具有以下属性：  -   `jsonrpc` - API 使用的 JSON-RPC 协议的版本; Zabbix API 实现的 JSON-RPC 版本是2.0； -   `method` - 被调用的 API 方法； -   `params` - 将被传递给API方法的参数； -   `id` - 请求的任意标识符； -   `auth` - 用户认证 token；因为我们还没有，它被设置为 `null`。  如果你正确提供了凭据，API 返回的响应将包含用户身份认证 token：  ``` {.json} {     "jsonrpc": "2.0",     "result": "0424bd59b807674191e7d77572075f33",     "id": 1 } ```  响应对象包含以下属性：  -   `jsonrpc` - JSON-RPC 协议的版本； -   `result` - 方法返回的数据； -   `id` - 对应请求的标识符。

en-us	#### Authentication  Change authentication configuration options.  [Authentication API](/manual/api/reference/authentication)
zh-cn	#### 认证  更改身份认证配置选项。  [Authentication API](/manual/api/reference/authentication)

en-us	#### authentication  Changes:\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) added new password policy fields `passwd_min_length` and `passwd_check_rules`.\
zh-cn	 #### 身份认证  变更：\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) 添加新的密码策略字段`passwd_min_length`和`passwd_check_rules`。\

en-us	#### authentication  Changes:\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) added new password policy fields `passwd_min_length` and `passwd_check_rules`.\
zh-cn	 #### 身份认证  变更：\ [ZBXNEXT-4029](https://support.zabbix.com/browse/ZBXNEXT-4029) 添加新的密码策略字段`passwd_min_length`和`passwd_check_rules`。\

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

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

en-us	# Authentication  This class is designed to work with authentication settings.  Object references:\  -   [Authentication](/manual/api/reference/authentication/object#authentication)  Available methods:\  -   [authentication.get](/manual/api/reference/authentication/get) -     retrieve authentication -   [authentication.update](/manual/api/reference/authentication/update) -     update authentication
zh-cn	# 认证  此类用于操作认证设置。  对象引用：\  -   [Authentication](/manual/api/reference/authentication/object#认证)  可用方法：\  -   [authentication.get](/manual/api/reference/authentication/get) - 获取认证 -   [authentication.update](/manual/api/reference/authentication/update) - 更新认证

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

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <[[\[email protected\]]{.__cf_email__ cfemail="0d6c6168754d776c6f6f6475236e6260"}](/cdn-cgi/l/email-protection#e48588819ca49e8586868d9cca878b89)>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <[[\[email protected\]]{.__cf_email__ cfemail="0d6c6168754d776c6f6f6475236e6260"}](/cdn-cgi/l/email-protection#e48588819ca49e8586868d9cca878b89)>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <[[\[email protected\]]{.__cf_email__ cfemail="254449405d655f4447474c5d0b464a48"}](/cdn-cgi/l/email-protection#eb8a878e93ab918a89898293c5888486)>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <[[\[email protected\]]{.__cf_email__ cfemail="254449405d655f4447474c5d0b464a48"}](/cdn-cgi/l/email-protection#eb8a878e93ab918a89898293c5888486)>  ------------------------------------------------------------------------  [ ]{#index}

en-us	##### Authorization  |Parameter|Description| |---------|-----------| |*Login attempts*|Number of unsuccessful login attempts before the possibility to log in gets blocked.| |*Login blocking interval*|Period of time for which logging in will be prohibited when *Login attempts* limit is exceeded.|
zh-cn	##### 授权  |参数|说明| |---------|------------| |*登录尝试*|在登录被阻止之前的不成功登录尝试次数。| |*登录阻止间隔*|超过*登录尝试*限制时将禁止登录的时间段。| 

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Zabbix 有限责任公司  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	## 作者  Zabbix 有限责任公司  ------------------------------------------------------------------------  [ ]{#index}

en-us	##### Automated type selection  Item configuration form now automatically suggests the matching type of information, if selected item key returns data only of the specific type (for example, **log\[\]** item requires *Type of information: Log*). *Type of information* parameter is now located under the *Key* parameter on the primary *Item* tab and is duplicated on the *Preprocessing* tab if at least one preprocessing step is specified. If Zabbix detects a possible mismatch of the selected type of information and key, a warning icon will be displayed next to the *Type of information* field.
zh-cn	##### 自动类型选择  监控项配置表单会自动建议匹配的信息类型，如果选定的监控项键值仅返回特定类型的数据（例如，**log\[\]** 监控行需要信息类型：Log*）。 *信息类型* 参数现在位于*监控项*选项卡上的*键值*参数下，如果指定了至少一个预处理步骤，则在*预处理*选项卡上重复。如果 Zabbix 检测到所选信息类型和密钥可能不匹配，则会在 *信息类型* 字段旁边显示一个警告图标。

en-us	##### Automatic mode  Host inventory can also be populated automatically. For that to work, when configuring a host the inventory mode in the *Host inventory* tab must be set to *Automatic*.  Then you can [configure host items](/manual/config/items/item) to populate any host inventory field with their value, indicating the destination field with the respective attribute (called *Item will populate host inventory field*) in item configuration.  Items that are especially useful for automated inventory data collection:  -   system.hw.chassis\[full|type|vendor|model|serial\] - default is     \[full\], root permissions needed -   system.hw.cpu\[all|cpunum,full|maxfreq|vendor|model|curfreq\] -     default is \[all,full\] -   system.hw.devices\[pci|usb\] - default is \[pci\] -   system.hw.macaddr\[interface,short|full\] - default is \[all,full\],     interface is regexp -   system.sw.arch -   system.sw.os\[name|short|full\] - default is \[name\] -   system.sw.packages\[regexp,manager,short|full\] - default is     \[all,all,full\]
zh-cn	##### 自动模式  主机资产也可以自动填充。为了使自动填充功能生效，配置主机时 *资产记录*选项卡中的清单模式必须设置为 *自动*。  然后，在监控项配置中你可以通过[配置主机监控项](/zh/manual/config/items/item)用任意指示目的字段相应属性的值（即 *填充主机资产字段的监控项*）来配置对应的主机资产字段。  以下是对资产信息自动采集非常有用的监控项:  -   system.hw.chassis\[full|type|vendor|model|serial\] - 默认是 \[full\]，需要root权限 -   system.hw.cpu\[all|cpunum,full|maxfreq|vendor|model|curfreq\] - 默认是 \[all,full\] -   system.hw.devices\[pci|usb\] - 默认是 \[pci\] -   system.hw.macaddr\[interface,short|full\] - 默认是 \[all,full\]，interface 支持正则表达式 -   system.sw.arch -   system.sw.os\[name|short|full\] - 默认是 \[name\] -   system.sw.packages\[package,manager,short|full\] - 默认是 \[all,all,full\]，package 支持正则表达式

en-us	#### Autoregistration actions  The following conditions can be set for actions based on active agent autoregistration:  |Condition type|Supported operators|Description| |--------------|-------------------|-----------| |*Host metadata*|contains<br>does not contain<br>matches<br>does not match|Specify host metadata or host metadata to exclude.<br>**contains** - host metadata contains the string.<br>**does not contain** - host metadata does not contain the string.<br>Host metadata can be specified in an [agent configuration file](/manual/appendix/config/zabbix_agentd).<br>**matches** - host metadata matches regular expression.<br>**does not match** - host metadata does not match regular expression.| |*Host name*|contains<br>does not contain<br>matches<br>does not match|Specify a host name or a host name to exclude.<br>**contains** - host name contains the string.<br>**does not contain** - host name does not contain the string.<br>**matches** - host name matches regular expression.<br>**does not match** - host name does not match regular expression.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|  
zh-cn	#### 自动注册动作  可以为基于主动式agent自动注册的动作设置以下条件:  |条件类型|支持的操作符|说明| |--------------|-------------------|-----------| |*Host metadata*|contains<br>does not contain<br>matches<br>does not match|主机元数据或要排除的主机元数据<br>**contains** - 主机元数据包含该字符串<br>**does not contain** - 主机元数据不包含该字符串<br>关于主机元数据请参见 [agent configuration file](/manual/appendix/config/zabbix_agentd).<br>**matches** - 主机元数据匹配该正则表达式<br>**does not match** - 主机元数据不匹配该正则表达式| |*Host name*|contains<br>does not contain<br>matches<br>does not match|主机名或要排除的主机名<br>**contains** - 主机名包含该字符串<br>**does not contain** - 主机名不包含该字符串<br>**matches** - 主机名匹配该正则表达式<br>**does not match** - 主机名不匹配该正则表达式| |*Proxy*|equals<br>does not equal|使用的Zabbix代理或要排除的Zabbix代理<br>**equals** - 使用该代理<br>**does not equal** - 使用此代理以外的其它代理|  

en-us	#### Autoregistration actions  The following conditions can be used in actions based on active agent autoregistration:  |Condition type|Supported operators|Description| |--|--|------| |*Host metadata*|contains<br>does not contain<br>matches<br>does not match|Specify host metadata or host metadata to exclude.<br>**contains** - host metadata contains the string.<br>**does not contain** - host metadata does not contain the string.<br>Host metadata can be specified in an [agent configuration file](/manual/appendix/config/zabbix_agentd).<br>**matches** - host metadata matches regular expression.<br>**does not match** - host metadata does not match regular expression.| |*Host name*|contains<br>does not contain<br>matches<br>does not match|Specify a host name or a host name to exclude.<br>**contains** - host name contains the string.<br>**does not contain** - host name does not contain the string.<br>**matches** - host name matches regular expression.<br>**does not match** - host name does not match regular expression.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|
zh-cn	#### 自动注册操作  以下条件可用于基于活动agent自动注册的操作：  |条件类型|支持的运算符|说明| |--|--|------| |*Host metadata*|包含<br>不包含<br>匹配<br>不匹配|指定主机元数据或要排除的主机元数据。<br>**包含** - 主机元数据包含字符串。<br >**不包含** - 主机元数据不包含字符串。<br>主机元数据可以在[agent配置文件](/manual/appendix/config/zabbix_agentd)中指定。<br>**匹配* * - 主机元数据与正则表达式匹配。<br>**不匹配** - 主机元数据与正则表达式不匹配。| |*Host name*|包含<br>不包含<br>匹配<br>不匹配|指定主机名或要排除的主机名。<br>**包含** - 主机名包含字符串。 <br>**不包含** - 主机名不包含字符串。<br>**匹配** - 主机名匹配正则表达式。<br>**不匹配** - 主机名与正则表达式不匹配。| |*Proxy*|等于<br>不等于|指定代理或要排除的代理。<br>**等于** - 使用此代理。<br>**不等于** - 使用除此之外的任何其他代理。|

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

en-us	#### - Autoregistration  In this section, you can configure the encryption level for active agent autoregistration.  ![adm\_autoreg2.png](../../../../../assets/en/manual/web_interface/frontend_sections/administration/adm_autoreg2.png)  Parameters marked with an asterisk are mandatory.  Configuration parameters:  |Parameter|Description| |---------|-----------| |*Encryption level*|Select one or both options for encryption level:<br>**No encryption** - unencrypted connections are allowed<br>**PSK** - TLS encrypted connections with a pre-shared key are allowed| |*PSK identity*|Enter the pre-shared key identity string.<br>This field is only available if 'PSK' is selected as *Encryption level*.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |*PSK*|Enter the pre-shared key (an even number of hexadecimal characters).<br>Maximum length: 512 hex-digits (256-byte PSK) if Zabbix uses GnuTLS or OpenSSL library, 64 hex-digits (32-byte PSK) if Zabbix uses mbed TLS (PolarSSL) library.<br>Example: 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952<br>This field is only available if 'PSK' is selected as *Encryption level*.|  See also: [Secure autoregistration](/manual/discovery/auto_registration#secure_autoregistration)
zh-cn	#### - 自动注册  在本节中，您可以配置活动代理自动注册的加密级别。  ![adm\_autoreg2.png](../../../../../assets/en/manual/web_interface/frontend_sections/administration/adm_autoreg2.png)  标有星号的参数是强制性的。  配置参数：  |参数|说明| |---------|------------| |*加密级别*|为加密级别选择一个或两个选项：<br>**不加密** - 允许未加密的连接<br>**PSK** - 允许使用预共享密钥的 TLS 加密连接| |*PSK 身份*|输入预共享密钥身份字符串。<br>此字段仅在选择“PSK”作为*加密级别*时可用。<br>不要将敏感信息放入 PSK 身份中，它是通过网络以未加密方式传输以通知接收器使用哪个 PSK。 |*PSK*|输入预共享密钥（偶数个十六进制字符）。<br>最大长度：如果 Zabbix 使用 GnuTLS 或 OpenSSL 库，则为 512 个十六进制数字（256 字节 PSK），64 个十六进制数字（32 -byte PSK) 如果 Zabbix 使用 mbed TLS (PolarSSL) 库。<br>示例：1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952<br>此字段仅在选择“PSK”作为*加密级别*时可用。|  参阅：[Secure autoregistration](/manual/discovery/auto_registration#secure_autoregistration)

en-us	# > Autoregistration object  The following objects are directly related to the `autoregistration` API.
zh-cn	# > 自动注册对象  以下对象与 `自动注册` API直接相关。

en-us	### Autoregistration  The autoregistration object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tls\_accept|integer|Type of allowed incoming connections for autoregistration.<br><br>Possible values:<br>1 - allow insecure connections;<br>2 - allow TLS with PSK.<br>3 - allow both insecure and TLS with PSK connections.| |tls\_psk\_identity|string|*(write-only)* PSK identity string.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |tls\_psk|string|*(write-only)* PSK value string (an even number of hexadecimal characters).|
zh-cn	### 自动注册  自动注册对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tls\_accept|integer|自动注册允许的传入连接的类型。<br><br>可用值：<br>1 - 允许不安全的连接；<br>2 - 允许用PSK连接TLS；<br>3 - 允许不安全的连接以及通过PSK连接TLS两种方式.| |tls\_psk\_identity|string|*(只写)* PSK认证字符串。<br>不要将敏感信息放在PSK认证中，它会通过网络以未加密的方式传输，以通知接收者要使用哪个PSK。| |tls\_psk|string|*(只写)* PSK值字符串（偶数个十六进制字符）|

en-us	### Autoregistration  The autoregistration object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |tls\_accept|integer|Type of allowed incoming connections for autoregistration.<br><br>Possible values:<br>1 - allow unsecure connections;<br>2 - allow TLS with PSK.<br>3 - allow both unsecure and TLS with PSK connections.| |tls\_psk\_identity|string|*(write-only)* PSK identity string.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |tls\_psk|string|*(write-only)* PSK value string (an even number of hexadecimal characters).|
zh-cn	### 自动注册  自动注册对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tls\_accept|integer|自动注册允许的传入连接的类型。<br><br>可用值：<br>1 - 允许不安全的连接；<br>2 - 允许用PSK连接TLS；<br>3 - 允许不安全的连接以及通过PSK连接TLS两种方式.| |tls\_psk\_identity|string|*(只写)* PSK认证字符串。<br>不要将敏感信息放在PSK认证中，它会通过网络以未加密的方式传输，以通知接收者要使用哪个PSK。| |tls\_psk|string|*(只写)* PSK值字符串（偶数个十六进制字符）|

en-us	# Autoregistration  This class is designed to work with autoregistration.  Object references:\  -   [Autoregistration](/manual/api/reference/autoregistration/object#autoregistration)  Available methods:\  -   [autoregistration.get](/manual/api/reference/autoregistration/get) -     retrieve autoregistration -   [autoregistration.update](/manual/api/reference/autoregistration/update) -     update autoregistration
zh-cn	# 自动注册  该方法用于自动注册  对象引用:\  -   [自动注册](/manual/api/reference/autoregistration/object#autoregistration)  可用方法:\  -   [autoregistration.get](/manual/api/reference/autoregistration/get) -     检索自动注册 -   [autoregistration.update](/manual/api/reference/autoregistration/update) -     更新自动注册

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

en-us	##### Average request count to Nginx server  View the average request count per second per day to the Nginx server:  -   add the request count per second item to the data set -   select the aggregate function `avg` and specify interval `1d` -   a bar graph is displayed, where each bar represents the average     number of requests per second per day
zh-cn	##### Nginx 服务器的平均请求数  查看每天每秒对 Nginx 服务器的平均请求数：  - 将每秒项的请求计数添加到数据集中 - 选择聚合函数“avg”并指定区间“1d” - 显示一个条形图，其中每个条形图代表平均值每天每秒的请求数

en-us	### Backward incompatible changes
zh-cn	 ### 向下不兼容的变更

en-us	##### Baseline monitoring Set of available baseline monitoring options has been extended with the two new functions **baselinedev** and **baselinewma**.   -   **baselinedev** - compares the last data period with the same data periods in preceding seasons and returns the number of deviations; -   **baselinewma** - calculates the baseline by averaging data from the same timeframe in multiple equal time periods ('seasons') using the weighted moving average algorithm.  In context of these functions, the term 'season' refers to a configurable timeframe, which could be hours, days, weeks, months or years. The length of a season and the number of seasons to analyse is set in function parameters.   See [history functions](/manual/appendix/functions/history) for more info.
zh-cn	##### 基线监测  可用的基线监控选项集已通过两个新功能 **baselinedev** 和 **baselinewma** 进行了扩展。  -   **baselinedev** - 将上一个数据周期与前一season的相同数据周期进行比较，返回偏差数； -   **baselinewma** - 通过使用加权移动平均算法对多个相等时间段 ('seasons') 中同一时间范围内的数据进行平均来计算基线。  在这些函数的上下文中，术语 'season' 指的是可配置的时间范围，可以是几小时、几天、几周、几个月或几年。 'season' 长度和要分析的季节数量在函数参数中设置。  有关更多信息，请参阅 [历史函数](/manual/appendix/functions/history) 。