--- title: View and manage data retention source: https://docs.newrelic.com/docs/data-apis/manage-data/manage-data-retention --- To find the data retention UI: from the [user menu](https://docs.newrelic.com/docs/accounts/accounts-billing/general-account-settings/intro-account-settings), click **Manage your data** and click **Data retention**. On the **Data retention** UI [page](https://one.newrelic.com/admin-portal/limits-data-retention/data-retention), you can review and manage how long different types of data are stored. You may want shorter retention for some data types in order to protect sensitive information, or you may want longer retention (up to seven years) to be able to see and analyze data and trends over a longer period. The Data retention page has two tabs: - **Account**: Manages retention for account-scoped data - **Organization**: Manages retention for organization-scoped data (such as AI chat and collaboration data) To learn about plans and costs for changing retention, refer to [Data options: Data Plus and original](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#upgrade-data-plus). ## Extend your data retention for long-term analysis and compliance Extending your data retention allows you to do long-term analysis, visualization, and alerting for all your metrics, events, logs, and traces across all of your sources. However, it's important to manage that data for cost, performance, and in some cases, compliance reasons. Our data management hub provides the tools you need to understand and control where your data is coming from, and adjust what's stored and for how long. > #### 💡 TIP > > With [our Data Plus option](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-plus), you get up to an additional 90 days of retention (for most data types) and other enterprise-grade capabilities, such as longer query durations, FedRAMP and HIPAA compliance, additional security features, and more. ## Account-scoped vs organization-scoped retention [#account-vs-organization] The Data retention UI has two tabs for managing retention at different scopes: ### Account tab The **Account** tab manages retention for most New Relic data types. When you use the Account tab, the account selected in the account picker determines which account's retention settings you are viewing or modifying. ### Organization tab The **Organization** tab manages retention for data that is stored at the organization level. Currently, this includes AI chat summaries and collaboration communication threads. Key characteristics of organization-scoped retention: - Applies to all accounts within your organization - The account picker selection does not affect these settings - Base retention is 30 days - Only users with the organization admin role can edit and save changes - Data is managed in a separate database > #### ⚠️ IMPORTANT > > When viewing the **Organization** tab, the account you select in the account picker will not affect what you see or what changes you make. Organization-scoped retention settings apply to your entire organization regardless of the account selected. ![screenshot of data retention page](https://docs.newrelic.com/images/accounts_screenshot-crop_edit-retention-settings.webp "Edit data retention page") The **Data retention** UI is where you can view and edit your effective retention values, as well as upgrade your retention plan. To view explanations of the table column headers, hover over each header in the UI, or see our explanations in the **Requirements** section below. ## Requirements [#requirements] The way users manage data retention may depend on how many accounts you have in your organization and what they are trying to do. ### Single-account organizations [#single-account-organizations] If you are in an organization that has only one account in it, your [**Billing User**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/) can manage the following: - **Max per contract:** This is the highest value you can set for the **Effective retention** of a data type. If you would like to increase this, see our [Data Plus](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-prices) plan. - **Effective retention:** This is the amount of time data is currently retained for a data type. For the user to be able to edit this, the organization (account) needs to be on [Standard or a higher edition](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#how-pricing-works). If your Billing User can't perform either of these two tasks, contact support or your New Relic representative. ### Multiple-account organizations [#multiple-account-organizations] If you're in an organization that has more than one account in it, users can manage the following: - **Max per contract:** This is the highest value you can set for the **Effective retention** of a data type. If you would like to increase this, see our [Data Plus](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-prices) plan. - **Effective retention:** This is the amount of time data is currently retained for a data type. For the user to be able to edit this: - The organization (account) needs to be on [Pro or a higher edition](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#how-pricing-works). - The user type needs to be **Full platform**. - The user would need **View** and **Modify** permissions for the [**Insights event retention**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#data-retention) feature that [points to the account(s)](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/) they need to edit **Effective retention** for. If your user can't perform either of these two tasks after referencing the above details, contact support or your New Relic representative. ### Organization-scoped retention requirements [#organization-requirements] For managing retention in the **Organization** tab: - **Who can edit:** Only users with the organization admin role can edit and save organization-scoped retention settings. - **Who can view:** All users can view organization-scoped retention settings. - **Account picker:** The account selected in the account picker does not affect organization-scoped retention settings. These settings apply to your entire organization. If you cannot edit organization-scoped retention and believe you should have access, contact your organization administrator or your New Relic representative. ## Default retention periods [#retention-periods] The best way to understand your New Relic data retention is to go to the **Data retention** UI page. We recommend this because your organization may have edited your settings and so they might not be the default settings shown below. This table shows the default [namespace](https://docs.newrelic.com/docs/glossary/glossary) retention settings. | Data source | Namespace | Retention for [Original Data option](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices) (days) | Retention for [Data Plus](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices) (days) | | ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | APM | APM | 8 | 98 | | APM | APM errors | 8 | 98 | | APM | APM error stack traces | 8 | 8 | | APM | AI Monitoring | 30 | 120 | | Browser | All ([learn more](#browser-namespaces)) | 8 | 98 | | Custom events | Custom events | 30 | 120 | | Logging | Logging | 30 | 120 | | Infrastructure | Infrastructure processes ([learn more](#infrastructure-data)) | 8 | 98 | | Infrastructure | Infrastructure integrations ([learn more](#infrastructure-data)) | 395 (13 months) | 485 (16 months) | | Marker ([change tracking](https://docs.newrelic.com/docs/change-tracking/change-tracking-introduction)) | Marker | 395 (13 months) | 485 (16 months) | | Mobile | Mobile crash event trails (breadcrumb) | 8 | 98 | | Mobile | Mobile exception | 8 | 98 | | Mobile | Mobile general | 8 | 98 | | Mobile | Mobile error | 8 | 98 | | Mobile | Mobile crash | 90 | 180 | | Mobile | Mobile session | 90 | 180 | | Streaming Videos & Ads | Streaming Video & Ads: Browser | 30 | 120 | | Streaming Videos & Ads | Streaming Video & Ads: Mobile | 30 | 120 | | Streaming Videos & Ads | Streaming Video & Ads: Connected Device | 30 | 120 | | Network | Flows (cloud & on-premises) | 30 | 120 | | Network | SNMP ([see metrics](#dimensional-metrics)) | 395 | 485 | | Network | Syslog | 30 | 120 | | Serverless | Lambda | 8 | 98 | | Serverless | Lambda custom | 8 | 98 | | Serverless | Lambda spans | 8 | 98 | | Synthetic monitoring (not editable) | Synthetic data (not editable) | 395 (13 months) | 395 (13 months) | | Traces | Distributed traces | 8 | 98 | | Transaction | Transaction traces | 8 | 8 | ## Retention details for assorted data types [#data-details] In this section are details about a few different types of data, including some data types that have retention settings that can't be changed. **Dimensional metrics (Metric API)** Raw [dimensional metric](https://docs.newrelic.com/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics) data (the `Metric` data type) is aggregated (rolled up) for a few different time ranges and those aggregations are retained for different lengths of time. The raw dimensional metric data points are stored for 30 days. Any aggregated data points (aggregation starts at one-minute) are retained for 13 months. Only the raw data ingest counts towards usage: the aggregated data does not. Metric retention periods are not editable. **Metric timeslice data (APM, browser, mobile)** [Metric timeslice data](https://docs.newrelic.com/docs/using-new-relic/data/understand-data/new-relic-data-types#timeslice-data) is generated by APM (both custom metrics and default metrics), mobile monitoring, and browser agents. A metric timeslice consists of three parts: a metric name, the segment of time the metric represents (the "timeslice"), and a numeric value (the measurement). APM, browser monitoring, and mobile agents can collect thousands of metric timeslices per minute for a variety of performance metrics, such as error rate, bandwidth usage, and garbage collection time. Metric timeslice data is aggregated like this: - first to 1-minute rollups that are stored for 8 days - the 1-minute rollups are also added to 1-hour roll-ups that are retained for 90 days Only the initial raw data ingest counts towards usage: the aggregated data does not. Some key metrics are stored indefinitely. Read on to learn the key metrics by product. Here are key metric timeslice data that is stored indefinitely: | APM | - [Apdex](https://docs.newrelic.com/docs/site/apdex-measuring-user-satisfaction), for app server - Throughput and page views - Response time, plus breakdown into [tiers](https://docs.newrelic.com/docs/accounts-partnerships/education/getting-started-new-relic/glossary#tier) or categories on [your app's main **Overview** chart](https://docs.newrelic.com/docs/apm/applications-menu/monitoring/apm-overview-page) - Page load time, plus breakdown into [segments](https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process#time-segments) - Error rate - CPU usage - Memory usage | | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Browser | - [Apdex](https://docs.newrelic.com/docs/site/apdex-measuring-user-satisfaction), for browser - Browser page load time - Throughput total. After 90 days, there is no breakout by browser type, and only the combined average value is available for the time range requested. | | Mobile | - Crash rate: For [iOS](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/getting-started/ios-agent-crash-reporting) and for [Android](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/getting-started/android-agent-crash-reporting) - [Network throughput](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page) - [Network response time](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/http-requests-page) - [Network error rates](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/network-pages/errors-mobile-apps) - [Interaction traces](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/interactions-page) | **APM namespaces** Each APM namespace maps to specific event types. Understanding this mapping helps clarify which retention period applies to each event — for example, `ErrorTrace`, `SqlTrace`, and `TransactionTrace` are **not** stored under the distributed traces namespace. - `APM` namespace: [`Transaction`](/attribute-dictionary/?event=Transaction), [`TransactionError`](/attribute-dictionary/?event=TransactionError) - `APM errors` namespace: [`ErrorTrace`](/attribute-dictionary/?event=ErrorTrace) - `APM error stack traces` namespace: Stack trace data associated with `ErrorTrace` events - `Transaction traces` namespace: [`TransactionTrace`](/attribute-dictionary/?event=TransactionTrace), [`SqlTrace`](/attribute-dictionary/?event=SqlTrace) Note that `Span` events (used in [distributed tracing](https://docs.newrelic.com/docs/distributed-tracing/concepts/introduction-distributed-tracing/)) are stored under the separate **Distributed traces** namespace, which has its own retention period. For more about APM events, see [Events reported by APM](https://docs.newrelic.com/docs/data-apis/understand-data/event-data/events-reported-apm/). **Browser namespaces** All browser namespaces have the same default retention period. Here are details about the events in each browser namespace: - `Browser` namespace: `BrowserPerformance`, `PageAction`, `PageView`, `UserAction` - `Browser events` namespace: `AjaxRequest`, `BrowserInteraction`, `PageViewTiming` - `Browser JS errors` namespace: `JavaScriptError` For more about these events, see [the browser events in the data dictionary](/attribute-dictionary/?dataSource=Browser+agent). **Infrastructure data** Infrastructure monitoring downsamples your data as it's generated. Only the 4x main infrastructure monitoring metric data types (`SystemSample`, `StorageSample`, `NetworkSample` and `ProcessSample`) 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 | 8 days | | 1 minute | 60 minutes to 6 hours | 30 days | | 10 minutes | 6 hours to 3 days | 13 months | | 1 hour | 3 days to 14 days | 13 months | | 3 hours | 14+ days | 13 months | ## Edit data retention [#adjust-retention] To view and edit your retention, go to [data retention view](https://one.newrelic.com/admin-portal/limits-data-retention/data-retention), and click **Edit data retention**. There you'll see options for editing data retention or upgrading to Data Plus. If you don't see that, review [the requirements](#requirements) and talk to your New Relic account representative. Options for increasing retention: - If you haven't already, switch to [Data Plus](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#data-plus), which offers significantly longer data retention and other benefits. - For Data Plus or original data option: add data retention. 30 days of additional data retention for your organization costs $0.05 per GB ingested per month. Important points about increasing retention: - When you enable a higher retention period, retention is increased across the board for all data types listed in the [**Data retention** UI](#find-ui). It cannot be increased only for specific data types. - Once you enable a higher retention period, reducing retention for specific data sources has no impact on your billing. To learn about ways to reduce your data ingest and billing, see [Manage data ingest](https://docs.newrelic.com/docs/data-apis/manage-data/manage-data-coming-new-relic). - When you adjust retention, it can take up to 24 hours to take effect. ### Reducing retention [#reduce-retention] When you reduce the retention period for a data source, existing data of that type won't immediately disappear. That data might be visible and returned in queries for up to several weeks. We have safeguards in place to ensure you don't accidentally delete data, but this also means that reducing retention values isn't a good strategy for quickly [removing data](#deleting-data). To learn about options for reducing data ingest, see [Manage data ingest](https://docs.newrelic.com/docs/data-apis/manage-data/manage-data-coming-new-relic). ## Delete existing data [#deleting-data] Once [telemetry data](https://docs.newrelic.com/docs/using-new-relic/data/understand-data/new-relic-data-types) is reported to the New Relic database 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 period](#adjust-retention) ends. If you want to delete data that has already been reported, contact your New Relic representative, if you have one. ## Export and stream data [#export-data] Organizations with Data Plus can export their data for long-term storage using their preferred tools. Features related to this include: - [Streaming data export](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-streaming-export) - [Historical data export](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export) ## Manage retention via API [#api-examples] In addition to changing your retention settings in the UI, you can use our [NerdGraph API](https://docs.newrelic.com/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph). Some example NerdGraph requests are included below. Note that your data retention changes may take up to 24 hours to take effect. Before using the API to adjust retention, review [the rules on adjusting retention](#adjust-retention). **List customizable retention event namespaces** To list the customizable retention event names spaces for your account: ````graphql query { actor { account(id: YOUR_ACCOUNT_ID) { dataManagement { customizableRetention { eventNamespaces { namespace } } } } } } ``` ```` **List active rules on an account** To list active rules on an account: ````graphql query { actor { account(id: YOUR_ACCOUNT_ID) { dataManagement { eventRetentionRules { id deletedAt deletedById createdAt createdById retentionInDays namespace } } } } } ``` ```` **Show active rule on an account/namespace pair** To show the active rule on a specific account/namespace pair: ````graphql query { actor { account(id: YOUR_ACCOUNT_ID) { dataManagement { eventRetentionRule(namespace: "APM") { id deletedById deletedAt createdById createdAt retentionInDays namespace } } } } } ``` ```` **Create a new rule** To create a new rule: ````graphql mutation { dataManagementCreateEventRetentionRule(accountId: YOUR_ACCOUNT_ID, namespace: "APM", retentionInDays: 8) { id deletedById deletedAt createdById createdAt retentionInDays namespace } } ``` ```` **Delete an existing rule** If you delete a rule applied to a child account, that child account will adopt the current retention value of its parent account for the given namespace. If you delete a rule applied to a parent account, the default retention value will re-apply for the given namespace. To delete an existing rule: ````graphql mutation { dataManagementDeleteEventRetentionRule(accountId: YOUR_ACCOUNT_ID, namespace: "APM") { id deletedById deletedAt createdById createdAt retentionInDays namespace } } ``` ```` **Copy existing child account rules to others** You can specify a child account to be the template or source account, and have other destination child accounts adopt the same namespace retention values of the source child account. Note: all child accounts must be within the same parent account. To copy an existing set of retentions: ````graphql mutation { dataManagementCopyRetentions( sourceAccountId: SOURCE_ACCOUNT_ID, destinationAccountIds: [DESTINATION_ACCOUNT_ID_1, DESTINATION_ACCOUNT_ID_2, DESTINATION_ACCOUNT_ID_3]) { success failure } } ``` Success and failure will return lists of destination account IDs that were successful (or failed) in copying rules from the source account. ```` ## Account inheritance [#account-structure] The data retention settings of a [parent account](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/mastersub-account-structure) are inherited by its children accounts. In this context, a New Relic organization's first account is considered the parent account, and other accounts added to the organization inherit the settings in that account. ## RSS - Atom Subscribe to the [RSS feed](https://github.com/newrelic/docs-website/commits/develop/src/content/docs/data-apis/manage-data/manage-data-retention.mdx.atom).