Devices · Servers and virtualization · Profile v13 from the Vesana community hub

Proxmox VE monitoring

The profile brings 25 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.

CheckViaDefault thresholds
PingPing
API reachableHTTP API
CPU usageREST APIwarn ≥ 85% · crit ≥ 95%
Memory usageREST APIwarn ≥ 90% · crit ≥ 96%
Root filesystem usageREST APIwarn ≥ 85% · crit ≥ 95%
Swap usageREST APIwarn ≥ 50% · crit ≥ 90%
Load per coreREST APIwarn ≥ 2 · crit ≥ 4
UptimeREST API
Storage usage (fullest)REST APIwarn ≥ 85% · crit ≥ 95%
Storages not reachableREST APIwarn ≥ 1 storages · crit ≥ 1 storages
VMs not runningREST APIwarn ≥ 1 VMs
Containers not runningREST APIwarn ≥ 1 CTs
Guests runningREST API
Cluster quorumREST APIwarn ≥ 1 clusters · crit ≥ 1 clusters
Cluster nodes offlineREST APIwarn ≥ 1 nodes · crit ≥ 1 nodes
Oldest backup ageREST APIwarn ≥ 26 hours · crit ≥ 50 hours
Backup failuresREST APIwarn ≥ 1 tasks
Backup warningsREST API
Guests without backup jobREST APIwarn ≥ 1 guests
Backup jobs configuredREST API
Services failedREST APIwarn ≥ 1 services · crit ≥ 1 services
ZFS pool healthREST APIwarn ≥ 1 pools · crit ≥ 1 pools
Disk health (SMART)REST APIwarn ≥ 1 disks · crit ≥ 1 disks
Updates pendingREST API
SubscriptionREST 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.0 or later. Profile data as of 2026-10-22.