Viewing Process Monitoring

Prerequisites

• You have installed the Cloud Eye Agent on a server. For details, see Installing the Agent.
• You have added a custom process to monitor. For details, see Adding Processes for Monitoring.

Constraints

The Agent of the new version no longer reports data on the top five processes, and process monitoring will become unavailable. You are advised to use custom process monitoring instead. For details about how to check the Agent version, see You have confirmed the Agent version.

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 dialog box.
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 1.
   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.

   Figure 1 Viewing process metrics
   

Viewing Custom Process Monitoring

1. Log in to the Cloud Eye console.

2. Perform the following operations based on your resources:
   • 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. Locate the row that contains the target resource and click View Metric.
4. Click 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 displayed View Metric drawer, view the CPU usage, memory usage, and number of opened files of the process. For details about the metrics, see Table 1. In the upper left corner, 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.
   Figure 2 Viewing process metrics
   
7. In the Custom Processes area, view details about custom processes running on the server.

   Table 1 Process monitoring metrics

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

Viewing the Number of System Processes

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

1. Log in to the Cloud Eye console.
2. Perform the following operations based on your resources:
   • 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. Locate the row that contains the target resource and click View Metric.
4. Click the Process Monitoring tab.
   In the System Processes area, view the process information. Table 2 describes the metrics of system processes.

   Figure 3 Number of system processes
   

   Table 2 System process metrics

   Name	Definition	Range	Collection (Linux)	Collection (Windows)
   Running Processes	Number of processes that are running	≥ 0	Monitored object: ECSs or BMSs 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: ECSs or BMSs 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: ECSs or BMSs 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: ECSs or BMSs 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: ECSs or BMSs 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
   Number of system processes	Total number of processes on the monitored object	≥ 0	Monitored object: ECSs or BMSs 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: ECSs or BMSs Obtain the total number of processes by using the system process status support module psapi.dll.

Viewing Processes Consuming the Most Resources

The Agent collects process CPU usages every minute and displays the top five 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 a process. In the command, replace pid with the ID of the target process.

• 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 five processes can change. The list shows them based on data collected every minute over the past 24 hours.
• The CPU usage, memory usage, and number of opened files are collected only for the top five 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 list may not show any metric data. In this case, synchronize the local time with the server time.

Querying information about the top five processes with the highest CPU usage

1. Log in to the Cloud Eye console.
2. Perform the following operations based on your resources:
   • 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. Locate the row that contains the target resource and click View Metric.
4. Click the Process Monitoring tab.
5. Click Configure under TOP 5 Processes with Highest CPU Usage.
6. In the displayed dialog box, enable monitoring for target processes and click OK.

   Locate a process and click View Details in the Operation column. On the displayed drawer, view the CPU usage, memory usage, and number of opened files of the process. For details about the metrics, see Table 3. In the upper left corner, 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 past year.

   Table 3 Top CPU process metrics

   Name	Definition	Range	Collection (Linux)	Collection (Windows)
   CPU Usage	CPU consumed by a process pHashId is the MD5 value of the concatenation of the process name and process ID.	0 to 1 x Number of vCPUs	Monitored object: ECSs or BMSs Check the metric value changes in /proc/pid/stat.	Monitored object: ECSs or BMSs Call the Windows API GetProcessTimes to obtain the CPU usage of the process.
   Memory Usage	Memory consumed by a process. pHashId is the MD5 value of the concatenation of the process name and process ID.	0 to 1	Monitored object: ECSs or BMSs Memory Usage = RSS x PAGESIZE/MemTotal RSS: obtained from the second column of the /proc/pid/statm file. PAGESIZE: obtained by running the getconf PAGESIZE command. MemTotal:obtained from the /proc/meminfo file.	Monitored object: ECSs or BMSs 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	Number of opened files consumed by the process pHashId is the MD5 value of the concatenation of the process name and process ID.	≥ 0	Monitored object: ECSs or BMSs Run the ls -l /proc/pid/fd command to view the number.	Not supported

Helpful Links

Too many processes or open files in an instance can overload the Agent, leading to higher CPU usage. You can modify the configuration file to solve the problem. For details, see How Do I Change the Process Collection Frequency by Modifying the Configuration File? or How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?