• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation visible in screens, where it may take some time for all screen elements to load properly, and the result often was a page where elements jumped around for a while. Since Zabbix 2.0.3, screens in monitoring Additionally, image background reloading was implemented in Latest data, graphs and slideshows. This should result in a better user experience and reduced network traffic for all of these pages. 8.1.2 Displaying

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation going from 1 to 5 average result would be 1. This has been changed to keep the sum of the values and only compute the average when storing it in the database. Note that the result is still stored as an integer elements, a new Application field is available for entering the required application name: 20 The result can be a very neat and concise screen element for viewing in Monitoring → Screens: 5.24.8 Ability

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation encountered problems with a number of devices that did not respond to these requests as expected. As a result, SNMP bulk processing has been made optional in Zabbix 2.4.0. Enabled by default, it can be disabled testing with zabbix_agentd -p and zabbix_agentd -t now also provides a detailed error message. As a result, in Configuration → Hosts → Items of the frontend, when rolling the mouse over the error icon, you

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation 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 was a significant 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 agent must first retrieve a list of items from

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation implemented allowing to cache the result of calculated trend functions. Zabbix server, when processing trend functions, will check the trend cache for the cached result. In case of failure the server will will read data from database and cache the result. 13 The trend function cache may help to decrease the database server load when triggers contain trend functions mixed with history or timer-based functions

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation executed steps, reporting on the result or failure of each preprocessing step. Preprocessing failed for: 1. Result (): 2. Result (): Expected format change in low-level discovery In order to support preprocessing of low-level discovery result and custom paths to low-level discovery (LLD) macro values in a JSON document, the format of JSON

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: Tag Branch Version Result 4.0.8 Zabbix 4.0.8 4.0.8.2400 release/4.0 Zabbix 4.0.8rc3 4.0.8.1303 feature/ZBX-16074 Zabbix discovery VMware datastore discovery has been moved from hypervisor level to vCenter level. As a result datastores are discovered and datastore info is collected only once for each datastore instead of

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation processing of trigger prototypes has been optimized by reducing the number of SQL statements. As a result, the process of creating triggers takes only half of the time as before. 5.10 Multiple OID support The global script result window has regained a header with the script name. Information about the executed command is now displayed as well. Script result in 3.0.0 Script result in 3.0.3 1.2 Updated

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation As all new lines must be analyzed by Zabbix and the matching lines sent to Zabbix server, it may result both in serious delays and a large number of identical messages sent and stored in the database display problems and their resolution in one line. More events in less space can be displayed as a result. |<| |<| |<| |-| |<| Similarly, the history of events, available as a screen element, now displays

• you can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result. 26 Active checks require more complex processing. The agent must first retrieve a list of items embedded script testing. This utility will execute a user script with a string parameter and print the result. Scripts are executed using the embedded Zabbix scripting engine. In case of compilation or execution