1 支持的宏_link管理

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

Macros supported by location


   {HOST.HOST<1-9>}

macro can be used as host within the macro. For example,


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

. Host, host prototype Interface IP/DNS Host macros: {HOST.CONN} , {HOST.DNS} , {HOST.HOST} , {HOST.IP} , {HOST.NAME}
User-definable macros ¹ ¹ For IP address, a single macro has to fill the whole field; multiple macros/mix with text are not supported Interface port User-definable macros A single macro has to fill the whole field; multiple macros/mix with text are not supported SNMP community User-definable macros Key parameters Host macros: {HOST.CONN} , {HOST.DNS} , {HOST.HOST} , {HOST.IP} , {HOST.NAME} , {HOST.PORT}
User-definable macros The supported {HOST.*} macros 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. Update interval, Custom intervals, Timeout (available for supported item types), Store up to (for history/trends) fields User-definable macros A single macro has to fill the whole field; multiple macros/mix with text are not supported. Delete lost resources, Disable lost resources fields User-definable macros These fields are supported for LLD rules only.

A single macro has to fill the whole field; multiple macros/mix with text are not supported. Preprocessing step parameters (including custom scripts),
custom error-handling parameters ( Set value to and Set error to fields) User-definable macros Filter regular expressions Host macros: {HOST.CONN} , {HOST.DNS} , {HOST.HOST} , {HOST.IP} , {HOST.NAME} , {HOST.PORT}
User-definable macros These fields are supported for LLD rules only. Override filter regular expressions User-definable macros These fields are supported for LLD rules only. Override operations: Update interval , History storage period , Trend storage period (for item prototypes) User-definable macros These fields are supported for LLD rules only.

A single macro has to fill the whole field; multiple macros/mix with text are not supported. Item types Calculated/aggregate item formula
( expression constants , function parameters , item key parameters , (aggregate item only) filter conditions (host group name and tag name)) User-definable macros HTTP agent item
URL, Query fields, Request body, Headers (names and values), SSL certificate file, SSL key file fields Host macros: {HOST.CONN} , {HOST.DNS} , {HOST.HOST} , {HOST.IP} , {HOST.NAME} , {HOST.PORT}
Item macros: {ITEM.ID} , {ITEM.KEY} , {ITEM.KEY.ORIG}
User-definable macros URLs that contain a secret macro will not work, as the macro in them will be resolved as "******" HTTP agent item
HTTP Proxy field Item macros: {ITEM.ID} , {ITEM.KEY} , {ITEM.KEY.ORIG}
User-definable macros HTTP agent item
Required status codes, HTTP authentication username/password, SSL key password fields User-definable macros Element label Expression macro: {?EXPRESSION} ¹
Host macros: {HOST.CONN} , {HOST.DESCRIPTION} , {HOST.DNS} , {HOST.HOST} , {HOST.ID} , {HOST.IP} , {HOST.NAME} , {HOST.PORT}
{HOSTGROUP.ID}
Host inventory macros
Map macros
Trigger macros: {TRIGGER.EVENTS.*} , {TRIGGER.ID} , {TRIGGER.PROBLEM.EVENTS.*} , {TRIGGERS.ACK} , {TRIGGERS.PROBLEM.ACK} , {TRIGGERS.PROBLEM.UNACK} , {TRIGGERS.UNACK} ¹ Only the avg , last , max and min functions, with seconds as parameter are supported in this macro in this location. The


   {HOST.HOST<1-9>}

macro can be used as host within the macro. For example,


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

