Closed Bug 1919390 Opened 2 years ago Closed 1 year ago

Migrate HTTP3_CHANNEL_ONSTART_SUCCESS, HTTP_CHANNEL_PAGE_ONSTART_SUCCESS_TRR3, and HTTP_CHANNEL_SUB_ONSTART_SUCCESS_TRR3 P1 probes to glean.

Categories

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

Product:
Core
Component:
Networking: HTTP
Type:
task
Points:
2

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1944631

People

(Reporter: sekim, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [necko-triaged][necko-priority-next])

Location of the probes (HTTP3_CHANNEL_ONSTART_SUCCESS, HTTP_CHANNEL_PAGE_ONSTART_SUCCESS_TRR3, and HTTP_CHANNEL_SUB_ONSTART_SUCCESS_TRR3)

Steps:

  1. Add an equivalent glean probe to metrics.yaml. Telemetry probe can be mirrored if compatible.
  2. Add an equivalent line that collects the probe in glean like this example.
  3. If the telemetry probe cannot be mirrored, it's best to ask the owner whether to keep both or remove the probe.
  4. Glean probes can be tested via sending a ping on about:glean
Blocks: necko-glean
Severity: -- → N/A
Points: --- → 2
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-next]

Florian has taken care of this for us in bug bug 1944631

Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1944631
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.