For New Relic pricing, the data ingested by your New Relic organization is one billing factor.
Learn about costs
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.
View data ingest in the UI
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.
Data options: Data Plus and original
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.
Feature/ability | Original Data option | Data Plus option | More feature details |
|---|---|---|---|
All editions | Requires Standard, Pro, or Enterprise (We note below if a feature is specific to an edition) | ||
Data free limit | 100 GB Ingested | 100 GB Ingested | |
Data price | $0.35/GB Ingested | $0.55/GB Ingested | |
Data retention free limit | Default of at least 8 days | 90 days extra over default | |
Price for each additional 30 days of retention | +$0.05/GB | +$0.05/GB | |
Additional price to store data in EU data center | +$0.05/GB | +$0.05/GB | Data is stored in the US data center by default. |
Max query limit | Up to 20B data points per minute | Up to 60B data points per minute | |
Maximum query duration | 1 minute | Up to 10 minutes | |
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 UI, and mask or hash sensitive log data. | ||
New Relic Vulnerability Management | +$0.10/GB | Standard, Pro, and Enterprise | Identify vulnerabilities and address risks at every stage of the software lifecycle. |
FedRAMP Moderate and HIPAA eligibility | Enterprise | Achieve security compliance through configurations that help you meet your FedRAMP and HIPAA requirements. | |
Standard, Pro, and Enterprise | Configure rules to simultaneously export telemetry data to your AWS or Azure storage of choice. Additional export fees to the cloud provider will apply. | ||
Standard, Pro, and Enterprise | 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 | Standard, Pro, and Enterprise |
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.
Azure Native New Relic Service details
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
Upgrade to Data Plus
To upgrade to Data Plus, go to the Data retention UI in the data management hub and click Upgrade retention.
- Note: You may see an Edit data retention button, but that is different than the Upgrade retention button.
- To see the Upgrade retention button, you need to have Billing permissions. If you meet the requirements and still don't see the Upgrade retention option, talk to your New Relic account representative.
What counts as billable GB Ingested?
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 GB Ingested. Examples of features and feature-related data that don't count towards GB Ingested include:
- Basic alerting functionality. For example,
NrAiIncident, an event used to generate these features, doesn't count towards GB Ingested. - 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,
NrConsumption). - Data related to account administration (for example,
NrIntegrationError,NrAuditEvent).
To understand your usage, see the usage UI.
Other calculation details
- In the context of our pricing model, a GB is defined as 1 billion bytes.
- Monthly GB 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.
Free edition
For details about GB Ingested for our Free edition, see Free edition.
Learn more
- For more on how to manage GB Ingested, see Manage data ingest.
- For how to query usage, see Query and alert on usage.