yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
a41a4e0331fbc0beff63bb28fa59228cc9a751df
doc-exports/docs/ces/umn/ces_faq_2513.html
qiujiandong1 c1d4f578e7 CES UMN 20250530 version 
Reviewed-by: Rumpler, Mihály <mihaly.rumpler@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2025-11-18 06:22:57 +00:00

182 KiB
Raw Blame History

What Metrics Are Supported by the Agent?

The Monitoring Period (Raw Data) of the agent metrics is 1 minute.

OS metric: CPU

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

cpu_usage

(Agent) CPU Usage

Used to monitor CPU usage

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

0-100

%

2.4.1

cpu_usage_idle

(Agent) Idle CPU Usage

Percentage of the time that CPU is idle

Unit: Percent

  • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period.
  • Collection method (Windows): Obtain the metric value using the API GetSystemTimes.

0-100

%

2.4.5

cpu_usage_other

(Agent) Other Process CPU Usage

Other CPU usage of the monitored object

  • Collection method (Linux): Other Process CPU Usage = 1– Idle CPU Usage – Kernel Space CPU Usage – User Space CPU Usage
  • Collection method (Windows): Other Process CPU Usage = 1– Idle CPU Usage – Kernel Space CPU Usage – User Space CPU Usage

0-100

%

2.4.5

cpu_usage_system

(Agent) Kernel Space CPU Usage

Percentage of time that the CPU is used by kernel space

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

0-100

%

2.4.5

cpu_usage_user

(Agent) User Space CPU Usage

Percentage of time that the CPU is used by user space

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

0-100

%

2.4.5

cpu_usage_nice

(Agent) Nice Process CPU Usage

Percentage of the time that the CPU is in user mode with low-priority processes which can easily be interrupted by higher-priority processes

  • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) ni value.
  • Collection method (Windows): not supported

0-100

%

2.4.5

cpu_usage_iowait

(Agent) iowait Process CPU Usage

Percentage of time that the CPU is waiting for I/O operations to complete

  • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) wa value.
  • Collection method (Windows): not supported

0-100

%

2.4.5

cpu_usage_irq

(Agent) CPU Interrupt Time

Percentage of time that the CPU is servicing interrupts

  • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) hi value.
  • Collection method (Windows): not supported

0-100

%

2.4.5

cpu_usage_softirq

(Agent) CPU Software Interrupt Time

Percentage of time that the CPU is servicing software interrupts

  • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) si value.
  • Collection method (Windows): not supported

0-100

%

2.4.5

OS Metric: CPU Load

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

load_average1

(Agent) 1-Minute Load Average

CPU load averaged from the last 1 minute

  • Collection method (Linux): The value of this metric is the result of the value of load1 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load1.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

load_average5

(Agent) 5-Minute Load Average

CPU load averaged from the last 5 minutes

  • Collection method (Linux): The value of this metric is the result of the value of load5 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load5.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

load_average15

(Agent) 15-Minute Load Average

CPU load averaged from the last 15 minutes

  • Collection method (Linux): The value of this metric is the result of the value of load15 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load15.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

OS Metric: Memory

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

mem_available

(Agent) Available Memory

Amount of memory that is available and can be given instantly to processes

  • Collection method (Linux): Obtain the metric value from /proc/meminfo.

    If MemAvailable is displayed in /proc/meminfo, obtain the value.

    If MemAvailable is not displayed in /proc/meminfo, MemAvailable = MemFree + Buffers+Cached

  • Collection method (Windows): formula (Available memory – Used memory) The value is obtained by calling the Windows API GlobalMemoryStatusEx.

≥ 0

GB

2.4.5

mem_usedPercent

(Agent) Memory Usage

