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)

task
Not set
major

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
Tasos or Nemo, any idea what is causing the tracebacks?
Flags: needinfo?(tasos)
Flags: needinfo?(jgiannelos)
(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.
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.
Depends on: 1069346
Flags: needinfo?(jgiannelos)
:nemo are you working on this?
Flags: needinfo?(tasos)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Verified FIXED; thanks (from bug 1069346).
Status: RESOLVED → VERIFIED
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.