Hi all,
Vitrage generate alarms acording to the templates. All the alarms raised by
vitrage has the type "vitrage". Suppose Nagios has an alarm A. Alarm A is
raised by vitrage evaluator according to the action part of a scenario, type of
alarm A is "vitrage". If Nagios reported alarm A lat
Sounds good.
Have you created an etherpad page for collecting topics, Ifat?
On Mon, Jan 16, 2017 at 10:43 PM Afek, Ifat (Nokia - IL) <
ifat.a...@nokia.com> wrote:
>
>
> *From: *Yujun Zhang
> *Date: *Sunday, 15 January 2017 at 17:53
>
>
>
> About fault and alarm, what I was thinking about the ca
From: Yujun Zhang
Date: Tuesday, 17 January 2017 at 02:41
Sounds good.
Have you created an etherpad page for collecting topics, Ifat?
Here: https://etherpad.openstack.org/p/vitrage-pike-design-sessions
__
OpenStack Dev
t; , "han.jin...@zte.com.cn"
, "wang.we...@zte.com.cn" ,
"jia.peiy...@zte.com.cn" , "zhang.yuj...@zte.com.cn"
Subject: [openstack-dev] [Vitrage] About alarms reported by datasource and the
alarms generated by vitrage evaluator
Hi all,
Vitrage generate alarms ac
elopment Mailing List (not for usage
> questions)"
> *Date: *Friday, 6 January 2017 at 03:27
> *To: *"openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> *Cc: *"gong.yah...@zte.com.cn" , "
> han.jin...@zte.com.cn"
quot;jia.peiy...@zte.com.cn" , "zhang.yuj...@zte.com.cn"
Subject: Re: [openstack-dev] [Vitrage] About alarms reported by datasource and
the alarms generated by vitrage evaluator
The two questions raised by YinLiYin is actually one, i.e. how to enrich the
alarm properties that
gt;
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
>
> *Cc: *"han.jin...@zte.com.cn" , "
> wang.we...@zte.com.cn" , "gong.yah...@zte.com.cn" <
> gong.yah...@zte.com.cn>,
0101785龚亚辉6092001895
日 期 ：2017年01月07日 02:18
主 题 ：Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the
alarms generated by vitrage evaluator
Hi YinLiYin,
This is an interesting question. Let me divide my answer to two parts.
First, the case that you described
.cn" ,
"jia.peiy...@zte.com.cn" , "zhang.yuj...@zte.com.cn"
Subject: Re: [openstack-dev] [Vitrage] About alarms reported by datasource and
the alarms generated by vitrage evaluator
Maybe I have missed something in the scenario template, but it seems you have
understood my
(host) of a confirmed alarm
> (instance) to "suspect" and trigger an diagnostic action on this change.
>
>
>
> Hope that I have made the use case clear.
>
>
>
> Thanks,
>
> Ifat.
>
>
>
>
>
> *From: *Yujun Zhang
>
>
> *Reply-To:
te.com.cn" , "wang.we...@zte.com.cn"
, "zhang.yuj...@zte.com.cn" ,
"jia.peiy...@zte.com.cn" , "gong.yah...@zte.com.cn"
Subject: Re: [openstack-dev] [Vitrage] About alarms reported by datasource and
the alarms generated by vitrage evaluator
Hi Ifat,
t;wang.we...@zte.com.cn" <
wang.we...@zte.com.cn>, "zhang.yuj...@zte.com.cn" ,
"jia.peiy...@zte.com.cn" , "gong.yah...@zte.com.cn"
*Subject: *Re: [openstack-dev] [Vitrage] About alarms reported by
datasource and the alarms generated by vitrage evaluator
Hi Ifa
:zhang.yuj...@zte.com.cn>>,
"jia.peiy...@zte.com.cn<mailto:jia.peiy...@zte.com.cn>"
mailto:jia.peiy...@zte.com.cn>>,
"gong.yah...@zte.com.cn<mailto:gong.yah...@zte.com.cn>"
mailto:gong.yah...@zte.com.cn>>
Subject: Re: [openstack-dev] [Vitrage]
we...@zte.com.cn" , "zhang.yuj...@zte.com.cn"
> , "jia.peiy...@zte.com.cn" <
> jia.peiy...@zte.com.cn>, "gong.yah...@zte.com.cn"
>
>
> *Subject: *Re: [openstack-dev] [Vitrage] About alarms reported by
> datasource and the alarms generated by
c: *"han.jin...@zte.com.cn" , "
> wang.we...@zte.com.cn" , "zhang.yuj...@zte.com.cn"
> , "jia.peiy...@zte.com.cn" <
> jia.peiy...@zte.com.cn>, "gong.yah...@zte.com.cn"
>
>
> *Subject: *Re: [openstack-dev] [Vitrage] About alarms report
Hi Yujun,
See my comments inline.
Ifat.
From: Yujun Zhang
Date: Wednesday, 11 January 2017 at 12:12
I have just realized abstract alarm is not a good term. What I was talking
about is fault and alarm.
Fault is what actually happens, and alarm is how it is detected (or deduced).
On Wed, Ja
Hi, Ifat
You comments is quite right. See my additional explanation inline.
On Thu, Jan 12, 2017 at 5:12 PM Afek, Ifat (Nokia - IL)
wrote:
>
>
> One possible solution would be introducing a high level (abstract)
> template from users view. Then convert it to Vitrage scenario templates (or
> dir
From: Yujun Zhang
Date: Thursday, 12 January 2017 at 17:37
On Thu, Jan 12, 2017 at 5:12 PM Afek, Ifat (Nokia - IL)
mailto:ifat.a...@nokia.com>> wrote:
'deduced' vs 'monitored' would be good enough for most cases. Unless we have
identify some real use case, I also think there is no need for bri
About fault and alarm, what I was thinking about the causal/deducing chain
in root cause analysis.
Fault state means the resource is not fully functional and it is evaluated
by related indicators. There are alarms on events like power loss or
measurands like CPU high, memory low, temperature high.
From: Yujun Zhang
Date: Sunday, 15 January 2017 at 17:53
About fault and alarm, what I was thinking about the causal/deducing chain in
root cause analysis.
Fault state means the resource is not fully functional and it is evaluated by
related indicators. There are alarms on events like power
20 matches
Mail list logo
