Closed Bug 1754638 Opened 3 years ago Closed 3 years ago

Remove or update probes expiring in Firefox 100: installation.first_seen#first_seen before Gecko version increases to 100 on 2022-03-08

Categories

(Firefox :: Installer, task)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox97 --- unaffected
firefox98 --- unaffected
firefox99 + fixed

People

(Reporter: telemetry-probes, Assigned: bytesized)

References

Details

(Whiteboard: [probe-expiry-alert])

Attachments

(2 files, 1 obsolete file)

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

installation.first_seen#first_seen

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.

Tracking because browser/modules/test/unit/test_InstallationTelemetry.js depends on it.

Flags: needinfo?(bytesized)
Summary: Remove or update probes expiring in Firefox 100: installation.first_seen#first_seen → Remove or update probes expiring in Firefox 100: installation.first_seen#first_seen before Gecko version increases to 100 on 2022-03-08

This probe was requested by :RT in Bug 1660198. It was originally set to expire in version 94. In Bug 1725295, the expiration was extended to version 100.

@RT Is this probe still needed or can it be removed? If it is still needed, could you tell me what the new expiration should be?

Flags: needinfo?(bytesized) → needinfo?(rtestard)
Attached file renewal_request.md (obsolete) —

There is a very high business value in retaining that probe since it will enable us to make better decisions moving forward and answer tricky questions as they surface:

  • With bug 1743465 we added the ability to identify if MSIX installs were on systems where Firefox was already installed, which is critical to help understand the value of our store distribution channel and requires this field AFAIU
  • In our backlog we intend to expose custom onboarding to make re-installs a better experience
  • This indicator helps surface that a significant portion of our new profiles originate from silent installations, which are strong enterprise signals. We're exploring options for better addressing our enterprise users and being able to segment them out will prove valuable to make decisions when this gets prioritized

Chris, thanks for helping review

Flags: needinfo?(rtestard)
Attachment #9264376 - Flags: data-review?(chutten)

Romain's data renewal request specifies that the new expiration should be "never". I'll put up a patch shortly to make that change.

Assignee: nobody → bytesized

Comment on attachment 9264376 [details]
renewal_request.md

The renewal form cannot be used to make a collection permanent (as it doesn't contain all the necessary information that permanent collections require, like the name of the responsible individual). Please refile with the full form

Attachment #9264376 - Flags: data-review?(chutten) → data-review-
Flags: needinfo?(rtestard)
Attached file Full form
Attachment #9264376 - Attachment is obsolete: true
Flags: needinfo?(rtestard)
Attachment #9265702 - Flags: data-review?(chutten)

Comment on attachment 9265702 [details]
Full form

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 #9265702 - Flags: data-review?(chutten) → data-review+
Pushed by ksteuber@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/61f538b29284 Set expiration for installation.first_seen probe to "never" r=bhearsum
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: