Zabbix 7.4 full support ends 12 November as 8.0 LTS raises its minimums

Zabbix 7.4 full support ends 12 November as 8.0 LTS raises its minimums

5 November 2026: Zabbix released version 8.0 LTS on 5 November, and that moves every older branch further along its support table. The nearest date is days away: full support for Zabbix 7.4 ends on 12 November 2026. Moving to 8.0 is not a simple package update for many sites, because its minimum database and PHP versions have gone up.

Not yet independently verified. The lifecycle dates and upgrade notes are Zabbix's own and we found no independent report. We read the headings and the quoted parts of the long upgrade notes, not every entry, so check the full notes before upgrading. We will update this when it can be confirmed, and remove this note.

The support dates to put in the diary

Zabbix's life cycle page now shows these dates:

Version	Released	Full support ends	Limited support ends
8.0 LTS	5 November 2026	30 November 2029	30 November 2031
7.4	1 July 2025	12 November 2026	31 May 2027
7.0 LTS	4 June 2024	30 June 2027	30 June 2029
6.0 LTS	8 February 2022	Ended 28 February 2025	28 February 2027

Under the policy, full support on an LTS branch runs for about three years and includes feature updates and security fixes, and the two limited years that follow cover critical fixes only. Teams still on 6.0 have under four months of those critical fixes left.

What has to be upgraded first

The 8.0.0 release notes raise the floor on the software underneath:

• PHP: 8.2, up from 8.0.
• MySQL and Percona: 8.4, up from 8.0.30.
• PostgreSQL: 15, with TigerData, the former TimescaleDB, at 2.20.
• MariaDB: 10.11.
• Elasticsearch: 8.0. Per the notes, "Zabbix server does not start if the Elasticsearch version is older than 8.0.0."
• ClickHouse: now supported, from 26.3 to 26.9.

MySQL sites have one more job. Where the database still uses utf8mb3, Zabbix says "it is strongly recommended to convert it to utf8mb4 character set and utf8mb4_bin collation before upgrading".

API access and scripts can break

Integrations are where an upgrade is most likely to bite. On new installations, access to the API is disabled by default for all roles. Existing installations keep it, except for newly created roles. An allow list with no methods now denies everything, so the upgrade adds a wildcard to affected roles, and those should be reviewed afterwards.

The notes also remove the massupdate method for hosts, templates and their groups, and public access to host interface methods other than get. Older macros such as HOSTNAME and IPADDRESS are gone, pre-1.6 agents are no longer supported, and the proxy internal items are restricted to hosts the server monitors directly. Automation built on any of these needs testing before the switch.

What the new branch adds

The release lists native OpenTelemetry collection for metrics, traces and logs, complex event processing to cut unnecessary alerts, and an official MCP server whose access follows existing user roles. Founder and CEO Alexei Vladishev says the aim is enterprise-level observability on an open platform.

We have added Zabbix 8.0 LTS to our network monitoring software category, alongside rivals such as Nagios XI.

Sources

• Zabbix: Life cycle and release policy, read 7 November 2026, 7 November 2026
• Zabbix: release notes for 8.0.0, 5 November 2026, 5 November 2026
• Zabbix documentation: upgrade notes for 8.0.0, read 7 November 2026, 7 November 2026
• Zabbix Japan via PR TIMES: Zabbix 8.0 LTS release, 6 November 2026, 6 November 2026