Process Monitoring

Prerequisites

Ensure that the Cloud Eye Agent has been installed on a server. For details, see Installing the Agent.

Constraints

There's no limit on the number of processes to be added, but the Agent collects only the first 16 processes.

Adding Process Monitoring

Process monitoring is used to monitor active processes on a host. By default, the Agent collects information such as CPU usage, memory usage, and the number of opened files of these processes. Customized process monitoring can collect the number of key processes and obtain the status of key processes at any time.

Modifying a Process Monitoring Task

1. Log in to the Cloud Eye console.
2. Choose Server Monitoring > Process Monitoring.
3. Locate the target process monitoring task and click Modify in the Operation column. The Modify Process Monitoring page is displayed.
4. Modify the description, specified resources, and name of the monitored process. For details about the parameters, see Table 2.
   Figure 3 Modify a process monitoring task
   
5. Click OK.

Deleting a Process Monitoring Task

1. Log in to the Cloud Eye console.
2. Choose Server Monitoring > Process Monitoring.
3. Locate the target process monitoring task and click Delete in the Operation column.
4. In the Delete Monitored Process dialog box, enter DELETE and click OK.
   Figure 4 Delete Monitored Process
   

Viewing Process Monitoring Metrics

1. Log in to the Cloud Eye console.
2. Choose Server Monitoring > Process Monitoring.
3. Click in the Monitoring column of a process monitoring task to go to the View Metric page.
4. Set Instance, Process Name, and Process ID to view the CPU usage, memory usage, and number of opened files of a specified process in line graphs. For details about related metrics, see Table 3.
5. On the View Metric page, select a monitoring period (Last 15 min, Last 30 min, Last 1h, Last 2h, Last 3h, Last 12h, Last 1d, Last 7d, or Last 30d), or select Select Range to customize one to view historical monitoring data from the last 155 days.

Viewing Custom Process Monitoring

1. Log in to the Cloud Eye console.
2. Perform the following operations based on the resources to be viewed:
   • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
   • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
3. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
4. Select the Process Monitoring tab.
5. Under Custom Process Monitoring, locate a custom process and click on the left of the process name.
6. Locate the row containing the target process ID and click View Details in the Operation column. On the View Metric drawer that is slid out, view the CPU usage, memory usage, and number of opened files of the current process. For details about the metrics, see Table 3. Above the graphs, Time Range can be Last 1h, Last 3h, Last 12h, Last 1d, or Last 7d. You can also customize the time range to view historical monitoring data for any period within the last 155 days.
7. In the Custom Processes area, details of custom processes running on the host is displayed.

   Table 3 Process Monitoring metrics

   Metric	Description	Value Range	Collection (Linux)	Collection (Windows)
   CPU Usage	CPU consumed by a process	0 to 1 x Number of CPU cores	Monitored object: ECS or BMS Check the metric value changes in the /proc/pid/stat file.	Monitored object: ECS or BMS Call the API GetProcessTimes to obtain the CPU usage of the process.
   Memory Usage	Memory consumed by a process	0-1	Monitored object: ECS or BMS Memory Usage = RSS x PAGESIZE/MemTotal RSS: Obtain its value by checking the second column of the /proc/pid/statm file. PAGESIZE: Obtain its value by running the getconf PAGESIZE command. MemTotal: Obtain its value from the /proc/meminfo file.	Monitored object: ECS or BMS Call 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.
   Opened Files	The number of opened files consumed by the process	≥ 0	Monitored object: ECS or BMS You can run the ls -l /proc/pid/fd command to view the number.	Monitored object: ECS or BMS Run Windows API NtQuerySystemInformation to obtain information about all opened handles in the system, check whether each handle is a file handle opened by the current process, and obtain the number of files opened by the current process. In Windows, the specified_process_file metric of some processes cannot be collected due to causes like insufficient permissions.

Enabling Alarm Notifications for Custom Process Monitoring

You can configure alarm notifications. When the number of processes decreases or increases, Cloud Eye will notify you immediately.

1. Log in to the Cloud Eye console.
2. Perform the following operations based on the resources to be viewed:
   • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
   • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
3. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
4. Select the Process Monitoring tab.
5. On the Custom Process Monitoring page, create an alarm rule for a process by using either of the following methods:
   • Locate a process and click Create alarm rules in the Operation column.
   • Click the icon next to the process name and click Create Alarm Rule in the row where the process ID is located.
6. Configure basic information about the alarm rule. For details, see Creating an Alarm Rule and Notifications.

