MetricsDataPing: Difference between revisions

Jump to navigation Jump to search
Line 21: Line 21:
== Data Elements<br>  ==
== Data Elements<br>  ==


A directory of elements collected by the various data collection pings (Metrics Data Collection Ping, Blocklist, AUS Ping, Version Check Ping, Services AMO, Telemetry) can be found here: [https://metrics.etherpad.mozilla.org/8 https://metrics.etherpad.mozilla.org/8]<br>
A directory of elements collected by the various data collection pings (Metrics Data Collection Ping, Blocklist, AUS Ping, Version Check Ping, Services AMO, Telemetry) can be found here: [https://metrics.etherpad.mozilla.org/ep/pad/view/ro.9e6LG/latest Data Collection Paths]<br>
<br>
<br>
The schema and definitions of data elements found in the Metrics Ping can be found here [https://intranet.mozilla.org/Metrics/MetricsDataPingClientDataSchema https://intranet.mozilla.org/Metrics/MetricsDataPingClientDataSchema]
The list and definitions of data elements in the Metrics Ping is here [https://metrics.etherpad.mozilla.org/ep/pad/view/ro.9$yFtH/latest MDP Data Point Descriptions]
<br> <br>
<br> <br>
'''Document Identifier Strategy'''
'''Document Identifier Strategy'''


Each profile will generate a UUID to be used as the document key.  Each day's submission will use that UUID, and this will also be the key for that profile's cumulative data on the server.  As of 2011/12/01, the intention is for the server to merge on the fly as new documents are submitted, not persisting the individual submissions at all.
Each profile will generate a UUID to be used as the document key.  Each day's submission will use that UUID, and this will also be the key for that profile's cumulative data on the server.  When each submission is received, the server merges it on the fly with the cumulative data, not persisting the individual documents.


== Client-side<br>  ==
== Client-side<br>  ==
131

edits

Navigation menu