Bandwidth Check Reference

All parameters, thresholds, and configuration options for the bandwidth check in octoja.

Written By Erdinc Akay

Last updated About 2 months ago

The Bandwidth Check measures network throughput on specific interfaces and alerts when utilization exceeds the configured thresholds.

Configuration fields

Field	Type	Required	Default	Description
Sampling duration (seconds)	Seconds	No	5	Delay between the two interface counter reads. Clamped to 1–30 seconds; values outside the range are coerced before sampling.
Monitor all interfaces	Boolean	No	Yes	Monitor all network interfaces
Interfaces	List of strings	No	—	Specific interface names to monitor. Only shown in the editor when Monitor all interfaces is unchecked. If the list is left empty, all interfaces are monitored as if Monitor all interfaces were checked.
Use percentage of link speed	Boolean	No	No	Use percentage of link speed instead of absolute Mbps value
Warning (%)	Percent	No	80	Utilization percentage that triggers a warning. Only shown when Use percentage of link speed is checked.
Critical (%)	Percent	No	95	Utilization percentage that triggers a critical result. Only shown when Use percentage of link speed is checked.
Warning (Mbps)	Mbps	No	800	Throughput that triggers a warning. Only shown when Use percentage of link speed is unchecked.
Critical (Mbps)	Mbps	No	950	Throughput that triggers a critical result. Only shown when Use percentage of link speed is unchecked.

Threshold auto-swap. If the warning threshold is greater than the critical threshold, the runtime swaps the two values before evaluation. This applies to both the Mbps and the percentage threshold pairs.
Percentage thresholds are clamped to 0–100. Values outside the range are coerced before the swap check.
No monitored interfaces. If filtering leaves zero interfaces (for example, every name in Interfaces is misspelled, or the host has no non-loopback interfaces in the Up state), the check returns a Warning result with an empty interface list rather than failing.
Counter-reset protection. If a per-interface byte counter goes backwards between the two samples (some drivers reset on link flap), the throughput for that direction is reported as 0 Mbps for that run instead of a negative value.

The check takes a network traffic sample over the configured duration. A longer sample duration provides more representative results but briefly increases the check execution time.
When monitoring all interfaces, the check automatically excludes loopback interfaces and any interface that is not in the Up operational state. Other virtual interfaces (VPN adapters, virtual switches) are included; exclude them by selecting specific interfaces if they cause false positives.
If an interface does not report a link speed, percentage thresholds cannot be applied and the check falls back to the Mbps thresholds for that interface. Link speed reporting is most reliable on Windows.

See also: Configure a Bandwidth Check