. Link label Expression macro: {?EXPRESSION} ¹ Interface port, Address for active agents port, Timeouts for item types fields User-definable macros (global only) A single macro has to fill the whole field; multiple macros/mix with text are not supported. Proxy group Failover period, Minimum number of proxies fields User-definable macros (global only) A single macro has to fill the whole field; multiple macros/mix with text are not supported. Scripts Manual event action Date/time macros
Event macros, Cause/symptom event macros, Recovery event macros (if recovery took place)
Event update macros: {EVENT.UPDATE.HISTORY} , {EVENT.UPDATE.STATUS}
Expression macro: {?EXPRESSION}
{FUNCTION.VALUE}
Host macros: {HOST.CONN} ¹ , {HOST.DESCRIPTION} , {HOST.DNS} ¹ , {HOST.HOST} ¹ , {HOST.ID} ² , {HOST.IP} ¹ , {HOST.NAME} ¹ , {HOST.PORT} ¹
Host inventory macros
Item macros (except {ITEM.STATE} , {ITEM.STATE.ERROR} )
{MANUALINPUT} ³
Proxy macros
Trigger macros: {TRIGGER.DESCRIPTION} , {TRIGGER.EVENTS.*} , {TRIGGER.EXPRESSION} , {TRIGGER.EXPRESSION.EXPLAIN} , {TRIGGER.EXPRESSION.RECOVERY} , {TRIGGER.EXPRESSION.RECOVERY.EXPLAIN} , {TRIGGER.HOSTGROUP.NAME} , {TRIGGER.ID} , {TRIGGER.NAME} , {TRIGGER.NAME.ORIG} , {TRIGGER.NSEVERITY} , {TRIGGER.SEVERITY} , {TRIGGER.STATUS} , {TRIGGER.TEMPLATE.NAME} , {TRIGGER.URL} , {TRIGGER.URL.NAME} , {TRIGGER.VALUE}
Username macros ¹
User-definable macros (global only) ¹ ¹ Including confirmation text
² Including confirmation text only for URL script type
³ Including URL field and confirmation text only for URL script type Manual host action Expression macro: {?EXPRESSION}
Host macros: {HOST.CONN} ¹ , {HOST.DESCRIPTION} , {HOST.DNS} ¹ , {HOST.HOST} ¹ , {HOST.ID} ² , {HOST.IP} ¹ , {HOST.NAME} ¹ , {HOST.PORT} ¹
Host inventory macros ³
{MANUALINPUT} ⁴
Username macros ¹
User-definable macros (global only) ¹ ¹ Including confirmation text
² Including confirmation text only for URL script type
³ Supported for Zabbix server and Zabbix proxy
⁴ Including URL field and confirmation text only for URL script type Tag name and value Host macros: {HOST.CONN} , {HOST.DNS} , {HOST.HOST} , {HOST.ID} , {HOST.IP} , {HOST.NAME} , {HOST.PORT}
Host inventory macros
Item macros: {ITEM.LASTVALUE*} , {ITEM.LOG.*} , {ITEM.VALUE*}
Trigger macros: {TRIGGER.ID} (trigger tag value only)
User-definable macros Tag name and value macros are resolved during the event generation process only. Trigger

Macro details

This list contains details for each built-in macro grouped by application area:

Action macros

Alert macros

Date/time macros

Discovery macros

Event macros

Event update macros

Cause/symptom event macros

Recovery event macros

Escalation macros

Function macros

Host macros

Target host macros

Host group macros

Host inventory macros

Item macros

Low-level discovery built-in macros

Map macros

Proxy macros

Script macros

Service macros

Trigger macros

Username macros

Note that to customize macro values (for example, shorten or extract specific substrings), you can use macro functions .

Action macros

{ACTION.ID}

The numeric ID of the triggered action.

{ACTION.NAME}

The name of the triggered action.

Alert macros

{ALERT.MESSAGE}

The Default message value from action configuration.

{ALERT.SENDTO}

The Send to value from user media configuration.

{ALERT.SUBJECT}

The Default subject value from action configuration.

Date and time macros

{DATE}

The current date in yyyy.mm.dd. format.

{TIME}

The current time in hh:mm:ss format.

{TIMESTAMP}

The current time in UNIX timestamp format.

Discovery macros

{DISCOVERY.DEVICE.IPADDRESS}

The IP address of the discovered device.
Available always, does not depend on host being added.

{DISCOVERY.DEVICE.DNS}

The DNS name of the discovered device.
Available always, does not depend on host being added.

{DISCOVERY.DEVICE.STATUS}

The status of the discovered device (UP/DOWN).

{DISCOVERY.DEVICE.UPTIME}

The time since the last change of discovery status for a particular device.
For example: 1h 29m 01s.
For devices with status DOWN, this is the period of their downtime.

{DISCOVERY.RULE.NAME}

The name of the discovery rule that discovered the presence or absence of device/service.

{DISCOVERY.SERVICE.NAME}

The name of the discovered service.
For example: HTTP.

{DISCOVERY.SERVICE.PORT}

The port of the discovered service.
For example: 80.

{DISCOVERY.SERVICE.STATUS}

The status of the discovered service (UP/DOWN).

{DISCOVERY.SERVICE.UPTIME}

