[email protected]

Zabbix 8.0 LTS: What's New, Support Dates and Upgrading from 7.0

Zabbix 8.0 LTS: What's New, Support Dates and Upgrading from 7.0

Editorial note: The information in this article was compiled to the best of our knowledge at the time of publication. Technical details, prices, versions, licensing terms, and external content may change. Please verify the information provided independently, particularly before making business-critical or security-related decisions. This article does not replace individual professional, legal, or tax advice.

Zabbix operations and upgrades by WZ-IT - We check your installation, plan the upgrade to 8.0 LTS and keep running Zabbix for you if you wish. Book an intro call · Monitoring operations

On 5 November 2026 Zabbix released version 8.0 LTS. It succeeds 7.0 LTS and brings ClickHouse as an additional history backend, application performance monitoring based on OpenTelemetry, an MCP server for AI assistants and new minimum versions for database and PHP. A direct upgrade from 7.0 is possible, provided the database is not Oracle. This article summarizes what is new, how long each version is supported and what to watch when upgrading from 7.0.

Table of contents

Short answer

Question Answer
Release Zabbix 8.0.0 LTS on 5 November 2026 (release notes)
Support Full support until 30 Nov 2029, limited support until 30 Nov 2031 (lifecycle)
Upgrade path Direct from any version starting at 2.0.x (upgrade docs)
New ClickHouse as history backend, OpenTelemetry APM, complex event processing, MCP server, dark blue theme
Minimum versions PHP 8.2, PostgreSQL 15, MySQL 8.4, MariaDB 10.11, TimescaleDB 2.20, Elasticsearch 8
Watch out for Oracle unsupported since 7.2, API access, TLS verification in HTTP templates, removed macros and API methods

Support periods at a glance

The Zabbix lifecycle page lists these periods for the current versions (as of 18 November 2026):

Version Release End of full support End of limited support
8.0 LTS 05 Nov 2026 30 Nov 2029 30 Nov 2031
7.4 01 Jul 2025 12 Nov 2026 (ended) 31 May 2027
7.0 LTS 04 Jun 2024 30 Jun 2027 30 Jun 2029
6.0 LTS 08 Feb 2022 28 Feb 2025 (ended) 28 Feb 2027

Two conclusions: if you still run 6.0 LTS, limited support ends on 28 February 2027, so plan the move straight to 8.0 now; a direct upgrade from 6.0 is supported. If you are on 7.4, full support ended on 12 November 2026 and limited support runs only until 31 May 2027. For 7.0 LTS, full support continues until mid-2027, so the move can be planned rather than rushed.

Key new features

According to the release notes and the what's new page, these are the focus areas:

Area New
Data storage ClickHouse as additional history backend (not for proxy history) with cluster support; Elasticsearch 8.x and 9.x; TimescaleDB 2.20 to 2.29 in 8.0.0
Application performance monitoring (APM) OpenTelemetry collector in the proxy (OTLP/gRPC), trace visualization, new "Telemetry query" item type for triggers, graphs and discovery; ClickHouse serves as the data source
Event processing Complex event processing: rules with time windows and conditions to group, enrich, suppress or limit events
AI integration MCP server (Model Context Protocol): AI assistants connect with an API token and see only what the token owner may see; changes are recorded in the audit log
Frontend Dark blue theme, dashboard import and export, scatter plot widget, customizable tables, CSV export of the audit log, inline form validation
Templates New or updated for Proxmox, Kubernetes, Envoy, GCP, Oracle Cloud, MariaDB, Percona, Podman, OpenAI and Claude API, among others
Security Proxy and proxy group visibility by permission, HashiCorp Vault AppRole, SAML signing enabled by default (new configurations)
Agents New item vfs.dev.get, new parameters mode and mountpoint for vfs.fs.get, filters via AllowKeyRegexp and DenyKeyRegexp, c-ares for DNS (optional, when built with --with-ares)
Mobile Server-side components for the Zabbix app (device management, push media type, bridge adapter); the app itself is "coming soon" per the docs

For operators who run Zabbix and a separate tracing service today, the combination of proxy collector, ClickHouse and the APM menu is the main addition. Whether it replaces a dedicated tracing stack depends on scale; APM is new in 8.0 and should first be tested in a staging environment.

New minimum versions

The upgrade notes raise the requirements:

Component Before (7.0) From 8.0
PostgreSQL 13.0 15.0
MySQL / Percona 8.0.30 8.4.0
MariaDB 10.5.00 10.11.00
TimescaleDB 2.13.0 2.20.0
Elasticsearch 7.0.0 8.0.0
PHP (frontend) 8.0 8.2

With Elasticsearch, the server refuses to start if the version is older than 8.0.0, and AllowUnsupportedDBVersions does not override this. Elasticsearch must therefore be updated before the new server starts. For MySQL, Zabbix explicitly recommends converting a schema using utf8mb3 and utf8mb3_bin to utf8mb4 and utf8mb4_bin beforehand.

Changes that affect upgrades

