● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
Z

Zabbix

Observability
Open source · AGPL-3.0

Zabbix is an open-source infrastructure and network monitoring platform: agent-based and agentless polling, trapping, triggers, and alerting, with a built-in web frontend and its own storage backend (historically MySQL/PostgreSQL/TimescaleD

updated 2026-07-01

What it is

Zabbix is an open-source infrastructure and network monitoring platform: agent-based and agentless polling, trapping, triggers, and alerting, with a built-in web frontend and its own storage backend (historically MySQL/PostgreSQL/TimescaleDB). It predates the CNCF observability stack by well over a decade and targets classic IT operations — servers, network gear, VMs — rather than cloud-native, ephemeral workloads.

One data point worth flagging: the GitHub stats given here (6,015 stars, Go Template as primary language, 192 contributors) don't match the profile of Zabbix's main C-based core repository, which is far larger and older. This repo is almost certainly a Zabbix-adjacent project — likely Helm charts or a Kubernetes-specific integration — not the core monitoring engine. Treat the GitHub numbers below as describing that specific repo, not the Zabbix project as a whole.

Who builds it and why

Zabbix the core product is built by Zabbix SIA, a Latvia-based company that has maintained it since the late 1990s, funded through commercial support, training, and certification rather than VC money. It's one of the few monitoring tools with a genuinely long, boring, stable development history — not a startup racing to a Series B.

The specific repo referenced here (Go Template, 192 contributors) reflects community tooling to make Zabbix deployable on Kubernetes — a bolt-on to a product that wasn't originally built with Kubernetes in mind.

Production readiness signal

Contributor count (192) and an active commit cadence suggest this repo is maintained, not abandoned. Star count (6,015) is modest — consistent with a supporting/packaging repo rather than a flagship project. CNCF maturity, latest release, and founding date are not publicly available from the data provided, so treat version stability and release cadence as unverified until you check the actual release history yourself before depending on it in production.

The core Zabbix product itself has decades of production use in enterprise NOCs — that track record exists independently of this specific repo's stats.

Who should use this

  • Teams running traditional infrastructure (bare metal, VMs, network appliances) alongside Kubernetes, who want one pane of glass instead of separate tools per environment.
  • Ops teams that want SNMP, IPMI, and agent-based host monitoring with mature alerting/escalation logic, not just metrics scraping.
  • Organizations that already run Zabbix for the rest of their estate and need a supported way to extend it into Kubernetes rather than adopting Prometheus separately.

Who should NOT use this

  • Kubernetes-native teams that already run Prometheus/Grafana — Zabbix adds a second, architecturally different monitoring stack with its own data model, and running both means duplicated alerting logic and dashboards.
  • Anyone wanting to build a SaaS observability product on top of this — AGPL-3.0 has strong copyleft/network-use implications; get legal review before offering it as a hosted service to third parties.
  • Teams needing high-cardinality metrics, distributed tracing, or logs-metrics-traces correlation — Zabbix's data model is built for host/item/trigger monitoring, not modern observability signal correlation.
  • Anyone expecting cloud-native release velocity — this is not it; expect a slower, more conservative development pace than tools born in the CNCF ecosystem.

Alternatives

  • Prometheus + Grafana — the default cloud-native stack; better cardinality handling and ecosystem fit for Kubernetes, but you build alerting/escalation yourself.
  • Checkmk — similar era and philosophy to Zabbix (agent-based, broad IT monitoring), with a comparable enterprise/on-prem focus.
  • Datadog — if you want managed infrastructure + APM + logs in one SaaS product and don't want to run monitoring infra yourself; not free, and not a fit if AGPL avoidance or data residency is a concern either way.

Pricing

Zabbix itself is fully open source (GPL-2.0 for the core product). The specific repo referenced in this profile is AGPL-3.0 — confirm license terms before embedding it in anything you distribute or host as a service. Commercial support, training, and certification are sold separately by Zabbix SIA; exact pricing is not publicly available here — check with Zabbix directly.

Frequently asked

What is Zabbix?+
Zabbix is an open-source infrastructure and network monitoring platform: agent-based and agentless polling, trapping, triggers, and alerting, with a built-in web frontend and its own storage backend (historically MySQL/PostgreSQL/TimescaleDB).
Who builds Zabbix?+
Zabbix the core product is built by Zabbix SIA, a Latvia-based company that has maintained it since the late 1990s, funded through commercial support, training, and certification rather than VC money.
Is Zabbix production ready?+
Contributor count (192) and an active commit cadence suggest this repo is maintained, not abandoned. Star count (6,015) is modest — consistent with a supporting/packaging repo rather than a flagship project.
Who should use Zabbix?+
Teams running traditional infrastructure (bare metal, VMs, network appliances) alongside Kubernetes, who want one pane of glass instead of separate tools per environment. Ops teams that want SNMP, IPMI, and agent-based host monitoring with mature alerting/escalation logic, not just metrics scraping.
Who should not use Zabbix?+
Kubernetes-native teams that already run Prometheus/Grafana — Zabbix adds a second, architecturally different monitoring stack with its own data model, and running both means duplicated alerting logic and dashboards. Anyone wanting to build a SaaS observability product on top of this — AGPL-3.
What are the alternatives to Zabbix?+
Prometheus + Grafana — the default cloud-native stack; better cardinality handling and ecosystem fit for Kubernetes, but you build alerting/escalation yourself. Checkmk — similar era and philosophy to Zabbix (agent-based, broad IT monitoring), with a comparable enterprise/on-prem focus.
How much does Zabbix cost?+
Zabbix itself is fully open source (GPL-2.0 for the core product). The specific repo referenced in this profile is AGPL-3.0 — confirm license terms before embedding it in anything you distribute or host as a service.