Closed
Bug 1920723
Opened 10 months ago
Closed 9 months ago
Migrate Services.telemetry.recordEvent calls in SearchService.sys.mjs to Glean APIs
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
133 Branch
Tracking | Status | |
---|---|---|
firefox133 | --- | fixed |
People
(Reporter: chutten, Assigned: florian)
References
Details
Attachments
(1 file)
search.engine.* events in SearchService were added side-by-side to both Legacy Telemetry and Glean two years ago in bug 1634555.
Now we intend to deprecate Legacy Telemetry's recordEvent
API in bug 1918702. To do that we can
- Remove the Legacy Telemetry events, leaving the Glean ones.
- If no one's using the Legacy Telemetry events, this'd be the ideal choice.
- Collect the Legacy Telemetry events via mirroring through the Glean API
- This will have two very similarly-structured and -named events in Glean, but will maintain Legacy Telemetry event collection
:Standard8, have the Legacy Telemetry events been used these past two years? Can we remove them and their calls? Or should we preserve their collection.
Flags: needinfo?(standard8)
Comment 1•10 months ago
|
||
The dashboards I have use the Glean version of the events, I'm asking around in case there's legacy usages.
Assignee | ||
Comment 2•10 months ago
|
||
Comment 3•9 months ago
|
||
I've not had any mentions that we need to keep this, so I think we can go ahead and remove the legacy events.
Flags: needinfo?(standard8)
Updated•9 months ago
|
Assignee: chutten → florian
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/276f9948628e
remove search.engine legacy telemetry event that has been replaced by a Glean event, r=Standard8,settings-reviewers.
Comment 5•9 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
status-firefox133:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•