1 Supported macros

Overview

The table contains a complete list of macros supported by Zabbix out-of-the-box.

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.

MacroSupported inDescription
{ACTION.ID}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Numeric ID of the triggered action.
Supported since 2.2.0.
{ACTION.NAME}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Name of the triggered action.
Supported since 2.2.0.
{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
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Current date in yyyy.mm.dd. format.
{DISCOVERY.DEVICE.IPADDRESS}→ Discovery notifications and commandsIP address of the discovered device.
Available always, does not depend on host being added.
{DISCOVERY.DEVICE.DNS}→ Discovery notifications and commandsDNS name of the discovered device.
Available always, does not depend on host being added.
{DISCOVERY.DEVICE.STATUS}→ Discovery notifications and commandsStatus of the discovered device: can be either UP or DOWN.
{DISCOVERY.DEVICE.UPTIME}→ Discovery notifications and commandsTime since the last change of discovery status for a particular device, with precision down to a second since Zabbix 5.0.4 (down to a minute before that).
For example: 1h 29m 01s.
For devices with status DOWN, this is the period of their downtime.
{DISCOVERY.RULE.NAME}→ Discovery notifications and commandsName of the discovery rule that discovered the presence or absence of the device or service.
{DISCOVERY.SERVICE.NAME}→ Discovery notifications and commandsName of the service that was discovered.
For example: HTTP.
{DISCOVERY.SERVICE.PORT}→ Discovery notifications and commandsPort of the service that was discovered.
For example: 80.
{DISCOVERY.SERVICE.STATUS}→ Discovery notifications and commandsStatus of the discovered service: can be either UP or DOWN.
{DISCOVERY.SERVICE.UPTIME}→ Discovery notifications and commandsTime since the last change of discovery status for a particular service, with precision down to a second since Zabbix 5.0.4 (down to a minute before that).
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
→ 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		Acknowledgment status of the event (Yes/No).
{EVENT.AGE}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Age of the event that triggered an action, with precision down to a second since Zabbix 5.0.4 (down to a minute before that).
Useful in escalated messages.
{EVENT.DATE}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Date of the event that triggered an action.
{EVENT.DURATION}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications		Duration of the event (time difference between problem and recovery events), with precision down to a second since Zabbix 5.0.4 (down to a minute before that).
Useful in problem recovery messages.

Supported since 5.0.0.
{EVENT.ID}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger URLs		Numeric ID of the event that triggered an action.
{EVENT.NAME} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications and commands ​		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 ​		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 ​		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		Operational data of the underlying trigger of a problem.
Supported since 4.4.0.
{EVENT.RECOVERY.DATE}→ Problem recovery notifications and commandsDate of the recovery event.
Supported since 2.2.0.
{EVENT.RECOVERY.ID}→ Problem recovery notifications and commandsNumeric ID of the recovery event.
Supported since 2.2.0.
{EVENT.RECOVERY.NAME} ​ ​→​ Problem recovery notifications and commands ​Name of the recovery event.
Supported since 4.4.1. ​
{EVENT.RECOVERY.STATUS}→ Problem recovery notifications and commandsVerbal value of the recovery event.
Supported since 2.2.0.
{EVENT.RECOVERY.TAGS}→ Problem recovery notifications and commandsA 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 and commandsA JSON array containing event tag objects. Expanded to an empty array if no tags exist.
Supported since 5.0.0.
{EVENT.RECOVERY.TIME}→ Problem recovery notifications and commandsTime of the recovery event.
Supported since 2.2.0.
{EVENT.RECOVERY.VALUE}→ Problem recovery notifications and commandsNumeric value of the recovery event.
Supported since 2.2.0.
{EVENT.SEVERITY} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications and commands ​		Name of the event severity.
Supported since 4.0.0. ​
{EVENT.SOURCE} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications and commands ​		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
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Verbal value of the event that triggered an action.
Supported since 2.2.0.
{EVENT.TAGS}→ Trigger-based notifications and commands
→ Problem update notifications and commands		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		A JSON array containing event tag objects. Expanded to an empty array if no tags exist.
Supported since 5.0.0.
{EVENT.TAGS.<tag name>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Problem and event URLs		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
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Time of the event that triggered an action.
{EVENT.UPDATE.ACTION}→ Problem update notifications and commandsHuman-readable name of the action(s) performed during problem update.
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 commandsDate of problem update (acknowledgment, etc).
Deprecated name: {ACK.DATE}
{EVENT.UPDATE.HISTORY}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Log of problem updates (acknowledgments, etc).
Deprecated name: {EVENT.ACK.HISTORY}
{EVENT.UPDATE.MESSAGE}→ Problem update notifications and commandsProblem update message.
Deprecated name: {ACK.MESSAGE}
{EVENT.UPDATE.STATUS} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications and commands ​		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 commandsTime of problem update (acknowledgment, etc).
Deprecated name: {ACK.TIME}
{EVENT.VALUE}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Numeric value of the event that triggered an action (1 for problem, 0 for recovering).
Supported since 2.2.0.
{HOST.CONN<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Global scripts (including confirmation text)
→ Map element labels, map URL names and values
→ Item key parameters1
→ Host interface IP/DNS
→ Trapper item “Allowed hosts” field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring4
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget/screen element
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Tag 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.		Host IP address or DNS name, depending on host settings2.
Supported in trigger names since 2.0.0.
{HOST.DESCRIPTION<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Map element labels		Host description.
Supported since 2.4.0.
{HOST.DNS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Global scripts (including confirmation text)
→ Map element labels, map URL names and values
→ Item key parameters1
→ Host interface IP/DNS
→ Trapper item “Allowed hosts” field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring4
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget/screen element
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Tag 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.		Host DNS name2.
Supported in trigger names since 2.0.0.
{HOST.HOST<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Global scripts (including confirmation text)
→ 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 monitoring4
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget/screen element
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Tag 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.		Host name.
{HOSTNAME<1-9>} is deprecated.
{HOST.ID<1-9>}→ 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/screen element
→ Trigger URLs
→ Tag names and values		Host ID.
{HOST.IP<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Global scripts (including confirmation text)
→ Map element labels, map URL names and values
→ Item key parameters1
→ Host interface IP/DNS
→ Trapper item “Allowed hosts” field
→ Database monitoring additional parameters
→ SSH and Telnet scripts
→ JMX item endpoint field
→ Web monitoring4
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget/screen element
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Tag 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.		Host IP address2.
Supported since 2.0.0. {IPADDRESS<1-9>} is deprecated.
{HOST.METADATA}→ Autoregistration notifications and commandsHost metadata.
Used only for active agent autoregistration. Supported since 2.2.0.
{HOST.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Global scripts (including confirmation text)
→ 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 monitoring4
→ Low-level discovery rule filter regular expressions
→ URL field of dynamic URL dashboard widget/screen element
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ Tag 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.		Visible host name.
Supported since 2.0.0.
{HOST.PORT<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications
→ Trigger names, operational data and descriptions
→ Trigger URLs
→ JMX item endpoint field
→ Tag names and values		Host (agent) port2.
Supported in autoregistration since 2.0.0.
Supported in trigger names, trigger descriptions, internal and trigger-based notifications since 2.2.2.
{HOSTGROUP.ID}→ Map element labels, map URL names and valuesHost group ID.
{INVENTORY.ALIAS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Alias field in host inventory.
{INVENTORY.ASSET.TAG<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Asset tag field in host inventory.
{INVENTORY.CHASSIS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Chassis field in host inventory.
{INVENTORY.CONTACT<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Contact field in host inventory.
{PROFILE.CONTACT<1-9>} is deprecated.
{INVENTORY.CONTRACT.NUMBER<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Contract number field in host inventory.
{INVENTORY.DEPLOYMENT.STATUS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Deployment status field in host inventory.
{INVENTORY.HARDWARE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Hardware field in host inventory.
{PROFILE.HARDWARE<1-9>} is deprecated.
{INVENTORY.HARDWARE.FULL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Hardware (Full details) field in host inventory.
{INVENTORY.HOST.NETMASK<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Host subnet mask field in host inventory.
{INVENTORY.HOST.NETWORKS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Host networks field in host inventory.
{INVENTORY.HOST.ROUTER<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Host router field in host inventory.
{INVENTORY.HW.ARCH<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Hardware architecture field in host inventory.
{INVENTORY.HW.DATE.DECOMM<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Date hardware decommissioned field in host inventory.
{INVENTORY.HW.DATE.EXPIRY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Date hardware maintenance expires field in host inventory.
{INVENTORY.HW.DATE.INSTALL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Date hardware installed field in host inventory.
{INVENTORY.HW.DATE.PURCHASE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Date hardware purchased field in host inventory.
{INVENTORY.INSTALLER.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Installer name field in host inventory.
{INVENTORY.LOCATION<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Location field in host inventory.
{PROFILE.LOCATION<1-9>} is deprecated.
{INVENTORY.LOCATION.LAT<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Location latitude field in host inventory.
{INVENTORY.LOCATION.LON<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Location longitude field in host inventory.
{INVENTORY.MACADDRESS.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		MAC address A field in host inventory.
{PROFILE.MACADDRESS<1-9>} is deprecated.
{INVENTORY.MACADDRESS.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		MAC address B field in host inventory.
{INVENTORY.MODEL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Model field in host inventory.
{INVENTORY.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Name field in host inventory. {PROFILE.NAME<1-9>} is deprecated.
{INVENTORY.NOTES<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Notes field in host inventory. {PROFILE.NOTES<1-9>} is deprecated.
{INVENTORY.OOB.IP<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OOB IP address field in host inventory.
{INVENTORY.OOB.NETMASK<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OOB subnet mask field in host inventory.
{INVENTORY.OOB.ROUTER<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OOB router field in host inventory.
{INVENTORY.OS<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OS field in host inventory.
{PROFILE.OS<1-9>} is deprecated.
{INVENTORY.OS.FULL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OS (Full details) field in host inventory.
{INVENTORY.OS.SHORT<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		OS (Short) field in host inventory.
{INVENTORY.POC.PRIMARY.CELL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC cell field in host inventory.
{INVENTORY.POC.PRIMARY.EMAIL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC email field in host inventory.
{INVENTORY.POC.PRIMARY.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC name field in host inventory.
{INVENTORY.POC.PRIMARY.NOTES<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC notes field in host inventory.
{INVENTORY.POC.PRIMARY.PHONE.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC phone A field in host inventory.
{INVENTORY.POC.PRIMARY.PHONE.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC phone B field in host inventory.
{INVENTORY.POC.PRIMARY.SCREEN<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Primary POC screen name field in host inventory.
{INVENTORY.POC.SECONDARY.CELL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC cell field in host inventory.
{INVENTORY.POC.SECONDARY.EMAIL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC email field in host inventory.
{INVENTORY.POC.SECONDARY.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC name field in host inventory.
{INVENTORY.POC.SECONDARY.NOTES<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC notes field in host inventory.
{INVENTORY.POC.SECONDARY.PHONE.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC phone A field in host inventory.
{INVENTORY.POC.SECONDARY.PHONE.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC phone B field in host inventory.
{INVENTORY.POC.SECONDARY.SCREEN<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Secondary POC screen name field in host inventory.
{INVENTORY.SERIALNO.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Serial number A field in host inventory.
{PROFILE.SERIALNO<1-9>} is deprecated.
{INVENTORY.SERIALNO.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Serial number B field in host inventory.
{INVENTORY.SITE.ADDRESS.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site address A field in host inventory.
{INVENTORY.SITE.ADDRESS.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site address B field in host inventory.
{INVENTORY.SITE.ADDRESS.C<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site address C field in host inventory.
{INVENTORY.SITE.CITY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site city field in host inventory.
{INVENTORY.SITE.COUNTRY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site country field in host inventory.
{INVENTORY.SITE.NOTES<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site notes field in host inventory.
{INVENTORY.SITE.RACK<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site rack location field in host inventory.
{INVENTORY.SITE.STATE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site state/province field in host inventory.
{INVENTORY.SITE.ZIP<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Site ZIP/postal field in host inventory.
{INVENTORY.SOFTWARE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software field in host inventory. {PROFILE.SOFTWARE<1-9>} is deprecated.
{INVENTORY.SOFTWARE.APP.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software application A field in host inventory.
{INVENTORY.SOFTWARE.APP.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software application B field in host inventory.
{INVENTORY.SOFTWARE.APP.C<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software application C field in host inventory.
{INVENTORY.SOFTWARE.APP.D<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software application D field in host inventory.
{INVENTORY.SOFTWARE.APP.E<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software application E field in host inventory.
{INVENTORY.SOFTWARE.FULL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Software (Full details) field in host inventory.
{INVENTORY.TAG<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Tag field in host inventory. {PROFILE.TAG<1-9>} is deprecated.
{INVENTORY.TYPE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Type field in host inventory. {PROFILE.DEVICETYPE<1-9>} is deprecated.
{INVENTORY.TYPE.FULL<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Type (Full details) field in host inventory.
{INVENTORY.URL.A<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		URL A field in host inventory.
{INVENTORY.URL.B<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		URL B field in host inventory.
{INVENTORY.URL.C<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		URL C field in host inventory.
{INVENTORY.VENDOR<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ Tag names and values
→ Map element labels, map URL names and values		Vendor field in host inventory.
{ITEM.DESCRIPTION<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications		Description of the Nth item in the trigger expression that caused a notification. Supported since 2.0.0.
{ITEM.ID<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file.		Numeric ID of the Nth item in the trigger expression that caused a notification. Supported since 1.8.12.
{ITEM.KEY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications
→ HTTP agent type item, item prototype and discovery rule fields:
URL, query fields, request body, headers, proxy, SSL certificate file, SSL key file.		Key of the Nth item in the trigger expression that caused a notification. Supported since 2.0.0.
{TRIGGER.KEY} is deprecated.
{ITEM.KEY.ORIG<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications		Original key (with macros not expanded) of the Nth item in the trigger expression that caused a notification. Supported since 2.0.6.
{ITEM.LASTVALUE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Tag names and values
→ Trigger URLs7		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 ZBX_HISTORY_PERIOD time ago (defined in defines.inc.php).
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.
Supported since 1.4.3. It is alias to {{HOST.HOST}:{ITEM.KEY}.last()}.
Customizing the macro value is supported for this macro; starting with Zabbix 3.2.0.
{ITEM.LOG.AGE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Age of the log item event, with precision down to a second since Zabbix 5.0.4 (down to a minute before that).
{ITEM.LOG.DATE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Date of the log item event.
{ITEM.LOG.EVENTID<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		ID of the event in the event log.
For Windows event log monitoring only.
{ITEM.LOG.NSEVERITY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Numeric severity of the event in the event log.
For Windows event log monitoring only.
{ITEM.LOG.SEVERITY<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Verbal severity of the event in the event log.
For Windows event log monitoring only.
{ITEM.LOG.SOURCE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Source of the event in the event log.
For Windows event log monitoring only.
{ITEM.LOG.TIME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Time of the log item event.
{ITEM.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications		Name of the Nth item (with macros resolved) in the trigger expression that caused a notification.
{ITEM.NAME.ORIG<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Internal notifications		Original name (i.e. without macros resolved) of the Nth item in the trigger expression that caused a notification.
Supported since 2.0.6.
{ITEM.STATE<1-9>}→ Item-based internal notificationsThe latest state of the Nth item in the trigger expression that caused a notification. Possible values: Not supported and Normal.
Supported since 2.2.0.
{ITEM.VALUE<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger names, operational data and descriptions
→ Tag names and values
→ Trigger URLs7		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 ZBX_HISTORY_PERIOD time ago (defined in defines.inc.php).
Supported since 1.4.3.

Customizing the macro value is supported for this macro, starting with Zabbix 3.2.0.
{LLDRULE.DESCRIPTION}→ LLD-rule based internal notificationsDescription of the low-level discovery rule which caused a notification.
Supported since 2.2.0.
{LLDRULE.ID}→ LLD-rule based internal notificationsNumeric ID of the low-level discovery rule which caused a notification.
Supported since 2.2.0.
{LLDRULE.KEY}→ LLD-rule based internal notificationsKey of the low-level discovery rule which caused a notification.
Supported since 2.2.0.
{LLDRULE.KEY.ORIG}→ LLD-rule based internal notificationsOriginal key (with macros not expanded) of the low-level discovery rule which caused a notification.
Supported since 2.2.0.
{LLDRULE.NAME}→ LLD-rule based internal notificationsName of the low-level discovery rule (with macros resolved) that caused a notification.
Supported since 2.2.0.
{LLDRULE.NAME.ORIG}→ LLD-rule based internal notificationsOriginal name (i.e. without macros resolved) of the low-level discovery rule that caused a notification.
Supported since 2.2.0.
{LLDRULE.STATE}→ LLD-rule based internal notificationsThe latest state of the low-level discovery rule. Possible values: Not supported and Normal.
Supported since 2.2.0.
{MAP.ID}→ Map element labels, map URL names and valuesNetwork 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<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		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 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.
Supported since 2.4.0.
{PROXY.NAME<1-9>}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		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 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.
Supported since 1.8.4.
{TIME}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Discovery notifications and commands
→ Autoregistration notifications and commands
→ Internal notifications		Current time in hh:mm:ss.
{TRIGGER.DESCRIPTION}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Trigger description. Supported since 2.0.4.
Starting with 2.2.0, all macros supported in a trigger description will be expanded if {TRIGGER.DESCRIPTION} is used in notification text.
{TRIGGER.COMMENT} is deprecated.
{TRIGGER.EVENTS.ACK}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels		Number of acknowledged events for a map element in maps, or for the trigger which generated current event in notifications. Supported since 1.8.3.
{TRIGGER.EVENTS.PROBLEM.ACK}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels		Number of acknowledged PROBLEM events for all triggers disregarding their state. Supported since 1.8.3.
{TRIGGER.EVENTS.PROBLEM.UNACK}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels		Number of unacknowledged PROBLEM events for all triggers disregarding their state. Supported since 1.8.3.
{TRIGGER.EVENTS.UNACK}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element labels		Number of unacknowledged events for a map element in maps, or for the trigger which generated current event in notifications. Supported in map element labels since 1.8.3.
{TRIGGER.HOSTGROUP.NAME}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		A sorted (by SQL query), comma-space separated list of host groups in which the trigger is defined. Supported since 2.0.6.
{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}→ Map element labelsNumber of acknowledged PROBLEM events for triggers in PROBLEM state. Supported since 1.8.3.
{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}→ Map element labelsNumber of unacknowledged PROBLEM events for triggers in PROBLEM state. Supported since 1.8.3.
{TRIGGER.EXPRESSION}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Trigger expression. Supported since 1.8.12.
{TRIGGER.EXPRESSION.RECOVERY}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Trigger recovery expression if OK event generation in trigger configuration 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 values		Numeric trigger ID which triggered this action.
Supported in trigger URLs since Zabbix 1.8.8, in trigger tag values since 4.4.1.
{TRIGGER.NAME}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		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		Original name of the trigger (i.e. without macros resolved).
Supported since 2.0.6.
{TRIGGER.NSEVERITY}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Numerical trigger severity. Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.
Supported starting from Zabbix 1.6.2.
{TRIGGER.SEVERITY}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Trigger severity name. Can be defined in Administration → General → Trigger severities.
{TRIGGER.STATE}→ Trigger-based internal notificationsThe latest state of the trigger. Possible values: Unknown and Normal.
Supported since 2.2.0.
{TRIGGER.STATUS}→ Trigger-based notifications and commands
→ Problem update notifications and commands		Current trigger value. 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		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. Supported since 2.0.6.
{TRIGGER.URL}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger-based internal notifications		Trigger URL.
{TRIGGER.VALUE}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Trigger expressions		Current trigger numeric value: 0 - trigger is in OK state, 1 - trigger is in PROBLEM state.
{TRIGGERS.UNACK}→ Map element labelsNumber 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 labelsNumber 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.
Supported since 1.8.3.
{TRIGGERS.ACK}→ Map element labelsNumber 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.
Supported since 1.8.3.
{TRIGGERS.PROBLEM.ACK}→ Map element labelsNumber of acknowledged PROBLEM triggers for a map element.
A trigger is considered to be acknowledged if all of it’s PROBLEM events are acknowledged.
Supported since 1.8.3.
{USER.ALIAS}→ Global scripts (including confirmation text)Alias (username) of the user who started the script.
Supported since 5.0.2.
{USER.FULLNAME}→ Problem update notifications and commands
→ Global scripts (including confirmation text)		Name, surname and alias 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}→ Global scripts (including confirmation text)Name of the user who started the script.
Supported since 5.0.2.
{USER.SURNAME}→ Global scripts (including confirmation text)Surname name of the user who started the script.
Supported since 5.0.2.
{host:key.func(param)}→ Trigger-based notifications and commands
→ Problem update notifications and commands
→ Map element/shape labels 3
→ Link labels in maps3​
→ Graph names5
→ Trigger expressions6		Simple macros, as used in building trigger expressions.

Supported for shape labels in maps since 3.4.2.
{$MACRO}→ See: User macros supported by locationUser-definable macros.
{#MACRO}→ See: Low-level discovery macrosLow-level discovery macros.
Supported since 2.0.0.

Customizing the macro value is supported for this macro, starting with Zabbix 4.0.0.
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.

2 In remote commands, 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.

3 Only the avg, last, max and min functions, with seconds as parameter are supported in this macro in map labels.

4 Supported since Zabbix 2.2.0, {HOST.*} macros are supported in web scenario Name, Variables, Headers, SSL certificate file and SSL key file fields and in scenario step Name, URL, Post, Headers and Required string fields.

5 Supported since Zabbix 2.2.0. 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:

  • {Cisco switch:ifAlias[{#SNMPINDEX}].last()}

  • {{HOST.HOST}:ifAlias[{#SNMPINDEX}].last()}

6 While supported to build trigger expressions, simple macros may not be used inside each other.

7 Supported since 4.0.0.

Indexed macros

The indexed macro syntax of {MACRO<1-9>} is limited to the context of trigger expressions. It can be used to reference hosts 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).

Additionally the {HOST.HOST<1-9>} macro is also supported within the {host:key.func(param)} macro in graph names. For example, {{HOST.HOST2}:key.func()} in the graph name will refer to the host of the second item in the graph.

Use macros without index (i. e.{HOST.HOST}, {HOST.IP}, etc) in all other contexts.