Let's push errors and logs to Sentry. We'll need to wait until we move to scl1 and then get Sentry set up there. I'm blocking this on bug 749789 for now, but that might get split up to a separate bug for scl1, in which case, this will depend on the new bug.
If we want to do this sooner we can try Arecibo while we wait for Sentry: http://mozweb.readthedocs.org/en/latest/errors.html?highlight=arecibo
Marking as P1, but not a blocker. If the number of notifications does not turn out to be overwhelming, we can take a look at reducing the priority.
Priority: -- → P1
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
Luke mentioned that this requires coordination with IT. Anything I can do?
We're just waiting on bug 749789.
Also, I'm working on Arecibo since we can do that now. We just need something better than emails.
Summary: Add Sentry error handling → Add Arecibo error handling
(In reply to Luke Crouch [:groovecoder] from comment #6) > Also, I'm working on Arecibo since we can do that now. We just need > something better than emails. Removing bugs 749789 and 750248 from the blockers, then, and filing a new bug. You'll probably need a new net flow opened to Arecibo.
Removing the s= tag to work around Scrumbugs issue 99: https://github.com/mozilla/scrumbugz/issues/99
Whiteboard: p=3 s=2012-10-16 → p=3
Component: Landing pages → Other
Whiteboard: p=3 → p=3 c=Other
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 795356
You need to log in before you can comment on or make changes to this bug.