en-us	#### Overview  The table contains a complete list of macros supported by Zabbix out-of-the-box.  ::: notetip To see all macros supported in a location (for example, in "map URL"), you may paste the location name into the search box at the bottom of your browser window (accessible by pressing CTRL+F) and do a search for *next*. :::  |Macro|Supported in|Description| |--|--------------|-------------| |{ACTION.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications|*Numeric ID of the triggered action.*| |{ACTION.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications|*Name of the triggered action.*| |{ALERT.MESSAGE}|→ Alert script parameters|*'Default message' value from action configuration.*<br>Supported since 3.0.0.| |{ALERT.SENDTO}|→ Alert script parameters|*'Send to' value from user media configuration.*<br>Supported since 3.0.0.| |{ALERT.SUBJECT}|→ Alert script parameters|*'Default subject' value from action configuration.*<br>Supported since 3.0.0.| |{DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current date in yyyy.mm.dd. format.*| |{DISCOVERY.DEVICE.IPADDRESS}|→ Discovery notifications and commands|*IP address of the discovered device.*<br>Available always, does not depend on host being added.| |{DISCOVERY.DEVICE.DNS}|→ Discovery notifications and commands|*DNS name of the discovered device.*<br>Available always, does not depend on host being added.| |{DISCOVERY.DEVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered device*: can be either UP or DOWN.| |{DISCOVERY.DEVICE.UPTIME}|→ Discovery notifications and commands|*Time since the last change of discovery status for a particular device*, with precision down to a second.<br>For example: 1h 29m 01s.<br>For devices with status DOWN, this is the period of their downtime.| |{DISCOVERY.RULE.NAME}|→ Discovery notifications and commands|*Name of the discovery rule that discovered the presence or absence of the device or service.*| |{DISCOVERY.SERVICE.NAME}|→ Discovery notifications and commands|*Name of the service that was discovered.*<br>For example: HTTP.| |{DISCOVERY.SERVICE.PORT}|→ Discovery notifications and commands|*Port of the service that was discovered.*<br>For example: 80.| |{DISCOVERY.SERVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered <service://> can be either UP or DOWN. \| \|{DISCOVERY.SERVICE.UPTIME} \|→ Discovery notifications and commands \|*Time since the last change of discovery status for a particular service*, with precision down to a second.<br>For example: 1h 29m 01s.<br>For services with status DOWN, this is the period of their downtime. \| \|{ESC.HISTORY} \|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Internal notifications \|*Escalation history. Log of previously sent messages.*<br>Shows previously sent notifications, on which escalation step they were sent and their status (*sent*, *in progress* or *failed*).| |{EVENT.ACK.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Acknowledgment status of the event (Yes/No)*.| |{EVENT.AGE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Age of the event that triggered an action*, with precision down to a second.<br>Useful in escalated messages.| |{EVENT.DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Date of the event that triggered an action.*| |{EVENT.DURATION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Duration of the event (time difference between problem and recovery events)*, with precision down to a second.<br>Useful in problem recovery messages.<br><br>Supported since 5.0.0.| |{EVENT.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric ID of the event that triggered an action.*| |{EVENT.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the problem event that triggered an action.*<br>Supported since 4.0.0.| |{EVENT.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event severity.* Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.<br>Supported since 4.0.0.| |{EVENT.OBJECT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event object.* Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.<br>Supported since 4.4.0.| |{EVENT.OPDATA}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Operational data of the underlying trigger of a problem.*<br>Supported since 4.4.0.| |{EVENT.RECOVERY.DATE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Date of the recovery event.*| |{EVENT.RECOVERY.ID}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Numeric ID of the recovery event.*| |{EVENT.RECOVERY.NAME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Name of the recovery event.*<br>Supported since 4.4.1.| |{EVENT.RECOVERY.STATUS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Verbal value of the recovery event.*| |{EVENT.RECOVERY.TAGS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*A comma separated list of recovery event tags.* Expanded to an empty string if no tags exist.<br>Supported since 3.2.0.| |{EVENT.RECOVERY.TAGSJSON}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*A JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag).* Expanded to an empty array if no tags exist.<br>Supported since 5.0.0.| |{EVENT.RECOVERY.TIME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Time of the recovery event.*| |{EVENT.RECOVERY.VALUE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands (if recovery took place)<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Numeric value of the recovery event.*| |{EVENT.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the event severity.*<br>Supported since 4.0.0.| |{EVENT.SOURCE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event source.* Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal.<br>Supported since 4.4.0.| |{EVENT.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Verbal value of the event that triggered an action.*| |{EVENT.TAGS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A comma separated list of event tags.* Expanded to an empty string if no tags exist.<br>Supported since 3.2.0.| |{EVENT.TAGSJSON}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag).* Expanded to an empty array if no tags exist.<br>Supported since 5.0.0.| |{EVENT.TAGS.<tag name>}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Webhook media type URL names and URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Event tag value referenced by the tag name.*<br>A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) should be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.<br>Supported since 4.4.2.| |{EVENT.TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Time of the event that triggered an action.*| |{EVENT.UPDATE.ACTION}|→ Problem update notifications and commands|*Human-readable name of the action(s)* performed during [problem update](/manual/acknowledges#updating_problems).<br>Resolves to the following values: *acknowledged*, *commented*, *changed severity from (original severity) to (updated severity)* and *closed* (depending on how many actions are performed in one update).<br>Supported since 4.0.0.| |{EVENT.UPDATE.DATE}|→ Problem update notifications and commands<br>→ Service update notifications and commands|*Date of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*<br>Deprecated name: {ACK.DATE}| |{EVENT.UPDATE.HISTORY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Log of problem updates (acknowledgments, etc).*<br>Deprecated name: {EVENT.ACK.HISTORY}| |{EVENT.UPDATE.MESSAGE}|→ Problem update notifications and commands|*Problem update message.*<br>Deprecated name: {ACK.MESSAGE}| |{EVENT.UPDATE.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the problem update status.* Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.<br>Supported since 4.4.0.| |{EVENT.UPDATE.TIME}|→ Problem update notifications and commands<br>→ Service update notifications and commands|*Time of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*<br>Deprecated name: {ACK.TIME}| |{EVENT.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Service recovery notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of the event that triggered an action (1 for problem, 0 for recovering).*| |{FUNCTION.VALUE<1-9>}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Event names|*Results of the Nth item-based function in the trigger expression at the time of the event.*<br>Only functions with */host/key* as the first parameter are counted. See [indexed macros](supported_by_location#indexed_macros).| |{FUNCTION.RECOVERY.VALUE<1-9>}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Results of the Nth item-based function in the recovery expression at the time of the event.*<br>Only functions with */host/key* as the first parameter are counted. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.CONN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host IP address or DNS name, depending on host settings*^[2](supported_by_location#footnotes)^.<br><br>May be used with a numeric index as {HOST.CONN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host description.*<br><br>This macro may be used with a numeric index e.g. {HOST.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.DNS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host DNS name*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.DNS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.HOST}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Item key parameters<br>→ Map element labels, map URL names and values<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host name.*<br><br>This macro may be used with a numeric index e.g. {HOST.HOST[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{HOSTNAME<1-9>}` is deprecated.| |{HOST.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host ID.*<br><br>May be used with a numeric index as {HOST.ID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.IP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters^[1](supported_by_location#footnotes)^<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ JMX item endpoint field<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Host IP address*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.IP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{IPADDRESS<1-9>}` is deprecated.| |{HOST.METADATA}|→ Autoregistration notifications and commands|*Host metadata.*<br>Used only for active agent autoregistration.| |{HOST.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Map element labels, map URL names and values<br>→ Item key parameters<br>→ Host interface IP/DNS<br>→ Trapper item "Allowed hosts" field<br>→ Database monitoring additional parameters<br>→ SSH and Telnet scripts<br>→ Web monitoring^[4](supported_by_location#footnotes)^<br>→ Low-level discovery rule filter regular expressions<br>→ URL field of dynamic URL dashboard widget<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Script type item, item prototype and discovery rule parameter names and values<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Description of item value widget|*Visible host name.*<br><br>This macro may be used with a numeric index e.g. {HOST.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.PORT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger names, event names, operational data and descriptions<br>→ Trigger URLs<br>→ JMX item endpoint field<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host (agent) port*^[2](supported_by_location#footnotes)^.<br><br>This macro may be used with a numeric index e.g. {HOST.PORT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{HOST.TARGET.CONN}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|IP address or DNS name of the target host, depending on host settings.<br>Supported since 5.4.0.| |{HOST.TARGET.DNS}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|DNS name of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.HOST}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|Technical name of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.IP}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|IP address of the target host.<br>Supported since 5.4.0.| |{HOST.TARGET.NAME}|→ Trigger-based commands<br>→ Problem update commands<br>→ Discovery commands<br>→ Autoregistration commands|Visible name of the target host.<br>Supported since 5.4.0.| |{HOSTGROUP.ID}|→ Map element labels, map URL names and values|*Host group ID.*| |{INVENTORY.ALIAS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Alias field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.ALIAS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.ASSET.TAG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Asset tag field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.ASSET.TAG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CHASSIS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Chassis field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CHASSIS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CONTACT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Contact field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CONTACT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.CONTACT<1-9>}` is deprecated.| |{INVENTORY.CONTRACT.NUMBER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Contract number field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.CONTRACT.NUMBER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.DEPLOYMENT.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Deployment status field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.DEPLOYMENT.STATUS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HARDWARE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.HARDWARE<1-9>}` is deprecated.| |{INVENTORY.HARDWARE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETMASK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host subnet mask field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETMASK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETWORKS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host networks field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETWORKS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.ROUTER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Host router field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HOST.ROUTER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.ARCH}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Hardware architecture field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.ARCH[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.DECOMM}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware decommissioned field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.DECOMM[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.EXPIRY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware maintenance expires field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.EXPIRY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.INSTALL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware installed field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.INSTALL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.PURCHASE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date hardware purchased field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.PURCHASE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.INSTALLER.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Installer name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.INSTALLER.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.LOCATION<1-9>}` is deprecated.| |{INVENTORY.LOCATION.LAT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location latitude field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LAT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION.LON}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Location longitude field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LON[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MACADDRESS.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*MAC address A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.MACADDRESS<1-9>}` is deprecated.| |{INVENTORY.MACADDRESS.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*MAC address B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MODEL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Model field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.MODEL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NAME<1-9>}` is deprecated.| |{INVENTORY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NOTES<1-9>}` is deprecated.| |{INVENTORY.OOB.IP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB IP address field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.IP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.NETMASK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB subnet mask field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.NETMASK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.ROUTER}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OOB router field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OOB.ROUTER[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.OS<1-9>}` is deprecated.| |{INVENTORY.OS.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS.SHORT}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*OS (Short) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.OS.SHORT[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.CELL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC cell field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.CELL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.EMAIL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC email field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC phone A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC phone B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.SCREEN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Primary POC screen name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.CELL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC cell field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.CELL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.EMAIL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC email field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC phone A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC phone B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.SCREEN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Secondary POC screen name field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SERIALNO.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Serial number A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.SERIALNO<1-9>}` is deprecated.| |{INVENTORY.SERIALNO.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Serial number B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site address C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.CITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site city field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.CITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.COUNTRY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site country field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.COUNTRY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.NOTES}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site notes field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.NOTES[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.RACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site rack location field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.RACK[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.STATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site state/province field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.STATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ZIP}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Site ZIP/postal field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SITE.ZIP[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.SOFTWARE<1-9>}` is deprecated.| |{INVENTORY.SOFTWARE.APP.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.D}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application D field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.D[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.APP.E}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software application E field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.E[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SOFTWARE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Software (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.TAG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Tag field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TAG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.TAG<1-9>}` is deprecated.| |{INVENTORY.TYPE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Type field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TYPE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.DEVICETYPE<1-9>}` is deprecated.| |{INVENTORY.TYPE.FULL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Type (Full details) field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.TYPE.FULL[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.A}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL A field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.A[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.B}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL B field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.B[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.URL.C}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*URL C field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.URL.C[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.VENDOR}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Map element labels, map URL names and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Vendor field in host inventory.*<br><br>This macro may be used with a numeric index e.g. {INVENTORY.VENDOR[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Description of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.DESCRIPTION.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Description (with macros unresolved) of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.DESCRIPTION.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>Supported since 5.2.0.| |{ITEM.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Numeric ID of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.ID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.KEY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Key of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.KEY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>`{TRIGGER.KEY}` is deprecated.| |{ITEM.KEY.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^<br>→ HTTP agent type item, item prototype and discovery rule fields:<br>URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.^[6](supported_by_location#footnotes)^<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Original key (with macros not expanded) of the Nth item in the trigger expression that caused a notification ^[4](supported_by_location#footnotes)^.*<br><br>This macro may be used with a numeric index e.g. {ITEM.KEY.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LASTVALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, event names, operational data and descriptions<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*The latest value of the Nth item in the trigger expression that caused a notification.*<br>It will resolve to \*UNKNOWN\* in the frontend if the latest history value has been collected more than the *Max history display period* time ago (set in the [Administration→General](/manual/web_interface/frontend_sections/administration/general#gui) menu section).<br>Note that since 4.0, when used in the problem name, it will not resolve to the latest item value when viewing problem events, instead it will keep the item value from the time of problem happening.<br>It is alias to `last(/{HOST.HOST}/{ITEM.KEY})`.<br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro; starting with Zabbix 3.2.0.<br><br>This macro may be used with a numeric index e.g. {ITEM.LASTVALUE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. item in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.AGE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Age of the log item event*, with precision down to a second.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.AGE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.DATE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Date of the log item event.*<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.DATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.EVENTID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*ID of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.EVENTID[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Numeric severity of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.NSEVERITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Verbal severity of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.SEVERITY[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.SOURCE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Source of the event in the event log.*<br>For Windows event log monitoring only.<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.SOURCE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.LOG.TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, operational data and descriptions<br>→ Trigger URLs<br>→ Event tags and values<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Time of the log item event.*<br><br>This macro may be used with a numeric index e.g. {ITEM.LOG.TIME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Name of the Nth item in the trigger expression that caused a notification.*<br><br>This macro may be used with a numeric index e.g. {ITEM.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.NAME.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|This macros is deprecated since Zabbix 6.0. It used to resolve to the *original name (i.e. without macros resolved) of the item* in pre-6.0 Zabbix versions when user macros and positional macros were supported in the item name.<br><br>This macro may be used with a numeric index e.g. {ITEM.NAME.ORIG[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.STATE}|→ Item-based internal notifications<br>→ Description of item value widget|*The latest state of the Nth item in the trigger expression that caused a notification.* Possible values: **Not supported** and **Normal**.<br><br>This macro may be used with a numeric index e.g. {ITEM.STATE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.STATE.ERROR}|→ Item-based internal notifications|*Error message with details why an item became unsupported.* <br> <br> If an item goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{ITEM.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger names, event names, operational data and descriptions<br>→ [Tag names and values](/manual/config/tagging#macro_support)<br>→ Trigger URLs<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|Resolved to either:<br>1) the historical (at-the-time-of-event) value of the Nth item in the trigger expression, if used in the context of trigger status change, for example, when displaying events or sending notifications.<br>2) the latest value of the Nth item in the trigger expression, if used without the context of trigger status change, for example, when displaying a list of triggers in a pop-up selection window. In this case works the same as {ITEM.LASTVALUE}<br>In the first case it will resolve to \*UNKNOWN\* if the history value has already been deleted or has never been stored.<br>In the second case, and in the frontend only, it will resolve to \*UNKNOWN\* if the latest history value has been collected more than the *Max history display period* time ago (set in the [Administration→General](/manual/web_interface/frontend_sections/administration/general#gui) menu section).<br><br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 3.2.0.<br><br>This macro may be used with a numeric index e.g. {ITEM.VALUE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. item in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{ITEM.VALUETYPE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Description of item value widget|*Value type of the Nth item in the trigger expression that caused a notification.* Possible values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text.<br><br>This macro may be used with a numeric index e.g. {ITEM.VALUETYPE[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).<br><br>Supported since 5.4.0.| |{LLDRULE.DESCRIPTION}|→ LLD-rule based internal notifications|*Description of the low-level discovery rule which caused a notification.*| |{LLDRULE.DESCRIPTION.ORIG}|→ LLD-rule based internal notifications|*Description (with macros unresolved) of the low-level discovery rule which caused a notification.*<br>Supported since 5.2.0.| |{LLDRULE.ID}|→ LLD-rule based internal notifications|*Numeric ID of the low-level discovery rule which caused a notification.*| |{LLDRULE.KEY}|→ LLD-rule based internal notifications|*Key of the low-level discovery rule which caused a notification.*| |{LLDRULE.KEY.ORIG}|→ LLD-rule based internal notifications|*Original key (with macros not expanded) of the low-level discovery rule which caused a notification.*| |{LLDRULE.NAME}|→ LLD-rule based internal notifications|*Name of the low-level discovery rule (with macros resolved) that caused a notification.*| |{LLDRULE.NAME.ORIG}|→ LLD-rule based internal notifications|*Original name (i.e. without macros resolved) of the low-level discovery rule that caused a notification.*| |{LLDRULE.STATE}|→ LLD-rule based internal notifications|*The latest state of the low-level discovery rule.* Possible values: **Not supported** and **Normal**.| |{LLDRULE.STATE.ERROR}|→ LLD-rule based internal notifications|*Error message with details why an LLD rule became unsupported.* <br> <br> If an LLD rule goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{MAP.ID}|→ Map element labels, map URL names and values|*Network map ID.*| |{MAP.NAME}|→ Map element labels, map URL names and values<br>→ Text field in map shapes|*Network map name.*<br>Supported since 3.4.0.| |{PROXY.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Description of the proxy*. Resolves to either:<br>1) proxy of the Nth item in the trigger expression (in trigger-based notifications). You may use [indexed](/manual/appendix/macros/supported_by_location#indexed_macros) macros here.<br>2) proxy, which executed discovery (in discovery notifications). Use {PROXY.DESCRIPTION} here, without indexing.<br>3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.DESCRIPTION} here, without indexing.<br><br>This macro may be used with a numeric index e.g. {PROXY.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{PROXY.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the proxy*. Resolves to either:<br>1) proxy of the Nth item in the trigger expression (in trigger-based notifications). You may use [indexed](/manual/appendix/macros/supported_by_location#indexed_macros) macros here.<br>2) proxy, which executed discovery (in discovery notifications). Use {PROXY.NAME} here, without indexing.<br>3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.NAME} here, without indexing.<br><br>This macro may be used with a numeric index e.g. {PROXY.NAME[<1-9>](supported_by_location#indexed_macros)} to point to the first, second, third, etc. host in a trigger expression. See [indexed macros](supported_by_location#indexed_macros).| |{SERVICE.DESCRIPTION}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Description of the service* (with macros resolved).| |{SERVICE.NAME}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Name of the service* (with macros resolved).| |{SERVICE.ROOTCAUSE}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*List of trigger problem events that caused a service to fail*, sorted by severity and host name. Includes the following details: host name, event name, severity, age, service tags and values.| |{SERVICE.TAGS}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*A comma separated list of service event tags.* Service event tags can be defined in the service configuration section Tags. Expanded to an empty string if no tags exist.| |{SERVICE.TAGSJSON}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*A JSON array containing service event tag objects.* Service event tags can be defined in the service configuration section Tags. Expanded to an empty array if no tags exist.| |{SERVICE.TAGS.<tag name>}|→ Service-based notifications and commands<br>→ Service update notifications and commands|*Service event tag value referenced by the tag name.* Service event tags can be defined in the service configuration section Tags.<br>A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) should be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.| |{TIME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Service-based notifications and commands<br>→ Service update notifications and commands<br>→ Discovery notifications and commands<br>→ Autoregistration notifications and commands<br>→ Internal notifications<br>→ Trigger event names<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current time in hh:mm:ss.*| |{TRIGGER.DESCRIPTION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger description.*<br>All macros supported in a trigger description will be expanded if `{TRIGGER.DESCRIPTION}` is used in notification text.<br>`{TRIGGER.COMMENT}` is deprecated.| |{TRIGGER.EXPRESSION.EXPLAIN}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)<br>→ Event names|*Partially evaluated trigger expression.*<br>Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger expressions.| |{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Partially evaluated trigger recovery expression.*<br>Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger recovery expressions.| |{TRIGGER.EVENTS.ACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of acknowledged events for a map element in maps, or for the trigger which generated current event in notifications.*| |{TRIGGER.EVENTS.PROBLEM.ACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of acknowledged PROBLEM events for all triggers disregarding their state.*| |{TRIGGER.EVENTS.PROBLEM.UNACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of unacknowledged PROBLEM events for all triggers disregarding their state.*| |{TRIGGER.EVENTS.UNACK}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Number of unacknowledged events for a map element in maps, or for the trigger which generated current event in notifications.*| |{TRIGGER.HOSTGROUP.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A sorted (by SQL query), comma-space separated list of host groups in which the trigger is defined.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}|→ Map element labels|*Number of acknowledged PROBLEM events for triggers in PROBLEM state.*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}|→ Map element labels|*Number of unacknowledged PROBLEM events for triggers in PROBLEM state.*| |{TRIGGER.EXPRESSION}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger expression.*| |{TRIGGER.EXPRESSION.RECOVERY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger recovery expression* if *OK event generation* in [trigger configuration](/manual/config/triggers/trigger) is set to 'Recovery expression'; otherwise an empty string is returned.<br>Supported since 3.2.0.| |{TRIGGER.ID}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Map element labels, map URL names and values<br>→ Trigger URLs<br>→ Trigger tag value<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric trigger ID which triggered this action.*<br>Supported in trigger tag values since 4.4.1.| |{TRIGGER.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the trigger* (with macros resolved).<br>Note that since 4.0.0 {EVENT.NAME} can be used in actions to display the triggered event/problem name with macros resolved.| |{TRIGGER.NAME.ORIG}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Original name of the trigger* (i.e. without macros resolved).| |{TRIGGER.NSEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numerical trigger severity.* Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.| |{TRIGGER.SEVERITY}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger severity name.* Can be defined in *Administration → General → Trigger displaying options*.| |{TRIGGER.STATE}|→ Trigger-based internal notifications|*The latest state of the trigger.* Possible values: **Unknown** and **Normal**.| |{TRIGGER.STATE.ERROR}|→ Trigger-based internal notifications|*Error message with details why a trigger became unsupported.* <br> <br> If a trigger goes into the unsupported state and then immediately gets supported again the error field can be empty.| |{TRIGGER.STATUS}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger value at the time of operation step execution.* Can be either PROBLEM or OK.<br>`{STATUS}` is deprecated.| |{TRIGGER.TEMPLATE.NAME}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*A sorted (by SQL query), comma-space separated list of templates in which the trigger is defined, or \*UNKNOWN\* if the trigger is defined in a host.*| |{TRIGGER.URL}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger-based internal notifications<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger URL.*| |{TRIGGER.VALUE}|→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Trigger expressions<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current trigger numeric value*: 0 - trigger is in OK state, 1 - trigger is in PROBLEM state.| |{TRIGGERS.UNACK}|→ Map element labels|*Number of unacknowledged triggers for a map element, disregarding trigger state.*<br>A trigger is considered to be unacknowledged if at least one of its PROBLEM events is unacknowledged.| |{TRIGGERS.PROBLEM.UNACK}|→ Map element labels|*Number of unacknowledged PROBLEM triggers for a map element.*<br>A trigger is considered to be unacknowledged if at least one of its PROBLEM events is unacknowledged.| |{TRIGGERS.ACK}|→ Map element labels|*Number of acknowledged triggers for a map element, disregarding trigger state.*<br>A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.| |{TRIGGERS.PROBLEM.ACK}|→ Map element labels|*Number of acknowledged PROBLEM triggers for a map element.*<br>A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.| |{USER.FULLNAME}|→ Problem update notifications and commands<br>→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Name, surname and username of the user* who added event acknowledgment or started the script.<br>Supported for problem updates since 3.4.0, for global scripts since 5.0.2| |{USER.NAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Name of the user* who started the script.<br>Supported since 5.0.2.| |{USER.SURNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Surname of the user* who started the script.<br>Supported since 5.0.2.| |{USER.USERNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Username of the user* who started the script.<br>Supported since 5.0.2.<br>{USER.ALIAS}, supported before Zabbix 5.4.0, is now deprecated.| |{$MACRO}|→ See: [User macros supported by location](/manual/appendix/macros/supported_by_location_user)|*[User-definable](/manual/config/macros/user_macros) macros.*| |{\#MACRO}|→ See: [Low-level discovery macros](/manual/config/macros/lld_macros)|*Low-level discovery macros.*<br><br>[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 4.0.0.| |{?EXPRESSION}|→ Trigger event names<br>→ Trigger-based notifications and commands<br>→ Problem update notifications and commands<br>→ Map element labels^[3](supported_by_location#footnotes)^<br>→ Map shape labels^[3](supported_by_location#footnotes)^<br>→ Link labels in maps^[3](supported_by_location#footnotes)^<br>→ Graph names^[5](supported_by_location#footnotes)^|*Expression macro* for formula calculations. Calculated by expanding all macros inside and evaluating the resulting expression.<br>See [example](/manual/config/triggers/expression#example_17) of using an expression macro in the event name.<br>Supported since 5.2.0.|
zh-cn	#### 概述  下表包含Zabbix原生支持宏的完整列表。   ::: notetip 要查看某个功能所支持的所有宏(例如，想要知道"map URL"功能中支持的所有宏)，你可以在浏览器的搜索框中输入这个功能的名称（用快捷键CTRL+F调出搜索框），然后点击“下一个” :::  |宏名称|支持该宏的功能|具体描述| |-----|------------|-----------| |{ACTION.ID}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知|*触发动作的数字ID*| |{ACTION.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知|*触发动作的名字*| |{ALERT.MESSAGE}|→ 告警脚本参数|*配置“动作”时用到的“默认消息”*<br>从3.0.0版本开始支持| |{ALERT.SENDTO}|→ 告警脚本参数|*'配置“媒体”时用到的“发送至”*<br>从3.0.0版本开始支持| |{ALERT.SUBJECT}|→ 告警脚本参数|*配置“动作”时用到的“默认主题”*<br>从3.0.0版本开始支持| |{DATE}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*日期格式为yyyy.mm.dd*| |{DISCOVERY.DEVICE.IPADDRESS}|→ 自动发现的通知和命令|*被发现的设备的IP地址*<br>永久有效，不依赖于是否添加了设备| |{DISCOVERY.DEVICE.DNS}|→ 自动发现的通知和命令|*被发现的设备的DNS名称*<br>永久有效，不依赖于是否添加了设备| |{DISCOVERY.DEVICE.STATUS}|→ 自动发现的通知和命令|*被发现设备的状态*: 可能是 UP 或者 DOWN.| |{DISCOVERY.DEVICE.UPTIME}|→ 自动发现的通知和命令|*某设备最近一次被监控到状态改变的时间。*, 精确到秒<br>例如： 1h 29m 01s.<br>对于状态是DOWN的设备来说，这就是他们变成关机状态的时间长度| |{DISCOVERY.RULE.NAME}|→ 自动发现的通知和命令|*用于发现设备或服务是否在线的自动发现规则的名称*| |{DISCOVERY.SERVICE.NAME}|→ 自动发现的通知和命令|*自动发现的服务的名称*<br>例如： HTTP.| |{DISCOVERY.SERVICE.PORT}|→ 自动发现的通知和命令|*自动发现的服务的端口*<br>例如： 80.| |{DISCOVERY.SERVICE.STATUS}|→ 自动发现的通知和命令|*自动发现的 <服务://> 状态，可能是UP 或者 DOWN \| \|{DISCOVERY.SERVICE.UPTIME} \|→ 自动发现的通知和命令 \|*该服务自动发现状态最近改变的时间*, 精确到秒<br>例如： 1h 29m 01s.<br>对于状态是DOWN的服务，是该服务不可用的时间\| \|{ESC.HISTORY} \|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 内部通知 \|*升级history.Log 过去发送的消息。*<br>显示之前发送过的通知，通知是基于什么升级步骤发送的，以及他们的状态 (*已发送, *进行中* or *失败*).| |{EVENT.ACK.STATUS}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*事件确认发状态(是/否)*.| |{EVENT.AGE}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*触发动作的事件的时长*, 精确到秒<br>在升级消息时有用| |{EVENT.DATE}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*触发动作的事件的日期*| |{EVENT.DURATION}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*事件持续时间（发生问题和恢复事件之间的时差）*, 精确到秒<br>在问题恢复信息中有用<br><br>从 5.0.0版本开始支持| |{EVENT.ID}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 触发器 URLs<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*触发动作的事件的数字ID*| |{EVENT.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*触发动作的问题事件名称*<br>从4.0.0版本开始支持| |{EVENT.NSEVERITY}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*描述事件严重性的数值* 包括: 0 - 未分级, 1 - 信息, 2 - 警告, 3 - 普通, 4 - 高, 5 - 灾难.<br>从4.0.0版本开始支持| |{EVENT.OBJECT}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*描述事件对象的数值* 包括：0 - 触发器, 1 - 自动发现的主机, 2 - 自动发现的服务, 3 - 低级自动发现规则, 4 - Item, 5 - 低级自动发现规则.<br>从4.4.0版本开始支持| |{EVENT.OPDATA}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*问题对应触发器的当前值*<br>从4.4.0版本开始支持 | |{EVENT.RECOVERY.DATE}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*事件恢复日期*| |{EVENT.RECOVERY.ID}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*恢复事件的数字ID*| |{EVENT.RECOVERY.NAME}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*恢复时间名称*<br>从4.4.1版本开始支持| |{EVENT.RECOVERY.STATUS}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*恢复事件的文字描述*| |{EVENT.RECOVERY.TAGS}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*用逗号分隔的恢复事件标签* 如果没有标签的，就是一个空字符<br>从3.2.0版本开始支持| |{EVENT.RECOVERY.TAGSJSON}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*一个包括事件标签[对象](/manual/api/reference/event/object#event_tag)的JSON数组.* 如果没有标签的，就是一个空数组<br>从5.0.0版本开始支持| |{EVENT.RECOVERY.TIME}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*恢复时间的时间.*| |{EVENT.RECOVERY.VALUE}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令 (如果恢复了)<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (如果恢复了)|*恢复时间的数值*| |{EVENT.SEVERITY}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*时间严重性等级的名称*<br>从4.0.0版本开始支持| |{EVENT.SOURCE}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*事件来源的数字描述* 包括：0 - 触发器, 1 - 自动发现, 2 - 自动注册, 3 - 内部.<br>从4.0.0版本开始支持| |{EVENT.STATUS}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*出发动作的事件的文字描述*| |{EVENT.TAGS}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*一组逗号分割单时间标签.* 如果没有标签的，就是一个空字符<br>从3.2.0版本开始支持| |{EVENT.TAGSJSON}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*一个包括事件标签[对象](/manual/api/reference/event/object#event_tag)的JSON数组.* 如果没有标签的，就是一个空数组<br>从5.0.0版本开始支持| |{EVENT.TAGS.<标签名称>}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ Wehook媒介URL名称和URL<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*用标签名称来引用的事件标签值.*<br>如果标签名称包含非字母数字的字符（包括非英语多字节UTF字符）需用双引号括起来。标签名称中引号括起来的引号和反斜杠必须用反斜杠转义。<br>从4.4.2版本开始支持| |{EVENT.TIME}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 自动发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|* 触发动作的事件时间*| |{EVENT.UPDATE.ACTION}|→ 问题更新的通知和命令|[问题更新](/manual/acknowledges#updating_problems)期间执行的*可读的动作名称* .<br>包括这些值: *已确认*, *已注释*, *严重级别从 (原始严重级别) 变化为 (更新严重级别)* 和 *已关闭* (取决于一次更新了多少个动作).<br>从4.0.0版本开始支持| |{EVENT.UPDATE.DATE}|→ 问题更新的通知和命令<br>→ 服务更新的通知和命令|*事件[更新](/manual/config/notifications/action/update_operations) 的日期(例如：确认，等等).*<br>过去使用 {ACK.DATE}，当前版本已弃用| |{EVENT.UPDATE.HISTORY}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*问题更新(例如：确认，等等)的日志*<br>过去使用 {EVENT.ACK.HISTORY}，当前版本已弃用| |{EVENT.UPDATE.MESSAGE}|→ 问题更新的通知和命令|*问题更新的消息。*<br>过去使用 {ACK.MESSAGE}，当前版本已弃用| |{EVENT.UPDATE.STATUS}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*问题更新状态的数值。* 包括： 0 - 因为问题/恢复事件触发了Webhook, 1 - 更新操作<br>从4.4.0版本开始支持| |{EVENT.UPDATE.TIME}|→ 问题更新的通知和命令<br>→ 服务更新的通知和命令|*事件[更新](/manual/config/notifications/action/update_operations) (例如：确认，等等)的时间*<br>过去使用 {ACK.TIME}，当前版本已弃用| |{EVENT.VALUE}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 基于服务的通知和命令<br>→ 服务更新的通知和命令<br>→ 服务恢复通知和命令<br>→ 内部通知<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*触发动作的事件的数值 (1 表示问题, 0 表示恢复)。*| |{FUNCTION.VALUE<1-9>}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)<br>→ 时间名称|*在发生事件的时刻，触发器表达式中，基于监控项的第N个函数的值*<br>只包括以*/host/key* 开始的函数. 具体参见 [宏索引](supported_by_location#indexed_macros)| |{FUNCTION.RECOVERY.VALUE<1-9>}|→ 问题[恢复通知](/manual/config/notifications/action/recovery_operations) 和命令<br>→ 问题更新的通知和命令<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*在发生事件的时刻，恢复表达式中，基于监控项的第N个函数的值*<br>只包括以*/host/key* 开始的函数. 具体参见 [宏索引](supported_by_location#indexed_macros).| |{HOST.CONN}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 内部通知<br>→ 地图元素标签，地图URL名称和值<br>→ 监控项键值参数^[1](supported_by_location#footnotes)^<br>→ 主机界面IP/DNS<br>→ Trapper 监控项 "主机范围" 字段<br>→ 数据库监控附加参数<br>→ SSH和Telnet脚本<br>→ JMX监控项端点字段<br>→ Web监控^[4](supported_by_location#footnotes)^<br>→ 低级自动发现规则过滤正则表达式<br>→ 仪表盘小部件动态URL的URL字段<br>→ 触发器名称, 时间名称, 当前操作数据和描述<br>→ 触发器URL<br>→ [标签名称和赋值](/manual/config/tagging#macro_support)<br>→ 脚本类型监控项，监控项原型和自动发现规则参数名称和赋值<br>→ HTTP agent类型监控项，监控项原型和自动发现规则字段:<br>URL, 查询字段, 请求体, 请求头, 代理, SSL证书文件, SSL key文件, 主机白名单.<br>→ 手动主机动作 [脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）|*依赖于主机设置的主机IP地址或DNS名称*^[2](supported_by_location#footnotes)^.<br><br>在触发器表达式中，可以用数字索引，来指向第一个，第二个，第三个主机，等等。例如：{HOST.CONN[<1-9>](supported_by_location#indexed_macros)}  详见 [索引宏](supported_by_location#indexed_macros).| |{HOST.DESCRIPTION}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 内部通知<br>→ 地图元素标签<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*主机描述.*<br><br>在触发器表达式中，该宏可用配合数字索引使用，来指向第一个，第二个，第三个主机，等等。例如： {HOST.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} 详见[索引宏](supported_by_location#indexed_macros).| |{HOST.DNS}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 内部通知<br>→ 地图元素标签，地图URL名称和值<br>→ 监控项键值参数^[1](supported_by_location#footnotes)^<br>→ 主机界面IP/DNS<br>→ Trapper 监控项 "主机范围" 字段<br>→ 数据库监控附加参数<br>→ SSH和Telnet脚本<br>→ JMX监控项端点字段<br>→ Web监控^[4](supported_by_location#footnotes)^<br>→ 低级自动发现规则过滤正则表达式<br>→ 仪表盘小部件中，动态 URL的URL字段 <br>→ 触发器名称, 时间名称, 当前操作数据和描述<br>→ 触发器 URLs<br>→ [标签名称和赋值](/manual/config/tagging#macro_support)<br>→ 脚本类型监控项，监控项原型和自动发现规则参数名称和赋值<br>→ HTTP agent类型监控项，监控项原型和自动发现规则字段:<br>URL, 查询字段, 请求体, 请求头, 代理, SSL证书文件, SSL key文件, 主机白名单.<br>→ 手动主机动作 [脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）|*主机DNS名称*^[2](supported_by_location#footnotes)^.<br><br>T在触发器表达式中，该宏可用配合数字索引使用，来指向第一个，第二个，第三个主机，等等。例如：{HOST.DNS[<1-9>](supported_by_location#indexed_macros)} 详见 [索引宏](supported_by_location#indexed_macros).| |{HOST.HOST}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 监控项键值参数<br>→ 地图元素标签，地图URL名称和值<br>→ 主机界面IP/DNS<br>→ Trapper 监控项 "主机范围" 字段<br>→ 数据库监控附加参数<br>→ SSH和Telnet脚本<br>→ JMX监控项端点字段<br>→ Web监控^[4](supported_by_location#footnotes)^<br>→ 低级自动发现规则过滤正则表达式<br>→ 仪表盘小部件动态URL的URL字段<br>→ 触发器名称, 时间名称, 当前操作数据和描述<br>→ 触发器 URLs<br>→ [标签名称和赋值](/manual/config/tagging#macro_support)<br>→ 脚本类型监控项，监控项原型和自动发现规则参数名称和赋值<br>→ HTTP agent类型监控项，监控项原型和自动发现规则字段:<br>URL, 查询字段, 请求体, 请求头, 代理, SSL证书文件, SSL key文件, 主机白名单.<br>→ 手动主机动作 [脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts) （包括确认文本）|*主机名称*<br>在触发器表达式中，可以用数字索引，来指向第一个，第二个，第三个主机，等等。例如： {HOST.HOST[<1-9>](supported_by_location#indexed_macros)} 详见 [索引宏](supported_by_location#indexed_macros).<br><br> 过去使用 `{HOSTNAME<1-9>}`，当前版本已弃用| |{HOST.ID}|→ 基于触发器的通知和命令<br>→ 问题更新的通知和命令<br>→ 内部通知<br>→ 地图元素标签，地图URL名称和值<br>→ 仪表盘小部件动态URL的URL字段<br>→ 触发器URL<br>→ [标签名称和赋值](/manual/config/tagging#macro_support)<br>→ 手动动作[脚本](/manual/web_interface/frontend_sections/administration/scripts)|*主机 ID.*<br><br>在触发器表达式中，可以用数字索引，来指向第一个，第二个，第三个主机，等等。例如：{HOST.ID[<1-9>](supported_by_location#indexed_macros)} 详见[索引宏](supported_by_location#indexed_macros).| |{HOST.IP}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 自动注册通知和命令<br>→ 内部通知<br>→ 映射元素标签，映射URL名称和值<br>→ 监控项关键参数^[1](supported_by_location#脚注)^<br>→ 主机接口IP/DNS<br>→ 触发器监控项 "允许的主机" 字段<br>→ 数据库监控附加字段<br>→ SSH和Telnet脚本<br>→ JMX项目终结点字段<br>→ Web监控^[4](supported_by_location#脚注)^<br>→ 低级别自动发现过滤正则表达式<br>→ 动态URL仪表盘组件的URL字段<br>→ 触发器名称，事件名称，操作型数据和描述<br>→ 触发器URL<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 脚本类型监控项，监控项原型和发现规则参数名称和值<br>→ HTTP代理类型监控项，监控项原型和发现规则字段：<br>URL，查询字段，请求正文，报头，代理，SSL证书文件，SSL密钥文件，允许的主机。.<br>→ 自定义主机操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*主机IP地址*^[2](supported_by_location#脚注)^.<br><br>这个宏可以和一个数字索引一起使用，例如： {HOST.IP[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{IPADDRESS<1-9>}` 已弃用。| |{HOST.METADATA}|→ 自动注册通知和命令|*主机元数据。*<br>仅适用活动代理自动注册。| |{HOST.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ 映射元素标签，映射URL名称和值<br>→ 监控项关键参数<br>→ 主机接口IP/DNS<br>→ 触发器监控项 "允许的主机" 字段<br>→ 数据库监控附加字段<br>→ SSH和Telnet脚本<br>→ Web监控^[4](supported_by_location#脚注)^<br>→ 低级别自动发现过滤正则表达式<br>→ 动态URL仪表盘组件的URL字段<br>→ 触发器名称，事件名称，操作型数据和描述<br>→ 触发器URL<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 脚本类型监控项，监控项原型和发现规则参数名称和值<br>→ HTTP代理类型监控项，监控项原型和发现规则字段：<br>URL，查询字段，请求正文，报头，代理，SSL证书文件，SSL密钥文件，允许的主机。.<br>→ 自定义主机操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*可见的主机名。*<br><br>这个宏可以和一个数字索引一起使用，例如： {HOST.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{HOST.PORT}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 自动注册通知和命令<br>→ 内部通知<br>→ 触发器名称，事件名称，操作型数据和描述<br>→ 触发器URL<br>→ JMX项目终结点字段<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机（代理）端口 *^[2](supported_by_location#脚注)^.<br><br>这个宏可以和一个数字索引一起使用，例如： {HOST.PORT[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{HOST.TARGET.CONN}|→ 基于触发器的命令<br>→ 问题更新命令<br>→ 发现命令<br>→ 自动注册命令|目标主机IP地址或DNS名称，取决于主机设置。<br>从5.4.0开始支持。| |{HOST.TARGET.DNS}|→ 基于触发器的命令<br>→ 问题更新命令<br>→ 发现命令<br>→ 自动注册命令|目标主机的DNS名称。<br>从5.4.0开始支持。| |{HOST.TARGET.HOST}|→ 基于触发器的命令<br>→ 问题更新命令<br>→ 发现命令<br>→ 自动注册命令|目标主机的技术名称。<br>从5.4.0开始支持。| |{HOST.TARGET.IP}|→ 基于触发器的命令<br>→ 问题更新命令<br>→ 发现命令<br>→ 自动注册命令|目标主机的IP地址。<br>从5.4.0开始支持。| |{HOST.TARGET.NAME}|→ 基于触发器的命令<br>→ 问题更新命令<br>→ 发现命令<br>→ 自动注册命令|目标主机的技术名称。<br>从5.4.0开始支持。| |{HOSTGROUP.ID}|→ 映射元素标签，映射URL名称和值|*主机组ID。*| |{INVENTORY.ALIAS}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的别名字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.ALIAS[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.ASSET.TAG}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的资产标签字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.ASSET.TAG[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CHASSIS}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的机壳字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.CHASSIS[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.CONTACT}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的联系字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.CONTACT[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.CONTACT<1-9>}` 已弃用。| |{INVENTORY.CONTRACT.NUMBER}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的合同号码字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.CONTRACT.NUMBER[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.DEPLOYMENT.STATUS}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的部署状态字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.DEPLOYMENT.STATUS[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HARDWARE}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HARDWARE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.HARDWARE<1-9>}` 已弃用。| |{INVENTORY.HARDWARE.FULL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件(全细节)字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HARDWARE.FULL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETMASK}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主机子网掩码字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HOST.NETMASK[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.NETWORKS}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主机网络字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HOST.NETWORKS[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HOST.ROUTER}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主机路由字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HOST.ROUTER[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.ARCH}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件架构字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HW.ARCH[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.DECOMM}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件退役日期字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HW.DATE.DECOMM[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.EXPIRY}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件维修过期日期字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HW.DATE.EXPIRY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.INSTALL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件安装日期字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HW.DATE.INSTALL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.HW.DATE.PURCHASE}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的硬件购买日期字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.HW.DATE.PURCHASE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.INSTALLER.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的安装名称字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.INSTALLER.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的位置字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.LOCATION[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.LOCATION<1-9>}` 已弃用。| |{INVENTORY.LOCATION.LAT}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的位置纬度字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.LOCATION.LAT[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.LOCATION.LON}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的位置经度字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.LOCATION.LON[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MACADDRESS.A}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的Mac 地址 A字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.MACADDRESS.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.MACADDRESS<1-9>}` 已弃用。| |{INVENTORY.MACADDRESS.B}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的Mac 地址 B字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.MACADDRESS.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.MODEL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的模型字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.MODEL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的名称字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NAME<1-9>}` 已弃用。| |{INVENTORY.NOTES}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的备注字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.NOTES[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.NOTES<1-9>}` 已弃用。| |{INVENTORY.OOB.IP}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的带外 IP 地址字段。 field in host inventory.*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OOB.IP[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.NETMASK}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的带外子网掩码字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OOB.NETMASK[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OOB.ROUTER}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的带外路由器字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OOB.ROUTER[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的操作系统字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OS[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.OS<1-9>}` 已弃用。| |{INVENTORY.OS.FULL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的操作系统(所有细节)字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OS.FULL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.OS.SHORT}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的操作系统( 简短)字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.OS.SHORT[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.CELL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC手机字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.CELL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.EMAIL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC email字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC名称字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.NOTES}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC注记字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.NOTES[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.A}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC电话A字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.PHONE.B}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC电话B字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.PRIMARY.SCREEN}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的主要的POC屏幕名称字段。。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.PRIMARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.CELL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC手机号码字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.CELL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.EMAIL}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC email字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.EMAIL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NAME}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC名称字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.NOTES}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC注记字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.NOTES[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.A}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC电话A字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.PHONE.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.PHONE.B}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC电话B字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.PHONE.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.POC.SECONDARY.SCREEN}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的第二个POC聚合图形名称字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.POC.SECONDARY.SCREEN[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SERIALNO.A}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的序列号A字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SERIALNO.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).<br><br>`{PROFILE.SERIALNO<1-9>}` 已弃用。| |{INVENTORY.SERIALNO.B}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的序列号B字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SERIALNO.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.A}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所地址A字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.ADDRESS.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.B}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所地址B字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.ADDRESS.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.ADDRESS.C}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所地址C字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.ADDRESS.C[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.CITY}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所城市字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.CITY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.COUNTRY}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所国家字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.COUNTRY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.NOTES}|→ 基于触发器的通知和命令<br>→ 问题更新通知和命令<br>→ 内部通知<br>→ [标签名称和值](/manual/config/tagging#macro_support)<br>→ 映射元素标签，映射URL名称和值<br>→ 自定义事件操作 [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*主机资产记录中的场所备注字段。*<br><br>这个宏可以和一个数字索引一起使用，例如： {INVENTORY.SITE.NOTES[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第1个、第2个、第3个等主机。参阅 [indexed macros](supported_by_location#indexed_macros).| |{INVENTORY.SITE.RACK}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中站点的机架位置字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SITE.RACK[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SITE.STATE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中站点所属的省/市。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SITE.STATE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SITE.ZIP}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中站点的邮编字段*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SITE.ZIP[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>`{PROFILE.SOFTWARE<1-9>}` 已弃用。| |{INVENTORY.SOFTWARE.APP.A}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件应用程序A的字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.APP.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE.APP.B}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件应用程序B的字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.APP.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE.APP.C}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件应用程序C的字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.APP.C[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE.APP.D}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件应用程序D的字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.APP.D[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE.APP.E}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件应用程序E的字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.APP.E[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.SOFTWARE.FULL}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的软件（完整细节描述）字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.SOFTWARE.FULL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.TAG}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的标签字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.TAG[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>`{PROFILE.TAG<1-9>}` 已弃用。| |{INVENTORY.TYPE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的类型字段。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.TYPE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>`{PROFILE.DEVICETYPE<1-9>}` 已弃用。| |{INVENTORY.TYPE.FULL}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中类型（完整详细信息）字段的内容。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.TYPE.FULL[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.URL.A}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中URL A的字段内容。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.URL.A[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.URL.B}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中URL B的字段内容。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.URL.B[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.URL.C}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中URL C的字段内容。*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.URL.C[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{INVENTORY.VENDOR}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 地图元素标签,地图URL的名称和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*主机清单中的供应商字段的内容*<br><br>该宏可以与数字索引一起使用，例如 {INVENTORY.VENDOR[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.DESCRIPTION}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*引发通知的触发器表达式中的第N个监控项的描述。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.DESCRIPTION.ORIG}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*引发通知的触发器表达式中的第N个监控项的描述（带有未解析的宏）。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.DESCRIPTION.ORIG[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>支持的最低版本是 5.2.0.| |{ITEM.ID}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 脚本类型item、item原型和发现规则参数的名称和值^[6](supported_by_location#footnotes)^<br>→ HTTP agent 类型监控项、监控项原型和发现规则字段:<br>URL,查询字段，请求正文,headers,代理proxy,SSL 证书文件,SSL密钥文件<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*引发通知的触发器表达式中的第 N 个监控项的序列ID。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.ID[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.KEY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 脚本类型item、item原型和发现规则参数的名称和值^[6](supported_by_location#footnotes)^<br>→ HTTP agent 类型监控项、监控项原型和发现规则字段:<br>URL,查询字段，请求正文,headers,代理proxy,SSL 证书文件,SSL密钥文件<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式中导致通知的第 N 监控项的键。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.KEY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>`{TRIGGER.KEY}` 已弃用。| |{ITEM.KEY.ORIG}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 脚本类型item、item原型和发现规则参数的名称和值^[6](supported_by_location#footnotes)^<br>→ HTTP agent 类型监控项、监控项原型和发现规则字段:<br>URL,查询字段，请求正文,headers,代理proxy,SSL 证书文件,SSL密钥文件, 允许的主机。^[6](supported_by_location#footnotes)^<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式中导致通知的第N监控项的原始键（宏未展开）。^[4](supported_by_location#footnotes)^.*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.KEY.ORIG[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LASTVALUE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名字，事件名字，操作数据和描述。<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 触发器的URL地址<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式中导致通知的第N项的最新值。*<br>如果收集到的最新历史值超过了 *最大历史显示周期*，在前端就会解析为\*UNKNOWN\* 。 (请查看 [管理→通用](/manual/web_interface/frontend_sections/administration/general#gui) 菜单选项)。<br>请注意，从 4.0 开始，在问题名称中使用时，在查看问题事件时不会解析为最新的监控项值，而是保留问题发生时的监控项值。 <br>它是此 `last(/{HOST.HOST}/{ITEM.KEY})`的别名。<br>从Zabbix的版本3.2.0开始，该宏支持[自定义](/manual/config/macros/macro_functions) 宏的值； <br><br>该宏可以与数字索引一起使用，例如 {ITEM.LASTVALUE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第一个、第二个、第三个等监控项。  请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.AGE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*监控项事件日志的持续时间*，可以精确到秒。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.AGE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.DATE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*监控项事件日志的日期*。时间格式类似于 yyyy:mm:dd 。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.DATE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.EVENTID}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*事件日志中的事件ID。*<br>仅适用于windows事件日志监控。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.EVENTID[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.NSEVERITY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*事件日志中日志的严重级别，用数字级别描述（1--7）。*<br>仅适用于windows事件日志监控。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.NSEVERITY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.SEVERITY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*事件日志中日志的严重级别，使用文字描述。*<br>仅适用于windows事件日志监控。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.SEVERITY[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.SOURCE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*事件日志中事件的源*<br>仅适用于windows事件日志监控。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.SOURCE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.LOG.TIME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名称、操作数据和描述<br>→ 触发器的URL地址<br>→ 事件的tags和值<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*item事件日志的发生时间。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.LOG.TIME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.NAME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式中导致通知的第N个监控项的名称。*<br><br>该宏可以与数字索引一起使用，例如 {ITEM.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.NAME.ORIG}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|从Zabbix 6.0之后此宏已弃用。 当监控项名称中支持用户宏和位置宏时，它用于在 Zabbix 6.0 之前的版本中解析为*监控项的原始名称（即没有解析宏）*。 <br><br>该宏可以与数字索引一起使用，例如 {ITEM.NAME.ORIG[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.STATE}|→ 基于监控项的内部通知|*触发器表达式中导致通知的第 N 监控项的最新状态。* 可能的值: **不支持** 和 **正常**.<br><br>该宏可以与数字索引一起使用，例如 {ITEM.STATE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.VALUE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器名字，事件名字，操作数据和描述。<br>→ [标签的名称和值](/manual/config/tagging#macro_support)<br>→ 触发器的URL地址<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|可被解释为如下的任意一项:<br>1) 如果在触发器状态更改的上下文中使用，则解释为触发器表达式中第N个监控项的历史值（事件发生时），例如在展示事件或发送通知时。<br>2) 如果在没有触发器状态更改的上下文的情况下使用，触发器表达式中第N个监控项的最新值。例如，在弹出选择窗口中显示触发器列表时。在本例中工作方式与 {ITEM.LASTVALUE}相同。<br>在第一种情况下，如果历史记录值已被删除或从未存储过，它将解释为\*未知\*。<br>在第二种情况下并且仅在前端中，如果收集的最新历史值超过*最大历史显示周期*时间，它将解析为\*未知\*. (查看 [管理→通用](/manual/web_interface/frontend_sections/administration/general#gui) 菜单选项).<br><br>[自定义](/manual/config/macros/macro_functions) 此宏支持宏值，从 Zabbix 3.2.0 开始。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.VALUE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中的第一个、第二个、第三个等监控项。请参考[宏索引](supported_by_location#indexed_macros)。| |{ITEM.VALUETYPE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式中导致通知的第N个监控项的值类型。* 可能的值: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text。<br><br>该宏可以与数字索引一起使用，例如 {ITEM.VALUETYPE[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。<br><br>支持的最低版本是 5.4.0.| |{LLDRULE.DESCRIPTION}|→ 基于 LLD 规则的内部通知|*引发通知的低级别自动发现规则的描述。*| |{LLDRULE.DESCRIPTION.ORIG}|→ 基于 LLD 规则的内部通知|*引发通知的低级别自动发现规则的描述（描述中带有未解析的宏）*<br>支持的最低版本是 5.2.0.| |{LLDRULE.ID}|→ 基于 LLD 规则的内部通知|*引发通知的低级别自动发现规则的规则序列ID*| |{LLDRULE.KEY}|→ 基于 LLD 规则的内部通知|*引发通知的低级别自动发现规则的键值*| |{LLDRULE.KEY.ORIG}|→ 基于 LLD 规则的内部通知|*引发通知的低级别自动发现规则的原始密钥（未扩展的宏）。*| |{LLDRULE.NAME}|→ 基于 LLD 规则的内部通知|*导致通知的低级发现规则（已解析宏）的名称。*| |{LLDRULE.NAME.ORIG}|→ 基于 LLD 规则的内部通知|*导致通知的低级发现规则的原始名称（即未解析宏）。*| |{LLDRULE.STATE}|→ 基于 LLD 规则的内部通知|*低级发现规则的最新状态。* 可能的值: **不支持** 和 **正常**.| |{MAP.ID}|→ 地图元素标签,地图URL的名称和值|*网络拓扑图ID*| |{MAP.NAME}|→ 地图元素标签,地图URL的名称和值<br>→ Text field in map shapes|*网络拓扑图名称*<br>支持的最低版本是 3.4.0.| |{PROXY.DESCRIPTION}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 发现的通知和命令<br>→ 自动注册的通知和命令<br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*代理的描述*。 可以被解释为如下的可能:<br>1) 触发器表达式中第 N 个监控项的代理（在基于触发器的通知中）。 您可以在此处使用[索引](/manual/appendix/macros/supported_by_location#indexed_macros) 宏。<br>2) 代理，它执行发现(在发现通知中)，在此处使用{PROXY.DESCRIPTION} ，无需索引。<br>3) 代理指向一个已经注册的agent (在自动注册通知中)。在此处使用{PROXY.DESCRIPTION}，无需索引。<br><br>该宏可以与数字索引一起使用，例如 {PROXY.DESCRIPTION[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{PROXY.NAME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 发现的通知和命令<br>→ 自动注册通知和命令 <br>→ 内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*代理的名称*. 可以被解释为如下的可能::<br>1)触发器表达式中第 N 个监控项的代理名称（在基于触发器的通知中）。 您可以在此处使用[索引](/manual/appendix/macros/supported_by_location#indexed_macros) 宏。<br>2)代理，它执行发现（在发现通知中）。在此处使用 {PROXY.NAME}，无需索引。<br>3) 代理指向一个已经注册的agent (在自动注册通知中)。 在此处使用{PROXY.NAME} ，无需索引。<br><br>该宏可以与数字索引一起使用，例如 {PROXY.NAME[<1-9>](supported_by_location#indexed_macros)} 指向触发器表达式中匹配的第1个，第2个，第3个等主机。 请参考[宏索引](supported_by_location#indexed_macros)。| |{SERVICE.NAME}|→ 基于服务的通知和命令<br>→ 服务的通知和命令|*服务名称* (已解析宏)。| |{SERVICE.ROOTCAUSE}|→ 基于服务的通知和命令<br>→ 服务的通知和命令|*导致服务失败的触发问题事件列表*, 使用安全性主机排序。 包括以下详细信息：主机名、事件名称、严重性、持续时间、服务标签和值。 | |{SERVICE.TAGS}|→ 基于服务的通知和命令<br>→ 服务的通知和命令|*服务事件标签的逗号分隔列表。* 服务事件标签可以在服务配置选项标签中定义。如果不存在标签，则扩展为空字符串。| |{SERVICE.TAGSJSON}|→ 基于服务的通知和命令<br>→ 服务的通知和命令|*包含服务事件标签对象的 JSON 数组。* 服务事件标签可以在服务配置选项标签中定义。 如果不存在标签，则扩展为空数组。| |{SERVICE.TAGS.<tag name>}|→ 基于服务的通知和命令<br>→ 服务的通知和命令|*标签名称引用的服务事件标签值。* 服务事件标签可以在服务配置选项标签中定义。<br>包含非字母数字字符（包括非英语多字节 UTF 字符）的标签名称应该用双引号引起来。 带引号的标记名称中的引号和反斜杠必须使用反斜杠进行转义。| |{TIME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于服务的通知和命令<br>→ 服务的通知和命令<br>→ 发现的通知和命令<br>→ 自动注册通知和命令 <br>→ 内部通知<br>→ 触发器事件名称<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*现在的时间，格式为 hh:mm:ss*| |{TRIGGER.DESCRIPTION}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器描述。*<br>如果在通知中使用了`{TRIGGER.DESCRIPTION}`，则触发器描述中支持的所有宏都将被扩展。<br>`{TRIGGER.COMMENT}` 已弃用。| |{TRIGGER.EXPRESSION.EXPLAIN}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件<br>→ 事件名称|*部分评估的触发器表达式。*<br>基于监控项的函数在事件生成时被评估并替换为结果，而所有其他函数都显示为表达式中所写的。可用于调试触发器表达式。| |{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands<br>→ 故障更新通知和命令<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*部分评估触发恢复表达式.*<br>基于触发器的函数在事件生成时被评估并替换为结果，而所有其他函数都显示为表达式中所写的。可用于调试触发恢复表达式。| |{TRIGGER.EVENTS.ACK}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 地图元素标签<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*地图中地图元素或在通知中生成当前事件的触发器的已确认事件数。*| |{TRIGGER.EVENTS.PROBLEM.ACK}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 地图元素标签<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*所有触发器的已确认 PROBLEM 事件的数量，无论其状态。*| |{TRIGGER.EVENTS.PROBLEM.UNACK}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 地图元素标签<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*所有触发器的未确认问题事件数，无论其状态。*| |{TRIGGER.EVENTS.UNACK}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 地图元素标签<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*地图中地图元素或在通知中生成当前事件的触发器的未确认事件数。*| |{TRIGGER.HOSTGROUP.NAME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*定义了触发器的已排序（按 SQL 查询）、以逗号分隔的主机组列表名称。*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}|→ 地图元素标签|*处于PROBLEM状态的触发器已确认的PROBLEM事件数。*| |{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}|→ 地图元素标签|*处于PROBLEM状态的触发器的未确认PROBLEM事件数。*| |{TRIGGER.EXPRESSION}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器表达式。*| |{TRIGGER.EXPRESSION.RECOVERY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发恢复表达式* 如果*事件生成OK*在[触发器配置](/manual/config/triggers/trigger)被用于'恢复表达'; 否者返回空的string字段。<br>支持的最低版本是 3.2.0.| |{TRIGGER.ID}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 地图元素标签,地图URL的名称和值<br>→ 触发器的URL地址<br>→ Trigger tag value<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发此操作的触发器ID。*<br>从Zabbix的4.4.1版本开始在触发标记值中受支持。| |{TRIGGER.NAME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器的名称* (已解析宏).<br>请注意自4.0.0开始，{EVENT.NAME} 可用于操作以显示已解析的宏触发的事件/问题名称。 | |{TRIGGER.NAME.ORIG}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器的原始名称* (即未解析宏).| |{TRIGGER.NSEVERITY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*使用数字表达的触发严重性* 可能的值: |0 - 未分类，1 - 信息，2 - 警告，3 - 平均，4 - 高，5 - 灾难。  |{TRIGGER.SEVERITY}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器严重性名称* 可以在这里定义 *管理 → 通用 → 触发器展示选项*.| |{TRIGGER.STATE}|→ 基于触发器的内部通知|*触发器的最新状态* 可能的值: **未知** 和 **正常**.| |{TRIGGER.STATUS}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*当前触发器的值* 可以是 PROBLEM 或者 OK.<br>`{STATUS}` 已弃用。| |{TRIGGER.TEMPLATE.NAME}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*值为已排序（按 SQL 查询）、逗号分隔的模板列表中定义了触发器，如果触发器是在主机中定义的则为 \*未知\*。*| |{TRIGGER.URL}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 基于触发器的内部通知<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*触发器的URL地址。*| |{TRIGGER.VALUE}|→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 触发器表达式<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件|*当前触发数值*: 0 - 触发器处于正常状态, 1 - 触发器处于问题状态。| |{TRIGGERS.UNACK}|→ 地图元素标签|*地图元素中已取消确认问题触发器的数量，忽略触发器状态。*<br>如果至少有一个问题事件已取消确认，则触发器被视为已取消确认。 | |{TRIGGERS.PROBLEM.UNACK}|→ 地图元素标签|*在地图标签中未确认的触发器（状态为PROBLEM）总数。*<br>如果至少有一个问题事件已取消确认，则触发器被视为已取消确认。 | |{TRIGGERS.ACK}|→ 地图元素标签|*地图元素中已确认触发器的数量, 忽略触发器状态。*<br>如果触发器的所有问题事件都被确认，则认为触发器已被确认。 | |{TRIGGERS.PROBLEM.ACK}|→ 地图元素标签|*地图元素中已确认触发器的数量。*<br>如果触发器的所有问题事件都被确认，则认为触发器已被确认。 | |{USER.FULLNAME}|→ 故障更新通知和命令<br>→ 对主机手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件 (including confirmation text)|在事件确认和脚本操作中添加*用户的姓氏、名字和完整姓名*的信息。<br>从Zabbix的3.4.0版本开始在问题更新功能中支持此宏，从5.0.2开始在全局功能中支持。| |{USER.NAME}|→ 对主机手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件 (including confirmation text)|启动脚本的*用户的名字*。<br>支持的最低版本是 5.0.2.| |{USER.SURNAME}|→ 对主机手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件 (including confirmation text)|启动脚本的*用户的姓氏*。<br>支持的最低版本是 5.0.2.| |{USER.USERNAME}|→ 对主机手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)<br>→ 手动操作[脚本](/manual/web_interface/frontend_sections/administration/scripts)事件 (including confirmation text)|启动脚本的*完整用户名称*（包括姓氏和名字）。<br>支持的最低版本是 5.0.2.<br>{USER.ALIAS}仅支持Zabbix 5.4.0以前的版本,此版本已弃用。| |{$MACRO}|→ 参阅: [User macros supported by location](/manual/appendix/macros/supported_by_location_user)|*[用户自定义](/manual/config/macros/user_macros) 宏。*| |{\#MACRO}|→ 参阅: [低级别自动发现宏](/manual/config/macros/lld_macros)|*低级别自动发现宏。*<br><br>[定制](/manual/config/macros/macro_functions) 宏的值, 从Zabbix的4.0.0版本开始。| |{?EXPRESSION}|→ 触发器事件名称<br>→ 基于触发器的通知和命令<br>→ 故障更新通知和命令<br>→ 地图元素标签^[3](supported_by_location#footnotes)^<br>→ 地图分享标签^[3](supported_by_location#footnotes)^<br>→ 地图中的链接标签^[3](supported_by_location#footnotes)^<br>→ 图表名称^[5](supported_by_location#footnotes)^|*表达式宏*用于公式计算。通过扩展内部的所有宏并评估结果表达式来计算。 <br>参阅 [案例](/[[/manual/config/triggers/expression#example_17) 在事件名称中使用表达式宏。<br>支持的最低版本是 5.2.0.|

