InfrastructureCloud VMs

Monitoring

The Monitoring tab on the server detail page shows live metrics and a history of recent operations. Use it to spot saturation, validate resize impact, and confirm that automated jobs (backups, snapshots, restores) ran as expected.

Open monitoring

  1. Go to Cloud VMs in the IBEE Solutions portal.
  2. Click your VM to open the detail page.
  3. Open the Monitoring tab.

The header shows when metrics were last updated and the sample interval (typically 1-minute intervals). Use the time range buttons to switch between 30m, 1h, 6h, 24h, and 7d. Click Refresh to force an immediate sample.

Compute metrics

MetricSourceWhat it shows
CPU UtilizationHost-side libvirtVM CPU % across all allocated vCPUs. Spikes above the plan’s vCPU count indicate steal pressure.
Memory UtilizationHost-side libvirt (when available)Memory used vs. allocated, in MB. Falls back to balloon stats when the guest agent is unavailable.

A current value and last sample timestamp are shown above each chart.

Storage and disk metrics

MetricSourceWhat it shows
Storage UtilizationQEMU guest agentGuest filesystem usage as a percentage and absolute used/total. Requires the guest agent to be installed.
Disk Throughputlibvirt block countersRead and write throughput (B/s, KB/s, MB/s).
Disk IOPSlibvirt block countersRead and write operations per second.

If Storage Utilization is missing, install or start qemu-guest-agent inside the VM:

$sudo apt-get install -y qemu-guest-agent
$sudo systemctl enable --now qemu-guest-agent

Throughput and IOPS metrics work without the guest agent.

Network metrics

The Network chart plots inbound and outbound traffic in bits or bytes per second. Use it together with the bandwidth allowance for your plan (Instance types) to estimate monthly egress.

Activity feed

The Activity section lists recent VM events with a timestamp and short status:

EventMeaning
Operation AcceptedThe control plane queued the operation.
Operation StartedThe hypervisor or storage layer began executing it.
Operation SucceededThe operation completed successfully.
Operation FailedThe operation did not complete; check the message and retry, or contact support.

Common operations you’ll see:

  • VM create — initial provisioning
  • VM attach_volume / VM detach_volume — block storage changes
  • VM start, VM stop, VM reboot — power actions
  • VM snapshot_create, VM snapshot_restore — recovery point operations
  • VM backup_create — scheduled backup runs

Tips

  • Investigate CPU sustained above 80% before resizing — many workloads are I/O- or memory-bound.
  • A flat Memory Utilization line near 100% with low free RAM is a strong signal to upsize.
  • If Disk Throughput plateaus while CPU has headroom, you may be hitting the disk’s IOPS ceiling — consider attaching faster Block Storage.
  • Use the 24h range to see backup or snapshot windows; expect a small CPU and disk bump during those windows.