Closed Bug 1186482 Opened 10 years ago Closed 10 years ago

[tracker] deprecate /explosive/

Categories

(Socorro :: Webapp, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lonnen, Assigned: peterbe)

References

Details

Attachments

(1 file)

Our explosive report has never been particularly useful, and represents an insignificant amount of site traffic. Lets remove it and associated functionality.
Yes, we want an explosiveness report but the one we have isn't it.
Assignee: nobody → peterbe
Blocks: 1230314
Depends on: 1230316
Kairo, To my unamazement but sadness I noticed that the webapp report is called "explosive", but when it talks to the middleware and postgresql it's called "suspicious". There's a crontabber job that reads from reports_clean and writes to a table called suspicious_crash_signatures. So far so good. But there's a something else called "explosive" (and "explosiveness") in the postgres-land. In particular this beast: https://github.com/mozilla/socorro/blob/master/socorro/external/postgresql/raw_sql/procs/update_explosiveness.sql What on earth is that?!! Can we delete that too from the tangled stored procedure mess.
Flags: needinfo?(kairo)
Blocks: 1231672
I chatted to Kairo. All of those stored procedures can be deleted. Hence https://bugzilla.mozilla.org/show_bug.cgi?id=1231672
Flags: needinfo?(kairo)
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/652d5a447790995652841378d80a308abcc95493 fixes bug 1186482 - deprecate /explosive/, r=AdrianGaudebert https://github.com/mozilla/socorro/commit/936bde974320252879b0ba2f16734c3fc938e1ab Merge pull request #3130 from peterbe/bug-1186482-deprecate-explosive fixes bug 1186482 - deprecate /explosive/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: