A user has two EC2 instances running in two separate regions. The user is running an internal memory
management tool, which captures the data and sends it to CloudWatch in US East, using a CLI with the same
namespace and metric. Which of the below mentioned options is true with respect to the above statement?
A.
The setup will not work as CloudWatch cannot receive data across regions
B.
CloudWatch will receive and aggregate the data based on the namespace and metric
C.
CloudWatch will give an error since the data will conflict due to two sources
D.
CloudWatch will take the data of the server, which sends the data first
Explanation:
Amazon CloudWatch does not differentiate the source of a metric when receiving custom data. If the user is
publishing a metric with the same namespace and dimensions from different sources, CloudWatch will treat
them as a single metric. If the data is coming with the same timezone within a minute, CloudWatch will
aggregate the data. It treats these as a single metric, allowing the user to get the statistics, such as minimum,
maximum, average, and the sum of all across all servers.
The answer is A. Cloudwatch doesn’t aggregate data which is across the regions.
0
0
answer is B. the second instance is using cli to send the data, so cloudwatch considers this external data.
0
0
Agree with B. Data is provided from within EC2 VM through CLI.
0
0
Answer is A
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetSingleMetricAllDimensions.html
1
0
ans A
Aggregate Statistics Across Resources
You can aggregate the metrics for AWS resources across multiple resources. Note that Amazon CloudWatch cannot aggregate data across regions. Metrics are completely separate between regions.
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetSingleMetricAllDimensions.html
1
0
B
Since both streams of data are send from US East, Cloud Watch would take them for one region input.
0
0
Agree , thank you
0
0
B
0
0
A
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.html
AWS services send metrics to CloudWatch, and you can send your own custom metrics to CloudWatch. You can add the data points in any order, and at any rate you choose. You can retrieve statistics about those data points as an ordered set of time-series data.
Metrics exist only in the region in which they are created.
If take above from AWS documentation then if a Metric is unique to each region then what you can public to that metric will also be unique to that specific region.
0
0
b
0
0
b
0
0
A
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetSingleMetricAllDimensions.html
above link does not say anything about CLI ..i will go with A
You can aggregate the metrics for AWS resources across multiple resources. Note that Amazon CloudWatch cannot aggregate data across regions. Metrics are completely separate between regions.
0
0
A
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GetSingleMetricAllDimensions.html
0
0
B is correct.
You can send metric to specified region, f.e.
aws –region eu-west-2 cloudwatch put-metric-data –namespace testing_metric –metric-data ‘MetricName=just-test-ok,Dimensions=[{Name=teststring,Value=11}],Value=11’
0
0
Correct answer is B
Amazon CloudWatch does not differentiate the source of a metric when receiving custom data. If the user is publishing a metric with the same namespace and dimensions from different sources, CloudWatch will treat them as a single metric. If the data is coming with the same timezone within a minute, CloudWatch will aggregate the data. It treats these as a single metric, allowing the user to get the statistics, such as minimum, maximum, average, and the sum of all across all servers.
0
0