Confirm
98
edits
Changes
First cut at describing the sync_events_v1 table.
A3: It's up to the engine and to the client. For desktop bookmarks, they're documented [https://dxr.mozilla.org/mozilla-central/source/services/sync/modules/bookmark_validator.js here] (or [https://dxr.mozilla.org/mozilla-central/rev/1d025ac534a6333a8170a59a95a8a3673d4028ee/services/sync/modules/bookmark_validator.js#27-68 here] if that link breaks).
=== Event Telemetry ===
Sync will often write "events" to telemetry. These are made available via the sync_events_v1 table.
==== Table Description ====
{| class="wikitable"
|-
! Field Names!! Data Type !! Description
|-
| document_id || varchar || The document ID of the original ping this event is from.
|-
| app_build_id || varchar || From the original ping
|-
| app_display_version || varchar || From the original ping
|-
| app_name || varchar || From the original ping
|-
| app_version || varchar || From the original ping
|-
| app_channel || varchar || From the original ping
|-
| uid || varchar || From the original ping
|-
| why || varchar || From the original ping
|-
| deviceId || varchar || From the original ping
|-
| event_timestamp || bigint || Number of milliseconds since the process started when the event was created. (??)
|-
| event_category || varchar || Always the string "sync"
|-
| event_method || varchar || The type of action taken on the object
|-
| event_object || varchar || The type of object being acted on
|-
| event_string_value || varchar || Always an empty string?
|-
| event_map_values || map(varchar, varchar) || Additional data specific to this event.
|-
| event_device_id || varchar || If this event is being targeted at a different sync device, this is the ID of the target.
|-
| event_flow_id || varchar || An ID used to identify a pair of commands which span multiple devices (todo: explain this!)
|-
| event_device_version || varchar ||
|-
| event_device_os || varchar ||
|-
| submission_date_s3 || varchar ||
|}
=== Query Examples ===
