[00:44:19] 10Quarry: "Running" query being displayed as unsubmitted - https://phabricator.wikimedia.org/T71176#2910203 (10Liuxinyu970226) [00:44:23] 10Quarry: Time limit on quarry queries - https://phabricator.wikimedia.org/T111779#2910204 (10Liuxinyu970226) [00:44:54] 10Quarry: Wrong status of queries in Recent Queries list - https://phabricator.wikimedia.org/T137517#2910210 (10Liuxinyu970226) [00:47:37] 10Quarry: Query runs over 5 hours without being killed - https://phabricator.wikimedia.org/T139162#2910226 (10Liuxinyu970226) [08:02:11] o/ [11:52:12] * elukey lunch! [13:20:15] hello team, happy new year :] [13:27:32] o/ [14:08:04] mforns: did you see my email about EL? [14:08:10] elukey, yes [14:08:22] any thoughts about how to debug these things? [14:08:29] I looked for processing errors in those schemas [14:08:37] but there are no more... [14:09:02] yes it last only one hour, I think it was some specific client having a weird parameter [14:09:07] curiously the logstash eventlogging dashboard, is not working... [14:10:06] elukey, sure, this happens a lot, someone must have deployed a change to their client-side and the events were incorrect during one hour [14:10:30] maybe it was a test environment pointing to production (without deploy) [14:10:30] :( [14:11:17] the logstash dashboard helps a lot in these cases, but it looks like it's broken [14:11:31] https://logstash.wikimedia.org/app/kibana#/dashboard/eventlogging?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-1h,mode:quick,to:now))&_a=(filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'logstash-*',key:_type,negate:!f,value:eventlogging),query:(match:(_type:(query:eventlogging,type:phrase))))),options:(darkTheme:!f),panels:!((col:1,columns:!(event.schema,level,message),id:eventlogging-search,panelIndex: [14:11:31] 2,row:7,size_x:12,size_y:4,sort:!('@timestamp',desc),type:search),(col:1,id:Events-over-time,panelIndex:4,row:1,size_x:12,size_y:2,type:visualization),(col:1,id:Trending-Messages,panelIndex:5,row:3,size_x:12,size_y:4,type:visualization)),query:(query_string:(analyze_wildcard:!t,query:'*')),title:eventlogging,uiState:()) [14:11:35] sorry [14:11:41] https://logstash.wikimedia.org/app/kibana#/dashboard/eventlogging [14:12:14] mmmmm [14:12:28] have we checked it after the kibana 4 migration? [14:12:39] yes, it's empty since 2016-12-30T21:00:00 [14:12:58] don't know when the migration happened [14:13:57] I can see https://logstash.wikimedia.org/app/kibana#/discover/eventlogging-search [14:14:15] elukey, http://tinyurl.com/htoeezj [14:16:34] mforns: try now! [14:16:57] elukey, vvorks!!! [14:17:04] magic? [14:17:26] nono I changed the filter [14:17:30] not sure if it is the right one [14:17:43] but I can see in the trending messages u'0' is not of type 'integer' [14:19:03] sure, this means some client was sending events for the changeslistfilter schema that were not following the schema [14:19:14] ah okok [14:19:17] as simple as that [14:19:52] yes, they sent the string '0' instead of 0 in the namespace field [14:20:08] https://meta.wikimedia.org/wiki/Schema:ChangesListFilters [14:20:29] but it looks like they corrected it, or if it was a test, they noticed that [14:26:59] ahhh now I got the procedure [14:27:00] thanks :) [14:27:17] is there an easy way to determine who is "they" ? [14:27:54] * elukey brb [14:46:56] elukey, I'd assume it's the schema owner, you can get it in the talk page of the schema, in this case: https://meta.wikimedia.org/wiki/Schema_talk:ChangesListFilters [14:47:07] under the field "maintainer" [14:52:16] super thanks :) [14:53:34] ah now I can see https://wikitech.wikimedia.org/wiki/Analytics/EventLogging#Verify_received_events [14:53:41] I went straight to the Administration page [14:53:43] :( [16:05:08] nuria, standuppp? [16:05:08] nuria: standuppppp [16:05:23] nuria: stanfduupp? [16:05:36] * elukey sings standup standup, standup for your rights [16:05:55] that was get up, standup sorry [16:15:32] elukey, fdans, I think today US folks are not working because it's "new year's day observed" [16:16:04] cause yesterday was holiday, but sunday, so it is shifted to today no? [16:16:14] (╯°□°)╯︵ ┻━┻ [16:16:34] yea that makes sense [16:16:35] in spain today is working day... [16:16:41] xD [16:18:26] yeah we have this arbitrary system of "whatever bank holidays that aren't weekends" [17:52:36] 10Analytics-Tech-community-metrics, 10Phabricator: Decide on wanted metrics for Maniphest in kibana - https://phabricator.wikimedia.org/T28#2911376 (10Aklapper) Again that painful realization that we have no stats on Phab or Bitergia (yet) which people filed the most Phab tasks in entire 2016 (we have [[ http:... [17:57:37] Heya a-team, just here for a minute :) [17:57:49] *HAPPY NEW YEAR !!!* [17:57:52] you too! :) [17:58:31] Thanks elukey :) [17:58:46] * elukey goes afk :) [17:58:48] o/ [17:59:43] quick info for mforns and milimetric: I have started sqooping yesterday, it's still ongoing - There was issue running the thing with hdfs user, we'll discuss that point later [18:00:31] I'll start the reconstruction process once sqooping is done :) [18:00:37] Bye elukey ! [18:07:17] hey joal ! [18:07:24] Hi mforns :) [18:07:39] happy new year too!! [18:08:47] Thanks mforns :) [18:09:05] It started at high speed for us with Lino ;) [18:09:33] joal, I read it [18:10:00] sorry for that [18:10:33] joal, today I think US folks are not working, new year's observed day [18:10:47] mforns: don't be, that's life, and it's actually better to have it early in my opinion :) [18:11:19] Ah, ok mforns :) [18:11:27] mforns: I didn't work much either [18:12:01] joal, yes, they say it's better as a child [18:26:58] hmm, does anyone know where I can find the echo_event etc tables for ruwiki on the analytics cluster from stat1002? [18:29:43] addshore: Hi, you're asking for eventlogging tables? [18:31:26] joal, I think he's asking for the echo extension's event table [18:31:31] https://www.mediawiki.org/wiki/Extension:Echo/echo_event_table/en [18:32:05] Ah mforns! We probably don't have them, right ? [18:32:09] AFAICS it doesn't seem to be replicated to analytics-store [18:32:20] mforns, addshore: In the cluster I mean [18:32:24] oh [18:32:46] never heard of that in the cluster, looking... [18:33:40] no... [18:34:47] not in hive [18:36:47] mforns, addshore: We probably can add those to sqoop jobs if they are usefull [18:37:02] joal, yes [18:37:27] in a weekly job though [18:38:05] mforns: maybe not even that frequent [18:38:12] aha [18:39:57] Arf, gone again a-team later [18:41:08] sorry, I dashed out [18:41:13] I was looking for them in analytics-store [18:41:30] I can go and grab them from a different place though, just need a one off look! [18:55:36] off to pick up my parents at the airport, back in ~1h [18:55:44] (happy new year joal!) [21:42:59] bye team! see you tomorrow [23:30:36] 10Analytics, 10Pageviews-API: Most viewed pages of 2016 - https://phabricator.wikimedia.org/T154381#2909045 (10MusikAnimal) [23:31:03] 10Analytics, 10Pageviews-API: Yearly endpoint for the /pageviews/top API - https://phabricator.wikimedia.org/T154381#2909045 (10MusikAnimal) [23:31:25] hello awesome Analytics team! How likely is this to happen? ^ [23:31:26] https://phabricator.wikimedia.org/T154381 [23:34:26] going off of https://phabricator.wikimedia.org/T139934 I might even be able to write a patch for it myself, if we think it's a good idea