Multi-dump support for Socorro storage - [tracker]

RESOLVED FIXED in 34

Status

Socorro
Backend
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: lars, Assigned: lars)

Tracking

unspecified
x86_64
Linux
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

6 years ago
the crash storage system will need to support multiple dumps per crash beginning in Q4
(Assignee)

Updated

6 years ago
Depends on: 807984, 807985, 807986
(Assignee)

Comment 1

6 years ago
bsmedberg: currently, when breakpad submits a crash to socorro via an HTTP POST, the dump is in a field called "upload_file_minidump".  What will be the names of the additional dump fields?  When referring to those other dumps throughout the socorro processing and display, will we use the same field names?  I ask because the original dump field name is awkward and not very descriptive in the context of a multidump crash.  We can either change that name, document a name mapping or refer to them by index.  I'm assuming that I'll be making a modification to the storage subsystem api (for use in the middleware, processor, etc) to fetch a dump by uuid and name/index. what's your preference?

Comment 2

6 years ago
See bug 784145 comment 0.

The current options for additional minidumps are "browser" on all platforms and "flash1" and "flash2" on Windows.
(Assignee)

Updated

6 years ago
Depends on: 816540
(Assignee)

Updated

6 years ago
Depends on: 816541
(Assignee)

Updated

6 years ago
Depends on: 816542
(Assignee)

Updated

6 years ago
Blocks: 816545
(Assignee)

Updated

5 years ago
Depends on: 721254
(Assignee)

Updated

5 years ago
Assignee: nobody → lars
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 31

Updated

5 years ago
Target Milestone: 31 → 32

Updated

5 years ago
Target Milestone: 32 → 33

Updated

5 years ago
Target Milestone: 33 → 34
You need to log in before you can comment on or make changes to this bug.