Devices · Servers and virtualization · Profile v2 (beta) from the Vesana community hub

Proxmox Backup Server monitoring

The profile brings 22 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
Web interfaceTCP port
Datastore usage (fullest)REST APIwarn ≥ 85% · crit ≥ 95%
Datastore unusableREST APIwarn ≥ 1 datastores · crit ≥ 1 datastores
Days until fullREST APIwarn ≤ 30 days · crit ≤ 10 days
Oldest backup ageREST APIwarn ≥ 26 hours · crit ≥ 50 hours
Verification failuresREST APIwarn ≥ 1 snapshots · crit ≥ 1 snapshots
Snapshots never verifiedREST API
SnapshotsREST API
Garbage collection ageREST APIwarn ≥ 200 hours · crit ≥ 400 hours
Garbage collection resultREST APIwarn ≥ 1 datastores · crit ≥ 1 datastores
Failed tasksREST APIwarn ≥ 1 tasks
CPU usageREST APIwarn ≥ 85% · crit ≥ 95%
Memory usageREST APIwarn ≥ 90% · crit ≥ 96%
Root filesystem usageREST APIwarn ≥ 85% · crit ≥ 95%
Load per coreREST APIwarn ≥ 2 · crit ≥ 4
UptimeREST 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. Profile data as of 2026-10-18.