[comment]: # translation:outdated
[comment]: # ({6dcfe607-6dcfe607})
# 1 Macro supportate
[comment]: # ({/6dcfe607-6dcfe607})
[comment]: # ({d36c0744-d36c0744})
#### 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications|*Numeric ID of the triggered action.*|
|{ACTION.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications|*Name of the triggered action.*|
|{ALERT.MESSAGE}|→ Alert script parameters|*'Default message' value from action configuration.*
Supported since 3.0.0.|
|{ALERT.SENDTO}|→ Alert script parameters|*'Send to' value from user media configuration.*
Supported since 3.0.0.|
|{ALERT.SUBJECT}|→ Alert script parameters|*'Default subject' value from action configuration.*
Supported since 3.0.0.|
|{DATE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ 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.*
Available always, does not depend on host being added.|
|{DISCOVERY.DEVICE.DNS}|→ Discovery notifications and commands|*DNS name of the discovered device.*
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.
For example: 1h 29m 01s.
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.*
For example: HTTP.|
|{DISCOVERY.SERVICE.PORT}|→ Discovery notifications and commands|*Port of the service that was discovered.*
For example: 80.|
|{DISCOVERY.SERVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered 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.
For example: 1h 29m 01s.
For services with status DOWN, this is the period of their downtime. \| \|{ESC.HISTORY} \|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Internal notifications \|*Escalation history. Log of previously sent messages.*
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
→ Problem update notifications and commands
→ 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ 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.
Useful in escalated messages.|
|{EVENT.DATE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ 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.
Useful in problem recovery messages.
Supported since 5.0.0.|
|{EVENT.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger URLs
→ 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the problem event that triggered an action.*
Supported since 4.0.0.|
|{EVENT.NSEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ 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.
Supported since 4.0.0.|
|{EVENT.OBJECT}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of of the event object.* Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.
Supported since 4.4.0.|
|{EVENT.OPDATA}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Operational data of the underlying trigger of a problem.*
Supported since 4.4.0.|
|{EVENT.RECOVERY.DATE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (if recovery took place)|*Name of the recovery event.*
Supported since 4.4.1.|
|{EVENT.RECOVERY.STATUS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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.
Supported since 3.2.0.|
|{EVENT.RECOVERY.TAGSJSON}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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.
Supported since 5.0.0.|
|{EVENT.RECOVERY.TIME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the event severity.*
Supported since 4.0.0.|
|{EVENT.SOURCE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ 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.
Supported since 4.4.0.|
|{EVENT.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ 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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ 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.
Supported since 3.2.0.|
|{EVENT.TAGSJSON}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ 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.
Supported since 5.0.0.|
|{EVENT.TAGS.}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Webhook media type URL names and URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Event tag value referenced by the tag name.*
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.
Supported since 4.4.2.|
|{EVENT.TIME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ 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).
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).
Supported since 4.0.0.|
|{EVENT.UPDATE.DATE}|→ Problem update notifications and commands
→ Service update notifications and commands|*Date of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*
Deprecated name: {ACK.DATE}|
|{EVENT.UPDATE.HISTORY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Log of problem updates (acknowledgments, etc).*
Deprecated name: {EVENT.ACK.HISTORY}|
|{EVENT.UPDATE.MESSAGE}|→ Problem update notifications and commands|*Problem update message.*
Deprecated name: {ACK.MESSAGE}|
|{EVENT.UPDATE.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric value of of the problem update status.* Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.
Supported since 4.4.0.|
|{EVENT.UPDATE.TIME}|→ Problem update notifications and commands
→ Service update notifications and commands|*Time of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*
Deprecated name: {ACK.TIME}|
|{EVENT.VALUE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ 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
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Event names|*Results of the Nth item-based function in the trigger expression at the time of the event.*
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
→ Problem update notifications and commands
→ 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.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Description of item value widget|*Host IP address or DNS name, depending on host settings*^[2](supported_by_location#footnotes)^.
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
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host description.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Description of item value widget|*Host DNS name*^[2](supported_by_location#footnotes)^.
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Item key parameters
→ Map element labels, map URL names and values
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Description of item value widget|*Host name.*
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).
`{HOSTNAME<1-9>}` is deprecated.|
|{HOST.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ URL field of dynamic URL dashboard widget
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host ID.*
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Description of item value widget|*Host IP address*^[2](supported_by_location#footnotes)^.
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).
`{IPADDRESS<1-9>}` is deprecated.|
|{HOST.METADATA}|→ Autoregistration notifications and commands|*Host metadata.*
Used only for active agent autoregistration.|
|{HOST.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Description of item value widget|*Visible host name.*
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ JMX item endpoint field
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host (agent) port*^[2](supported_by_location#footnotes)^.
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
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|IP address or DNS name of the target host, depending on host settings.
Supported since 5.4.0.|
|{HOST.TARGET.DNS}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|DNS name of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.HOST}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|Technical name of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.IP}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|IP address of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.NAME}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|Visible name of the target host.
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Alias field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Asset tag field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Chassis field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Contact field in host inventory.*
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).
`{PROFILE.CONTACT<1-9>}` is deprecated.|
|{INVENTORY.CONTRACT.NUMBER}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Contract number field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Deployment status field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Hardware field in host inventory.*
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).
`{PROFILE.HARDWARE<1-9>}` is deprecated.|
|{INVENTORY.HARDWARE.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Hardware (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host subnet mask field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host networks field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Host router field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Hardware architecture field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Date hardware decommissioned field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Date hardware maintenance expires field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Date hardware installed field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Date hardware purchased field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Installer name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Location field in host inventory.*
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).
`{PROFILE.LOCATION<1-9>}` is deprecated.|
|{INVENTORY.LOCATION.LAT}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Location latitude field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Location longitude field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*MAC address A field in host inventory.*
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).
`{PROFILE.MACADDRESS<1-9>}` is deprecated.|
|{INVENTORY.MACADDRESS.B}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*MAC address B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Model field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Name field in host inventory.*
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).
`{PROFILE.NAME<1-9>}` is deprecated.|
|{INVENTORY.NOTES}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Notes field in host inventory.*
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).
`{PROFILE.NOTES<1-9>}` is deprecated.|
|{INVENTORY.OOB.IP}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OOB IP address field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OOB subnet mask field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OOB router field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OS field in host inventory.*
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).
`{PROFILE.OS<1-9>}` is deprecated.|
|{INVENTORY.OS.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OS (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*OS (Short) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC cell field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC email field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC phone A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC phone B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Primary POC screen name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC cell field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC email field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC phone A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC phone B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Secondary POC screen name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Serial number A field in host inventory.*
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).
`{PROFILE.SERIALNO<1-9>}` is deprecated.|
|{INVENTORY.SERIALNO.B}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Serial number B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site address A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site address B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site address C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site city field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site country field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site rack location field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site state/province field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Site ZIP/postal field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software field in host inventory.*
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).
`{PROFILE.SOFTWARE<1-9>}` is deprecated.|
|{INVENTORY.SOFTWARE.APP.A}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software application A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software application B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software application C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software application D field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software application E field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Software (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Tag field in host inventory.*
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).
`{PROFILE.TAG<1-9>}` is deprecated.|
|{INVENTORY.TYPE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Type field in host inventory.*
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).
`{PROFILE.DEVICETYPE<1-9>}` is deprecated.|
|{INVENTORY.TYPE.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Type (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*URL A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*URL B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*URL C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Vendor field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Description of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Description (with macros unresolved) of the Nth item in the trigger expression that caused a notification.*
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).
Supported since 5.2.0.|
|{ITEM.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Numeric ID of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Key of the Nth item in the trigger expression that caused a notification.*
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).
`{TRIGGER.KEY}` is deprecated.|
|{ITEM.KEY.ORIG}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Script type item, item prototype and discovery rule parameter names and values^[6](supported_by_location#footnotes)^
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ 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)^.*
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
→ Problem update notifications and commands
→ Trigger names, event names, operational data and descriptions
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Trigger URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*The latest value of the Nth item in the trigger expression that caused a notification.*
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).
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.
It is alias to `last(/{HOST.HOST}/{ITEM.KEY})`.
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro; starting with Zabbix 3.2.0.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Age of the log item event*, with precision down to a second.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Date of the log item event.*
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*ID of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Numeric severity of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Verbal severity of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Source of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Time of the log item event.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|*Name of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ 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.
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
→ 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**.
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.*
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
→ Problem update notifications and commands
→ Trigger names, event names, operational data and descriptions
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Trigger URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Description of item value widget|Resolved to either:
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.
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}
In the first case it will resolve to \*UNKNOWN\* if the history value has already been deleted or has never been stored.
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).
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 3.2.0.
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ 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.
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).
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.*
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.*
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
→ Text field in map shapes|*Network map name.*
Supported since 3.4.0.|
|{PROXY.DESCRIPTION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Description of the proxy*. Resolves to either:
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.
2) proxy, which executed discovery (in discovery notifications). Use {PROXY.DESCRIPTION} here, without indexing.
3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.DESCRIPTION} here, without indexing.
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
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the proxy*. Resolves to either:
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.
2) proxy, which executed discovery (in discovery notifications). Use {PROXY.NAME} here, without indexing.
3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.NAME} here, without indexing.
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
→ Service update notifications and commands|*Description of the service* (with macros resolved).|
|{SERVICE.NAME}|→ Service-based notifications and commands
→ Service update notifications and commands|*Name of the service* (with macros resolved).|
|{SERVICE.ROOTCAUSE}|→ Service-based notifications and commands
→ 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
→ 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
→ 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.}|→ Service-based notifications and commands
→ 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.
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
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger event names
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Current time in hh:mm:ss.*|
|{TRIGGER.DESCRIPTION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger description.*
All macros supported in a trigger description will be expanded if `{TRIGGER.DESCRIPTION}` is used in notification text.
`{TRIGGER.COMMENT}` is deprecated.|
|{TRIGGER.EXPRESSION.EXPLAIN}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)
→ Event names|*Partially evaluated trigger expression.*
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
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Partially evaluated trigger recovery expression.*
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
→ Problem update notifications and commands
→ Map element labels
→ 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
→ Problem update notifications and commands
→ Map element labels
→ 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
→ Problem update notifications and commands
→ Map element labels
→ 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
→ Problem update notifications and commands
→ Map element labels
→ 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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger expression.*|
|{TRIGGER.EXPRESSION.RECOVERY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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.
Supported since 3.2.0.|
|{TRIGGER.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Map element labels, map URL names and values
→ Trigger URLs
→ Trigger tag value
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Numeric trigger ID which triggered this action.*
Supported in trigger tag values since 4.4.1.|
|{TRIGGER.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Name of the trigger* (with macros resolved).
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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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.*
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
→ Problem update notifications and commands
→ 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.
`{STATUS}` is deprecated.|
|{TRIGGER.TEMPLATE.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ 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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts)|*Trigger URL.*|
|{TRIGGER.VALUE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger expressions
→ 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.*
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.*
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.*
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.*
A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.|
|{USER.FULLNAME}|→ Problem update notifications and commands
→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ 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.
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)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Name of the user* who started the script.
Supported since 5.0.2.|
|{USER.SURNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Surname of the user* who started the script.
Supported since 5.0.2.|
|{USER.USERNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/administration/scripts) (including confirmation text)|*Username of the user* who started the script.
Supported since 5.0.2.
{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.*
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 4.0.0.|
|{?EXPRESSION}|→ Trigger event names
→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels^[3](supported_by_location#footnotes)^
→ Map shape labels^[3](supported_by_location#footnotes)^
→ Link labels in maps^[3](supported_by_location#footnotes)^
→ Graph names^[5](supported_by_location#footnotes)^|*Expression macro* for formula calculations. Calculated by expanding all macros inside and evaluating the resulting expression.
See [example](/manual/config/triggers/expression#example_17) of using an expression macro in the event name.
Supported since 5.2.0.|
[comment]: # ({/d36c0744-d36c0744})
[comment]: # ({new-c2e14e96})
### Actions
|Macro|Supported in|Description|
|--|--------|--------|
|{ACTION.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications|*Numeric ID of the triggered action.*|
|{ACTION.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications|*Name of the triggered action.*|
|{ALERT.MESSAGE}|→ Alert script parameters|*'Default message' value from action configuration.*
Supported since 3.0.0.|
|{ALERT.SENDTO}|→ Alert script parameters|*'Send to' value from user media configuration.*
Supported since 3.0.0.|
|{ALERT.SUBJECT}|→ Alert script parameters|*'Default subject' value from action configuration.*
Supported since 3.0.0.|
|{ESC.HISTORY} |→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Internal notifications |*Escalation history. Log of previously sent messages.*
Shows previously sent notifications, on which escalation step they were sent and their status (*sent*, *in progress* or *failed*).|
[comment]: # ({/new-c2e14e96})
[comment]: # ({new-e2629abe})
### Date and time
|Macro|Supported in|Description|
|--|--------|--------|
|{DATE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Current date in yyyy.mm.dd. format.*|
|{TIME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger event names
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Current time in hh:mm:ss.*|
[comment]: # ({/new-e2629abe})
[comment]: # ({new-0862ff4d})
### Discovery
|Macro|Supported in|Description|
|--|--------|--------|
|{DISCOVERY.DEVICE.IPADDRESS}|→ Discovery notifications and commands|*IP address of the discovered device.*
Available always, does not depend on host being added.|
|{DISCOVERY.DEVICE.DNS}|→ Discovery notifications and commands|*DNS name of the discovered device.*
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.
For example: 1h 29m 01s.
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.*
For example: HTTP.|
|{DISCOVERY.SERVICE.PORT}|→ Discovery notifications and commands|*Port of the service that was discovered.*
For example: 80.|
|{DISCOVERY.SERVICE.STATUS}|→ Discovery notifications and commands|*Status of the discovered 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.
For example: 1h 29m 01s.
For services with status DOWN, this is the period of their downtime. |
[comment]: # ({/new-0862ff4d})
[comment]: # ({new-a970bbfc})
### Events
|Macro|Supported in|Description|
|--|--------|--------|
|{EVENT.ACK.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Acknowledgment status of the event (Yes/No)*.|
|{EVENT.AGE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Age of the event that triggered an action*, with precision down to a second.
Useful in escalated messages.|
|{EVENT.DATE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Date of the event that triggered an action.*|
|{EVENT.DURATION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Duration of the event (time difference between problem and recovery events)*, with precision down to a second.
Useful in problem recovery messages.
Supported since 5.0.0.|
|{EVENT.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric ID of the event that triggered an action.*|
|{EVENT.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the problem event that triggered an action.*
Supported since 4.0.0.|
|{EVENT.NSEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the event severity.* Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.
Supported since 4.0.0.|
|{EVENT.OBJECT}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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.
Supported since 4.4.0.|
|{EVENT.OPDATA}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Operational data of the underlying trigger of a problem.*
Supported since 4.4.0.|
|{EVENT.RECOVERY.DATE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (if recovery took place)|*Date of the recovery event.*|
|{EVENT.RECOVERY.ID}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (if recovery took place)|*Name of the recovery event.*
Supported since 4.4.1.|
|{EVENT.RECOVERY.STATUS}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (if recovery took place)|*A comma separated list of recovery event tags.* Expanded to an empty string if no tags exist.
Supported since 3.2.0.|
|{EVENT.RECOVERY.TAGSJSON}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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.
Supported since 5.0.0.|
|{EVENT.RECOVERY.TIME}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (if recovery took place)|*Time of the recovery event.*|
|{EVENT.RECOVERY.VALUE}|→ Problem [recovery notifications](/manual/config/notifications/action/recovery_operations) and commands
→ Problem update notifications and commands (if recovery took place)
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (if recovery took place)|*Numeric value of the recovery event.*|
|{EVENT.SEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the event severity.*
Supported since 4.0.0.|
|{EVENT.SOURCE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the event source.* Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal.
Supported since 4.4.0.|
|{EVENT.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Verbal value of the event that triggered an action.*|
|{EVENT.TAGS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*A comma separated list of event tags.* Expanded to an empty string if no tags exist.
Supported since 3.2.0.|
|{EVENT.TAGSJSON}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*A JSON array containing event tag [objects](/manual/api/reference/event/object#event_tag).* Expanded to an empty array if no tags exist.
Supported since 5.0.0.|
|{EVENT.TAGS.}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Webhook media type URL names and URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Event tag value referenced by the tag name.*
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.
Supported since 4.4.2.|
|{EVENT.TIME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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/acknowledgment#updating_problems).
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).
Supported since 4.0.0.|
|{EVENT.UPDATE.DATE}|→ Problem update notifications and commands
→ Service update notifications and commands|*Date of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*
Deprecated name: {ACK.DATE}|
|{EVENT.UPDATE.HISTORY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Log of problem updates (acknowledgments, etc).*
Deprecated name: {EVENT.ACK.HISTORY}|
|{EVENT.UPDATE.MESSAGE}|→ Problem update notifications and commands|*Problem update message.*
Deprecated name: {ACK.MESSAGE}|
|{EVENT.UPDATE.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the problem update status.* Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.
Supported since 4.4.0.|
|{EVENT.UPDATE.TIME}|→ Problem update notifications and commands
→ Service update notifications and commands|*Time of event [update](/manual/config/notifications/action/update_operations) (acknowledgment, etc).*
Deprecated name: {ACK.TIME}|
|{EVENT.VALUE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Service-based notifications and commands
→ Service update notifications and commands
→ Service recovery notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the event that triggered an action (1 for problem, 0 for recovering).*|
[comment]: # ({/new-a970bbfc})
[comment]: # ({new-c2d6fe18})
### Cause and symptom events
{EVENT.CAUSE.*} macros are used in the context of a symptom event, for example, in notifications; they return information about the cause event.
The {EVENT.SYMPTOMS} macro is used in the context of the cause event and returns information about symptom events.
|Macro|Supported in|Description|
|--|--------|--------|
|{EVENT.CAUSE.ACK.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Acknowledgment status of the cause event (Yes/No)*.|
|{EVENT.CAUSE.AGE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Age of the cause event*, with precision down to a second.
Useful in escalated messages.|
|{EVENT.CAUSE.DATE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Date of the cause event.*|
|{EVENT.CAUSE.DURATION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Duration of the cause event (time difference between problem and recovery events)*, with precision down to a second.
Useful in problem recovery messages.|
|{EVENT.CAUSE.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric ID of the cause event .*|
|{EVENT.CAUSE.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the cause problem event.*|
|{EVENT.CAUSE.NSEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the cause event severity.*
Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.|
|{EVENT.CAUSE.OBJECT}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the cause event object.*
Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.|
|{EVENT.CAUSE.OPDATA}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Operational data of the underlying trigger of the cause problem.*|
|{EVENT.CAUSE.SEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the cause event severity.*|
|{EVENT.CAUSE.SOURCE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the cause event source.*
Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal.|
|{EVENT.CAUSE.STATUS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Verbal value of the cause event.*|
|{EVENT.CAUSE.TAGS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*A comma separated list of cause event tags.*
Expanded to an empty string if no tags exist.|
|{EVENT.CAUSE.TAGSJSON}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*A JSON array containing cause event tag [objects](/manual/api/reference/event/object#event_tag).*
Expanded to an empty array if no tags exist.|
|{EVENT.CAUSE.TAGS.}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Cause event tag value referenced by the tag name.*
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.|
|{EVENT.CAUSE.TIME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Time of the cause event.*|
|{EVENT.CAUSE.UPDATE.HISTORY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Log of cause problem updates (acknowledgments, etc).*|
|{EVENT.CAUSE.VALUE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric value of the cause event (1 for problem, 0 for recovering).*|
|{EVENT.SYMPTOMS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*The list of symptom events.*
Includes the following details: host name, event name, severity, age, service tags and values.|
[comment]: # ({/new-c2d6fe18})
[comment]: # ({new-a4586852})
### Functions
|Macro|Supported in|Description|
|--|--------|--------|
|{FUNCTION.VALUE<1-9>}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Event names|*Results of the Nth item-based function in the trigger expression at the time of the event.*
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
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Results of the Nth item-based function in the recovery expression at the time of the event.*
Only functions with */host/key* as the first parameter are counted. See [indexed macros](supported_by_location#indexed_macros).|
[comment]: # ({/new-a4586852})
[comment]: # ({new-0559d116})
### Hosts
|Macro|Supported in|Description|
|--|--------|--------|
|{HOST.CONN}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Description of item value widget|*Host IP address or DNS name, depending on host settings*^[2](supported_by_location#footnotes)^.
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
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Host description.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Description of item value widget|*Host DNS name*^[2](supported_by_location#footnotes)^.
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Item key parameters
→ Map element labels, map URL names and values
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Description of item value widget|*Host name.*
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).
`{HOSTNAME<1-9>}` is deprecated.|
|{HOST.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ URL field of dynamic URL dashboard widget
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (only for type URL, including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (only for type URL, including confirmation text)
→ Description of item value widget|*Host ID.*
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters^[1](supported_by_location#footnotes)^
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Description of item value widget|*Host IP address*^[2](supported_by_location#footnotes)^.
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).
`{IPADDRESS<1-9>}` is deprecated.|
|{HOST.METADATA}|→ Autoregistration notifications and commands|*Host metadata.*
Used only for active agent autoregistration.|
|{HOST.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels, map URL names and values
→ Item key parameters
→ Host interface IP/DNS
→ Trapper item "Allowed hosts" field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ Web monitoring^[4](supported_by_location#footnotes)^
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Description of item value widget|*Visible host name.*
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
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger names, event names, operational data and descriptions
→ Trigger URLs
→ JMX item endpoint field
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Host (agent) port*^[2](supported_by_location#footnotes)^.
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
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|IP address or DNS name of the target host, depending on host settings.
Supported since 5.4.0.|
|{HOST.TARGET.DNS}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|DNS name of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.HOST}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|Technical name of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.IP}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|IP address of the target host.
Supported since 5.4.0.|
|{HOST.TARGET.NAME}|→ Trigger-based commands
→ Problem update commands
→ Discovery commands
→ Autoregistration commands|Visible name of the target host.
Supported since 5.4.0.|
See also: [Host inventory](#host-inventory)
[comment]: # ({/new-0559d116})
[comment]: # ({new-5140de49})
### Host groups
|Macro|Supported in|Description|
|--|--------|--------|
|{HOSTGROUP.ID}|→ Map element labels, map URL names and values|*Host group ID.*|
[comment]: # ({/new-5140de49})
[comment]: # ({new-15530041})
### Host inventory
|Macro|Supported in|Description|
|--|--------|--------|
|{INVENTORY.ALIAS}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Alias field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Asset tag field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Chassis field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Contact field in host inventory.*
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).
`{PROFILE.CONTACT<1-9>}` is deprecated.|
|{INVENTORY.CONTRACT.NUMBER}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Contract number field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Deployment status field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Hardware field in host inventory.*
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).
`{PROFILE.HARDWARE<1-9>}` is deprecated.|
|{INVENTORY.HARDWARE.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Hardware (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Host subnet mask field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Host networks field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Host router field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Hardware architecture field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Date hardware decommissioned field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Date hardware maintenance expires field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Date hardware installed field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Date hardware purchased field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Installer name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Sc→ ript-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Location field in host inventory.*
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).
`{PROFILE.LOCATION<1-9>}` is deprecated.|
|{INVENTORY.LOCATION.LAT}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Location latitude field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Location longitude field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*MAC address A field in host inventory.*
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).
`{PROFILE.MACADDRESS<1-9>}` is deprecated.|
|{INVENTORY.MACADDRESS.B}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*MAC address B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Model field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Name field in host inventory.*
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).
`{PROFILE.NAME<1-9>}` is deprecated.|
|{INVENTORY.NOTES}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Notes field in host inventory.*
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).
`{PROFILE.NOTES<1-9>}` is deprecated.|
|{INVENTORY.OOB.IP}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OOB IP address field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OOB subnet mask field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OOB router field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OS field in host inventory.*
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).
`{PROFILE.OS<1-9>}` is deprecated.|
|{INVENTORY.OS.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OS (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*OS (Short) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC cell field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC email field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC phone A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC phone B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Primary POC screen name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC cell field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC email field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC phone A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC phone B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Secondary POC screen name field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Serial number A field in host inventory.*
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).
`{PROFILE.SERIALNO<1-9>}` is deprecated.|
|{INVENTORY.SERIALNO.B}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Serial number B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site address A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site address B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site address C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site city field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site country field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site notes field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site rack location field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site state/province field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Site ZIP/postal field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software field in host inventory.*
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).
`{PROFILE.SOFTWARE<1-9>}` is deprecated.|
|{INVENTORY.SOFTWARE.APP.A}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software application A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software application B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software application C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software application D field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software application E field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Software (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Tag field in host inventory.*
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).
`{PROFILE.TAG<1-9>}` is deprecated.|
|{INVENTORY.TYPE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Type field in host inventory.*
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).
`{PROFILE.DEVICETYPE<1-9>}` is deprecated.|
|{INVENTORY.TYPE.FULL}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Type (Full details) field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*URL A field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*URL B field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*URL C field in host inventory.*
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
→ Problem update notifications and commands
→ Internal notifications
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Map element labels, map URL names and values
→ Script-type items^[6](supported_by_location#footnotes)^
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)^[6](supported_by_location#footnotes)^
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Vendor field in host inventory.*
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).|
[comment]: # ({/new-15530041})
[comment]: # ({new-d0b03c62})
### Items
|Macro|Supported in|Description|
|--|--------|--------|
|{ITEM.DESCRIPTION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Description of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Description (with macros unresolved) of the Nth item in the trigger expression that caused a notification.*
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).
Supported since 5.2.0.|
|{ITEM.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Numeric ID of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Key of the Nth item in the trigger expression that caused a notification.*
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).
`{TRIGGER.KEY}` is deprecated.|
|{ITEM.KEY.ORIG}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Script-type item, item prototype and discovery rule parameter names and values
→ HTTP agent type item, item prototype and discovery rule fields:
URL, Query fields, Request body, Headers, Proxy, SSL certificate file, SSL key file, Allowed hosts.
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ 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)^.*
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
→ Problem update notifications and commands
→ Trigger names, event names, operational data and descriptions
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Trigger URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*The latest value of the Nth item in the trigger expression that caused a notification.*
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).
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.
It is alias to `last(/{HOST.HOST}/{ITEM.KEY})`.
The resolved value is truncated to 20 characters to be usable, for example, in trigger URLs. To resolve to a full value, you may use [macro functions](/manual/config/macros/macro_functions#seeing-full-item-values).
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro; starting with Zabbix 3.2.0.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Age of the log item event*, with precision down to a second.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Date of the log item event.*
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*ID of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Numeric severity of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Verbal severity of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Source of the event in the event log.*
For Windows event log monitoring only.
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
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Event tags and values
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Time of the log item event.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|*Name of the Nth item in the trigger expression that caused a notification.*
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ 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.
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
→ 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**.
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.*
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
→ Problem update notifications and commands
→ Trigger names, event names, operational data and descriptions
→ [Tag names and values](/manual/config/tagging#macro_support)
→ Trigger URLs
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Description of item value widget|Resolved to either:
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.
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}
In the first case it will resolve to \*UNKNOWN\* if the history value has already been deleted or has never been stored.
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).
The resolved value is truncated to 20 characters to be usable, for example, in trigger URLs. To resolve to a full value, you may use [macro functions](/manual/config/macros/macro_functions#seeing-full-item-values).
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 3.2.0.
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
→ Problem update notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ 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.
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).
Supported since 5.4.0.|
[comment]: # ({/new-d0b03c62})
[comment]: # ({new-d60e314e})
### Low-level discovery rules
|Macro|Supported in|Description|
|--|--------|--------|
|{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.*
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.*
If an LLD rule goes into the unsupported state and then immediately gets supported again the error field can be empty.|
[comment]: # ({/new-d60e314e})
[comment]: # ({new-fff4e71a})
### Maps
|Macro|Supported in|Description|
|--|--------|--------|
|{MAP.ID}|→ Map element labels, map URL names and values|*Network map ID.*|
|{MAP.NAME}|→ Map element labels, map URL names and values
→ Text field in map shapes|*Network map name.*
Supported since 3.4.0.|
[comment]: # ({/new-fff4e71a})
[comment]: # ({new-c0547f53})
### Proxies
|Macro|Supported in|Description|
|--|--------|--------|
|{PROXY.DESCRIPTION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Description of the proxy*. Resolves to either:
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.
2) proxy, which executed discovery (in discovery notifications). Use {PROXY.DESCRIPTION} here, without indexing.
3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.DESCRIPTION} here, without indexing.
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
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the proxy*. Resolves to either:
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.
2) proxy, which executed discovery (in discovery notifications). Use {PROXY.NAME} here, without indexing.
3) proxy to which an active agent registered (in autoregistration notifications). Use {PROXY.NAME} here, without indexing.
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).|
[comment]: # ({/new-c0547f53})
[comment]: # ({new-35c7fe9d})
### Services
|Macro|Supported in|Description|
|--|--------|--------|
|{SERVICE.DESCRIPTION}|→ Service-based notifications and commands
→ Service update notifications and commands|*Description of the service* (with macros resolved).|
|{SERVICE.NAME}|→ Service-based notifications and commands
→ Service update notifications and commands|*Name of the service* (with macros resolved).|
|{SERVICE.ROOTCAUSE}|→ Service-based notifications and commands
→ 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
→ 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
→ 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.}|→ Service-based notifications and commands
→ 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.
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.|
[comment]: # ({/new-35c7fe9d})
[comment]: # ({new-f378e3e7})
### Triggers
|Macro|Supported in|Description|
|--|--------|--------|
|{TRIGGER.DESCRIPTION}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Trigger description.*
All macros supported in a trigger description will be expanded if `{TRIGGER.DESCRIPTION}` is used in notification text.
`{TRIGGER.COMMENT}` is deprecated.|
|{TRIGGER.EXPRESSION.EXPLAIN}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)
→ Event names|*Partially evaluated trigger expression.*
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
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Partially evaluated trigger recovery expression.*
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
→ Problem update notifications and commands
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Number of acknowledged PROBLEM events for all triggers disregarding their state.*|
|{TRIGGER.EVENTS.PROBLEM.UNACK}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Number of unacknowledged PROBLEM events for all triggers disregarding their state.*|
|{TRIGGER.EVENTS.UNACK}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Trigger expression.*|
|{TRIGGER.EXPRESSION.RECOVERY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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.
Supported since 3.2.0.|
|{TRIGGER.ID}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Map element labels, map URL names and values
→ Trigger URLs
→ Trigger tag value
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Numeric trigger ID which triggered this action.*
Supported in trigger tag values since 4.4.1.|
|{TRIGGER.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Name of the trigger* (with macros resolved).
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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Original name of the trigger* (i.e. without macros resolved).|
|{TRIGGER.NSEVERITY}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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.*
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
→ Problem update notifications and commands
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Trigger value at the time of operation step execution.* Can be either PROBLEM or OK.
`{STATUS}` is deprecated.|
|{TRIGGER.TEMPLATE.NAME}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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
→ Problem update notifications and commands
→ Trigger-based internal notifications
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts)|*Trigger URL.*|
|{TRIGGER.VALUE}|→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger expressions
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/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.*
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.*
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.*
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.*
A trigger is considered to be acknowledged if all of it's PROBLEM events are acknowledged.|
[comment]: # ({/new-f378e3e7})
[comment]: # ({new-3b1a947a})
### Users
|Macro|Supported in|Description|
|--|--------|--------|
|{USER.FULLNAME}|→ Problem update notifications and commands
→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)|*Name, surname and username of the user* who added event acknowledgment or started the script.
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/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)|*Name of the user* who started the script.
Supported since 5.0.2.|
|{USER.SURNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)|*Surname of the user* who started the script.
Supported since 5.0.2.|
|{USER.USERNAME}|→ Manual host action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)
→ Manual event action [scripts](/manual/web_interface/frontend_sections/alerts/scripts) (including confirmation text)|*Username of the user* who started the script.
Supported since 5.0.2.
{USER.ALIAS}, supported before Zabbix 5.4.0, is now deprecated.|
[comment]: # ({/new-3b1a947a})
[comment]: # ({new-08004baa})
### Other macro types
|Macro|Supported in|Description|
|--|--------|--------|
|{$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.*
[Customizing](/manual/config/macros/macro_functions) the macro value is supported for this macro, starting with Zabbix 4.0.0.|
|{?EXPRESSION}|→ Trigger event names
→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels^[3](supported_by_location#footnotes)^
→ Map shape labels^[3](supported_by_location#footnotes)^
→ Link labels in maps^[3](supported_by_location#footnotes)^
→ Graph names^[5](supported_by_location#footnotes)^|See [expression macros](/manual/config/macros/expression_macros).
Supported since 5.2.0.|
[comment]: # ({/new-08004baa})
[comment]: # ({new-f4bb15e3})
##### Footnotes
^**1**^ The `{HOST.*}` macros supported in item key parameters will
resolve to the interface that is selected for the item. When used in
items without interfaces they will resolve to either the Zabbix agent,
SNMP, JMX or IPMI interface of the host in this order of priority or to
'UNKNOWN' if the host does not have any interface.
^**2**^ In global scripts, interface IP/DNS fields and web scenarios the
macro will resolve to the main agent interface, however, if it is not
present, the main SNMP interface will be used. If SNMP is also not
present, the main JMX interface will be used. If JMX is not present
either, the main IPMI interface will be used. If the host does not have
any interface, the macro resolves to 'UNKNOWN'.
^**3**^ Only the **avg**, **last**, **max** and **min** functions, with
seconds as parameter are supported in this macro in map labels.
^**4**^ `{HOST.*}` macros are supported in web scenario *Variables*,
*Headers*, *SSL certificate file* and *SSL key file* fields and in
scenario step *URL*, *Post*, *Headers* and *Required string* fields.
Since Zabbix 5.4.0, `{HOST.*}` macros are no longer supported in web
scenario *Name* and web scenario step *Name* fields.
^**5**^ Only the **avg**, **last**, **max** and **min** functions, with
seconds as parameter are supported within this macro in graph names. The
{HOST.HOST<1-9>} macro can be used as host within the macro. For
example:
* last(/Cisco switch/ifAlias[{#SNMPINDEX}])
* last(/{HOST.HOST}/ifAlias[{#SNMPINDEX}])
^**6**^ Supported since 5.2.5.
[comment]: # ({/new-f4bb15e3})
[comment]: # ({new-3a90dc8f})
#### Indexed macros
The indexed macro syntax of {MACRO**<1-9>**} works only in the
context of **trigger expressions**. It can be used to reference hosts or
functions in the order in which they appear in the expression. Macros
like {HOST.IP1}, {HOST.IP2}, {HOST.IP3} will resolve to the IP of the
first, second, and third host in the trigger expression (providing the
trigger expression contains those hosts). Macros like {FUNCTION.VALUE1},
{FUNCTION.VALUE2}, {FUNCTION.VALUE3} will resolve to the value of the
first, second, and third item-based function in the trigger expression
at the time of the event (providing the trigger expression contains
those functions).
Additionally the {HOST.HOST<1-9>} macro is also supported within
the `{?func(/host/key,param)}` expression macro in **graph names**. For
example, `{?func(/{HOST.HOST2}/key,param)}` in the graph name will refer
to the host of the second item in the graph.
::: notewarning
Indexed macros will not resolve in any other
context, except the two cases mentioned here. For other contexts, use
macros **without** index (i. e.{HOST.HOST}, {HOST.IP}, etc)
instead.
:::
[comment]: # ({/new-3a90dc8f})