Confirmed users
1,225
edits
Connected Devices/Projects/Metrics: Difference between revisions
Jump to navigation
Jump to search
m
→Project Overview: some updates in the project overview
m (→Next Steps) |
m (→Project Overview: some updates in the project overview) |
||
| Line 10: | Line 10: | ||
Having the Telemetry API as a common bearer is not enough as we need to ensure the information sent is consistent. For doing so, we will rely on the [https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/common-ping.html Telemetry "Ping" mechanism] that is already used in many Mozilla products. | Having the Telemetry API as a common bearer is not enough as we need to ensure the information sent is consistent. For doing so, we will rely on the [https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/common-ping.html Telemetry "Ping" mechanism] that is already used in many Mozilla products. | ||
In order to ensure information is consistent, can be easily processed and aggregated, we have defined 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 at the gate 1+ phase. Having a common ping format still leaves freedom to CD trains to send specific payloads within the pings as every product will have different aspects to be measured. | In order to ensure information is consistent, can be easily processed and aggregated, we have defined 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 at the gate 1+ phase. | ||
Connected Devices will be aiming to use a common ping format across all of Connected Devices. In summary, this currently consists of three ping formats: | |||
* FTU Ping - Typically sent after the device is started for the first time. This helps to determine how many Active devices there are. | |||
* Core Ping - Contains histograms that developers have instrumented in their code using the Metrics Library. Sent in a recurring interval such as once per day or once every two weeks depending on requirements. Whether or not this is sent is dependent on privacy choice of the user. | |||
* Crash Ping - Sent when there is a crash. Also dependent on privacy choice of user. | |||
These pings will all be submitted to the Telemetry data pipeline at incoming.telemetry.mozilla.org.Having a common ping format still leaves freedom to CD trains to send specific payloads within the pings as every product will have different aspects to be measured. | |||
=== Next Steps === | === Next Steps === | ||