Closed Bug 1017686 Opened 11 years ago Closed 10 years ago

JEP Telemetry

Categories

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

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: evold, Assigned: evold)

Details

Attachments

(1 file)

Writing a JEP to describe the telemetry work that I'd like to get done for the add-on sdk.
Assignee: nobody → evold
Hey Jeff, I haven't started the implementation side of this yet, but if you could take a look at what I have so far and provide some feedback that'd be great! I'm going to take a little break for now. I think I should probably implement one or two measurements before filling out the implementation side so that I have a better idea about what is involved.
Attachment #8430897 - Flags: feedback?(jgriffiths)
It looks good generally. I think also with telemetry, it is good to come up with some things to measure and start measuring them, getting the data for the initial list of measures will tell us useful things and also get our feet wet. We can always add more measures, or expire measures that aren't useful. Two things that are good to know: 1. telemetry measures typically expire, but we can keep them going 2. there are plans afoot to turn on telemetry by default in Beta (!)
Attachment #8430897 - Flags: feedback?(jgriffiths) → feedback+
Priority: -- → P2
JEP'ing is over.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: