AWS - CloudWatch
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?
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📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Understand alarm threshold and metric period
The alarm triggers if average CPU exceeds 70% during the period.Step 2: Identify effect of long metric period
A long period averages out spikes, so short CPU spikes above 70% may not trigger alarm.Final Answer:
The metric period is too long, smoothing out spikes -> Option AQuick Check:
Long period averages hide spikes [OK]
Quick Trick: 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
Master "CloudWatch" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes