1554325 - Validate the Sync engine pings in Fenix

Status: RESOLVED FIXED

(Data Science :: Review, task)

Description

[Lina Butler [:lina]]

https://github.com/mozilla-mobile/android-components/pull/3092 adds two pings to all a-c consumers: one for history syncing, and one for bookmarks syncing, submitted for each sync. In particular, we'd like to keep an eye on sync failure reasons as Fenix rolls out to more users.

Would it be possible to analyze those two pings, once that PR lands (with code and data review)?

Comment 1

[Georg Fritzsche [:gfritzsche]]

This sounds like it's best as a request for data science?
I'll move it to that component for now.

Our team is happy to help answer questions or point to prior art though (see e.g. bug 1525603).

Comment 2

[Lina Butler [:lina]]

Sure! 😊 I filed this in Glean because that’s where bug 1552211 was filed.

Comment 3

[Alessio Placitelli [:Dexter]]

Hey Jess,

I noticed that this bug was closed as fixed. Is there an analysis notebook available somewhere with the results of the validation?

Comment 4

[Jess Mokrzecki [:jmok]]

Hi Leif,

Please see the note from Alessio above. I marked this as resolved because it was marked that way in your weekly update. If that is a mistake please feel free to re-open.

Comment 5

[Leif Oines [:loines]]

Hey Alessio, you can see some results here:
https://docs.google.com/document/d/1EOtcCxSO_1K2FtfDlG1M6krprkqJWVkZhilHC4UFTrc/edit#heading=h.m0yhodjvifod

I think there is more that could be done here, but I closed the bug because I think the sync engineers have what they need for now. If there is something you would like looked at, lmk.

Comment 6

[Alessio Placitelli [:Dexter]]

(In reply to Leif Oines [:loines] from comment #5)

I think there is more that could be done here, but I closed the bug because I think the sync engineers have what they need for now. If there is something you would like looked at, lmk.

No no, that's perfect, thanks for providing this link! It's a good reference for us too :)