Closed
Bug 2053871
Opened 2 months ago
Closed 7 days ago
Add support for a new SubmissionType field to Socorro
Categories
(Socorro :: General, task, P1)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bdanforth, Assigned: sven)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [cringe])
Attachments
(1 file)
SubmissionType is how we will differentiate a Crash Ping from a Crash Report in Socorro. Unlike CrashEventID and StackTraces, it is not a crash annotation. It will be set by Antenna at ingest time based on which submission path the crash data arrived through. It is an enum with a value of either "ping" or "report".
From the processor side, this will look similar to Bug 2053525.
Acceptance criteria:
- Add SubmissionType to the raw and processed crash schemas as a public field.
- Description should clarify that the field is added by Antenna; it is not a Crash Annotation. Defaults to
"report"if the field is omitted.
- Description should clarify that the field is added by Antenna; it is not a Crash Annotation. Defaults to
- Ensure its value is copied over into the processed crash report during processing.
- We have an existing
CopyFromRawCrashrule, so I don't think we need a new processor rule to cover this.
- We have an existing
- Ensure it's searchable by indexing it in Elasticsearch (i.e. adding it to SUPERSEARCH_FIELDS).
- Unit tests as appropriate.
Updated•2 months ago
|
| Assignee | ||
Comment 1•14 days ago
|
||
Assignee: nobody → sven
| Assignee | ||
Comment 2•7 days ago
|
||
This was deployed to production in https://github.com/mozilla-services/socorro/releases/tag/v2026.09.16. I verified that all newly processed crashes have a submission_type field in the processed crash with value report.
Status: NEW → RESOLVED
Closed: 7 days ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•