Closed
Bug 1223062
Opened 9 years ago
Closed 9 years ago
Remove Pingdom RUM monitoring
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: peterbe, Assigned: peterbe)
Details
Attachments
(1 file)
If we disable the ID from consulate will remove the insertion of the javascript snippet.
Leaving the functionality (ability to set it up again) in is cheap and might be useful.
Assignee | ||
Comment 1•9 years ago
|
||
Any opinions on the need to remove the functionality altogether. Personally I vote we just leave it in for now and just remove the ID from consulate.
Assignee: nobody → peterbe
Flags: needinfo?(chris.lonnen)
Comment 2•9 years ago
|
||
It's a trap!
(Hint: you're the one who taught me not to leave unused code in a code base :) )
Assignee | ||
Comment 3•9 years ago
|
||
It's removed from prod and stage now.
Actually, Adrian is right. I did pontificate that.
If other organizations worry so much about uptime and performance of their socorro webapp, they probably don't use our webapp.
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(chris.lonnen)
Assignee | ||
Comment 4•9 years ago
|
||
Assignee | ||
Comment 5•9 years ago
|
||
JP, take heed. We're dropping it. It's out of policy and it would only give us web page monitoring. Something like New Relic will give us information about any type of request to the web app. In particular we'll be able to see how our public web API is doing and being used.
Remember, we still have an **uptime monitoring** on the home page.
Comment 6•9 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/96a2c23efd8a0519d49e016b1d76abedcb3562df
fixes bug 1223062 - Remove Pingdom RUM monitoring
https://github.com/mozilla/socorro/commit/9891947798afc3e64e63b79b79be2431c7517df4
Merge pull request #3086 from peterbe/bug-1223062-remove-pingdom-rum-monitoring
fixes bug 1223062 - Remove Pingdom RUM monitoring
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•