The time since the last change of discovery status for a particular service.
For example: 1h 29m 01s.
For services with status DOWN, this is the period of their downtime.

Escalation macros

{ESC.HISTORY}

The log of previously sent notifications, their escalation step and status ( sent , in progress or failed ).

Event macros

{EVENT.ACK.STATUS}

The acknowledgment status of the event (Yes/No).

{EVENT.AGE}

The age of the event that triggered an action, with precision down to a second.
Useful in escalated messages.

{EVENT.DATE}

The date of the event that triggered an action.

{EVENT.DURATION}

The duration of the event (time difference between problem and recovery events), with precision down to a second.
Useful in problem recovery messages.

{EVENT.ID}

The numeric ID of the event that triggered an action.

{EVENT.NAME}

The name of the event that triggered an action.

{EVENT.NSEVERITY}

The numeric value of the event severity.
Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.

{EVENT.OBJECT}

The numeric value of the event object.
Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.

{EVENT.OPDATA}

The operational data of the underlying trigger of the problem.

{EVENT.SEVERITY}

The name of the event severity.

{EVENT.SOURCE}

The numeric value of the event source.
Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal, 4 - Service.

{EVENT.STATUS}

The verbal value of the event that triggered an action.

{EVENT.TAGS}

A comma-separated list of event tags.
Expanded to an empty string if no tags exist.

{EVENT.TAGSJSON}

A JSON array containing event tag objects .
Expanded to an empty array if no tags exist.

{EVENT.TAGS<tag name>}

The event tag value referenced by the tag name.
A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) must be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.

{EVENT.TIME}

The time of the event that triggered an action.

{EVENT.TIMESTAMP}

The UNIX timestamp of the event that triggered an action.

{EVENT.VALUE}

The numeric value of the event that triggered an action.
Possible values: 1 - problem, 0 - recovering.

Cause/symptom event macros

{EVENT.CAUSE.ACK.STATUS}

The acknowledgment status of the cause event (Yes/No).
Used in the context of a symptom event.

{EVENT.CAUSE.AGE}

The age of the cause event, with precision down to a second.
Useful in escalated messages.
Used in the context of a symptom event.

{EVENT.CAUSE.DATE}

The date of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.DURATION}

The duration of the cause event (time difference between problem and recovery events), with precision down to a second.
Useful in problem recovery messages.
Used in the context of a symptom event.

{EVENT.CAUSE.ID}

The numeric ID of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.NAME}

The name of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.NSEVERITY}

The numeric value of the cause event severity.
Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.
Used in the context of a symptom event.

{EVENT.CAUSE.OBJECT}

The numeric value of the cause event object.
Possible values: 0 - Trigger, 1 - Discovered host, 2 - Discovered service, 3 - Autoregistration, 4 - Item, 5 - Low-level discovery rule.
Used in the context of a symptom event.

{EVENT.CAUSE.OPDATA}

The operational data of the underlying trigger of the cause problem.
Used in the context of a symptom event.

{EVENT.CAUSE.SEVERITY}

The name of the cause event severity.
Possible values: Not classified , Information , Warning , Average , High , Disaster .
Used in the context of a symptom event.

{EVENT.CAUSE.SOURCE}

The numeric value of the cause event source.
Possible values: 0 - Trigger, 1 - Discovery, 2 - Autoregistration, 3 - Internal.
Used in the context of a symptom event.

{EVENT.CAUSE.STATUS}

The verbal value of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.TAGS}

A comma-separated list of cause event tags.
Expanded to an empty string if no tags exist.
Used in the context of a symptom event.

{EVENT.CAUSE.TAGSJSON}

A JSON array containing cause event tag objects .
Expanded to an empty array if no tags exist.
Used in the context of a symptom event.

{EVENT.CAUSE.TAGS.<tag name>}

The cause event tag value referenced by the tag name.
A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) must be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.
Used in the context of a symptom event.

{EVENT.CAUSE.TIME}

The time of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.TIMESTAMP}

The UNIX timestamp of the cause event.
Used in the context of a symptom event.

{EVENT.CAUSE.UPDATE.HISTORY}

The log of cause problem updates (acknowledgments, etc).
Used in the context of a symptom event.

{EVENT.CAUSE.VALUE}

The numeric value of the cause event
Possible values: 1 - Problem, 0 - Recovering.
Used in the context of a symptom event.

{EVENT.SYMPTOMS}

The list of symptom events. Includes the following details: host name, event name, severity, age, service tags and values.
This macro is used in the context of the cause event and returns information about symptom events.

