This is a followup bug for bug #1604848 which added a throttling rule to reject all incoming crashes for SeaMonkey > 2.49.5.

This bug covers the rest of that roadmap towards ending support for SeaMonkey in Socorro.

Current plan:

August 2020:

• If SeaMonkey has had a release > 2.49.5 by then, we'll continue to accept crash reports for <= 2.49.5. We do not plan to forward crash reports to another system.
• If SeaMonkey has not had a release > 2.49.5, then we'll move SeaMonkey to the unsupported products list and reject all crash reports from that point going forward.

September 2020:

• If we haven't added SeaMonkey to the unsupported products list by this point, we will do so.
• We'll remove SeaMonkey-specific code from the rest of Socorro and remove crash report data from storage systems.

Bunch of things happened since we set the original plan.

The new plan is as follows:

March 2020:

• Remove existing collector throttle rules from previous plan (bug #1621033).
• Work out new schedule with SeaMonkey project.

October 2020:

• Check in with SeaMonkey project on progress towards switch crash ingestion systems.

July 31st, 2021:

• End support for SeaMonkey project in Socorro.
• Remove SeaMonkey as a supported project from collector.

January 2022:

• Any existing SeaMonkey crash report data expires from Socorro.
• Remove SeaMonkey as a supported project from processor and webapp.

How is this going? Does the SeaMonkey project have a plan for switching crash report ingestion, yet?

I haven't been involved with operation of the SeaMonkey project for 8-9 years now, but you included Ian and Edmund who AFAIK are still involved there.

Kairo: Sorry! The SeaMonkey About page says you're on the SeaMonkey council, so I needinfo'd you. I'll try to remember not to do that again.

In terms of transitioning, we would probably like to:

1. Change the endpoints in SeaMonkey to something *.seamonkey-project.org but have those redirecting to the mozilla crashreport servers
2. Set up and test our own crashreport servers
3. Switch off the redirect so it points to our servers

Which is probably similar to what TB would want to do, what I don't know is how / if the redirect would work without changes on the mozilla servers.

Thanks for the heads up. I've taken a look at this and I feel it's something we might be able to accomplish prior the removal of SeaMonkey from Soccorro and with TB being in the same boat, I might have a solution which could require a change in m-c. Will need to file a bug for this.

:willkg one minor point to make is that any old versions will still be trying to push crash stats to crash-stats.mozilla.com. I'm just hoping this won't become an annoyance. It'll be difficult to back-patch all versions out in the open.

We'll be removing SeaMonkey from the supported-products list in the collector, so it'll reject incoming crash reports from SeaMonkey. That should work fine from Socorro's side. There's no need to fix all the existing versions out there.

I'm checking in to see how this is going. Were you able to coordinate with the TB project and work out a plan?

I know ewong has been working on this and the related bug 1675676 (which also blocks TB) but the pandemic and other events have increased his workload outside of OSS so delayed things. I'll keep the NI against me so as to remind me to catch up with Edmund.

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #10)

I'm checking in to see how this is going. Were you able to coordinate with the TB project and work out a plan?

Hi Will.
Sorry, I haven't coordinated with the TB project. I'll see if I can ping someone on their project.

Hi! We're coming up on July 31st and I'm wondering how things are going. Are we still on schedule?

We're past July 31st now, so I'm going to start planning the work to shut off SeaMonkey crash ingestion.

Per the timeline in comment #2:

1. Very soon: Remove SeaMonkey from the list of supported products in the collector. After this change, incoming crash reports for SeaMonkey will be rejected. Crash reports that are already in Socorro will expire with the usual expiration of 6 months.
2. January 2022 or so: Remove any SeaMonkey-specific code from the rest of Socorro and remove SeaMonkey from the supported products in the webapp.

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #13)

Hi! We're coming up on July 31st and I'm wondering how things are going. Are we still on schedule?

:ewong has been setting up crash-upload, crash-stats and crash-reports servers. I know I have been submitting mini-dumps for him to test.

We were aiming to switch across to those servers in time for the 2.53.9 release which is due this month, but I believe there are still some issues to resolve on the server side, so it might now be the 2.53.10 release which is likely to come out in October.

It would be useful to have some more time to complete testing and migrate to the new servers.

I can move the date where we stop accepting crash reports for SeaMonkey to October 2021. So then the timeline would be like this:

1. October 2021: Remove SeaMonkey from the list of supported products in the collector. After this change, incoming crash reports for SeaMonkey will be rejected. Crash reports that are already in Socorro will still be available for viewing until they expire.
2. January 2022 or so: Remove any SeaMonkey-specific code from the rest of Socorro and remove SeaMonkey from the supported products in the webapp. Delete any remaining SeaMonkey crash reports from data stores that haven't expired, yet.

Does that work for you?

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #16)

I can move the date where we stop accepting crash reports for SeaMonkey to October 2021. So then the timeline would be like this:

1. October 2021: Remove SeaMonkey from the list of supported products in the collector. After this change, incoming crash reports for SeaMonkey will be rejected. Crash reports that are already in Socorro will still be available for viewing until they expire.
2. January 2022 or so: Remove any SeaMonkey-specific code from the rest of Socorro and remove SeaMonkey from the supported products in the webapp. Delete any remaining SeaMonkey crash reports from data stores that haven't expired, yet.

Does that work for you?

Hi, that should work. Is that 31st October for the first date?

My bad--I meant to be more specific. I was thinking October 31st, 2021.

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #18)

My bad--I meant to be more specific. I was thinking October 31st, 2021.

Looks perfectly reasonable. Thanks for the slight delay. Gives me a bit more time to work on getting things done.

:ewong

willkg merged PR #754: "bug 1608976: end collection of crash reports for SeaMonkey" in aab201b.

This ends crash collection for SeaMonkey crash reports. Landing this change will trigger an automatic deploy to the staging environment. I'll deploy it to production either today or tomorrow depending on how my day goes.

The next step will happen in January 2022 where we'll remove SeaMonkey crash reports from storage systems and remove SeaMonkey-specific supporting code from Socorro.

Ending crash collection was deployed just now to prod in bug #1741402.

I wrote up a bug for deleting crash data and removing support from the webapp. I think we're done here. Marking as FIXED.