Firefox Health Report

236 views
Skip to first unread message

Daniel Einspanjer

unread,
Sep 21, 2012, 8:11:01 PM9/21/12
to


As you may know, we've been working for several months on a feature codenamed the Metrics Data Ping (MDP). We made our initial proposal for MDP in February.

We’re retiring the “MDP” codename, and will be calling this feature the Firefox Health Report. We’re moving forward with the implementation of this feature in Firefox (i.e., the team will update patches on bugs, write and review code, do security and privacy reviews, etc.)

You can read more about the feature here in a blog post from Gilbert FitzGerald, Sr. Director of Analytics at Mozilla:
https://blog.mozilla.org/metrics/2012/09/21/firefox-health-report/



This FAQ may help answer any questions you have about FHR, how it works, the proposed data set associated with the feature and how we'll protect and use that data:
https://blog.mozilla.org/metrics/firefox-health-report/fhr-faq/

deins...@gmail.com

unread,
Sep 21, 2012, 8:16:27 PM9/21/12
to
The meta bug for the patches can be found here:
https://bugzilla.mozilla.org/show_bug.cgi?id=718066

There were changes to the mainline code this week that cause the currently posted patches not to apply cleanly at the moment. We have new re-based patches that will be updated by Monday morning.

Omega X

unread,
Sep 21, 2012, 9:14:46 PM9/21/12
to
What's the difference between this and current telemetry already
included? Also, will this data be accessible publicly?
--
==================================
~Omega X
MozillaZine Nightly Tester

deins...@gmail.com

unread,
Sep 22, 2012, 12:10:33 PM9/22/12
to
The data in FHR is oriented around longitudinal metrics about the overall performance and stability of the application whereas Telemetry is designed to analyze very specific and detailed data about the performance of specific portions of Firefox browser code. Telemetry uses measurements that are usually millisecond in precision, and there is no way to connect the performance of an installation from day to day to see how it changes.

All of the data collected by FHR is available on the client itself and aggregate information will be available for comparison to the local client data via the built in health report page.

Omega X

unread,
Sep 23, 2012, 6:43:22 PM9/23/12
to
Ok. But why is this opt-out? Current Firefox performance metrics like
Testpilot and Telemetry ask users to opt-in before it starts collecting
and transmitting data.

Bobby Holley

unread,
Sep 24, 2012, 5:45:07 AM9/24/12
to Omega X, dev-pl...@lists.mozilla.org
On Mon, Sep 24, 2012 at 12:43 AM, Omega X <Ask...@for.it> wrote:

> Ok. But why is this opt-out? Current Firefox performance metrics like
> Testpilot and Telemetry ask users to opt-in before it starts collecting and
> transmitting data.


Presumably because opt-in statistics are significantly less representative
of the general population than opt-out statistics, since the former biases
heavily towards techies and enthusiasts. My impression is that this is the
primary advantage of FHR over telemetry, the primary risk with respect to
privacy, and the reason it's being communicated so deliberately.

I'm not on the Metrics team though, so this is just my observation from the
outside. Daniel can correct me if I'm wrong here.

Cheers,
bholley
Reply all
Reply to author
Forward
0 new messages