A user has launched 10 instances from the same AMI ID using Auto Scaling. The user is trying to see the
average CPU utilization across all instances of the last 2 weeks under the CloudWatch console. How can the
user achieve this?
A.
View the Auto Scaling CPU metrics
B.
Aggregate the data over the instance AMI ID
C.
The user has to use the CloudWatchanalyser to find the average data across instances
D.
It is not possible to see the average CPU utilization of the same AMI ID since the instance ID is different
Explanation:
Amazon CloudWatch is basically a metrics repository. Either the user can send the custom data or an AWS
product can put metrics into the repository, and the user can retrieve the statistics based on those metrics.
The statistics are metric data aggregations over specified periods of time. Aggregations are made using the
namespace, metric name, dimensions, and the data point unit of measure, within the time period that is
specified by the user. To aggregate the data across instances launched with AMI, the user should select the
AMI ID under EC2 metrics and select the aggregate average to view the data.
Answer is A. Auto Scaling has its own aggregated CPU Utilization metric.
B needs detailed monitoring to be enabled
C is nonsense
D is nonsense
0
0
A.
View the Auto Scaling CPU metrics
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
0
0
B is the correct answer. AutoScaling does not have any CPU metric in CW
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/US_SingleMetricPerAMI.html
0
0
If they are launching with AMI ID alone , I agree with singh. But the question shows along with “AMI ID using Auto Scaling”. so it should be A
0
0
I think its B
http://docs.aws.amazon.com/autoscaling/latest/userguide/as-instance-monitoring.html#as-view-group-metrics
0
0
Sorry Ans is A
To view the metrics for your Auto Scaling instances, in the navigation pane, under Metrics, choose EC2. By default, all instances metrics are displayed. To view only the Auto Scaling instances, choose By Auto Scaling Group.
0
0
B is right, needs detailed monitoring to be enabled
0
0
It’s A
B, D – both of them are trying to explain 1 thing – use AMI ID to check CPU, but the AMI ID is used multiple times, the goal is not able to achieve.
C: Nonsense
Only A you can find in CloudWatch -> EC2 -> By Auto scaling group.
0
0
I would go with the Option B
In the CloudWatch Metrics by Category pane, under EC2 Metrics, select By Image (AMI) Id.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/US_SingleMetricPerAMI.html
0
0
Ans should be A
Cloudwatch –> ec2 –> autoscaling –> cpu utilization (AVG)
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetMetricAutoScalingGroup.html
0
0
[A] should be an Answer after testing same successfully!
Launched 3 instances using same AMI in an Auto Scaling group.
Increased CPU utilization using “stress” tool on all 3 instances for few minutes.
Went to Cloud Watch Metrics –> EC2 –> AutoScaling –> CPU Utilization (AVG)
you can also select any custom period (say 2 weeks) etc.
1
0
Answer B.
Amazon CloudWatch is basically a metrics repository. Either the user can send the custom
data or an AWS product can put metrics into the repository, and the user can retrieve the
statistics based on those metrics. The statistics are metric data aggregations over specified
periods of time. Aggregations are made using the namespace, metric name, dimensions,
and the data point unit of measure, within the time period that is specified by the user. To
aggregate the data across instances launched with AMI, the user should select the AMI ID
under EC2 metrics and select the aggregate average to view the data.
0
0
a
0
0
The answer should be A.
You can aggregate statistics for the EC2 instances in an Auto Scaling group. Note that Amazon CloudWatch cannot aggregate data across regions. Metrics are completely separate between regions.
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetMetricAutoScalingGroup.html
0
0
Answer should be A
View the Auto Scaling CPU metrics (Refer AS Instance Monitoring)
Aggregate the data over the instance AMI ID (Works but needs detailed monitoring enabled)
0
0
b
0
0
Answer is A
0
0
I will go with A, as in B it can count other instances launched with same AMI ID but outside of ASG.
0
0
A
0
0
Answer is A. View the Auto Scaling CPU metrics (Refer AS Instance Monitoring)
Very Close Answer – B. Aggregate the data over the instance AMI ID (Works but needs detailed monitoring enabled)
0
0