HYPHAby S33D
Documentation › Integrations

Hypervisors: vSphere, Proxmox VE, Hyper-V, KVM and VirtualBox

The state of hypervisors and their VMs, read-only, next to the agents installed inside the VMs.

VMware vSphere (ESXi and vCenter)

No agent goes on an ESXi host: an agent of your fleet queries the vSphere API with an account holding the ReadOnly role.

integrations:
  vsphere:
    interval: 60s
    targets:
      - name: vcenter
        url: https://vcenter.example/sdk
        username: hypha@vsphere.local
        password: "…"
        thumbprint: "AA:BB:…"     # SHA-1 fingerprint of a self-signed certificate
        # insecure: true          # avoid: accepts any certificate
        tags: {site: paris}

What HYPHA collects:

ESXi hosts and VMs become resources in Infrastructure. A VM that also runs a HYPHA agent is matched to its host by serial number ("VMware-…"): one line, and its page shows what vSphere says about it.

Proxmox VE

Two ways to read the cluster:

integrations:
  proxmox:
    url: https://pve.example:8006
    token_id: "hypha@pve!readonly"
    token_secret: "…"
    ca_file: /etc/hypha/pve-ca.pem

Checks: cluster quorum, node offline, storage unavailable, HA guest out of its requested state, last backup (vzdump) of each node failing, cleared as soon as the next one succeeds. Metrics for nodes, storages and guests (VMs and containers). Failed tasks become events.

Hyper-V

On Windows, the agent reads Get-VM when the Hyper-V service is present; no setting needed.

KVM and libvirt

On the host, virsh read-only (qemu:///system by default, set by uri).

VirtualBox

The host's agent collects the declared and running VMs, and reports an autostart VM that is stopped (virtualbox.vm.running). The user setting follows a single account.

Monitor templates

The Virtualization family of the catalogue: vSphere connector failing, ESXi host faulty, datastore inaccessible or almost full, vSphere VM faulty, old snapshot; Proxmox unreachable, quorum lost, node offline, storage unavailable or almost full, HA guest out of its state, backup failing; Hyper-V VM faulty, old checkpoint, degraded replication; KVM VM faulty, pool inactive or almost full.

Updated: 19 November 2026