Skip to main content
User guide

Network posture

The on-call board: open problems, unreachable devices, busy links, flapping interfaces, a problem timeline, the noisiest triggers and the latest alerts. Read straight from Zabbix, no model calls. All editions.

Network posture answers "where is the network hurting right now". Every load reads Zabbix directly without calling the model, and it is available in every edition. The page refreshes every 30 seconds; select Pause refresh in the upper-right corner to stop it. The Window can be 1 hour, 6 hours, 24 hours, 7 days or 30 days, 24 hours by default. You can filter by Host group; with the host-group allowlist on, a host group is required.

Network posture

Key metrics

MetricHow it is counted
Open problemsProblems not yet resolved, with how many are unacknowledged. Problems of high severity or above are counted on a badge
Unreachable devicesMonitored hosts whose agent, SNMP, IPMI or JMX interface is unavailable, or whose latest icmpping value is 0
Busy linksInterfaces whose current in or out rate is at least 80% of net.if.speed. The threshold is set by RST_REPORT_LINK_BUSY_PCT. Without interface items that carry a speed, it shows No interface items with a speed
Flapping interfacesInterfaces whose interface trigger fired 2 or more times in the window

Interface triggers are recognized by name (for example Link down, Interface, operational status) or by tag (interface, ifname, port), which covers the stock Zabbix network templates.

Problem timeline and severity mix

Problem timeline counts problem events in the window per time bucket. Next to it, Open problems by severity shows the severity split of problems still open. With more than 10,000 problem events in the window, the page notes that the timeline and rankings only count the latest 10,000.

Rankings and latest alerts

ListContentSelecting an entry
Noisiest triggersThe 10 triggers that fired most in the windowOpens Live problems filtered to that trigger
Most flapping interfacesThe top 10 interface triggers that fired 2 or more timesSame
Unreachable devicesUnreachable devices and why
Busy linksLinks over the threshold
Latest alertsThe most recent problems; filter with Search trigger or deviceOpens that alert's details

One noisy trigger often fills most of the queue. Regenerate its threshold in Triggers & items, or adjust it in Zabbix. For long-term link trends (P95, forecast), see Reports.

On this page