898204 - Collect telemetry on modules used.

Status: RESOLVED INCOMPLETE

(Add-on SDK Graveyard :: General, defect, P2)

Description

[Erik Vold [:erikvold] (please needinfo? me)]

I suspect we spend a lot of time on modules that do not get used, it would be very useful to have telemetry for our modules.

Comment 1

[Dave Townsend [:mossop]]

AWESOME IDEA!

Comment 2

[Jeff Griffiths (:canuckistani) (:⚡︎)]

Is this the right way to get module usage? As part of the re-pack process we wrote some scripts to download jetpacks, unpack them and do analysis. 

There are obvious limitations - we don't get data from add-ons hosted off of AMO. 

Do you think telemetry data is the right approach here? It also has the limitation of being opt-in, so we don't get a complete picture either.

Comment 3

[Erik Vold [:erikvold] (please needinfo? me)]

(In reply to Jeff Griffiths (:canuckistani) from comment #2)
> Is this the right way to get module usage? As part of the re-pack process we
> wrote some scripts to download jetpacks, unpack them and do analysis. 
> 
> There are obvious limitations - we don't get data from add-ons hosted off of
> AMO. 
> 
> Do you think telemetry data is the right approach here? It also has the
> limitation of being opt-in, so we don't get a complete picture either.

Telemetry data will give us a picture of usage, though it is opt-in like you said and so it will not give us a complete picture.

Comment 4

[Erik Vold [:erikvold] (please needinfo? me)]

The telemetry data will be useful for performance measuring which will be useful in the long run anyhow.

Comment 5

[Erik Vold [:erikvold] (please needinfo? me)]

I'm unassigning myself from this, it takes too long to get feedback.

Comment 6

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1399562