Collect telemetry data for all add-on types
Categories
(Toolkit :: Add-ons Manager, enhancement, P1)
Tracking
()
People
(Reporter: willdurand, Unassigned)
References
Details
As part of the "AMO Stats Processing" project, it was decided to use Telemetry data as the source of usage statistics displayed on AMO (instead of relying on a old, unreliable and costly infrastructure based on logs).
The problem is that we don't collect telemetry data for add-ons that are not extensions or themes. Extensions are listed as "active add-ons" (environment.addon.activeAddons) and the current theme is listed in environment.addon.theme). For these two add-on type, we do have new usage statistics on AMO.
We still need data for the other add-on types, namely: language packs and dictionaries. We can see in the codebase that we're only retrieving extensions and service extensions: https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/app/TelemetryEnvironment.jsm#730-735
Would it be possible to collect telemetry data for dictionaries and language packs in addition to extensions?
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
|
Reporter | |
Comment 1•4 years ago
|
||
Hi :chutten, would you know why only webextensions have been exposed as active add-ons by chance? We'd need similar data for dictionaries and langpacks so I am wondering if we could collect data for those add-on types too. Thanks!
|
||
Comment 2•4 years ago
|
||
I believe this is because this is an expensive-ish collection (the Environment is present in most Telemetry pings, and each active addon collection has many many data points associated with it) coupled with no one asking for it in the past.
Today, if this information is needed, I would probably recommend thinking about this new collection (dicts and langpacks) on its own and think about what information is necessary to answer the questions you need answered. Maybe a custom ping sent only when a dict/langpack is installed/uninstalled would be a better frequency? Maybe a count of them is sufficient, and should be sent in the "main" ping. Or perhaps the information in payload.addonDetails.XPI is sufficient?
|
|
Reporter | |
Comment 3•4 years ago
|
||
Thanks.
It looks like we have add-ons data in different locations and with different data points. I also learned about payload.info.addons recently, which, in fact, looks exactly like what we need for AMO usage stats. I am going to close this bug now and create a new one to review our Telemetry usage for add-ons.
Description
•