1.x, Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix 1.8. It does not require any configuration changes on agent side. Warning: Older Zabbix proxies of version 1.6.x can’t be used with Zabbix 1 3.6 Upgrade procedure The following steps have to be performed for successful upgrade from Zabbix 1.6.x to 1.8. The whole upgrade procedure may take several hours depending on size of Zabbix database Database upgrade is a required step when upgrading from one major Zabbix version to another, such as from 1.6 to 1.8. It is not required for minor upgrades, such as from 1.8.x to 1.8.x, unless specifically stated

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions upgrading Zabbix 1.8.x to 2.0! For upgrading from earlier versions first use upgrade scripts from Zabbix 1.6.x or Zabbix 1.8.x. 7 Install new Zabbix web interface 60 Follow installation instructions. 8 Start they have to be converted manually. 9 Upgrade notes for proxies Warning: Older Zabbix proxies (1.6 and 1.8) cannot be used with Zabbix 2.0 server; similarly, a Zabbix 2.0 proxy cannot be used with

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like work as expected for counters that require more that one sample - like CPU utilisation. Since 1.6 interval is used, so the check returns an average value for last ”interval” seconds every time

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like work as expected for counters that require more that one sample - like CPU utilisation. Since 1.6, interval is used, so the check returns an average value for last ”interval” seconds every

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions /usr/share/zoneinfo to /etc/localtime, for example: cp /usr/share/zoneinfo/Europe/Riga /etc/localtime 1.6 Locale changes The appliance contains a few locale changes: • Contains languages: en_US.UTF-8, ru_RU value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions /usr/share/zoneinfo to /etc/localtime, for example: cp /usr/share/zoneinfo/Europe/Riga /etc/localtime 116 1.6 Locale changes The appliance contains a few locale changes: • Contains languages: en_US.UTF-8, ru_RU value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions /usr/share/zoneinfo to /etc/localtime, for example: cp /usr/share/zoneinfo/Europe/Riga /etc/localtime 1.6 Locale changes The appliance contains a few locale changes: • Contains languages: en_US.UTF-8, ru_RU value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions /usr/share/zoneinfo to /etc/localtime, for example: 113 cp /usr/share/zoneinfo/Europe/Riga /etc/localtime 1.6 Locale changes The appliance contains a few locale changes: • Contains languages: en_US.UTF-8, ru_RU value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like work as expected for counters that require more that one sample - like CPU utilization. Since 1.6, interval is used, so the check returns an average value for last ”interval” seconds every time

Java gateway compiles and runs with Java 1.6 and above. It is recommended that those who provide a precompiled version of the gateway for others use Java 1.6 for compilation, so that it runs on all versions value is 1. Performance Monitor can be used to obtain list of available counters. Until version 1.6 this parameter will return correct value only for counters that require just one sample (like work as expected for counters that require more that one sample - like CPU utilisation. Since 1.6, interval is used, so the check returns an average value for last ”interval” seconds every time