Zabbix Documentation 4.4

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


Sidebar

manual:appendix:macros:supported_by_location

This is an old revision of the document!


1 Supported macros

Overview

The table contains a complete list of macros supported by Zabbix.

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
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update notifications
Numeric ID of the triggered action.
Supported since 2.2.0.
{ACTION.NAME} → Trigger-based notifications and commands
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update 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
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update notifications
Current date in yyyy.mm.dd. format.
{DISCOVERY.DEVICE.IPADDRESS} → Discovery notifications IP address of the discovered device.
Available always, does not depend on host being added.
{DISCOVERY.DEVICE.DNS} → Discovery notifications DNS name of the discovered device.
Available always, does not depend on host being added.
{DISCOVERY.DEVICE.STATUS} → Discovery notifications Status of the discovered device: can be either UP or DOWN.
{DISCOVERY.DEVICE.UPTIME} → Discovery notifications Time since the last change of discovery status for a particular device.
For example: 1h 29m.
For devices with status DOWN, this is the period of their downtime.
{DISCOVERY.RULE.NAME} → Discovery notifications Name of the discovery rule that discovered the presence or absence of the device or service.
{DISCOVERY.SERVICE.NAME} → Discovery notifications Name of the service that was discovered.
For example: HTTP.
{DISCOVERY.SERVICE.PORT} → Discovery notifications Port of the service that was discovered.
For example: 80.
{DISCOVERY.SERVICE.STATUS} → Discovery notifications Status of the discovered service: can be either UP or DOWN.
{DISCOVERY.SERVICE.UPTIME} → Discovery notifications Time since the last change of discovery status for a particular service.
For example: 1h 29m.
For services with status DOWN, this is the period of their downtime.
{ESC.HISTORY} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update 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
Acknowledgement status of the event (Yes/No).
{EVENT.AGE} → Trigger-based notifications and commands
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update notifications
Age of the event that triggered an action.
Useful in escalated messages.
{EVENT.DATE} → Trigger-based notifications and commands
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update notifications
Date of the event that triggered an action.
{EVENT.ID} → Trigger-based notifications and commands
→ Discovery notifications
→ Auto-registration notifications
→ Internal notifications
→ Problem update notifications
→ Trigger URLs
Numeric ID of the event that triggered an action.
{EVENT.NAME} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications ​
Name of the problem event that triggered an action.
Supported since 4.0.0. ​
{EVENT.NSEVERITY} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications ​
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 ​
Numeric value of of the event object. Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Auto registration, 4 - Item, 5 - Low-level discovery rule.
Supported since 4.4.0. ​
{EVENT.OPDATA} → Trigger-based notifications and commands
→ Problem update notification
Operational data of the underlying trigger of a problem.
Supported since 4.4.0.
{EVENT.RECOVERY.DATE} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update notifications
Date of the recovery event.
Can be used in recovery messages only.
Supported since 2.2.0.
{EVENT.RECOVERY.ID} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update notifications
Numeric ID of the recovery event.
Can be used in recovery messages only. Supported since 2.2.0.
{EVENT.RECOVERY.NAME} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications ​
Name of the recovery event.
Supported since 4.4.1. ​
{EVENT.RECOVERY.STATUS} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update notifications
Verbal value of the recovery event.
Can be used in recovery messages only. Supported since 2.2.0.
{EVENT.RECOVERY.TAGS} → Trigger-based notifications and commands
→ Problem update notifications
A comma separated list of recovery event tags. Expanded to an empty string if no tags exist.
Supported since 3.2.0.
{EVENT.RECOVERY.TIME} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update notifications
Time of the recovery event.
Can be used in recovery messages only.
Supported since 2.2.0.
{EVENT.RECOVERY.VALUE} → Trigger-based notifications and commands
→ Internal notifications
→ Problem update notifications
Numeric value of the recovery event.
Can be used in recovery messages only.
Supported since 2.2.0.
{EVENT.SEVERITY} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications ​
Name of the event severity.
Supported since 4.0.0. ​
{EVENT.SOURCE} ​ ​→​ Trigger-based notifications and commands
→ Problem update notifications ​