This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
manual:config:triggers [2014/09/25 14:42] sasha Page moved from 2.4:manual:config:triggers to manual:config:triggers |
manual:config:triggers [2019/02/11 06:59] (current) martins-v triggers are evaluated based on history only |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== - #3 Triggers ===== | + | ===== 3 Triggers ===== |
=== Overview === | === Overview === | ||
Line 16: | Line 16: | ||
Trigger status (the expression) is recalculated every time Zabbix server receives a new value that is part of the expression. | Trigger status (the expression) is recalculated every time Zabbix server receives a new value that is part of the expression. | ||
+ | |||
+ | Triggers are evaluated based on [[:manual/config/items/history_and_trends|history]] data only; trend data are never considered. | ||
If time-based functions (**nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix //timer// process. If both time-based and non-time-based functions are used in an expression, it is recalculated when a new value is received **and** every 30 seconds. | If time-based functions (**nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**) are used in the expression, the trigger is recalculated every 30 seconds by a Zabbix //timer// process. If both time-based and non-time-based functions are used in an expression, it is recalculated when a new value is received **and** every 30 seconds. | ||
- | You can [[:2.4/manual/config/triggers/expression|build trigger expressions]] with different degrees of complexity. | + | You can [[manual:config:triggers:expression|build trigger expressions]] with different degrees of complexity. |