Proxmox VE Health
Monitor VMs, containers, orphaned locks, storage, cluster quorum and snapshots of a Proxmox VE host locally, without credentials.
The Proxmox VE Health check monitors a Proxmox VE host: whether the VMs and containers that should run are running, whether guests are left with orphaned locks, how full storages are, whether the cluster has quorum, and how many snapshots exist and how old they are. It runs on Linux (x64) every 10 minutes by default, reads its data locally on the host and needs no credentials. The check does not change the host, its guests or the cluster.
Templates are not checked. The check does not cover backup history or guest tools; for backups, use Proxmox Backup Server.
Prerequisites
- The octoja agent runs directly on the Proxmox VE host with root privileges. The check queries
pveshand reads guest configurations under/etc/pve. - You can assign checks to the device. Configuration packages require Monitoring Check Management.
Steps
- Open the host and add Proxmox VE Health under Checks. Use a configuration package for multiple hosts.
- Keep the sub-checks you need enabled and turn off the others.
- Under Guests that must run (IDs or exact names), enter guests that must always run even if Start at boot is not enabled in Proxmox. Enter guests the check should ignore under Excluded guests (IDs or exact names).
- Adjust the thresholds if needed and save.
- After the first run, open the result. It shows the number of guests and storages checked, whether the host is standalone or clustered, and every issue found.
- Configure alerting if needed.
In a cluster, assign the check to every node. It only checks guests and storages of the node it runs on.
Settings
Thresholds must be positive, and the warning value must not exceed the critical value. A value that exactly reaches a threshold counts as exceeding it. Thresholds of disabled sub-checks are not validated.
Results
The suspended lock of a guest deliberately suspended to disk is not treated as orphaned. Running tasks such as backup, migration, snapshot or clone suppress the warning for the affected guest.
FAQ
How does this check differ from Proxmox Cluster & Quorum?
How does this check differ from Proxmox Cluster & Quorum?
Both check quorum and the online state of nodes. Proxmox Cluster & Quorum also checks Corosync links and the /etc/pve mount. If you run both checks on the same host, you can turn off Monitor cluster and quorum here so a cluster problem does not alert twice. Essential Proxmox services and HA are covered by Proxmox Services & HA.
Why does the check report a listed guest as missing?
Why does the check report a listed guest as missing?
The check only sees guests of the node it runs on. If the guest was migrated to another node, it is missing here. List guests that move between nodes only on the check of the node that should host them, or rely on Start at boot.
Was this helpful?
More in Virtualization & containers
Docker ContainerHyper-V VM StatusMicrosoft Hyper-V HostProxmox Cluster & QuorumStill need help? Ask the team