Closed Bug 1434378 Opened 8 years ago Closed 7 years ago

Track startup crashes in error_aggregates and experiment_error_aggregates

Categories

(Data Platform and Tools Graveyard :: Datasets: Error Aggregates, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: akomar)

References

Details

Attachments

(2 files)

It would be good to track startup crashes seperately from main crashes, as they are much more serious. Definitely something we would also want to track in Mission Control. Mauro wrote up a PR to add this data to crash_aggregates for bug 1306013, could probably use some of the work there as inspiration: https://github.com/mozilla/telemetry-batch-view/pull/166
Assignee: nobody → akomarzewski
(In reply to akomarzewski from comment #1) > Should main_crashes[1] metric include startup crashes? > > [1] > https://github.com/mozilla/telemetry-streaming/blob/ > b3bd4b2e70f0f4ff04ae9887c3ba9bc83481545e/src/main/scala/com/mozilla/ > telemetry/streaming/ErrorAggregator.scala#L249 That probably makes the most sense for a first pass. I don't think we care about tracking non-startup crashes as a seperate entity from main crashes. CCing a few people from relman who might have opinions on this so they can chime in if they feel like it.
Flags: needinfo?(wlachance)
Points: --- → 1
Priority: -- → P1
Blocks: 1454642
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: