Closed
Bug 1405205
Opened 8 years ago
Closed 8 years ago
Ensure telemetry for syncs and for validation reports what bookmark engine is in use.
Categories
(Firefox :: Sync, defect, P2)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
Firefox 60
People
(Reporter: markh, Assigned: tcsc)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
I'm actually not 100% sure the patch in bug 1305563 doesn't already do this, but it seems likely that a no-op sync doesn't.
Knowing which engine is involved in the sync will help us accurately determine what problems are unique to either engine, and the reporting it for validation will help us track introduction rates between the engines.
I think this change is fine as a followup, so I'm opening this bug rather than commenting in bug 1305563.
Updated•8 years ago
|
Priority: -- → P2
Updated•8 years ago
|
Assignee: nobody → tchiovoloni
| Comment hidden (mozreview-request) |
| Assignee | ||
Comment 2•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8917572 [details]
Bug 1405205 - Report bookmark engine as bookmarks-buffered in the sync ping
https://reviewboard.mozilla.org/r/188534/#review193778
::: services/sync/modules/telemetry.js:153
(Diff revision 1)
> if (error) {
> this.failureReason = SyncTelemetry.transformError(error);
> }
> + // We want the name to be different for bookmarks and bookmarks-buffered,
> + // so we just check if the pref enabling buffered is set here.
> + if (this.name == "bookmarks" && Svc.Prefs.get("engine.bookmarks.buffer", false)) {
This is admittedly cludgy, but it's vastly simpler and less error prone than whatever threading we'd need to do to expose a different name just to telemetry.
Another option is to look at the actual engine (e.g. in Service.engineManager) and see if it's buffered, maybe via a new property or something. If you'd rather I do that, np.
Comment 3•8 years ago
|
||
(In reply to Thom Chiovoloni [:tcsc] from comment #2)
> This is admittedly cludgy, but it's vastly simpler and less error prone than
> whatever threading we'd need to do to expose a different name just to
> telemetry.
Agreed, let's not thread a different name throughout just for telemetry.
> Another option is to look at the actual engine (e.g. in
> Service.engineManager) and see if it's buffered, maybe via a new property or
> something. If you'd rather I do that, np.
I'm leaning toward this, just because flipping the pref still requires a restart to switch engines. If we decide to roll this out gradually, via a system add-on, we'll count the existing engine as buffered, and vice versa.
| Comment hidden (mozreview-request) |
Comment 5•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8917572 [details]
Bug 1405205 - Report bookmark engine as bookmarks-buffered in the sync ping
https://reviewboard.mozilla.org/r/188534/#review193814
Awesome, thanks!
Attachment #8917572 -
Flags: review?(kit) → review+
| Assignee | ||
Comment 7•8 years ago
|
||
Not until kit's buffer patch (bug 1305563) lands.
Flags: needinfo?(tchiovoloni)
| Comment hidden (mozreview-request) |
| Assignee | ||
Comment 9•8 years ago
|
||
Comment on attachment 8917572 [details]
Bug 1405205 - Report bookmark engine as bookmarks-buffered in the sync ping
It's been so long, please take a peek and tell me that it still makes sense?
I mean, it's not like there's that much code there, but still, carrying over an r+ from October seems like a stretch
Attachment #8917572 -
Flags: review+ → review?(kit)
Comment 10•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8917572 [details]
Bug 1405205 - Report bookmark engine as bookmarks-buffered in the sync ping
https://reviewboard.mozilla.org/r/188534/#review222134
Still looks good, thanks!
Attachment #8917572 -
Flags: review?(kit) → review+
Comment 11•8 years ago
|
||
Pushed by tchiovoloni@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2398885a5762
Report bookmark engine as bookmarks-buffered in the sync ping r=kitcambridge
Comment 12•8 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
Comment 13•8 years ago
|
||
Assuming this is wontfix for 59 based on the dependency on bug 1305563
status-firefox59:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•