Remove or update probes expiring in Firefox 90: NETWORK_BACK_PRESSURE_SUSPENSION_*
Categories
(Core :: Networking: HTTP, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox89 | --- | fixed |
People
(Reporter: telemetry-probes, Assigned: nhnt11)
References
Details
(Whiteboard: [probe-expiry-alert][necko-triaged])
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
3.13 KB,
text/plain
|
chutten
:
data-review+
|
Details |
The following Firefox probes will expire in the next major Firefox nightly release: version 90 [1].
NETWORK_BACK_PRESSURE_SUSPENSION_RATE_V2
NETWORK_BACK_PRESSURE_SUSPENSION_CP_TYPE
NETWORK_BACK_PRESSURE_SUSPENSION_DELAY_TIME_MS
What to do about this:
- 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).
- 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.
Assignee | ||
Comment 1•3 years ago
•
|
||
Dragana, looks like you added these probes and/or last extended them in Oct 2020. Should we renew or remove them?
Comment 2•3 years ago
|
||
Yes, let's renew them.
Nihanth can you renew them?
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Assignee | ||
Comment 4•3 years ago
|
||
I've extended the expiry to "never" since we've renewed this a few times already.
Dragana: just to make sure I don't misrepresent anything here, does my answer to "Why was the initial period of collection insufficient?" look okay?
Comment 5•3 years ago
|
||
I've you've extended these probes to no longer expire you will need to fill out the full request so we can capture the extra requirements for permanent collections (mostly just identifying which individual will be responsible for them).
Assignee | ||
Comment 6•3 years ago
|
||
Done
Comment 7•3 years ago
|
||
I just wrote that you should make it permanent at the same time you posted the new request.
you can put only my name for the responsible person as well.
Thanks.
Comment 8•3 years ago
|
||
Comment on attachment 9211895 [details]
Request_1700824.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, Nihanth Subramanya and Dragana Damjanovic are responsible.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
Is the data collection request for default-on or default-off?
Default on for pre-release channels only.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does there need to be a check-in in the future to determine whether to renew the data?
No. This collection is permanent.
Result: datareview+
Pushed by nhnt11@gmail.com: https://hg.mozilla.org/integration/autoland/rev/7be0ab8037bb Extend Histogram expiry: NETWORK_BACK_PRESSURE_SUSPENSION_*. r=necko-reviewers,dragana
Comment 10•3 years ago
|
||
bugherder |
Description
•