Help Center/ Workspace/ User Guide (Administrators)/ Monitoring/ Cloud Eye OS Monitoring Metrics Supported by Workspace (with Agent Installed)
Updated on 2025-08-20 GMT+08:00

Cloud Eye OS Monitoring Metrics Supported by Workspace (with Agent Installed)

Functions

You can install the Agent plug-in on a desktop to provide system-level, proactive, and fine-grained monitoring of servers. This section describes the OS monitoring metrics reported by Workspace to Cloud Eye.

GPU monitoring metrics are supported.

OS monitoring supports metrics about CPU, CPU load, memory, disk, disk I/O, file system, NIC, TCP, and GPU.

After installing the Agent, you can view OS monitoring metrics of ECSs running different OSs. Monitoring data is collected every one minute.

  • OS monitoring metrics: CPU
    Table 1 CPU monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    cpu_usage

    (Agent) CPU Usage

    CPU usage of the monitored object.

    Unit: %

    • Linux: Check metric value changes in file /proc/stat in a collection period. Run the top command to check the %Cpu(s) value.
    • Windows: Obtain the metric value using the Windows API GetSystemTimes.

    0–100%

    Cloud desktop

    1 minute

  • OS monitoring metrics: Memory
    Table 2 Memory monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    mem_usedPercent

    (Agent) Memory Usage

    Memory usage of the monitored object.

    Unit: %

    • Linux: Obtain the metric value from the /proc/meminfo file: (MemTotal - MemAvailable)/MemTotal
      • If MemAvailable is displayed in /proc/meminfo, MemUsedPercent = (MemTotal - MemAvailable)/MemTotal
      • If MemAvailable is not displayed in /proc/meminfo, MemUsedPercent = (MemTotalMemFreeBuffersCached)/MemTotal
    • Windows: The calculation formula is as follows: Used memory size/Total memory size x 100%.

    0–100%

    Cloud desktop

    1 minute

  • OS monitoring metrics: NIC
    Table 3 NIC monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    net_bitRecv

    (Agent) Outbound Bandwidth

    Number of bits sent by this NIC per second.

    Unit: bit/s

    • Linux: Check metric value changes in file /proc/net/dev in a collection period.
    • Windows: Use the MibIfRow object in the WMI to obtain network metric data.

    ≥ 0 bit/s

    Cloud desktop

    1 minute

    net_bitSent

    (Agent) Inbound Bandwidth

    Number of bits received by this NIC per second.

    Unit: bit/s

    • Linux: Check metric value changes in file /proc/net/dev in a collection period.
    • Windows: Use the MibIfRow object in the WMI to obtain network metric data.

    ≥ 0 bit/s

    Cloud desktop

    1 minute

    net_packetRecv

    (Agent) NIC Packet Receive Rate

    Number of packets received by this NIC per second.

    Unit: count/s

    • Linux: Check metric value changes in file /proc/net/dev in a collection period.
    • Windows: Use the MibIfRow object in the WMI to obtain network metric data.

    ≥ 0

    Cloud desktop

    1 minute

    net_packetSent

    (Agent) NIC Packet Send Rate

    Number of packets sent by this NIC per second.

    Unit: count/s

    • Linux: Check metric value changes in file /proc/net/dev in a collection period.
    • Windows: Use the MibIfRow object in the WMI to obtain network metric data.

    ≥ 0

    Cloud desktop

    1 minute

  • OS monitoring metric: Disk
    Table 4 Disk monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    disk_free

    (Agent) Available Disk Space

    Available disk space on the monitored object.

    Unit: GB

    • Linux: Run the df -h command to check the value in the Avail column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
    • Windows: Obtain the metric value using the WMI API GetDiskFreeSpaceExW. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

    ≥ 0 GB

    Cloud desktop

    1 minute

    disk_usedPercent

    (Agent) Disk Usage

    Percentage of total disk space that is used, which is calculated as follows: Disk Usage = Used Disk Space/Disk Storage Capacity.

    Unit: %

    • Linux: Obtain the metric value using the following formula: Disk Usage = Used Disk Space/Disk Capacity. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
    • Windows: Obtain the metric value using the WMI API GetDiskFreeSpaceExW. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

    0–100%

    Cloud desktop

    1 minute

  • OS monitoring metric: File system
    Table 5 File system monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    disk_inodesUsedPercent

    (Agent) Percentage of Total inode Used

    Percentage of used inodes on the disk of the monitored object.

    Unit: %

    Linux: Run the df -i command to check the value in the IUse% column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

    0–100%

    Cloud desktop

    1 minute

  • OS monitoring metric: Disk I/O
    Table 6 Disk I/O monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    disk_ioUtils

    (Agent) Disk I/O Usage

    Disk I/O usage of the monitored object.

    Unit: %

    • Linux:

      The disk I/O usage is calculated based on the data changes in the thirteenth column of the corresponding device in file /proc/diskstats in a collection period.

      The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

    • Windows does not support this metric.

    0–100%

    Cloud desktop

    1 minute

  • OS monitoring metric: GPU
    Table 7 GPU monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    gpu_aggregate_correctable

    Aggregate Correctable ECC Errors

    Aggregate correctable ECC errors on the GPU.

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

    gpu_aggregate_uncorrectable

    Aggregate Uncorrectable ECC Errors

    Aggregate uncorrectable ECC errors on the GPU.

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

    gpu_performance_state

    (Agent) Performance Status

    GPU performance of the monitored object.

    Unit: none

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    P0-P15, P32

    • P0: indicates the maximum performance status
    • P15: indicates the minimum performance status
    • P32: indicates the unknown performance status

    Cloud desktop

    1 minute

    gpu_retired_page_double_bit

    Retired Page Double Bit Errors

    Number of retired page double-bit errors, which indicates the number of double-bit pages blocked by the GPU

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

    gpu_retired_page_single_bit

    Retired Page Single Bit Errors

    Number of retired page single-bit errors, which indicates the number of single-bit pages blocked by the GPU.

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

    gpu_status

    GPU Health Status

    Overall measurement of the GPU health.

    Unit: none

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.
    • 0: healthy
    • 1: subhealthy
    • 2: faulty

    Cloud desktop

    1 minute

    gpu_usage_decoder

    Decoding Usage

    Decoding capability usage of the GPU.

    Unit: %

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    0–100%

    Cloud desktop

    1 minute

    gpu_usage_encoder

    Encoding Usage

    Encoding capability usage of the GPU.

    Unit: %

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    0–100%

    Cloud desktop

    1 minute

    gpu_usage_gpu

    (Agent) GPU Usage

    GPU usage of the monitored object.

    Unit: %

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    0–100%

    Cloud desktop

    1 minute

    gpu_usage_mem

    (Agent) GPU Memory Usage

    GPU memory usage of the monitored object.

    Unit: %

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    0–100%

    Cloud desktop

    1 minute

    gpu_volatile_correctable

    Volatile Correctable ECC Errors

    Number of correctable ECC errors since the GPU is reset. The value is reset to 0 each time the GPU is reset.

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

    gpu_volatile_uncorrectable

    Volatile Uncorrectable ECC Errors

    Number of uncorrectable ECC errors since the GPU is reset. The value is reset to 0 each time the GPU is reset.

    Unit: count

    • Linux: Obtain the metric value using the libnvidia-ml.so.1 library file of the GPU.
    • Windows: Obtain the metric value using the nvml.dll library of the GPU.

    ≥ 0

    Cloud desktop

    1 minute

  • OS monitoring metric: CPU load
    Table 8 CPU load monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    load_average1

    (Agent) 1-Minute Load Average

    CPU load averaged from the last one minute.

    Linux: Obtain the metric value from the number of logic CPUs in load1/ in file /proc/loadavg. You can run the top command to check the value of load1.

    ≥ 0

    Cloud desktop

    1 minute

    load_average5

    (Agent) 5-Minute Load Average

    CPU load averaged from the last five minutes.

    Linux: Obtain the metric value from the number of logic CPUs in load5/ in file /proc/loadavg. You can run the top command to check the value of load5.

    ≥ 0

    Cloud desktop

    1 minute

    load_average15

    (Agent) 15-Minute Load Average

    CPU load averaged from the last 15 minutes.

    Linux: Obtain the metric value from the number of logic CPUs in load15/ in file /proc/loadavg. You can run the top command to check the value of load15.

    ≥ 0

    Cloud desktop

    1 minute

  • OS monitoring metric: TCP
    Table 9 TCP monitoring metrics

    Metric

    Name

    Description

    Value Range

    Monitored Object (Dimension)

    Monitoring Period (Raw Data)

    net_tcp_total

    (Agent) TCP TOTAL

    Total number of TCP connections in all statuses.

    Unit: count

    • Linux: Obtain TCP connections in all statuses from the /proc/net/tcp file, and then collect the number of connections in each status.
    • Windows: Obtain the metric value using the Windows API GetTcpTable2.

    ≥ 0

    Cloud desktop

    1 minute

    net_tcp_established

    (Agent) TCP ESTABLISHED

    Number of TCP connections in the ESTABLISHED status.

    Unit: count

    • Linux: Obtain TCP connections in all statuses from the /proc/net/tcp file, and then collect the number of connections in each status.
    • Windows: Obtain the metric value using the Windows API GetTcpTable2.

    ≥ 0

    Cloud desktop

    1 minute