Add telemetry for the installed built-in Search Engines
Categories
(Firefox :: Search, task, P2)
Tracking
()
People
(Reporter: standard8, Unassigned)
References
Details
As part of enabling built-in Search Engines WebExtensions to be updated out-of-band, we would like to be able to record telemetry on them.
This will:
- Enable monitoring of Search Engine roll-outs to ensure they are updated successfully.
- Aid with testing experiments to know that the expected versions are installed.
Search Engine WebExtensions currently have the environment data disabled for them.
From the discussion in the original bug (bug 1496075 comment 53 though to 60, and maybe a couple of others), it seems it was disabled to avoid telemetry generating multiple sub-session on startup. I don't know if that is still an issue.
Mike Connor also suggested reducing the amount of data for the search engine WebExtensions so that we are not increasing the size of a payload too much. Generally, just having the id and version should be enough.
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
So the telemetry above was disable to maintain the status quo, when we switched from OpenSearch to WebExtensions by default this meant the additional extensions were being recorded in telemetry. Since there wasnt any need for them previously, to avoid a data review and collecting information we dont need I excluded them from the telemetry. We can add it back easily with review, but given those questions are both related to Normandy rollouts, suspect they may have their own data for this.
Rehan, does Normandy have its own telemetry system to answer the above questions?
|
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 2•5 years ago
|
||
Sorry about the delayed response.
Search Engine WebExtensions currently have the environment data disabled for them.
When delivered via Normandy this will no longer be true
Rehan, does Normandy have its own telemetry system to answer the above questions?
Normandy does provide event telemetry about enrollments (or enrollment failures) which would let us track extension installations and installation failures.
|
|
Reporter | |
Comment 3•5 years ago
|
||
Thanks for the response Rehan.
Dale and I discussed this yesterday, we decided that since we know what's installed in a particular version (via what was shipped), and Normandy knows about what's running, that should be enough for now, given that we don't have specific questions around telemetry for this - the concern was more about knowing what's rolling out and where if an issue arose, and it seems that is covered.
Therefore closing as wontfix.
Description
•