Open Stack

Hi Volodymyr,

Let me see if I understood the problem correctly. Are my assumptions right?

·         You see the neutron port in your entity graph, and it is connected to the VM

·         You see the alarm on the alarms view, and its resources is the neutron port

·         You see the alarm in the entity graph, connected to the neutron port

·         You are asking why the neutron port in the entity graph is green and not red?

The template that you used as an example is not what you are asking for. This template states that if there is an alarm on the host (in your case, the alarm is on the neutron port), and the host contains an instance -> raise an alarm on the instance and set its state to suboptimal. The template that (I think) you need is more simple: if there is an alarm on a neutron port, set its state to error.

Below is the template that I think you should use. Note that I haven’t tested it locally (because I don’t have the same environment as yours), so there could be errors. As a first step, make sure you are using the correct collectd alarm name (use ‘name’ and not ‘rawtext’ which is Zabbix-specific), and then run ‘vitrage template validate’ to verify its correctness.


metadata:
 name: ovs_interface_down
 description: ovs interface is down
definitions:
 entities:
  - entity:
     category: ALARM
     type: collectd
     name: <put the collectd alarm name here>
     template_id: collectd_alarm
  - entity:
     category: RESOURCE
     type: neutron.port
     template_id: port
 relationships:
  - relationship:
     source: collectd_alarm
     relationship_type: on
     target: port
     template_id : collectd_alarm_on_port
scenarios:
 - scenario:
    condition: collectd_alarm_on_port
     - action:
        action_type: set_state
        action_target:
         target: port
        properties:
         state: ERROR


Let me know if it helped,
Ifat.

From: "Mytnyk, VolodymyrX" <volodymyrx.mytnyk at intel.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Thursday, 6 July 2017 at 17:18
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Cc: "Tahhan, Maryam" <maryam.tahhan at intel.com>
Subject: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Hi All,

                We are trying to configure the collectd and Vitrage service to raise an alarm in the Vitrage and show the alarm on the graph if a VM interface goes down. The collectd & collectd_vitrage plugin have been configured to send the notification if the OvS interface connected to VM  goes down (using OvS events plugin). In our case, when interface goes down, the collectd event is sent to Vitrage and we’re able to see it on the Alarm page. But we would like to show the alarm on the Entity Graph (highlighting the neutron port) but for some reason it doesn’t work. The https://github.com/openstack/vitrage/blob/master/tools/load_generator/templates/vm_0.yaml template has been used as a base for our scenario (changing `zabbix` datasource to `collectd` in the file). Our collectd datasource configuration (collectd_conf.yaml) looks like this (tried both variants):

collectd:
- collectd_host: silpixa00399503/ovs_events/qvo818dd156-be
   type: neutron.port
   name: qvo818dd156-be

collectd:
- collectd_host: silpixa00399503/ovs_events/qvo818dd156-be
   type: nove.host
   name: silpixa00399503

Our setup configuration looks like this:

|HOST| ---->  |VM| ---> |NEUTRON.PORT|---> |NEUTRON.NETWOR|

Any help on the issue would be much appreciated.

Thanks and Regards,
Volodymyr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170706/92dc1a32/attachment-0001.html>