Is this actually a KPI? That is, specifically that we're tracking App stuff? And, Tomasz, can you confirm the urgency and prioritise this with Dan? We've had discussions before about the need to avoid running into a "ah, just one more" situation with adding new dashboard tabs and metrics and I want to make sure everyone is on the same page with the importance of this task, relative to our support of Discovery as a whole.

The app absolutely produces a user agent - it also produces a UUID. This should be fairly simple, in the sense of not requiring us to invent new things, albeit fairly time consuming.

Oliver, the urgency is only with deciding if we need to urgently take an
action or not ) if all traffic is already marked with UA, we should be
good, and plan it without haste

So we have a phabricator task marked "urgent" not because solving it is urgent but because you didn't know if we'd be able to implement it trivially?

In the future emailing me may be easier ;p. I'm going to amend the task to remove urgency requirements.

So my next comment would be; again, why Apps specifically? I.E. why does this need to be called out?

@Ironholds What's your preferred method for identifying traffic from the apps? By user agent, or by putting some data in the X-Analytics header?

@Yurik @Ironholds

• We are able to determine the number of unique users of Nearby, via eventlogging from the app (i.e. when someone taps Nearby from the navigation menu): https://meta.wikimedia.org/wiki/Schema:MobileWikiAppNavMenu
• As for user agent when requesting tiles, the Mapbox SDK (which the app uses to render the map) automatically sets the user agent to something of the form "Mapbox Android SDK/[version]"

Does it still pass through the UUID in the x_analytics field?

Unfortunately I don't believe so. We'd have to see about making that change.

So basically we've got a generic user agent and no UUID? Yeah, that change will be needed. At the moment we won't even be able to robustly identify app traffic full stop, unless nobody else uses Mapbox.

I've opened an issue in the Mapbox SDK to allow setting a custom userAgent.
https://github.com/mapbox/mapbox-gl-native/issues/3149

Any updates on this?

It looks like we still can't set a custom userAgent in Mapbox (the above issue is still open)...

I think this functionality is now merged and will be available in the next Mapbox SDK release:

https://github.com/mapbox/mapbox-gl-native/issues/3149#issuecomment-223598501 -> https://github.com/mapbox/mapbox-gl-native/issues/1993#issuecomment-221167839 -> https://github.com/mapbox/mapbox-gl-native/pull/6441