{b}{t}{nn} format where: • {b} - source (1 - feature or release, 2 - tag) • {t} - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: example: Tag Branch Version Result 3.0.28 Zabbix 3.0.28 3.0.28.2400 release/3.0 Zabbix 3.0.28rc3 3.0.28.1303 feature/ZBX-16074 Zabbix 3.0.28rc1 3.0.28.1301 34 What’s new in Zabbix 3.0.29 This minor version com/scm/zbx/zabbix.git $ cd zabbix $ git checkout 3.0.31 -b 3.0.31 # replace 3.0.31 with the latest release available $ ./bootstrap.sh $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd` $ make dbschema

are different: {Local Zabbix server:vfs.file.contents[/etc/os-release].last()}<>{Remote Zabbix server:vfs.file.contents[/etc/os-release].last()} String comparison is also possible in calculated items with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example x86_64-8.1.0- release-win32-sjlj-rt_v6-rev0.7z) 2. Extract and move to c:\mingw 3. Setup environmental variable @echo Build agent without TLS: $ cd zabbix/ $ git checkout 5.0.1 -b 5.0.1 # replace 5.0.1 with the latest release available $ ./bootstrap.sh $ ./configure --sysconfdir=/usr/local/etc/zabbix --enable-agent --enable-ipv6

Currently Agent 2 is in experimental status, with a production-ready status expected in the next major release. See also: Zabbix agent 2 Webhooks in alerting In the new version you may write your own JavaScript MinGW-w64 with SJLJ (set jump/long jump) Exception Handling and Windows threads (look for x86_64-8.1.0-release- win32-sjlj-rt_v6-rev0.7z) 2. Extract and move to c:\mingw 3. Setup environmental variable @echo com/scm/zbx/zabbix.git $ cd zabbix $ git checkout 4.4.10 -b 4.4.10 # replace 4.4.10 with the latest release available $ ./bootstrap.sh $ ./configure --sysconfdir=/usr/local/etc/zabbix --enable-agent --enable-ipv6

{b}{t}{nn} format where: • {b} - source (1 - feature or release, 2 - tag) • {t} - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: example: Tag Branch Version Result 4.2.2 Zabbix 4.2.2 4.2.2.2400 release/4.2 Zabbix 4.2.2rc3 4.2.2.1303 feature/ZBX-16074 Zabbix 4.2.2rc1 4.2.2.1301 8 What’s new in Zabbix 4.2.3 This minor version contains zabbix.com/zabbix/4.2/rhel/7/x86_64/zabbix-release-4.2-2.el7.noarch.rpm RHEL 6: # rpm -Uvh https://repo.zabbix.com/zabbix/4.2/rhel/6/x86_64/zabbix-release-4.2-2.el6.noarch.rpm RHEL 5: # rpm -Uvh https://repo

zabbix.com/zabbix/3.4/rhel/7/x86_64/zabbix-release-3.4-2.el7.noarch.rpm RHEL 6: # rpm -ivh https://repo.zabbix.com/zabbix/3.4/rhel/6/x86_64/zabbix-release-3.4-1.el6.noarch.rpm RHEL 5: # rpm -ivh https://repo https://repo.zabbix.com/zabbix/3.4/rhel/5/x86_64/zabbix-release-3.4-1.noarch.rpm Frontend installation prerequisites Zabbix frontend requires additional packages not available in basic installation. You wget https://repo.zabbix.com/zabbix/3.4/debian/pool/main/z/zabbix-release/zabbix-release_3.4-1+stretch_all.deb # dpkg -i zabbix-release_3.4-1+stretch_all.deb # apt update For Ubuntu 18.04 (bionic), run

Bulgarian 10.1.2 Completed translations The following translations are 100% completed for this release: • American English • Brazilian Portuguese • French • German • Greek • Japanese • Portuguese Lithuanian 11.2.2 Completed translations The following translations are 100% completed for this release: • American English • Brazilian Portuguese • French • German • Greek • Japanese • Russian improvements 12.1.1 Completed translations The following translations are 100% completed for this release: • American English • Brazilian Portuguese • French • German • Greek • Japanese • Russian

packages have been renamed by adding a ”release” word in the name: Naming Package name Old zabbix-agent-6.0.7-1.el9.x86_64.rpm New zabbix-agent-6.0.8-release1.el9.x86_64.rpm There is no functional this change. This is necessary as preparation for providing packages of minor version (i.e. 6.0.x) release candidates, expected to start with 6.0.9. The naming change will ensure that for someone who has version of Zabbix 6.0. Note that source code repository for each plugin now contains a dedicated release/6.0 branch (previously, there was only master branch). MariaDB 10.10 support The maximum supported

{b}{t}{nn} format where: • {b} - source (1 - feature or release, 2 - tag) • {t} - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: 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 4.0.8rc1 4.0.8.1301 14 What’s new in Zabbix 4.0.9 This minor version does com/scm/zbx/zabbix.git $ cd zabbix $ git checkout 4.0.22 -b 4.0.22 # replace 4.0.22 with the latest release available $ ./bootstrap.sh $ ./configure --enable-agent --enable-ipv6 --prefix=`pwd` $ make dbschema

with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example x86_64-8.1.0- release-win32-sjlj-rt_v6-rev0.7z) 2. Extract and move to c:\mingw 3. Setup environmental variable @echo repositories. 66 1 Red Hat Enterprise Linux and derivatives Overview Official Zabbix 6.5 PRE-RELEASE packages for Red Hat Enterprise Linux versions 6, 7, 8, and 9, as well as for versions 8 and 9 of Rocky Linux are available on Zabbix website. Packages for Zabbix 7.0 will be available upon its release. Packages are available with: • MySQL or PostgreSQL database • Apache or Nginx web server support

immediate item value checks by outdated proxies that are no older than Zabbix server previous LTS release version. Older proxies are not supported, and all communication with Zabbix server will fail with with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example x86_64-8.1.0- release-win32-sjlj-rt_v6-rev0.7z) 2. Extract and move to c:\mingw 3. Setup environmental variable @echo files. SLES 15: # rpm -Uvh --nosignature https://repo.zabbix.com/zabbix/6.4/sles/15/x86_64/zabbix-release-6.4-1.sles15.noarch.rpm # zypper --gpg-auto-import-keys refresh 'Zabbix Official Repository' SLES