A user has setup a web application on EC2. The user is generating a log of the application performance at every
second. There are multiple entries for each second. If the user wants to send that data to CloudWatch every
minute, what should he do?
A.
The user should send only the data of the 60th second as CloudWatch will map the receive data timezone
with the sent data timezone
B.
It is not possible to send the custom metric to CloudWatch every minute
C.
Give CloudWatch the Min, Max, Sum, and SampleCount of a number of every minute
D.
Calculate the average of one minute and send the data to CloudWatch
Explanation:
Amazon CloudWatch aggregates statistics according to the period length that the user has specified while
getting data from CloudWatch. The user can publish as many data points as he wants with the same or
similartime stamps. CloudWatch aggregates them by the period length when the user calls get statistics about
those data points. CloudWatch records the average (sum of all items divided by the number of items. of the
values received for every 1-minute period, as well as the number of samples, maximum value, and minimum
value for the same time period. CloudWatch will aggregate all the data which have time stamps within a oneminute period.
C is incorrect.
http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/publishingMetrics.html#publishingDataPoints1
C is correct
D.
http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/publishingMetrics.html#publishingDataPoints1
You can aggregate your data before you publish to CloudWatch. When you have multiple data points per minute, aggregating data minimizes the number of calls to put-metric-data. For example, instead of calling put-metric-data multiple times for three data points that are within three seconds of each other, you can aggregate the data into a statistic set that you publish with one call:
ag·gre·gate
1.
a whole formed by combining several (typically disparate) elements.
a material or structure formed from a loosely compacted mass of fragments or particles.
Although you can publish data points with time stamps as granular as one-thousandth of a second, CloudWatch aggregates the data to a minimum granularity of one minute. CloudWatch records the average (sum of all items divided by number of items) of the values received for every 1-minute period, as well as number of samples, maximum value, and minimum value for the same time period. For example, the PageViewCount metric from the previous examples contains three data points with time stamps just seconds apart. CloudWatch aggregates the three data points because they all have time stamps within a one-minute period.
I will go with C.
Even though the option D also makes sense. It would be good if we have data values of min, max, sample count, and sum, using these in cloud watch can be easily aggregate the data based on the time range selected by the user.
D
agree with nagarjunadn & emma
http://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html#publishingDataPoints1
CloudWatch aggregates the data to a minimum granularity of one minute. CloudWatch records the average (sum of all items divided by number of items) of the values received for every 1-minute period, as well as number of samples, maximum value, and minimum value for the same time period.
d
c
C.
For large datasets, you can insert a pre-aggregated dataset called a statistic set. With statistic sets, you give CloudWatch the Min, Max, Sum, and SampleCount for a number of data points. This is commonly used when you need to collect data many times in a minute. For example, suppose you have a metric for the request latency of a webpage. It doesn’t make sense to publish data with every webpage hit. We suggest that you collect the latency of all hits to that webpage, aggregate them once a minute, and send that statistic set to CloudWatch.
c