Wednesday, 2018-12-19

openstackgerritMerged openstack/monasca-common master: Add description-file field to setup.cfg  https://review.openstack.org/62317501:01
*** bobh has joined #openstack-monasca03:25
*** bobh has quit IRC04:30
*** bobh has joined #openstack-monasca04:43
*** bobh has quit IRC05:22
*** dpawlik has joined #openstack-monasca07:21
*** dpawlik has quit IRC07:25
*** dpawlik has joined #openstack-monasca07:36
*** dpawlik has quit IRC07:36
*** dpawlik_ has joined #openstack-monasca07:36
*** pcaruana has joined #openstack-monasca08:03
*** pcaruana has quit IRC08:24
*** pcaruana has joined #openstack-monasca08:33
*** pcaruana has quit IRC08:41
openstackgerritAdrian Czarnecki proposed openstack/monasca-agent master: Add python classifier to setup.cfg  https://review.openstack.org/62612109:02
*** rodolof has joined #openstack-monasca09:10
*** dougsz has joined #openstack-monasca09:13
*** rodolof has quit IRC09:39
*** rodolof has joined #openstack-monasca09:40
openstackgerritAdrian Czarnecki proposed openstack/monasca-ui master: Add python3.5 classifier  https://review.openstack.org/62469609:42
openstackgerritAdrian Czarnecki proposed openstack/monasca-common master: Add python3.5 classifier to setup.cfg  https://review.openstack.org/62466309:44
openstackgerritAdrian Czarnecki proposed openstack/monasca-api master: Add python3.5 classifier to setup.cfg  https://review.openstack.org/62466109:45
openstackgerritAdrian Czarnecki proposed openstack/monasca-common master: Add missing build dependencies for agent in docker  https://review.openstack.org/62060609:46
*** rodolof has quit IRC10:51
*** rodolof has joined #openstack-monasca10:51
*** rodolof has quit IRC11:03
*** dpawlik_ has quit IRC11:09
*** dpawlik has joined #openstack-monasca11:09
*** dpawlik has quit IRC11:13
*** dpawlik has joined #openstack-monasca11:13
*** dpawlik has quit IRC11:14
*** dpawlik has joined #openstack-monasca11:14
*** dpawlik has quit IRC11:16
*** dpawlik has joined #openstack-monasca11:17
*** dpawlik has quit IRC11:17
*** dpawlik has joined #openstack-monasca11:17
*** rodolof has joined #openstack-monasca11:20
*** rodolof has quit IRC11:52
*** rodolof has joined #openstack-monasca11:53
*** dougsz has quit IRC12:03
*** rodolof has quit IRC12:05
*** dpawlik has quit IRC12:06
openstackgerritAdrian Czarnecki proposed openstack/monasca-events-api master: Reconfigure tempest configuration  https://review.openstack.org/62294012:21
*** dpawlik has joined #openstack-monasca12:50
openstackgerritMerged openstack/monasca-agent master: Add python classifier to setup.cfg  https://review.openstack.org/62612112:56
*** dougsz has joined #openstack-monasca12:57
openstackgerritMerged openstack/monasca-ui master: Add python3.5 classifier  https://review.openstack.org/62469612:58
*** bobh has joined #openstack-monasca13:04
openstackgerritAdrian Czarnecki proposed openstack/monasca-events-api master: Reconfigure tempest configuration  https://review.openstack.org/62294013:15
openstackgerritMerged openstack/monasca-common master: Add python3.5 classifier to setup.cfg  https://review.openstack.org/62466313:30
*** bobh has quit IRC14:25
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,chaconpiza15:00
joadavisgood morning15:00
witek#startmeeting monasca15:00
openstackMeeting started Wed Dec 19 15:00:39 2018 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 joadavis15:01
witektoday the first time in #openstack-monasca15:02
joadavis=-O15:03
witekjust posted a short reminder in the old channel15:03
witekagenda for today:15:03
witekhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:03
dougszhey all15:03
witekhi dougsz15:04
witek#topic Vitrage integration15:04
*** openstack changes topic to "Vitrage integration (Meeting topic: monasca)"15:04
*** dpawlik has quit IRC15:04
witekwe had some discussion with Ifat and Joseph about the integration with Vitrage15:04
*** dpawlik has joined #openstack-monasca15:05
witekand how the monitored resources (or alarms) should be identified in Vitrage15:05
witekhere the email list discussion:15:05
witekhttp://lists.openstack.org/pipermail/openstack-discuss/2018-December/000806.html15:05
*** dpawlik has quit IRC15:06
joadavisI didn't reply to his last email, but have been trying to dig up any alarm details that may be helpful.  I haven't explored the topic deeply before15:06
joadavisI think what he proposed is on the right track15:06
*** dpawlik has joined #openstack-monasca15:06
joadavisas I understand it, metrics from vms and metrics from hosts have different metric names, which may help15:07
witekin the change from Bartosz (POC from Berlin) he uses custom dimensions: resource_type and resource_id15:08
witekdo you think we could use such schema for all metrics?15:08
joadavissome metrics have the resource_id already, but I don't think any have type15:08
joadavisI think you could infer the type from the metric itself15:09
witekmost of the checks have the possibility to configure own `custom` dimensions per check instance15:09
witekbut that's e.g. not the case for libvirt15:10
joadavisIs there a resource_type in vitrage they are trying to match with?15:11
*** dpawlik has quit IRC15:11
witeklet me check their docu15:11
witekhttps://docs.openstack.org/vitrage/latest/contributor/vitrage-template-format.html15:12
witekthey define entity type, but I guess it's not what is meant15:13
witekas resource_type I understand e.g: node, instance, disc, interface15:13
joadavisthat is the impression I got too. That it would be used to differentiate hosts from vms, etc15:14
witekOK, and how should we treat e.g http_check?15:15
witekthat's pretty generic15:15
joadavistrue, good point.  That is probably most generic15:16
witekI think it's difficult to create a global mapping for metric of that type15:16
witeksimilarly process15:18
joadavishttp_alive_status does have service field.  For a vm it adds component and resource_id, but for a host those fields are missing15:18
joadavisdo you think we could add a resource_type to all metrics? it might be useful, just don't know how much work that would be15:19
joadavisnot sure how we would define a resource_id for a process, as it is not an OpenStack resource in all cases15:20
joadavisSimilar questions come up for aggregated metrics.  If the metric used to trigger the alarm is aggregated across all VMs, then we don't have a resource_id15:21
joadavisThat might be a use case we should discuss with them15:23
witekI have joined the self-healing meeting today morning (EU time)15:23
*** dpawlik has joined #openstack-monasca15:23
witekand we had a longer discussion with Ifat15:23
joadaviscool15:23
witekshe wants to propose a spec and start to define use cases we should cover15:24
joadavisThat sounds like a good idea. A starting set of use cases could keep us from digging too deep15:24
witekthere is another self-heeling meeting today in 2 hours, I guess15:25
witekI have to think over this mapping thing, still don't have a clear picture on it15:25
witekhere the logs from today's meeting:15:26
witekhttp://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-19-09.02.log.html15:26
joadavisthanks15:26
joadavisIf nothing comes up, I may join in at 9am PST15:27
witekthanks, I'm not sure myself yet15:27
witekshould we move on?15:27
*** dpawlik has quit IRC15:27
joadavisSpeaking of SIGs, have you seen anything about the auto-scaling sig starting meetings?15:28
witekno15:28
joadavisI think it has been quiet for a week15:28
joadavisI don't think it needs meetings yet, but I would like to start contributing to their use cases too15:28
joadavisyes, next topic. :)15:29
witekyes, we could publish our documentation there15:29
witek#topic spaces in dimension names15:29
*** openstack changes topic to "spaces in dimension names (Meeting topic: monasca)"15:29
joadavisyes, I saw Matthias' comments on the bug this morning15:30
joadavisI think it may be an acceptable workaround, but will check with the team and let support comment15:30
witekso, the reported case is about deployment using collecting libvirt metrics15:30
witekthe dimensions zone and tenant_name are set by the plugin15:31
witekand include spaces15:31
witekare in general dimensions values with spaces something we should support?15:31
joadavisfair question15:33
joadavislooking at the designs and documentation, I think there was an assumption that fields like zone and tenant_name would be unique identifiers and not long descriptions15:33
joadavisunique, human parsable identifiers. :)15:33
witekapparently API accepts it and it's not explicitly forbidden in the API ref15:34
joadavisI'm not sure how in this case someone set values iwth spaces without causing trouble at the cli or api, but you are right that it appears it accepted it15:34
joadavisin general, it does seem like we want dimensions to be flexible and there may be other fields that we would want to support spaces in15:35
joadavisI haven't looked in to the persister code for influxdb. How hard would it be to add escaping or something to support spaces?15:35
witekcould you check if Cassandra persister supports it?15:35
joadavisI asked the team, but I don't think James is online yet. :)15:36
witekInfluxDB has syntax for this, should not be very difficult15:36
joadavisI'll follow up witg them today15:36
witekthe problem is more our matrix Python/Java + InfluxDB/Cassandra15:37
witekthanks joadavis15:37
joadavisyes, I was surprised it was a problem for influx15:37
witekOK, let's follow up on this after holidays15:38
joadaviswill do15:38
witek#topic events listener15:38
*** openstack changes topic to "events listener (Meeting topic: monasca)"15:38
witekdougsz has added small comments15:39
joadavisSpec looks approved, though Doug had a couple good nits. I think we can merge and I'll do a quick follow-up to fix the nits15:39
joadavisunless you want me to fix it first. :)15:39
witekOK, let's do this15:39
witekit's up to you :)15:39
dougszSounds good to me15:39
witekjust gave W+115:40
joadavisthanks15:40
witek:)15:40
witekgreat job, thanks joadavis and Ashwin15:40
dougszyep, thanks guys, will be a really nice feature15:41
witekthanks dougsz for constructive remarks and discussion15:41
dougszI certainly didn't do any of the hard work :)15:42
joadavisI was finally watching the RH presentation on monitoring with Prometheus from Berlin summit. It is interesting when they come to some of the same conclusions, and have a similar event listener component. :)15:42
witek:)15:42
witekgetting back to this presentation, I think we could also consider adding support for collectd15:43
joadavisI've been pondering what a good solution for container monitoring will be.  collectd may be a good choice15:44
dougszcadvisor is also a nice one for containers15:44
joadavisI'm still slightly clueless though. :)15:44
joadavisyes... was it ceilometer that was using cAdvisor?15:45
dougszhmm, pass15:45
openstackgerritMerged openstack/monasca-specs master: Monasca Events Publishing Spec  https://review.openstack.org/58380315:46
dougszwitek: we would have a Monasca Agent plugin to harvest collectd metrics?15:46
dougszOr were you thinking about something that submits them directly to the API?15:47
witekI rather thought about monasca plugin for collectd15:47
dougszAh, I see.15:47
witekI think it's main advantage is that it's lightweight and performant15:47
joadavisI'm all for light weight. on of the reoccurring concerns when deploying monasca is that it is too heavy15:48
dougszAnd here we are talking about adding Events support to it :)15:48
witek:)15:48
dougszAt least it is modular though, so the collector can always be turned off in favour of collect or something.15:49
dougszThe statsd part is actually very useful to us.15:49
joadavismodular is a good thing15:49
dougsz+115:49
witekif we don't have anything else for today, I would like to wish you Merry Christmas15:51
witekand have a good start in the new year!15:51
joadavisIt may be worth defining a 'monasca light stack' for smaller deployments.15:51
joadavisMerry Christmas!15:51
dougszThanks, Merry Christmas to you all too15:51
dougszHope you get some quality time off...15:52
joadavisI'm looking forward to time with the kids15:52
joadavisI need to line up some interactive science experiments with them. :)15:53
witektomorrow we have a new additional meeting in the morning15:54
witekand then a break until Jan, 2nd15:54
witekthank you guys and bye bye15:54
witek#endmeeting15:55
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"15:55
openstackMeeting ended Wed Dec 19 15:55:06 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
dougszThanks all, until next year..15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-12-19-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-12-19-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-12-19-15.00.log.html15:55
joadavisTschuss15:55
*** dougsz has left #openstack-monasca15:58
*** bobh has joined #openstack-monasca16:06
*** bobh has quit IRC16:06
*** bobh has joined #openstack-monasca16:08
*** dpawlik has joined #openstack-monasca16:26
*** dpawlik has quit IRC16:30
*** dpawlik has joined #openstack-monasca16:42
*** dpawlik has quit IRC16:46
openstackgerritJoseph Davis proposed openstack/monasca-specs master: Fix a few nits in events-listener spec  https://review.openstack.org/62636216:52
*** dpawlik has joined #openstack-monasca16:58
*** dpawlik has quit IRC17:03
openstackgerritMerged openstack/monasca-specs master: Fix a few nits in events-listener spec  https://review.openstack.org/62636217:21
*** dpawlik has joined #openstack-monasca17:48
*** dpawlik has quit IRC17:53
*** dpawlik has joined #openstack-monasca18:04
*** dpawlik has quit IRC18:09
*** dpawlik has joined #openstack-monasca19:25
*** dpawlik has quit IRC19:30
*** dpawlik has joined #openstack-monasca19:41
*** dpawlik has quit IRC19:46
*** witek_ has joined #openstack-monasca20:16
*** bobh has quit IRC20:53
*** bobh has joined #openstack-monasca21:29
*** bobh has quit IRC21:34
*** dpawlik has joined #openstack-monasca21:42
*** dpawlik has quit IRC21:46
*** dpawlik has joined #openstack-monasca21:58
*** dpawlik has quit IRC22:02
*** bobh has joined #openstack-monasca22:19
*** witek_ has quit IRC22:20
*** bobh has quit IRC22:23
*** bobh has joined #openstack-monasca22:55
*** joadavis has quit IRC22:56
*** bobh has quit IRC23:00
*** bobh has joined #openstack-monasca23:15
*** bobh has quit IRC23:38
*** dpawlik has joined #openstack-monasca23:59

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