CloudWatch metrics in AWS - Step-by-Step Execution

Process Flow - CloudWatch metrics

Start Monitoring

↓

Collect Metrics Data

↓

Send Data to CloudWatch

↓

CloudWatch Stores Metrics

↓

User Views Metrics & Sets Alarms

↓

Alarms Trigger Actions if Thresholds Met

↓

End

Metrics data is collected from resources, sent to CloudWatch, stored, and then users can view or set alarms that trigger actions.

Execution Sample

AWS

aws cloudwatch put-metric-data --namespace MyApp --metric-name PageViews --value 100

This command sends a metric named PageViews with value 100 to CloudWatch under the MyApp namespace.

Process Table

Step	Action	Input/Condition	CloudWatch State	Output/Result
1	Start Monitoring	Resource begins sending metrics	No metrics stored yet	Ready to receive data
2	Collect Metrics Data	PageViews = 100	No metrics stored yet	Metric data prepared
3	Send Data to CloudWatch	PutMetricData command with PageViews=100	Receives metric data	Metric stored under MyApp/PageViews
4	CloudWatch Stores Metrics	Metric data received	PageViews metric stored with value 100	Data available for queries
5	User Views Metrics	User queries PageViews metric	Metric data stored	Displays value 100
6	User Sets Alarm	Threshold set at 90	Metric data stored	Alarm created for PageViews > 90
7	Metric Value Updates	New value 85 sent	PageViews metric updated to 85	Alarm not triggered
8	Metric Value Updates	New value 95 sent	PageViews metric updated to 95	Alarm triggered
9	Alarm Triggers Action	Alarm state ALARM	Alarm active	Notification or action executed
10	End	Monitoring continues	Metrics and alarms active	System ready for next data

💡 Monitoring continues indefinitely; this trace shows one cycle of metric data flow and alarm triggering.

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 7	After Step 8	Final
PageViews Metric Value	None	100	100	85	95	95
Alarm State	INSUFFICIENT_DATA	INSUFFICIENT_DATA	INSUFFICIENT_DATA	OK	ALARM	ALARM

Key Moments - 3 Insights

Why does the alarm not trigger when the metric value is 85 even though the threshold is 90?

Because 85 is less than the threshold 90, so the alarm state remains OK as shown in step 7 of the execution_table.

What happens inside CloudWatch when metric data is sent?

CloudWatch stores the metric data under the specified namespace and metric name, making it available for queries and alarms, as seen in step 4.

Can metrics be viewed before setting alarms?

Yes, metrics are stored and can be viewed anytime after data is sent, before alarms are set, as shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the PageViews metric value after step 7?

A 100

B 95

C 85

D None

💡 Hint

Check the 'PageViews Metric Value' row in variable_tracker after step 7.

At which step does the alarm state change to ALARM?

A Step 8

B Step 6

C Step 7

D Step 9

💡 Hint

Look at the 'Alarm State' variable in variable_tracker and the execution_table rows for alarm triggering.

If the threshold was set to 80 instead of 90, at which step would the alarm trigger?

A Step 6

B Step 7

C Step 8

D Step 9

💡 Hint

Compare metric values at steps 7 and 8 with the new threshold and check alarm state changes.

Concept Snapshot

CloudWatch metrics collect data from resources.
Data is sent using PutMetricData commands.
Metrics are stored under namespaces and names.
Users can view metrics and set alarms.
Alarms trigger actions when thresholds are crossed.

Full Transcript

CloudWatch metrics work by collecting data from your resources and sending it to CloudWatch. This data is stored and can be viewed anytime. You can set alarms on these metrics to notify or act when certain thresholds are met. For example, sending a PageViews metric with value 100 stores it in CloudWatch. If you set an alarm at 90, it will trigger when the metric value goes above 90. This process repeats continuously as new data arrives.

Practice

1. What is the primary purpose of AWS CloudWatch metrics?

easy

A. To create virtual machines

B. To store files and documents securely

C. To monitor and track the performance of cloud resources

D. To manage user permissions

