Kaldari:Expanding a bit to what Dan said:We took up EL from ori's basically 6 months ago. The operational support analytics provide is documented here: https://www.mediawiki.org/wiki/EventLogging/OperationalSupportEL has several parts and while we have not done much development on the mw extension we have done, together with ori, quite a bit of work on the server side of it as otherwise EL could not have scaled to the level its at right now:By all means poke us about bugs you feel need more attention.Thanks,NuriaOn Wed, Jan 7, 2015 at 12:23 PM, Dan Andreescu <dandreescu@wikimedia.org> wrote:Ryan - I'm sorry I was not aware of this. The Analytics team is responsible for Event Logging, and you can ping any of us if we're not paying attention to an issue.Christian has been largely taking care of EL by himself, and was kept quite busy with Event Logging reliability and the need to backfill lost data. As Christian transitions away from our team, the responsibility falls on the rest of us, and I personally am getting up to speed with it. The bug you mentioned, https://phabricator.wikimedia.org/T78325, sounds like a pain and I'm happy to work on it to learn more about EL. I will bring it up with Kevin and have him respond here if it's *not* a priority.On Wed, Jan 7, 2015 at 3:16 PM, Ryan Kaldari <rkaldari@wikimedia.org> wrote:Who is actually maintaining the EventLogging Extension now? As far as I can tell, none of the members of the Analytics-EventLogging project in Phabricator are developers. This makes it hard to know who to ping when there is a problem. For example, this EL bug that I filed a month ago was never triaged or replied to, and I'm not sure who to poke about it: https://phabricator.wikimedia.org/T78325On Wed, Jan 7, 2015 at 11:32 AM, Dan Andreescu <dandreescu@wikimedia.org> wrote:_______________________________________________Folks -- thanks for owning this. One concern -- this is the second deployment related problem in the last couple of months. I'm concerned that we need to investigate more resources in a testing environment as well as a deployment checklist. I'm also considering having EL added to Greg's deployment calendar (with the accompanying restrictions) since it's approaching being a core service.Thoughts?I think all that's needed here is a deployment checklist. The problem was that a change was not tested in beta labs before being deployed. We could automate that and then take it off the checklist at a later time. But as long as it happens somehow, I think we should be safe enough.
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics