| *** yujunz has joined #openstack-vitrage | 00:20 | |
| *** yujunz is now known as yujunz[away] | 00:49 | |
| *** yujunz[away] is now known as yujunz | 00:49 | |
| *** tovin07 has joined #openstack-vitrage | 00:52 | |
| *** yujunz is now known as yujunz[away] | 00:59 | |
| *** yujunz[away] is now known as yujunz | 00:59 | |
| *** yujunz is now known as yujunz[away] | 01:06 | |
| *** yujunz[away] is now known as yujunz | 01:07 | |
| *** yujunz is now known as yujunz[away] | 01:08 | |
| *** yujunz[away] is now known as yujunz | 01:08 | |
| *** yujunz is now known as yujunz[away] | 01:18 | |
| *** yujunz[away] is now known as yujunz | 01:26 | |
| *** yujunz is now known as yujunz[away] | 01:36 | |
| *** yujunz[away] is now known as yujunz | 01:38 | |
| openstackgerrit | gecong proposed openstack/python-vitrageclient: Remove white space between print and () https://review.openstack.org/384785 | 02:19 |
|---|---|---|
| -openstackstatus- NOTICE: Jobs running on osic nodes are failing due to network issues with the mirror. We are temporarily disabling the cloud. | 02:49 | |
| *** yujunz is now known as yujunz[away] | 03:10 | |
| *** yujunz[away] is now known as yujunz | 03:14 | |
| *** yujunz is now known as yujunz[away] | 03:28 | |
| *** yujunz[away] is now known as yujunz | 04:41 | |
| *** yujunz is now known as yujunz[away] | 04:52 | |
| *** yujunz[away] is now known as yujunz | 05:37 | |
| *** ifat_afek has joined #openstack-vitrage | 05:53 | |
| *** ifat_afek has quit IRC | 06:35 | |
| *** tovin07 has quit IRC | 06:40 | |
| *** tovin07 has joined #openstack-vitrage | 06:41 | |
| *** tovin07 has quit IRC | 06:41 | |
| *** tovin07 has joined #openstack-vitrage | 06:42 | |
| *** ifat_afek has joined #openstack-vitrage | 06:42 | |
| *** yujunz has quit IRC | 06:44 | |
| *** yujunz has joined #openstack-vitrage | 06:44 | |
| tovin07 | Hello, | 06:49 |
| tovin07 | Does anyone know why we have to set zabbix_resource_name, resource_name, and resource_type when config "Forward to vitrage" action? | 06:49 |
| tovin07 | I found that enrich_event(at vitrage/datasources/zabbix/driver.py:175) will re-set it to `host` and pre-config `name` and `type` at /etc/vitrage/zabbix_conf.yaml. | 06:49 |
| tovin07 | Current zabbix message template (missing zabbix_resource_name, resource_name, and resource_type): | 06:49 |
| tovin07 | host={HOST.NAME1} | 06:49 |
| tovin07 | hostid={HOST.ID1} | 06:49 |
| tovin07 | hostip={HOST.IP1} | 06:49 |
| tovin07 | triggerid={TRIGGER.ID} | 06:49 |
| tovin07 | description={TRIGGER.NAME} | 06:49 |
| tovin07 | rawtext={TRIGGER.NAME.ORIG} | 06:49 |
| tovin07 | expression={TRIGGER.EXPRESSION} | 06:49 |
| tovin07 | value={TRIGGER.VALUE} | 06:49 |
| tovin07 | priority={TRIGGER.NSEVERITY} | 06:49 |
| tovin07 | lastchange={EVENT.DATE} {EVENT.TIME} | 06:49 |
| tovin07 | P/S: All of the above has not been write in any documentation. I found them after dug into error log and source code. Zabbix datasource configuration (in /etc/vitrage/vitrage.conf) is missing in documentation and vitrage.conf.sample. Documentation for zabbix_conf.yaml is missing too (I clone sample config from nagios_conf.yaml). | 06:49 |
| tovin07 | Thanks! | 06:49 |
| ifat_afek | tovin07: Hi :-) | 07:22 |
| ifat_afek | I didn’t realize zabbix documentation was missing, we will fix it. It’s good that you looked at nagios as an example, as the configuration is very similar | 07:23 |
| ifat_afek | Let me try to explain about zabbix configuration | 07:24 |
| ifat_afek | zabbix defines triggers on hosts/items, but it is not aware of any resource type. If you get the information from zabbix, you have no way of knowing that “overcloud-controller-0” is a controller and “overcloud-compute-2” is a compute. | 07:30 |
| ifat_afek | In order to solve this, we created zabbix.conf, where you can define for every zabbix_host the actual vertex in Vitrage it should map to. Zabbix driver should pass the event to zabbix transformer, and zabbix transfomer should state that the new alarm vertex should be related to a resource vertex of type X and name Y. This will result in adding an alarm vertex to the graph and connecting it with an “on” relationship to the correct resource. | 07:33 |
| ifat_afek | resource type is essential in order to identify the right vertex, and we can’t tell it by simply looking at zabbix | 07:33 |
| ifat_afek | I hope that was clear… if not please ask again | 07:33 |
| ifat_afek | what do you mean by “current zabbix message template”? | 07:35 |
| *** yujunz is now known as yujunz[away] | 07:47 | |
| *** yujunz[away] is now known as yujunz | 07:48 | |
| *** yujunz is now known as yujunz[away] | 07:48 | |
| *** yujunz[away] is now known as yujunz | 07:51 | |
| *** yujunz is now known as yujunz[away] | 07:51 | |
| openstackgerrit | Merged openstack/vitrage-dashboard: sunburst improvements https://review.openstack.org/384194 | 07:53 |
| *** yujunz[away] is now known as yujunz | 07:54 | |
| *** yujunz is now known as yujunz[away] | 07:54 | |
| *** yujunz[away] is now known as yujunz | 07:57 | |
| *** yujunz is now known as yujunz[away] | 07:57 | |
| *** yujunz[away] is now known as yujunz | 07:58 | |
| tovin07 | Thanks for your answer | 08:05 |
| tovin07 | "current zabbix message template" ~ Default Message from here https://github.com/openstack/vitrage/blob/master/doc/source/zabbix_vitrage.rst | 08:05 |
| tovin07 | As you said that resource type is essential, do I need to include in in zabbix default message? | 08:07 |
| ifat_afek | You should not modify zabbix default message. You should configure it in zabbix.conf instead. Let me send you a short example | 08:29 |
| ifat_afek | zabbix: | 08:30 |
| ifat_afek | - zabbix_host: overcloud-controller-0.localdomain | 08:30 |
| ifat_afek | type: tripleo.controller | 08:30 |
| ifat_afek | name: overcloud-controller-0.localdomain | 08:30 |
| ifat_afek | - zabbix_host: overcloud-compute-4.localdomain | 08:30 |
| ifat_afek | type: nova.host | 08:30 |
| ifat_afek | name: overcloud-compute-4.localdomain | 08:30 |
| tovin07 | Great | 08:31 |
| tovin07 | Thank you | 08:32 |
| *** hieulq_ has joined #openstack-vitrage | 08:37 | |
| ifat_afek | Happy to help | 08:38 |
| ifat_afek | If you have any other questions don’t hesitate to ask, either in IRC or on the mailing list (with [vitrage] tag). Note that today and tomorrow is a holiday in Israel, so we might get back to you only on Thursday | 08:39 |
| *** yujunz has quit IRC | 08:41 | |
| *** hieulq has quit IRC | 08:41 | |
| pava | Hello ifat_afek | 08:41 |
| ifat_afek | pava: Hi :-) | 08:42 |
| *** yujunz has joined #openstack-vitrage | 08:43 | |
| pava | I am trying to deploy vitrage on an OPNFV/openstack deploy schenarion an I got help from you and eyal a few times | 08:44 |
| pava | I managed to isntall the dashboard and the api so to speak | 08:44 |
| pava | but i am getting some errors I am having difficulties troubleshooting :) | 08:45 |
| pava | when I start the api service I get this output http://hastebin.com/oxovesohub.sql | 08:45 |
| ifat_afek | I looked at the exception, unfortunately I don’t understand why it happened. Can you send it on the mailing list? I hope Eyal or someone else will be able to solve it on Thursday. | 08:51 |
| ifat_afek | Sorry for not being able to help at this stage | 08:51 |
| *** ifat_afek has quit IRC | 09:01 | |
| pava | No problem :) I will describe de scenario more throughly also it was versy skim description :) | 09:03 |
| *** openstack has joined #openstack-vitrage | 09:31 | |
| *** yujunz is now known as yujunz[away] | 09:48 | |
| *** tovin07 has quit IRC | 09:59 | |
| *** yujunz[away] is now known as yujunz | 10:02 | |
| *** yujunz has quit IRC | 10:15 | |
| *** yujunz has joined #openstack-vitrage | 10:24 | |
| *** yujunz has quit IRC | 10:29 | |
| *** yujunz-zte has joined #openstack-vitrage | 10:29 | |
| *** yujunz-zte has quit IRC | 10:31 | |
| *** yujunz has joined #openstack-vitrage | 10:32 | |
| *** yujunz has quit IRC | 10:36 | |
| *** openstackgerrit has quit IRC | 11:48 | |
| *** openstackgerrit has joined #openstack-vitrage | 11:49 | |
| *** yujunz has joined #openstack-vitrage | 12:04 | |
| *** yujunz has quit IRC | 12:12 | |
| *** yujunz-zte has joined #openstack-vitrage | 12:12 | |
| *** yujunz-zte has quit IRC | 12:16 | |
| *** yujunz has joined #openstack-vitrage | 12:16 | |
| *** openstackgerrit has quit IRC | 12:18 | |
| *** openstackgerrit has joined #openstack-vitrage | 12:18 | |
| *** yujunz has quit IRC | 12:19 | |
| *** yujunz has joined #openstack-vitrage | 13:59 | |
| *** yujunz has quit IRC | 14:41 | |
| *** yujunz has joined #openstack-vitrage | 14:41 | |
| *** yujunz has quit IRC | 15:01 | |
| *** ifat_afek has joined #openstack-vitrage | 16:12 | |
| *** ifat_afek has quit IRC | 16:14 | |
| *** ifat_afek has joined #openstack-vitrage | 21:16 | |
| *** ifat_afek has quit IRC | 21:22 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!