manual:appendix:macros:supported_by_location

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:appendix:macros:supported_by_location [2020/10/19 12:58]
martins-v precision down to a second for age/duration macros (ZBX-18188)
manual:appendix:macros:supported_by_location [2021/01/27 19:24] (current)
Line 17: Line 17:
 |{DISCOVERY.DEVICE.DNS} ​                ​|->​ Discovery notifications and commands ​ |//DNS name 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.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 since Zabbix 4.0.26 (down to a minute before that).\\ For example: 1h 29m 01s.\\ For devices with status DOWN, this is the period of their downtime. |+|{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 since Zabbix 4.0.25 (down to a minute before that).\\ For example: 1h 29m 01s.\\ For devices with status DOWN, this is the period of their downtime. |
 |{DISCOVERY.RULE.NAME} ​                 |-> Discovery notifications and commands ​ |//Name of the discovery rule that discovered the presence or absence of the device or service.// ​ | |{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.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.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.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 since Zabbix 4.0.26 (down to a minute before that).\\ For example: 1h 29m 01s.\\ For services with status DOWN, this is the period of their downtime. ​ |+|{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 since Zabbix 4.0.25 (down to a minute before that).\\ For example: 1h 29m 01s.\\ For services with status DOWN, this is the period of their downtime. ​ |
 |{ESC.HISTORY} ​                         |-> Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Internal notifications ​ |//​Escalation history. Log of previously sent messages.//​\\ Shows previously sent notifications,​ on which escalation step they were sent and their status (//sent//, //in progress// or //​failed//​). ​ | |{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 ​ |//Acknowledgement ​status of the event (Yes/​No)//​. ​ | +|{EVENT.ACK.STATUS} ​                    ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands ​ |//Acknowledgment ​status of the event (Yes/​No)//​. ​ | 
