Hi all,
I’ve published a Healthcheck module for Zabbix 7.
Zabbix monitors your infrastructure, but what monitors Zabbix itself?
This module verifies that the Zabbix API is responding, checks monitored hosts, enabled problem triggers, enabled items, and the freshness of collected item data. If everything passes, it sends a success ping to a configured healthcheck endpoint such as healthchecks.io. If a check fails, the ping is not sent.
That helps detect cases where Zabbix may still be polling hosts, but something on the Zabbix side is failing, or outbound connectivity is broken so alerts and actions never leave the server.
With a service like healthchecks.io, a missed ping can trigger an alert through integrations such as PagerDuty, Teams, Slack, GitHub, and others.
The module also adds frontend pages for heartbeat, history, and settings, and includes a runner you can schedule with systemd or cron.
I’ve published a Healthcheck module for Zabbix 7.
Zabbix monitors your infrastructure, but what monitors Zabbix itself?
This module verifies that the Zabbix API is responding, checks monitored hosts, enabled problem triggers, enabled items, and the freshness of collected item data. If everything passes, it sends a success ping to a configured healthcheck endpoint such as healthchecks.io. If a check fails, the ping is not sent.
That helps detect cases where Zabbix may still be polling hosts, but something on the Zabbix side is failing, or outbound connectivity is broken so alerts and actions never leave the server.
With a service like healthchecks.io, a missed ping can trigger an alert through integrations such as PagerDuty, Teams, Slack, GitHub, and others.
The module also adds frontend pages for heartbeat, history, and settings, and includes a runner you can schedule with systemd or cron.