What should the SysOps administrator do to collect the process utilization information with the LEAST amount of effort?
Configure the Amazon CloudWatch agent procstat plugin to capture CPU process metrics.
Configure an AWS Lambda function to run every minute to capture the PID and send a notification.
Log in to the EC2 instance by using a .pem key each night. Then run the top command.
Use the default Amazon CloudWatch CPU utilization metric to capture the PID in CloudWatch.
Explanations:
The CloudWatch agent procstat plugin can be used to capture detailed process-level metrics, including the PID and CPU usage. This is a minimal-effort, automated solution that collects the required data for identifying high-CPU processes.
Setting up a Lambda function every minute adds unnecessary complexity and overhead. It requires creating a custom function, permissions, and additional configuration, which is not the least effort approach.
Logging into the EC2 instance manually each night to run the top command is labor-intensive and impractical for continuous monitoring. It also does not provide automated or real-time tracking.
CloudWatch’s default CPU utilization metric only tracks overall CPU usage of the instance, not individual processes or their PIDs. This does not meet the requirement of identifying the specific process consuming CPU.
I believe the answer is:
Configure the Amazon CloudWatch agent procstat plugin to capture CPU process metrics.
I structure that the answer is:
Configure the Amazon CloudWatch agent procstat plugin to capture CPU process metrics.