Documentation
Table of Contents
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.
| Macro | Supported in | Description |
|---|---|---|
| {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. |
| {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. |
| {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 → Manual event action 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 service:// can be either UP or DOWN. | |{DISCOVERY.SERVICE.UPTIME} |→ Discovery notifications and commands |Time since the last change of discovery status for a particular service, with precision down to a second. 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 → Manual event action scripts |
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 → Manual event action 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 → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Manual event action scripts |
Date of the event that triggered an action. |
| {EVENT.DURATION} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action 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 → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Trigger URLs → Manual event action scripts |
Numeric ID of the event that triggered an action. |
| {EVENT.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action 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 → Manual event action 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 → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Manual event action 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 |
Operational data of the underlying trigger of a problem. Supported since 4.4.0. |
| {EVENT.RECOVERY.DATE} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Date of the recovery event. |
| {EVENT.RECOVERY.ID} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Numeric ID of the recovery event. |
| {EVENT.RECOVERY.NAME} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Name of the recovery event. Supported since 4.4.1. |
| {EVENT.RECOVERY.STATUS} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Verbal value of the recovery event. |
| {EVENT.RECOVERY.TAGS} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action 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 and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
A 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 commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Time of the recovery event. |
| {EVENT.RECOVERY.VALUE} | → Problem recovery notifications and commands → Problem update notifications and commands (if recovery took place) → Manual event action scripts (if recovery took place) |
Numeric value of the recovery event. |
| {EVENT.SEVERITY} | → Trigger-based notifications and commands → Problem update notifications and commands → Manual event action scripts |
Name of the event severity. Supported since 4.0.0. |
| {EVENT.SOURCE} | → Trigger-based notifications and commands → Problem update notifications and commands → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Manual event action 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 → Internal notifications → Manual event action scripts |
Verbal value of the event that triggered an action. |
| {EVENT.TAGS} | → Trigger-based notifications and commands → Problem update notifications and commands → Manual event action 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 → Manual event action scripts |
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 → Webhook media type URL names and URLs → Manual event action 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 → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Manual event action 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. 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 | Date of problem update (acknowledgment, etc). Deprecated name: {ACK.DATE} |
| {EVENT.UPDATE.HISTORY} | → Trigger-based notifications and commands → Problem update notifications and commands → Manual event action 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 |
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 | Time of problem update (acknowledgment, etc). Deprecated name: {ACK.TIME} |
| {EVENT.VALUE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
Numeric value of the event that triggered an action (1 for problem, 0 for recovering). |
| {HOST.CONN} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → 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 → Trigger names, event names, operational data and descriptions → Trigger URLs → Tag names and values → 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Host IP address or DNS name, depending on host settings2. May be used with a numeric index as {HOST.CONN<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {HOST.DESCRIPTION} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Map element labels → Manual event action scripts |
Host description. This macro may be used with a numeric index e.g. {HOST.DESCRIPTION<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 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 → Trigger names, event names, operational data and descriptions → Trigger URLs → Tag names and values → 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Host DNS name2. This macro may be used with a numeric index e.g. {HOST.DNS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 monitoring4 → 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 → 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Host name. This macro may be used with a numeric index e.g. {HOST.HOST<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 event action scripts |
Host ID. May be used with a numeric index as {HOST.ID<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 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 → Trigger names, event names, operational data and descriptions → Trigger URLs → Tag names and values → 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Host IP address2. This macro may be used with a numeric index e.g. {HOST.IP<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 monitoring4 → 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 → 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Visible host name. This macro may be used with a numeric index e.g. {HOST.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 event action scripts |
Host (agent) port2. This macro may be used with a numeric index e.g. {HOST.PORT<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Alias field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.ALIAS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.ASSET.TAG} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Asset tag field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.ASSET.TAG<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.CHASSIS} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Chassis field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.CHASSIS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.CONTACT} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Contact field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.CONTACT<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Contract number field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.CONTRACT.NUMBER<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.DEPLOYMENT.STATUS} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Deployment status field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.DEPLOYMENT.STATUS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HARDWARE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Hardware field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Hardware (Full details) field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HARDWARE.FULL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HOST.NETMASK} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Host subnet mask field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETMASK<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HOST.NETWORKS} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Host networks field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HOST.NETWORKS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HOST.ROUTER} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Host router field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HOST.ROUTER<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HW.ARCH} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Hardware architecture field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HW.ARCH<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HW.DATE.DECOMM} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Date hardware decommissioned field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.DECOMM<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HW.DATE.EXPIRY} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HW.DATE.INSTALL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Date hardware installed field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.INSTALL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.HW.DATE.PURCHASE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Date hardware purchased field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.HW.DATE.PURCHASE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.INSTALLER.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Installer name field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.INSTALLER.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.LOCATION} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Location field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.LOCATION<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Location latitude field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LAT<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.LOCATION.LON} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Location longitude field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.LOCATION.LON<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.MACADDRESS.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
MAC address A field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.A<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
MAC address B field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.MACADDRESS.B<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.MODEL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Model field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.MODEL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Name field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Notes field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.NOTES<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
OOB IP address field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OOB.IP<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.OOB.NETMASK} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
OOB subnet mask field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OOB.NETMASK<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.OOB.ROUTER} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
OOB router field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OOB.ROUTER<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.OS} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
OS field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OS<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
OS (Full details) field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OS.FULL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.OS.SHORT} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
OS (Short) field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.OS.SHORT<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.CELL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Primary POC cell field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.CELL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.EMAIL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Primary POC email field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.EMAIL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Primary POC name field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.NOTES} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Primary POC notes field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.PRIMARY.NOTES<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.PHONE.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.PHONE.B} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.PRIMARY.SCREEN} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.CELL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Secondary POC cell field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.CELL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.EMAIL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Secondary POC email field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.EMAIL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Secondary POC name field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.NOTES} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Secondary POC notes field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.POC.SECONDARY.NOTES<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.PHONE.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.PHONE.B} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.POC.SECONDARY.SCREEN} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SERIALNO.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Serial number A field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.A<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Serial number B field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SERIALNO.B<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.ADDRESS.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site address A field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.A<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.ADDRESS.B} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site address B field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.B<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.ADDRESS.C} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site address C field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.ADDRESS.C<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.CITY} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site city field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.CITY<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.COUNTRY} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site country field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.COUNTRY<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.NOTES} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site notes field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.NOTES<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.RACK} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site rack location field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.RACK<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.STATE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site state/province field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.STATE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SITE.ZIP} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Site ZIP/postal field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SITE.ZIP<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Software application A field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.A<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE.APP.B} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software application B field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.B<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE.APP.C} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software application C field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.C<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE.APP.D} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software application D field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.D<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE.APP.E} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software application E field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.APP.E<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.SOFTWARE.FULL} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Software (Full details) field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.SOFTWARE.FULL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.TAG} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Tag field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.TAG<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Type field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.TYPE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Map element labels, map URL names and values → Manual event action scripts |
Type (Full details) field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.TYPE.FULL<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.URL.A} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
URL A field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.URL.A<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.URL.B} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
URL B field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.URL.B<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.URL.C} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
URL C field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.URL.C<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {INVENTORY.VENDOR} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Tag names and values → Map element labels, map URL names and values → Manual event action scripts |
Vendor field in host inventory. This macro may be used with a numeric index e.g. {INVENTORY.VENDOR<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.DESCRIPTION} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.DESCRIPTION.ORIG} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 values8 → 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 values8 → 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 values8 → 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.8 → Manual event action scripts |
Original key (with macros not expanded) of the Nth item in the trigger expression that caused a notification 4. This macro may be used with a numeric index e.g. {ITEM.KEY.ORIG<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 → Trigger URLs7 → Manual event action scripts |
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 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 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>} to point to the first, second, third, etc. item in a trigger expression. See 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
Date of the log item event. This macro may be used with a numeric index e.g. {ITEM.LOG.DATE<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
Time of the log item event. This macro may be used with a numeric index e.g. {ITEM.LOG.TIME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.NAME} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
Name of the Nth item (with macros resolved) in the trigger expression that caused a notification. This macro may be used with a numeric index e.g. {ITEM.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.NAME.ORIG} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
Original name (i.e. without macros resolved) 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.ORIG<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.STATE} | → Item-based internal notifications | 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>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {ITEM.VALUE} | → Trigger-based notifications and commands → Problem update notifications and commands → Trigger names, event names, operational data and descriptions → Tag names and values → Trigger URLs7 → Manual event action scripts |
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 menu section). Customizing 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>} to point to the first, second, third, etc. item in a trigger expression. See indexed macros. |
| {ITEM.VALUETYPE} | → Trigger-based notifications and commands → Problem update notifications and commands → Internal notifications → Manual event action scripts |
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>} to point to the first, second, third, etc. host in a trigger expression. See 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. |
| {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 |
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. This macro may be used with a numeric index e.g. {PROXY.DESCRIPTION<1-9>} to point to the first, second, third, etc. host in a trigger expression. See 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 |
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. This macro may be used with a numeric index e.g. {PROXY.NAME<1-9>} to point to the first, second, third, etc. host in a trigger expression. See indexed macros. |
| {TIME} | → Trigger-based notifications and commands → Problem update notifications and commands → Discovery notifications and commands → Autoregistration notifications and commands → Internal notifications → Trigger event names → Manual event action 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 |
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.EVENTS.ACK} | → Trigger-based notifications and commands → Problem update notifications and commands → Map element labels → Manual event action 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 |
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 |
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 |
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 |
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 |
Trigger expression. |
| {TRIGGER.EXPRESSION.RECOVERY} | → Trigger-based notifications and commands → Problem update notifications and commands → Trigger-based internal notifications → Manual event action scripts |
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 value → Manual event action 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 |
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 |
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 |
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 |
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.STATUS} | → Trigger-based notifications and commands → Problem update notifications and commands → Manual event action scripts |
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 → Manual event action 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 |
Trigger URL. |
| {TRIGGER.VALUE} | → Trigger-based notifications and commands → Problem update notifications and commands → Trigger expressions → Manual event action 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 (including confirmation text) → Manual event action 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 (including confirmation text) → Manual event action scripts (including confirmation text) |
Name of the user who started the script. Supported since 5.0.2. |
| {USER.SURNAME} | → Manual host action scripts (including confirmation text) → Manual event action scripts (including confirmation text) |
Surname of the user who started the script. Supported since 5.0.2. |
| {USER.USERNAME} | → Manual host action scripts (including confirmation text) → Manual event action 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. |
| {host:key.func(param)} | → Trigger-based notifications and commands → Problem update notifications and commands → Map element/shape labels3 → Link labels in maps3 → Graph names5 |
Simple macros, as used in building trigger expressions. Supported for shape labels in maps since 3.4.2. |
| {$MACRO} | → See: User macros supported by location | User-definable macros. |
| {#MACRO} | → See: Low-level discovery macros | Low-level discovery macros. Customizing the macro value is supported for this macro, starting with Zabbix 4.0.0. |
| {?EXPRESSION} | → Trigger event names | Expression macro for formula calculations. Calculated by expanding all macros inside and evaluating the resulting expression. See example of using an expression macro in the event name. Supported since 5.2.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 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 Supported since Zabbix 2.2.0, {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. Macros {HOST.*} in web scenario Name and web scenario step Name are not supported since Zabbix 5.4.0.
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:
6 Simple macros may not be used inside each other.
7 Supported since 4.0.0.
8 Supported since 5.2.5.
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 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.
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.