E2M (Events-2-Metrics) authorization issues
Jul 17, 10:21 UTCJul 17, 10:21 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
New Relic, 90 days
12 incidents
Affected
APM : USAPM : EuropeAlerts : USAlerts : EuropeAPM : JPAlerts : JPUI : US - Alerts : USAlert Notifications : US - APM : USUI : Europe - Alerts : EuropeAlert Notifications : Europe - APM : EuropeAlert Notifications : JP - APM : JPUI : JP - Alerts : JP
Final update
Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put in place. The issue is now resolved, and the impacted services have returned to normal service.
Timeline
- Resolved · Jul 17, 10:21 UTC
Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put in place. The issue is now resolved, and the impacted services have returned to normal service.