Skip to content
Knowledge Hub/Article
Article

Zabbix 8.0 LTS: What Changed and Who Should Upgrade?

Zabbix 8.0 LTS is out, with OpenTelemetry, ClickHouse and an MCP server for AI agents. Who should upgrade, when, and how to prepare.

Oğuzhan Gerçek··4 min read
View on LinkedIn

Short answer: Zabbix 8.0 is the new long-term support (LTS) release, published on November 5, 2026. It brings metrics, logs and traces into one platform through OpenTelemetry, and adds ClickHouse support for history data, complex event processing to cut unnecessary alerts, and an official MCP server that connects AI agents to Zabbix. Full support runs until November 30, 2029. If you are on Zabbix 6.0, support ends completely on February 28, 2027, so the upgrade needs planning now.

What is Zabbix?

Zabbix is an open source monitoring platform that watches servers, network devices, virtual machines, applications and cloud services from one place. It collects measurements, raises an alert when a threshold is crossed, routes the alert to the right person and shows history in graphs.

Until now, Zabbix was strongest on infrastructure: servers, network, storage. Seeing inside the application usually meant running a separate tool next to it. 8.0 is the release that tries to close that gap.

What changed in 8.0?

Zabbix presents this release as "unified observability": a move from classic monitoring to observability. The main changes:

  • Metrics, logs and traces together with OpenTelemetry. The Zabbix proxy now includes an OpenTelemetry collector. Traces from applications can be viewed in the frontend, and telemetry can be queried with the new "Telemetry query" item type. For teams that watch the application side (APM) and the infrastructure in separate tools, this is the biggest change.
  • ClickHouse for history data. History can now be stored in ClickHouse, and ClickHouse clusters are supported. Supported ClickHouse versions range from 26.3 to 26.9.
  • Complex event processing (CEP). Events can be filtered, correlated, grouped and prioritized. The aim is to keep one failure from arriving as many separate alerts.
  • An official MCP server for AI agents. AI agents can connect to Zabbix over the Model Context Protocol: they can analyze collected data and event history, manage problems, and help reduce alert noise and find root causes. Agents stay within the user's existing permissions and roles.
  • Performance and security. There are performance and scalability improvements for large, data-intensive environments. On security, API access is now turned off by default for user roles, and AppRole authentication was added for HashiCorp Vault.
  • New templates. Ready-made templates arrived for Kubernetes, Proxmox (with OpenTelemetry), Microsoft Hyper-V, Podman, MariaDB, Percona and Google Cloud Storage.

Support calendar: who should upgrade, and when?

Zabbix LTS releases get five years of support: three years of full support, then two years of limited support covering critical fixes only. Standard releases are supported for much less. According to the calendar Zabbix publishes:

  • Zabbix 6.0 LTS: Full support ended on February 28, 2025, and limited support ends on February 28, 2027. This is the first item on the agenda.
  • Zabbix 7.4: Full support ended on November 12, 2026, and limited support runs until May 31, 2027. The upgrade should fit into the first half of 2027.
  • Zabbix 7.0 LTS: Full support until June 30, 2027, limited support until June 30, 2029. No rush; plan the upgrade if you need features such as OpenTelemetry or CEP.
  • Zabbix 8.0 LTS: Full support until November 30, 2029, limited support until November 30, 2031.

Check before you upgrade

  1. Take an inventory. Your version, database, number of proxies, custom templates and the integrations that use the Zabbix API.
  2. Confirm requirements in the official documentation. Make sure your database and operating system versions are supported on 8.0. Read the upgrade notes of the releases in between as well.
  3. Test integrations that use the API. In 8.0, API access is turned off by default for user roles. Check the roles of your integration users.
  4. Rehearse. Run the upgrade on a copy of the production database, measure how long it takes and write down the rollback steps.
  5. Turn on new features later. Move the version first, then enable OpenTelemetry, ClickHouse and CEP in separate steps. If one step causes a problem, you will not have to hunt for its source.

Zabbix at Eclit

In Eclit's 24/7 monitoring and NOC service we work with your existing tool: Zabbix, Prometheus, Grafana, PRTG and vendor tooling. Configuring the existing tool properly usually produces results faster than replacing it. We explained who receives a night-time alert, and under which rule, in our NOC article, and how to deal with alert noise in our observability article.

If you are planning the move to Zabbix 8.0, let's talk.

Frequently asked questions

When was Zabbix 8.0 released? On November 5, 2026. 8.0 is a long-term support (LTS) release of Zabbix.

How long is Zabbix 8.0 supported? Full support until November 30, 2029, and limited support, covering critical fixes only, until November 30, 2031.

When does Zabbix 6.0 support end? On February 28, 2027. Full support already ended in 2025; after this date no fixes are released for 6.0.

Sources