Zabbix Agent
Zabbix Agent is a lightweight monitoring agent that reports host and system metrics to a Zabbix Server or Zabbix Proxy.
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
50/100 Fair
- Maintained
- 65last commit 104 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- 100128 MB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 10 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-08-09
- Latest release
- 4.1.9
- Activity
- stale
Checked yesterday - source: GitHub (zabqix/Zabbix-agent)
Resources & Compatibility
Minimum requirements: 128 MB RAM, 256 MB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set up SSH and allow port 22 first If you plan to use SSH (secure shell access), start the SSH service and let inbound traffic reach port 22 before monitoring. Without both, remote SSH checks can't get to the host. source
- Start bsnmpd if you use SNMP If your setup uses SNMP (a protocol for collecting device metrics), run /etc/rc.d/bsnmpd start before monitoring begins. If the helper isn't running, SNMP-based metrics may stay empty. source
- First install Configure the agent with your Zabbix server or proxy address before starting it. source
Fetched 32 days ago - each note links to its source
Variants
Alternatives (12)
- Beszel - A lightweight server monitoring hub with historical data, docker stats, and alerts.
- Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
- Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
- EdgeConnect - Dynatrace EdgeConnect is a secure bridge that links your local data centres to the Dynatrace cloud.
- Icinga - Icinga is a fork of Nagios and is backward compatible.
- LAN Orangutan - LAN Orangutan is a lightweight, self-hosted network scanner that discovers and labels devices on your local network, tracks changes over ti…
- LibreNMS - LibreNMS is a fully featured network monitoring system that discovers and monitors network devices, interfaces, and services.
- Munin - Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?&q…
- Nagios - Nagios is an open-source monitoring system that checks hosts, network services, and IT infrastructure resources so IT administrators can id…
- NetAlertX - NetAlertX is a self-hosted network presence scanner and alert framework that monitors Wi-Fi or LAN devices, detects new, disconnected, or c…
- Netdata - Netdata is a real-time performance and health monitoring solution that collects per-second metrics from your servers, containers, networks,…
- Observium - Observium is a free and open-source, autodiscovering network monitoring platform.
Checked 51 days ago - source: AlternativeTo
Common questions
Can the agent monitor a host behind NAT or a restrictive firewall without opening an inbound port?
Yes, active checks let the agent connect outward to the Zabbix server or proxy, retrieve item configuration, and send collected values. Passive checks instead require the server or proxy to connect to the agent.
Where is the main Zabbix Agent configuration file and can it be split into fragments?
The primary configuration file is zabbix_agentd.conf, normally under /etc/zabbix on Unix-like systems and with the agent service files on Windows. It can be split with Include directives, but included files must be readable, syntactically valid, and duplicate settings should be avoided.
Why may the Zabbix server self-check fail in a containerized setup?
The default item may look for localhost, which does not work normally inside containers. Change the item target to zabbix-agent so it points to the running Zabbix Agent container.
Can newly installed Zabbix agents join an existing deployment automatically?
Yes, once Zabbix is set up, newly installed agents can self-register on the Zabbix server. The server can apply the correct template based on a discovery rule.
Answers sourced from github.com, github.com, www.reddit.com
Community
- I've fallen in love with Zabbix : r/selfhosted - Reddit (reddit)
- zabbix agent vs agent2 - Server Fault (forum)
Collected 49 days ago - public community threads