Currently the webrequest access_method field is using the URL .m subdomain to flag traffic from mobile web.
We need to change this to use the new x_analytics subfield: ismobile.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Update webrequest access_method computation | Joal | analytics/refinery | master | +5 -2 | |
| Remove webrequest access_method UDF and core code | Joal | analytics/refinery/source | master | +0 -150 |
Related Changes in GitLab:
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Update webrequest jar | repos/data-engineering/airflow-dags!1621 | joal | update_webrequest_jar | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krinkle | T214998 RFC: Serve mobile and desktop variants through the same URL (unified mobile routing) | |||
| Resolved | JAllemandou | T401665 Use `x_analytics` `ismobile` instead of url `.m` subdomain for webrequest mobile-web `access_method` |
Event Timeline
Comment Actions
Change #1178532 had a related patch set uploaded (by Joal; author: Joal):
[analytics/refinery@master] Update webrequest access_method computation
Comment Actions
Change #1178595 had a related patch set uploaded (by Joal; author: Joal):
[analytics/refinery/source@master] Remove webrequest access_method UDF and core code
Comment Actions
Change #1178595 merged by jenkins-bot:
[analytics/refinery/source@master] Remove webrequest access_method UDF and core code
Comment Actions
Change #1178532 merged by Joal:
[analytics/refinery@master] Update webrequest access_method computation
Comment Actions
joal opened https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/1621
Update webrequest jar
Comment Actions
joal merged https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/1621
Update webrequest jar
Comment Actions
@JAllemandou It looks like the new logic is live for webrequest and pageview datasets, is that right?
In the coming week, we'll rollout to test.wikipedia.org (T401595).
It is fine for testwiki if it isn't live yet, and we will of course wait for this and T401666 to resolve before the next phase of rollouts. I am asking so that, if it happens to be live already, I can do some testing in the hour after the switch on pageview stats. Otherwise I will do that at another time.
Comment Actions
Absolutely!
In the coming week, we'll rollout to test.wikipedia.org (T401595).
It is fine for testwiki if it isn't live yet, and we will of course wait for this and T401666 to resolve before the next phase of rollouts. I am asking so that, if it happens to be live already, I can do some testing in the hour after the switch on pageview stats. Otherwise I will do that at another time.
This should ne problem for webrequest/pageview, but will impact unique-devices. As long as @maya, @nshahquinn-wmf and @Hghani are ok, I'm ok :)
Comment Actions
Thanks @JAllemandou. I checked pageviews for wikitech.wikimedia.org. This makes for a great test case, because it has no mobile subdomain and thus has no existing "mobile web" pageviews (details about why, at T190384#11153446). Any such pageviews counted now, must be from the unified mobile routing:
Following the 5 Sep rollout, it now has mobile pageviews! https://w.wiki/FH7E
I also checked test.wikipedia.org and mediawiki.org, but those are harder to get a strong signal from, because we're expecting "no change" and they're fairly small wikis with a lot of fluctuation.Plus, they still receive explicit traffic to m-dot URL as well, so we can't attribute it fully to unified mobile routing.
Comment Actions
In the coming week, we'll rollout to test.wikipedia.org (T401595).
It is fine for testwiki if it isn't live yet, and we will of course wait for this and T401666 to resolve before the next phase of rollouts. I am asking so that, if it happens to be live already, I can do some testing in the hour after the switch on pageview stats. Otherwise I will do that at another time.This should ne problem for webrequest/pageview, but will impact unique-devices. As long as @maya, @nshahquinn-wmf and @Hghani are ok, I'm ok :)
Hey @JAllemandou I believe the impact of this is to unique devices domain table and we are discussing in T401666. im not sure if you needed something specific from us in this task.
Comment Actions
Hey @JAllemandou I believe the impact of this is to unique devices domain table and we are discussing in T401666. im not sure if you needed something specific from us in this task.
My question was about starting the rollout for testwiki, for which we will see an impact on unique-devices.
The change have been rooled out, nothing more needed :) Thanks @Mayakp.wiki