Recovery event macros

{EVENT.RECOVERY.DATE}

The date of the recovery event.

{EVENT.RECOVERY.ID}

The numeric ID of the recovery event.

{EVENT.RECOVERY.NAME}

The name of the recovery event.

{EVENT.RECOVERY.STATUS}

The verbal value of the recovery event.

{EVENT.RECOVERY.TAGS}

A comma-separated list of recovery event tags. Expanded to an empty string if no tags exist.

{EVENT.RECOVERY.TAGSJSON}

A JSON array containing recovery event tag objects . Expanded to an empty arrahy if no tags exist.

{EVENT.RECOVERY.TIME}

The time of the recovery event.

{EVENT.RECOVERY.TIMESTAMP}

The UNIX timestamp of the recovery event.

{EVENT.RECOVERY.VALUE}

The numeric value of the recovery event.

Event update macros

{EVENT.UPDATE.ACTION}

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).

{EVENT.UPDATE.ACTIONJSON}

A JSON array containing details of the action(s) performed during problem update .
Possible JSON property values:
- true (for acknowledge , unacknowledge , close , unsuppress , cause , and symptom properties);
- <message string> (for message property);
- timestamp (for suppress_until and timestamp properties) or 0 (for suppress_until property if suppressed indefinitely);
- 0, 1, 2, 3, 4, 5 (for old and new severity properties).

For example: {"acknowledge":true,"message":"Monthly maintenance.","severity":{"old":2,"new":1},"suppress_until":1730851199,"timestamp":1730822048}

{EVENT.UPDATE.DATE}

The date of the event update (acknowledgment, etc)
Deprecated name: {ACK.DATE}

{EVENT.UPDATE.HISTORY}

The log of problem updates (acknowledgments, etc).
Deprecated name: {EVENT.ACK.HISTORY}

{EVENT.UPDATE.MESSAGE}

The problem update message.
Deprecated name: {ACK.MESSAGE}

{EVENT.UPDATE.NSEVERITY}

The numeric value of the new event severity set during problem update operation.

{EVENT.UPDATE.SEVERITY}

The name of the new event severity set during problem update operation.

{EVENT.UPDATE.STATUS}

The Numeric value of the problem update status.
Possible values: 0 - Webhook was called because of problem/recovery event, 1 - Update operation.

{EVENT.UPDATE.TIME}

The time of the event update (acknowledgment, etc)
Deprecated name: {ACK.TIME}

{EVENT.UPDATE.TIMESTAMP}

The UNIX timestamp of the event update (acknowledgment, etc)

Function macros

{FUNCTION.VALUE}

The value of the Nth item-based function in the trigger expression at the time of the event.
Only functions with /host/key as the first parameter are counted.

This macro may be used with a numeric index e.g. {FUNCTION.VALUE <1-9> } to point to the first, second, third, etc. function in a trigger expression. See indexed macros .

{FUNCTION.RECOVERY.VALUE}

The value of the Nth item-based function in the recovery expression at the time of the event.*
Only functions with /host/key s as the first parameter are counted.

This macro may be used with a numeric index e.g. {FUNCTION.RECOVERY.VALUE <1-9> } to point to the first, second, third, etc. function in a trigger expression. See indexed macros .

Host macros

{HOST.CONN}

The host IP address or DNS name, depending on host settings.
In global scripts, interface IP/DNS fields and web scenarios the macro will resolve to the main agent interface. If an agent interface is not defined, the main SNMP interface will be used. If an SNMP interface is also not defined, the main JMX interface will be used. If a JMX interface is not defined either, the main IPMI interface will be used. If the host does not have any interface, the macro resolves to 'UNKNOWN'.

This macro 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}

The host description.

