Learn Zabbix - Modern Features & Roadmap

#Introduction

After episode 20 looked ahead through OpenTelemetry, episode 21 maps out Zabbix's entire release landscape: what's running, what's newest, and where development is heading. Understanding the release policy helps you decide which version to use in production and when to upgrade.

As of the writing of this series, three tracks coexist: 7.0 LTS as the long-term stable branch, 7.4 as the latest standard release, and 8.0 LTS being prepared. This episode dissects the capabilities of each and how to plan your release journey.

#Zabbix 7.0 LTS: The Long-Term Stable Branch

#Cloud-Native Proxy Scaling

Zabbix 7.0 introduced the cloud-native proxy — the ability to run a proxy as a horizontally scalable container workload. This addresses the needs of Kubernetes deployments and ephemeral environments: proxies can be added or removed according to collection load.

Cloud-native proxies can also run without a local database — data is forwarded directly to the central server. This configuration is ideal for workloads that are temporary and shouldn't leave data traces on disk.

Check the agent2 version for cloud support

zabbix_agent2 --version

The command zabbix_agent2 --version shows the agent2 version along with the list of loaded plugins. An agent2 version aligned with the server version is a prerequisite for taking advantage of new collection-side features.

#Website Transaction Monitoring

A feature directly useful for business: website transaction monitoring. Zabbix 7.0 can simulate user steps on a website — login, navigation, transactions — and monitor the response time and success of each step. This goes deeper than a mere HTTP agent checking a single endpoint.

Transactions are configured as steps that follow a user flow: open a page, wait for an element to appear, fill in an input, and check the final result. Each step has its own timeout and success condition. When one step fails, Zabbix marks the whole transaction as a problem and records which step failed — far more useful information than simply knowing the website is down.

#Event-Driven and API Enhancements

The 7.0 branch keeps receiving API improvements and event-driven capabilities that refine the automation from episode 14. Its long-term support is also clear: active support until June 2027 and security support until June 2029 — the reason 7.0 became the primary production choice in this series.

The combination of API improvements and event-driven capabilities strengthens Zabbix's position as a platform that can be fully controlled from code, not just from clicks in the frontend.

#Zabbix 7.4: Less Work, More Depth

#The Spirit of the 7.4 Update

The standard 7.4 release champions the spirit of "less work, more depth" — less manual work, deeper results. Updates focus on everyday usability: simplifying frequently repeated configuration flows and deepening analysis capabilities without adding complexity.

Because standard releases ship more often, 7.4 features preview the development direction that will land in the next LTS. Following the standard branch also builds the habit of regular upgrades rather than big, accumulated ones. Check the 7.4 release notes if you plan to use a specific feature — some become the foundation inherited by the next LTS release.

#Support and Migration

As a standard release, 7.4 has no long support window — support ends September 2026. For those following the standard branch, plan a migration to 8.0 LTS or 7.0 LTS before that date. This policy reinforces the lesson from episode 1: for production, LTS is always the primary home.

Zabbix version numbering follows the major.minor.patch scheme: the patch number marks fixes and security updates within the same branch. Updating patches regularly is part of security — many serious fixes are only available through the latest patch version, and postponing patch upgrades means leaving known holes open.

#Zabbix 8.0 LTS and the Roadmap

#Key Features of 8.0

Zabbix 8.0 LTS, scheduled for release in Q3 2026 and currently in beta, brings three things already mentioned in episode 20:

OpenTelemetry integration: accepting metrics, logs, and traces from the OTel ecosystem.
Mobile app: a new mobile application for field operations.
Modernized core: an update to the data and event processing foundation.

These features are still being refined in the beta version, and details may change before the final release. What's certain is that the direction is consistent with Zabbix's vision as an increasingly unified observability platform.

#The 8.2 Roadmap

After 8.0 LTS, the official roadmap points to 8.2 in Q1 2027 as the next standard release. This follows Zabbix's rhythm: LTS provides stability, standard releases provide innovation. Standard releases like 8.2 are a window to sample features before they're adopted into the next LTS.

2026-2027 release timeline

7.0 LTS   → active until Jun 2027, security until Jun 2029
7.4       → support until Sep 2026
8.0 LTS   → release Q3 2026 (currently beta)
8.2       → planned Q1 2027

The timeline above is a decision map: stay on 7.0 LTS for the next few years, or move to 8.0 LTS when it feels mature. Both are valid depending on your organization's risk profile. Note that support dates can change — always verify on the official lifecycle page or endoflife.date/zabbix.

Tip

Don't chase the newest release for prestige. Read the release notes of each version, check for features that actually solve your problems, and let a new LTS run its first few months in the field before using it for critical production.

#Building a Release Strategy

How to build a healthy version policy:

Production: 7.0 LTS as the default, with scheduled patch upgrades.
Staging: the newest version that will be the next migration target.
Experimentation: the standard or beta branch for learning features.
Schedule: LTS-to-LTS migrations at least once a year with a full backup.

With this strategy, you get LTS stability without losing visibility into where Zabbix is heading.

Patch upgrade on the 7.0 LTS branch

apt update
apt install --only-upgrade zabbix-server-mysql zabbix-frontend-php

The command apt install --only-upgrade zabbix-server-mysql only updates Zabbix packages to the latest patch on the same branch, without moving major versions. This routine keeps security support without the risk of a big migration. Before any upgrade, make sure: the database backup is valid, the target version is compatible with the configuration, and there's a rollback path — following the official per-version upgrade guides avoids surprises from schema changes.

#Closing

Episode 21 mapped the release landscape: 7.0 LTS with cloud-native proxy and website transactions as the production choice, 7.4 with the "less work, more depth" spirit ending September 2026, and 8.0 LTS bringing OpenTelemetry in a roadmap headed toward 8.2.

Key takeaways:

7.0 LTS is the production branch with support until 2029.
Cloud-native proxy enables horizontal scaling in container environments.
Website transaction monitoring simulates real user flows.
7.4 ends September 2026; prepare a migration to 8.0 or 7.0 LTS.
The roadmap continues to 8.2 in Q1 2027.

In episode 22, the final episode, we'll discuss the ecosystem, alternatives, and final reflection — comparing Zabbix with Prometheus, Grafana, Nagios, and Datadog, when to choose which, plus a full series recap with a production checklist and learning resources.