1415744 - Sync telemetry doesn't report a failureReason for failed sync engines.

Status: RESOLVED WONTFIX

(Firefox for iOS :: Sync, enhancement, P2)

Description

[Thom Chiovoloni [:tcsc] (ex-moco)]

It seems to also omit the engines if a top level failureReason is found [0] (e.g. you have failureReason xor engines, and some of those failure reasons don't seem like they're 'sync completely busted' level). e.g. Does iOS just give up on the rest of the sync if you get an HTTP error?

It seems like status might be where the data is kept, but it's not clear to me. Even if you don't get to this soon, it would be nice to have some clarification on that, since if you are reporting it in the wrong place we can adjust the scala backend code to read it from there so we at least have some insight.

[0]: https://github.com/mozilla-mobile/firefox-ios/blob/master/Sync/SyncTelemetryUtils.swift#L292-L306

Comment 1

[Thom Chiovoloni [:tcsc] (ex-moco)]

Sadly, status isn't useful either. It just reports whether or not the engine is enabled or disabled and why. The vast majority of the time it's "sync.not_started.reason.remotely_not_enabled". For the bookmarks engine it's often "sync.not_started.reason.red_light" also, but that still seems not very useful.

The pings don't appear to contain valuable per-engine error information in them at all, so it doesn't seem like there's a lot we could work around in the scala. Beyond some of the smaller issues in other bugs, at least.

Comment 2

[Justin D'Arcangelo [:justindarc]]

Can you take on the implementation work for this?

Comment 3

[Thom Chiovoloni [:tcsc] (ex-moco)]

I don't think so. I'd be more willing to if the info seemed available. Unfortunately it doesn't, and I'm not terribly familiar with iOS sync's architecture (or swift as a language).