This macro may be used with a numeric index as {HOST.DESCRIPTION <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{HOST.DNS}

The host DNS name.
In global scripts, interface IP/DNS fields and web scenarios the macro will resolve to the main agent interface. If an agent interface is not defined, the main SNMP interface will be used. If an SNMP interface is also not defined, the main JMX interface will be used. If a JMX interface is not defined either, the main IPMI interface will be used. If the host does not have any interface, the macro resolves to 'UNKNOWN'.

This macro may be used with a numeric index as {HOST.DNS <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{HOST.HOST}

The technical host name.br> Macro functions are not supported for this macro if it is used as a placeholder in the first parameter of a history function , for example, last(/{HOST.HOST}/{ITEM.KEY}) .
{HOSTNAME<1-9>} is deprecated.

This macro may be used with a numeric index as {HOST.HOST <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{HOST.ID}

The host ID.

This macro 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}

The host IP address.
In global scripts, interface IP/DNS fields and web scenarios the macro will resolve to the main agent interface. If an agent interface is not defined, the main SNMP interface will be used. If an SNMP interface is also not defined, the main JMX interface will be used. If a JMX interface is not defined either, the main IPMI interface will be used. If the host does not have any interface, the macro resolves to 'UNKNOWN'.
{IPADDRESS<1-9>} is deprecated.

This macro may be used with a numeric index as {HOST.IP <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{HOST.METADATA}

The host metadata.

Used only for active agent autoregistration.

{HOST.NAME}

The visible host name.

This macro may be used with a numeric index as {HOST.NAME <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{HOST.PORT}

The host (agent) port.
In global scripts, interface IP/DNS fields and web scenarios the macro will resolve to the main agent interface. If an agent interface is not defined, the main SNMP interface will be used. If an SNMP interface is also not defined, the main JMX interface will be used. If a JMX interface is not defined either, the main IPMI interface will be used. If the host does not have any interface, the macro resolves to 'UNKNOWN'.

This macro may be used with a numeric index as {HOST.PORT <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

Target host macros

{HOST.TARGET.CONN}

The IP address or DNS name of the target host.

{HOST.TARGET.DNS}

The DNS name of the target host.

{HOST.TARGET.HOST}

The technical name of the target host.

{HOST.TARGET.IP}

The IP address of the target host.

{HOST.TARGET.NAME}

The visible name of the target host.

Host group macros

{HOSTGROUP.ID}

The host group ID.

Host inventory macros

{INVENTORY.ALIAS}

The 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}

The 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}

The 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}

The Contact field in host inventory.
{PROFILE.CONTACT<1-9>} is deprecated.

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 .

{INVENTORY.CONTRACT.NUMBER}

The 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}

The 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}

The Hardware field in host inventory.
{PROFILE.HARDWARE<1-9>} is deprecated.

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 .

{INVENTORY.HARDWARE.FULL}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The Location field in host inventory.
{PROFILE.LOCATION<1-9>} is deprecated.

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 .

{INVENTORY.LOCATION.LAT}

The 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}

The 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}

The MAC address A field in host inventory.
{PROFILE.MACADDRESS<1-9>} is deprecated.

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 .

{INVENTORY.MACADDRESS.B}

The 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}

The 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}

The Name field in host inventory.
{PROFILE.NAME<1-9>} is deprecated.

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 .

{INVENTORY.NOTES}

The Notes field in host inventory.
{PROFILE.NOTES<1-9>} is deprecated.

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 .

{INVENTORY.OOB.IP}

The 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}

The 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}

The 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}

The OS field in host inventory.
{PROFILE.OS<1-9>} is deprecated.

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 .

{INVENTORY.OS.FULL}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The Serial number A field in host inventory.
{PROFILE.SERIALNO<1-9>} is deprecated.

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 .

{INVENTORY.SERIALNO.B}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The Software field in host inventory.
{PROFILE.SOFTWARE<1-9>} is deprecated.

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 .

{INVENTORY.SOFTWARE.APP.A}

The 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}

The 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}

The 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}

The 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}

The 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}

The 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}

The Tag field in host inventory.
{PROFILE.TAG<1-9>} is deprecated.

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 .

{INVENTORY.TYPE}

The Type field in host inventory.
{PROFILE.DEVICETYPE<1-9>} is deprecated.

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 .

{INVENTORY.TYPE.FULL}

The 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}

The 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}

The 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}

The 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}

The 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 macros

{ITEM.DESCRIPTION}

The description of the Nth item in the trigger expression that caused a notification.

