DumbMonit
ИнтеграцииВиртуализация и контейнеры
Мониторинг Proxmox VE в DumbMonit
Nodes, virtual machines, containers, storage and backups of a Proxmox server or cluster.
ДокументацияОфициальный сайт: Proxmox VE
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет 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.
Типичное применение. Hypervisor, cluster
Примеры
- Proxmox server
- Proxmox cluster
Как подключается
Что понадобится
- 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.
Сетевые порты, которые нужно открыть
8006/TCPAPI (HTTPS, default)
Шаги настройки: 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).
Обратите внимание. 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).