New Relic's query language, NRQL, has rate limits in place to ensure a high level of availability and reliability for all users. To understand the places NRQL can be used, see Where is NRQL used?.
You will rarely encounter rate limiting, especially if you follow these general guidelines:
- Limit the amount of requests with complex queries (for example, queries with
TIMESERIESclauses, or queries of over a million events) that run at the same time.
- Limit the amount of requests run concurrently over extended periods of time to a maximum of 5, especially if they include complex queries.
Limits on queried events
When you run a NRQL query, it will display the number of events inspected, as shown below:
In this context, "events" is used in a general sense to refer to all NRQL-available objects; this includes events, metrics, logs, and distributed tracing (span) data.
Each New Relic account has limits on the total number of events that can be inspected. There are limits that apply over two different time frames:
- A rolling 30-minute time window
- A 24-hour period
These limits are as follows:
|Rolling 30 minutes||600 billion events inspected (equivalent to a sustained rate of 20 billion events inspected per minute)|
|24 hours||7.2 trillion events inspected|
Once the limit has been reached for a given time period, limiting will be imposed and some queries may be impacted. After the time period has passed, if query volume drops below the limit, restrictions will be removed automatically.
NRQL query rate limits
The limit on NRQL queries is 50 queries per second, or 3000 queries per minute. Past this, New Relic cannot guarantee query performance, and you may be rate limited.
Limits on count of data types
The limit for total number of reported data types is 250 per account over a given 24-hour time period. If a user exceeds this limit, New Relic may filter or drop data.