zabbix-availability

Reports device reachability, flap history, and monitored inventory from Zabbix.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill zabbix-availability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zabbix-availability
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill zabbix-availability

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about zabbix-availability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a device is down using Zabbix?

Query host interface availability through the Zabbix API to see whether the poller can reach the device and since when. The result shows Zabbix's vantage point only; confirm actual device state with direct tools like pyats or multivendor-cli.

How to detect a flapping device in Zabbix monitoring?

Use event.get against the unreachability trigger to retrieve the transition history for the device. Count the state changes within your time window and report the flap count alongside the current availability state.

What is the difference between unreachable and not monitored in Zabbix?

Unreachable means Zabbix actively polls the host but cannot reach it, while not monitored means the host is absent from Zabbix entirely. These are distinct states, and confusing them is a common cause of incorrect outage conclusions.

Can this skill add or disable hosts in Zabbix?

No, the skill is strictly read-only and NMS configuration is out of scope. It can show disabled hosts as findings, but adding, enabling, or disabling hosts must be done through other tooling.

Why does a Zabbix item show no data for a monitored host?

An item with an empty lastclock is monitored but has never returned a value, indicating a broken poll. This is a real finding about the monitoring setup and should not be reported simply as no data.