Implement new RAPPOR configurations for low-frequency metrics |
||
Issue descriptionChrome's RAPPOR implementation produces inconsistent or unusable results on lower-frequency metrics. Three new configurations (mirroring the existing UMA, ETLD+1, and SafeBrowsing configurations) will be added, with the F parameter lowered from 0.5 to 0.25. These configurations will be intended for metrics which receive <500,000 reports per day, or operate over a sparse URL distribution.
,
May 3 2016
,
Oct 7 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1f7fce2d505249d6ca65f07eb22f2b28f83339e5 commit 1f7fce2d505249d6ca65f07eb22f2b28f83339e5 Author: xhwang <xhwang@chromium.org> Date: Fri Oct 07 09:55:49 2016 media: Add RAPPOR for ProtectedMediaIdentifier permission BUG= 598520 Review-Url: https://codereview.chromium.org/2394063004 Cr-Commit-Position: refs/heads/master@{#423828} [modify] https://crrev.com/1f7fce2d505249d6ca65f07eb22f2b28f83339e5/chrome/browser/permissions/permission_uma_util.cc [modify] https://crrev.com/1f7fce2d505249d6ca65f07eb22f2b28f83339e5/tools/metrics/rappor/rappor.xml |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Apr 30 2016