aodh driver properties not consistent with ceilometer spec
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Vitrage |
Fix Released
|
Undecided
|
Yujun Zhang |
Bug Description
It seems the aodh properties definition in vitrage [1] is not consistent with the latest ceilometer spec [2].
The response_id is now encapsulated in `traits` and we must prepend the scope in query to make it a valid alarm condition, e.g. `query: [{u'field': u'traits.
But in vitrage, the resource id is parsed from key 'resource_id' [3] and always get an empty result.
Could anybody confirm whether this is a bug or not?
- [1] https:/
- [2]
https:/
- [3] https:/
Changed in vitrage: | |
assignee: | nobody → Yujun Zhang (yujunz) |
Changed in vitrage: | |
status: | Confirmed → In Progress |
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