Closed Bug 1850885 Opened 1 year ago Closed 1 year ago

Remove or update probes expiring in Firefox 120: firefoxview.synced_tabs_empty#synced_tabs_empty before Gecko version gets increase to 120 on 2023-09-25

Categories

(Firefox :: Firefox View, task)

task

Tracking

()

RESOLVED FIXED
119 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox117 --- unaffected
firefox118 --- unaffected
firefox119 + fixed

People

(Reporter: telemetry-probes, Assigned: sfoster)

References

Details

(Whiteboard: [probe-expiry-alert], [fidefe-firefox-view] )

Attachments

(2 files)

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

firefoxview.synced_tabs_empty#synced_tabs_empty

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/components/firefoxview/tests/browser/browser_tab_pickup_device_added_telemetry.js tests for this.

Flags: needinfo?(sfoster)
Summary: Remove or update probes expiring in Firefox 120: firefoxview.synced_tabs_empty#synced_tabs_empty → Remove or update probes expiring in Firefox 120: firefoxview.synced_tabs_empty#synced_tabs_empty before Gecko version gets increase to 120 on 2023-09-25

The bug is marked as tracked for firefox119 (nightly). However, the bug still isn't assigned.

:pluk, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(pluk)
Flags: needinfo?(sfoster)
Flags: needinfo?(pluk)

Ethan, James, we have probes expiring for the old Firefox View as of 120. As I understand it, we only need the hold back for 119, and then firefoxview-next will be rolled out to everyone as of 120. Can you confirm we don't need to renew these telemetry probes for the old firefox view for 120?

Flags: needinfo?(jstephens)
Flags: needinfo?(epiper)

Actually, I just realized this was a probe sfoster specifically added in bug 1809661 to see how long we wait before tabs appear. I think we can let this lapse and remove the use of it.

Flags: needinfo?(jstephens)
Flags: needinfo?(epiper)
Whiteboard: [probe-expiry-alert] → [probe-expiry-alert], [fidefe-firefox-view]

This is a reminder regarding comment #2!

The bug is marked as tracked for firefox119 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.

The plan is to extend the expiry out so we can continue to track the issue this telemetry captures.

Assignee: nobody → sfoster
Status: NEW → ASSIGNED

Comment on attachment 9352540 [details]
Bug 1850885 - Extend the expiry date for the synced_tabs_empty/since_device_added telemetry. r?sclements!

Request for Data Collection Renewal

** This form is for the renewal of an existing, reviewed data collection.**

** All questions are mandatory.
You must receive Data Review from a
Data Steward
on a filled-out Request before shipping your renewed data collection.**

  1. Provide a link to the initial Data Collection Review Request for this collection.
  1. When will this collection now expire?
  • v132
  1. Why was the initial period of collection insufficient?
  • The events are sporadic with significant outliers. We don't yet have a plan for how to address the issue of unexpectedly long waits between adding a sync device and synced tabs from that device being delivered to firefox view. We want to continue to collect and monitor these events in the meantime.
Attachment #9352540 - Flags: data-review?(chutten)
Attachment #9352540 - Flags: data-review?(chutten)
Attachment #9352889 - Flags: data-review?(chutten)

Comment on attachment 9352889 [details]
data collection renewal request

DATA REVIEW RESPONSE:

Is the provided Data Collection Review complete, correct, and data-review+ by a Data Steward?

Yes.

Is the data collection covered by the existing Firefox Privacy Notice?

Yes.


Result: datareview+

Attachment #9352889 - Flags: data-review?(chutten) → data-review+
Pushed by sfoster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9f4d171149bb Extend the expiry date for the synced_tabs_empty/since_device_added telemetry. r=sclements
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: