DumbMonit
IntegrationsVirtualization and containers
Monitor XCP-ng / XenServer with DumbMonit
An XCP-ng or XenServer pool through XAPI: hosts disabled or offline, VMs and their power state, storage repositories filling up, and a high-availability pool that can no longer survive the host failures it is set to tolerate.
DocumentationOfficial website: XCP-ng
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
An XCP-ng or XenServer (Citrix Hypervisor) pool, read through XAPI, the management API every host already runs. No Xen Orchestra is needed.
Typical use. Pool through XAPI: hosts, VMs, storage repositories, high availability
Examples
- XCP-ng 8.2 and 8.3
- XenServer / Citrix Hypervisor
How it connects
What you need
- User name and passwordThe dumbmonit account, registered on the pool as a subject with the read-only role.
Network ports to open
443/TCPXAPI (HTTPS, default)
Setup steps: Give DumbMonit a read-only XAPI account
On every host of the pool, create a local account with a long random password.
useradd -M -s /sbin/nologin dumbmonit passwd dumbmonitOn the pool coordinator, turn on PAM authentication once.
xe pool-enable-external-auth auth-type=PAM service-name=pamRegister the account as a subject and note the UUID it prints.
xe subject-add subject-name=dumbmonitGive that subject the built-in read-only role, with the UUID.
xe subject-role-add uuid=SUBJECT_UUID role-name=read-onlyIn DumbMonit, enter the address of the pool coordinator (for example xcp01.lan) with that user name and password.
Heads-up. If the pool already uses Active Directory, create the account there and skip steps 1 and 2. XCP-ng uses a self-signed certificate: enable "Accept an unverifiable certificate" unless the DumbMonit host trusts it.