{"id":555,"date":"2026-09-06T01:17:46","date_gmt":"2026-09-06T04:17:46","guid":{"rendered":"https:\/\/www.linuxpro.com.br\/2026\/09\/a-historia-do-zabbix\/"},"modified":"2026-09-08T08:24:10","modified_gmt":"2026-09-08T11:24:10","slug":"a-historia-do-zabbix","status":"publish","type":"post","link":"https:\/\/www.linuxpro.com.br\/en\/2026\/09\/a-historia-do-zabbix\/","title":{"rendered":"The history of Zabbix: monitoring born in Riga"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" alt=\"Mascote do LinuxPro apontando para o alerta vermelho no painel de monitoramento, com o sino tocando sobre o servidor\" src=\"\/wp-content\/uploads\/2026\/09\/zabbix-historia-v2.webp\" width=\"1052\" height=\"652\" \/><\/p>\n<p>On 7 April 2001 Alexei Vladishev released Zabbix under the GPL. An internal tool became a project. The stable 1.0 arrived only on 23 March 2004. In April 2005 SIA Zabbix was born in Riga, Latvia. Twenty-one years as a company (anniversary on 12 April 2025), twenty-five years of code. On 25 August 2026, 7.4.14 and 7.0.30 LTS were released. 8.0 LTS is already in beta, with CEP, OpenTelemetry, and a new UI. The red cube on the cover bears the official wordmark: ZABBIX, #d40000, no flourishes.<\/p>\n<p><!-- more --><\/p>\n<h2>Riga, 2001: the anti-Nagios with a database<\/h2>\n<p>Vladishev did not want a plugin scheduler and a CGI. He wanted items in a database, history, graphs, triggers, and an agent on the host. Server in C, frontend in PHP, data in MySQL (later PostgreSQL, Timescale). The agent talks to the server; the server stores; the frontend reads. Active and passive checks. A proxy for networks the server cannot reach. A Java gateway for JMX. Years later, Agent2 in Go.<\/p>\n<p class=\"translation-block\"><a href=\"\/en\/2026\/09\/a-historia-do-nagios\/\">Nagios<\/a> shouted. Zabbix drew graphs. Auto-discovery and auto-registration arrived in 1.8 (December 2009). Host templates. LLD (low-level discovery) for disks, interfaces, containers \u2014 objects appear automatically. Those coming from Nagios cfg files felt the shock: here you click. Or talk to the API.<\/p>\n<p>Odd-numbered versions were development branches, even-numbered ones were stable \u2014 1.3 became 1.4. The convention lasted. 2.0 in 2012, 3.0 in 2016, 4.0 in 2018, 5.0 in 2020. The company opened offices in Japan, the US, Brazil, Mexico; in 2025, France. It acquired IZI-IT. Vladishev remains CEO.<\/p>\n<h2>6.0 and 7.0: HA, Kubernetes, AGPL<\/h2>\n<p>6.0 LTS (8 February 2022) added high-availability clustering to the server, Kubernetes monitoring, and anomaly detection with a hint of ML. 7.0 LTS (4 June 2024) was the political and technical break: the license changed from GPLv2 to <strong>AGPLv3<\/strong>. Anyone delivering Zabbix as SaaS needs to open the code or buy a license. Browser synthetic monitoring, a better API, and load-balanced proxies arrived. 7.4 (30 June 2025) is the \u201cfast\u201d stable branch; security support lasts until 31 December 2026. 7.0 LTS runs through June 2029. 6.0 LTS still receives patches \u2014 6.0.48 on 28 July 2026.<\/p>\n<h2>What Zabbix is, in one sentence<\/h2>\n<p>A metrics database with triggers. Item (the metric), host (the target), template (the blueprint), trigger (the calculation that becomes a problem), action (what to do), history\/trend (the graph). Proxy at the edge. PHP frontend. Agent on Linux, Windows, UNIX. Without Nagios's plugin-per-check model \u2014 although scripts can be called. Without <a href=\"\/en\/2026\/09\/a-historia-do-nagiosql\/\">NagiosQL<\/a>, because configuration has lived in SQL since day one.<\/p>\n<p>The Prometheus covered on this blog \u2014 <a href=\"\/en\/2026\/09\/monitorando-servidores-linux-com-prometheus\/\">Node Exporter and pull<\/a> \u2014 is a cousin: metrics, not checks. Zabbix never abandoned the classic alert (PROBLEM \/ OK) that Nagios taught. That is why it survived the SRE trend: the NOC still wants a blinking red light.<\/p>\n<h2>2026: 7.4.14, 8.0 LTS in the works<\/h2>\n<p>On 25 August 2026: 7.4.14 and 7.0.30. Agent2 in Go, official Docker <code data-no-translation=\"\">zabbix\/zabbix-docker<\/code> (branches 6.0, 7.0, 7.4, trunk updated in September). 8.0.0beta2 was released on 9 July 2026. What Vladishev showed at Summit 2025 \/ the Japan conference: Complex Event Processing (filtering, normalizing, suppressing, closing old events), APM and OpenTelemetry, cloud-native scaling (separate UI, API, server, and history DB), AI, a global marketplace for partner solutions. The new slogan: \u201cYour business works \u2014 you know it.\u201d Observability, not just ping.<\/p>\n<p>Packages on Ubuntu\/Debian come from Zabbix's own repository \u2014 the distro almost always lags behind. The frontend is PHP; FPM 8.5 on Ubuntu 26.04 does the job.<\/p>\n<h2>Nagios, Zabbix, and what each became<\/h2>\n<p>Nagios: the check and the pager. Zabbix: the item and the graph. Prometheus: the scrape and Grafana. All three coexist. Latvian company, AGPL code, Riga in the courtyard. The red cube is neither a fox nor a dovecote \u2014 it is the name, in uppercase, as always.<\/p>\n<h2>Wrap-up<\/h2>\n<p>A Latvian, a 2001 GPL release, and the determination to put metrics in a database. 7.4.14, 7.0 LTS, 8.0 in beta. AGPLv3 since 7.0. The courtyard on the cover is Riga: brick, Art Nouveau, harbor. Tux on the cobblestones. ZABBIX on the cube.<\/p>\n<p>The ancestor of alerting: <a href=\"\/en\/2026\/09\/a-historia-do-nagios\/\">Nagios<\/a>. The cfg editor: <a href=\"\/en\/2026\/09\/a-historia-do-nagiosql\/\">NagiosQL<\/a>. Modern pull: <a href=\"\/en\/2026\/09\/monitorando-servidores-linux-com-prometheus\/\">Prometheus and Node Exporter<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"<p>On April 7, 2001, Alexei Vladishev released Zabbix under the GPL. It was an internal tool; it became a project. Stable version 1.0 came only on March 23, 2004. In April 2005, SIA Zabbix was founded in Riga, Latvia. Twenty-one years as a company (anniversary on April 12, 2025), twenty-five \u2026 <a title=\"The history of Zabbix: monitoring born in Riga\" class=\"read-more\" href=\"https:\/\/www.linuxpro.com.br\/en\/2026\/09\/a-historia-do-zabbix\/\" aria-label=\"Read more about A hist\u00f3ria do Zabbix: o monitoramento que nasceu em Riga\">Read more<\/a><\/p>","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,2,111,120],"tags":[255,126,254,253],"class_list":["post-555","post","type-post","status-publish","format-standard","hentry","category-infra","category-linux","category-opensource","category-servidores","tag-agpl","tag-monitoramento","tag-riga","tag-zabbix"],"_links":{"self":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/555","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/comments?post=555"}],"version-history":[{"count":3,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/555\/revisions"}],"predecessor-version":[{"id":1188,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/555\/revisions\/1188"}],"wp:attachment":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/media?parent=555"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/categories?post=555"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/tags?post=555"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}