Page MenuHomePhabricator

Measure non-compliant browsers with Navigation Timing
Closed, ResolvedPublic

Description

Right now we're rejecting a unknown portion of browsers from the metric gathering based on our isCompliant check. Per comments on T104902, this is potentially a significant cut.

The goal here is to get insight into how big of a chunk we're talking about.

When a page view falls in the Navigation Timing sampling, we should always emit an event. Either with Schema:NavigationTiming if all the data is complete and usable. And otherwise, an error increment of sorts.

There are two parts to this:

  • Track errors from EventLogging itself (such as for url size, T112592).
  • Track rejection from our own code for non-compliant browsers.

The total sum of different error types should be tracked on the dashboard at https://grafana.wikimedia.org/#/dashboard/db/performance-metrics, along side the existing tracking for schema sample rate (which tracks rate of valid/successful events).

Event Timeline

Krinkle raised the priority of this task from Low to Needs Triage.Sep 15 2015, 2:18 AM
Krinkle set Security to None.

Change 238831 had a related patch set uploaded (by Krinkle):
Measure non-compliant Navigation Timing browsers

https://gerrit.wikimedia.org/r/238831

Krinkle triaged this task as Normal priority.Sep 16 2015, 7:26 PM
Krinkle claimed this task.
Krinkle moved this task from Inbox to Doing on the Performance-Team board.

Change 238831 merged by jenkins-bot:
Measure non-compliant Navigation Timing browsers

https://gerrit.wikimedia.org/r/238831

Change 240005 had a related patch set uploaded (by Krinkle):
Measure non-compliant Navigation Timing browsers

https://gerrit.wikimedia.org/r/240005

Change 240005 merged by jenkins-bot:
Measure non-compliant Navigation Timing browsers

https://gerrit.wikimedia.org/r/240005