Closed
Bug 1587548
Opened 5 years ago
Closed 4 years ago
Investigate fix for 4AM 0-length pings
Categories
(Data Platform and Tools :: Glean: SDK, defect, P1)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mdroettboom, Assigned: mdroettboom)
References
Details
(Whiteboard: [telemetry:glean-rs:m11])
Ensure that the fix for bug 1566488 had effect.
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → mdroettboom
|
|
Assignee | |
Updated•5 years ago
|
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:m11]
|
|
Assignee | |
Comment 1•5 years ago
|
||
It looks like about 10% of metrics pings are 4AM and 0 length, so this fix is much better, but not entirely resolved:
https://console.cloud.google.com/bigquery?sq=1018637472215:7e0ab0f4a58b4d7db2f481a53d4575e1
|
||
Comment 2•5 years ago
|
||
Mike, are we still seeing this after bug 1602824?
Flags: needinfo?(mdroettboom)
|
|
Assignee | |
Comment 3•5 years ago
|
||
I haven't looked yet, but plan to today. A little afraid, as I expect things to be very different.
Flags: needinfo?(mdroettboom)
|
|
||
Updated•5 years ago
|
Priority: P3 → P1
|
|
Assignee | |
Comment 4•4 years ago
|
||
Closing as invalid. The metrics ping scheduling has completely changed, and this no longer seems to be a frequently occurring thing.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•