---
title: "Metrics Reference"
sidebar_label: "Metrics Reference"
sidebar_position: 3
description: "List of metrics collected for products"
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import {CustomTable} from '@selectel/docux/components'

# Metrics Reference

This instruction describes the product metrics collected by the service.

The list of products that support metrics will be expanded.

## Dedicated Servers \{#dedicated-servers}

Monitoring is supported by servers with a [KVM console](/dedicated/manage/kvm-console.mdx), which is available for every dedicated server, except for the [Chipcore product line](/dedicated/order/dedicated-configurations.mdx#lines) servers and servers in a dedicated rack — see more on the [Servers in a Dedicated Rack](https://selectel.ru/services/dedicated/custom-rack/) page on selectel.ru.

The set of IPMI metrics may differ depending on the server model.

Each metric contains a `timestamp` — the time the metric was collected. You can convert the value using online services, for example, on the [unixtimestamp.com](https://www.unixtimestamp.com/).

<CustomTable>
  <table>
    <thead>
      <tr>
        <th>Metric name<br />Type, unit of measurement</th><th width="53%">Description</th><th width="47%">Labels</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>ipmi\_bmc\_info<br /><small>Gauge, UNIT</small></td><td>BMC (Baseboard Management Controller) metadata — firmware, manufacturer, and others. The metric value is always 1</td>

        <td>
          * `datacenter` — the name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `bmc_url` — BMC address;
          * `firmware_revision` — BMC firmware version;
          * `manufacturer_id` — manufacturer (vendor) ID;
          * `system_firmware_version` — system firmware version (BIOS, UEFI)
        </td>
      </tr>

      <tr>
        <td>up<br /><small>Gauge, bool</small></td>

        <td>
          Checking the availability of the metric source:

          * `1` — successful;
          * `0` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_up<br /><small>Gauge, bool</small></td>

        <td>
          Checking IPMI availability:

          * `1` — successful;
          * `0` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `collector` — name of the exporter's internal collector responsible for collecting a specific group of metrics;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_scrape\_duration\_seconds<br /><small>Gauge, seconds</small></td><td>Time taken for IPMI exporter to collect metrics</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_sel\_events\_count\_by\_state<br /><small>Gauge, count</small></td><td>Number of events from the SEL (System Event Log), grouped by event criticality level</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `state` — event criticality level
        </td>
      </tr>

      <tr>
        <td>ipmi\_chassis\_cooling\_fault\_state<br /><small>Gauge, bool</small></td>

        <td>
          Server cooling system status:

          * `1` — healthy;
          * `0` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_chassis\_drive\_fault\_state<br /><small>Gauge, bool</small></td>

        <td>
          Drive status:

          * `1` — healthy;
          * `0` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_chassis\_power\_state<br /><small>Gauge, bool</small></td>

        <td>
          Server power status:

          * `1` — on;
          * `0` — off
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID
        </td>
      </tr>

      <tr>
        <td>ipmi\_fan\_speed\_state<br /><small>Gauge, enum</small></td>

        <td>
          Fan status:

          * `0` — healthy;
          * `1` — deviation;
          * `2` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor identifier;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_power\_state<br /><small>Gauge, enum</small></td>

        <td>
          Server component power status:

          * `0` — healthy;
          * `1` — deviation;
          * `2` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_temperature\_state<br /><small>Gauge, enum</small></td>

        <td>
          Server component temperature status:

          * `0` — healthy;
          * `1` — deviation;
          * `2` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_voltage\_state<br /><small>Gauge, enum</small></td>

        <td>
          Voltage status:

          * `0` — healthy;
          * `1` — deviation;
          * `2` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_sensor\_state<br /><small>Gauge, enum</small></td>

        <td>
          Server component status:

          * `0` — healthy;
          * `1` — deviation;
          * `2` — failure
        </td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name;
          * `type` — sensor type
        </td>
      </tr>

      <tr>
        <td>ipmi\_fan\_speed\_rpm<br /><small>Gauge, RPM</small></td><td>Fan rotation speed</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_power\_watts<br /><small>Gauge, watts</small></td><td>Power consumption</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_temperature\_celsius<br /><small>Gauge, degrees °C</small></td><td>Server component temperature</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `name` — sensor name;
          * `id` — sensor ID
        </td>
      </tr>

      <tr>
        <td>ipmi\_voltage\_volts<br /><small>Gauge, volts</small></td><td>Voltage</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name
        </td>
      </tr>

      <tr>
        <td>ipmi\_sensor\_value<br /><small>Gauge</small></td><td>IPMI sensor data. The unit of measurement depends on the sensor type</td>

        <td>
          * `datacenter` — name of the data center where the server is hosted;
          * `location_id` — the pool where the server is hosted;
          * `resource_id` — server UUID;
          * `id` — sensor ID;
          * `name` — sensor name;
          * `type` — sensor type
        </td>
      </tr>
    </tbody>
  </table>
</CustomTable>

## Cloud servers \{#cloud-servers}

Metrics are collected at the hypervisor level and reflect the physical state of cloud servers and their resources: CPU, memory, disks, and network. Metric collection does not depend on the OS state. Metrics are collected even if the cloud server is booting, under high load, or unresponsive over the network. Metrics are not collected only when the cloud server is [turned off](/cloud-servers/manage/manage-server.mdx#turn-off-server).

Cloud server namespace – `compute`.

<CustomTable>
  <table>
    <thead>
      <tr>
        <th>Metric name <br />Type, unit of measurement</th><th width="53%">Description</th><th width="47%">Labels</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>server\_meta\_info <br /><small>Gauge, UNIT</small></td><td>Cloud server metadata</td>

        <td>
          <ul>
            <li>`project_name` — project name;</li><li>`server_uuid` — cloud server ID;</li><li>`server_name` — cloud server name</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>server\_state\_info<br /><small>Gauge, UNIT</small></td>

        <td>
          Current cloud server status:

          <ul>
            <li>`0 (no state)` — server state is unknown or undefined;</li><li>`1 (running)` — server is running;</li><li>`2 (blocked)` — server is blocked (waiting for resources or completion of a disk read/write operation);</li><li>`3 (paused)` — server is paused;</li><li>`4 (shutdown)` — server is shutting down;</li><li>`5 (shut off)` — server is stopped and powered off;</li><li>`6 (crashed)` — server has crashed;</li><li>`7 (pmsuspended)` — server is suspended and in sleep mode</li>
          </ul>
        </td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>cpu\_count <br /><small>Gauge, count</small></td><td>Number of vCPUs on the cloud server</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>vcpu\_usage\_ratio <br /><small>Gauge, %</small></td><td>Utilization of each cloud server vCPU in %</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`vcpu` — virtual CPU number</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>cpu\_usage\_ratio <br /><small>Gauge, %</small></td><td>Cloud server CPU utilization in %</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>memory\_total\_bytes <br /><small>Gauge, bytes</small></td><td>Memory size on the cloud server</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>memory\_usage\_bytes <br /><small>Gauge, bytes</small></td><td>Memory size used by the cloud server</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>memory\_usage\_ratio <br /><small>Gauge, %</small></td><td>percentage of RAM used by the cloud server</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>memory\_major\_faults\_total<br /><small>Counter, units</small></td><td>number of major page faults (major page faults) that have occurred on the cloud server since its last startup</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_meta\_info <br /><small>Gauge, UNIT</small></td><td>Cloud server disk metadata</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID;</li><li>`disk_type="network" / "file"` — disk type</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_write\_requests\_rate <br /><small>Gauge, operations/s</small></td><td>Number of write operations per second to the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_read\_requests\_rate <br /><small>Gauge, operations/s</small></td><td>Number of read operations per second from the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_read\_requests\_limit <br /><small>Gauge, operations/s</small></td><td>Maximum number of read operations for the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_write\_requests\_limit <br /><small>Gauge, operations/s</small></td><td>Maximum number of write operations for the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_flush\_requests\_rate <br /><small>Gauge, operations/s</small></td><td>Number of cache flush operations for the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_read\_bytes\_rate <br /><small>Gauge, bytes/s</small></td><td>Number of bytes per second read from the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>disk\_write\_bytes\_rate <br /><small>Gauge, bytes/s</small></td><td>Number of bytes per second written to the cloud server disk</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`disk_uuid` — cloud server disk ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>network\_meta\_info <br /><small>Gauge, UNIT</small></td><td>Metadata of cloud server network interfaces</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`virtual_interface` — cloud server port ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>network\_receive\_packets\_rate <br /><small>Gauge, packets/s</small></td><td>Number of packets per second received on the cloud server network interface</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`virtual_interface` — cloud server port ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>network\_transmit\_packets\_rate <br /><small>Gauge, packets/s</small></td><td>Number of packets per second transmitted through the cloud server network interface</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`virtual_interface` — cloud server port ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>network\_receive\_bits\_rate<br /><small>Gauge, bits/s</small></td><td>Number of bits per second received on the cloud server network interface</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`virtual_interface` — cloud server port ID</li>
          </ul>
        </td>
      </tr>

      <tr>
        <td>network\_transmit\_bits\_rate<br /><small>Gauge, bits/s</small></td><td>Number of bits per second sent through the cloud server network interface</td>

        <td>
          <ul>
            <li>`server_uuid` — cloud server ID;</li><li>`virtual_interface` — cloud server port ID</li>
          </ul>
        </td>
      </tr>
    </tbody>
  </table>
</CustomTable>

<Formbricks />