If you're on the original product-based pricing plan, you retain your existing subscriptions and data retention values. You manage these existing retention settings from the Data management hub in New Relic One. To manage your retention settings, go to the Data management UI. You'll see your existing retention settings. Adjust retention values by clicking Edit retention.
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.
Limits on editing and deleting data
Once telemetry data (events, metrics, logs, traces) is reported to New Relic and available for querying, that data cannot be edited or deleted. This is a purposeful design decision that optimizes New Relic's speed and performance. Data will expire after its data retention ends.
If you sent unwanted data or sensitive data to New Relic that must be removed, contact your account representative at New Relic, or get support at support.newrelic.com.
Product and API data retention policies
Select a New Relic product to see details about its data retention:
Specific retention policies apply to each APM 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 product-based pricing, 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.
Types of data are stored depending on your subscription level:
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.
In addition, Infrastructure downsamples your data on the fly, as it's generated. 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 following table illustrates when different downsampled buckets will be used, both 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 does not count against the 2275 event per compute unit limit.
If you exceed your limit, we do not 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 accounts on our original product-based pricing, 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
New Relic Logs logs in context data retention policy is based on your current APM product subscription level. For more information, see APM data retention.
For accounts on our original product-based pricing, 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.
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
The retention period for historical data depends on the product and subscription level. The following data retention periods exist for New Relic Plugins.
For accounts on our original product-based pricing, 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.
Your current subscription level appears in the right column of the Account summary page: Go to synthetics.newrelic.com > (account dropdown) > Account settings > Account > Summary.
Synthetics data retention policies
Component
Lite
Pro
Synthetics monitor 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.
Metric timeslice data is a specific type of data that is used for most metric charts and reports in APM, mobile, 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.