New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 598520 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Implement new RAPPOR configurations for low-frequency metrics

Project Member Reported by dominickn@chromium.org, Mar 29 2016

Issue description

Chrome'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.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 30 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/07aeedd625a49a1d7276026f545961f26690629a

commit 07aeedd625a49a1d7276026f545961f26690629a
Author: dominickn <dominickn@chromium.org>
Date: Sat Apr 30 00:32:20 2016

Add a low-frequency RAPPOR configuration, and use it for Safe Browsing and Permissions metrics.

This CL implements a new RAPPOR configuration with the F privacy
parameter set to 0.25 instead of 0.5. This has the effect of introducing
less noise into the permanent random response, and thus preserving some
additional amount of signal. The reduction has been approved by the
Privacy team for low-frequency metrics (<500,000 reports per day) and
does not compromise user's privacy or anonymity.

This CL uses the new configuration for the permissions and Safe Browsing
metrics. The existing metrics for these configurations are retained for
a comparative analysis; they will be removed entirely in a future CL.
The multi-dimensional permissions metrics are removed in this CL as they
cannot be feasibly analysed.

Any other metrics which seek to use the new low-frequency configuration
must seek approval from the Metrics and Privacy teams.

BUG= 598520 , 606645 

Review-Url: https://codereview.chromium.org/1921533004
Cr-Commit-Position: refs/heads/master@{#390819}

[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/chrome/browser/permissions/permission_uma_util.cc
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/chrome/browser/safe_browsing/safe_browsing_blocking_page.cc
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/chrome/browser/safe_browsing/safe_browsing_blocking_page.h
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/chrome/browser/ssl/ssl_blocking_page.cc
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/components/rappor/rappor_parameters.h
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/components/security_interstitials/core/metrics_helper.cc
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/components/security_interstitials/core/metrics_helper.h
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/ios/chrome/browser/ssl/ios_ssl_blocking_page.mm
[modify] https://crrev.com/07aeedd625a49a1d7276026f545961f26690629a/tools/metrics/rappor/rappor.xml

Status: Fixed (was: Started)
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 7 2016

Sign in to add a comment