An errant process is known to use an entire processor and run at 100%. A SysOps administrator wants to automate restarting an Amazon EC2 instance when the problem occurs for more than 2 minutes.
How can this be accomplished?
An errant process is known to use an entire processor and run at 100%. A SysOps administrator wants to automate restarting an Amazon EC2 instance when the problem occurs for more than 2 minutes.
How can this be accomplished?
To accomplish the task of restarting an EC2 instance when an errant process runs at 100% for more than 2 minutes, you need to create an Amazon CloudWatch alarm for the EC2 instance with detailed monitoring. Detailed monitoring provides metrics at 1-minute intervals, allowing you to set up an alarm that triggers after 2 consecutive datapoints (each 1 minute apart) indicate high CPU usage. Once the alarm is triggered, you can add an action to automatically restart the instance. Basic monitoring, which provides 5-minute interval metrics, would not allow precise control for a 2-minute threshold, hence detailed monitoring is necessary.
Basic monitoring is 5 minutes interval Detailed monitoring is 1 minute interval https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-basic-detailed.html
High Resolution is 30 secs.
Ans is B ref : https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html
B 100%