Zabbix Documentation 5.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:appendix:triggers:functions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:appendix:triggers:functions [2020/04/29 10:53]
martins-v wording fix
manual:appendix:triggers:functions [2020/05/07 06:46] (current)
martins-v nodata respects proxy availability (ZBXNEXT-1891)
Line 63: Line 63:
 ^ |||| ^ ||||
 |**nodata** (sec,<​mode>​) ​ ^^^^ |**nodata** (sec,<​mode>​) ​ ^^^^
-^ |Checking for no data received. ​ |**sec** - evaluation period in seconds.\\ The period should not be less than 30 seconds because the history syncer process calculates this function only every 30 seconds.\\ \\ nodata(0) is disallowed.\\ \\ **mode** - if set to //strict//, this function will be insensitive to proxy availability (see comments for details). ​ |Supported value types: //any//\\ \\ Returns:\\ 1 - if no data received during the defined period of time\\ 0 - otherwise\\ \\ Since Zabbix 5.0, the '​nodata'​ triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable,​ the '​nodata'​ triggers will not fire immediately after a restored connection, but will take the evaluation period into account plus the delay period ​(calculated as “current server time” - “proxy lastaccess time”). Note that for passive proxies ​unavailability ​is detected ​if connection is restored more than 15 seconds and no less than 2 & ProxyUpdateFrequency seconds later (“current server time” - “proxy lastaccess time”). For active proxies ​unavailability ​is detected ​if connection is restored more than 15 seconds later (“current server time” - “proxy lastaccess time”).\\ \\ To turn off sensitiveness to proxy availability,​ use the second parameter, e.g.: nodata(5m,​strict);​ in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past.\\ \\ Note that this function will display an error if, within the period of the 1st parameter:​\\ - there'​s no data and Zabbix server was restarted\\ - there'​s no data and maintenance was completed\\ - there'​s no data and the item was added or re-enabled\\ Errors are displayed in the //Info// column in trigger [[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|configuration]].\\ \\ This function may not work properly if there are time differences between Zabbix server, proxy and agent. See also: [[:​manual/​installation/​requirements#​time_synchronisation|Time synchronization requirement]]. ​ |+^ |Checking for no data received. ​ |**sec** - evaluation period in seconds.\\ The period should not be less than 30 seconds because the history syncer process calculates this function only every 30 seconds.\\ \\ nodata(0) is disallowed.\\ \\ **mode** - if set to //strict//, this function will be insensitive to proxy availability (see comments for details). ​ |Supported value types: //any//\\ \\ Returns:\\ 1 - if no data received during the defined period of time\\ 0 - otherwise\\ \\ Since Zabbix 5.0, the '​nodata'​ triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable,​ the '​nodata'​ triggers will not fire immediately after a restored connection, but will skip the data for the delayed ​period. Note that for passive proxies ​suppression ​is activated ​if connection is restored more than 15 seconds and no less than 2 & ProxyUpdateFrequency seconds later. For active proxies ​suppression ​is activated ​if connection is restored more than 15 seconds later.\\ \\ To turn off sensitiveness to proxy availability,​ use the second parameter, e.g.: nodata(5m,​strict);​ in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past.\\ \\ Note that this function will display an error if, within the period of the 1st parameter:​\\ - there'​s no data and Zabbix server was restarted\\ - there'​s no data and maintenance was completed\\ - there'​s no data and the item was added or re-enabled\\ Errors are displayed in the //Info// column in trigger [[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|configuration]].\\ \\ This function may not work properly if there are time differences between Zabbix server, proxy and agent. See also: [[:​manual/​installation/​requirements#​time_synchronisation|Time synchronization requirement]]. ​ |
 ^ |||| ^ ||||
 |**now** ​ ^^^^ |**now** ​ ^^^^