Skip to main content

View cloud server resource metrics

You can view cloud server resource metrics as graphs in the control panel.

Metric collection does not depend on the guest OS state. Metrics are collected even if the cloud server is booting, is under high load, or is not responding over the network. Metrics are only not collected when the cloud server is powered off.

Values for all metrics are collected every minute. If you have just created a server, the first values for network interface and volume metrics will appear in a few minutes.

View resource usage metrics

  1. In the Control panel, on the top menu, click Products and select Cloud Servers.

  2. Open the server page → Metrics tab.

  3. Optional: filter the metrics:

    3.1. Select a preset range or specify a period for which you need the metrics.

    3.2. Select UTC time or Local time for the displayed metric time.

  4. View the charts for the available cloud server metrics.

  5. If any metrics are not being collected on a cloud server, add the Virtio kernel modules to autoload.

Cloud server metrics in the control panel

CPU
  • vCPU load percentage of the cloud server;
  • load percentage of each vCPU of the cloud server
Memory
  • used RAM excluding operating system cache and buffers in bytes;
  • RAM usage percentage excluding operating system cache and buffers
Volume
  • number of read and write operations in IOPS;
  • number of bytes per second read from or written to the disk
Network
  • incoming and outgoing traffic in bits per second;
  • incoming and outgoing traffic speed in packets per second

Add VirtIO kernel modules to autostart

To collect metrics, VirtIO drivers must be installed on the cloud server. In modern Linux distributions, VirtIO drivers are installed by default.

If some cloud server load metrics are not being collected, add the VirtIO kernel modules to autostart.

  1. Connect to the server.

  2. Open the /etc/modules file in the nano:

    nano /etc/modules

  3. Add the modules:

    virtio_blk
    virtio_scsi
    virtio_balloon
    virtio_net

  4. Perform a soft reboot of the server. The modules will start automatically.