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

API requests taking 15 minutes or longer

api
welcome

#1

We are polling for New Relic Events, Incidents and Alert Violations. The polls are every 5 minutes, and we don’t receive any of the Overload (429) type of errors, nor do we get the Retry-After responses as described here. Yet these are taking upwards of 15 - 45 minutes to complete.

Queries use the public API’s. Here’s an example from our logs:

2020-01-30 14:55:00,002 INFO 244140371 HTTP REQ#327417563-366: HttpRequest(HttpMethod(GET),https://api.newrelic.com:443/v2/alerts_events.json,List(X-Api-Key: 123412, Cache-Control: no-cache),HttpEntity.Strict(none/none,ByteString()),HttpProtocol(HTTP/1.1))

2020-01-30 15:10:02,039 INFO 245042408 HTTP RSP#327417563-366: HttpResponse(200 OK,List(Proxied-By: Service Gateway, Content-Security-Policy: frame-ancestors *.newrelic.com, Cache-Control: max-age=0, private, must-revalidate, Date: Thu, 30 Jan 2020 15:10:01 GMT, ETag: "adfasf", Link: <https://api.newrelic.com/v2/alerts_events.json?page=2>; rel=next, <https://api.newrelic.com/v2/alerts_events.json?page=155>; rel=last, Server: nginx, Status: 200 OK, X-Rack-Cache: miss, X-Request-Id: asdfasd, X-Runtime: 1.469161, X-Ua-Compatible: IE=Edge,chrome=1),HttpEntity.Default(application/json,{"recent_events": [...]

This happens very often and is effecting our ability to provide up to date alerts to operations teams.


#2

Hi @clay4, would you mind sharing how you are making these API calls and the exact command they are using to make the calls? You can remove your API-key and any sensitive information.

Are you using a Proxy that would slow either the outbound request or the response coming back?


#3

Hi @clay4 - Just checking in to see if you had a chance to grab the info Ruairi was requesting?


#4

The command is equivalent to the following curl:

curl --request GET 'https://api.newrelic.com/v2/alerts_events.json' \
--header 'X-Api-Key: foo'

No proxy was used. This is running in an Azure cloud environment with direct access.

For the last 24 hours we were also seeing timeouts (both from Postman and also from The API Explorer page)

GET /v2/alerts_events.json HTTP/1.1
X-Api-Key: blah
User-Agent: PostmanRuntime/7.22.0
Accept: */*
Cache-Control: no-cache
Postman-Token: 3f3ac3b4-d068-48e5-a93f-90482065bd3a
Host: api.newrelic.com
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
HTTP/1.1 408 Request Timeout
Proxied-By: Service Gateway
Content-Security-Policy: frame-ancestors *.newrelic.com
Cache-Control: no-cache
Content-Type: application/json
Date: Thu, 06 Feb 2020 18:58:28 GMT
Server: nginx
Status: 408 Request Timeout
X-Rack-Cache: miss
X-Request-Id: 4dcc7b4d84367357727d02bc8c59f2d5
X-Runtime: 4.105091
X-Ua-Compatible: IE=Edge,chrome=1
content-encoding: gzip
transfer-encoding: chunked
{"error":{"title":"Resource timed out"}}

#5

I’m curious how many alerting events you have in your account?

It sounds like the API is taking a while pulling a lot of data?

I just ran the Alerts Events list API query on my account, with 50 events, and it returned all expected data in seconds.

Would you be able to try adding some filters to your API call like those below, in the hopes that it reduces the amount of data being fetched by the API;