Change Consequence for you
API access off by default (new installation: all roles; existing installation: newly created roles); empty allow list blocks all methods Review roles used by integrations. On upgrade, roles with an empty list receive the entry * (all methods allowed); replace it with the methods needed
TLS verification for HTTPS in templates and media types Untrusted self-signed and expired certificates cause errors; self-signed certificates work if the CA is in the trust store. Control via {$HTTP.TLS.VERIFY}; templates must be updated manually
API methods removed in 8.0: host.massupdate, template.massupdate, hostgroup.massupdate and hostinterface.create, update, delete, massadd and massremove Adjust your own scripts and automation
Removed deprecated macros, e.g. {IPADDRESS}, {HOSTNAME}, {STATUS}, {USER.ALIAS} Check notification texts and actions
Legacy protocols removed from the trapper; agents older than 1.6 no longer supported Replace very old agents beforehand
HTTP agent items: JSON and XML validation of the "Request body" field in the form removed Review configurations with a request body
Kubernetes templates marked deprecated Move to Kubernetes Cluster by HTTP and Kubernetes Node by HTTP

This list is an excerpt. When jumping from 7.0, the cumulative notes of the skipped versions 7.2 and 7.4 also apply: 7.2 removed the Oracle backend, and there are further API changes. The full lists are in the release notes, the 8.0 upgrade notes, the 7.2 upgrade notes and the API change pages for 7.4 and 8.0.

Upgrading from 7.0 to 8.0: order of steps

The upgrade documentation describes this order:

  1. Preparation: back up the database and configuration; bring database, PHP and, if used, Elasticsearch to the new minimum versions. A proxy using SQLite deletes an older database file and creates it anew; its history is lost in the process. You can copy the old file beforehand for archiving.
  2. Server: stop, update packages, start. The database migration can take long on large databases.
  3. Proxies: stop, update, start one at a time. Running proxies keep collecting while the server is down.
  4. Agents: recommended, not mandatory.
  5. Follow-up: review API roles, templates with HTTPS queries, macros and scripts.

Proxies of the previous LTS release work with a new server only in a limited mode: data collection, remote commands and immediate item checks work, configuration changes no longer arrive. They are not meant for long-term operation; update proxies promptly.

When the move makes sense

The timing is our recommendation based on the lifecycle table, not a vendor requirement.

  • Plan now: installations on 6.0 LTS (limited support ends 28 Feb 2027) and on 7.4 (full support ended).
  • Spring to summer 2027: installations on 7.0 LTS. Full support runs until 30 June 2027; use the time for a test run of the database updates and API integrations.
  • New installations: 8.0 LTS directly, with PostgreSQL 15, MySQL or Percona 8.4 or MariaDB 10.11, in each case within the upper limits of the requirements table.
  • Only after a test run: APM with ClickHouse and the MCP server. Both are new; check permissions and load in a staging environment first.

Status and methodology

As of 18 November 2026, 13 days after the release of 8.0.0. The basis is the Zabbix release notes, lifecycle page and upgrade documentation. Statements on proxy compatibility come from the upgrade documentation; the mapping "previous LTS = 7.0" follows from the lifecycle table. On the cut-off date only 8.0.0 is published; for production systems the current patch level in the release notes applies.

Our approach at WZ-IT

  1. Take stock: record Zabbix version, database, PHP, proxies, agents and API integrations.
  2. Compare: check the inventory against the minimum versions and removed features, and list deviations.
  3. Test run: restore a copy of the database on a test system, run the migration and templates.
  4. Upgrade: in the agreed window, update server, proxies and agents in sequence, then follow-up and functional check.
  5. Operations: on request, take over updates, monitoring of the monitoring and alerting long term (Zabbix operations, monitoring).

Further guides

Have your Zabbix upgrade checked: We compare your installation with the 8.0 requirements and discuss the approach. Book an intro call

Sources

Timo Wevelsiep

Written by

Timo Wevelsiep

Co-Founder & CEO

Co-Founder of WZ-IT. Specialized in cloud infrastructure, open-source platforms and managed services for SMEs and enterprise clients worldwide.

Frequently Asked Questions

Answers to important questions about this topic

Customers from mid-sized business, industry and the public sector, in Germany and internationally

  • Stadtwerke Brühl
  • DGHO e.V.
  • solarwerkstatt berlin
  • Krüger Dirndl
  • ABCO Water Systems
  • Golem.de
  • EVADXB
  • nextGYM
  • AInergy
  • ml&s
  • Odiseo Solutions
  • Annota
  • ARGE
  • SweetConnect GmbH
  • Aphy AG
  • CORGOS
  • Rekorder
  • SolidProof
  • Yonju
  • Keymate
  • Paritel
  • Mr. Clipart
  • Millenium
  • Negosh
  • Führerscheinmacher
  • BTI
  • Deutsche Gesellschaft für Datenschutz
Read client reviews

Enquiry

Move Zabbix to 8.0 LTS

We check your installation against the new minimum versions, plan the order of server and proxies and carry out the upgrade.

  • You speak directly with Timo and Robin, who are technically responsible
  • A professional assessment of your situation
  • Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
Timo and Robin, founders of WZ-IT

What does your setup need?

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH