Proxmox monitoring

Proxmox VM and LXC monitoring in one dashboard

Keep Proxmox guest state and resource usage beside the machine that runs them. Install statsd on the node to discover virtual machines and LXC containers through the local Proxmox tools.

Start free →Set up monitoring ↓
Proxmox guestsIllustrative data · not a live reading
GuestTypeStateMemory
100 · ubuntu-webVMrunning2.1 GB
200 · piholeLXCrunning96 MB
201 · backupLXCstopped—

What you can monitor

Virtual machines

See VM identity, running state and resource usage without switching away from the host overview. Use guest CPU and memory readings to find the workloads that need attention.

LXC containers

View LXC guests beside virtual machines. Keep stopped guests visible so an intentionally stopped container is distinguishable from a workload you expected to be running.

Node resources

Use the same agent for node CPU, memory, disks and network interfaces. Check host pressure alongside guest usage when a workload becomes slow.

Install statsd on each Proxmox node

  1. 1. Run the Linux installer on the node

    Create a System Stats account and open a shell on the Proxmox node itself. The native agent uses systemd and needs root or sudo access. Omit sudo when already running as root.

    Terminal
    curl -fsSL https://linux-stats.com/install.sh | sh
sudo statsd login
sudo statsd status

  2. 2. Approve the machine in your browser

    Open the authorization link on any device, sign in and approve the node. The CLI and background service must use the same configuration directory.

  3. 3. Verify the node and its guests

    Open the dashboard and check that guest state and resource readings arrive. If the Proxmox module is unavailable, confirm the local Proxmox tools are accessible to the service.

    Terminal
    sudo statsd doctor
sudo statsd interval proxmox

What the Proxmox agent can see

Requires the local Proxmox tools on a Proxmox node. The default collection interval is 5s. Change it with statsd interval proxmox using the service configuration directory.

Install the agent on every node you want to monitor. An agent inside an ordinary VM or LXC guest does not gain access to the hypervisor or discover the other guests on that node.

Node-side guest readings and operating-system metrics inside a guest are different views. Install a separate agent inside a guest when you need its own disks, interfaces and other system metrics.

Plan machine limits apply to registered machines. Registering another agent inside a guest uses another machine slot; compare plan limits before instrumenting an entire fleet.

Explore monitoring for your systems

Docker monitoring →

See which containers are running, how much CPU and memory they use, and whether their health checks are passing. System Stats brings Docker and machine metrics into the same dashboard.

Linux server monitoring →

Monitor Linux servers, ARM machines and Raspberry Pi from one dashboard. The statsd agent runs as a background service and collects the system metrics you need to investigate resource pressure.

HTTP uptime monitoring →

Check whether an endpoint responds as expected, how long it takes, and when it becomes unavailable. Keep uptime and response-time history beside the machines and containers behind your service.

Install the agent and see it all

Free up to 5 machines forever. No credit card. Two minutes from landing here to live metrics streaming in.

Start free → Talk to us