This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 473
Add global "sync ping", add UUID to all sync pings #5371
Comments
grigoryk
added
<telemetry>
<sync>
Component: sync-logins
E3
Estimation points: 3
labels
Dec 19, 2019
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Dec 20, 2019
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Dec 24, 2019
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Apr 1, 2020
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Apr 1, 2020
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Apr 2, 2020
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
6 tasks
grigoryk
pushed a commit
to grigoryk/android-components
that referenced
this issue
Apr 2, 2020
… all sync-related pings This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync".
6 tasks
bors bot
pushed a commit
that referenced
this issue
Apr 13, 2020
5386: Closes #5371 - Introduce 'sync' ping, add 'syncUuid' to all sync-related pings r=csadilek,Dexterp37,boek a=grigoryk This patch introduce an 'overarching' sync ping, which is meant to contain information describing a sync overall, vs individual engine runs. Currently it contains global sync errors. syncUuid was also added to all sync-related pings, allowing us to tie together in an analysis all pings that were emitted as part of a single "sync". Co-authored-by: Grisha Kruglov <gkruglov@mozilla.com>
5 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a concept of a "global sync error", which doesn't map well to per-engine pings. Let's add a "sync" ping to host these global errors.
Additionally, let's expand existing pings to include UUID field, which will be the unique per-sync identifier, allowing us to tie together information emitting by different engines during a sync.
For details and context, see #5294 (comment) and mozilla/application-services#2381
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: