Open Stack

Hi

I have a requirement of monitoring VMs, if a VM's meter like cpu_util become too high, then system generate an alarm for this VM with meter information.

I have tested alarm function of ceilometer, below are commands I used to create alarm object with meter and resource id or not:
ceilometer alarm-threshold-create  --name alarm1 --meter-name cpu_util --period 60 --evaluation-periods 1 --statistic avg --comparison-operator gt --threshold 1 -q resource_id=757dadaa-0707-4fad-808d-81edc11438aa
ceilometer alarm-threshold-create  --name alarm1 --meter-name cpu_util --period 60 --evaluation-periods 1 --statistic avg --comparison-operator gt --threshold 1

I have the following question:
If I have to define alarm object for every VM and every meter?
Take 100 VM and 2 meter cpu_util, memory_util as an example, I will have to define 100*2 alarm objects for them.
I think if I just define alarm object with meter not but VM(resource_id), then alarm evaluator will count all VM's meter.

Another question produced by question above: I know that alarm evaluator will process alarm object one by one, so too many alarm object may result in performance problems too.

I am not a ceilometer programmer and I apologize if I am missing something very obvious.
Can you give me some help to make me clear about them and how to implement my requirement?

Thanks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140403/c343943b/attachment.html>