DumbMonit
IntegrazioniVirtualizzazione e container
Monitorare Proxmox VE con DumbMonit
Nodes, virtual machines, containers, storage and backups of a Proxmox server or cluster.
DocumentazioneSito ufficiale: Proxmox VE
Le descrizioni sono in inglese, come nel prodotto. Le etichette della pagina seguono la tua lingua.
Cosa controlla DumbMonit
Hypervisor: nodes with their daemons and networking, virtual machines, containers, storages, LVM thin pools, backups, high availability, snapshots, replication, Ceph down to the OSD, physical disks and ZFS pools, pending updates, package changes, subscription and certificates. One monitor can cover a whole cluster.
Uso tipico. Hypervisor, cluster
Esempi
- Proxmox server
- Proxmox cluster
Come si collega
Cosa serve
- API token (recommended)No expiry and no session opened: the right choice for monitoring.
- Username / passwordOpens a two-hour session, renewed automatically. Use it only if tokens are not an option.
Porte di rete da aprire
8006/TCPAPI (HTTPS, default)
Passaggi di configurazione: Create a read-only user and token in Proxmox VE
Open Datacenter → Permissions → Users → Add, enter the user name dumbmonit, choose the realm Proxmox VE authentication server, then click Add.
dumbmonit@pveOpen Datacenter → Permissions → Add → User Permission: path /, user dumbmonit@pve, role PVEAuditor, then click Add.
Open Datacenter → Permissions → API Tokens → Add: user dumbmonit@pve, Token ID monitor, untick Privilege Separation, then click Add.
dumbmonit@pve!monitorCopy the Token ID and the Secret into DumbMonit's Token ID and Secret fields. The secret is shown only once.
Optional, for the pending-updates count: Datacenter → Permissions → Roles → Create a role with only Sys.Modify, then add it as a User Permission on path /nodes.
In DumbMonit, enter the address of any node (port 8006 by default).
Attenzione. Proxmox VE uses a self-signed certificate by default: tick "Accept an unverifiable certificate" in the options if the connection is refused. On Proxmox VE 8, guest agent details also need VM.Monitor (see the guide).