Closed
Bug 1199432
Opened 10 years ago
Closed 8 years ago
Analyze relationship between client ping parse failures and server-side missing pings
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: spenrose, Unassigned)
References
Details
(Whiteboard: [rC] [unifiedTelemetry])
+++ This bug was initially created as a clone of Bug #1179845 +++
Use the probe from [1] to determine whether missing v4 pings can be correlated with ping parsing failures in the client. Creating without assignment.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1187340
|
||
Updated•10 years ago
|
Group: mozilla-employee-confidential
|
||
Updated•10 years ago
|
Iteration: 43.1 - Aug 24 → 43.2 - Sep 7
Points: --- → 3
|
|
||
Updated•10 years ago
|
Whiteboard: [rC] [unifiedTelemetry] → [rC] [unifiedTelemetry][data-validation]
|
|
||
Updated•10 years ago
|
Whiteboard: [rC] [unifiedTelemetry][data-validation] → [rC] [unifiedTelemetry]
|
|
||
Updated•10 years ago
|
Priority: P1 → P3
|
|
||
Comment 1•8 years ago
|
||
As per group understanding, this has been addressed
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•