Closed Bug 1754656 Opened 2 years ago Closed 2 years ago

Remove or update probes expiring in Firefox 100: os.environment.launch_method

Categories

(Firefox :: Shell Integration, task, P1)

task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: telemetry-probes, Assigned: bytesized)

References

Details

(Whiteboard: [probe-expiry-alert][fidedi-ope])

Attachments

(2 files)

The following Firefox probes will expire in the next major Firefox nightly release: version 100 [1].

os.environment.launch_method

What to do about this:

  1. If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
  2. If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].

If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.

Your Friendly, Neighborhood Telemetry Team

[1] https://wiki.mozilla.org/Release_Management/Calendar
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

Flags: needinfo?(shong)

I think we probably want to keep these forever: it's always helpful to see how Firefox is being invoked from the OS on Windows, especially as we push towards being the default PDF handler, etc.

:romain, do you concur? If so I can prepare the data-review request.

Flags: needinfo?(shong) → needinfo?(rtestard)
Severity: -- → N/A
Priority: -- → P1
Whiteboard: [probe-expiry-alert] → [probe-expiry-alert][fidedi-ope]

Yes, pretty sure we want to retain this one forever given ongoing experiments with pin to taskbar, thanks!

Flags: needinfo?(rtestard)
Assignee: nobody → bytesized

So, the code freeze is today and this patch won't get merged until after it is over. This means that, after the code freeze, Nightly will go to version 100 and there will be a brief interruption in the reporting for this probe (on Nightly only) since the probe expires in version 100. Then, this patch will land and the interruption will be over and we will go back to reporting the probe properly. There will never be any interruption on Beta or Release, and no uplift of the patch will be needed to ensure that.

Attachment #9266365 - Flags: data-review?(chutten)

Comment on attachment 9266365 [details]
Bug 1754656 data review.md

DATA COLLECTION REVIEW RESPONSE:

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

Yes.

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

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

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

Yes, Romain Testard is responsible.

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.

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

Default on for all channels.

Does the instrumentation include the addition of any new identifiers?

No.

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

Yes.

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

No.


Result: datareview+

Attachment #9266365 - Flags: data-review?(chutten) → data-review+

I'll land this next week, after the soft freeze is over.

Pushed by ksteuber@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/45f5fe0dc7d1
Renew os.environment.launch_method r=nalexander
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.