Help Center/ Elastic Cloud Server/ User Guide/ Cloud Eye Monitoring/ Process Monitoring Metrics Supported by ECSs with the Agent Installed
Updated on 2025-11-25 GMT+08:00
View PDF
Share

Process Monitoring Metrics Supported by ECSs with the Agent Installed

Description

Process monitoring provides monitoring of active processes on ECSs and it requires the Agent to be installed on the ECSs to be monitored. By default, Cloud Eye collects CPU usage, memory usage, and number of opened files of active processes.

This section describes process monitoring metrics reported to Cloud Eye.

Cloud Eye can monitor dimensions nested to a maximum depth of four levels (levels 0 to 3). Level 3 is the deepest level. For example, if the monitored dimension of a metric is instance_id,mount_point, instance_id indicates level 0 and mount_point indicates level 1.

Namespace

AGT.ECS

Process Metrics

After the agent is installed, you can view the default process metrics listed in the following table, regardless of ECS types and OSs.

Table 1 Process metrics

Metric

Parameter

Description

Value Range

Unit

Conversion Rule

Dimension

Monitoring Period (Raw Data)

proc_pHashId_cpu

(Agent) Process CPU Usage

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

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

0–1 x Number of vCPUs.

%

N/A

instance_id

1 minute

proc_pHashId_mem

(Agent) Process Memory Usage

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

  • 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.

  • 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

%

N/A

instance_id

1 minute

proc_pHashId_file

(Agent) Process Open Files

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

  • Linux: Run the ls -l /proc/pid/fd command to view the number of opened files.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_running_count

(Agent) Running Processes

Number of processes that are running

  • 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.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_idle_count

(Agent) Idle Processes

Number of processes that are idle

  • 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.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_zombie_count

(Agent) Zombie Processes

Number of zombie processes

  • 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.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_blocked_count

(Agent) Blocked Processes

Number of processes that are blocked

  • 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.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_sleeping_count

(Agent) Sleeping Processes

Number of processes that are sleeping

  • 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.
  • Windows is not supported currently.

≥0

Count

N/A

instance_id

1 minute

proc_total_count

(Agent) Total Processes

Total number of processes on the monitored object

  • 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.
  • Windows: Obtain the total number of processes from the modules supported by the psapi.dll system process statuses.

≥0

Count

N/A

instance_id

1 minute

proc_specified_count

(Agent) Specified Processes

Number of specified processes

  • 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.
  • Windows: Obtain the total number of processes from the modules supported by the psapi.dll system process statuses.

≥0

Count

N/A
  • instance_id
  • instance_id,proc

1 minute

specified_process_file

(Agent) Files Opened by a Process

Number of files opened by a specific process of the monitored object

  • Linux: Run the ls -l /proc/pid/fd command to view the number of opened files.
  • Windows is not supported currently.

≥0

Count

N/A
  • instance_id
  • instance_id,proc

1 minute

Dimensions

Dimension

Key

Value

ECS

instance_id

Specifies the ECS ID.

You can obtain the value by referring to Querying the Original Dimension Values in Server Monitoring.

ECS - Process

proc

Specifies the ECS process.

You can obtain the value by referring to Querying the Original Dimension Values in Server Monitoring.

Example of Querying Multi-Level Dimension Metrics Using APIs

If an object has multiple dimension levels, you need to specify the monitored dimension levels when you use an API to query the metrics of this object.

For example, if you want to query the remaining storage capacity (disk_free) of a disk mount point for an ECS, the dimension of the metric is instance_id,mount_point, where instance_id indicates level 0 and mount_point indicates level 1.

  • To query a single metric by calling an API, the mount_point dimension is used as follows: 
    dim.0=instance_id,3d65c1ac-9a9f-4c5f-a054-35184a087bb2&dim.1=mount_point,6666cd76f96956469e7be39d750cc7d9

    3d65c1ac-9a9f-4c5f-a054-35184a087bb2 and 6666cd76f96956469e7be39d750cc7d9 are the values of instance_id and mount_point, respectively. For details about how to obtain the values, see the obtaining guide in the Dimension table.

  • To query multiple metrics by calling an API, the mount_point dimension is used as follows: 
    "dimensions": [ 
                { 
                    "name": "instance_id", 
                    "value": "3d65c1ac-9a9f-4c5f-a054-35184a087bb2"    
                }, 
                { 
                    "name": "mount_point", 
                    "value": "6666cd76f96956469e7be39d750cc7d9" 
                } 
            ]

    3d65c1ac-9a9f-4c5f-a054-35184a087bb2 and 6666cd76f96956469e7be39d750cc7d9 are the values of instance_id and mount_point, respectively. For details about how to obtain the values, see the obtaining guide in the Dimension table.

Parent Topic: Cloud Eye Monitoring