Manage data retention

This doc applies to accounts on our New Relic One pricing plan. If you're on our original product-based pricing plan, see Original data retention. Not sure which you're on? See Overview of pricing and account/user structure.

Find out how long your data will be stored in the New Relic database (NRDB) on the Data retention page. Standard tier accounts have between 8 and 395 days (about 13 months) of retention, depending on which capabilities of the New Relic platform you’re using. This level of data retention ensures that you can explore your data and experience the value of New Relic. Beyond that, you can purchase additional retention to ensure it suits your business needs.

Use the Data retention page to review the sources of data that you’re storing, when they were last updated, and the length the data is stored.

New Relic One data retention UI page
The Data retention UI shows the source of data, and how long it's retained. (If your account is on our original pricing plan, you'll have different data retention rules.)

Retention periods

For accounts on our New Relic One pricing plan, the following table provides the default retention periods. To increase retention, you must upgrade to a Pro or Enterprise tier.

Source Event namespace Days retained
APM APM errors 8
Browser Browser 8
Browser Browser events 8
Browser Browser JS errors 8
Browser Browser SPA monitoring (EventLog) 8
Browser Browser page view timing 8
Custom events Custom events 8
Serverless Lambda 8
Serverless Lambda custom 8
Serverless Lambda spans 8
Logs Log 30
Infrastructure Infrastructure processes 8
Infrastructure Infrastructure integrations 395 (13 months)
Metrics Metric 395 (13 months)
Events to Metrics Metric 395 (13 months)
Mobile Mobile crash event trails (breadcrumb) 8
Mobile Mobile exception 8
Mobile Mobile general 8
Mobile Mobile error 8
Mobile Mobile crash 90
Mobile Mobile session 90
Traces Traces 8

Metric data rollup

Metric timeslice data is generated by APM (both custom metrics and out-of-the-box metrics), Mobile, and Browser agents. MTS data is aggregated first to 1-minute rollups retained for 8 days, then aggregated to 1-hour roll-ups for 90 days, with key metric data in turn being stored indefinitely. We meter on the size of the initial 1-minute rollup, not on any of the subsequent rollups.

Metric raw data, from APM, Prometheus remote-write API, metrics functionality of the Telemetry SDK, and integrations built on the Telemetry SDK, is handled a little differently. Raw sub-minute metric data is stored for 30 days. Beyond 30 days, 1-minute resolution roll-up events are created and retained for 13 months. As with Metric timeslice data, we meter and bill on the size of the raw ingest, not the subsequent rollups.

Account inheritance

For organizations that have master/sub-account structures, data retention is inherited by a master account's sub-accounts. If a sub-account has its own retention settings, those override settings inherited from the master account.

Data deletion

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.

Original pricing plan differences

If you're on our original product-based pricing plan, you have different data retention rules. See Original data retention.

For more help

If you need more help, check out these support and learning resources: