Zabbix Monitoring
The BarnesBears home lab uses Zabbix Server at 192.168.10.87, with Zabbix Agent 2 deployed on managed hosts using Ansible where appropriate.
Monitored systems and checks
| System | Historical checks / notes |
|---|---|
traefik-1 |
Traefik reloads, file descriptors, goroutines, certificate expiry; guarded recovery script |
| Docker hosts | Docker discovery and access permissions for Agent 2 |
| Proxmox / infrastructure | Host availability and system metrics; confirm specific templates |
| Frigate host | Memory/swap monitoring; swapfile added after heavy swap usage |
| Mobility Print | Print queue monitoring and service/process checks |
| WordPress LXC | Swap alert investigated; container-reported swap metrics can reflect host state |
Traefik monitoring
Traefik exposes Prometheus metrics on a local endpoint previously checked at:
curl -s http://127.0.0.1:8082/metrics | grep 'traefik_tls_certs_not_after'
Zabbix Agent 2 is configured with permissions to read Traefik logs and a guarded recovery script:
/usr/local/sbin/zabbix-recover-traefik
Certificate expiry alerts cleared after a Traefik restart in an October 2026 incident involving stale certificate metric entries. Check live certificate state before assuming a restart is the correct remedy.
Administration
Confirm the Zabbix Agent 2 version, item status, permissions, and templates on each host. Docker access for zabbix may require group membership and an agent restart; weigh the privileges granted by Docker socket access.
Do not expose the Zabbix interface or agent endpoints publicly without explicit access controls.