<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Fan,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The reason we need such a thing is because in Vitrage (which is an Openstack Root Cause Analysis Engine) we may raise a deduced alarms on (for example) each
instance in the host, and we would like this name to be a human readable alarm (as you said yourself) without any random strings in order that it will be user and human friendly. Over time, the {seq-num} would grow and become less convenient and readable.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In addition, we would like to give the users the ability to listen \ do a webhook on a specific alarm name (so if we will have a random string attached to
each name, it won’t be possible). With your suggestion, we would need to at the very least be able to register to a set of alarms using regex – is this supported?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For more information about Vitrage:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="https://wiki.openstack.org/wiki/Vitrage">https://wiki.openstack.org/wiki/Vitrage</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Alexey<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ZhiQiang Fan [mailto:aji.zqfan@gmail.com]
<br>
<b>Sent:</b> Tuesday, May 03, 2016 6:05 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Alarm name unique constraint is only applied to each project, I don't remember the original cause, but in our customer's environment, alarm will be showed in the portal, with their name, no uuid, because user will be confused about such
a random like string, then if alarm name can be duplicated, it is hard for them to differ between alarms.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So is there particular reason why you need to create duplicate name? can it be something like event-alarm-{event_type}-{seq_number} ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Anyway, it is not so hard to remove this constraint, I just want to say that alarm name should be meaningful, otherwise it makes no difference with UUID: not human friendly.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, May 3, 2016 at 10:30 PM, Weyl, Alexey (Nokia - IL) <<a href="mailto:alexey.weyl@nokia.com" target="_blank">alexey.weyl@nokia.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
First of all, I wanted to thank again to all the participants in the fruitful Aodh-Vitrage design session in Austin :)<br>
<br>
I wanted to show in this email, the problem that we have when creating 2 event alarms with the same name.<br>
Here is what I got in the command line:<br>
<br>
stack@ubuntu-devstack:/etc/vitrage$ ceilometer alarm-list <br>
+----------+------+-------+----------+---------+------------+-----------------+------------------+<br>
| Alarm ID | Name | State | Severity | Enabled | Continuous | Alarm condition | Time constraints |<br>
+----------+------+-------+----------+---------+------------+-----------------+------------------+<br>
+----------+------+-------+----------+---------+------------+-----------------+------------------+<br>
<br>
stack@ubuntu-devstack:/etc/vitrage$ ceilometer alarm-event-create --name 'Event Alarm 2' --state alarm --event-type 'my.event'<br>
+---------------------------+--------------------------------------+<br>
| Property | Value |<br>
+---------------------------+--------------------------------------+<br>
| alarm_actions | [] |<br>
| alarm_id | 96f11384-abd7-4c11-b0a5-678646c11e79 |<br>
| description | Alarm when my.event event occurred. |<br>
| enabled | True |<br>
| event_type | my.event |<br>
| insufficient_data_actions | [] |<br>
| name | Event Alarm 2 |<br>
| ok_actions | [] |<br>
| project_id | bec13d47c22e45a9948981f5cb1ba45b |<br>
| query | [] |<br>
| repeat_actions | False |<br>
| severity | low |<br>
| state | alarm |<br>
| type | event |<br>
| user_id | d8812494489546aca8341af184eddd2c |<br>
+---------------------------+--------------------------------------+<br>
<br>
stack@ubuntu-devstack:/etc/vitrage$ ceilometer alarm-list<br>
+--------------------------------------+---------------+-------+----------+---------+------------+----------------------+------------------+<br>
| Alarm ID | Name | State | Severity | Enabled | Continuous | Alarm condition | Time constraints |<br>
+--------------------------------------+---------------+-------+----------+---------+------------+----------------------+------------------+<br>
| 96f11384-abd7-4c11-b0a5-678646c11e79 | Event Alarm 2 | alarm | low | True | False | query: [] | None |<br>
| | | | | | | event_type: my.event | |<br>
+--------------------------------------+---------------+-------+----------+---------+------------+----------------------+------------------+<br>
<br>
stack@ubuntu-devstack:/etc/vitrage$ ceilometer alarm-event-create --name 'Event Alarm 2' --state alarm --event-type 'my.event'<br>
Alarm with name='Event Alarm 2' exists (HTTP 409) (Request-ID: req-b05dd105-fd23-47d3-a0b6-940bde6bcdd8)<br>
<br>
<br>
Do you think it is possible to drop the uniqueness of the alarm name in Aodh (for the Vitrage use cases that we talked about in the design session)?<br>
<br>
Best regards,<br>
Alexey Weyl<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>