alarm status doesn't change

asked 2017-03-07 04:05:21 -0600

samah gravatar image

updated 2017-03-07 07:41:18 -0600

zaneb gravatar image

I want to test autoscaling process I modified pipeline.yaml file but the alarm state is always insufficient data and does'nt change to ok or alarm. In the template: evaluation_periods: 1 In pipeline.yaml: interval: 60

edit retag flag offensive close merge delete


I had such a problem with manually created alarms. It turned out that:

The alarm period should be a whole number multiple (1 or more) of the interval configured in the pipeline corresponding to the target meter.
Bernd Bausch gravatar imageBernd Bausch ( 2017-03-07 04:40:23 -0600 )edit

I set the alarm period to 60 and the interval to 60 it didn't work :/

samah gravatar imagesamah ( 2017-03-07 06:22:15 -0600 )edit

The problem was in the matching-metadata properties in the ceilometer alarm when I delete this properties the autoscaling work but why I find it in every template examples? What's used for?

samah gravatar imagesamah ( 2017-03-07 10:14:08 -0600 )edit

Congratulations for finding the cause! My understanding is that the matching metadata ensure that the correct meter is used. See for example the comment at the end of I can't say why it doesn't work in your case.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-07 15:58:54 -0600 )edit

Perhaps you don't set the metering metadata item on your instances. See line 79 in the template I referenced.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-07 16:00:57 -0600 )edit