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 [2014/09/26 11:28]
sasha Links adapted because of a move operation
manual:config:triggers [2021/05/12 07:29]
Line 1: Line 1:
-===== - #3 Triggers ===== 
-=== Overview === 
-Triggers are logical expressions that "​evaluate"​ data gathered by items and represent the current system state. ​ 
-While items are used to gather system data, it is highly impractical to follow these data all the time waiting for a condition that is alarming or deserves attention. The job of "​evaluating"​ data can be left to trigger expressions. ​ 
-Trigger expressions allow to define a threshold of what state of data is "​acceptable"​. Therefore, should the incoming data surpass the acceptable state, a trigger is "​fired"​ - or changes status to PROBLEM. 
-A trigger may have the following status: 
-|OK     |This is a normal trigger state. Called FALSE in older Zabbix versions.| 
-|PROBLEM|Normally means that something happened. For example, the processor load is too high. Called TRUE in older Zabbix versions.| 
-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 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.