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


manual:config:triggers:trigger

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:config:triggers:trigger [2019/02/14 13:39]
martins-v more on viewing inherited template tags in trigger config
manual:config:triggers:trigger [2020/02/12 12:10] (current)
marinagen a sentence about tag-value pairs (ZBX-16673)
Line 14: Line 14:
 The **Trigger** tab contains all the essential trigger attributes. ​ The **Trigger** tab contains all the essential trigger attributes. ​
  
-{{trigger_a0.png|}}+{{trigger1.png|}}
  
 All mandatory input fields are marked with a red asterisk. ​ All mandatory input fields are marked with a red asterisk. ​
  
 ^Parameter^Description^ ^Parameter^Description^
-|//​Name// ​  ​|Trigger name.\\ ​The name may contain the supported ​[[manual:​appendix:​macros:​supported_by_location|macros]]:​ ''​{HOST.HOST},​ {HOST.NAME},​ {HOST.CONN},​ {HOST.DNS}, {HOST.IP}, {ITEM.VALUE},​ {ITEM.LASTVALUE}''​ and ''​{$MACRO}''​.\\ **$1, $2...$9** macros can be used to refer to the first, second...ninth constant of the expression.\\ //Note//: $1-$9 macros will resolve correctly if referring to constants in relatively simple, straightforward expressions. For example, the name "​Processor load above $1 on {HOST.NAME}"​ will automatically change to "​Processor load above 5 on New host" if the expression is {New host:​system.cpu.load[percpu,​avg1].last()}>​5 ​ |+|//​Name// ​  ​|Trigger name.\\ ​Supported ​[[manual:​appendix:​macros:​supported_by_location|macros]] ​are: ''​{HOST.HOST},​ {HOST.NAME},​ {HOST.CONN},​ {HOST.DNS}, {HOST.IP}, {ITEM.VALUE},​ {ITEM.LASTVALUE}''​ and ''​{$MACRO}'' ​user macros.\\ **$1, $2...$9** macros can be used to refer to the first, second...ninth constant of the expression.\\ //Note//: $1-$9 macros will resolve correctly if referring to constants in relatively simple, straightforward expressions. For example, the name "​Processor load above $1 on {HOST.NAME}"​ will automatically change to "​Processor load above 5 on New host" if the expression is {New host:​system.cpu.load[percpu,​avg1].last()}>​5 ​ | 
 +|//​Operational data// ​ |Operational data allow to define arbitrary strings along with macros. The macros will resolve dynamically to real time data in //​Monitoring//​ -> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​. While macros in the trigger name (see above) will resolve to their values at the moment of a problem happening and will become the basis of a static problem name, the macros in the operational data maintain the ability to display the very latest information dynamically.\\ Supported [[manual:​appendix:​macros:​supported_by_location|macros]] are: ''​{HOST.HOST},​ {HOST.NAME},​ {HOST.CONN},​ {HOST.DNS}, {HOST.IP}, {HOST.PORT},​ {ITEM.VALUE},​ {ITEM.LASTVALUE}''​ and ''​{$MACRO}''​ user macros.\\ This field is supported since Zabbix 4.4.  |
 |//​Severity// ​ |Set the required trigger [[severity|severity]] by clicking the buttons. ​ | |//​Severity// ​ |Set the required trigger [[severity|severity]] by clicking the buttons. ​ |
 |//​Expression// ​  ​|Logical [[expression|expression]] used to define the conditions of a problem.\\ A problem is created after all the conditions included in the expression are met, i.e. the expression evaluates to TRUE. The problem will be resolved as soon as the expression evaluates to FALSE, unless additional recovery conditions are specified in //Recovery expression//​. ​ | |//​Expression// ​  ​|Logical [[expression|expression]] used to define the conditions of a problem.\\ A problem is created after all the conditions included in the expression are met, i.e. the expression evaluates to TRUE. The problem will be resolved as soon as the expression evaluates to FALSE, unless additional recovery conditions are specified in //Recovery expression//​. ​ |
Line 28: Line 29:
 |//Tag for matching// ​ |Enter event tag name to use for event correlation.\\ This field is displayed if 'All problems if tag values match' is selected for the //OK event closes// property and is mandatory in this case.\\ Supported since Zabbix 3.2.0. ​ | |//Tag for matching// ​ |Enter event tag name to use for event correlation.\\ This field is displayed if 'All problems if tag values match' is selected for the //OK event closes// property and is mandatory in this case.\\ Supported since Zabbix 3.2.0. ​ |
 |//Allow manual close// ​ |Check to allow [[:​manual/​config/​events/​manual_close|manual closing]] of problem events generated by this trigger. Manual closing is possible when acknowledging problem events.\\ Supported since Zabbix 3.2.0. ​ | |//Allow manual close// ​ |Check to allow [[:​manual/​config/​events/​manual_close|manual closing]] of problem events generated by this trigger. Manual closing is possible when acknowledging problem events.\\ Supported since Zabbix 3.2.0. ​ |
