It is a miss match in navtiming2 what is sent from the user (mediaWikiLoadComplete) but the code expect mediaWikiLoadEnd and mediaWikiLoadStart (and then calculate the newly named mediaWikiLoad). Let me fix that so we can soon start use the schema.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
webperf: Add missing mediaWikiLoad to navtiming2 | operations/puppet | production | +35 -2 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T99060 Create a dashboard of key user-centric metrics | |||
Resolved | Peter | T104902 Refactor Navigation Timing gathering to produce reliable stackable measures (aka "frontend.navtiming2") | |||
Resolved | Peter | T180598 NavigationTimingv2 misses mediaWikiLoadComplete |
Event Timeline
Change 392036 had a related patch set uploaded (by Phedenskog; owner: Phedenskog):
[operations/puppet@production] webperf: Add missing mediaWikiLoad to navtiming2
I've changed the name to mediaWikiLoad (the delta, I think we said that when we started) and then just skipped start/end, or do you see a need for them @Krinkle ?
Using mediaWikiLoad looks good, yeah.
As for needing the others, yes and no :) Yes, we do want one of them (mediaWikiLoadEnd), because per T160315 this event would be more useful as an offset instead of a delta. But the current client code only sends mediaWikiLoadComplete (a delta). It does have mediaWikiLoadStart/End, but those are not sent, so.. no we don't need those in webperf.py right now.
Change 392036 merged by Dzahn:
[operations/puppet@production] webperf: Add missing mediaWikiLoad to navtiming2