Closed
Bug 963341
Opened 11 years ago
Closed 11 years ago
Hook up New Relic's Python/Django agent to Mozilla Reps
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
It'd be great if we could get New Relic integrated into the Mozilla Reps website, to help with bug 962301 and other potential issues.
Comment 1•11 years ago
|
||
Hi :stephend,
We already have New Relic integrated in reps.mozilla.org.
The reason we don't have new relic support for the stage/dev
deployments is that they are hosted in the old atom infrastructure.
Comment 2•11 years ago
|
||
(In reply to John Giannelos [:nemo] from comment #1)
> We already have New Relic integrated in reps.mozilla.org.
> The reason we don't have new relic support for the stage/dev
> deployments is that they are hosted in the old atom infrastructure.
Thanks for the explanation nemo! Moving the site to the new infrastructure is tracked in bug 964320.
Depends on: 964320
Comment 3•11 years ago
|
||
This is now fixed.
https://rpm.newrelic.com/accounts/263620/applications/2836810
https://rpm.newrelic.com/accounts/263620/applications/3650909
https://rpm.newrelic.com/accounts/263620/applications/3689774
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•5 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
•