Event instrumentations and wiring for Wikimedia Foundation sites.
Details
Today
There are a few legacy breakpoints remaining, but not many: Code search.
Yesterday
Other use cases:
Relevant for our proposal: T263049: Avoid extra HTTPS connections for most Event Platform beacons
Thu, Oct 24
@Ottomata asked me to note that for Product Analytics it would be really helpful if the data was available in data lake and could be accessed/reported with Superset (which we know how to use).
ie. is it possible to show the number of "logout" clicks from logged in user that have a username starting with ~20?
No. Not with the existing schema. We do not log username for privacy reasons.
We would need events for:
- Log-in
- Exit session
Local testing:
Wed, Oct 23
The previous MW configuration and JS code for this has been kept and maintained since 2022 and so is already in production:
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1082102 would also have fixed this problem (I +2'd it last night, but it failed to merge due to some unrelated error).
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1082102 would fix this as well
Change #1082471 merged by jenkins-bot:
[mediawiki/extensions/WikimediaEvents@master] Unblock CI
Change #1082471 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[mediawiki/extensions/WikimediaEvents@master] Unblock CI
Mon, Oct 21
Yes, please.
so one more prometheus label domain: ["central"|"local"]?
Fri, Oct 18
@ovasileva this came up in https://phabricator.wikimedia.org/T375712#10240244 - basically @RHo was asking if we could detect clicks to "Exit session" from users. We can but we can't distinguish between a logged in user logging out and a temporary user. Not sure how important this is and whether it should be a considered a blocker for filing a ticket (please also see my concern on T374942#10242904) - we potentially might need tickets for our other schemas if there are other product needs.
Per https://turnilo.wikimedia.org/#webrequest_sampled_live/[...] the peak request rate for the /beacon/statsv path in the last 30 days was ~7,590,400 reqs/da or ~88 reqs/s. I think there's an opportunity to reduce this number by combining updates to counters and guages but I doubt this would have a massive impact.
Thu, Oct 17
Test Result - Prod