en-us	#### Overview  The trigger list for a host can be accessed from *Configuration → Hosts* by clicking on *Triggers* for the respective host.  ![](../../../../../../assets/en/manual/web_interface/triggers.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Severity*|Severity of the trigger is displayed by both name and cell background color.| |*Value*|Trigger value is displayed:<br>**OK** - the trigger is in the OK state<br>**PROBLEM** - the trigger is in the Problem state| |*Host*|Host of the trigger.<br>This column is displayed only if multiple hosts are selected in the filter.| |*Name*|Name of the trigger, displayed as a blue link to trigger details.<br>Clicking on the trigger name link opens the trigger [configuration form](/manual/config/triggers/trigger#configuration).<br>If the host trigger belongs to a template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger list on the template level.<br>If the trigger has been created from a trigger prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the trigger prototype list.| |*Operational data*|Operational data definition of the trigger, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Expression*|Trigger expression is displayed. The host-item part of the expression is displayed as a link, leading to the item configuration form.| |*Status*|Trigger status is displayed - *Enabled*, *Disabled* or *Unknown*. By clicking on the status you can change it - from Enabled to Disabled (and back); from Unknown to Disabled (and back).<br>Problems of a disabled trigger are no longer displayed in the frontend, but are not deleted.| |*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.| |*Tags*|If a trigger contains tags, tag name and value are displayed in this column.|  To configure a new trigger, click on the *Create trigger* button at the top right corner.
zh-cn	#### 概述  在“*配置→主机”中，点击对应主机的*触发器*，可查看对应主机的触发列表。  ![](../../../../../../assets/en/manual/web_interface/triggers.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*严重级别*|该触发器的级别，通过名称和单元格背景颜色显示| |*值*|显示触发值:<br>**OK**—触发状态为OK。<br>**问题**—触发状态为问题 | |*主机*|触发器所在主机。<br>当过滤框中选择了多个主机时，此字段才会显示| |*名称*|触发器名称，显示为蓝色链接，表示触发器详细信息。<br>点击触发器名称链接打开触发器[配置表单](/manual/config/triggers/trigger#configuration)。<br>如果主机触发器属于模板，则模板名称显示在触发器名称前面，为灰色链接。单击模板链接将打开模板级别的触发器列表。<br>如果触发器是从触发器原型创建的，其名称前面是低级自动发现规则名称，用橙色表示。单击发现规则名称将打开触发器原型列表 |*运行数据*|触发器的运行数据定义，包含将在*监控*→*问题*中动态解析的任意字符串和宏| |*表达式*|显示触发器表达式，表达式的主机-监控项部分以链接的形式显示，导向监控项的配置表单。| |*状态*|触发状态- *启用*、*禁用*或*位置*。通过点击状态，您可以改变它-从启用到禁用(或反过来);从未知到禁用(或反过来)。<br>触发器被禁用后，不再在前端显示问题，但不删除| |*信息*|正常情况下，此列无图标。如果出现错误，则会显示一个带有字母“i”的方形图标。将鼠标悬停在图标上可以看到一个带有错误描述的工具提示。| |*标签*|当触发器包含标签时，此列显示标签名称和值  如需配置新触发器，请单击右上角的“*创建触发器*”按钮。

