54
edits
Telemetry/Custom dashboards with re:dash: Difference between revisions
Telemetry/Custom dashboards with re:dash (view source)
Revision as of 16:04, 11 January 2017
, 11 January 2017Add docs on the stub installer
(added accessing data externally) |
(Add docs on the stub installer) |
||
| Line 28: | Line 28: | ||
===Presto=== | ===Presto=== | ||
We have a variety of datasets available | We have a variety of datasets available in a Presto instance. Most notably, the derived datasets generated by [https://github.com/mozilla/telemetry-batch-view telemetry-batch-view] (longitudinal, cross-sectional, main-summary, etc). See the [https://wiki.mozilla.org/Telemetry/Available_Telemetry_Datasets_and_their_Applications Full Documentation] for more information. | ||
===Stub Installer Ping Dataset=== | |||
This set includes data describing install success rates for Windows users. This dataset is documented [https://docs.google.com/document/d/1zsiuP66n9Aw1klBrm83x9eaFprc7QfjwpjPFWkb1Fxw/preview here]. | |||
Mat Howell provides a description of the stub installer [https://docs.google.com/document/d/1HKFETH8sJEaTs7vUj6RX96gO5heLw6eDncRhgQbNSuI/preview here]. From that description: | |||
The stub installer works by presenting some options to the user, then | |||
downloading the appropriate full installer and using those options to run it | |||
silently. The full installer is what actually installs the application; the | |||
stub installer only serves as a launcher for the full installer. | |||
... | |||
The stub installer sends one “ping” request right before it exits, whether | |||
the installation succeeded or failed. A checkbox is present in the options | |||
screen that allows the user to disable the ping. | |||
===Google Sheets=== | ===Google Sheets=== | ||