@Catrope's current plan:
- Migrate VE and WikiEditor to the mw.eventLog.Schema class, which was created after the VE instrumentation code was written
- Make the sampling rate configurable (like in this WIP change, but as an actual number rather than a weird hacky hex thing)
- Add oversampling support to mw.eventLog.Schema, which adds isOversampled=true to the event data for oversampled events (i.e. events that bypassed sampling and would not have been logged otherwise)
- Add code to WikimediaEvents that triggers oversampling in the cases where we need it
Sat, Oct 13
These metrics now use the Analytics Query Service—this didn't reduce the delay as we hoped, but we have at least removed our dependency on Wikistats 1.
I've started using a Google spreadsheet to format the metrics properly—that's a big step forward.
Fri, Oct 12
Thu, Oct 11
Tue, Oct 9
Mon, Oct 8
For the record, I actually think this is unblocked now!
Fri, Oct 5
Thu, Oct 4
Tue, Oct 2
I'm now changing the parent tasks back—the lack of this data means we can't produce any metrics about the load performance of mobile editors, which will be crucial for our annual plan goal.
Changing the parent tasks here since this doesn't block our immediate metrics work, since event timestamps are precise enough to calculate overall session duration.
Changing the parent tasks here since this doesn't block our immediate metrics work, since event timestamps are precise enough to calculate overall session timestamps
Mon, Oct 1
Looks good to me!
This data has been accumulating successfully for a month now (for example, see P7612). Thanks, everyone!
Reopening so I don't forget to check the data to verify the fix.