New Relic places limits on the amount and rate of data that accounts can store and report. This resource lists the default account-level data usage limits.
Why it matters
We understand that your configuration or other errors may cause your account to exceed these limits. But when this happens, your account, or any of your user accounts or sub-accounts, may experience one or both of the following:
- Sampling of data
- Temporary pause or cessation of data collection
To prevent data usage spikes from impacting other accounts, New Relic reserves the right to enact these policies. If you have questions about these default limits or your contract, contact your New Relic account representative.
All New Relic products data usage limits
Additional data usage limits apply to specific products. For more information, see the product section in this document.
| All New Relic products | Limit |
|---|---|
| Rate of event ingest per account | 5M per minute |
| Rate of timeslice metric ingest per account | 2M per minute |
| Max payload size | 1MB (10^6 bytes) |
| Max events per API call | 1K |
| Max total attributes per event | 254 (64 for events via agents) |
| Max attribute value size | 1 KB |
| Number of unique custom event types per account per day | 250 |
| Number of timeslice metric names per account | 4M |
| Number of timeslice metrics per application | 300K |
Metric data usage limits
Additional data usage limits apply to specific products. For more information, see the product section in this document.
| Metrics | Limit |
|---|---|
| Rate of dimensional metric ingest per account | The default per minute metric ingest rate limit is 3x the purchased monthly average data points per minute, up to a maximum of 15M. |
| Maximum dimensional metric cardinality per account (Note that cardinality means the number of unique metric timeseries) | The default account-level metric cardinality limit is 3x the purchased monthly average data points per minute, up to a maximum of 15M. |
| Rate of dimensional metric API POST requests per account | 10K |
Trace data usage limits
Additional data usage limits apply to specific products. For more information, see the product section in this document.
| Traces | Limit |
|---|---|
| Spans saved per minute sent to the Trace API. Applies to the account family. |
The default span per minute rate limit is 3x the monthly purchased span amount and is calculated as: (number of monthly purchased spans / 750 hours / 60 minutes) * 3 Up to a maximum of 2M spans per minute per account family. |
APM data usage limits
In addition to the data limits described in this document for all products, these data limits apply to APM.
| APM feature | Limit |
|---|---|
| Number of APM agent instances per account | 50K |
| Number of APM applications per account | 10K |
| Number of agent instances per application | 10K |
Browser data usage limits
In addition to the data limits described in this document for all products, these data limits apply to Browser.
| Browser feature | Limit |
|---|---|
| Number of Browser page views per minute per monitored app | 1M |
Infrastructure data usage limits
In addition to the data limits described in this document for all products, these data limits apply to Infrastructure.
| Infrastructure feature | Limit |
|---|---|
| Number of Infrastructure agents and Infrastructure integrations per account | 5K agents per account |
| Gross number of new monitored containers (Infrastructure agents) per hour per account | 5K agents per account |
Query data usage limits
In addition to the data limits described in this document for all products, these data limits apply to Insights.
| Insights feature | Limit |
|---|---|
| Query events inspected per account | 100B per hour |
| Rate of queries per account | 20 per second |
Mobile data usage limits
In addition to the data limits described in this document for all products, these data limits apply to Mobile.
| Mobile feature | Limit |
|---|---|
| Number of mobile crashes reported per hour | 10K |