ARCHIVED and superseded by Data-Engineering, see T287531: Create project tag for Data-Engineering.
Main place where the WMF Analytics Engineering team triages incoming work. If you tag something with Analytics it will go to the Incoming column and we will triage it usually within a week. For urgent problems, you can contact the team members on IRC or email.
@dcausse should we resolve this task?
mediawiki/page/restrictions-change/2.0.0 - don't require rev_id, etc.
Change #1190301 merged by jenkins-bot:
[mediawiki/extensions/EventBus@master] EventSerializer - fix logic for setting of meta.dt
Change #1190301 had a related patch set uploaded (by Ottomata; author: Ottomata):
[mediawiki/extensions/EventBus@master] EventSerializer - fix logic for setting of meta.dt
Thanks for the note here, @Milimetric! Please let us know when all of this is finished up and we'll switch out process over to the new metrics.
Hi @AndrewTavis_WMDE, yes I'm supporting Yaron in his work here. He has a proof of concept metric implementation. We just have to get it incorporated and deployed, but that may take some doing.
A related, older task: T121912: Better redirect handling for pageview API
You got me curious, so I spent a little time digging on this -- as far as I can tell not much has changed in the real world since Daniel Stenberg's blog post.
I should have put the comment on this here ticket instead of the old closed ticket, so doing so now (thanks again @Ottomata for heads up) - question for you @Krinkle . Any guidance appreciated if you've happened to be in the browser codebases or happened to be viewing their real world behaviors around this lately.
Okay thanks, we are funding Yaron to help with this work and hopefully make some headway with more video specific metrics.
Hey @Doc_James 👋 Would be nice if we could have these kinds of high level metrics, but that's out of the scope of the current project which is just trying to get as good of metrics as possible within the current scope of the available data. Exact instrumentation of a video play including duration watched would likely require WMF data engineering to get involved. This is a known issue, but as WMDE understood isn't something that can be prioritized right now, so we chose to go with the current approach.
This is something we at VideoWiki would love to see. Accurate metrics for number of plays of videos and duration of video played. Andrew do you plan to look at that second bit?
Change #1171696 merged by jenkins-bot:
[mediawiki/extensions/EventBus@master] EventFactory - allow the intake service to set meta.dt
I'm not totally sure who to notify of this, so @Joe can maybe help?
Change #1171696 had a related patch set uploaded (by Ottomata; author: Ottomata):
[mediawiki/extensions/EventBus@master] createRecentChangeEvent - allow the intake service to set meta.dt
@phuedx @dr0ptp4kt I assume the new beacon endpoint (/beacon/v2/events ?) exists now? If so, I believe this task is do-able by changing wgEventLoggingServiceUri to /beacon/v2/events?hasty=true ?
Thanks for all the information, @TheDJ :) Bringing @Ben.buchenau in as well as we've been discussing this. Does seem like we're reliant on preload=none for this. Is there a way for us to monitor if and when this change is made? I guess we'd see the spike in the data.
Additional note. If you also count the thumbnail poster downloads of videos, then by combining these numbers, You can give a very rough estimate of the click through rate for the impressions (inclusions of videos in pages). In Industry, this is called the "Play rate" metric.
Can you give examples of these requests that we are filtering? If they are directly on the video, are you only checking requests that have either no Range header or a Range header that begins with 0- ? Because videos are often a progressive downloads, and you'd be counting each chunk being downloaded if you don't account for that, whereas Ranges that begin with 0 at least ensure you only count the first chunk of the download.