Zabbix Monitoring Coverage
Overview
Problem triage only shows what Zabbix can see. This skill checks the things
that make Zabbix go blind: hosts that are disabled or unreachable, hosts with
nothing linked to them, a site proxy that stopped talking to the server, and
maintenance windows that silently suppress a host forever. Run it when a
customer is onboarded, before a quarterly review, and whenever a site
"has been quiet for a suspiciously long time".
Read api-patterns first. No tool in this
workflow is admin-gated in Conduit. zabbix_host_interfaces_list is opt-in
and not listed in Conduit; this skill gets interface availability from
zabbix_hosts_list with selectInterfaces instead.
Anti-triggers
Key Concepts
| Object |
Field |
Values |
| Host |
status |
0 monitored, 1 not monitored (disabled) |
| Host |
maintenance_status |
1 when a maintenance is in effect |
| Host |
monitored_by (7.0+) |
0 server, 1 proxy, 2 proxy group |
| Interface |
type |
1 agent, 2 SNMP, 3 IPMI, 4 JMX |
| Interface |
available |
0 unknown, 1 available, 2 unavailable; error says why |
| Proxy (7.0+) |
state |
0 unknown, 1 offline, 2 online |
| Proxy |
lastaccess |
Unix time the server last heard from it |
| Proxy (7.0+) |
operating_mode |
0 active, 1 passive |
| Proxy group (7.0+) |
state |
0 unknown, 1 offline, 2 recovering, 3 online, 4 degraded |
On Zabbix 6.x proxies have no state or operating_mode; judge them by
lastaccess alone, and the proxy name is in host, not name. Proxy
groups do not exist before 7.0. Check zabbix_api_version first.
Common Workflows
Customer coverage review
zabbix_hostgroups_list with search: {"name": "<customer>"} and
selectHosts: "count" for the group IDs and host counts.
zabbix_hosts_list with groupids,
output: ["hostid","host","name","status","maintenance_status"],
selectInterfaces: ["type","ip","dns","available","error"],
selectParentTemplates: ["name"], selectTags: "extend",
limit: 500. If the group is larger than 500, call once per group.
- Flag, per host:
status: 1 - disabled. Confirm the device was retired, otherwise it is
a gap.
- every interface
available: 2 - Zabbix cannot reach it; quote error.
- no parent templates - nothing is collected.
zabbix_triggers_list with groupids, output: ["triggerid"],
selectHosts: ["hostid"] and monitored: true (page by host group) to
find enabled hosts with no active triggers: they collect data but can
never raise a problem. zabbix_hosts_list with with_triggers: true
and countOutput: true gives the quick count to compare against.
zabbix_templates_list with selectHosts: "count" to list templates
linked to no host (cleanup) and to confirm the customer's standard
templates (OS, network, backup) are actually linked.
Site collector (proxy) health
zabbix_proxies_list with
selectHosts: "count" and output: "extend".
- A proxy whose
lastaccess is more than a few minutes old (or state: 1
on 7.0+) has stopped reporting. Every host behind it is blind, and Zabbix
may raise only one internal problem for it, or none.
- On 7.0+,
zabbix_proxy_groups_list with selectProxies: ["name","state"]
shows whether HA failover still has a healthy member (state: 4 degraded
means one proxy is left).
- Report each silent proxy with the number of hosts it carries and how long
it has been silent.
Maintenance hygiene
zabbix_maintenance_list with groupids, selectHosts: ["name"],
selectHostGroups: ["name"], selectTimeperiods: "extend".
- Flag windows whose
active_till is months or years out, and windows that
cover a whole customer group. They hide real problems. maintenance_type
1 means "no data collection", which also blanks SLA and trend data.
- Cross-check
zabbix_hosts_list with filter: {"maintenance_status": 1}
for hosts in maintenance right now.
Synthetic checks
zabbix_web_scenarios_list with groupids, selectHosts: ["name"] and
output: ["httptestid","name","status","delay"]. status: 1 means the
scenario is disabled. Authentication fields and sensitive headers are
redacted by the sidecar.
Gotchas
- Host count from Zabbix is not the customer's asset count. Compare
against the RMM or PSA inventory before calling coverage complete.
- A disabled host raises no problems. That is exactly why it belongs on
this report and never shows up in triage.
available is per interface. A host with a working agent interface
and a dead SNMP interface is partly blind; report the interface type.
- Proxy offline is easy to miss. Hosts behind a dead proxy often show
stale "OK" in dashboards because no new data arrived to change state.
- Older frontends reject 7.0+ fields.
selectProxyGroup and
proxy_groupids fail on 6.x with an invalid-params error.
Output
Per customer: host count, disabled hosts, unreachable hosts (with error),
hosts with no templates, hosts with no triggers, proxies silent and for how
long, maintenance windows to review. End with the three fixes that close the
biggest blind spots.
Related Skills
1---2name: zabbix-monitoring-coverage3description: >4 Monitoring-coverage and collector-health review for a customer's Zabbix:5 disabled and unreachable hosts, hosts with no templates or triggers,6 templates linked to nothing, site proxies that stopped reporting, proxy7 group HA state, maintenance windows that never end, and disabled web8 scenarios. Covers host status, interface availability and proxy state9 fields across Zabbix 6.x and 7.x. Read-only.10when_to_use: >-11 When checking whether a customer is actually being monitored, onboarding a12 new site into Zabbix, auditing coverage before a QBR, or finding out why a13 site went quiet. Use when: zabbix coverage, unmonitored hosts, zabbix14 proxy offline, site collector down, hosts without templates, zabbix15 onboarding check, stale maintenance, zabbix agent unreachable, or zabbix16 health check.17metadata:18 source: https://skillmd.com/skills/wyre-ai/zabbix-monitoring-coverage19---2021# Zabbix Monitoring Coverage2223## Overview2425Problem triage only shows what Zabbix can see. This skill checks the things26that make Zabbix go blind: hosts that are disabled or unreachable, hosts with27nothing linked to them, a site proxy that stopped talking to the server, and28maintenance windows that silently suppress a host forever. Run it when a29customer is onboarded, before a quarterly review, and whenever a site30"has been quiet for a suspiciously long time".3132Read [api-patterns](../api-patterns/SKILL.md) first. No tool in this33workflow is admin-gated in Conduit. `zabbix_host_interfaces_list` is opt-in34and not listed in Conduit; this skill gets interface availability from35`zabbix_hosts_list` with `selectInterfaces` instead.3637## Anti-triggers3839- **What is broken right now on monitored hosts** - use40 [problem-triage](../problem-triage/SKILL.md).41- **Availability percentages for a customer report** - use42 [sla-reporting](../sla-reporting/SKILL.md).4344## Key Concepts4546| Object | Field | Values |47|--------|-------|--------|48| Host | `status` | 0 monitored, 1 not monitored (disabled) |49| Host | `maintenance_status` | 1 when a maintenance is in effect |50| Host | `monitored_by` (7.0+) | 0 server, 1 proxy, 2 proxy group |51| Interface | `type` | 1 agent, 2 SNMP, 3 IPMI, 4 JMX |52| Interface | `available` | 0 unknown, 1 available, 2 unavailable; `error` says why |53| Proxy (7.0+) | `state` | 0 unknown, 1 offline, 2 online |54| Proxy | `lastaccess` | Unix time the server last heard from it |55| Proxy (7.0+) | `operating_mode` | 0 active, 1 passive |56| Proxy group (7.0+) | `state` | 0 unknown, 1 offline, 2 recovering, 3 online, 4 degraded |5758On Zabbix 6.x proxies have no `state` or `operating_mode`; judge them by59`lastaccess` alone, and the proxy name is in `host`, not `name`. Proxy60groups do not exist before 7.0. Check `zabbix_api_version` first.6162## Common Workflows6364### Customer coverage review65661. `zabbix_hostgroups_list` with `search: {"name": "<customer>"}` and67 `selectHosts: "count"` for the group IDs and host counts.682. `zabbix_hosts_list` with `groupids`,69 `output: ["hostid","host","name","status","maintenance_status"]`,70 `selectInterfaces: ["type","ip","dns","available","error"]`,71 `selectParentTemplates: ["name"]`, `selectTags: "extend"`,72 `limit: 500`. If the group is larger than 500, call once per group.733. Flag, per host:74 - `status: 1` - disabled. Confirm the device was retired, otherwise it is75 a gap.76 - every interface `available: 2` - Zabbix cannot reach it; quote `error`.77 - no parent templates - nothing is collected.784. `zabbix_triggers_list` with `groupids`, `output: ["triggerid"]`,79 `selectHosts: ["hostid"]` and `monitored: true` (page by host group) to80 find enabled hosts with no active triggers: they collect data but can81 never raise a problem. `zabbix_hosts_list` with `with_triggers: true`82 and `countOutput: true` gives the quick count to compare against.835. `zabbix_templates_list` with `selectHosts: "count"` to list templates84 linked to no host (cleanup) and to confirm the customer's standard85 templates (OS, network, backup) are actually linked.8687### Site collector (proxy) health88891. `zabbix_proxies_list` with90 `selectHosts: "count"` and `output: "extend"`.912. A proxy whose `lastaccess` is more than a few minutes old (or `state: 1`92 on 7.0+) has stopped reporting. Every host behind it is blind, and Zabbix93 may raise only one internal problem for it, or none.943. On 7.0+, `zabbix_proxy_groups_list` with `selectProxies: ["name","state"]`95 shows whether HA failover still has a healthy member (`state: 4` degraded96 means one proxy is left).974. Report each silent proxy with the number of hosts it carries and how long98 it has been silent.99100### Maintenance hygiene1011021. `zabbix_maintenance_list` with `groupids`, `selectHosts: ["name"]`,103 `selectHostGroups: ["name"]`, `selectTimeperiods: "extend"`.1042. Flag windows whose `active_till` is months or years out, and windows that105 cover a whole customer group. They hide real problems. `maintenance_type`106 1 means "no data collection", which also blanks SLA and trend data.1073. Cross-check `zabbix_hosts_list` with `filter: {"maintenance_status": 1}`108 for hosts in maintenance right now.109110### Synthetic checks111112`zabbix_web_scenarios_list` with `groupids`, `selectHosts: ["name"]` and113`output: ["httptestid","name","status","delay"]`. `status: 1` means the114scenario is disabled. Authentication fields and sensitive headers are115redacted by the sidecar.116117## Gotchas118119- **Host count from Zabbix is not the customer's asset count.** Compare120 against the RMM or PSA inventory before calling coverage complete.121- **A disabled host raises no problems.** That is exactly why it belongs on122 this report and never shows up in triage.123- **`available` is per interface.** A host with a working agent interface124 and a dead SNMP interface is partly blind; report the interface type.125- **Proxy offline is easy to miss.** Hosts behind a dead proxy often show126 stale "OK" in dashboards because no new data arrived to change state.127- **Older frontends reject 7.0+ fields.** `selectProxyGroup` and128 `proxy_groupids` fail on 6.x with an invalid-params error.129130## Output131132Per customer: host count, disabled hosts, unreachable hosts (with error),133hosts with no templates, hosts with no triggers, proxies silent and for how134long, maintenance windows to review. End with the three fixes that close the135biggest blind spots.136137## Related Skills138139- [api-patterns](../api-patterns/SKILL.md) - Parameters and errors140- [problem-triage](../problem-triage/SKILL.md) - Open problems