Solution

1. Step 1: Understand CloudWatch metrics role

   CloudWatch metrics collect data points about cloud resources like CPU usage or network traffic.

2. Step 2: Identify the main use

   This data helps monitor and keep cloud resources healthy and efficient.

3. Final Answer:

   To monitor and track the performance of cloud resources -> Option C

4. Quick Check:

   CloudWatch metrics = Monitor resources [OK]

Hint: CloudWatch metrics = numbers about resource health [OK]

Common Mistakes:

• Confusing metrics with storage services
• Thinking metrics create resources
• Mixing metrics with user management

2. Which of the following is the correct way to specify a metric namespace in AWS CloudWatch?

easy

A. Namespace: AWS/EC2

B. Namespace = AWS-EC2

C. Namespace -> AWS.EC2

D. Namespace is AWS_EC2

Solution

1. Step 1: Recall CloudWatch namespace format

   Namespaces use a string format with a slash, like AWS/EC2, to group metrics.

2. Step 2: Check each option format

   Only 'Namespace: AWS/EC2' uses the correct slash format without invalid characters.

3. Final Answer:

   Namespace: AWS/EC2 -> Option A

4. Quick Check:

   Namespace uses slash (/) format [OK]

Hint: Namespace uses slash (/) format, not dash or underscore [OK]

Common Mistakes:

• Using dash or underscore instead of slash
• Using equal sign instead of colon
• Using arrow notation incorrectly

3. Given the following CloudWatch metric data points for CPU utilization: [10, 20, 30, 40, 50], what is the average CPU utilization reported?

medium

A. 10

B. 25

C. 50

D. 30

Solution

1. Step 1: Sum all CPU utilization values

   10 + 20 + 30 + 40 + 50 = 150

2. Step 2: Calculate average by dividing sum by count

   150 / 5 = 30

3. Final Answer:

   30 -> Option D

4. Quick Check:

   Average = Sum / Count = 30 [OK]

Hint: Average = add all values, divide by number of values [OK]

Common Mistakes:

• Adding incorrectly
• Dividing by wrong count
• Picking max or min instead of average

4. You set a CloudWatch alarm to trigger when CPU utilization exceeds 70%, but it never triggers even when CPU is 80%. What is a likely cause?

medium

A. The metric period is too long, smoothing out spikes

B. The alarm threshold is set incorrectly below 70%

C. The alarm action is missing

D. The CPU utilization metric is disabled

Solution

1. Step 1: Understand alarm threshold and metric period

   The alarm triggers if average CPU exceeds 70% during the period.

2. Step 2: Identify effect of long metric period

   A long period averages out spikes, so short CPU spikes above 70% may not trigger alarm.

3. Final Answer:

   The metric period is too long, smoothing out spikes -> Option A

4. Quick Check:

   Long period averages hide spikes [OK]

Hint: Long metric periods smooth spikes, prevent alarms [OK]

Common Mistakes:

• Assuming threshold is set below 70%
• Ignoring missing alarm actions
• Thinking metrics can be disabled

5. You want to monitor the average latency of your web application every 5 minutes using CloudWatch. Which combination of settings is best to achieve this?

hard

A. Set metric period to 60 seconds and statistic to Sum

B. Set metric period to 300 seconds and statistic to Average

C. Set metric period to 300 seconds and statistic to Maximum

D. Set metric period to 60 seconds and statistic to Minimum

Solution

1. Step 1: Understand metric period and statistic

   Period defines how often data is collected; statistic defines how data is summarized.

2. Step 2: Match requirements to settings

   To monitor average latency every 5 minutes, use 300 seconds period and Average statistic.

3. Final Answer:

   Set metric period to 300 seconds and statistic to Average -> Option B

4. Quick Check:

   5 min period + Average = correct monitoring [OK]

Hint: Use 300s period and Average for 5-minute average latency [OK]

Common Mistakes:

• Using Sum or Maximum instead of Average
• Using 60s period for 5-minute average
• Confusing Minimum with latency monitoring