Open Bug 1928257 Opened 3 days ago Updated 21 hours ago

Remove or update probes expiring in Firefox 135: MEMORY_PHC_SLO* before Gecko version gets increased to 135 on 2024-11-25

Categories

(Core :: Memory Allocator, task)

Product:
Core
Component:
Memory Allocator
Type:
task

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox132 --- unaffected
firefox133 --- unaffected
firefox134 + affected

People

(Reporter: telemetry-probes, Unassigned, NeedInfo)

References

Details

(Whiteboard: [probe-expiry-alert])

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

MEMORY_PHC_SLOP
MEMORY_PHC_SLOTS_ALLOCATED
MEMORY_PHC_SLOTS_FREED
PROCESS_LIFETIME

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 patch to extend their expiry.

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

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

Flags: needinfo?(pbone)

Tracking because every expired telemetry probe causes a test failure.

status-firefox132: --- → unaffected
status-firefox133: --- → unaffected
status-firefox134: --- → affected
status-firefox-esr115: --- → unaffected
status-firefox-esr128: --- → unaffected
tracking-firefox134: --- → +
Summary: Remove or update probes expiring in Firefox 135: MEMORY_PHC_SLO* → Remove or update probes expiring in Firefox 135: MEMORY_PHC_SLO* before Gecko version gets increased to 135 on 2024-11-25
You need to log in before you can comment on or make changes to this bug.