in the release notes of the version. Before running upgrade scripts drop the following indexes: MySQL alter table dhosts drop index dhosts_1; alter table dservices drop index dservices_1; alter table Database upgrade scripts are located in directory upgrades/dbpatches/1.8/: • MySQL: upgrades/dbpatches/1.8/mysql/patch.sql • Oracle: upgrades/dbpatches/1.8/oracle/patch.sql • PostgreSQL: upgrades/dbpatches/1 support arrays. 6.4 Other changes • In previous versions, Zabbix server was able to reconnect to MySQL database if it temporarily became unavailable. With 1.8.2, this is also supported for PostgreSQL

French 1.2 Daemon improvements 1.3 Miscellaneous improvements Fixed issues with mysql user parameter configuration script mysql.size parameter. It con- tained a complex bash expression and was failing if Zabbix protocols) stays limited at 16MB • Zabbix server and proxy will now retry connections to MySQL if connecting to a DNS name and resolution fails • When encoding email subject from UTF-8 to Base64 1.3 Suppressed warning messages about deprecated mysql extension Before Zabbix 2.0.8, PHP version 5.5+ users would get a warning message about the mysql PHP extension being deprecated. Starting with Zabbix

indexes in Zabbix MySQL database schema ** Redundant indexes were removed in several Zabbix MySQL database tables. This should improve performance and slightly reduce the database size for MySQL users in these on child-table columns having foreign key constraints Such indexes were created automatically on MySQL, now they are created also on PostgreSQL, Oracle, DB2 to improve performance of Zabbix server and be set to 0.0001 seconds. 18.3 Miscellaneous improvements Fixed issues with mysql user parameter configuration script mysql.size parameter. It con- tained a complex bash expression and was failing if

line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations as,

will be set to 0.0001 seconds. 3 Miscellaneous improvements Fixed issues with mysql user parameter configuration script mysql.size parameter. It contained a complex bash expression and was failing if the line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m

line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations as,

line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations as,

line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m requires a separate database. Attention: Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle or IBM DB2 is at your own risk and may contain some limitations as,

• remove host • enable host • remove from host group • unlink from template MySQL 8.0 supported Support for MySQL 8.0 has been added. Date-based indices setup for Elasticsearch In order to properly about the oc- curred problem. Database down message from now on consists of the following content: [MySQL|PostgreSQL|Oracle|IBM DB2] database [on :] is not available: MySQL. Internal events can be disabled Internal events will not be created, if all internal actions for

Parameter structure for Zabbix agent 2 plugins has been updated: • For Ceph, Docker, Memcached, MySQL, Oracle, and Redis plugins, a Uri can now only be specified as a named session parameter. • For line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows it by Hostname value from the config file shell> zabbix_agentd --print shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf shell> zabbix_agentd.exe -i shell> zabbix_agentd.exe -i -m