alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed ”Shared”, now are also supported on ”Dedicated”: • system.stat[cpu,ec] (with ”Dedicated” always returns 100 (percent)) • system.stat[cpu,pc] • system.stat[ent] See system.stat[] in agent items for more passive check the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed load last month (a 10% increase over the previous month): {Server:system.cpu.load.trendavg(1M,now/M)}>1.1*{Server:system.cpu.load.trendavg(1M,now/M-1M)} You may also use the new ”Event name” parameter relative ./ prefix instead of a full path. Example: UserParameterDir=/opt/myscripts UserParameter=check_cpu,./custom_script.sh SNMP item testing When testing SNMP items, it is now possible to specify version-specific

alert that your CPU load is too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed the filter. Monitoring of physical CPU utilization on IBM AIX Zabbix agent for AIX has been enhanced with capability to monitor physical CPU utilization. A system.cpu.util[] item key now has an additional parameter: • system.cpu.util[<cpu>,,,] The key parameter allows to specify whether an item should report logical or physical CPU utilization (sup-

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed at most. 5.16 VMware monitoring improvements A new simple check to monitor VMware virtual machine CPU ready state was added. For more information see VMware monitoring item keys. 5.17 Context support action processing performance. 23 5.21 Item changes/improvements A new proc.cpu.util item has been added to monitor process CPU utilisation. This item is supported on Linux and Solaris platforms. net.udp

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed high latency environments. • The rounding of numbers has been made more accurate when calculating CPU statistics. 10 What’s new in Zabbix 3.2.5 10.1 Frontend improvements • In Windows event log history Cannot accurately apply filter: no value received for macro "{#MACRO.NAME}". Item changes • system.cpu.num agent item on AIX now returns a value based on the logical processors attached to an AIX LPAR and

3.3.1 For version 1.8 • All hosts now are required to belong to at least one group. • CPU index for system.cpu.util key on Linux now starts with 0. • Key vfs.fs.size returns data in bytes for all operating performance. The pollers do not communicate directly with the database and use very little of server CPU and memory resources. 4.1.1.2 Added configuration data cache module 18 Database cache is enabled linked against single template: In this case, templated trigger expression would be: {ca_001:system.cpu.load[,avg1].min({$CPULOAD_PERIOD})}>{$MAX_CPULOAD} 5 Various 5.1 Host maintenance Host and host group

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed at a time or it even makes more sense to collect related metrics simultaneously, for example: • CPU utilization of individual cores • Incoming/outgoing/total network traffic 9 To allow for bulk metric Cannot accurately apply filter: no value received for macro "{#MACRO.NAME}". Item changes • system.cpu.num agent item on AIX now returns a value based on the logical processors attached to an AIX LPAR and

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed passive check the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry. A Zabbix proxy is the ideal solution for centralized monitoring of remote locations

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed passive check the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. Active checks require more complex processing. The load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry. A Zabbix proxy is the ideal solution for centralized monitoring of remote locations

alert that your CPU load it too high on Server X you must first create a host entry for Server X followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed system.cpu.util on Solaris was unified with other platforms - kernel parameter was changed to system and wait parameter was changed to iowait. system.cpu.num is now supported for OSX system.cpu.load now now accepts percpu as the first parameter - if specified, total load divided by online CPU count is returned (default is still all and returns normal load value) vm.memory.size now supports more modes