This macro may be used with a numeric index as {ITEM.DESCRIPTION <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{ITEM.DESCRIPTION.ORIG}

The original 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 as {ITEM.DESCRIPTION.ORIG <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{ITEM.ID}

The numeric ID of the Nth item in the trigger expression that caused a notification.

This macro may be used with a numeric index as {ITEM.ID <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{ITEM.KEY}

The key of the Nth item in the trigger expression that caused a notification.
Macro functions are not supported for this macro if it is used as a placeholder in the first parameter of a history function , for example, last(/{HOST.HOST}/{ITEM.KEY}) .
{TRIGGER.KEY} is deprecated.

This macro may be used with a numeric index as {ITEM.KEY <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{ITEM.KEY.ORIG}

The original key (with macros unresolved) of the Nth item in the trigger expression that caused a notification.

This macro may be used with a numeric index as {ITEM.KEY.ORIG <1-9> } to point to the first, second, third, etc. host in a trigger expression. See indexed macros .

{ITEM.LASTVALUE}

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).
When used in the problem name, the macro will not resolve to the latest item value when viewing problem events; instead, it will keep the item value from the time when the problem happened.
When used in notifications, in some cases the macro might not resolve to the latest item value at the moment the trigger fired. For example, if an item quickly receives two values, "A" and "B", and the trigger fires for "A", notifications might show "B" as the latest value due to a slight processing delay - the latest item value changed between the time the trigger fired and when the notification was created. To avoid this, you can use the {ITEM.VALUE} macro, which resolves to the value at the moment the trigger fires, ensuring the correct value is used in the notification.
It is alias to last(/{HOST.HOST}/{ITEM.KEY}) .
The resolved value for text/log items is truncated to 20 characters by the frontend in the following locations:
- Operational data;
- Trigger description;
- Trigger URLs;
- Trigger URL labels;
- Description of the item value widget.
To resolve to a full value, you may use macro functions , as no values are truncated by the server. For example: {{ITEM.LASTVALUE}.regsub("(.*)", \1)}

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.LASTVALUE.AGE}

The time that elapsed between the latest item value collection and macro evaluation.
Displayed in a human-readable format (e.g. 1m 45s).

This macro may be used with a numeric index e.g. {ITEM.LASTVALUE.AGE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LASTVALUE.DATE}

The date when the latest item value was collected.
Displayed in a YYYYMMDD format.
Server time zone is used in trigger names (in Monitoring -> Problems list), event names, and tag names and values. In all other cases user time zone is used.

This macro may be used with a numeric index e.g. {ITEM.LASTVALUE.DATE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LASTVALUE.TIME}

The time when the latest item value was collected.
Displayed in an HHMMSS format.
Server time zone is used in trigger names (in Monitoring -> Problems list), event names, and tag names and values. In all other cases user time zone is used.

This macro may be used with a numeric index e.g. {ITEM.LASTVALUE.TIME <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LASTVALUE.TIMESTAMP}

The UNIX timestamp when the latest item value was collected.

This macro may be used with a numeric index e.g. {ITEM.LASTVALUE.TIMESTAMP <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LOG.AGE}

The age of the log 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. item in a trigger expression. See indexed macros .

{ITEM.LOG.DATE}

The date when the log entry was written to the log.

This macro may be used with a numeric index e.g. {ITEM.LOG.DATE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LOG.EVENTID}

The 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. item in a trigger expression. See indexed macros .

{ITEM.LOG.NSEVERITY}

The 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. item in a trigger expression. See indexed macros .

{ITEM.LOG.SEVERITY}

The 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. item in a trigger expression. See indexed macros .

{ITEM.LOG.SOURCE}

The 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. item in a trigger expression. See indexed macros .

{ITEM.LOG.TIME}

The time when the log entry was written to the log.

This macro may be used with a numeric index e.g. {ITEM.LOG.TIME <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.LOG.TIMESTAMP}

The UNIX timestamp when the log entry was written to the log.

This macro may be used with a numeric index e.g. {ITEM.LOG.TIMESTAMP <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.NAME}

The name of the item with all macros resolved.

This macro may be used with a numeric index e.g. {ITEM.NAME <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.NAME.ORIG}

The original name (with macros unresolved) of the item.

This macro may be used with a numeric index e.g. {ITEM.NAME.ORIG <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.STATE}

The latest state of the Nth item in the trigger expression that caused a notification.
Possible values: Not supported , Normal .

This macro may be used with a numeric index e.g. {ITEM.STATE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.STATE.ERROR}

The error message with details why an item became unsupported.
If an item goes into the unsupported state and then immediately gets supported again the error field can be empty.

{ITEM.VALUE}

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).
The resolved value for text/log items is truncated to 20 characters by the frontend in the following locations:
- Operational data;
- Trigger description;
- Trigger URLs;
- Trigger URL labels;
- Description of the item value widget.
To resolve to a full value, you may use macro functions , as no values are truncated by the server. For example: {{ITEM.VALUE}.regsub("(.*)", \1)}

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.VALUE.AGE}

