Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

ALL AWS Specialty Practice Exams for only $17.99 $13.99 each!

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified DevOps Engineer Professional Wrong time period for cloudwatch enhanced monitoring

  • Wrong time period for cloudwatch enhanced monitoring

  • HHH

    Member
    December 7, 2020 at 2:50 pm

    The explanations for one of the MCQ questions is “Detailed Monitoring feature simply sends the metric data for your instance to CloudWatch in 1-minute periods.”

    this should be changed to “1-second periods” as the detailed/enhanced monitoring in cloudwatch allows 1 second granularity.

  • Carlo-TutorialsDojo

    Administrator
    December 7, 2020 at 4:40 pm

    Hello HHH,

    Thank you for your feedback.

    By default, your instance is enabled for basic monitoring. You can optionally enable detailed monitoring. After you enable detailed monitoring, the Amazon EC2 console displays monitoring graphs with a 1-minute period for the instance.

    I assume that you’re referring to High-Resolution metrics. Metrics produced by AWS services are standard resolution by default. When you publish a custom metric, you can define it as either standard resolution or high resolution. When you publish a high-resolution metric, CloudWatch stores it with a resolution of 1 second, and you can read and retrieve it with a period of 1 second, 5 seconds, 10 seconds, 30 seconds, or any multiple of 60 seconds.

    References:

    https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html#high-resolution-metrics

    https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html

    Regards,

    Carlo

  • HHH

    Member
    December 7, 2020 at 4:51 pm

    Hi Carlo,

    Thank you very much for the clarification. Appreciate your quick response.

    -Harish

Viewing 1 - 3 of 3 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now