Closed
Bug 1286572
Opened 8 years ago
Closed 8 years ago
NewRelic API key failing
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ericz, Assigned: ericz)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3195])
Our New Relic reporting script recently stopped working saying an API key is invalid.
|
Assignee | |
Comment 1•8 years ago
|
||
The Marketing account's API key changed, I updated puppet with the new value, verified it works and re-ran the script/email.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Comment 2•8 years ago
|
||
Apologies for the lack of cross-team communication and coordination there. Will you please update the key in the server configs for sumo and mdn as well?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
|
Assignee | |
Comment 3•8 years ago
|
||
We did some digging and the New Relic agents appear to authenticate with a "license key" which was not changed like the "API key" was. Therefore, we don't know why we saw the failure and then recovery. New Relic has not said there was any outage on their side. Possibly it was a temporary outbound proxy issue in scl3 as nothing in AWS was affected.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•