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 Loadable modules Loadable modules, new in Zabbix 2.2, offer a way unsupported, but also when a low-level discovery rule becomes unsupported or a trigger goes into an unknown state. The benefit of having internal events is that users can configure actions based on these events zabbix[items] • zabbix[items_unsupported] • zabbix[java„] • zabbix[process,,,<state>] (alerter, db watchdog, escalator, node watcher, proxy poller, timer processes aren’t supported

can separately define the conditions that have to be met for the trigger to return back to the OK state. 10 There is also more control over how OK events are generated. You can use the problem expression expression as basis, or even select ’None’ in which case the trigger will always remain in problem state if it goes into it. Additionally, PROBLEM event generation mode for single/multiple problem events ”Event type” conditions for internal events - Item in “normal” state, Low-level discovery rule in “normal” state, Trigger in “normal” state 11 For more details, see: • Actions • Recovery operations

available, in the following format: • for map description:

(for trigger and internal events): • ’Problem’ value if the original event is still in problem state; • ’OK’ value if the original event has been resolved. 19 Low-level discovery • Support of LLD ’Problem’ state. When received data are below the threshold, triggers stay in/return to an ’Ok’ state. event - a single occurrence of something that deserves attention such as a trigger changing state or a which may even use a different data collection method. problem - a trigger that is in ”Problem” state. action - a predefined means of reacting to an event. An action consists of operations (e.g. sending

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 in user macros information about a service. The service.info item should now be used instead of the deprecated service_state item. A new db.odbc.discovery item has been introduced to support low-level discovery using ODBC these modules not being loaded, the item will fall back on the old method of retrieving sockets by state via reading the /proc/net/tcp(6) file(s). The methodology for reading the /proc/net/tcp(6) file(s)

rules contains a filter allowing to filter by host group, host, discovery item type, discovery rule state and other parameters. Additionally, the added first column in the list now always displays the host most browsers from using autocompletion in the affected fields. Systemd discovery based on unit state Zabbix agent 2 item systemd.unit.discovery now also returns the current enablement status of unit parameter persistent_dir specifies a directory for storing a file with a state of log[], log.count[], logrt[] or logrt.count[] item. The state includes the log file name, size, position how far the log file was

keeping the notification list with all event links open. • If you snooze a notification in problem state, it will not play audio when the particular problem becomes resolved. • Regardless of how many tabs ’Problem’ state. When received data are below the threshold, triggers stay in/return to an ’Ok’ state. event - a single occurrence of something that deserves attention such as a trigger changing state or a which may even use a different data collection method. problem - a trigger that is in ”Problem” state. problem update - problem management options provided by Zabbix, such as adding comment, acknowledging

- as being ”online” or ”offline”. On Windows a third, ”unknown” state, is possible. A processor is considered to be in an unknown state when it has been detected, but no data has been collected from the 4 Daemon improvements • When monitoring Windows eventlog Zabbix agent will no longer set an item state to NOTSUPPORTED in case of error when formatting the message. Instead, an unformatted message will ’Problem’ state. When received data are below the threshold, triggers stay in/return to an ’Ok’ state. event - a single occurrence of something that deserves attention such as a trigger changing state or a

ports:vmware.dvswitch.discovery[], vmware.dvswitch.fetchports.get[]; • Virtual machines: vmware.vm.state[], vmware.vm.tools[], vmware.vm.snapshot.get[], vmware.vm.consolidationneeded[], vmware.vm.attribute[]; ’Problem’ state. When received data are below the threshold, triggers stay in/return to an ’Ok’ state. event - a single occurrence of something that deserves attention such as a trigger changing state or a which may even use a different data collection method. problem - a trigger that is in ”Problem” state. problem update - problem management options provided by Zabbix, such as adding comment, acknowledging

zabbix[proxy_buffer,state,changes] - returns the number of state changes between disk/memory buffer modes since start; • zabbix[proxy_buffer,state,current] - returns the current working state where the new Select next to the item key field). Preprocessing Advanced root-cause handling for unsupported item state Error handling in case of a failure to retrieve an item value (and thus it becoming unsupported) there can be only one ”any error” matching step at the end of the pipeline probing for unsupported state of the item. If present, it is activated if none of the specific checks (mis)matched the according