• /
  • Log in
  • Free account

Manage data coming into New Relic

When you connect your data to New Relic, we process what we receive and apply data dropping and transformation rules. Then we count the bytes needed to represent your data in a standard format, like JSON. If you're on our New Relic One pricing plan, you're charged by the number of bytes written to our database, above and beyond the standard amount that’s free.


This doc is for 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.

The Data ingestion page shows your ingest rates for a period you specify on the top-right of the Data management hub. Since 30 days ago is the default setting, but you can also set a custom date span.

The page shows your daily average GBs, and the total for the range you set. You can toggle between an overall ingest view and an account view to identify which of your accounts are sending the most data. The page also provides the current month-to-date, and the projected end-of-month total ingest rates. With this information, you can proactively drop data or turn off agents in order to manage ingest and, therefore, costs.

If you want to take a look at how we query the data, click the ellipsis icon (just above the chart) to slide out the chart query and open it in our query builder. And If you want to drill down further into your data usage, check out the sample queries in the usage docs.

Gif shows data ingestion with source and account views

From the Login drop-down, select Manage your data, and then select Data ingestion. This is the Data ingestion page with data source and account views.

Data ingestion sources

The Data ingestion page describes which of your data sources provide the most data on average and during specific data ranges. The sources are described here.

Billable data sources


Timeslices (1-minute) and Metric:Raw

Metrics are timeslices + MetricRaw

Metric group: MetricsBytes

Metric timeslice data averages to one-hour periods after eight days. After 90 days, the permanent metric data continues to be stored in one-hour periods. We currently store the raw metric data for 30 days.

You are only billed for the initial ingest volume. You are not billed for subsequent rollups.

APM (transactions and errors)

APM events

Metric group: ApmEventsBytes


Includes multiple Infrastructure events

Infrastructure host data

Metric group:InfraHostBytes

Information related to your servers and virtual machines coming from infrastructure agents, including storage and network data

Infrastructure process data stored in ProcessSample.

Metric group: InfraProcessBytes

Data are metrics related to each process running on the hosts running the Infrastructure agent. This feature is turned off by default.

Infrastructure integrations

Metric group: InfraIntegrationBytes

Performance data related to applications and services, typically managed by the customer, including data related to Docker containers, Windows services, Nagios checks, and cloud integrations such as managed services in AWS, Azure, and GCP.


Includes logs and LogExtendedRecord

Metric group: LoggingBytes

Log messages longer than 4KB are split into multiple events that, when needed, are stitched together to display the original message; this reduces the size of message data.


Custom events

Metric group: CustomEventsBytes

Mobile error

Mobile general

Breadcrumb crash event trails

Mobile session

Mobile exception

Mobile crash

Mobile events

Metric group: MobileEventsBytes


Metric group: TracingBytes

Namespaces that contain all tracing events, including tracing spans and excluding internal tracing.




PcvPerf (PageView timing)

Browser events

Metric group: BrowserEventsBytes



Metric group: ServerlessBytes

Set alerts for data use

Query and alert on usage data describes how to set alerts to get notified if you're nearing data ingest limits you don't want to cross. For example, you might set an alert on logs, which can stack up quickly in an active system.

Adjust your data ingest

Drop data for lower retention costs and data compliance

On ingest, we apply data dropping rules so you won't be charged for data that's not useful. Learn how to set additional data dropping rules yourself. Use NerdGraph to drop entire data types or drop data attributes from data types so they’re not written to NRDB. This enables you to focus on the data you want, reduces retention costs, and avoids writing sensitive data to the database. For dropping log data, see Drop data with drop filter rules.

Turn off agents and integrations

If you don’t need data from specific agents or integrations that you have installed, you can uninstall/delete those tools. For instructions, see the specific documentation for an agent or integration.

For more help

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

Create issueEdit page
Copyright © 2021 New Relic Inc.