Closed Bug 1850880 Opened 3 years ago Closed 3 years ago

Remove or update metrics expiring in Firefox 120: networking.http_content_onst*

Categories

(Core :: Networking: HTTP, task, P2)

task

Tracking

()

RESOLVED FIXED
119 Branch
Tracking Status
firefox119 --- fixed

People

(Reporter: telemetry-probes, Assigned: acreskey)

References

Details

(Whiteboard: [metric-expiry-alert][necko-triaged])

Attachments

(1 file)

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

networking.http_content_onstart_delay
networking.http_content_onstop_delay

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 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.

Andrew, I assume we want to extend this probe?

Flags: needinfo?(acreskey)

It looks like we're going to remove these since we are changing our approach (and they are a bit messy in the codebase).

Assignee: nobody → acreskey
Severity: -- → S3
Priority: -- → P2
Whiteboard: [metric-expiry-alert] → [metric-expiry-alert][necko-triaged]

We are pivoting our OMT strategy and so these expiring probes will not provide additional value.

Flags: needinfo?(acreskey)
Pushed by acreskey@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/86adcf3bfe46 Remove metrics expiring in Firefox 120: networking.http_content_onstart/stop r=necko-reviewers,valentin
Status: NEW → RESOLVED
Closed: 3 years 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: