Add dedicated probe for node selections related to a user input
Categories
(DevTools :: Inspector, task, P3)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
Details
We currently compare the scalar devtools.inspector.node_selection_count with the histogram DEVTOOLS_INSPECTOR_OPENED_COUNT to categorize devtools users between:
- accidental: selection count === inspector open count
- active: selection count > inspector open count
- very active: selection count > ( inspector open count + 5)
However, the selection count can go up even if the user is not interacting with devtools.
When the currently selected node is removed, eg. because the page is dynamically updated or because a navigation occurs.
For instance, with the following STRs:
- open Firefox
- open a tab on mozilla.org
- open inspector
- reload the tab 3 times
- close the tab
The probes will have the following values:
- DEVTOOLS_INSPECTOR_OPENED_COUNT: 1
- devtools.inspector.node_selection_count: 7
Which would classify the user as a very active user, even though the user never interacted with devtools after opening it.
The risk is that we are mis-categorizing users who accidentally open DevTools but don't close the toolbox immediatly. Not sure if this represents a significant % of the accidental user base, but it would be great to fix this.
Our selection_count scalar is logged at https://searchfox.org/mozilla-central/rev/dcd9c2d2bc19d96d487825eb70c2333a4d60994e/devtools/client/inspector/inspector.js#1522 , and we have a reason argument which normally gives some context about the selection update.
We should review the current reasons provided to this method and see if we can define a shortlist of reasons which correspond to a user input. Then we can either:
- only log the current scalar when the selection comes from a user action
- or introduce a new probe (telemetry event) dedicated to this?
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Description
•