Node status / overview
Overall node state, with a detailed overview and cluster association in its attributes.
- Node overview
- Cluster association and scope
Available when node-list monitoring is enabled.
Documentation
A technical dictionary of the entities exposed by Proxmox Extended Sensors. Search by entity name, resource or capability, or browse the categories below.
No matches. Try another name, identifier or attribute.
Search by name, technical identifier, attribute or capability.
130 results
Entities attached to a Proxmox VE node. Conditional entries appear only when the relevant option or data is available.
Overall node state, with a detailed overview and cluster association in its attributes.
Available when node-list monitoring is enabled.
Health of the sidecar endpoints used for extended node information.
CPU model reported by the node, with a core-count fallback.
Configuration and available activity details for Kernel Samepage Merging.
Number of available updates; retrieval failures can expose an error or message.
Node uptime returned in the PVE node data.
Kernel version reported by the PVE node.
Proxmox VE version reported by the node.
Other node-data keys may create additional sensors. Their names and number depend on the data returned by the monitored node; they are not a fixed universal list.
Current processor utilization of the PVE node.
Current node memory utilization.
Current node swap utilization.
Memory saved or shared through Kernel Samepage Merging.
Available when the node reports KSM data.
Time the node spends waiting on I/O, with diagnostic details.
One-minute node load average.
Calculated performance and pressure score; lower is better.
Receive rate calculated from monitored VM and CT network counters.
Transmit rate calculated from monitored VM and CT network counters.
Utilization of the node root filesystem.
Number of available storages for the node.
Available when storage-list monitoring is enabled.
Progress and results of PVE backup tasks from the last 24 hours.
Available when backup-progress monitoring is enabled.
Latest node task summary.
On when CPU exceeds 85%, RAM exceeds 90%, or active tasks exceed five.
Problem signal that turns on when I/O wait exceeds 10%.
On when CPU exceeds 85%, I/O wait exceeds 10%, or one-minute load exceeds the node core count.
Reboots the PVE node.
Available when node controls are enabled.
Shuts down the PVE node.
Available when node controls are enabled.
Sends a Wake-on-LAN request for the node.
Available when a Wake-on-LAN MAC is configured for the node.
Hardware monitoring must be enabled and compatible sidecar or lm-sensors data must be available. Exact dynamic names and quantities vary with the monitored system.
Grouped CPU temperature using package, Tctl or Tdie data when available, with an averaged-core fallback and support for ARM cpu_thermal data.
Available when hardware monitoring is enabled and compatible sidecar or lm-sensors data is detected.
Primary PCH or chipset temperature detected on the monitored node.
Available when hardware monitoring is enabled and a compatible chipset sensor is detected.
Temperature for a detected NVMe device, using lm-sensors data with SMART temperature fallback when available.
Available when hardware monitoring is enabled and an NVMe device is detected.
Additional compatible temperature channels reported by lm-sensors. Adapter and PWM entries are skipped, and ACPI-only blocks are not exposed as standalone sensors.
Available when hardware monitoring is enabled and compatible temperature data exists.
Fan-speed sensors created from detected fan input channels. Exact names and quantity depend on the monitored hardware.
Available when hardware monitoring is enabled and fan input data is detected.
Voltage sensors created from detected voltage input channels. Exact names and quantity depend on the monitored hardware.
Available when hardware monitoring is enabled and voltage input data is detected.
Capacity of a detected physical memory module. One entity is created per DIMM returned by the sidecar inventory.
Available for DIMMs detected in the physical memory inventory.
Sensors are created for virtual machines and containers selected for detailed monitoring. Controls appear when their corresponding guest-control features are enabled.
Current state of a monitored QEMU virtual machine.
Current processor utilization of the virtual machine.
Memory currently used by the virtual machine.
Total memory assigned to the virtual machine.
Total disk capacity reported for the virtual machine.
Current virtual-machine uptime in hours.
Cumulative network data received by the virtual machine.
Cumulative network data transmitted by the virtual machine.
Starts the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Requests a virtual-machine shutdown.
Available when VM controls and the corresponding feature are enabled.
Stops the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Reboots the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Resets the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Pauses the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Hibernates the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Resumes the virtual machine.
Available when VM controls and the corresponding feature are enabled.
Current state of a monitored LXC container.
Current processor utilization of the container.
Memory currently used by the container.
Total memory assigned to the container.
Total disk capacity reported for the container.
Disk capacity currently used by the container.
Current container uptime in hours.
Cumulative network data received by the container.
Cumulative network data transmitted by the container.
Starts the container.
Available when CT controls and the corresponding feature are enabled.
Requests a container shutdown.
Available when CT controls and the corresponding feature are enabled.
Stops the container.
Available when CT controls and the corresponding feature are enabled.
Reboots the container.
Available when CT controls and the corresponding feature are enabled.
Storage entities follow selected PVE resources, while physical disks, mounted disks and ZFS pools depend on the corresponding detected data.
Utilization of a selected and applicable PVE storage resource.
Available for storage resources discovered for the node and included in selected_storage.
Space currently used on a selected PVE storage resource.
Available for storage resources discovered for the node and included in selected_storage.
Space currently available on a selected PVE storage resource.
Available for storage resources discovered for the node and included in selected_storage.
Total capacity of a selected PVE storage resource.
Available for storage resources discovered for the node and included in selected_storage.
Storage type reported for a selected PVE storage resource.
Available for storage resources discovered for the node and included in selected_storage.
Capacity of a detected non-boot physical disk. SMART details vary by disk type and the smartctl data available.
Available when physical-disk monitoring is enabled and a supported non-boot disk is detected; SMART attributes require corresponding SMART data.
Summary of currently mounted, unmounted and missing local or network mounts.
Current health of a detected ZFS pool.
Available only when ZFS pool data is detected.
Server-level status and task entities are accompanied by a dynamic entity family for each discovered PBS datastore.
Proxmox Backup Server version reported by the server.
Proxmox Backup Server release reported by the server.
Current authentication status for the PBS connection.
Current PBS processor utilization.
Node-status data can be unavailable when the optional capability is not supported.
Current PBS memory utilization.
Total memory reported by the PBS server.
Memory currently used by the PBS server.
Memory currently available on the PBS server.
Summary of the latest PBS task.
Worker type of the latest PBS task.
Result or current status of the latest PBS task.
Latest task message or status text.
Duration of the latest task; running duration is calculated when no end time exists.
Current utilization of a discovered PBS datastore.
Created for each discovered PBS datastore.
Total datastore capacity.
Created for each discovered PBS datastore.
Datastore capacity currently used.
Created for each discovered PBS datastore.
Datastore capacity currently available.
Created for each discovered PBS datastore.
Deduplication ratio reported for the datastore.
Created for each discovered PBS datastore.
Timestamp of the latest backup stored in the datastore.
Created for each discovered PBS datastore.
Size of the latest stored backup.
Created for each discovered PBS datastore.
Verification-aware status of the latest datastore backup.
Created for each discovered PBS datastore.
Number of backup errors associated with the datastore.
Created for each discovered PBS datastore.
Summary of the backup snapshots stored in the datastore.
Created for each discovered PBS datastore.
Maintenance status and datastore actions reflect discovered datastores and, where required, their matched jobs.
Current or latest Garbage Collection execution for a PBS datastore.
Created for each discovered PBS datastore.
Current or latest Verify execution for a PBS datastore.
Created for each discovered PBS datastore.
Current or latest Prune execution for a PBS datastore.
Created for each discovered PBS datastore.
Most recent Garbage Collection, Prune, Verify or Sync action matched to the datastore when possible.
Created for each discovered PBS datastore.
Starts Garbage Collection for the datastore.
Created for each discovered PBS datastore.
Starts the matched Prune operation for the datastore.
Availability and behaviour can depend on a configured and matched datastore job.
Starts the matched Verify operation for the datastore.
Availability and behaviour can depend on a configured and matched datastore job.
Starts the matched Sync operation for the datastore.
Availability and behaviour can depend on a configured and matched datastore job.
Requests shutdown of the PBS server.
Available when PBS node controls are enabled.
Reboots the PBS server.
Available when PBS node controls are enabled.
Sends a Wake-on-LAN request for the PBS server.
Available when a PBS Wake-on-LAN MAC is configured.
Cluster-wide entities combine quorum, node availability, resources, guests, storage, firewall and HA data.
Overall Proxmox VE cluster quorum state.
Number of cluster nodes currently online.
Aggregate cluster CPU utilization weighted by node core count.
Aggregate cluster memory utilization.
Number of virtual machines currently running across the cluster.
Number of containers currently running across the cluster.
Aggregate utilization across cluster storage resources.
Current cluster firewall state.
Current high-availability status for the cluster.
Available only when cluster HA data exists.
Cluster backup health and replication entities appear only when their corresponding jobs and runtime data apply.
Overall state of known cluster backup jobs.
Hours since the latest cluster backup task.
Cluster backup health classification based on backup age and state.
Count of failed or non-OK cluster tasks within the last 24 hours.
Number of known replication jobs.
Available when applicable replication inventory or jobs exist.
Overall replication state derived from job runtime and inventory data.
Available when applicable replication inventory or jobs exist.
Time of the latest synchronization for an active replication job; attached to the corresponding VM or CT device.
Created for applicable active replication jobs.
Scheduled time of the next synchronization for an active replication job; attached to the corresponding VM or CT device.
Created for applicable active replication jobs.
Duration of the active replication job's latest synchronization; attached to the corresponding VM or CT device.
Created for applicable active replication jobs.
Identity rules explain why entities remain stable across migrations and why conditional families may not appear in every environment.
Node, storage, mounted-disk and similar resources use identities associated with the relevant PVE environment.
When a PVE entry participates in an active cluster scope, monitored VM and CT identity is cluster-scoped. A guest can migrate between cluster nodes while retaining its Home Assistant identity.
PBS datastore and maintenance identities are server-scoped, so same-named datastores on different PBS servers remain distinct.
Replication measurements use stable job-based identity and attach to the existing VM or CT device.
Many entity families appear only when their feature, resource and source data are available.
Use these checks to locate missing entities and understand environment-dependent Reference content.
Confirm that the related integration resource or device is configured, the feature is enabled, and the entity is not conditional on unavailable data. Also check that the VM, CT, storage or datastore is selected or discovered as required.
Hardware sensors depend on environment-specific sidecar and lm-sensors data. Exact temperature, fan and voltage entities vary by machine.
Review PVE hardware guidanceSMART attributes vary by disk and device type and by the smartctl data available. No physical disk is expected to expose every documented SMART attribute.
ZFS entities exist only when relevant ZFS pool data is detected.
Confirm that the guest is selected or effectively selected for monitoring.
Review VM & CT monitoringReplication entities are conditional and exist only when applicable replication jobs and data are available.
Review Cluster diagnosticsIdentify whether the expected entity belongs to the PBS server, task, datastore or maintenance family, then verify the corresponding server capability and datastore discovery.
Review PBS troubleshootingReference documents entities exposed by the integration. The automatic Dashboard intentionally presents a curated subset and does not display every entity.
Review Dashboard documentationOpen Settings → Devices & services → Proxmox Extended Sensors, choose the relevant device, then open its entity list. The global Entities view can also be filtered by integration, device or entity name.