Remove or update metrics expiring in Firefox 130: bounce.tracking.protection.purge_duration
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: telemetry-probes, Assigned: manuel)
References
Details
(Whiteboard: [metric-expiry-alert])
Attachments
(1 file)
The following metrics will expire in the next Firefox Nightly release: version 130.
bounce.tracking.protection.purge_duration
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their
metrics.yaml
definition file. - If one, some, or all of the metrics are still required, please submit a Data Collection Review and patch to extend their expiry. There is a shorter form for data collection renewal.
If you have any problems, please ask for help on the #glean Matrix room or the #data-help Slack channel.
We'll give you a hand.
Your Friendly Neighbourhood Glean Team
This bug was auto-filed by probe-scraper.
Comment 1•5 months ago
|
||
Manuel, what do you think about aligning expiry with the other probes (134)? It seems worth keeping for a bit longer, especially for when we roll this out to ETP strict.
Assignee | ||
Comment 2•5 months ago
|
||
Align all telemetry probes on the same release to update/remove them
together.
Add expire dates for startup telemetry due to low effort extend the
telemetry.
Updated•5 months ago
|
Assignee | ||
Comment 4•5 months ago
|
||
(In reply to Paul Zühlcke [:pbz] from comment #1)
Manuel, what do you think about aligning expiry with the other probes (134)? It seems worth keeping for a bit longer, especially for when we roll this out to ETP strict.
I agree
Comment 5•5 months ago
|
||
bugherder |
Description
•