manual:config:triggers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
manual:config:triggers [2011/11/08 09:21] martins-v seems to be redundant for 2.0 |
manual:config:triggers [2019/02/11 06:57] (current) martins-v triggers are evaluated based on history only |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| 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. | ||
| - | If time-based functions (**nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**) are used in the expression, the trigger is recalculated every 30 seconds. | + | Triggers are evaluated based on [[:manual/config/items/history_and_trends|history]] data only; trend data are never considered. |
| - | You can [[2.0:manual:config:triggers:expression|build trigger expressions]] with different degrees of complexity. | + | 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 [[manual:config:triggers:expression|build trigger expressions]] with different degrees of complexity. | ||