Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Revert my Alerts back to your Legacy Alerting

rfb

#1

Please paste the permalink to the page in question below:

Please share your question/describe your issue below. Include any screenshots that may help us understand your question:

Hi, I need help to revert back to legacy alerting please


#2

Hi there, @ffeller! I can help you get rolled back! Thanks for letting us know—look out for my email. :e-mail:


#3

Hi, Could you please roll back my alerting system to legacy as well.

Kind Regards,
Sushma


#4

Hi @sushma -

Thanks for reaching out. Unfortunately, yesterday was the end of life for our legacy alerts tool and it is no longer available to customers. So I can’t get you rolled back. Here is the original communication about the End of Life, which contains some useful resources about new Alerts:

Important: Upcoming Changes for New Relic Servers and legacy alerting features

If you need to view your old alert policy configuration, our Alerts product team have enabled the API endpoint to list legacy alert policies for a short time. You can use the following cURL command to retrieve that information:

[grave accents]
curl -X GET 'https://api.newrelic.com/v2/alert_policies.json' \
-H "X-Api-Key:${APIKEY}" -i 
[grave accents]

#5

Hi @hross

I would like to be able to retrieve information from the legacy system but I am unable to. The API endpoint seems to be unavailable. When I try your curl command I get a message telling me that the API is deprecated:

$ curl -X GET 'https://api.newrelic.com/v2/alert_policies.json' -H "X-Api-Key:${APIKEY}" -i
HTTP/1.1 410 Gone                
Server: openresty                       
Date: Thu, 17 May 2018 17:47:31 GMT               
Content-Type: application/json                
Content-Length: 129
Connection: keep-alive
Status: 410 Gone
X-UA-Compatible: IE=Edge,chrome=1                                                                              
Cache-Control: no-cache   
X-Request-Id: d87ecda2e465a9831f4895dd500f53bb
X-Runtime: 0.061425                            
X-Rack-Cache: miss        

{"error":{"title":"The alert policies API is deprecated. Please see 'alerts.newrelic.com' for the new alerting infrastructure."}}

I did actually retrieve the alert policy information before the deadline however there is other information in the legacy system that I didn’t realise was going away an now I’m unable to retrieve it. In particular I am unable to access any the information from the notification channels. I need this information to be able to accurately recreate them in the new system:

$ curl -X GET 'https://api.newrelic.com/v2/alert_channels.json' -H "X-Api-Key:${APIKEY}" -i
HTTP/1.1 404 Not Found       
Server: openresty         
Date: Thu, 17 May 2018 17:49:14 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Status: 404 Not Found
X-UA-Compatible: IE=Edge,chrome=1
Cache-Control: no-cache
X-Request-Id: 44d013596d4650e7ca8df3451a1f6fa5
X-Runtime: 0.002786
X-Rack-Cache: miss

Would it be possible to have this re-enabled please?


#6

Hi @derby - We did some looking on our end. Looks like we needed to flip an additional switch for this, but we think it should be open now. Would you mind trying this again and letting us know if you are more successful?


#7

Thank you @hross. I can now access alert_policies.json however I am still unable to access alert_channels.json:

$ curl -X GET 'https://api.newrelic.com/v2/alert_channels.json' -H "X-Api-Key:${APIKEY}" -i

HTTP/1.1 404 Not Found
Server: openresty
Date: Thu, 17 May 2018 22:07:13 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Status: 404 Not Found
X-UA-Compatible: IE=Edge,chrome=1
Cache-Control: no-cache
X-Request-Id: cc26e16cf261c878b79639357c97714c
X-Runtime: 0.002789
X-Rack-Cache: miss

Not Found

servers.json is also unavailable but has a different HTTP response:

$ curl -X GET 'https://api.newrelic.com/v2/servers.json' -H "X-Api-Key:${APIKEY}" -i                                                 
HTTP/1.1 200 OK
Server: openresty
Date: Thu, 17 May 2018 22:07:29 GMT
Content-Type: application/json
Content-Length: 85
Connection: keep-alive
Status: 200 OK
X-UA-Compatible: IE=Edge,chrome=1
ETag: "e3d8f90dfb734cf8ed230c697a93f073"
Cache-Control: max-age=0, private, must-revalidate
X-Request-Id: 9f0c250489ebb01ef455f43c0748f3de
X-Runtime: 0.054900
X-Rack-Cache: miss

{"servers":[],"links":{"server.alert_policy":"/v2/alert_policies/{alert_policy_id}"}}

#8

Hey @derby - So sorry that this has not been more smooth! alert_channels.json is enabled now as well.


#9

Thanks @hross but I’m still getting the same 404:

$ curl -X GET 'https://api.newrelic.com/v2/alert_channels.json' -H "X-Api-Key:${APIKEY}" -i
HTTP/1.1 404 Not Found
Server: openresty
Date: Fri, 18 May 2018 18:51:06 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Status: 404 Not Found
X-UA-Compatible: IE=Edge,chrome=1
Cache-Control: no-cache
X-Request-Id: ed7ec04a666765cbec8f9face65c197b
X-Runtime: 0.005367
X-Rack-Cache: miss

Not Found

#10

I should have had someone test. I am sorry if this is frustrating. Let me go back to the team again for you…


#11

Hi @derby,

I think you may be using the incorrect endpoint. Try using https://api.newrelic.com/v2/notification_channels.json instead, so that your curl command would look like:

curl -X GET 'https://api.newrelic.com/v2/notification_channels.json' -H 'X-Api-Key:${APIKEY}' -i

Let us know if this is still not working for you!


#12

Hi @Fidelicatessen, @hross

That’s much better. I’ve now got the information I need.

Thank you both very much for all your help!