14:30:33 #startmeeting metrics team 14:30:33 Meeting started Thu Nov 1 14:30:33 2018 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:43 please add any topics that are still missing. 14:31:23 https://storm.torproject.org/grain/YYTsbtLcpvGTrBF2Zs4XrJ 14:32:06 no more topics from me 14:32:32 gaba: anything from you? 14:33:30 no 14:33:36 alright, starting. 14:33:39 * Monitoring for operational issues (irl) 14:34:03 i have been working on writing nagios plugins for monitoring various operational issues. i think we should be able to finish this roadmap item pretty soon. 14:34:12 awesome!! 14:34:14 the first issue addressed already has the new plugin deployed, #28242, so now we know: when an individual onionoo instance is misbehaving and when its varnish is misbehaving. we still test to see that going to onionoo.tpo works, but we only test one of the haproxy frontends when we do this. the architecture for haproxy<->varnish<->onionoo may need some rethinking at some point to actually 14:34:17 failover nicely so for now i'm considering that check finished. 14:35:10 sounds good. 14:35:13 the next issue is onionperf. i've got a plugin in #28271 that checks to see that the analyze task has been running. we will also check pings, and that the tgen server is running on the internet. i've got some plugins for looking at onion services (that i'm trying to make somewhat reusable) but i've hit a problem: 14:35:15 https://github.com/robgjansen/onionperf/issues/42 14:35:19 basically every time you start onionperf you get a new onion address so this makes monitoring pretty difficult. as we're updating the onionperf's tor version etc. anyway, i'm going to see if we can fix this and update at the same time. 14:36:18 okay. 14:36:28 we should have checks in place for collector and for metrics-web too. we want checks that are deeper than just "there is a webserver running" so we should think about what these checks do. 14:36:30 i wonder if there are some common failure modes we should watch out for. 14:36:51 I might already have a list somewhere. 14:36:58 I can give that some thoughts next week. 14:37:26 ok cool. if you can send it to the metrics-team list then i can see it in the archive and give it some thought then 14:37:43 i will be travelling so won't have email, but can still check the archives on the web 14:37:46 do we have a list with current checks? 14:37:58 the current checks is just the onionoo one 14:38:27 I guess I mean that plus the current changes, with considerations what we're monitoring and why. 14:38:34 and what we're not monitoring and why. 14:38:50 ah ok, the two tickets above then have all the details 14:38:54 okay. 14:39:48 that's all i have for this topic 14:40:00 cool! 14:40:28 * Hackfest in January/February 2019 (karsten) 14:40:37 regarding dates, 14:41:20 I could arrive on jan 30 in the afternoon and stay until feb 4 in the morning. 14:41:34 that's 1/2 wednesday, thursday, friday for the hackfest 14:41:40 and saturday and sunday for fosdem. 14:41:57 unfortunately, I cannot attend the whole week before fosdem. 14:42:21 so it would be only 3 days for metrics. Unless irl and the other person we will have meet before 14:42:40 i plan to arrive on the 27th 14:42:44 ok, let's add that to the pad so jon knows 14:42:45 and leave on the 4th 14:42:51 i've already got this on the pad 14:42:56 I could stay another day after. 14:43:05 but I need to be here on the 29th. 14:43:13 ok, np 14:43:15 i think after fosdem will be not that useful 14:43:20 hehe 14:43:25 i mean, i will be not that useful 14:43:29 plausible. 14:43:38 is there anybody else you want to invite? 14:43:42 that you think should be there 14:43:44 our new dev. 14:43:50 which we don't have yet. 14:43:51 yes 14:43:53 who* 14:44:24 are there things you could do with network team folks on monday, tuesday, and wednesday morning? 14:44:36 yes, they are going to be there the whole week 14:44:58 that is other question, interaction with network team 14:45:00 right. I wonder if irl could work with them on something cross-team related. 14:45:06 they are going to be mostly working on refactoring 14:45:12 other than friday that will be roadmap 14:45:48 we can have one morning for roadmap retrospective at the metrics team too 14:45:55 potentially there are controlport things that are useful to metrics that could do with face-to-face interaction with network team 14:46:21 teor was suggesting to work on privcount with you both 14:46:34 gaba: let's collect possible topics like that one. (the retrospective) 14:46:45 right ok, i'm happy to look at privcount stuff too 14:46:51 https://pad.riseup.net/p/tor-metricsteam-agenda-hackweek-2019.1-keep 14:46:52 and maybe the new dev could arrive on the 27th, too. 14:46:53 :) 14:47:04 :) ok. 14:47:18 so, I'll write down 30th to 4th as my dates then. 14:48:22 great, that's all from me on that topic. 14:48:28 i will look at booking travel as soon as i can, to get the best price 14:48:44 ah, I'll be driving by car. 14:48:50 the votes look like we are going to just be in brussels 14:48:52 I can take 3 people with me to fosdem. 14:49:05 or 2 people and 2 small people. 14:49:27 okay. 14:49:34 yes 14:49:41 even better. 14:49:52 we need to look at costs too. 14:50:47 regarding the decision whether we're going to brussels or somewhere else? 14:51:27 anyway, not something we can discuss today. 14:51:43 moving on? 14:51:46 yes 14:52:04 * Kick off CollecTor Python PoC (karsten) 14:52:11 it's a new month! 14:52:25 and there's not as much time remaining this year anymore. 14:52:47 we need to start working on the collector rewrite soon. 14:53:12 I was wondering, given that you're going to be offline next week, irl, whether I can start doing something for the collector deliverable next week. 14:53:26 yes, i think this will be my big project for once the monitoring is complete 14:53:29 I hope to not write as much code for this. 14:53:45 but maybe I can prepare this for you to pick up. 14:54:10 what's your plan for starting this? 14:54:24 if you could write a list of requirements for the relaydescs module then that would be a great start 14:54:48 I can certainly do that. do you have anything in mind as format? 14:55:08 otherwise I'll produce a braindump, but I'm not sure whether that's as useful for you. 14:55:17 if you can do markdown, eventually this would turn into rST and be documentation 14:55:27 but markdown is fine for now 14:55:53 ok. markdown sounds fine. 14:56:03 but what do you expect to read in those requirements? 14:56:32 how detailed should they be? 14:56:48 how often things should be fetched, what documents we should fetch and in what order 14:57:29 okay. 14:57:47 cool. is on the list. 14:57:50 thanks (: 14:57:56 sure! 14:58:08 another thing that came to mind when reading your announcement. ;) 14:58:09 * Possible to prioritize #28116 review? (karsten) 14:58:24 I was mainly thinking whether I can move that forward while you're away. 14:58:40 yes, i can make sure this is done before monday 14:59:08 okay, that would be really cool. if it doesn't work out, it's okay. if it does, awesome! :) 14:59:31 * Monthly report (karsten) 14:59:40 I started a draft. 14:59:47 let me put it on the pad. 15:00:04 there it is. 15:00:46 this is less urgent. 15:00:56 I just figured that we could get this out this week. 15:01:04 but we can as well send it in 1.5 weeks. 15:01:08 did you add a link to the draft report somewhere? 15:01:16 I pasted it to the agenda pad. 15:01:49 do you have it? 15:02:01 i might be able to look at this on the train on monday if there is not time before then 15:02:16 I'd say that's soon enough. 15:02:19 later would work, too. 15:02:25 it is 8 hours of train, so it will probably fit in 15:02:28 hah 15:02:40 let me refresh it as i dont see it 15:02:52 below announcements. 15:03:06 ah yes 15:03:37 okay, moving on: 15:03:38 * Tomorrow's retrospective and roadmap update: open or closed? (karsten) 15:03:57 regarding the open/closed part, I think I assumed these were closed. 15:04:22 We can have it close. I was not sure if there is somebody else should be there. 15:04:39 I can't think of anybody. 15:04:43 That is why I was sending both of you a message to see if we send it to the metrics team mailing list or not. 15:04:45 I was thinking it's a team-internal thing. 15:04:46 ok then 15:04:54 In that case we may not have anybody :) 15:04:55 can we create a new channel? 15:04:58 yes 15:04:59 ah, yes. 15:05:05 we could do that, too. 15:05:27 that is, have the meeting and tell any strangers coming by that it's supposed to be a team-internal meeting. 15:05:53 the issue is that we don't have a team-internal mailing list. 15:05:59 let's remove the link to the place of the meeting then from the pad 15:06:05 and we create one before the meting 15:06:09 ok. 15:06:55 any question about how we are going to do it? 15:07:08 what you sent sounds like a fine plan! 15:07:37 ok 15:07:49 we're also doing the roadmap update tomorrow, right? 15:08:09 yes 15:08:13 okay. 15:08:18 we can do the roadmap after the retrospective 15:08:28 sounds good. 15:08:51 that answers my question on this topic. moving on? 15:08:56 yes 15:09:05 * Timesheet reminder (karsten) 15:09:17 i have just submitted my timesheets 15:09:21 just a reminder that we need october timesheets very soon. 15:09:34 including this weeks? 15:09:37 week's 15:09:53 yes 15:09:57 okay, perfect. 15:10:02 thanks! 15:10:17 last topic: 15:10:18 * Next meeting time after daylight savings ended (karsten) 15:10:31 though, before we talk about that: are we going to have a meeting next week? 15:10:42 it sounds like you're away from the internet anyway, irl, right? 15:10:49 or just email? 15:11:01 i would have internet 15:11:05 but probably can't attend the meeting 15:11:13 okay. 15:11:25 let's skip next week then. 15:11:28 i also will be remotely participating in the ietf on bangkok time 15:11:34 so this will be interesting 15:11:40 heh 15:11:53 ok 15:11:58 for the week after, let's think about shifting time to standard time. 15:12:14 you mean change the time of the meeting? 15:12:21 yes. 15:12:31 I have another meeting in 15 minutes. 15:12:45 which is going to be moved by 1 hour soon. 15:12:58 i prefer to not believe in DST 15:13:06 and not make any changes based on it 15:13:07 oh, me, too. 15:13:12 I blame the others. 15:13:14 ;) 15:13:18 :) 15:13:23 if we make a change then we should make the change that means we don't have to make another 15:13:42 then it will collide with the other meeting. 15:13:53 next summer. 15:14:01 next summer europe doesn't have DST 15:14:03 still, not having a 1 hour gap would be good. 15:14:08 yes, but the states. 15:14:23 (maybe I'm confusing things now, this gets far too complicated...) 15:14:50 okay, how about this: 15:14:55 yes, DST moves all the meetings 1 hour earlier for US :/ 15:15:12 no meeting next week, meeting at usual time the week after, where we discuss moving or not. 15:15:23 it sounds good 15:15:28 ok\ 15:15:52 alright. 15:15:57 I think we're done. 15:16:00 whee. 15:16:19 (: 15:16:28 thanks, irl and gaba! have a good day/evening! bye. :) 15:16:38 #endmeeting