Closed Bug 1639454 Opened 3 months ago Closed 3 months ago

Introduce telemetry for the Compatibility side panel


(DevTools :: Inspector: Compatibility, task, P2)



(firefox78 fixed)

Firefox 78
Tracking Status
firefox78 --- fixed


(Reporter: Honza, Assigned: daisuke)


(Blocks 1 open bug)



(2 files)

This is a follow up for bug 1625132.

The Compatibility side panel usage is currently using the following telemetry:


We should introduce specific telemetry for it:

See this function:


Martin, do you see any data for: DEVTOOLS_CUSTOM_TIME_ACTIVE_SECONDS & DEVTOOLS_CUSTOM_OPENED_COUNT ? Perhaps this could be useful until we introduce the new telemetry.


Flags: needinfo?(mbalfanz)

Yes, I do see data for this probe. I'll add it to the LayoutTools Dashboard

Flags: needinfo?(mbalfanz)


I think that we should still introduce specific probe for the Compat panel since DEVTOOLS_CUSTOM_TIME_ACTIVE_SECONDS & DEVTOOLS_CUSTOM_OPENED_COUNT are used for all custom panels (some panels could be added by extensions). It's a fallback used for all panels that don't have their own probe.

Martin, WDYT?


Flags: needinfo?(mbalfanz)

Yes, we definitely need to introduce a probe specific to the webcompat panel. The data I see is flawed in that there is more history than I should see, so I can't be sure what exactly collected the data.

Flags: needinfo?(mbalfanz)

Great, thanks Martin.

Daisuke, it would be awesome to land this yet in 78 (if possible) to start collecting the data.
(note that the 78 soft freeze is next week Thursday).


Flags: needinfo?(daisuke)

Thank you for the notice!
I will do soon.

Assignee: nobody → daisuke
Flags: needinfo?(daisuke)
Attached file
Attachment #9150676 - Flags: data-review?(tdsmith)
Comment on attachment 9150676 [details]

1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, in Histograms.json and Events.yaml as aggregated by the probe dictionary.

2) Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, the Firefox telemetry opt-out.

3) If the request is for permanent data collection, is there someone who will monitor the data over time?

Honza will monitor the probes.

4) Using the **[category system of data types](** on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, interaction data.

5) Is the data collection request for default-on or default-off?


6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?


7) Is the data collection covered by the existing Firefox privacy notice?


8) Does there need to be a check-in in the future to determine whether to renew the data?

No, this is a permanent collection.

9) Does the data collection use a third-party collection tool?

Attachment #9150676 - Flags: data-review?(tdsmith) → data-review+
Pushed by
Introduce OPENED_COUNT and TIME_ACTIVE_SECONDS telemetry for the compatibility panel. r=Honza

Backed out changeset 2cb92b52fb42 (bug 1639454) for telemetry related bustages

Push with failures:

Backout link:

Failure log:

[task 2020-05-26T23:11:02.646Z] 23:11:02     INFO -  make[4]: Entering directory '/builds/worker/workspace/obj-build/toolkit/components/telemetry'
[task 2020-05-26T23:11:02.646Z] 23:11:02     INFO -  toolkit/components/telemetry/
[task 2020-05-26T23:11:02.646Z] 23:11:02     INFO -  /builds/worker/workspace/obj-build/_virtualenvs/init_py3/bin/python -m mozbuild.action.file_generate /builds/worker/checkouts/gecko/toolkit/components/telemetry/build_scripts/ main .deps/ .deps/ /builds/worker/checkouts/gecko/toolkit/components/telemetry/Histograms.json /builds/worker/checkouts/gecko/dom/base/UseCounters.conf /builds/worker/checkouts/gecko/dom/base/nsDeprecatedOperationList.h ../../../layout/style/ /builds/worker/checkouts/gecko/servo/components/style/properties/ /builds/worker/checkouts/gecko/dom/base/UseCountersWorker.conf
[task 2020-05-26T23:11:02.646Z] 23:11:02     INFO -  Unsupported kind "count" for histogram "DEVTOOLS_COMPATIBILITYVIEW_OPENED_COUNT":
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -  New "count" histograms are not supported on Desktop, you should use scalars instead:
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -  Are you trying to add a histogram on Android? Add "operating_systems": ["android"] to your histogram definition.
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO - recipe for target '.deps/' failed
[task 2020-05-26T23:11:02.647Z] 23:11:02    ERROR -  make[4]: *** [.deps/] Error 1
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -  make[4]: Leaving directory '/builds/worker/workspace/obj-build/toolkit/components/telemetry'
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -  make[4]: *** Waiting for unfinished jobs....
[task 2020-05-26T23:11:02.647Z] 23:11:02     INFO -  make[4]: Entering directory '/builds/worker/workspace/obj-build/dom/bindings'
[task 2020-05-26T23:11:02.648Z] 23:11:02     INFO -  rm -f Node.webidl
[task 2020-05-26T23:11:02.648Z] 23:11:02     INFO -  make[4]: Leaving directory '/builds/worker/workspace/obj-build/dom/bindings'
Flags: needinfo?(daisuke)
Pushed by
Introduce OPENED_COUNT and TIME_ACTIVE_SECONDS telemetry for the compatibility panel. r=Honza
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 78
Flags: needinfo?(daisuke)
You need to log in before you can comment on or make changes to this bug.