<div dir="ltr">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.<div><br></div><div>So is there particular reason why you need to create duplicate name? can it be something like event-alarm-{event_type}-{seq_number} ?</div><div><br></div><div>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.<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 10:30 PM, Weyl, Alexey (Nokia - IL) <span dir="ltr"><<a href="mailto:alexey.weyl@nokia.com" target="_blank">alexey.weyl@nokia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>