Mobile/Metrics: Difference between revisions

Mobile/Metrics (view source)

774 bytes added , 6 April 2016

m

canmove, Confirmed users, Bureaucrats and Sysops emeriti

2,798

edits

@@ Line 17: / Line 17: @@
 *[https://gecko.readthedocs.org/en/latest/mobile/android/fennec/uitelemetry.html UI telemetry]: Mobile-specific UI telemetry implementation. You can query this data with re:dash, or look at the [https://people.mozilla.org/~mfinkle/uitelemetry/ UI telemetry dashboard].
 *[https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/core-ping.html Core ping]: New opt-out telemetry ping that we're working on to replace FHR.
+==== Pipeline ====
+Getting data into the system requires multiple steps:
+* Client submits pings.
+** Pings are generated and an attempt to send is made.
+** Due to network connectivity, server issues or any other real-world issue, the ping could fail to be sent.
+** Failed pings are archived locally and resend attempts are made at a later time.
+* Server receives pings and does a small amount of validation and routing.
+* Pings are ready for streaming style analyses. (~1 minute after receiving)
+* Pings are saved in durable storage. (~15 minutes after receiving)
+* Ping data is available to Spark analyses. (~15 minutes after receiving)
+* Ping data is run through ETL scripts and imported into Presto/Re:dash. Ready for snapshot style analyses. (~24 hours after receiving)
 === Exploring Telemetry Data ===