en-us	#### Overview  The trigger list for a template can be accessed from *Configuration → Templates* by clicking on *Triggers* for the respective template.  ![](../../../../../../assets/en/manual/web_interface/template_triggers.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Severity*|Severity of the trigger is displayed by both name and cell background color.| |*Template*|Template the trigger belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the trigger displayed as a blue link to trigger details.<br>Clicking on the trigger name link opens the trigger [configuration form](/manual/config/triggers/trigger#configuration).<br>If the trigger is inherited from another template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger list on that template level.| |*Operational data*|Operational data definition of the trigger, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Expression*|Trigger expression is displayed. The template-item part of the expression is displayed as a link, leading to the item configuration form.| |*Status*|Trigger status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|If a trigger contains tags, tag name and value are displayed in this column.|  To configure a new trigger, click on the *Create trigger* button at the top right corner.
zh-cn	#### 概览  在*配置→模板*中，点击对应模板的*触发器*，可查看对应模板的触发器列表。  ![](../../../../../../assets/en/manual/web_interface/template_triggers.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*严重等级*|该触发器的级别，通过名称和单元格背景颜色显示| |*模板*|触发器所属的模板。<br>当筛选框中选择了多个模板时，此字段才会显示。| |*名称*|触发器的名称，以蓝色链接的形式显示，可了解触发器的详细信息。<br>单击触发器名称链接将打开触发器 [配置表格](/manual/config/triggers/trigger#configuration).<br>如果触发器是从其他模板继承的，则模板名称会以灰色链接的形式显示在触发器名称前面。单击模板链接将打开该模板级别的触发器列表。| |*运行时数据*|触发器的运行时数据定义，包含在*监控*→*问题*中动态解析的任意字符串和宏变量。| |*表达式*|显示触发器表达式。表达式的模板-监控项部分显示为一个链接，连接到监控项配置形式。| |*状态*|显示触发状态-*启用*”或“*禁用*”。通过单击状态，您可以更改它-从启用到禁用(并返回)。| |*标签*|如果触发器包含标签，此列显示标签名称和值。|  单击右上角的“*创建触发器*”按钮，可新建触发器。

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

