Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Jon Robson
Ori, thanks for checking and the reassurance and thanks for sorting this out guys! Keep us updated! On Wed, Apr 30, 2014 at 3:27 PM, Ori Livneh wrote: > On Wed, Apr 30, 2014 at 3:05 PM, Jon Robson wrote: >> >> There also do not seem to be any new entries being created in >> MobileWebUploads_820

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Ori Livneh
On Wed, Apr 30, 2014 at 3:05 PM, Jon Robson wrote: > There also do not seem to be any new entries being created in > MobileWebUploads_8209043 which is slightly concerning... > I see entries in db1048. So, again: this is temporary lag in replication due to the setup being new. ___

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Toby Negrin
Let's give the database the time it needs to replicate and perform needed validation before we start troubleshooting other issues. I'm concerned that too many things are going on here. Thanks to everyone who is working on this right now. -Toby On Wed, Apr 30, 2014 at 3:17 PM, Jon Robson wrote:

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Jon Robson
I've not seen any events logged on this table since 26th April. I know for sure there have been some since then as I triggered some on the 27th (I saw them in the network tab)... I'm using stat1003 I just want to rule out schema validation errors. ___ Mo

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Steven Walling
On Wed, Apr 30, 2014 at 3:05 PM, Jon Robson wrote: > There also do not seem to be any new entries being created in > MobileWebUploads_8209043 which is slightly concerning... > Jon if you're looking on the usual log databse this is likely just the ~30 hours of lag. EventLogging was recently switc

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Jon Robson
There also do not seem to be any new entries being created in MobileWebUploads_8209043 which is slightly concerning... On Wed, Apr 30, 2014 at 2:28 PM, Dan Andreescu wrote: >> Is there a bug/ticket tracking this other than the one filed under >> MobileFrontend? If not, perhaps we should reassign

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Dan Andreescu
> > Is there a bug/ticket tracking this other than the one filed under > MobileFrontend? If not, perhaps we should reassign the MobileFrontend bug > to a more appropriate place. > We should report a bug for every separate issue, and I think this one is "Limn Dashboards not working since EventLoggi

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Arthur Richards
Is there a bug/ticket tracking this other than the one filed under MobileFrontend? If not, perhaps we should reassign the MobileFrontend bug to a more appropriate place. On Wed, Apr 30, 2014 at 2:19 PM, Dan Andreescu wrote: > Are there any updates on this from Sean? It's not super critical at th

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Dan Andreescu
> > Are there any updates on this from Sean? It's not super critical at the > moment; I just want to know what's going on and when we might expect the > graphs and data to return to normal :) > The latest I know is that the mobile-reportcard dashboards are updating again. That means db1047/log is

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-30 Thread Maryana Pinchuk
Are there any updates on this from Sean? It's not super critical at the moment; I just want to know what's going on and when we might expect the graphs and data to return to normal :) On Fri, Apr 25, 2014 at 3:57 PM, Ori Livneh wrote: > Sean sent this update earlier (before Jon noticed the issu

Re: [WikimediaMobile] [Analytics] Eventlogging for editing broken

2014-04-25 Thread Ori Livneh
Sean sent this update earlier (before Jon noticed the issue) and agreed to let me forward it here. > db1047 has been upgraded to MariaDB 10, however it is not yet replicating > from m2 because I ran into a replication bug on db1046, the m2 slave I had > intended to make db1047's master for the log