Status

Infrastructure & Operations
WebOps: IT-Managed Tools
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: ericz, Assigned: ericz)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3195])

(Assignee)

Description

a year ago
Our New Relic reporting script recently stopped working saying an API key is invalid.

Updated

a year ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3195]
(Assignee)

Comment 1

a year 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
Last Resolved: a year ago
Resolution: --- → FIXED
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

a year 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
Last Resolved: a year agoa year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.