manual:config:triggers

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
Next revision Both sides next revision
manual:config:triggers [2014/09/26 11:28]
sasha Links adapted because of a move operation
manual:config:triggers [2021/05/13 05:19]
martins-v new trigger syntax (ZBXNEXT-6451)
Line 1: Line 1:
-===== - #3 Triggers =====+===== 3 Triggers =====
  
 === Overview === === Overview ===
Line 12: Line 12:
  
 ^VALUE ​ ^DESCRIPTION^ ^VALUE ​ ^DESCRIPTION^
-|OK     ​|This is a normal trigger state. ​Called FALSE in older Zabbix versions.+|OK       ​|This is a normal trigger state. ​ 
-|PROBLEM|Normally means that something happened. For example, the processor load is too high. Called TRUE in older Zabbix versions.|+|PROBLEM ​ |Normally means that something happened. For example, the processor load is too high.  |
  
 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 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. ​+Most trigger functions are evaluated based on [[:​manual/​config/​items/​history_and_trends|history]] data, while some trigger functions for long-term analytics, e.g. **trendavg()**,​ **trendcount()**,​ etc, use trend data. 
 + 
 +Time-based functions (**nodata()**,​ **date()**, **dayofmonth()**,​ **dayofweek()**,​ **time()**, **now()**) are recalculated every 30 seconds by a Zabbix //history syncer// process. ​Time-based ​functions can only be used alongside at least one non-time-based ​function; ​in this case the trigger ​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. You can [[manual:​config:​triggers:​expression|build trigger expressions]] with different degrees of complexity.