Determine if payload.addonDetails.XPI should be removed from common pings
Categories
(Data Platform and Tools :: General, task, P3)
Tracking
(Not tracked)
People
(Reporter: relud, Unassigned)
References
Details
Attachments
(1 file)
1.78 KB,
text/plain
|
Details |
it was pointed out in a meeting that extensions aren't necessarily XPI
s anymore, so this field may be obsolete?
some investigation shows me that in recent versions of firefox payload.addonDetails.XPI
does in fact contain information about installed addons.
Comment 1•5 years ago
|
||
Thanks for filing this, it feels like maybe we should ask someone from the client/addons team if this data is still relevant? If not, perhaps we can just stop submitting it. Here's the data from a random client on nightly.
Comment 2•5 years ago
|
||
We don't use this field in TAAR as far as I know. We only use the active_addons
field in main_summary.
Comment 3•5 years ago
|
||
:ddurst, do you happen to know what addonDetails
is useful for (not to be confused with activeAddons
, which is a different thing)
Speaking of which, addonDetails
should only be a part of the "main" ping, not anything else. activeAddons
is the one that's in the Environment.
Comment 4•5 years ago
|
||
I do not (I think it was theoretically useful for something, but I don't know if it's practically so). Do we know if any queries are using it (I suspect not)?
Redirecting to rhelmer and Fallen.
Reporter | ||
Comment 5•5 years ago
|
||
it is being used in main summary to determine disabled addons
Updated•5 years ago
|
Updated•5 years ago
|
Comment 6•3 years ago
|
||
main_summary
is deprecated and we aren't using payload.addonDetails.XPI
in any other ETL, so I think this collection can be removed.
Updated•2 years ago
|
Description
•