The previous plan for assessing the current state of affairs was via adding request logging capabilities to various parts of the labs infrastructure, but that's a huge dependency that's not up to us to resolve. Therefore, I propose to add EventLogging tracking of the following features:
This should work on top-10 Wikipedias (because these features are user-added, making it consistenly work everywhere is a gigantic task).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krinkle | T110353 Audit use of cookies | |||
| Resolved | MaxSem | T103017 Use EventLogging to track geo feature usage |
We're going to probably need something more specific than "usage":
Change 221012 had a related patch set uploaded (by MaxSem):
WIP: Track geo feature usage
Change 226224 had a related patch set uploaded (by MaxSem):
Enable tracking of geo features on enwiki
Enabled everywhere, data is coming, if there are problems or we need a dashboard, we will create another task.
Does this change trigger T107244: Middle clicking coordinates doesn't open a new tab?
@MaxSem: Does this change trigger T107244: Middle clicking coordinates doesn't open a new tab?
This has been deployed to production for two months. Do you need to collect more data, or can this be turned off for now? Or is this a permanent thing?
This data is being actively dashboarded ( https://searchdata.wmflabs.org/maps/ ) to help Discovery-ARCHIVED decide what resources we want to invest in improving maps. I'd really prefer that this was left on, because otherwise we'll have gaps in our data which will hinder our efforts to be data driven in our resource allocation.
If you want to keep it on, you have to figure out a way to do it without cookie-ing users. The GeoFeaturesUser is currently tantamount to a persistent tracking cookie.
@ori if you're looking to make changes to the EL here I'd suggest open a new task rather than tweak the priority on a resolved one.
(This is not to say I don't think your concerns are good'ns we should work on, mind)