The time that elapsed between the item value collection and macro evaluation.
Displayed in a human-readable format (e.g. 1m 45s).

This macro may be used with a numeric index e.g. {ITEM.VALUE.AGE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.VALUE.DATE}

The date when the item value was collected.
Displayed in a YYYYMMDD format.
The server time zone is used in trigger names (in Monitoring -> Problems list), event names, and tag names and values. In all other cases user time zone is used.

This macro may be used with a numeric index e.g. {ITEM.VALUE.DATE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.VALUE.TIME}

The time when the item value was collected.
Displayed in an HHMMSS format.
The server time zone is used in trigger names (in Monitoring -> Problems list), event names, and tag names and values. In all other cases user time zone is used.

This macro may be used with a numeric index e.g. {ITEM.VALUE.TIME <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.VALUE.TIMESTAMP}

The UNIX timestamp when the item value was collected.

This macro may be used with a numeric index e.g. {ITEM.VALUE.TIMESTAMP <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{ITEM.VALUETYPE}

The 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. item in a trigger expression. See indexed macros .

Low-level discovery built-in macros

{LLDRULE.DESCRIPTION}

The description of the low-level discovery rule that caused a notification.

{LLDRULE.DESCRIPTION.ORIG}

The original description (with macros unresolved) of the low-level discovery rule that caused a notification.

{LLDRULE.ID}

The numeric ID of the low-level discovery rule that caused a notification.

{LLDRULE.KEY}

The key of the low-level discovery rule that caused a notification.

{LLDRULE.KEYORIG}

The original key (with macros unresolved) of the low-level discovery rule that caused a notification.

{LLDRULE.NAME}

The name of the low-level discovery rule that caused a notification.

{LLDRULE.NAMEORIG}

The original name (with macros unresolved) of the low-level discovery rule that caused a notification.

{LLDRULE.STATE}

The latest state of the low-level discovery rule.
Possible values: Not supported , Normal .

This macro may be used with a numeric index e.g. {LLDRULE.STATE <1-9> } to point to the first, second, third, etc. item in a trigger expression. See indexed macros .

{LLDRULE.STATE.ERROR}

The error message with details why the low-level discovery rule became unsupported.
If a low-level discovery rule goes into the unsupported state and then immediately gets supported again the error field can be empty.

Map macros

{MAP.ID}

The network map ID.

{MAP.NAME}

The network map name.

Proxy macros

{PROXY.DESCRIPTION}

The proxy description.
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. item in a trigger expression. See indexed macros .

{PROXY.NAME}

The proxy name.
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. item in a trigger expression. See indexed macros .

Script macros

{MANUALINPUT}

The manual input value specified by user at script execution time.

Service macros

{SERVICE.DESCRIPTION}

The service description with macros resolved.

{SERVICE.ID}

The numeric ID of the service that triggered an action.

{SERVICE.NAME}

The service name with macros resolved.

{SERVICE.ROOTCAUSE}

The list of trigger problem events that caused a service to fail, sorted by severity and host name.
Includes the following details: host name, event name, severity, age, service tags and values.

{SERVICE.TAGS}

A comma-separated list of service event tags.
Service event tags can be defined in the service configuration tags section. Expanded to an empty string if no tags exist.

{SERVICE.TAGSJSON}

A JSON array containing service event tag objects.
Service event tags can be defined in the service configuration tags section. Expanded to an empty array if no tags exist.

{SERVICE.TAGS<tag name>}

The service event tag value referenced by the tag name.
The service event tags can be defined in the service configuration tags section.
A tag name containing non-alphanumeric characters (including non-English multibyte-UTF characters) must be double quoted. Quotes and backslashes inside a quoted tag name must be escaped with a backslash.

Trigger macros

{TRIGGER.DESCRIPTION}

The 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}

The number of acknowledged events for a map element in maps, or for the trigger which generated current event in notifications.

{TRIGGER.EVENTS.PROBLEM.ACK}

The number of acknowledged problem events for all triggers disregarding their state.

{TRIGGER.EVENTS.PROBLEM.UNACK}

The number of unacknowledged problem events for all triggers disregarding their state.

{TRIGGER.EVENTS.UNACK}

The number of unacknowledged events for a map element in maps, or for the trigger which generated current event in notifications.

{TRIGGER.EXPRESSION}

