Closed
Bug 1255456
Opened 9 years ago
Closed 9 years ago
Make the new Heroku MemCachier instances report to New Relic
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P3)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
The MemCachier integration with New Relic isn't working for the new Heroku apps.
So I've filed:
https://memcachier.zendesk.com/requests/1358
"""
I've had New Relic reporting set up successfully for this Heroku app that uses the Memcachier addon:
https://analytics.memcachier.com/REDACTED
However, when I added the same New Relic license key to two new Heroku apps:
https://analytics.memcachier.com/REDACTED
https://analytics.memcachier.com/REDACTED
...I don't see any additional instance rows in the table on New Relic:
https://rpm.newrelic.com/accounts/677903/plugins/17846
...just the one existing "MemCachier Cache".
I'm guessing the problem is either:
(a) enabling the New Relic integration wasn't successful on those new instances, even though the Memcachier page confirmed the setting of the license key
(b) all of the Memcachier instances are reporting under the same "MemCachier Cache" name, thereby overwriting each other
"""
Assignee | ||
Comment 1•9 years ago
|
||
Their reply:
"""
I believe (b) is exactly what's going on. The New Relic API (as we understand it at least) doesn't give us a way to post data for different resources with the same newrelic API key. I'll look into their API again to see what we can do, though.
Thanks for bringing this to our attention,
"""
My reply:
"""
...
If it helps at all, MemCachier's New Relic integration is able to report each instance separately (see screenshot), so hopefully the API should support it?
Many thanks,
"""
Assignee | ||
Comment 2•9 years ago
|
||
Their reply:
"""
Sorry for the long delay on this. We've got a fix in the work but it will take a little time as we need to modify a few different layers of our system to pass around a cache name. The 'actual' fix is one line, but we just don't know the cache name at that point usually.
However, we've just pushed out a temporary fix that should work for you specific setup. You should now see three caches showing up in newrelic using the names you've set for the apps in Heroku. Please let us know if it works or doesn't.
"""
My reply:
"""
I've just checked NR and the temporary fix is working well :-)
Many thanks for the update & working on this!
"""
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•