On May 31, 2023, the usage UI for our original pricing model reaches end-of-life (EoL). In this doc are NRQL queries that customers on the original pricing model can use to understand their usage.
What customers are affected?
This affects New Relic organizations on our original pricing model, which is a pricing model where we billed by various products (like APM, Browser monitoring, Infrastructure monitoring, and more).
What can you do?
If your organization is affected by this end-of-life and you'll be staying on our original pricing plan, options include:
- Create custom dashboards that include the usage queries below
- Run one-off queries when you need to understand usage
Details about querying
Some details about querying usage data:
- Usage data is stored on the
NrDailyUsageevent type and theNrUsageevent type - Querying with the query builder in the UI will query in a specific account, and any child accounts. You can also use NerdGraph for cross-account querying.
We'll give you some example usage queries below for different product categories.
For details about how CU-based pricing works, see Host- and CU-based pricing.
Overview queries
Billboard with comparison to prior time period:
SELECT rate(SUM(apmComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(apmComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by host:
SELECT rate(SUM(apmComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 FACET hostId,agentHostname,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by host:
SELECT rate(SUM(apmComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day FACET hostId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15For details about how host-based pricing works, see Host- and CU-based pricing.
Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(apmHoursUsed) / 24, 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(apmHoursUsed), 1 hour) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by host:
SELECT rate(SUM(apmHoursUsed), 1 hour) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 FACET hostId,agentHostname,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by host:
SELECT rate(SUM(apmHoursUsed), 1 hour) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'APM' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day FACET hostId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(browserPageViewCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Browser' AND `usageType` = 'Application' AND `consumingAccountId` = 1 AND `isPrimaryApp` != 'false' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT SUM(browserPageViewCount) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Browser' AND `usageType` = 'Application' AND `consumingAccountId` = 1 AND `isPrimaryApp` != 'false' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by consuming account:
SELECT rate(SUM(browserPageViewCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Browser' AND `usageType` = 'Application' AND `consumingAccountId` = 1 AND `isPrimaryApp` != 'false' FACET consumingAccountName,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by consuming account:
SELECT SUM(browserPageViewCount) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Browser' AND `usageType` = 'Application' AND `consumingAccountId` = 1 AND `isPrimaryApp` != 'false' TIMESERIES 1 day FACET consumingAccountName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period, monthly users:
SELECT SUM(mobileUniqueUsersPerMonth) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Mobile' AND `usageType` = 'Application' AND `consumingAccountId` = 1 TIMESERIES 1 day COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, monthly users:
SELECT SUM(mobileUniqueUsersPerMonth) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Mobile' AND `usageType` = 'Application' AND `consumingAccountId` = 1 TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by mobile app name:
SELECT SUM(mobileUniqueUsersPerMonth) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Mobile' AND `usageType` = 'Application' AND `consumingAccountId` = 1 TIMESERIES 1 day FACET mobileAppName,mobileAppId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by mobile app name:
SELECT SUM(mobileUniqueUsersPerMonth) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Mobile' AND `usageType` = 'Application' AND `consumingAccountId` = 1 TIMESERIES 1 day FACET mobileAppName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15For details about how infrastructure CU-based pricing works, see Host- and CU-based pricing.
Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(infrastructureComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Infrastructure' AND `usageType` = 'Host' AND `consumingAccountId` = 1 COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT SUM(infrastructureComputeUnits) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Infrastructure' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by agent hostname:
SELECT rate(SUM(infrastructureComputeUnits), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Infrastructure' AND `usageType` = 'Host' AND `consumingAccountId` = 1 FACET agentHostname SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by host:
SELECT SUM(infrastructureComputeUnits) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Infrastructure' AND `usageType` = 'Host' AND `consumingAccountId` = 1 TIMESERIES 1 day FACET agentHostname SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Logs' AND `consumingAccountId` = 1 AND `metric` = 'BytesSaved' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Logs' AND `consumingAccountId` = 1 AND `metric` = 'BytesSaved' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Logs' AND `consumingAccountId` = 1 AND `metric` = 'BytesSaved' FACET consumingAccountName,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Logs' AND `consumingAccountId` = 1 AND `metric` = 'BytesSaved' TIMESERIES 1 day FACET consumingAccountName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(usage), 1 minute) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Metrics' AND `consumingAccountId` = 1 AND `metric` = 'DataPointsSent' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(usage), 1 minute) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Metrics' AND `consumingAccountId` = 1 AND `metric` = 'DataPointsSent' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by consuming account:
SELECT rate(SUM(usage), 1 minute) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Metrics' AND `consumingAccountId` = 1 AND `metric` = 'DataPointsSent' FACET consumingAccountName,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by consuming account:
SELECT rate(SUM(usage), 1 minute) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Metrics' AND `consumingAccountId` = 1 AND `metric` = 'DataPointsSent' TIMESERIES 1 day FACET consumingAccountName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Serverless' AND `consumingAccountId` = 1 AND `metric` = 'LambdaEventsSaved' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Serverless' AND `consumingAccountId` = 1 AND `metric` = 'LambdaEventsSaved' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Serverless' AND `consumingAccountId` = 1 AND `metric` = 'LambdaEventsSaved' FACET consumingAccountName,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Serverless' AND `consumingAccountId` = 1 AND `metric` = 'LambdaEventsSaved' TIMESERIES 1 day FACET consumingAccountName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Detailed queries
Usage over time period, by monitor name:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' FACET syntheticsMonitorName,syntheticsMonitorId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by monitor name:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' TIMESERIES 1 day FACET syntheticsMonitorName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Usage over time period, by type label:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' FACET syntheticsTypeLabel SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by type label:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' TIMESERIES 1 day FACET syntheticsTypeLabel SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Usage over time period, by location:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' FACET syntheticsLocation SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by location:
SELECT rate(SUM(syntheticsSuccessCheckCount + syntheticsFailedCheckCount), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Synthetics' AND `usageType` = 'Check' AND `consumingAccountId` = 1 AND `syntheticsTypeLabel` != 'Ping' TIMESERIES 1 day FACET syntheticsLocation SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15Overview queries
Billboard with comparison to prior period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Traces' AND `consumingAccountId` = 1 AND `metric` = 'SpansSaved' COMPARE WITH 1 month ago SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Traces' AND `consumingAccountId` = 1 AND `metric` = 'SpansSaved' TIMESERIES 1 day SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 5Drilldown queries
Usage over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Traces' AND `consumingAccountId` = 1 AND `metric` = 'SpansSaved' FACET consumingAccountName,consumingAccountId SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 500Trend chart over time period, by consuming account:
SELECT rate(SUM(usage), 1 day) as usage FROM NrDailyUsage, NrUsage WHERE `productLine` = 'Traces' AND `consumingAccountId` = 1 AND `metric` = 'SpansSaved' TIMESERIES 1 day FACET consumingAccountName SINCE '2023-02-01 00:00:00' UNTIL '2023-03-01 00:00:00' LIMIT 15APM and infrastructure: Compute-unit vs host-based pricing
APM offers a choice between two pricing models: compute unit (CU) based pricing and host-based pricing. New Relic Infrastructure offers only CU-based pricing. This section shows how both options are calculated, and explains what "host" means in these pricing contexts:
On our original pricing model, CU-based pricing is available for these New Relic products:
- APM (choice of either CU-based pricing or host-based pricing)
- Infrastructure: only CU-based pricing
With CU-based pricing, your monthly price is determined by the size of the host (computing power and memory) running New Relic and the number of hours it connects to New Relic during the month. If a host is connected to New Relic at any time during an hour, that hour counts towards the CU calculation.
Each host is counted separately for each New Relic account the host reports data to. For example, if you have a parent account with two children accounts, each running applications on the same host for 3,000 CUs in a given month, the usage for the parent account will be 6,000 CUs.
For APM, CU-based pricing is the best choice if you have many cloud-based dynamic computing resources. For this reason, CU-based pricing is sometimes referred to as cloud pricing.
CUs are calculated as follows:
CUs = (# of CPUs + GBs of RAM) x hours used
The maximum size of a given host (CPUs + GB RAM) is capped at 16.
Examples:
- If a host has 2 CPU cores, 2GB RAM, and connects to New Relic for one hour (or less than one hour), it consumes 4 CUs.
- If a host has 2 CPU cores, 2GB RAM, and connects to New Relic for an entire month (750 hours used as standard month size), it consumes 3,000 CUs.
You can purchase blocks of CUs to be consumed on a monthly basis. The total number of CUs purchased monthly is calculated by adding up the estimated CU consumption for all hosts for the month. There is no month-to-month rollover of unused CUs. Also, New Relic does not charge by JVMs, containers (such as Docker or Cloud Foundry), or application instances--it charges by the hosts running those containers or application instances.
Price points vary, depending on the New Relic product and subscription level.
팁
For our original pricing model, APM pricing can be either CU-based or host-based, while New Relic Infrastructure uses only CU-based pricing.
With host-based pricing, New Relic charges based on the number of equivalent hosts used in a month. One equivalent host is defined as: a host connected to New Relic for 750 hours (750 hours used as standard month size). If a host is connected to New Relic at any time during an hour, that hour counts towards the host calculation.
These hours can be divided across multiple hosts. For example, you might have three hosts that are each connected to New Relic for 250 hours during one month: these hours would add up to equal one equivalent host.
Each host is counted separately for each New Relic account the host reports data to. For example, if you have a parent account with two child accounts, each running applications on the same single host for 750 hours in a given month, the usage for the parent account will be 2 equivalent hosts.
Once connected to New Relic, hosts are distinguished by their unique hostnames. A host is connected to New Relic when the language agent is active and is deployed on the host. New Relic does not charge by containers (such as Docker or Cloud Foundry), JVMs, or application instances; it charges by the hosts running those containers or application instances.
New Relic APM gives you a choice between host-based pricing and CU-based pricing. Host-based pricing is ideal if you have mainly static environments, consisting of hosts you manage in your own data center.
To understand how New Relic computes both host-based pricing and CU-based pricing, it's important to understand how the word host is used. A host can be one of the following:
A physical machine is a hardware-based device with dedicated physical resources, including memory, processing, and storage. Each machine has its own OS which applications run on.
A virtual machine (VM) is the software implementation of a physical machine that executes programs like a physical machine. One or more virtual machines can run on a physical machine. Each virtual machine has its own OS and allocated virtual machine resources such as RAM and CPU.
A cloud instance is a type of virtual machine that is run in the public cloud. In this context, virtual machines and cloud instances are different from Java Virtual Machines (JVMs) and containers.
For New Relic pricing calculation purposes, a month is defined as 750 hours.