1781978 - Remove or update probes expiring in Firefox 106: browser.startup.abouthome_cache_* when Gecko version gets increased to 106 on 2022-08-22

Status: VERIFIED FIXED

(Firefox :: New Tab Page, task)

Description

[telemetry-probes]

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

FX_ABOUTHOME_CACHE_CONSTRUCTION
browser.startup.abouthome_cache_result
browser.startup.abouthome_cache_shutdownwrite

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.

Comment 1

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Tracking because a test depend on this:
browser/components/newtab/test/browser/abouthomecache/browser_basic_endtoend.js

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

:daleharvey, 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 auto_nag documentation.

Comment 3

[Dale Harvey (:daleharvey)]

Leaving needinfo in Mike, Mike if the telemetry should be extended is there any chance you could do that? I don't really have the context on whether this telemetry should be removed ot not. I will prepare a patch to remove it though so if it is to be deleted that will be ready.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

This is a reminder regarding comment #2!

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

Comment 5

[Mike Conley (:mconley) (:⚙️)]

Attachment: Data collection renewal request.md

Comment 6

[Mike Conley (:mconley) (:⚙️)]

Attachment: Bug 1781978 - Bump expiry on about:home startup cache probes. data-review=darcese, r?niklas!

Comment 7

[Daniela Arcese [:daniela]]

Attachment: data renewal review

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/16e6f97ec794
Bump expiry on about:home startup cache probes. data-review=darcese, r=niklas

Comment 9

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/16e6f97ec794

Comment 10

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Verified fixed in the latest version increase simulation.

Comment 11

[Alex Finder]

(In reply to Pulsebot from comment #8)

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/16e6f97ec794
Bump expiry on about:home startup cache probes. data-review=darcese, r=niklas

== Change summary for alert #35100 (as of Thu, 11 Aug 2022 12:45:59 GMT) ==

Regressions:

Ratio	Test	Platform	Options	Absolute values (old vs new)
4%	booking FirstVisualChange	android-hw-a51-11-0-aarch64-shippable-qr	warm webrender	639.96 -> 668.58
4%	booking ContentfulSpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	warm webrender	879.04 -> 914.00
4%	booking loadtime	android-hw-a51-11-0-aarch64-shippable-qr	warm webrender	903.73 -> 939.67
3%	booking PerceptualSpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	warm webrender	1,276.33 -> 1,317.50

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=35100

Comment 12

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

The change doesn't affect current, it only ensures the behavior will be the same in Firefox 106. Could the change be from bug 1782184 which landed directly before?

Comment 13

[Alex Finder]

Performed multiple retriggers around revision 16e6f97ec794 and noticed that there is some noise. Will close the alert as invalid as a result. Please disregard previous regression comment.