Open Stack

Hi,


In case you missed it, we have a POC of a Monasca datasource for Vitrage
[1] J  Thanks Bartosz Zurkowski for the effort!

There is one issue that we need to close though – how to connect the
Monasca alarms to the resources in Vitrage.

In order to connect an alarm to a resource, Vitrage should be able to
identify that resource in its entity graph using the dimensions coming from
Monasca. I understood that these dimensions are configurable and not
pre-defined.


Basically, there are two cases.

1.       For OpenStack resources, all Vitrage needs to know is the UUID of
the resource. I assume that there is always a dimension for that resource,
right? Is the dimension always called the same? If not, how can Vitrage
identify that this is the interesting dimension (if there are other
dimensions for this alarm)?


2.       For other resources it is more complicated, as they might not have
a natural unique id. For example, a NIC id in Vitrage may be generated out
of the host name + NIC name. Monasca alarm may have two separate dimensions
for the host and nic. How can Vitrage understand that those two dimensions
identify the resource? In other cases, Vitrage may need a resource_type
dimension to uniquely identify the resource.


Another question: I understood that Monasca can send alarms that originate
from other monitors like Ceilometer, Prometheus etc. What are the
dimensions in these cases?

Monasca team, I’ll be happy to hear your opinion about these questions. If
you can provide several different examples it will be very helpful.


Thanks,

Ifat


[1] https://review.openstack.org/#/c/622899
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181211/c7b93c19/attachment.html>