<div dir="ltr">The two questions raised by YinLiYin is actually one, i.e. <b>how to enrich the alarm properties </b>that can be used as an condition in root cause deducing.<div><br></div><div>Both 'suspect' or 'datasource' are additional information that may be referred as a condition in general fault model, a.k.a. scenario in vitrage.</div><div><br></div><div>It seems it could be done by</div><div><ol><li><font size="2">introduce a flexible `metadata` dict in to ALARM entity</font></li><li><font size="2">Allow generating update event[1] on metadata change</font></li><li><font size="2">Allow using ALARM metadata in scenario condition</font></li><li><font size="2">Allow setting ALARM metadata in scenario action</font></li></ol></div><div>This will leave the flexibility to continuous development by defining a complex scenario template and keep the vitrage evaluator simple and generic.</div><div><br></div><div>My two cents.</div><div><br></div><div>[1]: <a href="http://docs.openstack.org/developer/vitrage/scenario-evaluator.html#concepts-and-guidelines">http://docs.openstack.org/developer/vitrage/scenario-evaluator.html#concepts-and-guidelines</a> <br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Jan 7, 2017 at 2:23 AM Afek, Ifat (Nokia - IL) <<a href="mailto:ifat.afek@nokia.com">ifat.afek@nokia.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg">
<div class="m_5609626365442085205WordSection1 gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Hi YinLiYin,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">This is an interesting question. Let me divide my answer to two parts.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">First, the case that you described with Nagios and Vitrage. This problem depends on the specific Nagios tests that you configure in your system, as well as on the Vitrage templates that
you use. For example, you can use Nagios/Zabbix to monitor the physical layer, and Vitrage to raise deduced alarms on the virtual and application layers. This way you will never have duplicated alarms. If you want to use Nagios to monitor the other layers
as well, you can simply modify Vitrage templates so they don’t raise the deduced alarms that Nagios may generate, and use the templates to show RCA between different Nagios alarms.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Now let’s talk about the more general case. Vitrage can receive alarms from different monitors, including Nagios, Zabbix, collectd and Aodh. If you are using more than one monitor, it is
possible that the same alarm (maybe with a different name) will be raised twice. We need to create a mechanism to identify such cases and create a single alarm with the properties of both monitors. This has not been designed in details yet, so if you have
any suggestion we will be happy to hear them.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Best Regards,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Ifat.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">From:
</span></b><span style="font-family:Calibri;color:black" class="gmail_msg">"<a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a>" <<a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a>><br class="gmail_msg">
<b class="gmail_msg">Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>><br class="gmail_msg">
<b class="gmail_msg">Date: </b>Friday, 6 January 2017 at 03:27<br class="gmail_msg">
<b class="gmail_msg">To: </b>"<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>><br class="gmail_msg">
<b class="gmail_msg">Cc: </b>"<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>" <<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>>, "<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>" <<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>>, "<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>" <<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>>, "<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>" <<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>>, "<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>" <<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>><br class="gmail_msg">
<b class="gmail_msg">Subject: </b>[openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_5609626365442085205WordSection1 gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p style="margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important" class="gmail_msg">
<span style="font-family:宋体" class="gmail_msg">Hi all, <u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p style="margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important" class="gmail_msg">
<span style="font-family:宋体" class="gmail_msg"> 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 latter, a new alarm A with type "Nagios" would be generator in the entity graph. There would be two vertices for the same alarm in the graph. And we have to define two alarm entities, two relationships,
two scenarios in the template file to make the alarm propagation procedure work.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p style="margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important" class="gmail_msg">
<span style="font-family:宋体" class="gmail_msg"> It is inconvenient to describe fault model of system with lot of alarms. How to solve this problem?<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<div class="gmail_msg">
<p style="margin-left:36.0pt" class="gmail_msg"><span style="font-size:5.5pt;font-family:宋体" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p style="margin-left:36.0pt" class="gmail_msg"><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:9.0pt;font-family:Calibri;color:#58595b" class="gmail_msg">殷力殷</span></span><span style="font-size:9.0pt;font-family:"\005fae\008f6f\0096c5\009ed1","serif";color:#58595b" class="gmail_msg"> </span><span style="font-family:Arial;color:#58595b" class="gmail_msg">YinLiYin</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p style="margin-left:36.0pt" class="gmail_msg"><span style="font-size:5.5pt" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p style="margin-left:36.0pt" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
<table class="m_5609626365442085205MsoNormalTable gmail_msg" border="0" cellpadding="0" width="600" style="width:450.0pt;margin-left:36.0pt">
<tbody class="gmail_msg">
<tr class="gmail_msg">
<td width="97" valign="top" style="width:72.75pt;padding:.75pt .75pt .75pt .75pt" class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-family:宋体;color:black" class="gmail_msg"><img width="130" height="120" id="m_5609626365442085205sign-icon" src="cid:image001.gif@01D26859.D4BAB6B0" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</td>
<td width="497" valign="top" style="width:372.75pt;padding:.75pt .75pt .75pt .75pt" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="word-break:break-all"><span style="font-family:宋体;color:black" class="gmail_msg"><img width="115" height="38" id="m_5609626365442085205sign-logo" src="cid:image002.gif@01D26859.D4BAB6B0" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:7.5pt;font-family:宋体;color:#58595b" class="gmail_msg">上海市浦东新区碧波路</span></span><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:7.5pt;font-family:"\005fae\008f6f\0096c5\009ed1","serif";color:#58595b" class="gmail_msg">889</span></span><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:7.5pt;font-family:宋体;color:#58595b" class="gmail_msg">号中兴研发大楼</span></span><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:7.5pt;font-family:"\005fae\008f6f\0096c5\009ed1","serif";color:#58595b" class="gmail_msg">D502 </span></span><span style="font-size:7.5pt;font-family:"\005fae\008f6f\0096c5\009ed1","serif";color:#58595b" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_5609626365442085205signedit gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">D502, ZTE Corporation R&D Center, 889# Bibo Road</span></span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">,
<br class="gmail_msg">
<span class="m_5609626365442085205signedit gmail_msg">Zhangjiang Hi-tech Park, Shanghai, P.R.China, 201203</span> <br class="gmail_msg">
</span><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">T</span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<span class="m_5609626365442085205signedit gmail_msg"><a href="tel:+86%2021%206889%206229" value="+862168896229" class="gmail_msg" target="_blank">+86 21 68896229</a></span><br class="gmail_msg">
</span><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">M</span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<span class="m_5609626365442085205signedit gmail_msg"><a href="tel:+86%20136%204189%205907" value="+8613641895907" class="gmail_msg" target="_blank">+86 13641895907</a></span> <br class="gmail_msg">
</span><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">E</span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<span class="m_5609626365442085205signedit gmail_msg"><a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a></span><br class="gmail_msg">
</span><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg"><a href="http://www.zte.com.cn/" class="gmail_msg" target="_blank">www.zte.com.cn</a></span><span style="font-family:宋体;color:black" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p style="margin-left:36.0pt" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
</div></div>
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
</blockquote></div>