en-us	#### Overview  The webhook media type is useful for making HTTP calls using custom JavaScript code for straightforward integration with external software such as helpdesk systems, chats, or messengers. You may choose to import an integration provided by Zabbix or create a custom integration from scratch.
zh-cn	#### 概述  webhook 媒体类型对于使用自定义的JavaScript代码进行HTTP调用非常有用，它可以直接与外部软件（如 Helpdesk 系统、聊天工具或信使）进行集成。您可以选择使用 Zabbix 提供的集成方式或创建一个自定义集成方式。

en-us	#### Overview  The web scenario list for a host can be accessed from *Configuration → Hosts* by clicking on *Web* for the respective host.  A list of existing web scenarios is displayed.  ![](../../../../../../assets/en/manual/web_interface/web_scenarios.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the web scenario. Clicking on the web scenario name opens the web scenario [configuration form](/manual/web_monitoring#configuring_a_scenario).<br>If the host web scenario belongs to a template, the template name is displayed before the web scenario name as a gray link. Clicking on the template link will open the web scenario list on the template level.| |*Number of steps*|The number of steps the scenario contains.| |*Update interval*|How often the scenario is performed.| |*Attempts*|How many attempts for executing web scenario steps are performed.| |*Authentication*|Authentication method is displayed - Basic, NTLM, or None.| |*HTTP proxy*|Displays HTTP proxy or 'No' if not used.| |*Status*|Web scenario status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| |*Tags*|Web scenario tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| |*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|  To configure a new web scenario, click on the *Create web scenario* button at the top right corner.
zh-cn	#### 概述  主机的web场景列表可在“*Configuration→Hosts*”中点击对应主机的“*web*”。  显示已存在的web场景列表。 ![](../../../../../../assets/en/manual/web_interface/web_scenarios.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名称*| web场景名称。点击web场景名称打开web场景[配置表单](/manual/web_monitoring#configuring_a_scenario)。<br>如果web场景是从其他模板继承的，则web场景名称前以灰色链接显示模板名称。点击模板链接将打开该模板级别的web场景列表| |*步骤数*|场景包含的步骤数| |*更新周期*|场景多长时间更新一次| |*重试次数*|执行web场景步骤的重试次数| |*认证*|显示认证方式-基本，NTLM on None| |*HTTP代理*|如果不使用HTTP代理，则显示“No”| |*状态*|Web场景状态- *启用*或*禁用*。<br>通过单击状态可以更改| |*标签*|Web场景标签。<br>最多可以显示三个标签(名称:键值对)。如果有更多的标签，会显示一个“…”链接，当标签鼠标悬停，会看到所有的标签。| |*信息*|如果一切正常，此列中没有显示图标。如果出现错误，则会显示一个带有字母“i”的方形图标。将鼠标悬停在图标上可以看到一个带有错误描述的工具提示。|  要配置新的web场景，请单击右上角的*创建web场景*按钮。

