There are few ways to create Aodh alarms. The bug happens for event-alarms.
For threshold-alarm, on the other hand, the resource_id appears without the “traits” prefix, so Vitrage Aodh datasource should be able to handle both cases.
An example for creating a threshold alarm:
ceilometer alarm-threshold-create --name 'cpu_alarm' --description 'CPU utilization is above 70%' -m 'cpu_util' --period 60 --threshold 0.7 --comparison-operator gt --query 'resource_id=5f6db701-19d6-4a98-895b-8094f2bd7304'
There are few ways to create Aodh alarms. The bug happens for event-alarms.
For threshold-alarm, on the other hand, the resource_id appears without the “traits” prefix, so Vitrage Aodh datasource should be able to handle both cases.
An example for creating a threshold alarm: -create --name 'cpu_alarm' --description 'CPU utilization is above 70%' -m 'cpu_util' --period 60 --threshold 0.7 --comparison- operator gt --query 'resource_ id=5f6db701- 19d6-4a98- 895b-8094f2bd73 04'
ceilometer alarm-threshold