CloudWatch

Question 1

CloudWatch EC2 Detailed Monitoring

Answer 1

• Metrics every 5 minutes
• Detailed monitoring every 1 minute
• EC2 memory usage is by default not pushed
  
  • Must be pushed with a custom metric

Question 2

CloudWatch Custom Metrics

Answer 2

• use dimensions (attributes) to segment metrics
  
  • instance.id
  • environment.name

Metric Resolution:

- standard: 1 minute
- High Resolution: up to 1 second (StorateResolution API Parameter) - Higher Cost

• Use API call PutMetricData
• use exponential back off in case of throttle errors

Question 3

CloudWatch Alarms

Answer 3

• trigger notifications for any metric
• can go to Auto Scaling, EC2 Actions, SNS notification
• various options (sampling, %, max,min)

Question 4

CloudWatch Alarms: States

Answer 4

• OK
• INSUFFICIENT_DATA
• ALARM

Question 5

CloudWatch Alarms: Period

Answer 5

• Length of time in seconds to evaluate a metric

- High Resolution custom metrics: can only choose 10 sec or 30 sec.

Question 6

CloudWatch Logs

Answer 6

• Can send logs using the SDK
• can collect from Beanstalk, EC2, VPC, API GW… etc.
• Logs can go to:
  
  • batch exporter to S3 for archival
  • stream to ElasticSearch cluster for further analytics

Question 7

CloudWatch Events

Answer 7

• schedule corn jobs
• event patterns: event rules to react to a service something
  
  • codePipeline state changes
• trigger to lambda functions
• creates a small Jason document to give information of the change

Question 8

Amazon EventBridge

Answer 8

• EventBridge is the next evolution of CloudWatch Events
• Default Event Bus: generated by AWS services
• Partner Even Bus: receive events from other SaaS services or application
• Custom Even Bus: from your own applications
• cross account even buses can be access
• rules for event buses

Question 9

CloudWatch: Log Expiration Polices

Answer 9

By default, logs are key kept indefinitely and never expire.

• Retention between 1 day to ten years