Hi YinLiYin,
I’m not sure I understood the use case. Are you using a monitor that raises
alarms A, B, C, D, and E? or does the monitor raise only alarms A and C, and
the other alarms are deduced alarms created by Vitrage?
In Vitrage templates you can determine causal relationship between different
alarms. No matter who generated the alarm (Vitrage, Nagios, Zabbix, Aodh…), you
can model that A is a cause for B etc. You can also model that (B or D) is a
cause of E.
If you see in Vitrage UI that alarms A, B and E are triggered, you can open the
Root Casue Analysis view for one of them and see the A->B->E chain. In this use
case, C and D are not triggered at all, and you will not see them in the UI.
In what use case will you ‘suspect’ A or C? can you describe it in more details?
Best Regards,
Ifat.
From: "yinli...@zte.com.cn" <yinli...@zte.com.cn>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: Friday, 6 January 2017 at 03:15
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Cc: "gong.yah...@zte.com.cn" <gong.yah...@zte.com.cn>, "han.jin...@zte.com.cn"
<han.jin...@zte.com.cn>, "wang.we...@zte.com.cn" <wang.we...@zte.com.cn>,
"jia.peiy...@zte.com.cn" <jia.peiy...@zte.com.cn>, "zhang.yuj...@zte.com.cn"
<zhang.yuj...@zte.com.cn>
Subject: [openstack-dev] [Vitrage] About introduce suspect state of a alarm
Hi all,
I have a question when learnning vitrage:
A, B, C, D, E are alarms, consider the following alarm propagation model:
A --＞ B
C --＞ D
B or D --＞ E
When alarm E is reported by the system, from the above model, we know that
one or both of the following conditions may be true:
1. A is trigged
2. C is trigged
That is alarm A and C are suspected to be triggered. The suspect state
of the alarm is valuable for system administrator because
one could check the system to find out whether the suspected alarms is
really triggered according to the information.
In current vitrage template, we could not describe this situation. An
alarm has only two states: triggered or not triggered.
Whether we could introduce suspect state for alarms ?
殷力殷 YinLiYin
[cid:image001.gif@01D2685B.2F443EC0]
[cid:image002.gif@01D2685B.2F443EC0]
上海市浦东新区碧波路889号中兴研发大楼D502
D502, ZTE Corporation R&D Center, 889# Bibo Road,
Zhangjiang Hi-tech Park, Shanghai, P.R.China, 201203
T: +86 21 68896229
M: +86 13641895907
E: yinli...@zte.com.cn
www.zte.com.cn<http://www.zte.com.cn/>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