en-us	#### Overview  The web scenario list for a template can be accessed from *Configuration → Templates* by clicking on *Web* for the respective template.  A list of existing web scenarios is displayed.  ![](../../../../../../assets/en/manual/web_interface/template_web_scenarios.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the web scenario. Clicking on the web scenario name opens the web scenario [configuration form](/manual/web_monitoring#configuring_a_scenario).<br>If the web scenario is inherited from another template, the template name is displayed before the web scenario name, as a gray link. Clicking on the template link will open the web scenarios list on that template level.| |*Number of steps*|The number of steps the scenario contains.| |*Update interval*|How often the scenario is performed.| |*Attempts*|How many attempts for executing web scenario steps are performed.| |*Authentication*|Authentication method is displayed - Basic, NTLM on None.| |*HTTP proxy*|Displays HTTP proxy or 'No' if not used.| |*Status*|Web scenario status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| |*Tags*|Web scenario tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.|  To configure a new web scenario, click on the *Create web scenario* button at the top right corner.
zh-cn	#### 概述  模板的web场景列表可以从*配置→模板*点击相应的模板的*web*访问。  显示已存在的web场景列表。  ![](../../../../../../assets/en/manual/web_interface/template_web_scenarios.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名称*| web场景名称。点击web场景名称打开web场景[配置表单](/manual/web_monitoring#configuring_a_scenario)。<br>如果web场景是从其他模板继承的，则web场景名称前以灰色链接显示模板名称。点击模板链接将打开该模板级别的web场景列表| |*步骤数*|场景包含的步骤数| |*更新周期*|场景多长时间更新一次| |*重试次数*|执行web场景步骤的重试次数| |*认证*|显示认证方式-基本，NTLM on None| |*HTTP代理*|如果不使用HTTP代理，则显示“No”| |*状态*|Web场景状态- *启用*或*禁用*。<br>通过单击状态可以更改| |*标签*|Web场景标签。<br>最多可以显示三个标签(名称:键值对)。如果有更多的标签，会显示一个“…”链接，当标签鼠标悬停，会看到所有的标签。|  要配置新的web场景，请单击右上角的*创建web场景*按钮。

