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
manual:config:triggers [2021/05/12 07:28]
martins-v more precise wording
manual:config:triggers [2021/05/17 11:38] (current)
Line 19: Line 19:
 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. 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.
  
-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 //history syncer// 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. ​+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.