Closed
Bug 1286580
Opened 9 years ago
Closed 8 years ago
Bad Date served by Aggregator for beta44 Causes tmo failure
Categories
(Data Platform and Tools :: General, defect, P2)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: chutten, Unassigned)
References
()
Details
https://mzl.la/29vGCs9 doesn't load because of an assertion failure in telemetry.js. It assumes dates coming from the aggregator are well-formed, but for some reason at least one isn't.
Updated•9 years ago
|
Points: --- → 3
Priority: -- → P2
Updated•8 years ago
|
Component: Metrics: Pipeline → Telemetry Aggregation Service (TMO)
Product: Cloud Services → Data Platform and Tools
Comment 1•8 years ago
|
||
We have a few of these bad build_id fields. We retrieve it from application/buildId, which of course may have weird strings (but not too many). We currently have 30 build_ids that do not match `\d{8}` (mozaggregator only takes the first 8 chars). I think we should leave those aggregated as-is for the moment, and deal with the problem client-side.
Updated•8 years ago
|
Component: Telemetry Aggregation Service (TMO) → Telemetry Dashboard
Product: Data Platform and Tools → Webtools
Version: unspecified → other
Reporter | ||
Comment 2•8 years ago
|
||
Beta 44 doesn't matter so much these days...
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Webtools → Data Platform and Tools
Assignee | ||
Updated•3 years ago
|
Component: Telemetry Dashboards (TMO) → General
You need to log in
before you can comment on or make changes to this bug.
Description
•