DumbMonit
IntegrationsStorage and backups
Monitor Proxmox Backup Server with DumbMonit
Backup freshness per machine, failed tasks, sync and verify jobs, datastore space.
DocumentationOfficial website: Proxmox Backup Server
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
Backup server: a thirty-day backup calendar per machine, failed tasks with their logs, scheduled jobs (sync, verify, prune, garbage collection), datastores, disks and ZFS pools, pending updates, the services and package versions of the server itself, and the tape tier when there is one.
Typical use. Backup server
Examples
- Proxmox Backup Server
How it connects
What you need
- 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.
Network ports to open
8007/TCPAPI (HTTPS, default)
Setup steps: Create a read-only user and token in Proxmox Backup Server
Open Configuration → Access Control → User Management → Add, enter the user name dumbmonit, choose the realm Proxmox Backup authentication server, then click Add.
dumbmonit@pbsOpen Configuration → Access Control → API Token → Add: user dumbmonit@pbs, token name monitor. Copy the Token ID and the Secret now, the secret is shown only once.
dumbmonit@pbs!monitorOpen Configuration → Access Control → Permissions → Add → User Permission: path /, user dumbmonit@pbs, role Audit.
Add a second permission with Add → API Token Permission: path /, token dumbmonit@pbs!monitor, role Audit. A token has its own permissions, so both are needed.
Optional, to see pull sync jobs and the tape tier: repeat both permissions with role RemoteAudit on path /remote and role TapeAudit on path /tape.
In DumbMonit, enter the server address (for example pbs.lan:8007), the Token ID and the Secret.
Heads-up. Both the user and the token need the permission: given to the token alone, it grants nothing and PBS reports nothing. The server uses a self-signed certificate by default: tick "Accept an unverifiable certificate" in the options if the connection is refused.