Add more specificity on when to record telemetry on reloaded due to a config change (search engine changed, engine-update)
Categories
(Firefox :: Search, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: mcheang, Assigned: scunnane)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng][search-telemetry-backlog])
Attachments
(1 file)
In Bug 1852527, I added telemetry for when the default engine's property is updated. (engine-update).
We discovered that our telemetry is not very specific when it comes to reloading engines due to a config change.
At the moment, when we reload due to a configuration change, we update the engines as they may have changed: engine.updateIfNoNameChange. However, we don't track if any attribute has actually changed from previous, and so we send out an update regardless: #updateFromManifest
We should consider adding more specificity on when we report the telemetry, some options:
- Only notify when something on the search engine has actually changed
- when reloading engines, have a special observer notification to indicate that all engines may have changed.
This bug may be a good spike to do during a DragonSlayer - spend a few hours experimenting and seeing what we'd like it to look like, and implement it.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Backed out changeset 55c366ee4422 (Bug 1876178) for causing documentation failures
Failure log: https://treeherder.mozilla.org/logviewer?job_id=483514893&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/7493a728ca5f93a9ea51ed98390dff1aa36be807
Comment 5•1 year ago
|
||
Backed out for causing documentation failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/0f913e6025c10ac90a6f492c27155b8dd78730b5
| Assignee | ||
Updated•1 year ago
|
Description
•