Closed Bug 1291218 Opened 9 years ago Closed 9 years ago

CloudAMQP instances no longer reporting to New Relic

Categories

(Tree Management :: Treeherder: Infrastructure, defect, P2)

Product:
Tree Management
Component:
Treeherder: Infrastructure
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

The prototype/stage/prod Heroku apps' CloudAMQP instances have stopped reporting here: https://rpm.newrelic.com/accounts/677903/plugins/17459 Seems to have occurred around the same time as the password rotation, though unlike the log errors from the other rabbitmq plugins, wasn't fixed by restarting the CloudAMQP node. Have included this in the email to CloudAMQP support sent in bug 1286702 comment 8.
Assignee: nobody → emorley
CloudAMQP have: * restarted the agents for me * found the bug which prevented "enable" / "disable" from doing so, so next time we should be able to self-serve In addition, I've found that the RabbitMQ admin panel has a "cluster name" setting, which can be altered from the unhelpful defaults of eg "yellow-swan" to more helpful names like "treeherder-{stage,prod}", which is then what is displayed in New Relic: https://rpm.newrelic.com/accounts/677903/plugins/17459
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Blocks: 1255460
You need to log in before you can comment on or make changes to this bug.