Closed Bug 1792201 Opened 3 years ago Closed 3 years ago

t/c/telemetry's pings.yaml should be firefox_desktop, not gecko

Categories

(Toolkit :: Telemetry, defect, P1)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
107 Branch
Tracking Flags:
Tracking Status
firefox-esr102 --- unaffected
firefox105 --- unaffected
firefox106 --- unaffected
firefox107 --- fixed

People

(Reporter: chutten, Assigned: chutten)

References

(Regression)

Details

(Keywords: regression)

And t/c/glean's pings.yaml should be gecko, not firefox_desktop.

Why? Legacy Telemetry, even if instrumented using Glean, isn't running unless we're in Firefox Desktop. You can see this by how t/c/t/metrics.yaml is in firefox_desktop_metrics

As for t/c/g: That's FOG, which you'd think could be a Firefox Desktop-only layer... nominally. There are some deeper layers that are reused, though, as evidenced by t/c/g/metrics.yaml being in gecko_metrics

This bug is about editing metrics_index.py to make these two changes.

Set release status flags based on info from the regressing bug 1790046

status-firefox105: --- → unaffected
status-firefox106: --- → unaffected
status-firefox107: --- → affected
status-firefox-esr102: --- → unaffected

Whoops, put https://phabricator.services.mozilla.com/D158061 against bug 1767040 instead.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.