Closed
Bug 1270460
Opened 8 years ago
Closed 8 years ago
Configure New Relic for the new Heroku stage/prod instances
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P2)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
The following will need to be set up via the web UI: * Application configuration * Alert policy groups * Alerts for plugins The apps can't be added/configured until the Python agent first reports (deploys don't create a new app).
Assignee | ||
Comment 1•8 years ago
|
||
Whilst we don't yet have accessible DBs for stage/prod, I've deployed bug 1270454 which allows us to skip the migration steps (that were blocking deploys) and have increased the web dyno count on stage/prod to 1. Visiting the app loads the static assets (even if the API calls fail), causing reports to be sent to New Relic, creating the app. I've configured stage/prod to match the existing configs (and namespaced the SCL3 vs Heroku apps): Existing stage: https://rpm.newrelic.com/accounts/677903/applications/5585473/edit Existing prod: https://rpm.newrelic.com/accounts/677903/applications/4180461/edit New stage: https://rpm.newrelic.com/accounts/677903/applications/14179733/edit New prod: https://rpm.newrelic.com/accounts/677903/applications/14179757/edit The new apps are now appearing on: https://rpm.newrelic.com/accounts/677903/applications
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•