1577074 - Instrument scripts executed from editor mode

Status: RESOLVED FIXED

(DevTools :: Console, task, P1)

Description

[:Harald Kirschner :digitarald]

Simplest fix would probably adding an extra_key to the execute_js event: https://dxr.mozilla.org/mozilla-central/source/toolkit/components/telemetry/Events.yaml#1065. The key would be input and the value either be inline or multiline.

Later we can think about more user flows, but users actually executing code in editor mode is the success metric should probably track most right now.

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Bug 1577074 - Instrument scripts executed from editor mode. r=rcaliman.

We add an extra "input" property that is filled with
either "inline" or "multiline" depending if the expression
was evaluated in regular webconsole layout or in editor mode.

The test that was checking the execute_js telemetry event is
modify to only check what it was created for (hitting enter
on incomplete expression adds new line), and a new test is
added to specifically check that the execute_js telemetry event
is recorded as we expect.

Comment 2

[:Harald Kirschner :digitarald]

Attachment: request.txt

Comment 3

[:Harald Kirschner :digitarald]

Comment on attachment 9088883 [details]
request.txt

Changing data steward as Tim is out today.

Comment 4

[Ben Miroglio [:bmiroglio]]

Comment on attachment 9088883 [details]
request.txt

# Data Review Form 

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

This will be documented in the Events specification: https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Events.yaml

2) Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Provide details as to the control mechanism available.

Yes, this can be turned off by toggling off Telemetry in Preferences

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

:digitarald

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** 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?

default-on

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)?

No.

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

Yes

8) Does there need to be a check-in in the future to determine whether to renew the data? (Yes/No) (If yes, set a todo reminder or file a bug if appropriate)**

No, this data is permanent.

9) Does the data collection use a third-party collection tool? **If yes, escalate to legal.**

No.

data-review r+

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6e9f2e7ef819
Instrument scripts executed from editor mode. r=rcaliman.

Comment 6

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/6e9f2e7ef819