1928270 - Remove or update metrics expiring in Firefox 135: ls.preparelsdatabase.processing_time before Gecko version gets increased to 135 on 2024-11-25

Status: RESOLVED FIXED

(Core :: Storage: localStorage & sessionStorage, task)

Description

[telemetry-probes]

The following metrics will expire in the next Firefox Nightly release: version 135.

ls.preparelsdatabase.processing_time
ls.request.recv_cancellation

What to do about this:

1. If one, some, or all of the metrics are no longer needed, please remove them from their metrics.yaml definition file.
2. If one, some, or all of the metrics are still required, please submit a patch to extend their expiry.

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

[Jan Varga [:janv]]

I'd like to adjust the metrics, but I have more important things to handle right now. I would say, let's extend the expiration to 138 for now.

Comment 2

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

Tracking because every expired telemetry probe causes a test failure.

Comment 3

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

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

:jstutte, 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.

Comment 4

[Harveer Singh]

Changes for this has been landed as part of the main patch for the defect: https://bugzilla.mozilla.org/show_bug.cgi?id=1928268