Important
This doc applies for organizations on our original pricing model. If you're on our usage-based pricing model, see Manage your data. Not sure which you're on? See Overview of pricing models.
New Relic stores different types of data for different periods of time. The retention period for a type of data will vary depending on the product, the subscription level, and the feature.
Data retention UI
The best way to understand your data retention and see what options are available is to go to the UI. One reason this is recommended is because your organization may have edited your settings and they may no longer be the default settings documented here.
The Data retention UI page is located in the Data management hub. Adjust retention values by clicking Edit retention.
Limits on editing and deleting data
Once you report telemetry data (events, metrics, logs, traces) to New Relic and it's available for querying, you can't edit or delete that data. This is a purposeful design decision that optimizes New Relic's speed and performance. Data will expire after its data retention ends.
If you send unwanted or sensitive data to New Relic, contact your account representative or get support at support.newrelic.com to remove it.
Product and API data retention policies
Select a New Relic product to see details about its data retention:
Specific retention policies apply to each subscription level, including Lite, Essentials, Pro, and Enterprise. This includes metric timeslice data, key metrics, trace data, and event data. In addition to retention limits, your data is subject to aggregation (averaging) after certain elapsed time periods. For more information, see the aggregate metric data description.
APM data retention policies
For accounts on our original pricing model, APM data retention policies depend on your APM product subscription level.
Component | Lite | Essentials | Pro |
---|---|---|---|
Metric timeslice data | 24 hours | 3 days | 90 days |
Key metrics | none | forever | forever |
Distributed tracing and logs in context | none | none | 8 days |
Other trace data * | 1 day | 3 days | 7 days |
Event data ** | 1 day | 3 days | 8 days |
* If you view a transaction trace in the New Relic UI, New Relic stores that trace data for up to one year.
** Learn about how to extend the retention of event data.
Legacy APM data retention policies
Component | Standard | Startup | Small Business | Enterprise |
---|---|---|---|---|
Metric timeslice data | 7 days | 14 days | 30 days | 90 days |
Key metrics | none | none | none | forever |
Trace data | 7 days | 7 days | 7 days | 7 days |
Event data | none | 8 days | 8 days | 8 days |
For organizations on our original pricing model, data is stored depending on your subscription level:
Component | Lite | Pro |
---|---|---|
Metric data | 24 hours | 90 days |
Key metrics | 24 hours | forever |
Trace data | 7 days | 7 days |
Event data * | 1 day | 8 days |
SPA data | Unavailable | 8 days |
* Learn about how to extend the retention of event data.
For organizations on our original pricing model, Infrastructure data retention policies depend on your Infrastructure subscription level and your infrastructure compute units pricing model. The data retention rules apply the same way whether displaying that data in the UI or querying it.
Tip
Infrastructure data retention policies are separate from your Insights subscription.
Infrastructure downsampling and data retention
Depending on your subscription level, how we store data varies:
Component | Essentials | Pro |
---|---|---|
Infrastructure data | 3 months | 13 months |
Host count Host count will stop reflecting a host whose agent is no longer reporting after three minutes. However, host data will be available, subject to other retention criteria. | 3 minutes | 3 minutes |
Inventory attributes removed Inventory attributes for a host are retained for 24 hours after the agent stops reporting. | 24 hours | 24 hours |
Integration data | Not available with Essentials | Limit of 2275 integration events per compute unit per month |
In addition, infrastructure monitoring downsamples your data as it's ingested. All infrastructure metric data types (including on-host integrations metrics) will display different granularity depending on the age of the data and the size of the time window. The table below shows when we will use different downsampled buckets. We will use them in the Infrastructure UI and for queries.
Bucket Size | Used For Time Windows Covering... | Data Retained For... |
---|---|---|
Raw (5, 10 or 15 second) | 0 to 59 minutes | 7 days |
1 minute | 60 minutes to 6 hours | 30 days |
10 minutes | 6 hours to 3 days | Full account retention period |
1 hour | 3 days to 14 days | Full account retention period |
3 hours | 14+ days | Full account retention period |
Integration compute unit event limits
The 2275 limit on integration events per compute unit per month is a limit on total Infrastructure integration events. It's not a limit of 2275 for each integration's events.
Additional details and clarifications about this limit:
- This limit applies to all events from all integrations (cloud integrations and on-host integrations). The events are all handled the same.
- Default data received by the Infrastructure agent doesn't count against the 2275 event per compute unit limit.
- If you exceed your limit, we don't enforce this limit. If you exceed your limit, we'll review pricing options with you to ensure you get the most cost-effective pricing for your organization's integrations.
For organizations on our original pricing model, a paid Insights subscription is what governs the extension of event data retention for:
Our APM, Browser, Mobile, and Serverless products
Custom events that come from an agent API or from the Event API
To see the data retention governed by your Insights subscription: go to the usage UI and select Insights usage.
With an Insights Pro subscription, you can use flexible retention to customize how long your event data is retained. This lets you keep only the data you need, for as long as you need it.
This is an explanation of how the number of stored events are calculated by default for an Insights Pro subscription. (Note that with flexible retention, you have more fine-grained control over the retention period.)
The events stored is calculated based on 1) total events stored over time (calculated based on the events generated per week) and 2) the weeks of data retention available. This is how you can represent this equation:
events stored = (events generated per week) * (weeks of retention)An Insights Pro subscription provides a given number of weeks of data retention as well as a given number of events over that retention period.
For example:
- (200M transactions per week) * (4 weeks of retention) = 800M events stored in Insights
- (16M transactions per week) * (50 weeks of retention) = 800M events stored in Insights
With Insights Pro subscriptions, we purge data based on the retention window, not volume. We delete it once it's past the retention window.
For example: If your Insights license is for 800 million events with a 4 week retention period, your data would start being purged after it's older than four weeks. Temporary spikes in data exceeding your subscription level will still be recorded, but consistent overage should be solved by upgrading your subscription level or decreasing data collected.
For customers without an Insights Pro subscription, New Relic may throttle or downsample events to a limit of not more than than 4,000 events per host per minute.
In this example, you have an Insights Pro subscription with a license for 800 million events over 4 weeks, a rate of 200 million events per week. You have APM Pro, Browser Pro, and Mobile Enterprise. A fifth week of data is added via your subscriptions, bumping you to a total of 1 billion events stored within your plan:
- If you are using 975 million events, you are not over your retention.
- If you are using 1.25 billion events, you are over your retention.
For organizations on our original pricing model, log data can be retained for up to 30 days by New Relic. Shorter retention periods of 8 or 15 days are also available.
Logs-in-context data retention
Our logs-in-context data retention policy is based on your current APM product subscription level. For more information, see APM data retention.
For organizations on our original pricing model, Mobile data retention policies depend on your New Relic Mobile product subscription level. This includes data components such as metric data, aggregate metrics, key metrics, trace data, and event data.
For information about your subscription-related data usage, see Mobile subscription usage.
Mobile data retention policies
Component | Lite | Enterprise |
---|---|---|
Overview page data | 24 hours | 90 days |
Crash data and stack traces | 24 hours | 90 days |
HTTP requests (except errors) as metric data | Unavailable | 90 days |
HTTP request errors as metric data | Unavailable | 3 days |
Interaction traces | Unavailable | 90 days |
Custom events * | Unavailable | 1 day |
Mobile events * | 1 day | 8 days |
MobileBreadcrumb events * | Unavailable | 3 days |
MobileCrash events * | 1 day | 90 days |
MobileHandledException events * | Unavailable | 3 days |
MobileJSError events (React Native preview) * | Unavailable | 3 days |
MobileRequest events * | Unavailable | 3 days |
MobileRequestError events * | Unavailable | 3 days |
MobileSession events * | 1 day | 90 days |
* Learn how to extend retention of event data.
Standard Mobile (legacy) data retention policies
Unless otherwise noted, Insights event data is unavailable for Standard subscriptions.
Component | Standard |
---|---|
Overview page data | 7 days |
Crash data and stack traces | 7 days |
HTTP requests (except errors) as metric data | 7 days |
HTTP request errors as metric data | 3 days |
Interaction traces | Unavailable |
MobileCrash events | 8 days |
MobileSession events | 8 days |
For organizations on our original pricing model, Synthetics data retention policies depend on your Synthetics product subscription level. This includes data components such as metric data, aggregate metrics, key metrics, trace data, and Insights events.
Tip
Synthetic monitoring events do not count against an Insights Pro subscription.
Your current subscription level appears in the right column of the Account summary page: Go to synthetics.newrelic.com > (user menu) > Account settings > Account > Summary.
Synthetics data retention policies
Component | Lite | Pro |
---|---|---|
Synthetic monitoring data | 2 weeks | 13 months |
Event data | 2 weeks | 13 months |
Also see the data retention details for APIs, including:
All raw metric data points will be retained for 30 days. All additional aggregated data derived from the raw metric data points (for example, one-minute rollups) will be retained for 13 months. Any change to the retention period beyond such periods may result in a charge to you.
Data components
For organizations on our original pricing model, the section below provides an explanation of some types of data components governed by the data retention rules of specific products:
See Event data retention for information on the event data type.
Metric timeslice data is a specific type of data that is used for most metric charts and reports in APM, , and browser.
Important
Note that metric timeslice data differs from other metric data types.
All metric timeslice data is aggregated, but New Relic deals with fresh data and old data in different ways.
- Fresh data has specific policies applied to the data to keep granular views of performance as aggregate metrics.
- As data ages and becomes less useful in a granular state, we summarize that data and only keep key metrics.
Aggregate metric timeslice data summarizes calls to specific methods in your application: how many times each one was called and response times. In the New Relic UI, you see the class and method names along with their aggregate numbers. Metric data aggregation depends on your subscription level.
Subscription Level | Aggregate retention |
---|---|
Enterprise | Aggregates (averages) to 1-hour periods after 8 days. After 90 days, the permanent metric data continues to be stored in 1-hour periods. This means you cannot obtain data granularity of less than 1 hour after 8 days, and only a subset of metrics are available after 90 days. |
Pro | After 8 days |
Essentials | After 3 days. |
Legacy Small Business, Startup, and Standard | After 3 days. |
Lite | After 2 hours. |
We retain your most recent data in one-minute increments. We also aggregate permanent metric data to day-size increments after 90 days. When looking at older data in small time windows, you may notice that charts show less detail. As data ages, it is aggregated into larger segments.
New Relic retains certain "key" metric timeslice data aggregations forever for Enterprise and Pro customers, for any number of applications. New Relic aggregates permanent key metric data to hour-size increments after 90 days.
Product | Key metrics |
---|---|
APM |
|
Browser |
|
Mobile |
|
Depending on the product, New Relic retains different types of trace data:
Product | Trace data |
---|---|
APM | Types of trace data: |
Browser | Types of trace data: |
Mobile | Types of trace data: |
*JavaScript errors in the stack trace UI are saved as trace data. JS errors are also saved as events.