Alarm Trigger Delay
I have a complete loadbalanced ScalingGroup, but the time it takes to create or delete a new instance takes 10 minutes.
Policy:
type: OS::Heat::ScalingPolicy
properties:
adjustment_type: change_in_capacity
auto_scaling_group_id: {get_resource: myServer_Group}
cooldown: 30
scaling_adjustment: 1
Alarm:
type: OS::Ceilometer::Alarm
properties:
meter_name: cpu_util
statistic: avg
period: 30
evaluation_periods: 1
threshold: 50
alarm_actions:
- {get_attr: [Policy, alarm_url]}
comparison_operator: gt
So I set the Policy Cooldown to 30seconds and the period of the alarm also to 30seconds. I keep my Instance at 90% CPU so that the alarm should trigger within the first (or second) Period. Why does it stil take 10 minutes to trigger?
I hope that someone can explain me this events and thanks to everyone who help me with my Questions.
ceilometer alarm-history -a 5507767f-1b31-461d-a6c1-9a855ebbdbb0
+------------------+----------------------------+--------------------------------------------+
| Type | Timestamp | Detail |
+------------------+----------------------------+--------------------------------------------+
| creation | 2014-10-02T12:53:02.986000 | name: Scal-cpu_alarm_HIGH-zjhgpr3ct2qy |
| | | type: threshold |
| | | rule: cpu_util > 50.0 during 1 x 60s |
| state transition | 2014-10-02T13:03:35.944000 | state: alarm |
| state transition | 2014-10-02T13:05:35.942000 | state: insufficient data |
| state transition | 2014-10-02T13:13:36.008000 | state: alarm |
| state transition | 2014-10-02T13:15:36.004000 | state: insufficient data |
+------------------+----------------------------+--------------------------------------------+