. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 6 Supported functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StartTimers no 1-1000 1 Number of pre-forked instances of timers. Timers process time-based trigger functions and maintenance periods. Only the first timer process handles the maintenance periods. This ystem.hostname 参数 Hostname 没有 定义时使用这个参数设 置主机名。 该参数不能用于 UserParameters, performance counters or aliases, 但能用于 system.run[]。 从 Zabbix 1.8.6 开始 支持该参数。 71 HostnameItem no system.hostname Item used for

experimental basis in Zabbix 4.2, is now official. See also: Migration to TimescaleDB Aggregation functions in graphs Along with data display in graphs as bars, the new version also introduces the possibility configured in the data set settings when configuring a graph widget. You may pick the aggregation function and the time interval. Since a data set may comprise several items, there is also another option Additionally the expression tag of these triggers does not reference the host or item, but only the function ({last()}<>0 in the example): Host ... Item

config helper Trigger configuration helper does not allow setting parameter in seconds for trigger function last() anymore 5.2.24 Improved search results page In the search results page, individual blocks cases • Item value macros in map labels now support multiplier suffixes (for example, ”{host:item.function(5m)}”) • In the global search results, host and template configuration links for host group results commands now • Suffixes ”KMGTsmhdw” are now supported in the second parameter of count() trigger function • Previously it was possible to send large amount of data to the Zabbix server, potentially exhausting

sensors. Zabbix 2.2.0 adds reading states of IPMI discrete sensors. A new function band() (bitwise AND) and an improved function count() can be used for testing state of bits of discrete sensors. 5.4 {host:key.func(param)} macro syntax. Similarly to map labels, only avg(), last(), max() and min() functions with seconds as parameter are supported within this macro in graph names. Value mapping is supported 5.9 Some trigger function parameters can be empty A more friendly trigger expression parser allows to omit optional parameters in trigger functions. For example, trigger function ”last(#1)” can be written

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691 6 Supported functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . aggregate calculations) • Aggregated items no longer exist as a separate item type (former aggregate functions, such as grpsum, grpavg, etc have been changed to sum_foreach, avg_foreach, etc to be used in calculated supports other expressions as parameters • Item reference is now the first parameter of history functions (as host/item) • Changed syntax for expression macros The outlined changes can be observed in

to create a very flexible setup. 5 What’s new in Zabbix 5.2.0 Trigger functions for long-term analytics New trigger functions have been added allowing to compare data from absolute periods (hour, day day, week, month, year) and notify user if there is a significant difference. The new functions are: • trendavg - average of trend values for period • trendcount - count of trend values for period • minimum of trend values for period • trendsum - sum of trend values for period Note that the new functions return a result based on trend values, not history. For example, you may want to know if there

to proxy availability, using the new second parameter, e.g.: nodata(5m,strict). In this case the function will work the same as before and fire as soon as the evaluation period (five minutes, in this case) JavaScript code. JavaScript functions for MD5 and SHA256 calculation 27 The functions for MD5 and SHA256 hash calculation have been added to global JavaScript functions. JavaScript memory limit The Zabbix agent 2 items proc.num, proc.cpu.utilization, proc.mem have been updated to use the latest functions intro- duced in Go 1.16 and thus provide better performance. Go version 1.16 or newer is now required

extract. For these purposes, the new version comes with a new concept of macro functions. Currently, two macro functions are supported: • regsub - substring extraction by a regular expression match (case • iregsub - substring extraction by a regular expression match (case insensitive) These macro functions are supported for the {ITEM.VALUE} and {ITEM.LASTVALUE} macro values in trigger names, trigger descrip- event tags, notifications subjects and notification messages. For more information see the macro function section. 9 5.6 Nested representation of host groups Having a built-in mechanism for a logical

template only. 5.9 Option to remove missing resources when importing When using the XML import function before, it was possible to create new elements and update those that already existed. While that displays fatal error if mbstring PHP functions are not enabled. There are no string wrapper functions anymore; they have been replaced by string and/or mbstring functions accordingly. Additionally, the mbstring naming for the use of filter has been introduced. If previously Filter stood for both show and hide functions (with only very tiny icons indicating the direction), now separate Show filter and Hide filter

Encryption section. 5.3 Predictive trigger functions Predictive capabilities are now available via forecast() and timeleft() trigger functions. These functions analyse item history and return the future eliminating consequences afterwards. For more information, see: • Predictive trigger functions • Supported trigger functions (entries for ’forecast’ and ’timeleft’) 5.4 SMTP authentication options Configuring been reduced multiple times. The nodata() function calculation has been improved to limit the database requests to the range specified in nodata() function. When an active proxy connects to Zabbix server