CloudServices/Sync/ReDash: Difference between revisions
< CloudServices | Sync
Jump to navigation
Jump to search
(fixed formatting) |
(update) |
||
| Line 1: | Line 1: | ||
=== Table Described === | |||
The Sync team's telemetry goes through our data pipeline and lands in Presto to be explored in [https://sql.telemetry.mozilla.org/ Re:Dash]. Below is a description of the data available in the '''sync_summary''' table. | The Sync team's telemetry goes through our data pipeline and lands in Presto to be explored in [https://sql.telemetry.mozilla.org/ Re:Dash]. Below is a description of the data available in the '''sync_summary''' table. | ||
| Line 17: | Line 19: | ||
| deviceid || varchar || Browser profile id? Not currently captured. | | deviceid || varchar || Browser profile id? Not currently captured. | ||
|- | |- | ||
| when || bigint || Linux time stamp of when error occurred. | | when || bigint || Linux time stamp of when error occurred. Make sure to put in "quotes" since when is a reserved SQL word. | ||
|- | |- | ||
| took || bigint || ??? | | took || bigint || ??? | ||
| Line 25: | Line 27: | ||
| status || row(sync varchar, service varchar) || ?? | | status || row(sync varchar, service varchar) || ?? | ||
|- | |- | ||
| why || varchar || | | why || varchar || Always null because XYZ and is meant for ABC | ||
|- | |- | ||
| engines || array(row(name varchar, took bigint, status varchar, failureReason row(name varchar, value varchar), incoming row(applied bigint, failed bigint, newFailed bigint, reconciled bigint), outgoing array(row(sent bigint, failed bigint)))) || ?? | | engines || array(row(name varchar, took bigint, status varchar, failureReason row(name varchar, value varchar), incoming row(applied bigint, failed bigint, newFailed bigint, reconciled bigint), outgoing array(row(sent bigint, failed bigint)))) || ?? | ||
Revision as of 00:03, 14 October 2016
Table Described
The Sync team's telemetry goes through our data pipeline and lands in Presto to be explored in Re:Dash. Below is a description of the data available in the sync_summary table.
| Field Names | Data Type | Description |
|---|---|---|
| app_build_id | varchar | Firefox build ID (e.g. 20160801085519) |
| app_display_version | varchar | Firefox version (e.g. 50.0a2) |
| app_name | varchar | Platform? |
| app_version | varchar | What's the difference with app_display_version? |
| uid | varchar | Hashed Sync/FxA ID |
| deviceid | varchar | Browser profile id? Not currently captured. |
| when | bigint | Linux time stamp of when error occurred. Make sure to put in "quotes" since when is a reserved SQL word. |
| took | bigint | ??? |
| failurereason | row(name varchar, value varchar) | Sync failure reason |
| status | row(sync varchar, service varchar) | ?? |
| why | varchar | Always null because XYZ and is meant for ABC |
| engines | array(row(name varchar, took bigint, status varchar, failureReason row(name varchar, value varchar), incoming row(applied bigint, failed bigint, newFailed bigint, reconciled bigint), outgoing array(row(sent bigint, failed bigint)))) | ?? |
| submission_date_s3 | varchar | ?? |
Query Examples
The example below demonstrate how to select data in JSON object.
WITH errors AS ( SELECT failurereason.name AS name, failurereason.value AS value FROM sync_summary WHERE failurereason IS NOT NULL ) SELECT name, COUNT(value) FROM errors GROUP BY name