Querying the System Processes

After the Agent is installed, you can check system processes on Cloud Eye.

To query the number of processes, perform the following steps:

1. Log in to the Cloud Eye console.
2. Perform the following operations based on the resources to be viewed:
   • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
   • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
3. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
4. Select the Process Monitoring tab.
   In the System Processes area, the process information is displayed. Table 4 describes the metrics of system processes.

   Table 4 System process metrics

   Metric	Description	Value Range	Collection (Linux)	Collection (Windows)
   Running Processes	Number of processes that are running	≥ 0	Monitored object: ECS or BMS 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.	Not supported
   Idle Processes	Number of processes that are idle	≥ 0	Monitored object: ECS or BMS 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.	Not supported
   Zombie Processes	Number of zombie processes	≥ 0	Monitored object: ECS or BMS 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.	Not supported
   Blocked Processes	Number of processes that are blocked	≥ 0	Monitored object: ECS or BMS 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.	Not supported
   Sleeping Processes	Number of processes that are sleeping	≥ 0	Monitored object: ECS or BMS 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.	Not supported
   Total Processes	Total number of processes	≥ 0	Monitored object: ECS or BMS 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.	Monitored object: ECS or BMS Obtain the total number of processes by using the system process status support module psapi.dll.

Viewing Top Processes with the Highest CPU Usage

• The Agent collects process CPU usages every minute and displays the top 5 processes, ranked by the CPU usage over the last 24 hours.
• Run the top command to query the CPU usage and memory usage of a process.
• Run the lsof or ls /proc/pid/fd |wc -l command to query the number of files opened by the current process. In the command, replace pid with the ID of the process to be queried.
  

  • If a process occupies multiple CPUs, the CPU usage may exceed 100% because the collection result is the total usage of multiple CPUs.
  • The top 5 processes are not fixed. The process list displays the top 5 processes that have entered the statistical period of 1 minute in the last 24 hours.
  • The CPU usage, memory usage, and number of opened files are collected only for the top 5 processes for which monitoring has been enabled in the last 24 hours. If such a process has been stopped, its data will not be displayed.
  • The time in the list indicates the time when a process was created.
  • If the system time on the client browser is different from that on the monitored ECS, the graph may not show any metric data. In this case, synchronize the local time with the ECS time.
  • The Agent of the new version no longer reports data on the top 5 processes, and process monitoring will become unavailable. You are advised to use Custom Process Monitoring instead.

To query information about the top 5 processes with the highest CPU usages

1. Log in to the Cloud Eye console.
2. Perform the following operations based on the resources to be viewed:
   • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
   • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
3. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
4. Select the Process Monitoring tab.
5. Click Configure under TOP 5 Processes with Highest CPU Usage.
6. In the displayed TOP 5 Processes with Highest CPU Usage dialog box, enable monitoring for target processes and click OK.

   Locate a process and click View Details in the Operation column. On the View Metric drawer that is slid in, view the CPU usage, memory usage, and number of opened files of the process. For details about the metrics, see Table 5. Above the graphs, Time Range can be Last 1h, Last 3h, Last 12h, Last 1d, or Last 7d. You can also customize the time range to view historical monitoring data for any period within the last 155 days.

   Table 5 Process Monitoring metrics

   Metric	Description	Value Range	Collection (Linux)	Collection (Windows)
   CPU Usage	CPU consumed by a process pHashId (process name and process ID) is the value of md5.	0 to 1 x Number of CPU cores	Monitored object: ECS or BMS Check the metric value changes in the /proc/pid/stat file.	Monitored object: ECS or BMS Call the API GetProcessTimes to obtain the CPU usage of the process.
   Memory Usage	Memory consumed by a process pHashId (process name and process ID) is the value of md5.	0 to 1	Monitored object: ECS or BMS Memory Usage = RSS x PAGESIZE/MemTotal RSS: Obtain its value by checking the second column of the /proc/pid/statm file. PAGESIZE: Obtain its value by running the getconf PAGESIZE command. MemTotal: Obtain its value from the /proc/meminfo file.	Monitored object: ECS or BMS Invoke Windows API procGlobalMemoryStatusEx to obtain the total memory size. Invoke GetProcessMemoryInfo to obtain the used memory size. Use the used memory size to divide the total memory size to get the memory usage.
   Opened Files	The number of opened files consumed by the process pHashId (process name and process ID) is the value of md5.	≥ 0	Monitored object: ECS or BMS You can run the ls -l /proc/pid/fd command to view the number.	Not supported