971360 - Bump DEVTOOLS_* telemetry probes to Firefox 50

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect)

Description

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

As per this blog post, we need to ensure we keep collecting telemtry data for devtools:

http://lawrencemandel.com/2013/11/01/telemetry-reboot-firefox-os-probe-expiration/

Lawrence - I'm using it's play to glob the various DEVTOOLS_* probes together into one bug?

Comment 1

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Jeff Griffiths (:canuckistani) from comment #0) 
> Lawrence - I'm using it's play to glob the various DEVTOOLS_* probes
> together into one bug?

Yes. I think that's fine. No need to make work. However, please think about whether you need to track all of the probes long term. How are the probes used? Who is monitoring them?

As well, we can set Telemetry probes to never expire. If that's what you mean by Firefox 50, I suggest you use the non expiring option instead.

Comment 2

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

(In reply to Lawrence Mandel [:lmandel] from comment #1)
> (In reply to Jeff Griffiths (:canuckistani) from comment #0) 
> > Lawrence - I'm using it's play to glob the various DEVTOOLS_* probes
> > together into one bug?
> 
> Yes. I think that's fine. No need to make work. However, please think about
> whether you need to track all of the probes long term. How are the probes
> used? Who is monitoring them?

I use them, I'm building a dashboard. I put it as Firefox 50 so far because it seemed like a nice round number and I don't yet know which ones I need and which ones I don't need, or will always need.

> As well, we can set Telemetry probes to never expire. If that's what you
> mean by Firefox 50, I suggest you use the non expiring option instead.

It's not quite what I mean, but I'll keep it in mind.

Comment 3

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

To begin work on this we need to decide which probes we need. I would suggest:
- DEVTOOLS_TOOLBOX_INIT
- DEVTOOLS_OPTIONS_INIT
- DEVTOOLS_WEBCONSOLE_INIT
- DEVTOOLS_BROWSERCONSOLE_INIT
- DEVTOOLS_INSPECTOR_INIT
  - DEVTOOLS_MARKUP_INIT
  - DEVTOOLS_RULEVIEW_INIT
  - DEVTOOLS_COMPUTEDVIEW_INIT
  - DEVTOOLS_FONTINSPECTOR_INIT
  - DEVTOOLS_LAYOUTVIEW_INIT
- DEVTOOLS_JSDEBUGGER_INIT
- DEVTOOLS_JSBROWSERDEBUGGER_INIT
- DEVTOOLS_STYLEEDITOR_INIT
- DEVTOOLS_SHADEREDITOR_INIT
- DEVTOOLS_JSPROFILER_INIT
- DEVTOOLS_NETMONITOR_INIT
- DEVTOOLS_TILT_INIT
- DEVTOOLS_PAINTFLASHING_INIT
- DEVTOOLS_SCRATCHPAD_INIT
- DEVTOOLS_RESPONSIVE_INIT
- DEVTOOLS_DEVELOPERTOOLBAR_INIT
- DEVTOOLS_APPMANAGER_INIT (there are currently no probes for the app manager)
- DEVTOOLS_BROWSERTOOLBOX_INIT (there are currently no probes for the browser toolbox)

Comment 4

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

What is meant by the INIT-style measures, how do you propose to report this? Otherwise looks like a good list.

Comment 5

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

INIT would be a time measurement similar to the probe that lets us know how long similar to *_TIME_ACTIVE_SECONDS except that it tells us how long a tool has taken to initialize.

If this would be useful for you then please let me know. Also, is there anything else that you would like to measure?

Comment 6

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

The INIT measures sound great but aren't necessary, they can wait until 31. As previously discussed bug 974171 is higher priority. Thanks!

Comment 7

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Filter on 1ff0543e-b501-4893-a72b-e4773c01e655

Comment 8

[Georg Fritzsche [:gfritzsche]]

I see that DEVTOOLS_* probes have expiry "never".

Comment 9

[Alessio Placitelli [:Dexter]]

(In reply to Georg Fritzsche [:gfritzsche] from comment #8)
> I see that DEVTOOLS_* probes have expiry "never".

You're right, all these probes have already been taken care of. Closing this.