Connected Devices/Projects/Metrics: Difference between revisions

Connected Devices/Projects/Metrics (view source)

54 bytes added , 14 April 2016

m

Confirmed users

1,225

edits

@@ Line 20: / Line 20: @@
 === Next Steps ===
-* Share the basic ping format with all the different CD trains and get their feedback so we can iterate over it and adapt to the potential needs of any train.
+Team Objectives for Q2:
-* Build the common CD framework (Controller and Histograms libraries) that can be used by any of the trains independently of the technology chosen for each of them
+* Create a Rust-based Metrics library ready for integration with Connected Devices trains. API will be documented and tested and will enable capture of three types of app metrics: (1) Crashes, (2) FTU, (3) Core usage/histogram data.
-* Understand where are the trains in terms of measurement and which kind of metrics they consider important.
+* Evangelize the Metrics project with CD trains and solicit technical feedback.
-* Test the proposal with one train to be used as benchmark
+* Have a clear plan on how to query/dashboard CD metrics data through the central Mozilla telemetry pipeline, for implementation & delivery in Q3.
-* Help all the teams with Telemetry API adoption, Data Analysis and Reporting.
+* Assist with integration of the library into one of the existing CD trains or publish a sample project to illustrate usage of the library
 == Program Status ==