For organizations on our usage-based pricing model, the data ingested and stored to your New Relic organization is one billing factor.
For how to find billing and usage information in the UI, see Billing-related UI.
Your organization's price per GB of ingested data varies depending on which data option you have:
For our usage-based pricing model, “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.
Here are some notes about New Relic features and data that do not count towards ingest and billing:
- Basic alerting functionality doesn't count towards billing.
- Applied intelligence data reported from third-party services counts towards billing but internally generated data (for example,
NrIncidentEventdata) does not.
- Golden metrics don't count towards billing. (For details about how those are defined, see our entity definitions).
- Synthetic monitor checks don't count towards billing. The monthly limit on synthetic checks is determined by your pricing edition.
- Usage-tracking data (for example,
NrConsumption) doesn't count towards billing.
- Data related to organization and account administration (for example,
NrAuditEvent) doesn't count towards billing.
To understand your usage, see the usage UI.
Other calculation details:
- In the context of our usage-based pricing model, a GB is defined as 1 billion bytes.
- Monthly data ingested is rounded down to the nearest integer. For example, if your account uses 100.9 GBs during a month, that's counted as 100 GBs.
- For more on how data is ingested, see Manage data ingest.
- For how to estimate data ingest and cost, see Data ingest estimator.
- For how to query usage, see Query and alert on usage.
If your organization is on our free tier and your data ingest exceeds 100 GBs in a calendar month, your data ingest is disabled until the beginning of the next month. Note that when ingest is disabled, the re-enabling of ingest at the start of the following month may take up to 24 hours.