New issue
Advanced search Search tips

Issue 854413 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Previews eligibility UMA is unclear

Project Member Reported by ryansturm@chromium.org, Jun 19 2018

Issue description

Eligibility reason should be recorded such that ECT is the first check. This will help understand how much the blacklist is affecting things rather than ECT. Because ECT checks rule out 90+% of pages and we can't control ECT, it would be nice to get fine tuned information about just blacklist checks.

Additionally, LOFI and lite pages appear to record more UMA than other types, and it is very confusing when reading UMA dashboards.

I propose that we also record Client LoFi and Server LoFi eligibility reasons separately, as they have different triggering conditions.
 
Ben and I ran into some issues when trying to determine if we are being too aggressive with the blacklist. I think the above changes could help us actually use the UMA.
+1 for checking ECT first
Components: Blink>Previews
Labels: -Pri-3 M-69 Pri-2

Comment 4 by bengr@chromium.org, Jun 22 2018

Also, ideally, the buckets in the UMA would add up to the total number of navigations.
Refreshed during triage.
Should this be P2 ?
Labels: -Pri-2 -M-69 M-70 Pri-3

Comment 7 by tbansal@chromium.org, Jan 18 (4 days ago)

Labels: -Pri-3 Pri-2
Owner: robertogden@chromium.org

Sign in to add a comment