Connected Devices/Projects/Metrics: Difference between revisions

Jump to navigation Jump to search

Connected Devices/Projects/Metrics (view source)

Revision as of 08:37, 27 May 2016

878 bytes removed ,  27 May 2016
→‎Background: adding "Rationale" chapter
(→‎Project Overview: updating Metrics info due to the new approach followed (using Google Analytics))
(→‎Background: adding "Rationale" chapter)
Line 5: Line 5:
In addition, accessing data from different products should require as low effort as possible for decision makers in Connected Devices (engineers, PMs, senior management…).
In addition, accessing data from different products should require as low effort as possible for decision makers in Connected Devices (engineers, PMs, senior management…).


== Background ==
== Rationale ==
At the beginning of this project our goal was to build a framework that will allow each train to collect the specific data needed, but still use the [http://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/index.html unified Telemetry Pipeline] to send data to the metrics infrastructure. So we will be able to rely on architecture that already exists in Mozilla and which has running processes for validating, sanitizing and even automatically analyzing device data.
Nearly all the Connected Devices train are likely, at some point of time, to require collection of data. Data gathered from the projects is extremely useful to understand how people use our products but also to check how changes implemented in the Products affect how people use them.


After some months working to ensure the information sent was consistent, relying on the [https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/common-ping.html Telemetry "Ping" mechanism] already used in many Mozilla products and defining one common [https://docs.google.com/a/mozilla.com/document/d/1nMdnuYWGSXRzLramzzAWpR78ZRA5645bpWAWKIyTvp0/edit?usp=sharing|Connected Connected Devices Ping Format proposal] that could be implemented by each train, we changed our approach.
In summary The idea of the CD Metrics Framework is providing all the CD trains an easy way to:
* Collect metrics in the products
* Get Access to the metrics information
* Visualize the metrics information


Due to the benefits of using Telemetry are clear for Gecko-based projects, but this might not apply to other our CD trains.
* The CD projects are intended to be initially small projects and Google Analytics and other 3rd party providers offer kind of dashboards really easy to be used.
* Some other projects in Mozilla have already started to use this kind of solutions
 
== Framework Decision ==
== Framework Decision ==
After studying [https://docs.google.com/spreadsheets/d/1zMgrunttlH0qSr-2qpiIAPb6DPo837V68AGYmJYCPME/edit#gid=0 several third party solutions] the team decided to go for Google Analytics.
After studying [https://docs.google.com/spreadsheets/d/1zMgrunttlH0qSr-2qpiIAPb6DPo837V68AGYmJYCPME/edit#gid=0 several third party solutions] the team decided to go for Google Analytics.
Oteo
Confirmed users
1,225

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1134670"

Navigation menu