Ask Your Question
0

How would a ceilometer alarm trigger when monitoring an AutoScalingGroup?

asked 2014-07-08 13:13:41 -0500

vahidh gravatar image

I'm trying to understand when a Ceilometer alarm that monitors a Heat AutoScalingGroup triggers.

Here's an example:

This alarm is configured to indicate when CPU utilization goes above a threshold:

cpu_alarm_high:
  type: OS::Ceilometer::Alarm
  properties:
    description: Scale-up if the average CPU > 75% for 1 minute
    meter_name: cpu_util
    statistic: avg
    period: 60
    evaluation_periods: 1
    threshold: 75
    alarm_actions:
      - {get_attr: [web_server_scaleup_policy, alarm_url]}
    matching_metadata: {'metadata.user_metadata.stack': {get_param: "OS::stack_id"}}
    comparison_operator: gt

If the AutoScalingGroup includes two or more VMs at some point in time, does the "avg" statistics field refer to average CPU utilization across all VMs? Or average per VM? For example, if one VM is running on 100% CPU and the other on 10% (for over a minute) should that trigger this alarm or not?

Is there any documentation out there explaining details like this?

Thanks.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-09-17 15:27:36 -0500

vahidh gravatar image

I found out the answer after trying it out in a Heat template. The average or whatever statistics is specified applies to all VMs in the AutoScalingGroup. With the above example, when there are more than one instances inthe group the average CPU utilization across all VMs should be over 75% for a one minute period for the scale-up policy to trigger.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2014-07-08 13:13:41 -0500

Seen: 668 times

Last updated: Sep 17 '14