重要
This doc is for accounts on our original Product-based pricing. If you're on the newer pricing plan, see New Relic One pricing plan. Not sure which you're on? See Overview of pricing plans.
For accounts on our original pricing plan, our usage UI lets you predictably track your data usage, and see how that may affect your pricing. This document explains how New Relic calculates billable usage for APM accounts that have CU-based pricing (not host-based pricing), and also provides available subscription usage attributes and example NRQL queries to use in the New Relic UI or with API calls.
Data generation
Once per day, an APM account will generate an NrDailyUsage
event for:
- Every application instance created over the last 24 hours
- Every unique host on which an application instance existed over the last 24 hours
These two types of events allow your usage data to be queried and analyzed in many different ways. To query the application events, use a usageType
attribute value of Application
. To query the host events, use a usageType
attribute value of Host
.
All APM events use a productLine
attribute value of APM
. For more information, see APM query examples.
Usage calculations
Monthly billable CUs for a host are calculated by the size of the host running APM (number of CPUs + GBs of RAM) multiplied by the number of hours the host is connected to New Relic during that month. For more on how this is calculated, see CU-based pricing.
ヒント
Only the account Owner and Admins can view the usage UI. However, anyone in your account can query usage data using the NrDailyUsage
event.
To get an estimate of the current month's eventual billable CUs:
- Go to the usage UI.
- On the APM usage page, set the time picker to Current month.
- Multiply the Avg daily compute units by the number of days in the current month.
For more information about the usage UI, see Intro to subscription usage data.
Table definitions
Here are definitions of the column headers displayed in the UI table and CSV files. The columns visible depend on the Group by option selected at the top of the page.
Header | Definition |
---|---|
Account name | The name of the account. This can be a standalone account, a parent account or a customer partnership. |
Host ID | The unique identifier for that host. If the host is in AWS, we use the AWS-provided instance ID. For other hosts, New Relic assigns a host ID. For more about how this value is created, see |
Agent hostname | The name of the host, as reported by the agent. For more about this value, see |
Average daily compute units | The average daily compute units used. |
% of total usage | The percentage of the total usage used. |
General attributes
The following are general (not APM-specific) account-related attributes. These attributes can help you understand how your accounts are using New Relic products.
Attribute | Description |
---|---|
| ID of the New Relic account that is directly responsible for the stored events, as determined from the license key used. |
| Name of the New Relic account that is directly responsible for the stored events, as determined from the license key used. |
| The ID of the parent account, also known as the master account. This is the account that's either responsible for stored events or that is the parent of the consuming account. When a parent account is the consuming account, This attribute is present even for accounts that don't have a parent account. This is to ensure continued reporting if the account is later made a parent account. |
| Name of the parent account (also known as the master account) that's either responsible for stored events, or that is the parent of the consuming account. When a parent is the consuming account, This attribute is present even for accounts that do not have a parent account. This is to ensure continued reporting if the account is later made a parent account. |
| Partner ID of the New Relic customer partnership associated with the account responsible for the stored events. This attribute is only present if the consuming account is associated with a New Relic customer partnership. |
| Name of the New Relic customer partnership associated with the account responsible for the stored events. This attribute is only present if the consuming account is associated with a customer partnership. |
| ID of the child account that is responsible for the stored event. When this attribute is present, This attribute is only present if the consuming account is a child account (not a parent account). |
| Name of the child account responsible for stored events. When present, this attribute is the same as the This attribute is only present if the consuming account is a child account (not a parent account). |
| UNIX timestamp (seconds since epoch) of the day and time when event generation was initiated. |
APM attributes (CU-based)
The following are usage-related attributes generated by CU-based APM accounts (not host-based APM). To query APM-specific data, use a productLine
attribute value of APM
.
Attribute | Description |
---|---|
| ID reported by the agent to uniquely identify the host for which this usage event is reported. This value can come from several sources in the application’s environment, but commonly is the value returned by the |
| Bytes of RAM available to the host, as detected by the New Relic agent from the host OS. |
| Number of logical CPU cores available to the host, as detected by the New Relic agent from the host OS. |
| Version of the APM agent running in the application instance reporting this usage. Present only for events where To update your agent version, see Update the New Relic agent. |
| ID uniquely identifying the application that is reporting this usage, as it appears in the APM product. Present only for events where |
| ID uniquely identifying the application instance (the process running the APM agent). |
| Name of the application reporting this usage, as it appears in the APM product. Present only for events where |
| Size of the host, for CU-based billing purposes. Calculated as |
| Bytes of RAM available to the host, as defined by the cloud provider for the host’s instance type. |
| Number of logical processors available to the host, as defined by the cloud provider for the host’s instance type. |
| Number of compute units (CUs) recorded for the given host. CUs are calculated as |
| Describes the algorithm used to calculate the host size for CU usage. Values include:
|
| The number of unique container IDs associated with this host. Present only for events where |
| Number of hours for which usage was recorded for the given entity. When an entity is connected to New Relic for any amount of time within a given hour, that hour is counted toward usage. |
| Name of the language that the usage-reporting application is written in, as reported by the New Relic agent. Examples: |
| Bytes of RAM available to the host. Used to calculate |
| Number of logical processors available to the host, used to calculate |
| Linux boot ID of host for which this usage is reported, which is unique for each boot lifetime of each Linux operating system instance. Will only be present when the New Relic agent is one of the following versions: |
| ID uniquely identifying the cloud host instance (example: an AWS EC2 instance) for which this usage is reported. (For example, for an AWS EC2 instance, the value would look like Agents with these versions will detect cloud provider data for AWS: |
| Size of the cloud instance for this host for CU-based APM billing purposes, as calculated according to the formula for |
| Instance type of the host as defined by the cloud provider and detected by the agent. For example: |
| Name of the cloud provider for this host. Example values: |
| Name of the zone that a cloud provider host is located in. For example: |
| ID of the Docker or other Linux container in which the application instance is running. This will not be present if a container was not detected by the agent. Present only for events where |
| ID used to uniquely identify the host for which this usage is reported. Any given hour of APM usage for this host will be counted only once when calculating |
| This is |
| This is |
| This is |
| The New Relic product the usage data is from. APM usage data will have the value |
| For APM, this value can be either For Only |
Query examples
Here are some examples of NRQL queries you can use with your account usage data.
Use of Docker or other containers
Some previous APM agents may miscount containers as hosts, which may lead to over-reporting of compute unit (CU) usage.
To fix this calculation for Linux-based containers (including Docker), upgrade your APM agent to these versions:
- Go: 1.11 or higher
- Java: 3.42.0 or higher
- .NET: 6.19.330.0 or higher
- Node.js: 2.1.0 or higher
- PHP: 7.5.0.199 or higher
- Python: 2.90.0.75 or higher
- Ruby: 4.4.0.336 or higher
その他のヘルプ
さらに支援が必要な場合は、これらのサポートと学習リソースを確認してください:
- Explorers Hubでは、コミュニティからのサポートを受けたり、ディスカッションに参加したりすることができます。
- 当社サイトで答えを見つけて、サポートポータルの使用方法を確認してください。
- Linux、Windows、およびmacOS向けトラブルシューティングツールであるNew Relic Diagnosticsを実行してください。
- New Relicの とandドキュメント をご確認ください。