en-us	#### Overview  This item type allows data polling using the HTTP/HTTPS protocol. Trapping is also possible using Zabbix sender or Zabbix sender protocol.  HTTP item check is executed by Zabbix server. However, when hosts are monitored by a Zabbix proxy, HTTP item checks are executed by the proxy.  HTTP item checks do not require any agent running on a host being monitored.  HTTP agent supports both HTTP and HTTPS. Zabbix will optionally follow redirects (see the *Follow redirects* option below). Maximum number of redirects is hard-coded to 10 (using cURL option CURLOPT\_MAXREDIRS).  See also [known issues](/manual/installation/known_issues#https_checks) for when using HTTPS protocol.  ::: noteimportant Zabbix server/proxy must be initially configured with cURL (libcurl) support. :::
zh-cn	#### 概述  此监控项类型允许使用HTTP/HTTPS协议进行数据轮询。使用Zabbix sender或Zabbix sender协议也可以进行捕获。  HTTP监控项检查由Zabbix服务器执行。但是，当主机由Zabbix proxy监控时，HTTP项检查由proxy执行。  HTTP 监控项检查不需要任何 agent 运行在被监控的主机上。  HTTP agent同时支持HTTP和HTTPS。Zabbix可以选择跟随重定向（参考下文 *Follow redirects* 的选项）。最大重定向数硬编码为10（用cURL的参数 CURLOPT_MAXREDIRS）  了解何时使用HTTPS协议，另请参阅[已知问题](/manual/installation/known_issues#https_checks)  ::: noteimportant Zabbix server/proxy必须首先配置cURL(libcurl)支持。 :::

