The profile brings 22 checks. Vesana queries the device’s HTTP interface — from a collector in that network or from the Vesana server itself.
| Check | Via | Default thresholds |
|---|---|---|
| Ping | Ping | |
| Web GUI port | TCP port | |
| SSH port | TCP port | |
| Web GUI certificate | TLS certificate | |
| System status | HTTP API | warn ≤ 1 · crit ≤ -1 |
| Firewall states usage | HTTP API | warn ≥ 70 · crit ≥ 90 |
| Memory usage | HTTP API | warn ≥ 85 · crit ≥ 95 |
| Disk usage (worst filesystem) | HTTP API | warn ≥ 80 · crit ≥ 90 |
| CPU load (1 min) | HTTP API | warn ≥ 4 · crit ≥ 8 |
| Services stopped | HTTP API | warn ≥ 1 · crit ≥ 3 |
| Gateways down | HTTP API | crit ≥ 1 |
| Gateways degraded | HTTP API | warn ≥ 1 |
| IPsec tunnels established | HTTP API | |
| OpenVPN sessions | HTTP API | |
| WireGuard peers | HTTP API | |
| CARP demotion | HTTP API | warn ≥ 1 · crit ≥ 240 |
| Interface input errors (since boot) | HTTP API | |
| System temperature (max) | HTTP API | warn ≥ 75 · crit ≥ 85 |
| Firmware updates pending | HTTP API | warn ≥ 1 |
| IDS/IPS running | HTTP API | |
| DHCP leases (Dnsmasq) | HTTP API | |
| DHCP leases (Kea) | HTTP API |
Thresholds, intervals and checks can be changed per device without touching code. Profile improvements are published as new versions on the hub; existing installations receive them as an update. Profile data as of 2026-09-13.