For New Relic pricing, the data ingested by your New Relic organization is one billing factor.
If you're not yet a New Relic customer and are curious about costs, first see our main pricing page. If you're an existing customer, keep reading to learn details about data ingest billing.
For how to find usage and billing information in the UI, see Billing UI.
For how to view and manage your data ingest, see Manage ingest.
Your organization's price per GB of ingested data varies depending on which data option your organization has: Data Plus or our Original Data option. The Data Plus option offers advanced data capabilities for optimized performance, scale, security, and governance. A New Relic organization can have only one option at a time.
Here's a table with comparisons of the two options. Prices and limits are monthly, and prices are in USD.
Original Data option
Data Plus option
More feature details
Requires Pro or Enterprise
Data ingest free limit
Data ingest price
Data retention free limit
Default of at least 8 days
90 days extra over default
Price for each additional 30 days of retention
Additional price to store data in EU data center
Data is stored in the US data center by default.
Max query limit
300B data points per 30 minutes
1T data points per 30 minutes
Maximum query duration
10 minutes via query builder and API; 2 minutes for the remainder of UI
Cloud provider choice
Single cloud provider
Azure or multiple cloud providers
Choose your preferred cloud provider for your observability workloads to align your telemetry storage with your engineering deployment model and cloud preference.
Automatically mask known credit card and Social Security number patterns in logs.
Create and track rules directly in the log management UI, and mask or hash sensitive log data.
New Relic Vulnerability Management
Identify vulnerabilities and address risks at every stage of the software lifecycle.
Achieve security compliance through configurations that help you meet your FedRAMP and HIPAA requirements.
Configure rules to simultaneously export telemetry data to your AWS or Azure storage of choice. Additional export fees to the cloud provider will apply.
Run larger queries with no timeout for historical analysis and modeling, long-term storage, and integration with other data analytics platforms.
Azure Native New Relic Service
To see a side-by-side comparison of Data Plus and our original data option, view our Data Plus data sheet.
Interested in Data Plus? See Upgrade to Data Plus.
With the Azure Native New Relic Service, you can collect and store your telemetry data for apps and infrastructure directly in Azure. This feature is included with Data Plus, but with these limitations:
- Available only in the US data center region
- FedRAMP Moderate/HIPAA eligibility not available
- Historical data export not available
- New Relic Vulnerability Management not available
To upgrade to Data Plus, go to the Data retention UI in the data management hub and click Edit data retention. If you meet the requirements and don't see the upgrade option, talk to your New Relic account representative.
In the context of the New Relic pricing plan, "ingested data" refers to the data saved to New Relic by your organization after we apply various data trimming and data transformation rules. In other words, it's not the amount of raw data sent to New Relic, but the size of the data that actually ends up being stored.
In general, data that we generate to provide our features doesn't count towards your ingest. Examples of features and feature-related data that don't count towards ingest include:
- Basic alerting functionality and applied intelligence features. For example,
NrAiIncident, an event used to generate these features, doesn't count towards ingest.
- Data created by aggregated raw data (for example, aggregated infrastructure data or dimensional metric data).
- Golden metrics (for more on golden metrics, see our entity definitions).
- Synthetic monitor checks. For details on synthetics billing, see Synthetics limits and pricing.
- Usage and billing tracking data (for example,
- Data related to account administration (for example,
To understand your usage, see the usage UI.
- In the context of our pricing model, a GB is defined as 1 billion bytes.
- Monthly data ingested is rounded down to the nearest integer. For example, if your organization uses 100.9 GBs during a month, that's counted as 100 GBs.
For details about data ingest for our Free edition, see Free edition.