-|{EVENT.AGE} ​                           |-> Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ ​ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Age of the event that triggered an action//, with precision down to a second since Zabbix 4.0.26 (down to a minute before that).\\ Useful in escalated messages. ​ |+|{EVENT.AGE} ​                           |-> Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ ​ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Age of the event that triggered an action//, with precision down to a second since Zabbix 4.0.25 (down to a minute before that).\\ Useful in escalated messages. ​ |
 |{EVENT.DATE} ​                          ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ ​ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Date of the event that triggered an action.// ​ | |{EVENT.DATE} ​                          ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ ​ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Date of the event that triggered an action.// ​ |
 |{EVENT.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 event that triggered an action.// ​ | |{EVENT.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 event that triggered an action.// ​ |
Line 42: Line 42:
 |{EVENT.TIME} ​                          ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Time of the event that triggered an action.// ​ | |{EVENT.TIME} ​                          ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ -> Autoregistration notifications and commands\\ ​ -> Internal notifications ​ |//Time of the event that triggered an action.// ​ |
 |{EVENT.UPDATE.ACTION} ​                 |-> Problem update notifications and commands ​ |//​Human-readable name of the action(s)// performed during [[:​manual/​acknowledges#​updating_problems|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.ACTION} ​                 |-> Problem update notifications and commands ​ |//​Human-readable name of the action(s)// performed during [[:​manual/​acknowledges#​updating_problems|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 (acknowledgement, etc).//\\ Deprecated name: {ACK.DATE} ​ | +|{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 ​ |//Log of problem updates (acknowledgements, etc).//\\ Deprecated name: {EVENT.ACK.HISTORY} ​ |+|{EVENT.UPDATE.HISTORY} ​                ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands ​ |//Log of problem updates (acknowledgments, etc).//\\ Deprecated name: {EVENT.ACK.HISTORY} ​ |
 |{EVENT.UPDATE.MESSAGE} ​                ​|->​ Problem update notifications and commands ​ |//Problem update message.//​\\ Deprecated name: {ACK.MESSAGE} ​ | |{EVENT.UPDATE.MESSAGE} ​                ​|->​ Problem update notifications and commands ​ |//Problem update message.//​\\ Deprecated name: {ACK.MESSAGE} ​ |
-|{EVENT.UPDATE.TIME} ​                   |-> Problem update notifications and commands ​ |//Time of problem update (acknowledgement, etc).//\\ Deprecated name: {ACK.TIME} ​ |+|{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\\ -> Discovery notifications and commands\\ -> Autoregistration notifications and commands\\ -> Internal notifications ​ |//Numeric value of the event that triggered an action (1 for problem, 0 for recovering).//​\\ Supported since 2.2.0. ​ | |{EVENT.VALUE} ​                         |-> Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Discovery notifications and commands\\ -> Autoregistration notifications and commands\\ -> Internal notifications ​ |//Numeric value of the event that triggered an action (1 for problem, 0 for recovering).//​\\ Supported since 2.2.0. ​ |
 |{HOST.CONN[[supported_by_location#​indexed_macros|<​1-9>​]]} ​                      ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Internal notifications\\ -> Global scripts (including confirmation text)\\ -> Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup>​\\ -> Item key parameters<​sup>​[[supported_by_location#​footnotes|2]]</​sup>​\\ -> Host interface IP/DNS\\ -> Trapper item %%"​%%Allowed hosts%%"​%% field<​sup>​[[supported_by_location#​footnotes|12]]</​sup>​\\ -> Database monitoring additional parameters<​sup>​[[supported_by_location#​footnotes|5]]</​sup>​\\ -> SSH and Telnet scripts<​sup>​[[supported_by_location#​footnotes|5]]</​sup>​\\ -> JMX item endpoint field\\ -> Web monitoring<​sup>​[[supported_by_location#​footnotes|6]]</​sup>​\\ -> Low-level discovery rule filter regular expressions<​sup>​[[supported_by_location#​footnotes|8]]</​sup>​\\ -> URL field of dynamic URL dashboard widget/​screen element<​sup>​[[supported_by_location#​footnotes|8]]</​sup>​\\ -> Trigger names and descriptions\\ -> Trigger URLs<​sup>​[[supported_by_location#​footnotes|10]]</​sup>​\\ -> Event tags 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<​sup>​[[supported_by_location#​footnotes|12]]</​sup>​. ​ |//Host IP address or DNS name, depending on host settings//<​sup>​[[supported_by_location#​footnotes|3]]</​sup>​.\\ Supported in trigger names since 2.0.0. ​ |  |{HOST.CONN[[supported_by_location#​indexed_macros|<​1-9>​]]} ​                      ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Internal notifications\\ -> Global scripts (including confirmation text)\\ -> Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup>​\\ -> Item key parameters<​sup>​[[supported_by_location#​footnotes|2]]</​sup>​\\ -> Host interface IP/DNS\\ -> Trapper item %%"​%%Allowed hosts%%"​%% field<​sup>​[[supported_by_location#​footnotes|12]]</​sup>​\\ -> Database monitoring additional parameters<​sup>​[[supported_by_location#​footnotes|5]]</​sup>​\\ -> SSH and Telnet scripts<​sup>​[[supported_by_location#​footnotes|5]]</​sup>​\\ -> JMX item endpoint field\\ -> Web monitoring<​sup>​[[supported_by_location#​footnotes|6]]</​sup>​\\ -> Low-level discovery rule filter regular expressions<​sup>​[[supported_by_location#​footnotes|8]]</​sup>​\\ -> URL field of dynamic URL dashboard widget/​screen element<​sup>​[[supported_by_location#​footnotes|8]]</​sup>​\\ -> Trigger names and descriptions\\ -> Trigger URLs<​sup>​[[supported_by_location#​footnotes|10]]</​sup>​\\ -> Event tags 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<​sup>​[[supported_by_location#​footnotes|12]]</​sup>​. ​ |//Host IP address or DNS name, depending on host settings//<​sup>​[[supported_by_location#​footnotes|3]]</​sup>​.\\ Supported in trigger names since 2.0.0. ​ | 
Line 179: Line 179:
 |{TRIGGERS.ACK} ​                        ​|->​ Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup> ​ |//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.\\ Supported since 1.8.3.| |{TRIGGERS.ACK} ​                        ​|->​ Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup> ​ |//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.\\ Supported since 1.8.3.|
 |{TRIGGERS.PROBLEM.ACK} ​                ​|->​ Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup> ​ |//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.\\ Supported since 1.8.3.| |{TRIGGERS.PROBLEM.ACK} ​                ​|->​ Icon labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup> ​ |//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.\\ Supported since 1.8.3.|
-|{USER.FULLNAME} ​                       |-> Problem update notifications and commands ​ |//Name and surname of the user// who added event acknowledgement.\\ Supported since 3.4.0. ​ |+|{USER.FULLNAME} ​                       |-> Problem update notifications and commands ​ |//Name and surname of the user// who added event acknowledgment.\\ Supported since 3.4.0. ​ |
 |{host:​key.func(param)} ​                ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Icon/shape labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup>​ <​sup>​[[supported_by_location#​footnotes|4]]</​sup>​\\ -> Link labels in maps<​sup>​[[supported_by_location#​footnotes|4]]</​sup>​​\\ -> Graph names<​sup>​[[supported_by_location#​footnotes|7]]</​sup>​\\ -> Trigger expressions<​sup>​[[supported_by_location#​footnotes|9]]</​sup> ​ |//Simple macros, as used in building trigger [[manual:​config:​triggers:​expression|expressions]]//​.\\ \\ Supported for shape labels in maps since 3.4.2. ​ | |{host:​key.func(param)} ​                ​|->​ Trigger-based notifications and commands\\ -> Problem update notifications and commands\\ -> Icon/shape labels in maps<​sup>​[[supported_by_location#​footnotes|1]]</​sup>​ <​sup>​[[supported_by_location#​footnotes|4]]</​sup>​\\ -> Link labels in maps<​sup>​[[supported_by_location#​footnotes|4]]</​sup>​​\\ -> Graph names<​sup>​[[supported_by_location#​footnotes|7]]</​sup>​\\ -> Trigger expressions<​sup>​[[supported_by_location#​footnotes|9]]</​sup> ​ |//Simple macros, as used in building trigger [[manual:​config:​triggers:​expression|expressions]]//​.\\ \\ Supported for shape labels in maps since 3.4.2. ​ |
 |{$MACRO} ​                              ​|->​ See: [[:​manual/​appendix/​macros/​supported_by_location_user|User macros supported by location]] ​ |//​[[:​manual/​config/​macros/​usermacros|User-definable]] macros.// ​ | |{$MACRO} ​                              ​|->​ See: [[:​manual/​appendix/​macros/​supported_by_location_user|User macros supported by location]] ​ |//​[[:​manual/​config/​macros/​usermacros|User-definable]] macros.// ​ |