[00:51:32] Analytics-Wikimetrics: Epic: WikimetricsUser shares a cohort - https://phabricator.wikimedia.org/T69461#1130857 (Fhocutt) [01:45:13] springle: yt? [01:47:08] nuria: hi! [01:47:18] springle: have time for 1 question? [01:47:39] Analytics-Tech-community-metrics, MediaWiki-Developer-Summit-2015, ECT-March-2015: Achievements, lessons learned, and data related with the MediaWiki Developer Summit 2015 - https://phabricator.wikimedia.org/T87514#1130942 (Rfarrand) More updates added, not quite finished. Comments so far? [01:48:43] nuria: yep [01:48:50] springle: k, this table: [01:48:55] https://www.irccloud.com/pastebin/RfMEwUHQ [01:49:10] has an id field w/o an auto_increment [01:49:58] is that something we removed? [01:50:11] nuria: i guess so? the master is the same [01:51:27] springle: ok, i do not understand how that can be, will research, as old EL code creates tables with id field with autoincrement and newer EL code (deployed this week) will create tables w/o that id [01:51:48] nuria: the only person i know of manually touching EL tables recently on the master is ori. perhaps he touched it. if not, some bug [01:52:09] i di reall something about him truncating a table and recreating, but idk the details [01:53:29] nuria: should we fix it, or do you wish to investigate first? [01:54:31] springle: I think i will investigate and let you know. [01:55:52] nuria: https://phabricator.wikimedia.org/T91031 might be a logical place to discuss this (as an aside). and if other tables may be affected [01:56:43] springle: ok, got it [01:58:40] springle: that is odd cause seems that it is not related to code [01:58:58] ori: yt? [09:08:32] Analytics, Analytics-Kanban: Turn off WP Zero's Limn-Dashboards & put up a "moved sign" - https://phabricator.wikimedia.org/T92920#1131227 (QChris) >>! In T92920#1130547, @kevinator wrote: > Spoke to Dan and this isn't as simple as dropping in an index.html where the current dashboards are. > > Easiest s... [09:47:56] Analytics-Tech-community-metrics, MediaWiki-Developer-Summit-2015, ECT-March-2015: Achievements, lessons learned, and data related with the MediaWiki Developer Summit 2015 - https://phabricator.wikimedia.org/T87514#1131281 (Qgil) Thank you, this is very interesting. I think the level of detail is eno... [10:32:45] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131462 (yuvipanda) NEW [10:33:14] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131469 (yuvipanda) I am temporarily moving the biggest of the files (51G eventlogging_processor-client-side-events.log.1) on to /srv. Someone who knows m... [10:59:32] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131505 (yuvipanda) The biggest logs seem to be filled with validation errors about https://meta.wikimedia.org/wiki/Schema:Edit [11:09:41] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131534 (yuvipanda) p:Triage>Normal [11:58:23] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131591 (yuvipanda) p:Normal>Unbreak! Free space is being gobbled up really fast still, and won't last more than a few hours. @nuria Is the eventl... [11:58:59] qchris: around? [12:00:18] ah, he isn’t... [12:00:19] I guess? [13:16:44] milimetric: hey [13:16:53] hi YuviPanda [13:16:54] milimetric: https://phabricator.wikimedia.org/T93185 [13:17:00] milimetric: might be causing EventLogging issues [13:17:07] (full disk) [13:17:09] oh coitus [13:17:12] yeah, just read it [13:17:14] hahaha [13:17:15] that's a big problem [13:17:26] yeah [13:17:51] * YuviPanda is on spotty internet atm [13:18:04] especially so because we just realized we might need to go manually repair all the old data [13:18:09] so throwing away the logs can't happen [13:18:27] (all the old data == the bad Edit schema data that we need for VE numbers) [13:18:49] thanks YuviPanda, I'll go have a look [13:19:00] milimetric: yup, I moved some logs to /srv [13:19:06] figured deleting the logs would be terrible [13:19:29] milimetric: yw. [13:19:52] Analytics, Analytics-EventLogging, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131723 (Milimetric) Thanks @YuviPanda for the emergency fix, I'm tagging our team and making this high importance. [13:20:08] Analytics, Analytics-EventLogging, Analytics-Kanban, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131724 (Milimetric) [13:25:11] Ironholds, hi! [13:26:22] Analytics, Analytics-EventLogging, Analytics-Kanban, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131736 (yuvipanda) Cool :) I also copied logs_02_06_onward folder onto /srv to make space as well. [13:26:33] Analytics, Analytics-EventLogging, Analytics-Kanban, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131737 (yuvipanda) Cool :) I also copied logs_02_06_onward folder onto /srv to make space as well. [13:27:15] milimetric: as ops on ‘ops clinic duty’, I have handed this off to you now :) [13:28:31] YuviPanda: acknowledged. Though I will state for the record that giving me ops things is like giving toddlers chainsaws. [13:29:04] milimetric: :D [13:29:43] hey mforns [13:29:58] milimetric, aw, no. Giving ME ops things is like giving toddlers chainsaws [13:30:05] giving you ops things is like giving a moody preteen a chainsaw [13:30:11] don't be so hard on yourself ;p [13:30:59] Ironholds, the isAppPageRequest method you linked me to, is not in the refinery repo? [13:31:12] erm [13:31:15] yes it is? [13:31:22] I'm looking at it literally right now ;p [13:31:32] it is, however, currently a subsection of isPageview and not exposed as its own UDF [13:31:43] Ironholds, in the compiled code in stat1002, I can find isPageview, for example, but not isAppPageRequest [13:31:49] Ironholds: pfft, you haven’t had leslie carr email you stern emails, have you? :P me and milimetric have :) [13:31:51] which is why I said I'd work on it this morning, because pulling it out means (pulling it out + UDF + unit tests) [13:32:12] mforns, yes, because it's a private method within isPageview [13:32:22] frankly I'd be pretty worried if you COULD find it ;p [13:32:23] Oj [13:32:25] oh! [13:32:32] it'd mean I screwed up [13:32:50] so, I'm gonna spend the morning pulling it out and writing unit tests and that'll be bundled into my big architectural change to refinery-core [13:32:55] and then it'll be available! \o/ [13:33:07] Ironholds, my bad, thx [13:33:17] (I'd make it its own distinct thing, but it'll be dependent on said big architectural change and so unless that gets CRd quick, they're going in the same patch [13:33:18] NP! [13:33:32] my bad too :D. [13:33:38] YuviPanda, actually, yes I have ;p [13:33:52] also, she's still deeply amused that her stern emails are talked of in such tones [13:34:19] Ironholds: publicly? :P [13:34:27] indeed! [13:35:02] Ironholds: :D I got started doing ops stuff after that, and now it’s a running gag because someone else in analytics did the same mistake me and milimetric did about 2 days after I started in ops... [13:35:23] same package even, I think [13:35:34] hah! [13:36:26] Ironholds: and equivalent machines! Mine was for stat1, and this time it was stat1003 I think [13:37:46] nice! [13:38:17] mforns, anyway. So, the easiest way to expose this and everything else is if we can get the architectural change merged - https://gerrit.wikimedia.org/r/#/c/197296/ [13:38:30] aha [13:38:34] I think nuria is pretty much happy with it, which is a good sign because Nuria sent me an email before she CRd my first patch [13:38:42] apologising in advance for being much stricter than otto ;p [13:38:51] and, well, she is :P [13:39:28] so once that's in I can throw in the second patch and you can CR if you're comfortable CRing and need it quickly. Shouldn't be hard, I just need to get the unit tests set up; nothing doesn't get unit tests [13:39:43] (except for stringContains and matchesPattern, because if those break, so do all the things with unit tests) [13:40:24] Ironholds, I see [13:40:35] ok, I'll bring this up in our stand-up [13:40:41] cool! [13:40:44] * Ironholds thumbs up [13:40:51] it's weird people ask me for stuff involving code these days [13:40:56] at some point it will get non-weird, I'm sure [13:41:07] :] [13:44:34] hokay, going afk for a bit. Back when everyone is awake :). mforns, LMK the standup outcome! [13:44:52] Ironholds, sure [13:55:15] Analytics, Analytics-EventLogging, Analytics-Kanban, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131817 (Nuria) Sorry I did not send e-mail to team yesterday. The root cause is a huge volume of events that are invalid that we can... [14:11:39] Analytics-Kanban, VisualEditor: VE events need to be sampled - https://phabricator.wikimedia.org/T93201#1131831 (Nuria) NEW a:Milimetric [14:15:17] Analytics-Cluster, Analytics-Kanban: Mobile PMs has reports on session-related metrics from Wikipedia Apps - https://phabricator.wikimedia.org/T86535#1131849 (mforns) a:mforns [14:17:02] Analytics-EventLogging, Analytics-Kanban, VisualEditor: VE events need to be sampled - https://phabricator.wikimedia.org/T93201#1131850 (Nuria) [14:18:05] Analytics, Analytics-EventLogging, Analytics-Kanban, operations: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1131852 (Nuria) Ticket: https://phabricator.wikimedia.org/T93201 [14:27:04] Analytics-EventLogging, Analytics-Kanban, VisualEditor: VE events need to be sampled - https://phabricator.wikimedia.org/T93201#1131880 (kevinator) p:Triage>High [14:28:23] Analytics-EventLogging, Analytics-Kanban, VisualEditor: VE events need to be sampled {lion} - https://phabricator.wikimedia.org/T93201#1131881 (kevinator) [14:29:47] Analytics-Kanban, Analytics-Wikimetrics: Utf-8 names on json reports appear as unicode code points: "\u0623\u0645\u064a\u0646" - https://phabricator.wikimedia.org/T93023#1131895 (kevinator) p:Triage>Normal [14:37:36] Analytics, Analytics-Kanban: Onboard Madhu - https://phabricator.wikimedia.org/T92985#1131920 (kevinator) p:Triage>Normal [14:40:03] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1131931 (kevinator) [15:27:55] nuria: want to deploy EL with me today, or should we wait? [15:28:02] ottomata: we cannot [15:28:14] ottomata: we need to deploy 1st the throttle for invalid events [15:28:49] you making changes to EL code to deploy? [15:28:51] sucheta, I forgot to give you your gift! [15:29:03] * Ironholds clearly now needs to go to LP [15:29:53] ottomata: otherwise we are tiping over .... [15:30:09] ottomata: but i will go from currently deployed changeset [15:30:13] ottomata: not master [15:30:26] ottomata: makes sense? [15:31:11] nuria, wait, what is tipping over? [15:31:14] just the error logs, right? [15:31:17] upstart logs are filling up? [15:31:18] ottomata: El itself [15:31:22] ottomata: yess [15:31:27] that is not EL, that is disk. [15:31:49] ottomata: well if no disk -> process shut down as they cannot log -> el no process events no more [15:32:02] ottomata: yesterday's log was 50G [15:32:10] ottomata: for validation failures [15:32:13] so delete more logs? [15:33:09] this one, right? [15:33:10] eventlogging_processor-client-side-events.log [15:33:14] growing at about 2MB / sec [15:33:25] ottomata: yes, i need to not log every error [15:34:10] ottomata: as we do not need a 50G log every day as it's going to fill machine faster than we can clean it up [15:34:24] nuria, why not just not log the whole event in the error logs? [15:34:26] just the error [15:35:21] or, since this is kind of an emergency stop gap, just logrotate every hour or something [15:35:50] ottomata: I think we should log less, but with enough info so errors are actionable [15:36:03] ok so [15:36:59] ottomata: so per mforns idea we could random sample errors [15:37:10] nuria [15:37:10] here [15:37:11] https://github.com/wikimedia/mediawiki-extensions-EventLogging/blob/master/server/bin/eventlogging-processor#L70 [15:37:14] just remove raw_event [15:37:17] from the log line. [15:37:28] or no [15:37:29] i'm sorry [15:37:29] hm. [15:37:31] no [15:37:32] ottomata: but then errors are not actionable [15:37:35] the stuff in (%s) is the problem [15:37:54] ottomata: the errors we log should have enough info to fix the issue [15:38:02] i'm looking at that file now [15:38:13] each message has the full schema in it [15:38:17] with descriptions of each field [15:38:26] ottomata: ya that is redundant [15:38:31] that is why the file is so huge [15:38:35] yes there are lots of errors [15:38:38] but each line is showing that [15:39:10] ottomata: right, i will remove that. [15:41:39] hm, i think it must be coming from exception thrown by jsonschema.Draft3Validator .validate [15:43:22] you should maybe just catch different types of errors and do things differently [15:44:20] hmmmmmMMMMm [15:44:34] nuria, i don't know python exceptions well, if you print e.message, rather than e. it might do it for you. [15:44:58] ottomata: i will get a codechange as soon as we are out of meeting [15:45:06] ottomata: will add you CR [15:47:11] ottomata: let me use beta labs for a bit cause i can test it there [15:48:31] ja, nuria, i just tried it [15:48:34] i tworks [15:48:35] it works [15:48:49] i can submit patch now, shall I? [15:50:41] it is happening! :) [15:52:06] nuria: https://gerrit.wikimedia.org/r/#/c/197929/1/server/bin/eventlogging-processor [15:52:30] i ididn't commit it on top of my changes, but it i did do it on master...i probably will ahve to put it on its own branch if you want to deploy that without my changes [15:52:34] rigiht? [15:56:56] ottomata: I think that is not going to change matters much, exceptions in python are not like the ones in java [15:57:26] nuria [15:57:29] i tried it, it does. [15:57:30] ottomata: but yes, patch needs to be on top of latest deployed changeset, let me test that in beta-labs [15:57:35] https://github.com/Julian/jsonschema/blob/master/jsonschema/exceptions.py#L62 [15:57:44] if you print the message [15:57:55] it will print everything from that __unicode__ method [15:58:00] which includes the schema [15:58:13] , but you can just print e.message, which is just the error message [15:58:36] ottomata: ah, ok, if you tried then sounds good, let me transplant that [15:58:36] then, in the parens I get [15:58:37] (u'editingSessionId' is a required property) [15:58:44] rather that that HUGE string about everyhting [15:58:55] ottomata: everything and its mom [15:58:59] haha [15:59:03] ottomata: ok, let me transplant [15:59:22] nuria, may it be that my patch that you merged yesterday is causing these issues? [15:59:30] mforns: NOOOOO [15:59:44] mforns: your patch, if anything, reduces throughput from js client [15:59:53] Analytics, Analytics-Kanban: Turn off WP Zero's Limn-Dashboards & put up a "moved sign" - https://phabricator.wikimedia.org/T92920#1132184 (kevinator) Desired outcome: 1- User goes to http://gp.wmflabs.org/dashboards/ncell-nepal 2- User sees message "This Wikipedia Zero dashboard is no longer available...... [15:59:54] mforns: do not worry [16:00:24] nuria, oh again I forgot that the server-side error log, was only for the dev-server [16:00:33] mforns: right [16:04:45] ottomata: this is same on top of current latest deploy: https://gerrit.wikimedia.org/r/#/c/197930/ [16:05:54] nuria, mine was on otp of the latest deploy too [16:05:56] it is the same [16:06:03] ottomata: ahhh sorrry [16:06:05] https://gerrit.wikimedia.org/r/#/c/197929/ [16:06:17] but, i'm not sure how to deploy, cause gerrit wants to rebase it [16:06:20] i think we need to make a branch [16:06:25] or, just deploy it as a patch manually [16:06:33] ottomata: k, you want to deploy it? [16:06:38] would love to ! :) [16:06:43] ottomata: nbo , we deploy on box [16:06:58] ok, so pull from gerrit and deploy? [16:07:00] on /srv/deployment/evenetlogging/Eventlogging [16:07:01] or just edit on box? [16:07:03] and deploy? [16:07:07] ottomata: i do not think there is another way [16:07:13] ottomata: pull from gerrit [16:07:15] we could make a real branch [16:07:26] ottomata: as git-deploy doesn't let you eploy non merged stuff [16:07:27] but, if you want to deploy the kafka thing with me today...then we don't have to do that [16:07:27] :) [16:07:34] right, if we made a branched and merged it there [16:07:44] ottomata: call me grandma but i rather fix one thing at a time [16:07:50] oh indeed [16:07:51] i'm just saying [16:07:58] ottomata: jaja [16:07:59] if we plan on doing a real deploy later, then we can manuallay make this change now [16:08:13] ottomata: let's fix the logging issues 1st [16:08:15] but, if you want to wait a while on that, then we might want to do a real deploy rather than a manual change for this [16:08:36] ottomata: I rather fix the acute problem with manual deploy, we will log it on sal [16:08:40] ok [16:08:48] ottomata: i can do it [16:08:48] just on vanadium, right? [16:08:53] ottomata: yes [16:09:02] naw, show me how. [16:09:07] ottomata: k, [16:09:10] so, checkout this gerrit change, and then python setup install? [16:09:24] ottomata: go to /srv/deployment/eventlogging/Eventlogging and pull from gerrit [16:09:42] ottomata: git fetch https://gerrit.wikimedia.org/r/mediawiki/extensions/EventLogging refs/changes/70/188270/6 && git checkout FETCH_HEAD [16:09:47] ottomata: you will need sudo [16:09:52] k [16:10:14] ottomata: above is an example [16:10:18] ottomata: not real thing [16:10:18] yes [16:10:25] ottomata: then we do [16:10:28] then python setup.py install? [16:10:42] ottomata: git checkout -b changeset [16:10:50] i did that in the same command [16:10:51] like [16:10:55] ottomata: so we know what piece of code we have there [16:11:00] git fetch https://gerrit.wikimedia.org/r/mediawiki/extensions/EventLogging refs/changes/29/197929/2 && git checkout -b error-log-reduction FETCH_HEAD [16:11:00] ottomata: k you are a pro [16:11:11] ottomata: then we do the python install thingy [16:11:17] in server directory [16:11:19] ja [16:11:21] ready for that? [16:11:24] ya [16:11:43] done [16:11:44] ottomata: and then [16:11:56] eventloggingctl stop [16:12:02] eventloggingctl start [16:12:02] the whole thing?! [16:12:06] ok [16:12:20] doing it. [16:12:39] ottomata: and later ps -auxfw [16:12:45] to make sure all started nicely [16:12:50] cool, error logs much smaller now [16:12:53] lets see how much... [16:12:54] ottomata: and tail -f on /var/log/upstart [16:13:29] ok, looks like about 300KB/s now [16:13:33] vs 2MB / sec [16:13:35] before [16:13:45] ottomata: BIG improvement ... pufffff [16:13:59] nuria, btw, do you know pv? [16:14:01] ottomata: lemme look [16:14:01] pipe viewer? [16:14:02] really cool [16:14:10] tail -f /var/log/upstart/eventlogging_processor-client-side-events.log | pv > /dev/null [16:14:22] ottomata: looks good [16:14:33] ottomata: so let's merge this same change to master [16:15:21] ottomata: anbd let's log to sal what we deployed and that's it (for now) BIG thanks! [16:17:25] !log manually deployed change to eventlogging on vanadium that reduces size of error log messages in /var/log/upstart: https://gerrit.wikimedia.org/r/#/c/197929/ [16:18:50] ottomata: super thanks again [16:19:51] ja you know, just being selfish! I wanna deploy! [16:20:08] nuria: we shoudl just rebase and merge this onto master then [16:20:09] https://gerrit.wikimedia.org/r/#/c/197929/ [16:20:16] yes [16:20:30] so the "kafka" changes carry these too. [16:20:48] rebase was fine, i'll let you merge it :) [16:26:35] Analytics, Analytics-EventLogging, Analytics-Kanban, operations, Patch-For-Review: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1132304 (Nuria) Crisis averted, loogs are growing to 300kbs sec not to *ahem* 2MB per sec. Resolving ticket. [16:26:49] Analytics, Analytics-EventLogging, Analytics-Kanban, operations, Patch-For-Review: Disk space full on vanadium from logs in /var/log/upstart - https://phabricator.wikimedia.org/T93185#1132307 (Nuria) Open>Resolved [16:30:16] nuria: so yeah ujmmmm deploy today? circle one: yes/no [16:30:16] ? [16:30:20] :D [16:30:46] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132318 (csteipp) Hi all, I looked through this again and wanted to get some clarification on it. When I talked wit... [16:30:58] ottomata: yes, noon PST? I have two meetings until then [16:31:06] ottomata: is that too late? [16:31:59] hm, nuria, i feel comfortable doing it on my own, but if there was a problem i'd want you around. noon is 3 pm my time, i think that should be fine, right? [16:32:08] even if i have to go, you will be around for a bit more? [16:32:22] ottomata: quite a bit more , like 6/7pm PST [16:32:28] so 6 more hours [16:32:32] ok, then that's fine, let's do it then. [16:32:40] k [16:36:36] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1132335 (mforns) NEW [16:49:56] Analytics-Engineering, Analytics-Wikimetrics: Unable to add a custom cohort user - https://phabricator.wikimedia.org/T91751#1132374 (kevinator) The documentation was anonymously edited today with a better description of the steps to follow: https://www.mediawiki.org/wiki/Analytics/Wikimetrics/Help#Adding_... [17:17:41] Ironholds, I get a gift? YAY. [17:18:06] sucheta, I found a second {{citation needed}} stamp [17:18:57] Oh, you're the best! I want it. [17:23:49] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1132492 (Milimetric) The Rolling New Active Editor metric did not complete for this cohort with default parameters. ``` [2015-03-19 16:18:46,078: INFO/Worker-29] wikimetrics.models.rep... [17:52:09] Analytics, Scrum-of-Scrums, Wikipedia-App-Android-App, Wikipedia-App-iOS-App, and 3 others: Avoid cache fragmenting URLs for Share a Fact shares - https://phabricator.wikimedia.org/T90606#1132599 (dr0ptp4kt) [17:53:33] Analytics, Scrum-of-Scrums, Wikipedia-App-Android-App, Wikipedia-App-iOS-App, and 3 others: Avoid cache fragmenting URLs for Share a Fact shares - https://phabricator.wikimedia.org/T90606#1063059 (dr0ptp4kt) [17:56:50] Analytics, Scrum-of-Scrums, Wikipedia-App-Android-App, Wikipedia-App-iOS-App, and 3 others: Avoid cache fragmenting URLs for Share a Fact shares - https://phabricator.wikimedia.org/T90606#1132651 (dr0ptp4kt) a:dr0ptp4kt [18:00:15] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132687 (Nuria) >When I talked with Aaron about setting the cookie, it was going to be a generic cookie for the mont... [18:04:55] Analytics-Cluster, Analytics-Kanban, Performance: Implement Last-Access cookie [34 pts] {bear} - https://phabricator.wikimedia.org/T88813#1132716 (Nuria) @RobLa-WMF: >Ok, it took me a little bit to wrap my head about what y'all are doing with this, and was kind of skeptical. Assuming I understand this... [18:05:12] Analytics-Cluster, Analytics-Kanban, Performance: Implement Last-Access cookie [34 pts] {bear} - https://phabricator.wikimedia.org/T88813#1132717 (Nuria) [18:17:11] Analytics-Kanban, Patch-For-Review: Failure Types by User Type - https://phabricator.wikimedia.org/T91123#1132784 (Milimetric) Note: this and all other analyses done this quarter for the Edit schema are no longer valid. This is because we have an unknown number of invalid events in our logs that affect th... [18:31:13] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132835 (kevinator) [18:31:14] Analytics-Cluster, Analytics-Kanban: Add processed user agent to refined tables - https://phabricator.wikimedia.org/T91793#1132837 (kevinator) [18:31:15] Analytics-Cluster, Analytics-Kanban: Refine webrequest x_analytics field into a map in the refined table. - https://phabricator.wikimedia.org/T89396#1132836 (kevinator) [18:31:43] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132841 (Anomie) >>! In T92977#1132687, @Nuria wrote: > Cookie lives forever, but its value is changing on every acc... [18:31:52] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132852 (kevinator) [18:31:54] Analytics-Cluster, Analytics-Kanban, Epic: {epic} WMF has UC report per project per month & day {bear} - https://phabricator.wikimedia.org/T88647#1132851 (kevinator) [18:34:28] Analytics-Cluster, Analytics-Kanban: Add user_agent map to refined tables - https://phabricator.wikimedia.org/T91793#1132872 (kevinator) [18:35:01] is there a reason this and related tasks are on the Wikimetrics board? https://phabricator.wikimedia.org/T76761 [18:36:28] fhocutt, kevinator_ put it there, although maybe it was by accident? [18:36:47] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132875 (Nuria) @Anomie Let us know if there are privacy concers but per comments above we do not think there is any... [18:37:09] it doesn't seem to be related, but I don't want to remove it if there was a reason it was there [18:37:42] Analytics-Cluster, Analytics-Kanban: Add x_analytics map to refined tables - https://phabricator.wikimedia.org/T89396#1132880 (kevinator) p:Low>Normal [18:38:36] fhocutt, maybe it has something to do with wikimetrics because it depends on productionizing the scheduler part of it, but I'm not sure [18:39:03] fhocutt: I'm looking at the task again [18:39:40] thanks kevinator_ [18:40:44] fhocutt: yeah, this task should not be in the wikimetrics project [18:40:55] I will move it now and any of its children [18:41:08] thanks! [18:42:37] Analytics-Cluster, Analytics-Engineering: Mondrian has access to the PostgreSQL database - https://phabricator.wikimedia.org/T76766#1132895 (kevinator) [18:42:51] Analytics-Cluster, Analytics-Engineering: make cubes as windows into warehouse - https://phabricator.wikimedia.org/T76767#1132896 (kevinator) [18:43:20] Analytics-Cluster, Analytics-Engineering: EPIC: Aggregating and Shaping the data for browsing - https://phabricator.wikimedia.org/T76761#1132904 (kevinator) [18:44:35] Analytics-Cluster, Analytics-Engineering: Mondrian has access to the PostgreSQL database - https://phabricator.wikimedia.org/T76766#819533 (kevinator) test [18:45:33] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1132925 (Anomie) Both tasks may refer to the same document, but the //discussion// on the other ticket clearly doesn... [18:50:27] Analytics-EventLogging, Analytics-Kanban, VisualEditor, WMF-NDA: Wikitext Eventlogging events not validating - https://phabricator.wikimedia.org/T93242#1132939 (Nuria) NEW [18:51:28] ottomata, yt? [18:52:24] Analytics-EventLogging, Analytics-Kanban, WikiEditor, WMF-NDA: Wikitext Eventlogging events not validating - https://phabricator.wikimedia.org/T93242#1132948 (Catrope) [18:55:14] mforns: ja [18:55:23] hey! [18:55:35] ottomata, are you planning to work on the x-analytics udf? [18:55:59] because if you are on other things, maybe I can do that? [18:57:20] ? [18:57:25] oh the xanalytics map thing? [18:57:30] joal was going to work on it [18:57:37] but ya know, baby happened [18:58:05] https://phabricator.wikimedia.org/T89396 [18:58:16] i think he may have already done some work on it [19:03:03] but mforns i dunno if he has or not [19:03:12] hmm, you looking for things to do? [19:03:13] : [19:03:14] :) [19:03:36] ottomata, no it's because I need it for the other task [19:03:38] mforns: i think joseph has done almost done [19:03:57] mforns: email joseph and ask if he can submit what he has, and we can finish it up [19:04:07] mforns: but maybe if you send him an e-mail you can verify [19:04:15] ah yes sorry [19:04:22] nuria, ottomata: ok, sure [19:04:22] mforns: for now you can just use the udf to extract fields, no? [19:04:29] sorry, or not udf [19:04:30] function :) [19:04:31] umm [19:05:02] https://github.com/wikimedia/analytics-refinery-source/blob/master/refinery-core/src/main/java/org/wikimedia/analytics/refinery/core/Webrequest.java#L69 [19:05:12] ottomata, yes, sure I'll use temporary code until the udf is merged, and send an email to joal [19:05:28] ooohh [19:05:33] ok, thanks! [19:05:55] yup :) [19:06:03] nuria: ya wanna? [19:06:15] ottomata: yes, let's do it [19:06:41] batcave? [19:06:41] yeehaw [19:06:42] k [19:11:39] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1133060 (Milimetric) Even worse, the report appears successful and has a result!! https://metrics.wmflabs.org/reports/result/6da4d2f5-16d7-4285-b5eb-856126fc9833.json [19:11:50] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1133061 (Milimetric) [19:12:41] wow ^ [19:21:32] milimetric, I saw your email, have you found a particular issue in the infrastructure? [19:22:02] mforns: yeah, the fact that we're running huge queries on top of views on a shaky database [19:22:03] :) [19:22:07] but nothing new, no [19:22:15] milimetric, ok [19:26:48] x-analytics map should be pretty trivial [19:27:05] "split on commas, for each split_string, split on equals, first value is key, second value is value, reassemble" [19:48:11] Analytics-Engineering: Pageviews definition undercounts app requests - https://phabricator.wikimedia.org/T93255#1133116 (Ironholds) NEW [20:20:29] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1133211 (kevinator) p:Triage>High [20:34:38] nuria, ping :) [20:46:03] Ironholds: hello [20:46:08] heyo :) [20:46:09] Ironholds: i own you a CR [20:46:28] well, nobody owes me nuthin'! But if you could do it I can get some work done for mforns and updating the PV def :) [20:46:37] Ironholds: qq: do you know how many PVs and uniques we got over the course of the past year? (either full calendar year or past 12 months -- whichever) [20:47:02] ori, uniques is unpossible, but pageviews...let me get my calculator. Including or excluding bots? [20:47:15] excluding [20:47:25] s/calendar/the SQL table I dumped things into [20:47:27] bots view pages? [20:47:31] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1133276 (kevinator) @milimetric, can you clarify: The title refers to RAE, but the comment says RNAE didn't complete. Are all rolling metrics not working? [20:47:49] bots view pages. Bots tend to be run by assholes; the legacy definition didn't even TAG them [20:48:04] (the new one includes them but also includes a nice boolean flag, so we can get sum(pageviews) or sum(pageviews) WHERE is_automata=0) [20:48:12] is_ottomata [20:48:21] * Ironholds snerks [20:48:28] whichever is easier to tally [20:48:34] you know how hard I have to resist writing an isOttomata UDF now? [20:48:38] it just returns TRUE every single time. [20:48:51] or "At our heart of hearts, aren't we ALL aspiring to be Ottomata?" [20:49:08] anyway. Hokey, I can give you PVs for 2014 trivially [20:49:15] is "more than a quarter of a trillion" true? [20:49:25] * Ironholds thinks [20:49:37] 20b month * 12 = 240. maybe that's rounding up a little. [20:49:37] prrrobably not, when you exclude bots and the legacy def's ludicrous overcounting [20:49:45] year, but it's more like 15B a month :/ [20:49:54] the existing data? it counts all banner impressions. [20:49:58] which...gaaaaah. [20:50:26] kevinator, mforns: what's the context for the DataWarehouse tasks on the Wikimetrics board? https://phabricator.wikimedia.org/T76387 [20:50:27] we don't have a rough idea of how many uniques we get in a year? [20:50:45] other than the comscore data, we do not :/ [20:50:49] (pageviews query running) [20:50:58] you don't want to count me as a unique?! [20:51:02] i browse wikipedia sometime! [20:51:03] cmooon! [20:51:03] Ironholds: (thanks, btw!) [20:51:09] fhocutt, looking [20:51:17] (not sure what DataWarehouse is or the goal behind these) [20:51:26] np! [20:51:34] ottomata, no seriously, I am throwing that patch in [20:52:01] public static String isOttomata(){ return "Probably not, statistically speaking. But at our core, do we not ALL aspire to be Ottomata?";} [20:52:17] fhocutt: for metrics like Rolling Active Editor and otherones that Vital Signs needed, [20:52:26] or maybe I should call the public UDF isOttomata and the underlying java ottomated_ottomata() [20:52:33] fhocutt, we are building a datawarehouse which will store the data that wikimetrics needs to generate reports, in a way that it is faster to query [20:52:38] Wikimetrics isn't able to generate these fast enough [20:52:49] ori, 194,894,218,000 and change [20:52:52] ok, thanks! [20:52:58] so we tasked out building a datawarehouse [20:53:18] fhocutt, when we finish to build the warehouse, all metrics that use the current db, will need a rewrite to use the warehouse [20:53:26] is everything intended to move over to use it eventually? [20:53:27] I'm actually making a new run before we kill the sampled logs, and the def has been refined a wee bit, so it's probably a bit higher. But then that undoubtedly contains DDoSing assholes we couldn't find, so it might be lower too. That's the precise approximate number :D [20:53:51] fhocutt, what do you mean with everyhting? :] [20:54:06] all metrics for all users, not just eevs [20:54:57] fhocutt: yes all the metrics should be calcualted using the warehouse... but that's further down the road [20:55:16] Ironholds: thanks very much for that! [20:55:41] Our primary use cases are for Vital Signs, not the metrics used by most of the wikimetrics users [20:55:52] ori, np! [20:55:56] * fhocutt nods [20:56:00] haha [20:56:04] so the transition of wikimetrics to a DW is further down the road [20:57:15] how do the eevs reports affect other reports being run? More general load on the system with heavier queries = slower, or is there something more subtle? [20:58:05] ottomata: done with debian? [20:58:16] Ironholds: do we have uniques per day estimates (from comscore, or any other source)? [20:58:41] not to my knowledge, but Dario would be a better resource for that; he's got more of a handle on the comscore stuff than me :) [20:58:51] ori: for other than apps i do not think so [20:58:54] all I have is 18 american spirits and a harvard sweater [20:58:55] ori: for apps yes [20:59:09] kk, thanks [20:59:41] nuria, ja! had forgotten to fix the timestamp in the vk format though. [20:59:47] checking on it now... [20:59:53] k [21:00:08] will look at Ironholds in the meantime [21:01:04] nuria, I now have the mental image of you unceasingly giving me the hairy eyeball until I scream "okay, okay, I'll remember to edit Changelog.md with the first commit, I swear!" [21:01:16] "just please, stop staring!" [21:09:01] yus! it is working nuria! [21:09:18] the debian or everything, batcave? [21:09:59] ^ ottomata [21:10:27] in batcave [21:25:50] milimetric, qq: when I set SQL_ECHO = True in wikimetrics, which log gets the echoed query? I looked it in upstart, but did not find anything... [21:26:24] leila: Do we have any data about the quality of logged-in responses vs. anon responses in WikiGrok? [21:26:35] mforns: the wikimetrics queue log, I believe [21:26:42] because celery's the one executing [21:26:48] and you have to restart celery [21:27:20] milimetric, yes, makes sense, but I did not find it there... and I restarted vagrant, well, I'll try it again [21:27:32] oh you're in vagrant [21:27:35] hm... [21:28:07] maybe the log level of the queue is set too high? [21:28:09] (CR) Nuria: [C: 1] "I Think it will be nice if Pageview and LegacyPageview can be renamed to PageviewDefinition and LegacyPageviewDefinition, that makes seman" (6 comments) [analytics/refinery/source] - https://gerrit.wikimedia.org/r/197296 (owner: OliverKeyes) [21:28:22] milimetric, oh, I'll check that [21:29:12] mforns: it might be easier to just run the tests [21:29:21] you should see the output in the test output, no? [21:29:36] and you can run just the test you need, one that runs that metric [21:29:37] milimetric, log level is DEBUG, so... [21:29:41] yeah, so that's not it [21:29:44] mforns: whoever executes - as milimetric says- will echo, if it is celery running queries it will be on celery's log , but if it is the website it will be on wikimetrics.web on vagrant [21:29:54] yeah, but it's not showing up in vagrant nuria [21:30:24] whatever you do, Marcel, don't git pull or destroy the vagrant machine :) [21:30:29] milimetric: well, vagrant is not doing nothing there it's sqlalchemy [21:30:33] milimetric, xD [21:31:00] nuria: vagrant is clearly causing some kind of confusion or problem, because logs are not where we'd expect them [21:31:14] so either it's a complexity with restarting the service, or picking up new config, whatever [21:31:22] mforns: where'd you change the config, btw? [21:31:28] in /etc/wikimetrics, right? [21:31:37] oooooooooooooooooh [21:31:38] ok [21:31:39] milimetric: where are logs? mines are were you would expect them [21:31:50] nvm, I think I just found the problem ^ [21:32:00] puppet config, right? [21:32:02] no [21:32:07] milimetric, of course sorry, long time no see wikimetrics [21:32:13] i mean, yeah, you could change the puppet config too [21:32:23] but if you're just turning on SQL_ECHO, no need to do puppet [21:32:33] yes just a quick test [21:32:37] milimetric, mforns i hardcode it on the code and see it fine [21:32:48] kaldari: we haven't looked at that. [21:32:56] nuria: right, he changed the local configs instead of the /etc/wikimetrics ones [21:33:02] milimetric: k [21:33:40] what do you want to use it for, kaldari? [21:34:00] nuria: you got a sec? I wanted to brain-bounce some data-loading for dashiki [21:34:07] leila: It’s on our list of research questions and the wikidata community is interested in it. Would it be difficult to do an analysis on that (even though we don’t have a huge amount of data on logged in users). [21:34:18] i am deploying eventlogging with ottomata , later? [21:34:39] which list of research questions, kaldari? [21:34:46] nuria: no prob, later's fine [21:35:07] leila: https://meta.wikimedia.org/wiki/Research:WikiGrok#Research_questions [21:35:18] milimetric, nuria: it worked, thanks. [21:35:58] I see. we can run an analysis on it kaldari. by when do you need this? [21:36:33] leila: As soon as you can get to it. No hard deadline. [21:36:51] those are the best kaldari. ;-) okay. I make a task for it. [21:36:59] leila: Thanks! [21:38:32] np, kaldari. there is one issue in general with approaching this king of question: suppose I tell you that I know 0.006 of total users who responded to at least one WG question were editors and they all answered the question asked from them right the first time. Then, what's the conclusion? [21:39:57] nuria, thanks for review! [21:40:03] will fix in a jiffy (just hitting up the store :)) [21:40:04] the point of WG is to increase engagement by engaging more non-editors. If its goal is to add quality data to WikiData asap, that's a different goal and it makes sense to look at whether editors do better than non-editors [21:41:33] leila: I guess the ideal results would be… “logged in users answered in agreement with base truth (or hand-coded truth) 99% of time (n=323); anon users answered in agreement with base truth (or hand-coded truth) 95% of time (n=23944)”. Would that work? [21:41:34] Analytics-Cluster, Analytics-Kanban, Epic: {epic} WMF has UC report per project per month & day {bear} - https://phabricator.wikimedia.org/T88647#1133432 (kevinator) [21:42:38] but suppose this ideal scenario doesn't happen. What will the community conclude, kaldari? [21:43:02] leila: What’s an “ideal scenario”? [21:43:06] I'm not part of some discussions that you are, kaldari. I just want to make sure I support you with an analysis that helps. [21:44:36] leila: I’m fine with whatever the results are. We can always explain that they are preliminary results. [21:45:36] the ideal scenario depends on our goal. If our goal is to increase user engagement /and/ as a biproduct collect quality data for WikiGrok, our ideal scenario will be different than if the goal is to add data asap to WikiData with high quality. [21:47:03] do you know which of the two is our goal? I heard Maryana mentioning multiple times recently that the goal is to increase engagement so I'm going with that assumption. [21:47:09] milimetric: ok, done with eventlogging deployment [21:47:39] nuria: ok, running to the cave [21:47:45] milimetric: ok [21:48:09] leila: No matter what the results, I think we can achieve both goals. If data quality from a certain group is low, we can just require higher agreement thresholds for that group. [21:49:10] Analytics-Kanban, Analytics-Wikimetrics: Troubleshoot Wikimetrics RAE reports - https://phabricator.wikimedia.org/T93217#1133496 (mforns) @kevinator I wrote the description of the task. I used RAE in the first place because James' email made reference to it. I think Dan executed RNAE to test, so that's wh... [21:49:15] that's true, and I think we should consider whether the contributor was an editor or not as a feature in our model, kaldari. [21:49:47] leila: We have support for a scoring system in the db schema, but so far we don’t have any compelling reason to use it. Comparing data from different groups would help to inform whether that is a priority for future development. [21:50:18] milimetric: wait, restarting [21:50:42] kaldari, isn't the plan to use it once we have test4 data collected? [21:52:11] liela: Yes, but the wikidata community wants to know how the existing data looks for logged in vs. anon, so if it isn’t too hard to analysze I think it would be a good gesture on our part. [21:52:57] leila: I’m currently discussing with the community about posting some of our existing test data for feedback. [21:53:28] I see kaldari. I'll run the comparison. np. [21:53:39] leila: thanks! much appreciated! [22:03:18] Analytics-Cluster, Analytics-Kanban, Epic: {epic} WMF has UC report per project per month & day {bear} - https://phabricator.wikimedia.org/T88647#1133622 (kevinator) Update: since Nuria's last comment: we found a way to count both monthly and daily uniques by putting year-month-day in the cookie, sendi... [22:04:21] (CR) OliverKeyes: De-static-everything (1 comment) [analytics/refinery/source] - https://gerrit.wikimedia.org/r/197296 (owner: OliverKeyes) [22:07:06] Analytics-Cluster, Analytics-Kanban: WMF has report of monthly UCs by project [13 pts] {bear} - https://phabricator.wikimedia.org/T88814#1133624 (kevinator) Update: scope change since we found a way to count daily uniques that is not too costly. https://wikitech.wikimedia.org/wiki/Analytics/Unique_clients... [22:27:45] (CR) Nuria: De-static-everything (1 comment) [analytics/refinery/source] - https://gerrit.wikimedia.org/r/197296 (owner: OliverKeyes) [22:28:02] Analytics, Analytics-Kanban, Patch-For-Review: Turn off WP Zero's Limn-Dashboards & put up a "moved sign" - https://phabricator.wikimedia.org/T92920#1133677 (QChris) a:QChris [22:30:04] milimetric: I am about to mess with wikipedia-zero on limn1. I see that the instance is still a self-hosted puppet master. [22:30:08] The agent is turned off. [22:30:17] Is that just to avoid unneeded runs, or [22:30:25] is it harmfull to run the agent? [22:30:46] (I see that the instance's puppet checkout is outdated, but meh. That would not get in the way) [22:31:23] qchris: yeah, it's the same deal as wikimetrics, we were just afraid puppet breakages would affect it [22:31:30] k. [22:31:36] do I see a handsome volunteer coming to help us with wikipedia zero stuff? [22:31:40] :) [22:31:47] nuria: :-P [22:31:50] (PS2) Joal: Move UAParser wrapper to refinery-core and update refinery-hive accordingly. [analytics/refinery/source] - https://gerrit.wikimedia.org/r/195952 [22:40:06] (CR) Joal: "Added null handling in core function and changed parameterized test to use junitparams and reuse dataset for TestUAParserUserAgentMostPopu" [analytics/refinery/source] - https://gerrit.wikimedia.org/r/195952 (owner: Joal) [22:50:09] milimetric: Are you sure the puppet is fine to run on limn1? It fails due to issues around the diamond collector (which is not harmful), but it also said to [22:50:12] Notice: /Stage[main]/Apache/File[/etc/apache2/sites-enabled/edit-analysis.conf]/ensure: removed [22:50:24] Is "http://edit-analysis.wmflabs.org/" expected to be up? [22:50:35] :) ha [22:50:39] (The corresponding code in puppet is not clear) [22:50:44] well, complicated answer [22:50:46] no, that's my fault [22:50:51] I manually edited that puppet there [22:51:01] and nuria is now working on making my change permanent [22:51:09] but the dashboards that were there are using bad data [22:51:15] and are misleading, so it's ok that they're down [22:51:34] Mhmm. It would be easy to at least make the Apache config appear again. [22:51:45] It sounds like wmf wants that. right? [22:52:15] if it's trivial, then that might be nice just to have for nuria as a starting point [22:52:21] k. [22:52:28] Cool. Thanks. [22:59:12] oh no, thank _you_ for picking up one of the chainsaws we were juggling. +1 coke [23:01:06] :-P [23:07:03] no one is responding in -operations, so I thought I'd ping here: [23:07:05] 16:04 < icinga-wm> PROBLEM - Check status of defined EventLogging jobs on vanadium is CRITICAL: CRITICAL: Stopped EventLogging jobs: reporter/statsd consumer/server-side-events-log consumer/mysql-m4-master consumer/client-side-events-log consumer/client-side-events-kafka-log consumer/all-events-log multiplexer/all-events processor/server-side-events processor/client-side-events-kafka [23:07:11] proessor/clrient-side-events forwarder/8422 forwarder/8421 [23:07:20] nuria: ^ [23:07:22] (that's 16:04 pacific, ie: 3 minutes ago) [23:07:36] milimetric: ^ [23:07:55] greg-g: yes, sorry [23:07:56] qchris, greg-g: yes, i know, disk is full , i am doing cleanup, will re-start again in a sec [23:08:02] kk [23:08:14] greg-g: sorry but today has been quite teh day with EL [23:08:16] *the [23:08:18] (we were on it, sorry for not responding in -ops, you can ping me or nuria directly) [23:08:19] :( [23:08:20] sorry [23:08:28] sorry it's been a not fun day [23:08:37] :) it's ok, we have fun not having fun [23:08:56] :) [23:09:31] greg-g: i really have to be able to claim alarms, let me see if i have permits now [23:10:23] yeah, if not, file a ticket and cc me, I can help push it :) [23:11:54] greg-g: Ok, onicinga now, looking at critical alarms https://icinga.wikimedia.org/icinga/ [23:12:09] greg-g: how do i go about claiming alarms? [23:13:19] nuria: go https://icinga.wikimedia.org/cgi-bin/icinga/status.cgi?host=all&type=detail&servicestatustypes=16&nostatusheader [23:13:28] (ie: click on the critical word at the top) [23:13:33] check the things you want to ack [23:13:39] dropdown "acknowledge this... whatever they say" [23:14:08] greg-g: k [23:16:36] greg-g: ok, i got two , looks like i am not authorized for the other one. will file ticket [23:16:58] greg-g: rather, will ask otto tomorrow & file ticket if pertains [23:18:50] * greg-g nods :) [23:19:28] greg-g: and now that i fixed disk issues , is there something else i need to do to "close the alarms"? [23:19:57] it should recovery itself? not sure what the error really means :) [23:20:07] as long as those jobs start again I guess/ [23:20:08] ? [23:21:31] greg-g: i restart them so yeah they are recovered [23:22:04] cool, then icinga should catchup soon I presume [23:22:16] greg-g: ok, MANY thanks! [23:22:16] I need to head out, thanks for the quick response all [23:22:23] :) [23:23:52] !log eventlogging re-start due to vanadium disk filling up. Moved logs to "/srv/" [23:25:29] yurik_: On limn1 (the analytics labs instance that hosts the wp-zero dashboards), there is a directory [23:25:31] /var/lib/limn/gp/gp-zero-local-only-data [23:25:43] that is owned by you, and seems to hold one-off data. [23:25:55] Since I am about to tear down the wikipedia-zero setup on that machine ... [23:26:01] are those files still needed? [23:26:03] qchris, wha? [23:26:20] stat1002? [23:26:28] no. [23:26:32] limn1.eqiad.wmflabs [23:26:45] The analytics provided legacy dashboards. [23:26:59] ah, yes, i think its ok to kill it [23:27:10] Ok. Thanks for confirming. [23:27:10] please check with dfoy though [23:27:18] ah. [23:27:24] qchris, double check if dfoy is using any of the limn graphs [23:27:38] We got ok to pull them offline. [23:27:43] (from dfoy) [23:27:44] ok [23:27:56] as long as he's ok with it, so am i ) [23:28:05] i got all the data on stat1002 [23:28:11] ok. [23:28:11] thx for checking [23:47:29] Analytics-Cluster, Analytics-Kanban: WMF has report of monthly UCs by project [13 pts] {bear} - https://phabricator.wikimedia.org/T88814#1134062 (kevinator) [23:47:31] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1134063 (kevinator) [23:48:53] Analytics, Analytics-Kanban, Patch-For-Review: Turn off WP Zero's Limn-Dashboards & put up a "moved sign" - https://phabricator.wikimedia.org/T92920#1134067 (QChris) [23:48:59] Analytics-Cluster, Analytics-Kanban, Performance: Implement Unique Clients report on cluster using x-analytics header & last access date {bear} - https://phabricator.wikimedia.org/T92977#1125610 (kevinator) I merged in T88814 because it's the same work, but that task did not have "daily" in the title a... [23:55:52] qchris: thank you thank you thank you \o/ [23:56:00] kaldari: question about event_taskToken. is this unique on its own or only in combination with event_userToken? [23:56:00] yw :-) [23:56:20] I'm practically dancing [23:56:49] That's what the pages look like after taking the dashboards down: [23:56:50] http://gp.wmflabs.org/graphs/free_mobile_traffic_by_version# [23:57:11] leila: should be unique on its own, although not with 100% certainty due to the bug nuria fixed. [23:57:32] yup, I already checked them [23:57:38] k. Cool. [23:57:45] looks like you found a better solution than a redirect [23:58:16] Well ... a "410 Gone" seems more appropriate than a redirect. [23:58:27] Custom error pages ftw :-) [23:58:42] cool :-)