Closed
Bug 1307417
Opened 8 years ago
Closed 8 years ago
ATMO V2: Enable NewRelic for atmo.dev.mozaws.net
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jezdez, Unassigned)
References
Details
(Whiteboard: [SvcOps])
To better understand what is happening on the staging (and later prod) nodes we need access to a monitoring solution such as New Relic. While bug 1305042 covers system level log files, an application monitoring system that handles the various parts of the ATMO stack would improve the monitoring coverage. There seems to be a NewRelic app set up for ATMO V2 (https://rpm.newrelic.com/accounts/263620/applications/17103346) but no reporting is happening. It's not clear what the issues are that prevent it from working.
Updated•8 years ago
|
Whiteboard: [SvcOps]
Comment 1•8 years ago
|
||
Wontfix as we are moving to Heroku for the time being.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•