The profile brings 17 checks. Vesana reads the device’s REST API with a read-only account — from a collector in that network or from the Vesana server itself.
| Check | Via | Default thresholds |
|---|---|---|
| Ping | Ping | |
| HTTPS Port | TCP port | |
| vSphere Agent Port (902) | TCP port | |
| SSH Port | TCP port | |
| SSL Certificate | TLS certificate | |
| CPU usage (%) | REST API | warn ≥ 80% · crit ≥ 90% |
| Memory usage (%) | REST API | warn ≥ 90% · crit ≥ 95% |
| Datastore usage max (%) | REST API | warn ≥ 85% · crit ≥ 95% |
| Datastores inaccessible | REST API | |
| Connection state | REST API | |
| Uplinks without link | REST API | warn ≥ 1 nics |
| Hardware sensors | REST API | |
| Virtual machines running | REST API | |
| Virtual machines not running | REST API | warn ≥ 1 vms |
| Uptime | REST API | |
| Overall health | REST API | warn ≥ 1 · crit ≥ 2 |
| Reboot required | REST 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. This version needs Vesana 1.9.440 or later. Profile data as of 2026-10-23.