-|//​URL// ​  |If not empty, the URL entered here is available as a link in several frontend locations, e.g. when clicking on the problem name in //​Monitoring -> Problems// (//URL// option in the //Trigger// menu) and //​Problems//​ dashboard widget.\\ Supported macros: {ITEM.VALUE},​ {ITEM.LASTVALUE},​ {TRIGGER.ID},​ several [[:​manual/​appendix/​macros/​supported_by_location|{HOST.*}]] macros, user macros. ​ |+|//​URL// ​  |If not empty, the URL entered here is available as a link in several frontend locations, e.g. when clicking on the problem name in //​Monitoring -> Problems// (//URL// option in the //Trigger// menu) and //​Problems//​ dashboard widget.\\ Supported macros: ​{EVENT.ID}, ​{ITEM.VALUE},​ {ITEM.LASTVALUE},​ {TRIGGER.ID},​ several [[:​manual/​appendix/​macros/​supported_by_location|{HOST.*}]] macros, user macros. ​ |
 |//​Description// ​  |Text field used to provide more information about this trigger. May contain instructions for fixing specific problem, contact detail of responsible staff, etc.\\ //Starting with Zabbix 2.2//, the description may contain the same set of macros as trigger name.  | |//​Description// ​  |Text field used to provide more information about this trigger. May contain instructions for fixing specific problem, contact detail of responsible staff, etc.\\ //Starting with Zabbix 2.2//, the description may contain the same set of macros as trigger name.  |
 |//​Enabled// ​  ​|Unchecking this box will disable the trigger if required. ​ | |//​Enabled// ​  ​|Unchecking this box will disable the trigger if required. ​ |
Line 39: Line 40:
  
 ^Parameter^Description^ ^Parameter^Description^
-|//​Name/​Value// ​ |Set custom tags to mark trigger events.\\ Tags are a pair of tag name and value. You can use only the name or pair it with a value.\\ User macros, user macro context, low-level discovery macros and macro [[:​manual/​config/​macros/​macro_functions|functions]] with ''<​nowiki>​{{ITEM.VALUE}}</​nowiki>'',​ ''<​nowiki>​{{ITEM.LASTVALUE}}</​nowiki>''​ and low-level discovery macros are supported in event tags. Low-level discovery macros can be used inside macro context.\\ If the total length of expanded value exceeds 255, it will be cut to 255 characters.\\ See all [[:​manual/​config/​event_correlation/​trigger/​event_tags#​macro_support|macros]] supported for event tags.\\ [[:​manual/​config/​event_correlation/​trigger/​event_tags|Event tags]] can be used for event correlation,​ in action conditions and will also be seen in //​Monitoring//​ -> //​Problems//​ or the //​Problems//​ widget.\\ Supported since Zabbix 3.2.0. ​ |+|//​Name/​Value// ​ |Set custom tags to mark trigger events.\\ Tags are a pair of tag name and value. You can use only the name or pair it with a value. A trigger may have several tags with the same name, but different values.\\ User macros, user macro context, low-level discovery macros and macro [[:​manual/​config/​macros/​macro_functions|functions]] with ''<​nowiki>​{{ITEM.VALUE}}</​nowiki>'',​ ''<​nowiki>​{{ITEM.LASTVALUE}}</​nowiki>''​ and low-level discovery macros are supported in event tags. Low-level discovery macros can be used inside macro context.\\ {TRIGGER.ID} macro is supported in trigger tag values since Zabbix 4.4.1. It may be useful for identifying triggers created from trigger prototypes and, for example, suppressing problems from these triggers during maintenance.\\ If the total length of expanded value exceeds 255, it will be cut to 255 characters.\\ See all [[:​manual/​config/​event_correlation/​trigger/​event_tags#​macro_support|macros]] supported for event tags.\\ [[:​manual/​config/​event_correlation/​trigger/​event_tags|Event tags]] can be used for event correlation,​ in action conditions and will also be seen in //​Monitoring//​ -> //​Problems//​ or the //​Problems//​ widget.\\ Supported since Zabbix 3.2.0. ​ |
  
 The **Dependencies** tab contains all the [[dependencies|dependencies]] of the trigger. ​ The **Dependencies** tab contains all the [[dependencies|dependencies]] of the trigger. ​
Line 59: Line 60:
 To test the expression, click on //​Expression constructor//​ under the expression field. To test the expression, click on //​Expression constructor//​ under the expression field.
  
-{{:​manual:​config:​triggers:​expr_constructor_link_new.png|}}+{{:​manual:​config:​triggers:​trigger_to_test.png|}}
  
 In the Expression constructor,​ all individual expressions are listed. To open the testing window, click on //Test// below the expression list. In the Expression constructor,​ all individual expressions are listed. To open the testing window, click on //Test// below the expression list.
  
-{{:​manual:​config:​triggers:​expr_constructor_test_new.png|}}+{{:​manual:​config:​triggers:​expressions_test_button.png?600|}}
  
 In the testing window you can enter sample values ("80, 70, 0, 1" in this example) and then see the expression result, by clicking on the //Test// button. In the testing window you can enter sample values ("80, 70, 0, 1" in this example) and then see the expression result, by clicking on the //Test// button.
  
-{{:​manual:​config:​triggers:​expression_test_new.png?600|}}+{{:​manual:​config:​triggers:​expr_test.png?600|}}
  
 The result of the individual expressions as well as the whole expression can be seen. The result of the individual expressions as well as the whole expression can be seen.