Page MenuHomePhabricator
Create Task
Maniphest T190977

Investigate NavigationTiming.nonCompliant error increase
Closed, ResolvedPublic
Actions

Description

See https://grafana.wikimedia.org/dashboard/db/eventlogging-schema?orgId=1&from=1521080974548&to=1522278151882&var-datasource=eqiad%20prometheus%2Fops&var-schema=NavigationTiming

Screen Shot 2018-03-28 at 16.02.46.png (1×2 px, 377 KB)

We should check if these are anything other than the known cases of nonCompliant browsers:

  • Safari and WebView on iOS 8.0 (iOS 8.0 introduced broken navtiming, removed in iOS 8.1)
  • Safari on iOS 9.0 (iOS 9.0 introduced a differently broken navtiming, fixed in iOS 9.1 for Safari)
  • WebView on iOS 9.0 and later (iOS 9.1 did not fix navtiming for WebView, and remains broken)
  • IE 9 and IE 10 (no longer in Grade A; navtiming fixed in IE 11)
  • Chrome 63 and later when the view was redirected. – T187858

And if there are no new cases, we should check if maybe the above nonCompliant browsers are more commonly used in Asia; or whether the errors remains mostly distributed the same as before.

Past issues:

Related Objects

Event Timeline

Krinkle created this task.Mar 28 2018, 11:09 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 28 2018, 11:09 PM
Krinkle updated the task description. (Show Details)Mar 28 2018, 11:10 PM
• Imarlier subscribed.Mar 29 2018, 9:11 PM

Interestingly, checking out records coming in via kafkacat, I'm seeing some that I wouldn't expect to be issues:

"user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36"
"user_agent":"Mozilla/5.0 (X11; CrOS x86_64 10176.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.190 Safari/537.36"
"user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36"
"user_agent":"Mozilla/5.0 (Linux; Android 7.0; HTC_A9u Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.109 Mobile Safari/537.36"
"user_agent":"Mozilla/5.0 (Linux; Android 8.0.0; G2299 Build/OPR1.170623.032) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.109 Mobile Safari/537.36"
Krinkle added a comment.EditedMar 29 2018, 9:22 PM

Ah, I forgot to add to the task description. We've got one more known case of non-compliant Navigation Timing data: Redirected views in Chrome 63+.

Per T187858 / https://bugs.chromium.org/p/chromium/issues/detail?id=813889.

Krinkle updated the task description. (Show Details)Mar 29 2018, 9:22 PM
• Imarlier triaged this task as Low priority.Apr 2 2018, 8:17 PM
• Imarlier moved this task from Inbox, needs triage to Backlog: Maintenance, non-prioritized on the Performance-Team board.
Krinkle mentioned this in T181425: Move most Navigation Timing logic to backend.Apr 2 2018, 8:20 PM
Krinkle mentioned this in T191242: Plot Navigation Timing error rate as ratio to success rate.Apr 2 2018, 8:26 PM

I've added the follow-up bits to T181425, and also created T191242: Plot Navigation Timing error rate as ratio to success rate.

• Gilles subscribed.Apr 13 2018, 8:55 AM

Haven't you guys proven in a different task that this was entirely due to the oversampling? Should this task be closed?

• Imarlier closed this task as Resolved.Apr 13 2018, 11:56 AM
• Imarlier claimed this task.
Krinkle mentioned this in T197954: Mobile Safari (WebView) produces invalid Navigation Timing data.Jun 22 2018, 2:13 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL