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, this ingest process tells us how many GB you pay for, 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 page.
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 | Description |
|---|---|
| Timeslices (1-minute) and Metric:Raw |
Metrics are timeslices + MetricRaw Metric group: 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. |
| APM (transactions and errors) |
Metric group: |
| InfraSamples:Raw |
Includes multiple Infrastructure events: |
|
Infrastructure host data Metric group: 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: 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: 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. |
|
| Logging |
Includes logs and Metric group: 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. |
| Default |
Metric group: |
|
Mobile error Mobile general Breadcrumb crash event trails Mobile session Mobile exception Mobile crash |
Metric group: |
| Tracing |
Metric group: Namespaces that contain all tracing events, including tracing spans and excluding internal tracing. |
|
Browser:EventLog Browser Browser:JSErrors PcvPerf (PageView timing) |
Metric group: |
| Lambda |
Serverless Metric group: |
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
You can use NerdGraph to drop entire data types or drop data attributes from data types so they’re not written to NRDB. This improves performance, reduces retention costs, and avoids writing sensitive data to the database. Learn how to drop data. See Drop data with drop filter rules for information on dropping log data.
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.