Socorro:Planning 2.0: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
** Correlations? | ** Correlations? | ||
** Trends? | ** Trends? | ||
* What cron/offline reports would be interesting? | |||
** Sudden crash patterns (How do we detect them)? | |||
** Alerts via SMS on above crash patterns? | |||
** Nightly report showcasing top DLL crashes with trends? | |||
** Number of crashes based on geo? | |||
** Other metrics? | |||
* What else? | * What else? | ||
** What is an acceptable time lag between actual and processed crash? i.e. do you need the crashes analyzed in real-time, near real-time or within few hours? | |||
Latest revision as of 15:15, 12 May 2010
Goals
- Better, more useful search
- (2.x) Better correlations
- (2.x) Trend reports
- (Future) Data mining
Existing bugs
User questions
- Do you use Socorro now?
- If not why not?
- What reports do you use, and how? (Use cases)
- How do you currently use search?
- Do you use the CSV files?
- Do you generate any personal reports or analyses?
- What would you like to be able to do from the UI?
- What queries?
- What graphs?
- Search?
- Correlations?
- Trends?
- What cron/offline reports would be interesting?
- Sudden crash patterns (How do we detect them)?
- Alerts via SMS on above crash patterns?
- Nightly report showcasing top DLL crashes with trends?
- Number of crashes based on geo?
- Other metrics?
- What else?
- What is an acceptable time lag between actual and processed crash? i.e. do you need the crashes analyzed in real-time, near real-time or within few hours?