Server monitoring with Zabbix: what does Zabbix 7.0 LTS bring?

Zabbix is one of the most widely used open-source server monitoring systems: it watches the state of servers, network devices, virtual machines and applications, collects data about them, and tells you when something is wrong – ideally before your clients notice. Zabbix 7.0 LTS, the long-term supported version for the coming years, was released on 4 June. In this article we look at how a Zabbix system is put together, what 7.0 brings, and how to get started.

Why do you need monitoring?

The worst way to find out about an outage is from a client. The point of monitoring is to spot most problems before they turn into a service outage: the disk that is filling up, the certificate that is about to expire, the memory that is slowly running out, the failing disk in a RAID array. We wrote about the real cost of outages in an earlier article.

Good basic monitoring covers at least the following:

  • availability: does the machine respond (ping), are the web server, the database and email running;
  • resources: CPU, memory, disk space, disk I/O, network traffic;
  • services: HTTP response code and response time, SSL certificate expiry, the mail queue;
  • hardware: SMART status of disks, RAID, power supplies, temperature (via IPMI or SNMP);
  • backups: did the nightly backup run, and how big was it.

How is Zabbix structured?

Component What it does
Zabbix server Collects and processes the data, evaluates the alert conditions (triggers), sends notifications
Database MySQL, MariaDB or PostgreSQL (also with TimescaleDB); this is where the configuration and the measured data are stored
Web interface PHP-based interface for settings, graphs and dashboards
Zabbix agent / agent 2 Runs on the monitored machine and collects data locally; agent 2 is written in Go and supports plugins
Zabbix proxy Collects data at a remote site or in a remote network and forwards it to the server

A lot can be measured without an agent too: switches, routers and printers over SNMP, server hardware over IPMI, websites with HTTP checks, and there are ready-made templates for VMware, cloud services and databases as well. Zabbix works with templates: a Linux server template brings the values to measure, the alert conditions and the graphs all at once.

What’s new in Zabbix 7.0 LTS?

The most important of the new features in version 7.0:

  • Proxy groups: high availability and load balancing. Hosts can be assigned to proxy groups, and if a proxy fails, the other members of the group automatically take over its hosts. Until now, this needed external tools or manual switchover.
  • Browser (synthetic) monitoring. A new item type lets you write multi-step browser scenarios (logging in, adding to the basket, paying), which Zabbix runs through a Selenium WebDriver, with screenshots and timing.
  • Asynchronous pollers. Agent, SNMP and HTTP checks are performed by asynchronous processes, and one process runs many checks at the same time. On large systems this means the same number of measurements with far fewer resources.
  • Per-item timeouts. The timeout is no longer a global setting: it can be set per item or per proxy, so you don’t have to raise it for everything because of one slow query.
  • Memory buffer for proxies. The proxy can buffer the collected data in memory instead of on disk, which is faster.
  • Multi-factor authentication. Users can log in to the web interface with TOTP (for example, an authenticator app) or with Duo.
  • New dashboard widgets. Gauge, pie and donut charts, a honeycomb view, and host and item navigators, and widgets can also pass data to each other.
  • Licence. From 7.0, Zabbix uses the AGPLv3 licence instead of the earlier GPLv2. For your own internal use, this changes nothing.

How long is it supported?

According to the Zabbix life cycle policy, LTS versions get three years of full support and two years of limited support (critical fixes only):

Version Release End of full support End of limited support
Zabbix 6.0 LTS 8 February 2022 28 February 2025 28 February 2027
Zabbix 7.0 LTS 4 June 2024 30 June 2027 30 June 2029

For production systems we recommend an LTS version; the intermediate (standard) releases only get fixes for a short time.

Installing Zabbix agent 2 on Debian 12

It’s best to install from Zabbix’s own repositories, because the distributions’ packages are usually older. On Debian 12:

wget https://repo.zabbix.com/zabbix/7.0/debian/pool/main/z/zabbix-release/zabbix-release_7.0-1+debian12_all.deb
sudo dpkg -i zabbix-release_7.0-1+debian12_all.deb
sudo apt update
sudo apt install zabbix-agent2 zabbix-agent2-plugin-*

On Ubuntu (there is already a package for 24.04 too) and on AlmaLinux and Rocky Linux the steps are similar; the Zabbix download page gives the exact commands for each operating system.

Then set the server address and the host name in /etc/zabbix/zabbix_agent2.conf:

Server=192.0.2.10
ServerActive=192.0.2.10
Hostname=web01.example.com
sudo systemctl restart zabbix-agent2
sudo systemctl enable zabbix-agent2

For passive checks, the server has to reach the agent on TCP port 10050; for active checks, the agent has to reach the server on port 10051. On the firewall, open these only for the address of the Zabbix server (or proxy); you can read about writing firewall rules in the knowledge base of aWh, our hosting brand. If the traffic goes over a public network, turn on encryption (with a pre-shared key or a certificate).

Finally, add the host in the web interface and link the “Linux by Zabbix agent” template to it.

Upgrading from 6.0 LTS

Full support for 6.0 LTS lasts until February 2025, so there is no need to rush, but it’s worth planning the move for this year. Before you start:

  1. Check the requirements. 7.0 needs at least PHP 8.0, MySQL 8.0.30, MariaDB 10.5 or PostgreSQL 13. On an older operating system, this alone can mean an upgrade.
  2. Back up. Make a backup of both the database and the configuration files (/etc/zabbix/). Zabbix server upgrades the database schema the first time it starts, and with a large database this can take a long time.
  3. Upgrade the proxies together with the server. Proxies on an older version only work with the new server to a limited extent.
  4. The agents can wait. Older Zabbix agents also work with the new server, so you can replace them gradually.
  5. Try it first. With a large system, it’s worth upgrading a copy first, to see how long it takes and whether your own templates work.

Monitoring is one of the foundations of infrastructure reliability: anything you don’t measure, you only find out about once something has already gone wrong. We help with installing Zabbix systems, setting up templates and alerts, and with operations built on those alerts; you can read about this on the Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch