zabbix-no-datalisted
Install: claude install-skill stufently/zabbix-ai-cli-mcp
# Zabbix: silence and no-data
Silence is ambiguous: a host that reports nothing looks the same as a host with
nothing wrong. These commands tell the two apart.
## Workflow
1. **Across the installation**:
```bash
zabbix-ai-cli-mcp unreachable --json
```
Lists monitored hosts with an unavailable interface, with the error text Zabbix
recorded and whether the host is in maintenance.
2. **For one host**:
```bash
zabbix-ai-cli-mcp host investigate web01 --json
```
Read `no_data_items` and `unsupported_items` together with `status.agent_available`.
3. **For specific checks**:
```bash
zabbix-ai-cli-mcp metrics latest web01 --search disk --json
```
Each value carries `no_data`, `stale` and `age`.
## Distinguishing the causes
- **Agent unreachable** — the interface is unavailable and carries an error. Nothing
on that host is reporting; investigate connectivity, not individual checks.
- **Item unsupported** — the check runs and fails. `error` says why: a missing
binary, a permission problem, a changed key. This is a monitoring fault.
- **Item silent but supported** — the check stopped producing values without
erroring. Often a template or interval change.
- **In maintenance without data collection** — the gap is expected. Check
`maintenance list` before calling it a fault.
## Reading the result
`stale` means the newest value is older than three collection intervals. It is only
computed for items that collect on a schedule: trapper