Memory usage of the instance

  • Collection method (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 = (MemTotal – MemFree – Buffers – Cached)/MemTotal

  • Collection method (Windows): formula (Used memory size/Total memory size x 100%)

0-100

%

2.4.1

mem_free

(Agent) Idle Memory

Amount of memory that is not being used

  • Collection method (Linux): Obtain the metric value from /proc/meminfo.
  • Collection method (Windows): not supported

≥ 0

GB

2.4.5

mem_buffers

(Agent) Buffer

Amount of memory that is being used for buffers

  • Collection method (Linux): Obtain the metric value from /proc/meminfo. You can run the top command to check the KiB Mem:buffers value.
  • Collection method (Windows): not supported

≥ 0

GB

2.4.5

mem_cached

(Agent) Cache

Amount of memory that is being used for file caches

  • Collection method (Linux): Obtain the metric value from /proc/meminfo. You can run the top command to check the KiB Swap:cached Mem value.
  • Collection method (Windows): not supported

≥ 0

GB

2.4.5

total_open_files

(Agent) Total File Handles

Total handles used by all processes

  • Collection method (Linux): Use the /proc/{pid}/fd file to summarize the handles used by all processes.
  • Collection method (Windows): not supported

≥ 0

Count

2.4.5

OS Metric: Disk

Currently, CES Agent can collect only physical disk metrics and does not support disks mounted using the network file system protocol.

By default, CES Agent will not monitor Docker-related mount points. The prefix of the mount point is as follows:

/var/lib/docker;/mnt/paas/kubernetes;/var/lib/mesos

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

disk_free

(Agent) Available Disk Space

Free space on the disks

  • Collection method (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 (~).
  • Collection method (Windows): Use the Windows Management Instrumentation (WMI) API GetDiskFreeSpaceExW to obtain disk space data. 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

2.4.1

disk_total

(Agent) Disk Storage Capacity

Total disk capacity

  • Collection method (Linux): Run the df -h command to check the value in the Size 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 (~).

  • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. 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

2.4.5

disk_used

(Agent) Used Disk Space

Disk's used space

  • Collection method (Linux): Run the df -h command to check the value in the Used 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 (~).
  • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. 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

2.4.5

disk_usedPercent

(Agent) Disk Usage

Percentage of used disk space. It is calculated as follows: Disk Usage = Used Disk Space/Disk Storage Capacity.

  • Collection method (Linux): It is calculated as follows: Used/Size. 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 (~).
  • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. 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

%

2.4.1

disk_rwstate

(Agent) Disk Read/Write Status

Read and write status of the disk attached to the monitored object. The status can be 0 (read and write) or 1 (read-only).

  • Collection method (Linux): Obtain the disk attachment status from the /proc/1/mountinfo file.
  • Collection method (Windows): not supported
  • 0: read and write
  • 1: read-only

None

2.5.6

OS Metric: Disk I/O

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

disk_agt_read_bytes_rate

(Agent) Disks Read Rate

Volume of data read from the instance per second

  • Collection method (Linux):

    Calculate the data changes in the sixth 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 (~).

  • Collection method (Windows):

    Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

    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 (~).

    When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

≥ 0

byte/s

2.4.5

disk_agt_read_requests_rate

(Agent) Disks Read Requests

Number of read requests sent to the monitored disk per second

  • Collection method (Linux):

    The disk read requests are calculated by calculating the data changes in the fourth 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 (~).

  • Collection method (Windows):

    Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

    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 (~).

    When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

≥ 0

Request/s

2.4.5

disk_agt_write_bytes_rate

(Agent) Disks Write Rate

Volume of data written to the instance per second

  • Collection method (Linux):

    The disk write rate is calculated by calculating the data changes in the tenth 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 (~).

  • Collection method (Windows):

    Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

    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 (~).

    When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

≥ 0

byte/s

2.4.5

disk_agt_write_requests_rate

(Agent) Disks Write Requests

Number of write requests sent to the monitored disk per second

  • Collection method (Linux):

    The disk write requests are calculated by calculating the data changes in the eighth 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 (~).

  • Collection method (Windows):

    Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

    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 (~).

    When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

≥ 0

Request/s

2.4.5

disk_readTime

(Agent) Average Read Request Time

The average time taken for disk read operations

  • Collection method (Linux):

    The average read request time is calculated by calculating the data changes in the seventh 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 (~).

  • Collection method (Windows): not supported

≥ 0

ms/count

2.4.5

disk_writeTime

(Agent) Average Write Request Time

The average time taken for disk write operations

  • Collection method (Linux):

    The average write request time is calculated by calculating the data changes in the eleventh 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 (~).

  • Collection method (Windows): not supported

≥ 0

ms/count

2.4.5

disk_ioUtils

(Agent) Disk I/O Usage

Percentage of the time that the disk has had I/O requests queued to the total disk operation time

  • Collection method (Linux):

    The disk I/O usage is calculated by calculating 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 (~).

  • Collection method (Windows): not supported

0-100

%

2.4.1

disk_queue_length

(Agent) Disk Queue Length

Average number of read or write requests queued up for completion for the monitored disk in the monitoring period

  • Collection method (Linux):

    The average disk queue length is calculated by calculating the data changes in the fourteenth 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 (~).

  • Collection method (Windows): not supported

≥ 0

count

2.4.5

disk_write_bytes_per_operation

Disk Bytes Per Write Operation

Average number of bytes in an I/O write for the monitored disk in the monitoring period

  • Collection method (Linux):

    The average disk write size is calculated by calculating the data changes in the tenth column of the corresponding device to divide that of the eighth column 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 (~).

  • Collection method (Windows): not supported

≥ 0

Byte/op

2.4.5

disk_read_bytes_per_operation

Disk Bytes Per Read Operation

Average number of bytes in an I/O read for the monitored disk in the monitoring period

  • Collection method (Linux):

    The average disk read size is calculated by using the data changes in the sixth column of the corresponding device to divide that of the fourth column 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 (~).

  • Collection method (Windows): not supported

≥ 0

Byte/op

2.4.5

disk_io_svctm

(Agent) Disk I/O Service Time

Average time in an I/O read or write for the monitored disk in the monitoring period

  • Collection method (Linux):

    The average disk I/O service time is calculated by using the data changes in the thirteenth column of the corresponding device to divide the sum of data changes in the fourth and eighth columns 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 (~).

  • Collection method (Windows): not supported

≥ 0

ms/op

2.4.5

disk_device_used_percent

Block Device Usage

Percentage of total disk space that is used. The calculation formula is as follows: Used storage space of all mounted disk partitions/Total disk storage space.

0-100

%

2.5.6

OS Metric: File System

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

disk_fs_rwstate

(Agent) File System Read/Write Status

Read and write status of the mounted file system of the monitored object The status can be 0 (read and write) or 1 (read-only).

  • Collection method (Linux): Check file system information in the fourth column in file /proc/mounts.
  • Collection method (Windows): not supported
  • 0: read and write
  • 1: read-only

None

2.4.5

disk_inodesTotal

(Agent) Disk inode Total

Total number of index nodes on the disk

  • Collection method (Linux): Run the df -i command to check the value in the Inodes 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 (~).
  • Collection method (Windows): not supported

≥ 0

None

2.4.5

disk_inodesUsed

(Agent) Total inode Used

Number of used index nodes on the disk

  • Collection method (Linux): Run the df -i command to check the value in the IUsed 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 (~).
  • Collection method (Windows): not supported

≥ 0

None

2.4.5

disk_inodesUsedPercent

(Agent) Percentage of Total inode Used

Number of used index nodes on the disk

  • Collection method (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 (~).
  • Collection method (Windows): not supported

0-100

%

2.4.1

OS Metric: NTP

Metric

Name

Description

Value Range

Unit

Conversion Rule

Earliest Agent Version Required

ntp_offset

(Agent) NTP Offset

NTP offset of the monitored object

  • Collection method (Linux): Run the ntpq -p or chronyc sources -v command.
  • Collection method (Windows): not supported

≥ 0

ms

N/A

2.7.1

OS Metric: TCP Connections

By default, two basic metrics related to TCP connections are collected: (Agent) TCP TOTAL and (Agent) TCP ESTABLISHED.

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

net_tcp_total

(Agent) Total Number of TCP Connections

Total number of TCP connections

  • Collection method (Linux): Run the ss -s command to view the total number of TCP connections.
    NOTE:

    The number of TCP connections refers to the number of all active TCP connections on an ECS.

  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.1

net_tcp_established

(Agent) Number of connections in the ESTABLISHED state

Number of TCP connections in the ESTABLISHED state

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.1

net_tcp_sys_sent

(Agent) Number of connections in the TCP SYS_SENT state.

Number of TCP connections that are being requested by the client

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_sys_recv

(Agent) Number of connections in the TCP SYS_RECV state.

Number of pending TCP connections received by the server

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_fin_wait1

(Agent) Number of TCP connections in the FIN_WAIT1 state.

Number of TCP connections waiting for ACK packets when the connections are being actively closed by the client

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_fin_wait2

(Agent) Number of TCP connections in the FIN_WAIT2 state.

Number of TCP connections in the FIN_WAIT2 state

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_time_wait

(Agent) TCP TIME_WAIT Connections

Number of TCP connections in the TIME_WAIT state

≥ 0

count

2.4.5

net_tcp_close

(Agent) Number of TCP connections in the CLOSE state.

Number of closed TCP connections

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_close_wait

(Agent) TCP CLOSE_WAIT Connections

Number of TCP connections in the CLOSE_WAIT state

≥ 0

count

2.4.5

net_tcp_last_ack

(Agent) Number of TCP connections in the LAST_ACK state.

Number of TCP connections waiting for ACK packets when the connections are being passively closed by the client

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_listen

(Agent) Number of TCP connections in the LISTEN state.

Number of TCP connections in the LISTEN state

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_closing

(Agent) Number of TCP connections in the CLOSING state.

Number of TCP connections to be automatically closed by the server and the client at the same time

  • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
  • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.

≥ 0

count

2.4.5

net_tcp_retrans

(Agent) TCP Retransmission Rate

Percentage of packets that are resent

  • Collection method (Linux): Obtain the metric value from the /proc/net/snmp file. The value is the ratio of the number of sent packets to the number of retransmitted packages in a collection period.
  • Collection method (Windows): Obtain the metric value using the GetTcpStatistics API.

0-100

%

2.4.5

OS Metric: NIC

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

net_bitRecv

(Agent) Outbound Bandwidth

Number of bits sent by this NIC per second

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

≥ 0

bit/s

2.4.1

net_bitSent

(Agent) Inbound Bandwidth

Number of bits received by this NIC per second

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

≥ 0

bit/s

2.4.1

net_packetRecv

(Agent) NIC Packet Receive Rate

Number of packets received by this NIC per second

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

≥ 0

Count/s

2.4.1

net_packetSent

(Agent) NIC Packet Send Rate

Number of packets sent by this NIC per second

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

≥ 0

Count/s

2.4.1

net_errin

(Agent) Receive Error Rate

Percentage of receive errors detected by this NIC per second

  • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
  • Collection method (Windows): not supported

0-100

%

2.4.5

net_errout

(Agent) Transmit Error Rate

Percentage of transmit errors detected by this NIC per second

  • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
  • Collection method (Windows): not supported

0-100

%

2.4.5

net_dropin

(Agent) Received Packet Drop Rate

Percentage of packets received by this NIC which were dropped per second

  • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
  • Collection method (Windows): not supported

0-100

%

2.4.5

net_dropout

(Agent) Transmitted Packet Drop Rate

Percentage of packets transmitted by this NIC which were dropped per second

  • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
  • Collection method (Windows): not supported

0-100

%

2.4.5

Process Monitoring Metrics

Metric

Name

Description

Value Range

Unit

Earliest Agent Version Required

proc_pHashId_cpu

(Agent) CPU Usage

CPU consumed by a process. pHashId (process name and process ID) is the value of md5.

  • Collection method (Linux): Check the metric value changes in file /proc/pid/stat.
  • Collection method (Windows): Call the Windows API GetProcessTimes to obtain the CPU usage of the process.

0–1 x Number of vCPUs

%

2.4.1

proc_pHashId_mem

(Agent) Memory Usage

Memory consumed by a process. pHashId (process name and process ID) is the value of md5.

  • Collection method (Linux):

    RSS*PAGESIZE/MemTotal

    Obtain the RSS value by checking the second column of file /proc/pid/statm.

    Obtain the PAGESIZE value by running the getconf PAGESIZE command.

    Obtain the MemTotal value by checking file /proc/meminfo.

  • Collection method (Windows): Call the Windows API procGlobalMemoryStatusEx to obtain the total memory size. Call GetProcessMemoryInfo to obtain the used memory size. Use the used memory size to divide the total memory size to get the memory usage.

0-100

%

2.4.1

proc_pHashId_file

(Agent) Number of opened files

Number of files opened by a process. pHashId (process name and process ID) is the value of md5.

  • Collection method (Linux): Run the ls -l /proc/pid/fd command to view the number of opened files.
  • Collection method (Windows): not supported

≥ 0

Count

2.4.1

proc_running_count

(Agent) Running processes

Number of processes that are running

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

proc_idle_count

(Agent) Idle Processes

Number of processes that are idle

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

proc_zombie_count

(Agent) Zombie Processes

Number of zombie processes

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

proc_blocked_count

(Agent) Blocked Processes

Number of processes that are blocked

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

proc_sleeping_count

(Agent) Sleeping Processes

Number of processes that are sleeping

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): not supported

≥ 0

None

2.4.1

proc_total_count

(Agent) Total Processes

Total number of processes on the monitored object

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): Obtain the total number of processes by using the system process status support module psapi.dll.

≥ 0

None

2.4.1

proc_specified_count

(Agent) Specified Processes

Number of specified processes

  • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
  • Collection method (Windows): Obtain the total number of processes by using the system process status support module psapi.dll.

≥ 0

None

2.4.1
Parent topic: Server Monitoring