Open Stack

On 02/02/2017, 15:43, "gordon chung" <gord at live.ca> wrote:
>    
> On 02/02/17 06:30 AM, Afek, Ifat (Nokia - IL) wrote:
> > I understand. So clearly the use case of Vitrage raising alarms in Aodh is not relevant at the moment.
> > We will have to think if over and see how Panko fits in the use case.
>    
> if the use case is that you wanted to store history of Vitrage alarms, 
> yes, i believe it's better/easier stored in Panko. i hope i understand 
> your requirement now. Aodh does have the ability to create composite 
> alarms which are basically an alarm consisting of multiple sub alarms. i 
> don't know if that will help you guys?

The history is not what we are looking for. Our idea was to provide visibility of the instances status, as known by Vitrage, through Aodh alarms API (so users that use Aodh will be aware of it).

Regarding the composite alarms, I believe that Vitrage templates are more complex, as the condition depends on the resources topology and not only on other alarms. 

> i apologise this took so long to clarify.

I thought I should be the one to apologize ;-)