1227579 - Switch about:healthreport over to Unified Telemetry for Firefox 43+

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P1)

Description

[Georg Fritzsche [:gfritzsche]]

We conservatively only disabled data upload for v2 / old FHR for Firefox 43+, which means that we don't automatically switch over to the v4/Telemetry backed about:healthreport.

We need to switch over to the new version for privacy & other reasons.

Comment 1

[Georg Fritzsche [:gfritzsche]]

[Tracking Requested - why for this release]:
This needs to happen for privacy & user transparency reasons.

Comment 2

[Georg Fritzsche [:gfritzsche]]

The only open dependencies here are bug 1220110 & bug 1220119, but they minor, server-side (part of the remote content) and already submitted for review (https://github.com/mozilla/fhr-jelly/pull/176).

L10n is not blocking landing the client changes here.

Comment 3

[Georg Fritzsche [:gfritzsche]]

Attachment: Flip the main about:healthreport URL to the v4 content

Comment 4

[Pulsebot]

https://hg.mozilla.org/integration/fx-team/rev/9680aa9b2aeb

Comment 5

[Georg Fritzsche [:gfritzsche]]

Comment on attachment 8691460 [details] [diff] [review]
Flip the main about:healthreport URL to the v4 content

Approval Request Comment
[Feature/regressing bug #]: Unified Telemetry & about:healthreport
[User impact if declined]: about:healthreport shows the wrong data on 43+
[Describe test coverage new/current, TreeHerder]: Automated coverage for backing system, repeated manual QA coverage over different scenarios, bug 1217341 was the last extensive verification for the new content.
[Risks and why]: Low-risk, this just points about:healthreport to the updated content for v4 / Unified Telemetry, which was already verified.
[String/UUID change made/needed]: None.

More background:
The current content under the new URL is a (risk-free) copy of the old (v2) content.
Bug 1227619 will bring the new (v4) content to the production server.
After that, the v4 content will be powered by Telemetry - bug 1217341 already verified that this works properly.

Comment 6

[Liz Henry (:lizzard) (relman/hg->git project)]

Tracking for 43+ since we want to aim this feature change at 43 release.

Comment 7

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Georg, I was reviewing the patch and the pref value looks interesting bcuz of locale and v4 in it. Is this a pref that Firefox users can change? or is this a UT server-side pref setting?

Comment 8

[Georg Fritzsche [:gfritzsche]]

(In reply to Ritu Kothari (:ritu) from comment #7)
> Georg, I was reviewing the patch and the pref value looks interesting bcuz
> of locale and v4 in it. Is this a pref that Firefox users can change? or is
> this a UT server-side pref setting?

The %LOCALE% part is substituted with the users locale (e.g. "en-US", "de", ...).
The v4 part is to point it to the new contents - we have to keep the old (v2) contents around to serve existing clients.

Comment 9

[Liz Henry (:lizzard) (relman/hg->git project)]

Comment on attachment 8691460 [details] [diff] [review]
Flip the main about:healthreport URL to the v4 content

Please uplift this pref flip; part of unified telemetry feature.

Comment 10

[Liz Henry (:lizzard) (relman/hg->git project)]

Georg and Adalucinet, please verify this once it lands on beta, sounds like this is pretty crucial to have in place for 43 release. It should be in beta 7 which builds tomorrow and will release on Friday.

Comment 11

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

(In reply to Georg Fritzsche [:gfritzsche] from comment #8)
> (In reply to Ritu Kothari (:ritu) from comment #7)
> > Georg, I was reviewing the patch and the pref value looks interesting bcuz
> > of locale and v4 in it. Is this a pref that Firefox users can change? or is
> > this a UT server-side pref setting?
> 
> The %LOCALE% part is substituted with the users locale (e.g. "en-US", "de",
> ...).
> The v4 part is to point it to the new contents - we have to keep the old
> (v2) contents around to serve existing clients.

Thanks Georg! So:
1. What happens a few releases down the line? Will the pref value not need V#s in it? Will this be sometime when 47 goes live?
2. What if a FF43 user changes v4 to v2?
3. Are all the data quality issues addressed that made us disable this for FF41 and give it on only for 5% users? I am assuming with this patch UT is enabled for all 43 users. Or am I mistaken?

Comment 12

[Benjamin Smedberg]

UT was enabled for all 42 users. The URL is not likely to change in the future (at least any time soon). And it's not exposed to users, so we don't need to worry about them changing it. If they did via about:config, the page would work but not display the data we're actually sending.

Comment 13

[Georg Fritzsche [:gfritzsche]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/1f88b627ee6a
https://hg.mozilla.org/releases/mozilla-beta/rev/57d947eb27f0

Comment 14

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/9680aa9b2aeb

Comment 15

[Ada [:adalucinet]]

Verified with 43.0b8 (Build ID: 20151201152349), across platforms [1], that:
- 'datareporting.healthreport.about.reportUrl' pref has 'https://fhr.cdn.mozilla.net/%LOCALE%/v4/' value and about:healthreport displays the correct content 
- 'datareporting.policy.dataSubmissionEnabled.v2' pref is set to false by default
- all the v4 pings are correctly generated

Let me know if anything else needs to be covered here.

[1] Windows 7 64-bit, Ubuntu 14.04 32-bit and Mac OS X 10.11

Comment 16

[Ada [:adalucinet]]

Verified fixed also with 44.0b2 (Build ID: 20151221151411), across platforms [1]. 

[1] Windows 7 64-bit, Mac OS X 10.11 and Ubuntu 12.04 32-bit