en-us	#### Overview  This page provides a list of cookies used by Zabbix.  |Name|Description|Values|Expires/Max-Age|HttpOnly[^1]|Secure[^2]| |----|-----------|------|---------------|------------|----------| |ZBX\_SESSION\_NAME|Zabbix frontend session data, stored as JSON encoded by base64|<|Session (expires when the browsing session ends)|\+|\+ (only if HTTPS is enabled on a web server)| |tab|Active tab number; this cookie is only used on pages with multiple tabs (e.g. *Host*, *Trigger* or *Action* configuration page) and is created, when a user navigates from a primary tab to another tab (such as *Tags* or *Dependencies* tab).<br><br>0 is used for the primary tab.|Example: 1|Session (expires when the browsing session ends)|\-|\-| |browserwarning\_ignore|Whether a warning about using an outdated browser should be ignored.|yes|Session (expires when the browsing session ends)|\-|\-| |system-message-ok|A message to show as soon as page is reloaded.|Plain text message|Session (expires when the browsing session ends) or as soon as page is reloaded|\+|\-| |system-message-error|An error message to show as soon as page is reloaded.|Plain text message|Session (expires when the browsing session ends) or as soon as page is reloaded|\+|\-|  ::: noteclassic  Forcing 'HttpOnly' flag on Zabbix cookies by a webserver directive is not supported.  :::  [^1]: When `HttpOnly` is 'true' the cookie will be made accessible only     through the HTTP protocol. This means that the cookie won't be     accessible by scripting languages, such as JavaScript. This setting     can effectively help to reduce identity theft through XSS attacks     (although it is not supported by all browsers).  [^2]: `Secure` indicates that the cookie should only be transmitted over     a secure HTTPS connection from the client. When set to 'true', the     cookie will only be set if a secure connection exists.
zh-cn	#### 概述  此页面提供了 Zabbix 使用的 cookie 列表。  |名称|描述|值|过期/最大年龄|HttpOnly[^1]|安全[^2]| |----|-----------|------|---------------|------------|----------| |ZBX\_SESSION\_NAME|Zabbix 前端会话数据，存储为base64编码的JSON|<|会话（浏览会话结束时过期）|\+|\+（仅当在Web服务器上启用HTTPS时）| |tab|活动标签号；此 cookie 仅用于具有多个选项卡的页面（例如 *Host*、*Trigger* 或 *Action* 配置页面），并在用户从主选项卡导航到另一个选项卡时创建（例如 *Tags* 或 *Dependencies * 选项卡）。<br><br>0 用于主选项卡。|示例：1|会话（浏览会话结束时到期）|\-|\-| |browserwarning\_ignore|是否应该忽略有关使用过时浏览器的警告。|yes|会话（浏览会话结束时过期）|\-|\-| |system-message-ok|页面重新加载后立即显示的消息。|纯文本消息|会话（浏览会话结束时到期）或页面重新加载后立即显示|\+|\-| |system-message-error|重新加载页面后立即显示的错误消息。|纯文本消息|会话（在浏览会话结束时到期）或页面重新加载后立即显示|\+|\-|  ::: noteclassic 不支持通过 webserver 指令在 Zabbix cookie 上强制使用 'HttpOnly' 标志。 :::  [^1]：当 `HttpOnly` 为 'true' 时，cookie 将只能通过 HTTP 协议访问。这意味着 cookie 将无法通过 JavaScript 等脚本语言访问。此设置可以有效帮助减少通过 XSS 攻击进行的身份盗用（尽管并非所有浏览器都支持）。  [^2]: `Secure` 表示 cookie 只能通过来自客户端的安全 HTTPS 连接传输。当设置为“true”时，只有存在安全连接时才会设置 cookie。

en-us	### Overview  This page provides the steps required to build a loadable plugin binary from the sources.  If the source tarball is downloaded, it is possible to build the plugin offline, i.e. without the internet connection.  The PostgreSQL plugin is used as an example. Other loadable plugins can be built in a similar way.
zh-cn	### 概览  此页面提供了从源码构建可加载插件二进制文件所需的步骤。  如果下载了源码压缩包，则可以离线构建插件，例如，没有互联网连接。  以 PostgreSQL 插件为例。 可以用类似的方式构建其他可加载插件。

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

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

en-us	#### Overview  This section contains best practices that should be observed in order to set up Zabbix in a secure way.  The practices contained here are not required for the functioning of Zabbix. They are recommended for better security of the system.
zh-cn	#### 概述  本章节内容提供了对于Zabbix来说，可采用更加安全的安装方式。  实现Zabbix的功能并不局限于该范例中所涉及的内容。但建议用户可通过参考该配置方式为Zabbix提供更好的系统安全性。

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

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

en-us	#### Overview  This section demonstrates how to build Zabbix agent 2 (Windows) from sources.
zh-cn	#### 概述  本节将演示如何从源代码构建Zabbix agent 2 (Windows)。

en-us	#### Overview  This section demonstrates how to build Zabbix macOS agent binaries from sources with or without TLS.  
zh-cn	#### 概述  本节演示如何从包含或不包含 TLS 的源代码构建 Zabbix macOS agent 二进制文件。

en-us	#### Overview  This section demonstrates how to build Zabbix Windows agent binaries from sources with or without TLS.
zh-cn	#### 概述  本节将演示如何从有或没有TLS的源构建 Zabbix Windows agent二进制文件。

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

en-us	### Overview  This section describes Zabbix additions to the JavaScript language implemented with Duktape and supported global JavaScript functions.
zh-cn	### 概述  本节介绍Zabbix对JavaScript语言的支持，该语言使用Duktape和受支持的全局JavaScript函数实现。

en-us	#### Overview  This section explains how to add a “Host group” type element when configuring a [network map](/manual/config/ visualization/maps/map).
zh-cn	#### 概述  本节说明如何在配置[网络地图](/manual/config/visualization/maps/map)时添加“ Host group”类型的元素。

en-us	#### Overview  This section lists parameters supported in a Zabbix agent configuration file (zabbix\_agentd.conf). Note that:  -   The default values reflect daemon defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported in the beginning of     the line.
zh-cn	#### 概览  本节列出了 Zabbix agent 的配置文件（zabbix\_agentd.conf）中支持的参数。 请注意：  -   默认值反映的是守护进程的默认值，而不是附带的配置文件中的值； -   Zabbix 仅支持 UTF-8 编码的配置文件，且编码中不可使用[字节顺序标记（BOM）](https://en.wikipedia.org/wiki/Byte_order_mark)； -   仅在行首支持以 “\#” 开始的注释。

en-us	#### Overview  This section lists parameters supported in a Zabbix proxy configuration file (zabbix\_proxy.conf). Note that:  -   The default values reflect daemon defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported in the beginning of     the line.
zh-cn	#### 概览  本节列出了 Zabbix proxy 的配置文件（zabbix\_proxy.conf）中支持的参数。 请注意：  -   默认值反映的是守护进程的默认值，而不是附带的配置文件中的值； -   Zabbix 仅支持 UTF-8 编码的配置文件，且编码中不可使用[字节顺序标记（BOM）](https://en.wikipedia.org/wiki/Byte_order_mark)； -   仅在行首支持以“\#”开始的注释。

en-us	#### Overview  This section lists parameters supported in a Zabbix server configuration file (zabbix\_server.conf). Note that:  -   The default values reflect daemon defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported in the beginning of     the line.
zh-cn	#### 概述  本节列出了 Zabbix 服务器配置文件（Zabbix\_server.conf）中支持的参数。请注意：  -   默认值反映的是守护进程的默认值，而不是附带的配置文件中的值； -   Zabbix 仅支持 UTF-8 编码的配置文件，不支持 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) 格式； -   以 “\#” 开头的注释只支持在行首。

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

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

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

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

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

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