The trigger expression.

{TRIGGER.EXPRESSION.EXPLAIN}

A partially-evaluated trigger expression.
Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger expressions.

{TRIGGER.EXPRESSION.RECOVERY}

The trigger recovery expression if OK event generation in trigger configuration is set to "Recovery expression"; otherwise an empty string is returned.

{TRIGGER.EXPRESSION.RECOVERY.EXPLAIN}

A partially-evaluated trigger recovery expression.
Item-based functions are evaluated and replaced by the results at the time of event generation whereas all other functions are displayed as written in the expression. Can be used for debugging trigger recovery expressions.

{TRIGGER.HOSTGROUP.NAME}

A sorted (by SQL query), comma-space separated list of host groups in which the trigger is defined.

{TRIGGER.ID}

The numeric trigger ID which triggered this action.

{TRIGGER.NAME}

The trigger name with macros resolved.
Note that {EVENT.NAME} can be used in actions to display the triggered event/problem name with macros resolved.

{TRIGGER.NAME.ORIG}

The original trigger name (with macros unresolved).

{TRIGGER.NSEVERITY}

The numerical trigger severity.
Possible values: 0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster.

{TRIGGER.PROBLEM.EVENTS.PROBLEM.ACK}

The number of acknowledged problem events for triggers in problem state.

{TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}

The number of unacknowledged problem events for triggers in problem state.

{TRIGGER.SEVERITY}

The trigger severity name.
Can be defined in Administration > General > Trigger displaying options .

{TRIGGER.STATE}

The latest state of the trigger.
Possible values: Unknown , Normal .

{TRIGGER.STATE.ERROR}

The error message with details why a trigger became unsupported.
If a trigger goes into the unsupported state and then immediately gets supported again the error field can be empty.

{TRIGGER.STATUS}

The trigger value at the time of operation step execution.
Possible values: Problem , OK .
{STATUS} is deprecated.

{TRIGGER.TEMPLATE.NAME}

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}

The trigger URL.

{TRIGGER.URL.NAME}

The label for the trigger URL.

{TRIGGER.VALUE}

The current numeric trigger value.
Possible values: 0 - trigger is in OK status, 1 - trigger is in Problem status.

{TRIGGERS.ACK}

The number of acknowledged triggers for a map element, disregarding trigger state.
A trigger is considered to be acknowledged if all of its problem events are acknowledged.

{TRIGGERS.PROBLEM.ACK}

The number of acknowledged problem triggers for a map element.
A trigger is considered to be acknowledged if all of its problem events are acknowledged.

{TRIGGERS.PROBLEM.UNACK}

The 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.UNACK}

The 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.

Username macros

{USER.FULLNAME}

The name, surname and username of the user who added event acknowledgment or started the script.

{USER.NAME}

The name of the user who started the script.

{USER.SURNAME}

The surname of the user who started the script.

{USER.USERNAME}

The username of the user who started the script.
{USER.ALIAS} is now deprecated.

宏索引{MACRO<1-9>}语法仅限于 触发器表达式的上下文 。它能用于按顺序引用表达式中包含的设备。例如：在表达式中包含了设备1，设备2，设备3，那么宏{HOST.IP1},{HOST.IP2}, {HOST.IP3}将分别引用设备1，设备2，设备3的IP地址信息。在提供触发器表达式包含这些函数时，宏{FUNCTION.VALUE1}，{FUNCTION.VALUE2}，{FUNCTION.VALUE3} 将解析为事件发生时触发器表达式中第一个、第二个和第三个基于监控项函数的值。

另外，可以在 图形名称 中使用宏 {?func(/host/key,param)} ，同时再叠加使用宏{HOST.HOST<1-9>}。例如，图形名称中的宏 {?func(/{HOST.HOST2}/key,param)} 代表引用图形中的第二个监控项。

除了这里提到的两种情况外，索引宏不会在任何其他场境中解析。对于其他场景可以使用不带索引的宏。(即{HOST.HOST}，{HOST.IP}，等)

We appreciate your feedback! Our documentation writers will review your report and consider making suggested changes. Please note that we cannot respond. If you would like to follow up on the progress or participate in the discussion, please consider creating a documentation bug report at https://support.zabbix.com/ We greatly appreciate your contribution! Our documentation writers will review the example and consider incorporating it into the page. Please note that while we cannot provide a direct response, your input is highly valuable to us in improving our documentation.