change stage submitter to trigger on v2/raw_crash/
Categories
(Socorro :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
Details
Attachments
(1 file)
Back in the day, we had Pigeon which triggered on S3 save events in v2/raw_crash/, so we had to make the stage submitter trigger on S3 save events in v1/processed_crash/. In April 2019, we reworked the collector so that it sent crash ids directly to Google Pub/Sub so we didn't need Pigeon anymore and we disabled it.
That allows us to switch the stage submitter to trigger on S3 save events in v2/raw_crash/. Doing this will eliminate the current problem we have where if we reprocess lots of crash reports in prod, it sends 1/10 of those to stage and that kicks up alerts in stage about the queue being too long.
This bug covers switching stage submitter to trigger on v2/raw_crash/.
|
Assignee | |
Comment 1•6 years ago
|
||
Making this a P2 to do soon. This fixes some issues and it'll be good to clean this up before we go on hiatus.
|
|
Assignee | |
Comment 2•6 years ago
|
||
|
|
Assignee | |
Comment 3•6 years ago
|
||
willkg merged PR #15: "bug 1568977: change to trigger on v2/raw_crash/" in 55c5d31.
We'll need to push this to prod and have ops change how it gets triggered. Keeping this open for that work.
|
|
Assignee | |
Comment 4•6 years ago
|
||
I tagged socorro-submitter with 3 and pushed that out. Miles adjusted things in AWS. Looks like we're good here!
Description
•