OK, I have assigned myself for this issue and hope to resolve it soon.
--
Yujun
On Thu, Aug 11, 2016 at 6:30 PM Afek, Ifat (Nokia - IL)
wrote:
> Hi Yujun,
>
> There are few ways to create Aodh alarms. You are referring to
> event-alarms, and I believe you are right about the bug.
>
> Note, howev
Hi Yujun,
There are few ways to create Aodh alarms. You are referring to event-alarms,
and I believe you are right about the bug.
Note, however, that for threshold-alarm, the resource_id appears without the
“traits” prefix, so Vitrage Aodh datasource should be able to handle both
cases. An exa
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.resource_id', u'type': u'string
