[openstack-dev] [vitrage] reference a type of alarm in template

Rosensweig, Elisha (Nokia - IL) elisha.rosensweig at nokia.com
Mon Aug 15 18:15:46 UTC 2016


The "type" means where it was generated - aodh, vitrage, nagios...

I think you are looking for"name", a field that describes the actual problem. We should add that to our documentation to clarify.

Sent from Nine<http://www.9folders.com/>
From: Yujun Zhang <zhangyujun+zte at gmail.com>
Sent: Aug 15, 2016 16:10
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [vitrage] reference a type of alarm in template

I have a question on how to reference a type of alarm in template so that we can build scenarios.

In the template sample [1], an alarm entity has three keys: `category`, `type` and `template_id`. It seems `type` is the only information to distinguish different alarms. However, when an alarm is raised by aodh, it seems all alarms are assigned entity type `aodh` [2], so are they shown in dashboard.

Suppose we have two different types of alarms from `aodh`, e.g. `volume.corrupt` and `volume.deleted`. How should I reference them separately in a template?

[Screen Shot 2016-08-15 at 8.44.56 PM.png]


[1] https://github.com/openstack/vitrage/blob/master/etc/vitrage/templates.sample/deduced_host_disk_space_to_instance_at_risk.yaml#L8
[2] https://github.com/openstack/vitrage/blob/master/vitrage/datasources/aodh/transformer.py#L75

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160815/e1c28a26/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-08-15 at 8.44.56 PM.png
Type: image/png
Size: 82131 bytes
Desc: Screen Shot 2016-08-15 at 8.44.56 PM.png
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160815/e1c28a26/attachment.png>

More information about the OpenStack-dev mailing list