Thursday, 2018-06-21

*** bobh has joined #openstack-vitrage00:22
*** bobh has quit IRC02:24
*** bobh has joined #openstack-vitrage02:33
*** bobh has quit IRC02:47
*** ifat_afek has joined #openstack-vitrage04:34
*** ifat_afek has quit IRC04:35
*** e0ne has joined #openstack-vitrage05:13
*** e0ne has quit IRC05:14
*** eyalb has joined #openstack-vitrage05:28
openstackgerritsunqingliang proposed openstack/vitrage master: fix typos  https://review.openstack.org/57684007:34
*** e0ne has joined #openstack-vitrage07:40
*** eyalb has quit IRC07:54
*** eyalb has joined #openstack-vitrage07:55
*** ifat_afek has joined #openstack-vitrage08:55
openstackgerritsunqingliang proposed openstack/vitrage master: fix typos  https://review.openstack.org/57684008:58
e0newill vitrage have ptg this fall? I don't see it in the list :(09:01
*** e0ne has quit IRC09:01
opetrenko_Hello, I'm trying to refactor vitrage config usage. Therefore I have a question, maybe we should restructure config opts, and config groups?09:20
eyalbsend a pull request and we will review it09:24
opetrenko_ok, just wanted to discuss, should I refactor it, or it will be just a waste of time09:25
eyalband please explain the config refactoring is needed09:25
opetrenko_In commit message?09:25
eyalbyes09:26
eyalbyou can explain here also if you want09:27
*** e0ne has joined #openstack-vitrage09:55
*** e0ne has quit IRC10:10
*** e0ne has joined #openstack-vitrage10:12
*** e0ne has quit IRC10:16
openstackgerritAnna Reznikov proposed openstack/vitrage master: don't mark deleted if alarm or edge already marked  https://review.openstack.org/57712410:59
*** e0ne has joined #openstack-vitrage11:58
openstackgerritMerged openstack/vitrage master: fix typos  https://review.openstack.org/57684012:09
sq4indhey, trying to setup vitrage (again) and now I am getting this errors: https://pastebin.com/LhBtbUh7 Any ideas ?12:20
sq4indnvm fixed :D12:24
*** bobh has joined #openstack-vitrage12:32
ifat_afeksq4ind: Great :-) let us know if you need any other help12:34
sq4indifat_afek: looks like everything is working. Now trying to setup dashboard12:35
ifat_afekCool12:36
*** ifat_afek has quit IRC12:43
sq4inddashboard working :D12:48
sq4indcool thing added to the top bar in openstack web dashboard ! :)12:49
sq4indI like it12:49
eyalbyes windriver guys did it12:49
*** bobh has quit IRC12:55
sq4indok and here comes problems12:58
sq4indso almost everything works12:58
sq4indbut somehow I cannot see alarm from nagios in the vitrage12:58
sq4indinstead I am getting this errors in graph.log: https://pastebin.com/U7Y6UuAY12:58
sq4indany ideas ?12:58
eyalbdid you add nagios as a datasource in vitrage.conf ?12:59
sq4indeyalb: of course in a section [nagios] and in datasources/types13:00
eyalbwhat version of vitrage are you using ?13:01
sq4indlatest available in centos 7.5 (queens) rpm version is: openstack-vitrage-graph-2.3.0-1.el7.noarch13:06
eyalbfrom the error it looks like the nagios is not registered ? can you paste the vitrage.conf13:08
eyalbmaybe the exception you sent is an old exception before nagios was registered ?13:09
sq4indeyalb: do you want whole vitrage.conf ?13:09
eyalbyes13:09
sq4indok let me prepare it13:10
eyalbclean the graph.log and do restart graph to check that the exception is from now13:11
sq4indok will do13:11
sq4indeyalb: https://pastebin.com/g9fDau3q - vitrage.conf13:14
sq4indafter clearing log and restarting service logs is clean13:17
eyalbthe conf file looks ok13:17
eyalbok13:17
sq4indhowever I cannot see any alert in vitrage13:17
sq4indand I've forced alarm on one of the nova hosts13:17
sq4indthe critical one13:18
sq4indwith cpu utilization13:18
eyalbif you use the cli you also don't see an alarm ?13:18
eyalbdid you write a conf file mapper for nagios ? called nagios_conf.yaml ?13:21
openstackgerritMerged openstack/vitrage master: don't mark deleted if alarm or edge already marked  https://review.openstack.org/57712413:24
eyalbhttps://docs.openstack.org/vitrage/latest/contributor/nagios-config.html13:24
sq4indeyalb: yes13:24
sq4indI will clear alert and try again13:26
eyalbcan you check the collector logs to see if you have errors also13:26
sq4indlooking13:26
sq4indno errors in collector.log13:27
sq4indlet me check one more thing13:28
sq4indlast time I had a problem with naming when nova1 were in critical state nova10 was marked as red in vitrage13:28
eyalbthere is a missing dependency between collector and graph13:29
eyalbcan you do a restart to collector and then to the graph13:29
sq4indyep I can13:30
sq4indlet me just check it13:30
sq4indlooks like it started working13:34
sq4indsome kind of working13:34
sq4indand I have the same issue that I had before... in my case: nova10 has alarm, nova1 host is ok... vitrage is displaying that nova1 has a problem and nova10 is ok13:39
sq4indand btw - when I am doing in cli: openstack rca resource list I cannot see any nova.host type resources13:41
sq4indis it ok ?13:41
eyalbsq4ind: I need to go can you send your problem to the mailing list me and ifat will look at it on sunday13:49
sq4indeyalb: yep I will, can you plese tell me the @ of mailing list ?13:50
eyalbopenstack mailing list you need to put ion the subject [Vitrage]13:51
sq4indok coll13:51
sq4indcool* will do it shortly13:51
sq4indthanks13:51
eyalbhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev13:51
eyalbmy pleasure13:52
*** eyalb has quit IRC13:57
*** e0ne has quit IRC16:30
*** aasmith has quit IRC16:51
*** aasmith has joined #openstack-vitrage16:54
*** e0ne has joined #openstack-vitrage17:30
*** e0ne has quit IRC19:17

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!