What's the difference between aggregate and individual crash reports?

An individual crash report is a single occurrence with its specific stack trace, device, version, and context, good for diagnosing the particular instance. An aggregate view groups many occurrences of the same crash into one issue with occurrence counts, affected-player counts, and cross-instance patterns, good for understanding scale and priority. Individual reports give per-instance detail; aggregates show how common and impactful each crash is. You use both at different levels.

Why do I need aggregate crash data, not just individual reports?

Because individual reports don't show scale, one report doesn't tell you whether a crash hit one player or thousands, or whether several reports are the same issue. The aggregate view groups occurrences by signature and counts them, revealing which crashes are most common and impactful, and surfacing patterns (like a crash clustered on one device) that single reports hide. That aggregate picture is what lets you prioritize, deciding which crashes to fix based on real scale and impact.

When should I look at individual crash reports?

When diagnosing a specific crash you've decided to fix. After using the aggregate view to prioritize (identifying which grouped issue affects the most players), you drill into individual occurrences to examine the specific stack trace, device context, and breadcrumbs needed to understand and fix that crash. So the aggregate guides what to work on, and individual reports provide the per-instance detail to actually diagnose it, the two are complementary at the prioritization and diagnosis levels respectively.

Aggregate vs Individual Crash Reports

Quick answer: An individual crash report is one occurrence; an aggregate view groups many occurrences of the same crash into one issue with counts and patterns. Individual reports give per-instance detail; aggregates show scale and priority.

Crash data can be viewed as individual reports (each occurrence) or in aggregate (grouped issues), and the two serve different needs, specific detail versus scale and priority. Here's the comparison.

What an Individual Crash Report Offers

An individual crash report is a single occurrence: one crash, with its specific stack trace, device, version, and breadcrumb context. Its strength is specific detail, you see exactly what happened in that instance, which is useful for diagnosing the bug and understanding particular conditions.

Bugnet captures individual reports with full context, so you can examine specific instances. But individual reports alone don't tell you scale, one report doesn't reveal whether this crash hit one player or ten thousand. The individual view is for digging into a specific instance, not for prioritizing.

What the Aggregate View Offers

The aggregate view groups many occurrences of the same crash into one issue, with an occurrence count, affected-player count, and patterns across instances. Its strength is scale and priority: it tells you how common and impactful each crash is, and reveals patterns (all on one device) that single reports hide.

Bugnet's aggregate view groups crashes by signature and ranks by impact, so you see which crashes matter most. The aggregate is what turns raw occurrences into a prioritized picture, you see the few issues causing most crashes, which is essential for deciding what to fix.

Why You Use Both

They serve different needs: aggregates show scale and priority (which crashes matter, how common, what patterns), while individual reports show per-instance detail (the specific stack trace and conditions to diagnose). You use the aggregate to decide what to fix, then drill into individual reports to diagnose the chosen issue.

Bugnet provides both, the grouped aggregate for prioritization, and the individual occurrences with full context for diagnosis. So treat them as complementary at different levels: use the aggregate view to prioritize (which crashes affect the most players), and individual reports to dig into the specifics of the crash you've chosen to fix.

An individual crash report is one occurrence (per-instance detail for diagnosis); an aggregate view groups many into one issue with counts and patterns (scale and priority). Use aggregates to decide what matters, individuals to dig in.