Wednesday, 2019-02-27

*** joadavis has joined #openstack-monasca00:06
*** spsurya has joined #openstack-monasca04:15
*** winstein has joined #openstack-monasca05:30
*** openstackgerrit has joined #openstack-monasca06:55
openstackgerritJoseph Davis proposed openstack/monasca-ceilometer master: Adding example configuration files WIP  https://review.openstack.org/63957706:55
*** pcaruana has joined #openstack-monasca08:13
*** witek has joined #openstack-monasca08:17
*** pcaruana has quit IRC08:28
*** pcaruana has joined #openstack-monasca08:42
*** pcaruana has quit IRC08:51
*** pcaruana has joined #openstack-monasca08:58
*** pcaruana|afk| has joined #openstack-monasca09:01
*** pcaruana has quit IRC09:03
*** dougsz has joined #openstack-monasca09:05
openstackgerritWitold Bedyk proposed openstack/monasca-common master: Add wrapper for Confluent Kafka client consumer  https://review.openstack.org/63872509:49
*** pcaruana|afk| has quit IRC13:09
*** pandy has joined #openstack-monasca14:46
witekCourtesy Monasca meeting reminder in #openstack-monasca: witek, jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz_,fouadben, amofakhar, aagate, haruki,kaiokmo,pandiyan,charana,guilhermesp,chaconpiza,toabctl14:55
*** pcaruana has joined #openstack-monasca14:57
toabctlhi14:57
witekhi toabctl14:58
joadavisgood morning14:58
witeklet's wait few minutes for people to roll in14:58
witekhi joadavis14:58
witek#startmeeting monasca15:00
dougszhey all15:00
openstackMeeting started Wed Feb 27 15:00:17 2019 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
witekhi dougsz15:00
witekthe agenda for today:15:00
witekhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
witekfeel free to add topics15:00
witek#topic OpenStack release dates15:01
*** openstack changes topic to "OpenStack release dates (Meeting topic: monasca)"15:01
witekjust a reminder15:01
witekwe're approaching a couple of dates in the release schedule15:01
witekNon-client library freeze being the first ont15:02
witekone15:02
witektomorrow15:02
witekit affects mainly monasca-common15:02
dougszWould be nice to get this change in if that's possible: https://review.openstack.org/#/c/638423/15:03
dougszOops, sorry, note relevant15:03
dougsz*not15:03
witekwould be good anyway :)15:04
dougsz*monasca-agent change for statsd15:04
witekwe have 2 last minute changes in monasca-common15:04
witekhttps://review.openstack.org/63719015:04
witekand Kafka https://review.openstack.org/63872515:05
witekI'll have a look at the validation change tonight15:05
witekI think we can probably also merge https://review.openstack.org/62676115:06
witekthe next date is next week15:07
witekfor python-monascaclient15:07
witekand then RC1 on March 2115:07
witekplease have a look through the repos and check which changes should land until then15:08
witek#topic Kafka client15:09
*** openstack changes topic to "Kafka client (Meeting topic: monasca)"15:09
witekI've pushed implementation for the Kafka consumer in monasca-common15:09
witekhttps://review.openstack.org/63872515:09
dougszGreat to see this moving forward, need to take a closer look at that review when I have time15:10
witekit has become much simpler than the kafka-python one15:10
witekwhich makes me wondering if we indeed shouldn't move it out from monasca-common15:10
*** mohankumar has joined #openstack-monasca15:11
joadavisIf we move it out of monasca-common, how many places would we need to duplicate it?15:12
dougszI suppose the pattern of being able to swap in another kafka client and not update all the other monasca projects is a good one.15:12
dougszIf the wrapper can be generic enough15:12
witekdougsz: that's a point for leaving it in monasca-common, at least in the first phase15:13
witekjoadavis: producer in api and notification15:13
witekconsumer in persister and notification15:13
witekthen we also have monasca-transform15:14
witekif we decide to leave it in monasca-common, I would like to merge it before the freeze this week, so that we can complete the work in Stein15:15
dougszDo you have a Monasca deployment with that wrapper running in production?15:15
witekI know it's very short, but the code will not break anything for now15:15
witekno15:16
joadavis+1 for merging it now15:17
dougszI see, so you can get it in now, and then patch it up after the deadline15:17
dougsz(if it needs patching up when you come to use it)15:18
witekyes, I'm adding unit tests right now, should be ready tonight15:18
witekshould we move on?15:20
witek#topic Dropping parse errors in monasca-persister15:20
*** openstack changes topic to "Dropping parse errors in monasca-persister (Meeting topic: monasca)"15:20
witekhttps://review.openstack.org/63858915:20
witekthe change allows for dropping the messages being blocked due to parsing errors in InfluxDB15:21
witekbut I think the actual reason might be the newer version of InfluxDB which we currently test15:22
witekI haven't checked that though15:23
dougszYeah, need to investigate more - I have hit similar problems to this with badly formatted metrics breaking the persistor15:23
witekwhat was the reason?15:24
dougszI forget exactly now, but invalid characters in metric or something. Caused by metrics generated from logs not going via the Monasca API for validation.15:25
joadavisI think that commit would be fine if we can get to the root cause.  I might like more detail in the log message if possible, and wonder if it should be error instead of warning15:27
witekmonasca-persister is our performance bottleneck that's why I'm a little reluctant15:29
witekand also I would like to add full support for newer InfluxDB if that's the root cause of the problems15:29
dougszyeah - I agree it needs more investigation15:30
witekbut I'm fine with merging this one if we don't fine a better way15:30
witek#topic legacy jobs migration to Bionic15:31
*** openstack changes topic to "legacy jobs migration to Bionic (Meeting topic: monasca)"15:31
witekthere is a recent thread on mailing list about moving to Bionic for all jobs15:32
witekI've checked that we still build jars with legacy Xenial jobs15:32
witekI think in the thread mainly testing jobs were meant15:32
witekbut we should migrate these anyway15:33
witekegacy-monasca-{common,api,persister,thresh}-maven-build15:33
witeklegacy-monasca-{common,persister,thresh}-localrepo-upload15:33
witekwe're actually not publishing API jar anymore15:34
witekI guess we can remove building this as well, right?15:34
witekmeaning legacy-monasca-api-maven-build15:34
witekI'll create a story in backlog for this15:36
witekif someone has time, can take care of it15:36
witekI hope it works without greater problems15:36
witek#topic metrics grouping15:37
*** openstack changes topic to "metrics grouping (Meeting topic: monasca)"15:37
witekmohankumar: is that one yours?15:37
pandyHi witek, that's mine :)15:38
witekhi pandy15:38
mohankumarwitek : It's pandy15:38
pandyfirst would like to thanks all for accepting paper to present at denver summit.15:38
witekcongratulations!15:38
joadaviscongratulations!!15:39
dougsz+115:39
mohankumarpandy : congrats mate !15:39
pandycoming to point, currenly VM dimesions are grouping with tenant_id & resource_id15:39
pandywe had feedback from end users to have "tenant_name" & "resource_name"15:40
pandyso would like to add that feature, looking forward your advise15:41
witekdocumentation says "VM name and tenant name (in addition to default IDs) can be provided as dimensions if vm_name and tenant_name are provided in the list of metadata keys."15:42
joadavisso either the names can be included in the metric when generated, or they can be matched up against data in post-processing15:43
pandyhttps://github.com/openstack/monasca-agent/blob/9ee96263e9b7ae03c8a061cfecaa4e8fcda1bd87/docs/Libvirt.md#vm-dimensions15:43
pandyI could see that in documents, but when we query metrics with dimensions "tenant_name" getting invalid parameter ?15:44
witekhttp://git.openstack.org/cgit/openstack/monasca-agent/tree/docs/Libvirt.md#n7015:45
witekplease check `metadata` in you libvirt plugin configuration15:45
pandyok, I will check15:48
witekhttps://github.com/openstack/monasca-agent/blob/master/monasca_agent/collector/checks_d/libvirt.py#L20615:48
witekthat should work, I guess15:49
witek#topic open stage15:50
*** openstack changes topic to "open stage (Meeting topic: monasca)"15:50
witekdo we have anything else?15:50
witekoh, I haven't noticed the new entry in agenda15:51
pandyokay, thanks. I got it :)15:51
witek#topic custom alerting templates15:51
*** openstack changes topic to "custom alerting templates (Meeting topic: monasca)"15:51
mohankumarwitek : please review and approve :)15:52
mohankumarhttps://blueprints.launchpad.net/monasca/+spec/add-custom-alert-templates15:52
witekthat's something that we have in our backlog for some time already15:52
mohankumarwitek : okay15:53
witekthere is a story for templating Slack notifications15:53
mohankumarwitek: I see let me check15:53
witekhttps://storyboard.openstack.org/#!/story/200130815:53
witekwe definitely need something similar for emails as well15:54
witekbtw. we don't use launchpad anymore and moved to Storyboard15:54
dougszagreed, I need to finish the Slack one15:54
witekhere is the board with current tasks:15:55
witekhttps://storyboard.openstack.org/#!/board/11115:55
pandyyes, i remember that i was discussed same with dougsz some time back to customise notification at present it's verbose mode and hard to understand quickly15:55
witekmohankumar: is that something that you could/would like to work on?15:56
mohankumarwitek : yes , I 'll sync with dougsz  and will find way to customize for email15:57
pandydougsz, would like to know status of slack notification ? if fine i can work on customising mail onle15:57
witekcould you please create a story for this?15:57
mohankumarwitek : sure !C15:58
witekgreat, thanks15:58
witekwe have to wrap up15:58
witekanother meeting in 2 min.15:58
mohankumarwitek: another question , for bug reporting you use storyboard or launchpad ?15:59
witekthanks for joining15:59
pandythanks :)15:59
witekand please have a look on Kafka change later today or tomorrow15:59
witekbye15:59
dougszbye all, will check Kafka change tomorrow15:59
witekmohankumar: storyboard15:59
mohankumarthanks all !15:59
witekand tag it with `bug`15:59
mohankumarwitek : got it !15:59
witek#endmeeting15:59
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"15:59
openstackMeeting ended Wed Feb 27 15:59:57 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-27-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-27-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-27-15.00.log.html16:00
joadavisOh, one last question (post meeting) - do we have an idea which days at the PTG we will meet for Monasca?  I am guessing that Thursday will be the most popular day for projects to try to meet16:00
*** winstein has quit IRC16:10
*** pcaruana has quit IRC16:57
*** mohankumar has quit IRC17:18
*** pandy has quit IRC17:21
*** dougsz has quit IRC18:02
*** spsurya has quit IRC19:52
witekjoadavis: I don't have any info about PTG schedule yet21:08
openstackgerritWitold Bedyk proposed openstack/monasca-common master: Add wrapper for Confluent Kafka client consumer  https://review.openstack.org/63872522:19
*** witek has quit IRC22:54
*** chaconpiza has quit IRC23:19

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