Zabbix Documentation 3.2

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 [2015/02/09 14:55]
martins-v new macros supported in trigger URL field
manual:config:triggers:trigger [2017/04/13 08:01] (current)
martins-v it is not possible to resolve a problem by recovery expression if the problem condition still persists
Line 18: Line 18:
 ^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.\\ 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 ​ |
-|//​Expression// ​  ​|Logical [[expression|expression]] used for calculating the trigger state. ​ | 
-|//Multiple PROBLEM events generation// ​  |By checking this option you can set that an event is generated upon //every// '​Problem'​ evaluation of the trigger. ​ | 
-|//​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.  | 
-|//​URL// ​  |If not empty, the URL entered here is available as a link when clicking on the trigger name in //​Monitoring -> Triggers//​.\\ Macros may be used in the trigger URL field - {TRIGGER.ID},​ several [[:​manual/​appendix/​macros/​supported_by_location|{HOST.*}]] macros (since Zabbix 3.0.0) and user macros (since Zabbix 3.0.0). ​ | 
 |//​Severity// ​ |Set the required trigger [[severity|severity]] by clicking the buttons. ​ | |//​Severity// ​ |Set the required trigger [[severity|severity]] by clicking the buttons. ​ |
 +|//Problem expression// ​  ​|Logical [[expression|expression]] used to define the conditions of a problem. ​ |
 +|//OK event generation// ​  |OK event generation options:\\ **Expression** - OK events are generated based on the same expression as problem events;\\ **Recovery expression** - OK events are generated if the problem expression evaluates to FALSE and the recovery expression evaluates to TRUE;\\ **None** - in this case the trigger will never return to an OK state on its own.\\ Supported since Zabbix 3.2.0. ​ |
 +|//Recovery expression// ​  ​|Logical [[expression|expression]] used to define the conditions when the problem is resolved.\\ Recovery expression is evaluated only after the problem expression evaluates to FALSE. It is not possible to resolve a problem by recovery expression if the problem condition still persists.\\ This field is optional and only available if '​Recovery expression'​ is selected for //OK event generation//​.\\ Supported since Zabbix 3.2.0. ​ |
 +|//PROBLEM event generation mode// ​  |Mode for generating problem events:\\ **Single** - a single event is generated when a trigger goes into the '​Problem'​ state for the first time;\\ **Multiple** - an event is generated upon //every// '​Problem'​ evaluation of the trigger. ​ |
 +|//OK event closes// ​ |Select if OK event closes:\\ **All problems** - all problems of this trigger\\ **All problems if tag values match** - only those trigger problems with matching event tag values\\ 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.\\ User macros and user macro context is supported since Zabbix 3.2.2. Low-level discovery macros can be used inside user macro context.\\ Supported since Zabbix 3.2.0. ​ |
 +|//​Tags// ​ |Set custom tags to mark trigger events.\\ [[:​manual/​config/​triggers/​event_tags|Event tags]] can be used for event correlation,​ in action conditions and will also be seen in //​Monitoring//​ -> //​Problems//​.\\ Tags are a pair of tag name and value. You can use only the name or pair it with a value.\\ Both tag names and tag values may include low-level discovery macros and macro [[:​manual/​config/​macros/​macro_functions|functions]]:​ ''​{{ITEM.VALUE}.regsub(pattern,​ output)}, {{ITEM.VALUE}.iregsub(pattern,​ output)}''​. If the total length of expanded value exceeds 255, it will be cut to 255 characters.\\ User macros and user macro context is supported since Zabbix 3.2.2. Low-level discovery macros can be used inside user macro context.\\ Note that in Zabbix 3.2.0, 3.2.1 it is not allowed to use a forward slash in the tag name.\\ Event tags are 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.\\ This field is available if event acknowledgement is activated in //​Administration//​ -> //​General//​. \\ Supported since Zabbix 3.2.0. ​ |
 +|//​URL// ​  |If not empty, the URL entered here is available as a link when clicking on the trigger name in //​Monitoring -> Triggers//​.\\ Macros may be used in the trigger URL field - {TRIGGER.ID},​ several [[:​manual/​appendix/​macros/​supported_by_location|{HOST.*}]] macros (since Zabbix 3.0.0) and user macros (since Zabbix 3.0.0). ​ |
 +|//​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. ​ |