NavigationTiming logs action, page id, namespace id and revision id, but all of those are useless for special pages so it is not very useful for measuring changes for a certain special page. We should probably log the canonical special page name when applicable.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| ext.NavigationTiming: Remove some unnecessary properties | Imarlier | mediawiki/extensions/NavigationTiming | master | +20 -36 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Imarlier | T186253 Log special page name in NavigationTiming | |||
| Resolved | • Imarlier | T186295 Slim down Navigation Timing schema |
Event Timeline
Comment Actions
I'm going to be working on a bunch of other changes related to NavTiming, this should be easy enough to include.
Comment Actions
Do you think this would be possible to do by Monday or Tuesday? It would be nice to be able to use it for T186244.
I can write the patch (as you said it's an easy change), I'm not sure if the dashboards need to be updated after an EL schema change though.
Comment Actions
The sampling is not nearly high enough to include sufficient views of any particular special page to get useful data from real-users for before/after comparison purposes.
I'd recommend using synthetic testing for this purpose instead. Perform a bunch of one-off runs with WebPageTest using different devices, browsers, and connectivity configurations, and again after the deployment. This also has the benefit of including a film strip and timeline. We can help with picking the right configurations, run counts and mediator (e.g. from a test with 10 runs, which to use for comparision: median by loadEventEnd, fastest by TTFB, or.. etc.)
Comment Actions
On a related note, the page/revision/namespace data is not currently used for anything other than as starting point in a deep-dive after detecting a regression, to help narrow down a possible cause.
As part of T181956, this could be automatically triggered in specific scenarios client-side. And in any event, I fully support adding the wgCanonicalSpecialPageName to the event data. Although I do think we we should also consider dropping a few fields first, given it is growing rather large. See T186295.
Comment Actions
Change 410472 had a related patch set uploaded (by Imarlier; owner: Imarlier):
[mediawiki/extensions/NavigationTiming@master] [WIP] ext.NavigationTiming: Remove some unnecessary properties
Comment Actions
@Tgr Sorry about not seeing your question earlier about gettiing this out, sorry we missed your timing!
Comment Actions
Change 410472 merged by jenkins-bot:
[mediawiki/extensions/NavigationTiming@master] ext.NavigationTiming: Remove some unnecessary properties