Closed
Bug 1068090
Opened 10 years ago
Closed 10 years ago
Investigate/fix New Relic for Reps - Python tracebacks/exceptions aren't showing up
Categories
(Mozilla Reps Graveyard :: reps.mozilla.org, task)
Mozilla Reps Graveyard
reps.mozilla.org
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stephend, Unassigned)
References
()
Details
Bug 860266 and bug 963341 sought to set up New Relic for Reps, but even though there's a traceback/500 error [1] currently on dev, it's not showing up [2] [1] https://reps-dev.allizom.org/e/new-event-181/ [2] https://rpm.newrelic.com/accounts/263620/applications/3650909/traced_errors
Comment 1•10 years ago
|
||
Tasos or Nemo, any idea what is causing the tracebacks?
Flags: needinfo?(tasos)
Flags: needinfo?(jgiannelos)
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to William Reynolds [:williamr] from comment #1) > Tasos or Nemo, any idea what is causing the tracebacks? Let's deal with the tracebacks in their respective bugs bug 1068092, bug 1066332 -- I'm interested here in finding out why/fixing that they don't currently show up in New Relic.
Comment 3•10 years ago
|
||
It seems like we are not reporting any data from reps-dev.m.o instance to New Relic since 28 July 2014. Stage and prod are working as expected.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•10 years ago
|
||
Verified FIXED; thanks (from bug 1069346).
Status: RESOLVED → VERIFIED
Updated•4 years ago
|
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•