Zabbix alerts panel #11

New Issue

2026-07-12T20:11:04-06:00

jhodgkin commented

2026-07-12 20:11:04 -06:00

Pull active problems from Zabbix's API (CT109) and surface them as a unified alerts panel. Complements, doesn't duplicate, Zabbix's own alerting. Needs a Zabbix API token from the user.

jhodgkin commented

2026-07-12 21:15:58 -06:00

Investigated instead of just asking for a token, and found Zabbix (CT109) was never actually finished being set up, independent of this dashboard:

Web frontend isn't wired into Apache at all (serves the default "It works" placeholder page, not Zabbix)
/etc/zabbix/web/zabbix.conf.php doesn't exist — the setup wizard was never run
DB only has stock default templates, no real homelab hosts were ever added as monitored hosts (just Zabbix self-monitoring)
Default Admin Super Admin account almost certainly still on the stock zabbix password, reachable on the LAN

User's call: skip Zabbix entirely for now (see also a note added to the main homelab repo's backlog for the underlying infra gap, separate from this dashboard). Leaving this issue open but not actively worked — the alerts panel has nothing meaningful to pull until Zabbix itself is actually configured.

Investigated instead of just asking for a token, and found Zabbix (CT109) was never actually finished being set up, independent of this dashboard: - Web frontend isn't wired into Apache at all (serves the default "It works" placeholder page, not Zabbix) - `/etc/zabbix/web/zabbix.conf.php` doesn't exist — the setup wizard was never run - DB only has stock default templates, no real homelab hosts were ever added as monitored hosts (just Zabbix self-monitoring) - Default `Admin` Super Admin account almost certainly still on the stock `zabbix` password, reachable on the LAN User's call: skip Zabbix entirely for now (see also a note added to the main homelab repo's backlog for the underlying infra gap, separate from this dashboard). Leaving this issue open but not actively worked — the alerts panel has nothing meaningful to pull until Zabbix itself is actually configured.

jhodgkin commented

2026-07-12 21:16:34 -06:00

Correction/important context found after my last comment: the main homelab repo already has jhodgkin/homelab#15, a planned migration that decommissions Zabbix entirely in favor of Prometheus + Loki + Grafana. That's why it was never finished — it's already been slated for replacement, not neglected. Also flagged there: that issue's plan reserves CT122 for the new Grafana stack, which collides with this dashboard's CT122 (filed a heads-up comment there).

Per user's call: skipping Zabbix integration entirely. Closing this issue as won't-do — once homelab#15 lands, the natural replacement is a Prometheus/Grafana-backed panel instead, which would be a new issue at that point, not a resurrection of this one.

Correction/important context found after my last comment: the main homelab repo already has `jhodgkin/homelab#15`, a planned migration that **decommissions Zabbix entirely** in favor of Prometheus + Loki + Grafana. That's why it was never finished — it's already been slated for replacement, not neglected. Also flagged there: that issue's plan reserves CT122 for the new Grafana stack, which collides with this dashboard's CT122 (filed a heads-up comment there). Per user's call: skipping Zabbix integration entirely. Closing this issue as won't-do — once `homelab#15` lands, the natural replacement is a Prometheus/Grafana-backed panel instead, which would be a new issue at that point, not a resurrection of this one.

jhodgkin closed this issue

2026-07-12 21:16:34 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jhodgkin/homelab-monitor#11