Closed
Bug 1390707
Opened 7 years ago
Closed 7 years ago
Add `extensions.legacy.enabled` pref to Telemetry Aggregates
Categories
(Data Platform and Tools :: General, enhancement, P2)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bmiroglio, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
*This is for Nightly 57 ONLY*
Having this pref in TMO would help the add-ons team
1.) track blowback on Nightly since we just set extensions.legacy.enabled = false by default.
2.) filter out Users on Nightly 57 that reset the pref back to true
The alternative is generating custom reports, however if adding the pref to TMO is trivial then let's do that :).
Frank--what's your take on this?
Reporter | ||
Updated•7 years ago
|
Summary: Add `extensions.legacy.enabled` pref as a filter Telemetry Aggregates → Add `extensions.legacy.enabled` pref to Telemetry Aggregates
Updated•7 years ago
|
Assignee: nobody → fbertsch
Status: NEW → ASSIGNED
Priority: -- → P1
Comment 1•7 years ago
|
||
We've decided that this is too specific of an ask for the aggregator. Instead we should add this information to main_summary, where we can easily query it in re:dash and build reports there.
The schema needs updated: https://github.com/mozilla/telemetry-batch-view/blob/master/src/main/scala/com/mozilla/telemetry/views/MainSummaryView.scala#L799
As well as the function to retrieve the prefs: https://github.com/mozilla/telemetry-batch-view/blob/master/src/main/scala/com/mozilla/telemetry/views/MainSummaryView.scala#L307
And then it will show. Does this work for you, Ben?
Assignee: fbertsch → nobody
Status: ASSIGNED → NEW
Component: Datasets: Telemetry Aggregates → Datasets: Main Summary
Flags: needinfo?(bmiroglio)
Comment 4•7 years ago
|
||
Not immediately, I'm bogged down with experiments + heavy_users stuff.
Flags: needinfo?(fbertsch)
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
User prefs are stored as a nested struct in main_summary.
Unfortunately, adding new fields to a nested struct causes schema evolution to fail (and hence will break the dataset in re:dash).
The above PR will need to be re-worked to use a different approach - I suggest we flatten all the prefs into top-level fields named "user_pref_<sanitized pref name>"
Frank, what do you think of this approach (it's similar to what we do for scalars and histograms currently)?
Flags: needinfo?(fbertsch)
Updated•7 years ago
|
Points: --- → 2
Priority: P1 → P2
Comment 7•7 years ago
|
||
Updated•7 years ago
|
Attachment #8918977 -
Attachment is obsolete: true
Comment 8•7 years ago
|
||
Good plan, happy to see you kept the old prefs as they were. I'm reviewing now.
Flags: needinfo?(fbertsch)
Comment 9•7 years ago
|
||
This has been added - a new top-level field called "user_pref_extensions_legacy_enabled" will appear in tomorrow's table.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•2 years ago
|
Component: Datasets: Main Summary → General
You need to log in
before you can comment on or make changes to this bug.
Description
•