Page MenuHomePhabricator

Investigate mobile map gadget for eventlogging
Closed, DeclinedPublic


We should look at what has been done in this code and see what we'd want to capture, via event logging, for this feature if it would go live:

Add gadget to your enwiki account:

and then go to and see this (when searching on articles that have coordinates, ie:

Event Timeline

debt created this task.Aug 10 2017, 8:06 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 10 2017, 8:06 PM

I'm looking at various maps grafana dashboards, amongst others:

And I notice that collection of event logging seems to have broken down in late july ??

debt added a comment.Aug 23 2017, 5:54 PM

@TheDJ - unfortunately, we have a bug that we're trying to get fixed so that new data is shown on all the dashboards: T173333.

I'm looking at various maps grafana dashboards, amongst others:

And I notice that collection of event logging seems to have broken down in late july ??

We deprecated/discontinued the scripts that calculated metrics for Grafana. For Maps metrics, please refer to, which we're currently having issues with but hope to fix very soon (as Deb mentioned).

We're also working on adding interaction/usage metrics (like the ones seen in & to that dashboard.

mpopov added a comment.EditedAug 29 2017, 8:34 PM

@TheDJ Event logging would be quite an undertaking, but we can start with tracking tiles requested specifically by the gadget (as opposed to mobile web in general). When the gadget (or leaflet, maybe?) makes the API calls to Kartotherian for the tiles, do you use a custom user agent or are you able to specify one? Because if you can specify a custom user agent, on our side we can then look for that UA specifically when we count tiles served. A good UA would include name of gadget & URL or your name & contact info, for example.

This wouldn't be tracking interactions, but if we can start counting tiles served to instances of the gadget specifically, it would be a proxy for usage and would be a good first step.

TheDJ added a comment.EditedAug 29 2017, 9:07 PM

It's already partially logged, since it's just calling out to existing kartographer code. I just disabled the mw.track's when i copied the code from the maplink modules, because I didn't want it to pollute those events. We could of course adapt Schema:Kartographer, but I was considering using that "extra" field that the schema has and use that to differentiate between maplinks from the default module, and maplinks triggered by this gadget..

This is also why i can't add user agents strings etc, the Kartographer code doesn't give me access to that level of interaction.

Ah, got it. Cool, that makes things easier! Yeah, adding some kind of a marker to the extra field somewhere in would be the way to go.

TheDJ added a comment.Aug 30 2017, 9:36 AM

This was my idea:

This is similar to how the layer information is being passed for the wikivoyage tracking events. Note that this is just my sandbox version of the gadget, not live yet.

Seems there is a bug in the existing event logging that we should probably also fix in that case...

Change 378522 had a related patch set uploaded (by TheDJ; owner: TheDJ):
[mediawiki/extensions/WikimediaEvents@master] Kartographer: Capture geohack variant

debt moved this task from Backlog to Needs review on the Maps-Sprint board.Sep 18 2017, 5:48 PM
debt moved this task from Up Next to Tracking on the Discovery-Analysis board.Sep 21 2017, 8:42 PM

Change 378522 abandoned by TheDJ:
Kartographer: Capture geohack variant

Restricted Application added a project: Product-Analytics. · View Herald TranscriptApr 19 2018, 12:20 AM
mpopov closed this task as Declined.May 10 2018, 8:22 PM

Declining for now but open to re-opening in the future if the parent task is re-opened and this work is needed.