In aggregate calculations information from several items may be collected by Zabbix server (by doing direct database queries) to calculate an aggregate, depending on the aggregate function used.
Aggregate calculations do not require any agent running on the host being monitored.
To define aggregate calculations, select the Calculated item type.
Aggregates can be retrieved by working with either:
aggregate_functionis one of the supported aggregate functions: avg, max, min, sum, etc.
foreach_functionis one of the supported foreach functions: avg_foreach, count_foreach, etc.
Foreach functions use an item filter, to work with the history of multiple items, and return an array of values - one for each item.
If the aggregate results in a float value it will be trimmed to an integer if the aggregated item type of information is Numeric (unsigned).
An aggregate calculation may become unsupported if:
Examples of keys for aggregate calculations.
Total disk space of host group 'MySQL Servers'.
Sum of latest values of all items matching net.if.in[*] on the host.
Average processor load of host group 'MySQL Servers'.
5-minute average of the number of queries per second for host group 'MySQL Servers'.
Average CPU load on all hosts in multiple host groups that have the specific tags.
Calculation used on the latest item value sums of a whole host group.
The total number of unsupported items in host group 'Zabbix servers'.
Expressions (including function calls) cannot be used as history, trend, or foreach function parameters. However, those functions themselves can be used in other (non-historical) function parameters.
Note that in an expression like:
it cannot be guaranteed that both parts of the equation will always have the same set of values. While one part of the expression is evaluated, a new value for the requested period may arrive and then the other part of the expression will have a different set of values.