Page MenuHomePhabricator

Investigate NavigationTiming.nonCompliant error increase
Closed, ResolvedPublic

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:

Event Timeline

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"

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.

Imarlier moved this task from Inbox to Backlog: Maintenance on the Performance-Team board.

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

Imarlier claimed this task.