Skip to content

Commit

Permalink
fix(billing): what doesn't count towards billing
Browse files Browse the repository at this point in the history
  • Loading branch information
zuluecho9 committed Feb 17, 2022
1 parent f2aa7a2 commit 4eea0a0
Showing 1 changed file with 7 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ For how to find billing and usage information in the UI, see [Billing-related UI

## Data ingest calculation [#usage-calculation]

To view your usage, go to the [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/billing-ui).

For the [New Relic One pricing model](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), “ingested data” refers to the data saved for your New Relic 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 details on New Relic features and data that **do not** count towards ingest and billing:
* [Basic alerting functionality](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow) does not count towards billing.
* [Applied intelligence](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-applied-intelligence): data reported from third-party services counts towards billing but internal events (for example, the `NrIncidentEvent`) do not.
* Usage-tracking data (for example, `NrUsage`, `NrMTDConsumption`, `NrConsumption`) does not count towards billing.
* Administration-related data (for example, `NrIntegrationError`, `NrAuditEvent`) does not count towards billing.
Here are some notes about New Relic features and data that **do not** count towards ingest and billing:
* [Basic alerting functionality](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/alerts-concepts-workflow) doesn't count towards billing.
* [Applied intelligence](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-applied-intelligence): data reported from third-party services counts towards billing but internally generated data (for example, `NrIncidentEvent` data) does not.
* Usage-tracking data (for example, `NrUsage`, `NrMTDConsumption`, `NrConsumption`) doesn't count towards billing.
* Data related to organization and account administration (for example, `NrIntegrationError`, `NrAuditEvent`) doesn't count towards billing.

To see details about your usage, go to the [usage UI](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/billing-ui).

Other calculation details:
* In the context of New Relic One pricing, a GB is defined as 1 billion bytes.
Expand Down

0 comments on commit 4eea0a0

Please sign in to comment.