Widget host availability
Widget appearance:
Environment:
- Zabbix 7.4
- NGINX
- PostgreSQL
Server & Host Specifications
srv‑zabbix (RHEL 10):
- vCPU: 4
- RAM: 8GiB
srv‑smb (Rocky 10):
- vCPU: 6
- RAM: 8GiB
host‑win‑test (Windows 11):
- vCPU: 4
- RAM: 8GiB
ICMP vs Zabbix agent availability
If a host uses a static IP address, ICMP checks provide the fastest and most accurate detection of power state changes
For hosts using DHCP-assigned IP addresses, ICMP becomes unreliable because the IP may change after reboot or lease renewal.
| IP Type | Recommended Method | Reason |
|---|---|---|
| Static IP | ICMP | Fastest detection, stable address, minimal boot/shutdown delay |
| Dynamic IP | Zabbix agent availability | Works independently of IP changes, reliable with DHCP, hostname-based |
Shutdown → Detection Time
(Time measured from host power‑off/shutdown until Zabbix detects the host as unavailable)
| Method | Host | IP Type | Detection Time |
|---|---|---|---|
| ICMP | Linux | static | ~55 seconds |
| Zabbix agent availability | Windows | dynamic | ~1.22 minutes |
| Zabbix agent availability | Linux | static | ~1.42 minutes |
Power‑on → Availability Time
(Time measured from host power‑on until Zabbix reports the host as available)
| Method | Host | IP Type | Detection Time |
|---|---|---|---|
| ICMP | Linux | static | ~33 seconds |
| Zabbix agent availability | Windows | dynamic | ~4.03 minutes |
| Zabbix agent availability | Linux | static | ~1.00 minute |
Widget config
