Open Bug 1596600 Opened 5 years ago Updated 2 years ago

Determine if payload.addonDetails.XPI should be removed from common pings

Categories

(Data Platform and Tools :: General, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: relud, Unassigned)

References

Details

Attachments

(1 file)

it was pointed out in a meeting that extensions aren't necessarily XPIs 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.

Blocks: 1595899
Attached file Example of this field (deleted) —

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.

We don't use this field in TAAR as far as I know. We only use the active_addons field in main_summary.

: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.

Flags: needinfo?(ddurst)

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.

Flags: needinfo?(rhelmer)
Flags: needinfo?(philipp)
Flags: needinfo?(ddurst)

it is being used in main summary to determine disabled addons

Flags: needinfo?(rhelmer)
Priority: -- → P3

main_summary is deprecated and we aren't using payload.addonDetails.XPI in any other ETL, so I think this collection can be removed.

Component: Datasets: Main Summary → General
Flags: needinfo?(philipp)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: