Why does CPUUtilization Alarm have always INSUFFICIENT_DATA state?

Question

I'm trying to create an Auto-Scaling Group, which will work based upon CPUUtilization of the Target Group.

I managed to created an Auto-Scaling group. When I execute the Scaling Policies via some test data. It works.

I created 2 alarms in Cloudwatch. However, those are in "INSUFFICIENT_DATA".

The alarms should be able to checking the CPUUtilization of the Auto-Scaling Group.

So, how can I run the autoscaling based on CPUUtilization of Target Group?

The screentshots are below:

The loadbalancer configuration

The target group configuration

The autoscaling configuration

The scaling policies

The CloudWatch alarm config

Alarm configuration for Scale-UP

Alarm configuration for Scale-Down

Do you have any other working alarm? – Mahdi Mar 20 '18 at 11:16 — Mahdi, Mar 20 '18 at 11:16
Do you have Windows machines in your ASG? – Mahdi Mar 20 '18 at 11:32 — Mahdi, Mar 20 '18 at 11:32
nope. i don't have windows. – user9522155 Mar 20 '18 at 11:36 — user9522155, Mar 20 '18 at 11:36

score 0 · Answer 1 · answered Mar 20 '18 at 11:19

https://serverfault.com/questions/479689/cloudwatch-alarms-strange-behavior

I found this answer. My alarm works for period 1 minute. But my cloudwatch monitoring wasn't detailed.

When I change the alarm checking period from 1 minute to 1 hour, the alarm works. However, I need to execute the alarm for period 1 minute. I enabled the detailed monitoring but still doesn't work.

Why does CPUUtilization Alarm have always INSUFFICIENT_DATA state?

1 Answers1