To ensure our systems are always up and ready to support you, and to keep you from unintended use, we place limits on the amount of data you can send, query, and store.
To find the limits UI: from the account dropdown, click Manage your data and click Limits.
This UI displays information about how close an account is to hitting rate limits (both data ingest-related limits and query limits), and violations of those limits. The data displayed here is generated from:
The limits UI displays information related to an account's data ingest rate and query rate, and violations of limits.
What the color-coding in the violation table means:
- Red: exceeded a limit
- Yellow: 80-100% of a limit
- Green: below 80%
- Gray: limits that don't have reported usage or violations for the given time range
Some tips on using the limits UI:
- To get more detail about a table entry, try clicking it. Some entries have more detail, including associated NRQL queries.
- When you select a time range greater than six hours, the chart uses average values, which may smooth out spikes. This is the reason you may see the message "For the time window chosen, the 'Max limit usage' value represents the average of your usage limits." To see more accurate results, use a time range below six hours.
- It's possible for the use of a resource to be over a limit while not generating a violation. For example, query limit events are generated for a one-minute level, but violations are only generated for continually exceeding that limit at the 5-minute level.
If you want more detail than the UI provides, see Query your resource use.
Limits are enforced per account (not per organization). You might reach a limit if you start monitoring a new high-traffic application, or have a sudden data spike. When you do reach a limit, New Relic responds according to the type of data and the limit that's reached. Some examples of responses:
- We place a limit on the number of ingested requests per minute (RPM) per data type. When this limit is reached, we stop accepting data and return a 429 status code for the duration of the minute.
- For queries, we place limits on the number of queries per minute and the number of records inspected (see query limits). When the number of queries per minute limit is reached, New Relic will begin rejecting queries until the number of queries is below the limit. When the records inspected limit is reached, New Relic will reject traffic from the source scanning the largest number of records and attempt to allow traffic from other sources.
- For metrics, we place a limit on the number of unique timeseries (cardinality) per account and per metric. When this limit is reached, aggregated data is turned off for the rest of the UTC day.
For every major limit violation, New Relic creates an
NrIntegrationError event for that account, which has these limit-related attributes:
The name of the limit.
Describes the limit and the impact.
The limit reached.
This table includes general max limits that apply across all New Relic accounts. Specific New Relic tools, like agents and integrations, have their own limits and configurations, and those limits will sometimes be lower than these theoretical account-level maximum limits.
Rate of NRDB record* ingest
55 million per account per minute
Max NRDB records* ingested per API call
1MB (10^6 bytes)
Max attribute value size
1KB (10^3 bytes)
Max attribute name length
Max attribute value length
Metric, Trace, and Event API: 4096 characters. Log API: 4094 characters.
Max payload size
1MB (10^6 bytes)
Max total attributes per data type (including default attributes)
254 (less for some tools; for example, 64 for agents)
250 (primarily a limit for custom events)
Browser: number of page views
1M per minute per app
Rate of metric timeslice data (used by APM, browser, mobile)
See Trace limits.
Infrastructure agents, integrations
Mobile monitoring: number of crashes reported
10K per hour
See synthetics limits.
* NRDB records refers to database records for our core data types, which includes events, metrics (dimensional), logs, and distributed tracing (span) data, all stored in the New Relic database (NRDB). This does not include metric timeslice data.
Our ingest APIs have additional limits that may override the more general account-level limits. Note that these limits also apply for our tools that use these APIs.
To find limits for our other agents and integrations, which will override more general account-level limits, see the docs for those tools: you can search our quickstarts here. Some default reporting limits are located in these tools' configuration docs.