Closed
Bug 1264332
Opened 9 years ago
Closed 9 years ago
Investigate/verify the proportion of invalid crash pings in the crash aggregates job.
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: azhang, Assigned: azhang)
References
(Depends on 1 open bug)
Details
Although only 0.06% of all pings are ignored by the crash aggregates job, we don't know what percentage of this are crash pings.
I will be investigating how these ignored pings impact the data.
In a random sample of 50000 *crash* pings, 3 of them are ignored. I expect that these ignored pings will not be an issue.
I've added a few counters to the crash aggregates job to get some better numbers. It will complete in ~3 hours.
Assignee | ||
Comment 2•9 years ago
|
||
After looking through ~400M pings, this appears to be working correctly:
> SUCCESSFULLY COMPUTED CRASH AGGREGATES FOR 2016-04-12
> SUCCESSFULLY UPLOADED CRASH AGGREGATES FOR 2016-04-12 TO S3
> ========================================
> JOB COMPLETED SUCCESSFULLY
> 424812681 main pings processed, 280652 main pings ignored
> 3250411 crash pings processed, 1014 crash pings ignored
> ========================================
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 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
•