What problem does it solve?
Network teams often misread NMS data, treating "Zabbix cannot reach it" as proof a device is down, or overlooking devices that are not monitored at all. This Skill enforces disciplined, timestamped reporting of what the Zabbix poller actually observed, distinguishing unreachable, unknown, and unmonitored states.
Core Features & Use Cases
- Availability Reporting: Queries host interface availability via the Zabbix API and reports reachability with the exact observation time, never claiming a device is down.
- Flap Detection: Pulls event history from unreachability triggers to count state transitions, separating a sustained outage from repeated flapping.
- Monitored Inventory Audit: Lists hosts, host groups, templates, and items with units and retention, surfacing disabled hosts and items that have never returned data as findings.
- Use Case: An engineer asks why alerts stopped for a branch router. The Skill reveals the host is disabled in Zabbix rather than unreachable, exposing a monitoring gap instead of a network outage.
Quick Start
Ask the agent how long Zabbix has been unable to reach a specific device and whether it has been flapping.