Last Comment Bug 733516 - Request for telemetry add-on data
: Request for telemetry add-on data
Status: RESOLVED WONTFIX
[Telemetry] -- needs PM project priority
:
Product: Mozilla Metrics
Classification: Other
Component: Data/Backend Reports (show other bugs)
: unspecified
: x86_64 Linux
: -- normal (vote)
: Backlogged - BZ
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks: TheGreatAddonTest
  Show dependency treegraph
 
Reported: 2012-03-06 13:05 PST by Justin Lebar (not reading bugmail)
Modified: 2015-04-02 07:17 PDT (History)
13 users (show)
See Also:
Due Date:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Justin Lebar (not reading bugmail) 2012-03-06 13:05:59 PST
Telemetry sends along with each ping the install's active add-ons.  I'd like to access this data for the purposes of figuring out which add-ons are popular and perhaps figuring out how add-ons are enabled/disabled over time.

I'm not sure what's the best way for you guys to give me access to this data.  I'm happy to massage it on my end, so if you gave me raw JSON dumps, that would be fine.  Perhaps we could start with pings from the most recent obsolete Aurora build and the set of pings from the Aurora build immediately before Aurora hit version 8.

While we're at it, I'd like the following information out of the pings:

 * Operating system
 * Build identifier
 * List of (active) add-ons
 * PAGE_FAULTS_HARD
 * All histograms starting with "MEMORY"
 * All histograms starting with "CYCLE_COLLECTOR"
 * All histograms starting with "GC"
 * All the SIMPLE_MEARSURE_ data points.

If it's easier, you can just give me the whole ping.  :)

If you'd like me to analyze this data directly on the Telemetry servers, that's fine too.  I can write SQL, but I may need some hand-holding to use hbase or hadoop.
Comment 1 Nathan Froyd [:froydnj] 2012-03-07 09:41:51 PST
(In reply to Justin Lebar [:jlebar] from comment #0)
>  * PAGE_FAULTS_HARD

Do note that this histogram is not available on Windows systems.
Comment 2 Justin Lebar (not reading bugmail) 2012-04-10 09:25:20 PDT
Can someone please look at this?  This is blocking a MemShrink:P1 bug.
Comment 3 Annie Elliott 2012-07-02 14:06:34 PDT
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Comment 4 Annie Elliott 2012-07-09 15:06:42 PDT
Triaged.
Comment 5 Brendan Eich [:brendan] 2012-07-14 15:00:02 PDT
I'm a clueless n00b (or just old) -- what does the triage markup in this bug mean?

/be
Comment 6 Annie Elliott 2012-07-16 09:08:39 PDT
Hi Brendan -

No, I believe *I* get the n00b distinction (just reset my LDAP for the 1st time :)...

Metrics this past quarter did a HUGE bootstrap on their project & program management. Part of this was asking Telemetry to prioritise their 100+ current asks.

They assigned many P1s, some P2, etc. Some did not get assigned a Px. This was one of them. 

As there are so very many Telemetry asks, this one (not having been assigned any Px), was left in bugzilla on the backlog for the time being.

You can feel free to contact me or Gilbert if you have general process questions.

-Annie
Comment 7 Justin Lebar (not reading bugmail) 2012-07-16 09:13:09 PDT
To be clear: When this /is/ triaged, it will be tracked in the Metrics Jira instance?
Comment 8 Annie Elliott 2012-07-16 09:16:05 PDT
It has been triaged. When it is *prioritised* it will be tracked in JIRA.

Note You need to log in before you can comment on or make changes to this bug.