Open Bug 1845124 Opened 2 years ago Updated 4 months ago

Why did the number of network recoverable errors not improve after tooLateToSend?

Categories

(Toolkit :: Telemetry, task, P1)

Product:
Toolkit
Component:
Telemetry
Type:
task

Tracking

()

Status:
ASSIGNED

People

(Reporter: chutten, Assigned: chutten)

References

Details

In bug 1777233 we stopped trying to send pings late in shutdown when it was too late to send them. This, combined with bug 1776201's change to turn unrecoverable network errors to recoverable ones, led us to believe we'd see a precipitous and welcome drop in the number of recoverable neterrs with bug 1777233's change.

The drop didn't end up happening.

This bug is about looking into why. Is bug 1777233's code working as designed and desired? Is our hypothesis that late pings were to blame unsupported? What do we know about these unrecoverable errors? What could we learn (with more instrumentation, perhaps?)?

Assignee: nobody → pmcmanis
Status: NEW → ASSIGNED
Priority: -- → P1

The bug assignee is inactive on Bugzilla, and this bug has priority 'P1'.
:chutten, could you have a look please?

For more information, please visit BugBot documentation.

Assignee: pmcmanis → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(chutten)

Yup, I'll add this to my list. Thank you, BugBot.

Assignee: nobody → chutten
Status: NEW → ASSIGNED
Flags: needinfo?(chutten)
You need to log in before you can comment on or make changes to this bug.