Add a field to identify whether Firefox is running in Headless mode

RESOLVED FIXED in Firefox 68

Status

()

enhancement
P1
normal
RESOLVED FIXED
3 months ago
2 months ago

People

(Reporter: mreid, Assigned: chutten)

Tracking

Trunk
mozilla68
Points:
---

Firefox Tracking Flags

(firefox68 fixed)

Details

Attachments

(4 attachments)

Reporter

Description

3 months ago

It could be useful to know whether or not Firefox is running in Headless Mode for a given telemetry ping.

Looks like we can detect headless mode by checking the MOZ_HEADLESS env variable (as set by the app runner)

Priority: -- → P2
Assignee

Comment 2

2 months ago

Looks like we can use GfxInfo's isHeadless to take care of caching the value for us and getting it to JS where we can put it in the Environment.

Assignee: nobody → chutten
Status: NEW → ASSIGNED
Priority: P2 → P1
Assignee

Comment 3

2 months ago

If Firefox is in Headless Mode we expect it to behave rather differently. For
example, I imagine gpu perf metrics will be less than representative. We should
annotate Telemetry pings with whether or not we're operating in headless mode.

Assignee

Comment 4

2 months ago
Posted file GitHub Pull Request

PR for schema update

Assignee

Comment 5

2 months ago
Posted file Data Review Request

A quick ni?mreid so we can document that we did indeed talk about him owning this probe and I'm not just assigning it to him :)

Flags: needinfo?(mreid)
Attachment #9057349 - Flags: data-review?(teon)
Reporter

Comment 6

2 months ago

Yep, I think this will be useful in many contexts, including investigations like Bug 1507173. I'm happy to be responsible for this probe.

Flags: needinfo?(mreid)
Assignee

Updated

2 months ago
Attachment #9057349 - Flags: data-review?(teon) → data-review?(tdsmith)
Comment on attachment 9057349 [details]
Data Review Request

1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes, environment.rst is updated (minimally, but I think clearly) to include the collection.

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

Yes, the [Firefox telemetry opt-out](https://support.mozilla.org/en-US/kb/share-data-mozilla-help-improve-firefox).

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

Mark Reid.

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 1, technical 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?

No, permanent collection.

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

No.
Attachment #9057349 - Flags: data-review?(tdsmith) → data-review+

Comment 8

2 months ago
Pushed by chutten@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/71d205b6e9c7
Report whether Headless or not in Telemetry Environment r=janerik

Comment 9

2 months ago
bugherder
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.