Socorro:PRD 2.x: Difference between revisions
| Line 8: | Line 8: | ||
= Requirements Gathering = | = Requirements Gathering = | ||
We interviewed Socorro users from the Firefox, Platform and QA teams, as well as Mozilla Messaging (for Thunderbird) about their current use of the product. | We interviewed Socorro users from the Firefox, Platform and QA teams, as well as Mozilla Messaging (for Thunderbird) about their current use of the product. | ||
* | * [https://wiki.mozilla.org/Socorro:Planning_2.0 Interview prompt sheet] | ||
* | * [https://wiki.mozilla.org/Socorro:PRD_Interviews Interview notes summaries] | ||
= Features = | |||
== New / explosive crash tracking == | |||
* What date / buildid did a crash first occur? | |||
* When (date / buildid) did a crash spike in frequency? | |||
== Full text search == | |||
== Faceted search == | |||
Faceted search allows the categorization of a set of crashes along a pre-defined set of dimensions. Given a working dataset, which might be, for example, topcrashers for a particular build, a set of search results, or the set of crashes for a particular signature, users should be able to drill down through these crashes along various dimensions. | |||
=== Faceted signature search === | |||
Given a set of signatures (top crashers or search results), see them categorized and navigate by these categories. | |||
* Product version | |||
* Buildid | |||
* OS | |||
(Daniel: does this make sense, or do we just want the next one?) | |||
=== Faceted crash search === | |||
Given a set of crashes for a signature, see them categorized and navigate by these categories. | |||
Crashes that are gathered under a particular signature have already effectively been categorized under that signature. Other aspects of the crashes may differ, for example, the rest of the stack trace, operating system, loaded plugins, and extensions. | |||
Categories may include: | |||
* Product version | |||
* buildid | |||
* OS | |||
* Time since startup (<1, <5m, >5m) | |||
* Loaded plugins | |||
* Extensions | |||
* Stack frames (how to represent this?) | |||
* Address of crash | |||
Revision as of 18:41, 4 June 2010
DRAFT
The content of this page is a work in progress intended for review.
Please help improve the draft!
Ask questions or make suggestions in the discussion
or add your suggestions directly to this page.
Overview
In Socorro 1.7 we move to Hbase for storage, and in 1.8 we move the processors too and turn off throttling for good.
Socorro 2.x will allow us to take advantage of the capabilities of Hbase and pass those on to the end users.
Requirements Gathering
We interviewed Socorro users from the Firefox, Platform and QA teams, as well as Mozilla Messaging (for Thunderbird) about their current use of the product.
Features
New / explosive crash tracking
- What date / buildid did a crash first occur?
- When (date / buildid) did a crash spike in frequency?
Full text search
Faceted search
Faceted search allows the categorization of a set of crashes along a pre-defined set of dimensions. Given a working dataset, which might be, for example, topcrashers for a particular build, a set of search results, or the set of crashes for a particular signature, users should be able to drill down through these crashes along various dimensions.
Faceted signature search
Given a set of signatures (top crashers or search results), see them categorized and navigate by these categories.
- Product version
- Buildid
- OS
(Daniel: does this make sense, or do we just want the next one?)
Faceted crash search
Given a set of crashes for a signature, see them categorized and navigate by these categories.
Crashes that are gathered under a particular signature have already effectively been categorized under that signature. Other aspects of the crashes may differ, for example, the rest of the stack trace, operating system, loaded plugins, and extensions.
Categories may include:
- Product version
- buildid
- OS
- Time since startup (<1, <5m, >5m)
- Loaded plugins
- Extensions
- Stack frames (how to represent this?)
- Address of crash