Closed
Bug 1785104
Opened 4 years ago
Closed 2 years ago
Add remote settings listeners to update SearchSERPTelemetry as soon as an update is received from remote settings
Categories
(Firefox :: Search, task, P3)
Firefox
Search
Tracking
()
RESOLVED
FIXED
121 Branch
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | fixed |
People
(Reporter: standard8, Assigned: jteow)
References
Details
(Whiteboard: [snt-triaged])
Attachments
(1 file)
Currently, SearchSERPTelemetry only loads from remote settings on startup, if remote settings receives an update, then the update is not applied until the next startup.
For a lot of updates, this is acceptable, but when we are releasing changes alongside search-config changes, then it would be useful if we have both updated as soon as they are received so that the reported telemetry is as correct as possible.
One thing to note is that we'll also need to make sure we pass any updates through to the child processes.
Updated•4 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNT-251
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → jteow
Status: NEW → ASSIGNED
Updated•2 years ago
|
Attachment #9361446 -
Attachment description: Bug 1785104 - Update consumers of search-telemetry-v2 when it is updated - r?standard8! → WIP: - Bug 1785104 - Update consumers of search-telemetry-v2 when it is updated - r?standard8!
Updated•2 years ago
|
Attachment #9361446 -
Attachment description: WIP: - Bug 1785104 - Update consumers of search-telemetry-v2 when it is updated - r?standard8! → Bug 1785104 - Update consumers of search-telemetry-v2 when it is updated - r?standard8!
Pushed by jteow@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b9da4d65ad73
Update consumers of search-telemetry-v2 when it is updated - r=Standard8
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox121:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•