en-us	#### Overview  This section presents examples of using preprocessing steps to accomplish some practical tasks.
zh-cn	#### 概述  本节介绍使用预处理步骤完成一些实际任务的示例。

en-us	#### Overview  This section provides details of preprocessing by JavaScript.
zh-cn	#### 概述  本节提供 JavaScript 预处理的详细信息。

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

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

en-us	 ### Overview  This section provides information on:  *   Agent2 -> Server : active checks request *   Server -> Agent2 : active checks response  *   Agent2 -> Server : agent data request *   Server -> Agent2 : agent data response
zh-cn	 ### 概览  本节提供有关信息:  * · Agent2 -> Server : 主动检查请求 * · Server -> Agent2 : 主动检查响应  * · Agent2 -> Server : 代理数据请求 * · Server -> Agent2 : 代理数据响应

en-us	#### Overview  This section provides item value preprocessing details. Item value preprocessing allows to define and execute [transformation rules](/manual/config/items/preprocessing) for the received item values.  Preprocessing is managed by a preprocessing manager process, which was added in Zabbix 3.4, along with preprocessing workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is used between data gatherers (pollers, trappers, etc) and the preprocessing process. Either Zabbix server or Zabbix proxy (for items monitored by the proxy) is performing preprocessing steps.
zh-cn	#### 概述  本节提供监控项值预处理详细信息。 监控项值预处理允许为接收到的监控项值定义和执行[转换规则](/manual/config/items/preprocessing) 。  预处理由预处理管理进程管理，该进程在Zabbix 3.4中添加，用于执行预处理步骤。 所有来自不同数据收集器的值（无论是否经过预处理）都会在添加到历史缓存之前通过预处理管理器。 基于套接字的 IPC 通信作用于数据收集器（轮询器、捕获器等）和预处理进程之间。 Zabbix server或 Zabbix proxy（由代理监控的监控项）负责执行预处理步骤。

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

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

en-us	#### Overview  This section provides the details of parameters that are  common for [dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard) widgets.  #### Common parameters  The following parameters are common for every single widget:  |   |   | |---|---| |*Name*|Enter a widget name.| |*Refresh interval*|Configure default refresh interval. Default refresh intervals for widgets range from *No refresh* to *15 minutes* depending on the type of widget. For example: *No refresh* for URL widget, *1 minute* for action log widget, *15 minutes* for clock widget.| |*Show header*|Mark the checkbox to show the header permanently.<br>When unchecked the header is hidden to save space and only slides up and becomes visible again when the mouse is positioned over the widget, both in view and edit modes. It is also semi-visible when dragging a widget to a new place.|  Refresh intervals for a widget can be set to a default value for all the corresponding users and also each user can set his own refresh interval value:  -   To set a default value for all the corresponding users switch to     editing mode (click the *Edit dashboard* button, find the right     widget, click the *Edit* button opening the editing form of a     widget), and choose the required refresh interval from the dropdown     list. -   Setting a unique refresh interval for each user separately is     possible in view mode by clicking the     ![](../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/edit_button_widget_view.png)     button for a certain widget.  Unique refresh interval set by a user has priority over the widget setting and once it's set it's always preserved when the widget's setting is modified.  To see **specific parameters** for each widget, go to individual widget pages  for:  -   [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)  
zh-cn	#### Overview  This section provides the details of parameters that are  common for [dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard) widgets.  #### Common parameters  The following parameters are common for every single widget:  |   |   | |---|---| |*Name*|Enter a widget name.| |*Refresh interval*|Configure default refresh interval. Default refresh intervals for widgets range from *No refresh* to *15 minutes* depending on the type of widget. For example: *No refresh* for URL widget, *1 minute* for action log widget, *15 minutes* for clock widget.| |*Show header*|Mark the checkbox to show the header permanently.<br>When unchecked the header is hidden to save space and only slides up and becomes visible again when the mouse is positioned over the widget, both in view and edit modes. It is also semi-visible when dragging a widget to a new place.|  Refresh intervals for a widget can be set to a default value for all the corresponding users and also each user can set his own refresh interval value:  -   To set a default value for all the corresponding users switch to     editing mode (click the *Edit dashboard* button, find the right     widget, click the *Edit* button opening the editing form of a     widget), and choose the required refresh interval from the dropdown     list. -   Setting a unique refresh interval for each user separately is     possible in view mode by clicking the     ![](../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/edit_button_widget_view.png)     button for a certain widget.  Unique refresh interval set by a user has priority over the widget setting and once it's set it's always preserved when the widget's setting is modified.  To see **specific parameters** for each widget, go to individual widget pages  for:  -   [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)  

en-us	#### Overview  This section provides the details of parameters that are  common for [dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard) widgets.  #### Common parameters  The following parameters are common for every single widget:  |   |   | |---|---| |*Name*|Enter a widget name.| |*Refresh interval*|Configure default refresh interval. Default refresh intervals for widgets range from *No refresh* to *15 minutes* depending on the type of widget. For example: *No refresh* for URL widget, *1 minute* for action log widget, *15 minutes* for clock widget.| |*Show header*|Mark the checkbox to show the header permanently.<br>When unchecked the header is hidden to save space and only slides up and becomes visible again when the mouse is positioned over the widget, both in view and edit modes. It is also semi-visible when dragging a widget to a new place.|  Refresh intervals for a widget can be set to a default value for all the corresponding users and also each user can set his own refresh interval value:  -   To set a default value for all the corresponding users switch to     editing mode (click the *Edit dashboard* button, find the right     widget, click the *Edit* button opening the editing form of a     widget), and choose the required refresh interval from the dropdown     list. -   Setting a unique refresh interval for each user separately is     possible in view mode by clicking the     ![](../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/edit_button_widget_view.png)     button for a certain widget.  Unique refresh interval set by a user has priority over the widget setting and once it's set it's always preserved when the widget's setting is modified.  To see **specific parameters** for each widget, go to individual widget pages  for:  -   [Action log](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/action_log) -   [Clock](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/clock) -   [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) -   [SLA report](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/sla_report) -   [System information](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/system) -   [Problems by severity](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problems_severity) -   [Top hosts](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts) -   [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)
zh-cn	#### 概述  此章节提供了[仪表盘](/manual/web_interface/frontend_sections/monitoring/dashboard)组件的通用参数细节。  #### 通用参数  以下参数对每个组件都是通用的：  |   |   | |---|---| |*名称*|输入组件名称。| |*刷新间隔*|配置默认刷新间隔。组件的默认刷新间隔从*不刷新*到*15分钟*取决于组件的类型。示例：URL组件是*不刷新*，动作记录组件是*1分钟*，时钟组件是*15分钟*。| |*显示组件头部*|勾选多选框来永久显示组件头部。<br>当取消勾选时，无论在查看还是编辑模式，为了节省空间，头部会被隐藏，只有在鼠标位于组件上方时向上滑动能重新显示头部。当拖动组件到新位置时，头部也会部分可见。|  组件的刷新间隔可为所有相关用户设为一个默认值，也可为每个用户单独设置其刷新间隔：  -   要为所有相关用户设为一个默认值，切换到编辑模式（点击*编辑仪表盘*按钮，     找到正确的组件，点击*编辑*按钮打开组件的编辑表单），之后在下拉菜单中  选择需要的刷新间隔。 -   要为每个用户单独设置其刷新间隔，在查看模式中，点击一个组件的     ![](../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/edit_button_widget_view.png)  按钮。  一个用户设置的单独的刷新间隔优先级高于组件设置，并且一旦设置了单独 的刷新间隔，即使组件设置被修改，它也会一直保持不变。  查看每个组件的**特殊参数**，可进入单独的组件页面：  -   [动作记录](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/action_log) -   [时钟](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/clock) -   [自动发现状态](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/discovery_status) -   [收藏的图表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/favorite_graphs) -   [收藏的拓扑图](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/favorite_maps) -   [地理图](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/geomap) -   [图表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph) -   [图表（传统）](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph_classic) -   [图表原型](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/graph_prototype) -   [主机可用性](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/host_availability) -   [监控项值](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value) -   [拓扑图](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/map) -   [拓扑图导航树](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/map_tree) -   [纯文本](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/plain_text) -   [问题主机](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problem_hosts) -   [问题](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problems) -   [SLA报表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/sla_report) -   [系统信息](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/system) -   [按严重性的问题](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/problems_severity) -   [前排主机](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/top_hosts) -   [触发器概览](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/trigger_overview) -   [URL](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/url) -   [Web监控](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/web_monitoring)

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Debian/Ubuntu.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x|For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|<| |5.2.x|For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x|For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x|For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x|For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x|For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x|For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x|For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::  
zh-cn	#### 概述  本章节提供了在 Debian/Ubuntu 系统上使用 Zabbix 二进制包，从 Zabbix **5.4**.x 成功 [upgrade](/manual/installation/upgrade) 到 Zabbix **6.0**.x 所需的步骤。  虽然升级 Zabbix 代理不是强制性的（但建议将其升级），但 但 Zabbix server和proxy必须具有[相同主版本]。因此，在Zabbix server 和 Zabbix proxy 的架构升级时，Zabbix server 和所有的 Zabbix proxy必须停止服务并进行升级。在Zabbix server 升级期间，保持Zabbix proxy 运行正常并不好，因为在Zabbix proxy升级期间，它们的旧数据将被丢弃，并且在Zabbix proxy配置与Zabbix server同步前并不会收集新数据。  请注意，若Proxy的数据库为SQLite类型，其保留的历史数据会在版本升级完成后全部被删除，因为不支持 SQLite 数据库升级并且必须手动删除 SQLite 数据库文件。当第一次启动Zabbix proxy并且缺少 SQLite 数据库文件时，Zabbix proxy会自动创建它。  在数据库升级到版本 6.0 时，根据数据库存储大小，可能需花很长时间升级完毕。  ::: 注意事项 升级前请务必阅读相关 **upgrade notes!** :::  如下提供升级说明：  |升级前版本|阅读完整的升级说明|版本之间最重要的变化| |------------|-----------------------|---------------------------------------| |5.4.x|适用于：<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|<| |5.2.x|适用于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600) |提高了最低要求的数据库版本；<br>将聚合项作为单独的类型删除。| |5.0.x|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|所需的最低 PHP 版本从 7.2.0 提高到 7.2.5。| |4.4.x|适用于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|放弃对 IBM DB2 的支持；<br >最低要求的 PHP 版本从 5.4.0 提高到 7.2.0；<br>最低要求的数据库版本提高；<br>更改了 Zabbix PHP 文件目录。| |4.2.x|适用于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|已删除 Jabber、Ez 短信媒体类型。| |4.0.x LTS|适用于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2]( https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br >Zabbix [6.0](/manual/installation/upgrade_notes_600)|老的Zabbix agent不再能够向升级后的Zabbix server 报告数据；<br>新的Zabbix agent不再能够与老的 Zabbix server 一起工作。| |3.4.x|适用于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br> Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' 和 'zlib' 库现在强制；<br>删除对纯文本协议的支持，并且强制标头；<br>不再支持 1.4 之前版本的 Zabbix agent；<br>被动模式Zabbix agent配置中的 Server 参数现在是强制的。| |3.2.x|适用于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br> Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|为 Zabbix server和前端删除了作为后端数据库的 SQLite 支持；<br>支持 Perl 兼容正则表达式 (PCRE)，而不是扩展 POSIX；<br> Zabbix server强制使用“libpcre”和“libevent”库；<br>为用户参数添加了退出代码检查仪表、远程命令和不带 'nowait' 标志的 system.run\[\] 项目以及 Zabbix server执行的脚本；<br>必须升级 Zabbix Java 网关以支持新功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2]( https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br >Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/安装/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|数据库升级可能会很慢，具体取决于历史表的大小。| |2.4.x|适用于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br> Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 5.3.0 提高到 5.4.0<br>LogFile ag ent 参数必须指定| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4]( https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br >Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/安装/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/文档/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/安装/upgrade_notes_600)|移除了基于节点的分布式监控| |2.0.x|适用于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br> Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.  