Closed Bug 420997 Opened 16 years ago Closed 15 years ago

Add aggregate data to crash signature page

Categories

(Socorro :: General, task, P2)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: morgamic, Unassigned)

References

Details

in reports/list (or the view for viewing a crash signature) we need:

<chofmann>
Stack Signature: xxxxxxxx
Total Reports: Y
Unique users: X
Ave. time to this crash since session startup: Z seconds


first two help us figure out if the crashes for a stack signature are from a
few bozo's running the same test case over and over, or if there is fairly wide
distribution across many users.

the later helps to pin point thinks like start up crashes which really take a
high priority in the analysis and fixing.  If users can find something that
crashes the browser within a few seconds after start up we really focus a lot
of attention on those...
</chofmann>

bsmedberg mentioned there may be some privacy concerns surrounding user counts that is worthy of discussion...
Priority: -- → P2
Summary: Add aggregate data to crash signature → Add aggregate data to crash signature page
The privacy concern is this: we don't want people to be able to correlate crashes against a unique user: this makes it possible, even likely, that you can identify the user from the URLs he was visiting when he crashed.

So I'm worried about displaying "Unique users: 1" or even "Unique users: 3" in public... I'm not really concerned about it if the # of unique users is >10.
That's a fair concern (and one I wouldn't have thought of!). The simple fix is to just show "Unique users: < 10" in the case of less than 10 users reporting a stack.

This is useful information for the topcrash page as well, I'm finding. Anyway we can include it there? (Or should I file a new bug for that?)
This is for the topcrash page, no extra bug needed.
Blocks: 411357
Blocks: 418856
Severity: normal → trivial
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.