report is on the service name), expected sla shown in black not green, more... multiple service dependencies can be selected now 5.2.19 Templated host screens Screens can be defined in templates. They Allow deleting trigger dependencies during mass update If no trigger dependencies are added and their controlling checkbox is marked in the trigger mass update, all dependencies for selected triggers 9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library (note that up to Zabbix 2.0.12 JSON

description field content is also visible in host inventory overview. 5.10.7 Trigger dependencies shown as links Trigger dependencies previously were displayed as just plain text listing of trigger names. Now the configuration. Links are green for enabled triggers, while red indicates that the trigger is disabled. Dependencies are also shown as links (in blue) in trigger configuration and mass update forms. Additionally Monitoring → Events page. • IT services in pop-up windows are now sorted by name. • IT service dependencies in the configuration window are now sorted by name. 5.11 Macro improvements User macros {$MACRO}

9 What’s new in Zabbix 2.2.4 9.1 Trigger evaluation order improved for dependencies To make sure that trigger dependencies work correctly, it is im- portant that the trigger evaluation order works would work fine regarding dependencies as long as the more important trigger was evaluated first. However, in situations where the dependent trigger was evaluated first, dependencies would not work correctly root trigger would not have been evaluated and changed to ’OK’ yet. To solve this, triggers in dependencies now are always evaluated starting with the most important first. In a ”trigger A depends on trigger

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list

displaying whether the value mapping is used in any items. 11 5.9 Dependencies between trigger prototypes While defining trigger dependencies has been a Zabbix feature for a long time, doing the same for Following a popular request, ability to define dependencies has now been implemented for trigger prototypes as well. To define dependencies you go to the Dependencies tab in the trigger prototype form (similarly 9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. 30 lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list

9.27.jar lib/logback-classic-0.9.27.jar lib/slf4j-api-1.6.1.jar lib/android-json-4.3_r3.1.jar Dependencies of Java gateway: Logback, SLF4J, and Android JSON library. lib/logback.xml lib/logback-console archive, then the necessary dependencies are already included in the source tree. If you obtained Zabbix from your distribution’s package, then the necessary dependencies are already provided by the no additional downloads are necessary. If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list