Page MenuHomePhabricator

EventLogging on the beta cluster should work well and match production (tracking)
Closed, ResolvedPublic

Description

Quick TODOs:

  • Make sure back-end works well on labs
  • Fix issue with NavigationTiming (awjr reported breakage on test2wiki)
  • Sort out test2wiki (it's its own schema wiki, and I don't know if that makes sense.)

Version: unspecified
Severity: normal

Details

Reference
bz49723

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:00 AM
bzimport set Reference to bz49723.

I'd really like to see EL on beta labs, but test2 is a peer node to production wikis and beta labs is entirely separate from production, so this seems confusing.

(In reply to comment #1)

I'd really like to see EL on beta labs, but test2 is a peer node to
production wikis and beta labs is entirely separate from production,
so this seems confusing.

Yes, you're right -- I'm conflating things. I'll file a separate bug for test2 later. This bug is (or ought to be) about the beta cluster.

This is mostly done now. The beta cluster will now log client-side events to http://bits.beta.wmflabs.org/event.gif. A varnishncsa instance on that host forwards events to deployment-eventlogging.pmtpa.wmflabs:8422. Server-side events are sent via UDP directly to deployment-eventlogging.pmtpa.wmflabs:8421. You can run 'zsub localhost:8600' on deployment-eventlogging to watch incoming events. (Be mindful of the fact that varnishncsa buffers and delivers events in batches; you may need to generate several events before yours appears.)

Still outstanding: writing event data to MongoDB & MySQL.

For some reason, we're still getting a JS error on mobile pages (from http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page?debug=true):
Uncaught Error: Unknown dependency: ext.eventLogging load.php:10078
sortDependencies load.php:10078
sortDependencies load.php:10110
resolve load.php:10133
mw.loader.load load.php:11023
(anonymous function) Main_Page:225

What could be causing this? This is blocking mobile web from testing on betalabs.

$wgMFLogEvents was set to false on betalabs which sets the ext.EventLogging target to desktop. However, NavigationTiming was still calling ext.EventLogging as a dependency. Ori set $wgMFLogEvents = true on betalabs, problem solved. I'll be filing a separate bug for bad behavior in MobileFrontend when $wgMFLogEvents === false.

(In reply to comment #7)

Is this done now?

Jon, Ori's last comment suggests that there is still a bit more to do.

Ori what is the status of "event data to MongoDB & MySQL." ?
I've posted a fix for bug 50145

(In reply to comment #9)

Ori what is the status of "event data to MongoDB & MySQL." ?
I've posted a fix for bug 50145

https://gerrit.wikimedia.org/r/#/c/71927/ brings us 90% there. It's scheduled to go out Monday at 20:00 UTC. If it goes smoothly I may try to squeeze MongoDB / MySQL configs for labs into the same window.

Change 74085 had a related patch set uploaded by Ori.livneh:
Make role::eventlogging realm-aware

https://gerrit.wikimedia.org/r/74085

Change 74085 merged by Ryan Lane:
Make role::eventlogging realm-aware

https://gerrit.wikimedia.org/r/74085

This is now complete; applying 'role::eventlogging' correctly provisions EventLogging. deployment-eventlogging.pmtpa.wmflabs is running the full setup: events logged via //bits.beta.wmflabs.org/event.gif are written to log files in /var/log/eventlogging and to local MySQL and MongoDB instances. Many thanks to MaxSem for getting the ball rolling and doing much of the initial work.

[moving from MediaWiki extensions to Analytics product - see bug 61946]