Hi Volodymyr, Seems like the problem is that the alarm does not get connected to the port. In your collectd_conf.yaml, you should write:
collectd: - collectd_host: silpixa00399503/ovs_events/qvo818dd156-be (collectd resource name) type: neutron.port name: qvo818dd156 (openstack neutron port name) By doing this, you cause any Collectd alarm that is raised on the Collectd source named silpixa00399503/ovs_events/qvo818dd156-be to be connected in Vitrage to a resource of type neutron.port with name qvo818dd156. Try to look in the output of ‘vitrage topology show’ (you did not attach it to the mail) and see the exact details of the port. Let me know if it helped, Ifat. From: "Mytnyk, VolodymyrX" <volodymyrx.myt...@intel.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, 6 July 2017 at 23:59 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Cc: "Tahhan, Maryam" <maryam.tah...@intel.com> Subject: Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph Hi Ifat, Thank you for your help. See my response on your questions below: · You see the neutron port in your entity graph, and it is connected to the VM V: yes, it’s correct. · You see the alarm on the alarms view, and its resources is the neutron port V: I see the alarm, sent by collectd , on the alarm page (or vitrage alarm list). Not sure how to check the alarm resources? · You see the alarm in the entity graph, connected to the neutron port V: The Alarm is show on the entity graph, but it’s NOT connected to the neutron port. · You are asking why the neutron port in the entity graph is green and not red? V: The neutron port doesn’t change the color at all. I’ve validated and tried the suggested template but unfortunately it doesn’t help. I still see the alarm on the graph but it is not connected to neutron port. Also, the neutron port desn’t change the state. Please note, that I’m using master branch for the Vitrage in my environment. Also, attaching the topology dump with raised alarm. Used configurations : ==================== collectd: - collectd_host: silpixa00399503/ovs_events/qvo818dd156-be type: neutron.port name: qvo818dd156 # What name we should use here in case of neutron.port? metadata: name: ovs_interface_down description: ovs interface down definitions: entities: - entity: category: ALARM type: collectd name: qvo818dd156 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 actions: - action: action_type: set_state action_target: target: port properties: state: ERROR Thanks and Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Thursday, July 6, 2017 10:01 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Cc: Tahhan, Maryam <maryam.tah...@intel.com> Subject: Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph 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.myt...@intel.com<mailto:volodymyrx.myt...@intel.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Thursday, 6 July 2017 at 17:18 To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Cc: "Tahhan, Maryam" <maryam.tah...@intel.com<mailto:maryam.tah...@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
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev