Network Firewall (Appliance) Check Reference
Configuration fields, vendor-specific API surfaces, alert codes, and platform support for the Network Firewall check in octoja.
Written By Stefan Steuer
Last updated 26 days ago
Network Firewall (Appliance) Check Reference
Configuration options and alert behaviour for the Network Firewall (Appliance) check.
The Network Firewall check probes a perimeter firewall appliance for reachability, firmware up-to-date status, license / feature-key expiry, and security signals. Default interval: 15 minutes. The check supports seven vendor surfaces (FortiGate REST API, FortiGate SNMP, OPNsense, Sophos XG / XGS, WatchGuard REST, WatchGuard SNMP, and SonicWall SNMP); fields visible in the UI depend on the selected vendor. The two FortiGate surfaces are distinct: the REST API surface reports firmware and FortiGuard license status, while the SNMP surface reads live measurements (CPU, memory, disk, sessions, VPN tunnels, HA cluster members, and interfaces). The SNMP surfaces vary by vendor: WatchGuard (SNMP) adds CPU, interfaces, and HA; SonicWall (SNMP) adds CPU, RAM, interfaces, and VPN tunnels.
Vendor matrix
Configuration fields
Common fields apply across vendors; the rest are revealed when the matching vendor is selected.
Common
OPNsense
WatchGuard (REST)
Sophos XG / XGS
FortiGate (REST API)
FortiGate (SNMP)
The SNMP surface polls the FortiGate over SNMP for live measurements. Threshold, interface, VPN, and HA fields below are visible only for this vendor.
WatchGuard (SNMP)
The SNMP surface polls a WatchGuard Firebox directly over SNMP. It reuses the same SNMP connection fields as FortiGate (SNMP), plus the CPU, interface, and HA fields below. RAM, disk, and VPN measurements are not collected on this surface.
SonicWall (SNMP)
The SNMP surface polls a SonicWall appliance directly over SNMP. It reuses the same SNMP connection fields as FortiGate (SNMP), plus the CPU, RAM, interface, and VPN fields below. Disk and HA measurements are not collected on this surface.
Issue codes
The check reports a list of issue rows; the worst severity becomes the overall result.
*WatchGuard outdated only fires when a Target Fireware version is configured. FortiGate (REST API) needs no target version — the appliance itself reports available upgrades via FortiGuard.
Error codes
When the check itself cannot run (bad configuration, authentication failure, unreachable API), it reports one of the following error codes instead of issue rows. The check detail view shows the matching message.
Metrics collected
vendor— the vendor string echoed back for the rendereronline— appliance is reachable / at least one Firebox is connectedfirmwareCurrent— currently installed firmware version (best-effort across vendor JSON shapes)firmwareLatest— latest version reported by OPNsense / FortiGate, or the configured target string for Sophos / WatchGuardupToDate— true / false / null (null when the up-to-date dimension was not evaluated)licenseExpiresAt— soonest feature-key / subscription expiry (WatchGuard and FortiGate), ISO-8601openAlerts— ThreatSync open-incident count when available (WatchGuard only)issues— list of{severity, code, detail}entries that contributed to the result
FortiGate (SNMP) additionally returns the live measurements below.
sysName/model/fortiOsVersion/uptimeDays— appliance identity and uptimecpuPercent/memPercent/diskPercent— CPU, memory, and disk usage in percentmemTotalMB/diskTotalMB— total memory and disk capacitysessionCount— active session countvpnTunnelsplusvpnTunnelsTotal/vpnTunnelsUp/vpnTunnelsDown— per-tunnel status and totalshaMode/haGroup/haNodes/haNodeCount— HA mode, group, and per-node CPU / memoryinterfacesplusifTotal/ifUp/ifDownandifInErrors/ifOutErrors— interface status and aggregate error counters
Platform support
The check runs on the octoja agent; the agent platform is irrelevant — what matters is reachability to the appliance or cloud.
Notes
- The check runs every 15 minutes on the agent. The interval is not user-configurable.
- HTTP timeout per API call is 30 seconds.
- The OPNsense flow triggers a fresh firmware-check before reading status, then waits 4 seconds — the OPNsense API serves a cached status until a check is explicitly triggered.
- The WatchGuard parser is tolerant of field-name variations across tenants:
connectionStatus/status,fireboxVersion/osVersion,featureKeyExpiration/expirationDate, and so on. - Version comparison is lower-case prefix matching (e.g.
12.7matches12.7.1). Set Target firmware version to a prefix to allow patch revisions through. - OPNsense and Sophos feature-key / license expiry is currently not surfaced. The license dimension applies to WatchGuard and FortiGate only.
- The Sophos XML API requires the credentials in the request body, not headers — octoja escapes user input via the XML serializer before posting.
- FortiGate (SNMP) thresholds are normalised so that the warning value is never higher than the critical value — if entered the wrong way round, octoja swaps them.
- FortiGate (SNMP) VPN tunnel status is aggregated by tunnel name: a tunnel counts as up when any of its selectors is up.
- FortiGate (SNMP) interface collection skips software loopback interfaces. A required interface that is admin-up but operationally down is reported as down.