gecko-dev/services/healthreport
2013-09-16 09:51:54 -04:00
..
modules-testing Bug 864993 - Part 2: Properly implement app update collection; r=rnewman 2013-07-18 16:13:43 -07:00
tests Bug 887518 - Move loadAddonManager() to test_provider_addons.js. r=gps 2013-06-26 15:32:27 -07:00
healthreport-prefs.js bug 867737 - update FHR reporting URL, r=gps 2013-05-05 10:04:38 -04:00
HealthReport.jsm Bug 854018 - Record counts for FHR upload actions; r=rnewman 2013-05-01 09:41:55 -07:00
HealthReportComponents.manifest Bug 854018 - Record counts for FHR upload actions; r=rnewman 2013-05-01 09:41:55 -07:00
healthreporter.jsm Bug 887081 - Attach healthreporter to global object. r=gps 2013-09-06 09:08:26 -07:00
Makefile.in Bug 912293 - Remove now redundant boilerplate from Makefile.in. r=gps 2013-09-05 09:01:46 +09:00
moz.build Bug 870370 - Move EXTRA_COMPONENTS to mozbuild (file batch #3); r=mshal 2013-06-11 16:38:22 -04:00
profile.jsm Bug 887580 - Properly export object in profile.jsm and policy.jsm. r=gps 2013-06-26 17:01:45 -07:00
providers.jsm Bug 916186 - Don't record birth time in crashes provider. r=gps 2013-09-16 09:51:54 -04:00
README.rst Bug 842393 - Documentation for Firefox Health Report; r=rnewman 2013-02-18 16:11:50 -08:00

=====================
Firefox Health Report
=====================

This directory contains the implementation of the Firefox Health Report
(FHR).

Firefox Health Report is a background service that collects application
metrics and periodically submits them to a central server.

Implementation Notes
====================

healthreporter.jsm contains the main interface for FHR, the
*HealthReporter* type. An instance of this is created by the data
reporting service. See /services/datareporting/.

providers.jsm contains numerous Metrics.Provider and Metrics.Measurement
used for collecting application metrics. If you are looking for the FHR
probes, this is where they are.

Preferences
===========

Preferences controlling behavior of Firefox Health Report live in the
*datareporting.healthreport.* branch.

Some important preferences are:

* **service.enabled** - Controls whether the entire health report
  service runs. The overall service performs data collection, storing, and
  submission. This is the primary kill switch for Firefox Health Report
  outside of the build system variable. i.e. if you are using an
  official Firefox build and wish to disable FHR, this is what you
  should change.

* **uploadEnabled** - Whether uploading of data is enabled. This
  is the preference the checkbox in the UI reflects. If this is
  disabled, FHR still collects data - it just doesn't upload it.

If the entire service is disabled, you lose data collection. This means that
data analysis won't be available because there is no data to analyze!

Registering Providers
=====================

Firefox Health Report providers are registered via the category manager.
See HealthReportComponents.manifest for providers defined in this
directory.

Essentially, the category manager receives the name of a JS type and the
URI of a JSM to import that exports this symbol. At run-time, the
providers registered in the category manager are instantiated. This
allows for a loose coupling of providers which in turns makes managing
the code behind the providers much simpler.

Other Notes
===========

There are many legal and privacy concerns with this code, especially
around the data that is submitted. Changes to submitted data should be
signed off by responsible parties.