New Relic data dictionary

This data dictionary defines some of our default-reported data stored in NRDB and queryable via NRQL. This includes events like Transaction, MobileRequest, and BrowserInteraction, and our Metric, Log, and Span data types. These definitions are also available from our query builder UI by mousing over applicable data type and attribute names.

This dictionary doesn't contain:

  • Data from our infrastructure integrations (for that, see docs for a specific integration)
  • Custom data
  • Detailed integration-specific attributes for Metric data

NrDailyUsage

Data source:

Once per day, New Relic products generate a NrDailyUsage event. Use the productLine attribute to identify and filter for the specific product's usage.

Attribute nameDefinitionData types
agentHostname
ID

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 gethostname Linux syscall. In Docker environments, this attribute can take on the value (sometimes truncated) of the Docker container ID. agentHostname is one of three possible providers for the hostId value.

apmAgentMemoryBytes
bytes (B)

Bytes of RAM available to the host, as detected by the New Relic agent from the host OS.

apmAgentProcessorCount
count

Number of logical CPU cores available to the host, as detected by the New Relic agent from the host OS.

apmAgentVersion

Version of the New Relic APM agent running in the application instance reporting this usage.

Present only for events where usageType equals Application. To update your agent version, see Update the New Relic agent.

apmAppId
ID

ID uniquely identifying the application that is reporting this usage, as it appears in the APM product. Present only for events where usageType equals Application.

apmAppInstanceId
ID

ID uniquely identifying the application instance (the process running the New Relic APM agent).

apmAppName

Name of the application reporting this usage, as it appears in the APM product. Present only for events where usageType equals Application.

apmBillingInstanceSize

Size of the host, for CU-based billing purposes.

Calculated as apmProcessorCount plus (apmMemoryBytes/(1024^3)), or the number of processors plus memory (GiB).

apmCloudDerivedMemoryBytes
bytes (B)

Bytes of RAM available to the host, as defined by the cloud provider for the host's instance type.

apmCloudDerivedProcessorCount
count

Number of logical processors available to the host, as defined by the cloud provider for the host's instance type.

apmComputeUnitRule

Describes the algorithm used to calculate the host size for CU usage.

Values include:

  • agent_collected_calculated_data: Use the host size data collected by the agent from the OS environment.
  • cloud_provider_data: Use the host size data from the cloud provider.
  • missing_data: Some host size data was missing. This could be due to an older agent that doesn't support reporting CPU and memory sizes, or an agent and OS combination for which CPU and memory sizes are not supported. This will result in the default host size (16) being applied.
apmComputeUnits
count

Number of compute units (CUs) recorded for the given host.

CUs are calculated as apmHoursUsed multiplied by apmBillingInstanceSize. For more information, see Compute unit pricing.

apmContainerCount
count

The number of unique container IDs associated with this host. Present only for events where usageType equals Host.

apmHoursUsed

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. When calculating monthly APM host usage, the calculation for equivalent hosts for a month assumes that a standard month has 750 hours: `apmHoursUsed / 750`.

apmLanguage

Name of the language that the usage-reporting application is written in, as reported by the New Relic agent.

Examples: ruby, java, python. Present only for events where usageType equals Application.

apmMemoryBytes
bytes (B)

Bytes of RAM available to the host. Used to calculate apmBillingInstanceSize.

The value of one of these attributes will be used: apmCloudDerivedMemoryBytes, apmAgentMemoryBytes.

apmProcessorCount

Number of logical processors available to the host, used to calculate apmBillingInstanceSize.

The value of one of these attributes will be used: apmCloudDerivedProcessorCount, apmAgentProcessorCount.

bootId
ID

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: 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 bootId is one of three possible providers for the hostId value.

browserAppId
ID

ID uniquely identifying the application reporting this usage, as it appears in the Browser product. Deprecated.

browserPageViewCount
count

Number of page views for an application for that 24-hour period.

For more on how events are generated, see Data generation. Page views for both Pro and Lite Browser agents are counted.

cloudInstanceId
ID

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 i-1234abcd5678ef900.) This is used to uniquely identify the host if the apmComputeUnitRule is cloud_provider_data. This will not be present if no cloud provider was detected by the agent. Agents with these versions will detect cloud provider data for AWS: Go: 1.11 or higher Java: 3.18.0 or higher .NET: 5.1.72.0 or higher Node.js: 1.21.0 or higher PHP: 5.5.0 or higher Python: 2.54.0.41 or higher Ruby: 3.12.1.298 or higher cloudInstanceId is one of three possible providers for the hostId value.

cloudInstanceSize

Size of the cloud instance for this host for CU-based APM billing purposes.

This is calculated according to the formula for apmBillingInstanceSize, using the CPU and memory sizes associated with the instance type defined by the cloud provider. Will not be present if no cloud provider was detected by the agent.

cloudInstanceType

Instance type of the host as defined by the cloud provider and detected by the agent.

For example: c4.2xlarge. This will not be present if no cloud provider was detected by the agent.

cloudProvider

Name of the cloud provider for this host. Example values: aws, azure. This will not be present if no cloud provider was detected by the agent.

cloudZone

Name of the zone that a cloud provider host is located in.

For example: eu-central-1b. This will not be present if no cloud provider was detected by the agent.

consumingAccountId
ID

ID of the New Relic account that's directly responsible for the stored data, as determined from the license key.

consumingAccountName

Name of the New Relic account directly responsible for the stored data, as determined from the license key.

containerId

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 usageType equals Application. This attribute is not used to uniquely identify hosts for billing purposes.

hostId
ID

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 apmHoursUsed. There are several possible host identifiers reported by the New Relic agent. The attributes, if present, will be chosen to use in this order of precedence: cloudInstanceId, bootId, agentHostname.

infrastructureAgentMemoryBytes
bytes (B)

Bytes of RAM available to the host, used to calculate infrastructureBillingInstanceSize.

infrastructureAgentProcessorCount
count

Number of logical CPU cores available to the host, used to calculate infrastructureBillingInstanceSize.

infrastructureAgentVersion

Version of the Infrastructure agent running on the host reporting this usage.

If multiple agents are reporting from the same host, the version from the first agent seen in a given hour will be used.

infrastructureBillingInstanceSize
gibibyte (Gib)

Size of the host, for CU billing purposes. Calculated as: number of processors multiplied by memory in gibibytes (GiB).

infrastructureCloudDerivedMemoryBytes
bytes (B)

Bytes of RAM available to the host, as reported by the cloud provider, used to calculate infrastructureBillingInstanceSize.

infrastructureCloudDerivedProcessorCount
count

Number of logical CPU cores available to the host, as reported by the cloud provider, used to calculate infrastructureBillingInstanceSize.

infrastructureComputeUnitRule

Describes the algorithm used to calculate the host size for CU usage.

Values include: agent_collected_calculated_data: Use the host size data collected by the agent from the OS environment. cloud_provider_data: Use the host size data from the cloud provider. missing_data: Some host size data was missing. This could be due to an agent and operating system combination for which CPU and memory sizes are not supported. This will result in the default host size (16) being applied.

infrastructureComputeUnits

Number of compute units (CUs) recorded for the given host.

CUs are calculated as: infrastructureHoursUsed multiplied by infrastructureBillingInstanceSize. For more about compute unit calculation, see Compute unit pricing.

infrastructureHoursUsed

Number of hours for which usage was recorded for the given host. When a host is connected to New Relic for any amount of time within a given hour, that hour is counted toward usage.

insightsEventNamespace

The type of event. For example: Transaction, MobileCrash, or SystemSample. Event namespaces are associated with a specific data retention period.

insightsIncludedEventCount
count

Count of all events of the given insightsEventNamespace stored for the retention period included with a paid non-Insights product subscription.

For example, APM Pro subscriptions include several days' retention of Transaction events. This attribute represents a count of events existing in storage as measured on a given day, and not a count of the events added to storage during a given day. Summing this attribute over a period of more than a day may not give you what you expect; for example, it will not yield the total volume of events written to storage in that period.

insightsIncludedRetentionInHours

Number of hours for which events of the given insightsEventNamespace are stored but are not counted toward your paid Insights Pro subscription.

For more information about the data reported in nrDailyUsage, see Insights usage: Attributes and queries.

insightsNrProduct

New Relic product (Insights, APM, Browser, Mobile, etc.) that corresponds to the given insightsEventNamespace.

insightsTotalEventCount
count

Count of all events stored for the given insightsEventNamespace as of the given day.

Sum of insightsIncludedEventCount and the number of events stored beyond the retention period included with a paid non-Insights product subscription. This attribute represents a count of events existing in storage as measured on a given day, and not a count of the events added to storage during a given day. Summing this attribute over a period of more than a day may not give you what you expect; for example, it will not yield the total volume of events written to storage in that period.

insightsTotalRetentionInHours

Number of hours for which events of the given insightsEventNamespace are stored.

instanceSizeCapped

This is True if the calculated host size was greater than 16 and therefore capped.

isPrimaryApp

Boolean. true means the application is the primary app. false means the app is one of several apps that an agent reports data for. Deprecated.

For more on multiple app names in APM and Browser, see Use multiple names for an app. The sum of events where this attribute is true will give an accurate total of page views when you are using the multiple app names feature. Counting events where this attribute is false will result in over-counting of usage.

masterAccountId
ID

The ID 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 account is the consuming account, masterAccountId is the consumingAccountId. 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.

masterAccountName

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 account is the consuming account, masterAccountName is the same as consumingAccountName. 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.

missingCpuData

This is True if the APM agent reports no CPU count.

missingRamData

This is True if the APM agent reports no memory count.

mobileAppId
ID

ID uniquely identifying the application reporting this usage, as it appears in the Mobile product.

mobileAppName

Name of the application reporting this usage, as it appears in the Mobile product.

mobileUniqueUsersPerMonth
count

Number of unique users (device IDs) counted during the current calendar month to date for a Mobile app.

partnershipId
ID

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.

partnershipName

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.

productLine

The New Relic product the usage data is from. Use this attribute to identify / filter for product specific usage data.

subAccountId
ID

ID of the child account (also known as the sub-account) responsible for the stored event. When present, subAccountId is the same as consumingAccountId.

This attribute is only present if the consuming account is a child account (not a parent account).

subAccountName

Name of the child account (also known as the sub-account) responsible for stored events. When present, this is the same as consumingAccountName.

This attribute is only present if the consuming account is a child account (not a parent account).

syntheticsFailedCheckCount
count

Number of failed checks that ran on the given day for the given synthetic monitor and location.

Failed checks count toward subscription usage for synthetics. Only checks with syntheticsType not equal to SIMPLE count toward billable subscription usage.

syntheticsLocation

Location the check ran in.

syntheticsLocationLabel

Human-readable label for the location of the check.

For more information about the data reported in nrDailyUsage, see Insights usage: Attributes and queries.

syntheticsMonitorId
ID

Unique ID of the monitor.

syntheticsMonitorName

Name of the monitor.

syntheticsSuccessCheckCount
count

Number of successful checks that ran on the given day for the given synthetic monitor and location.

Only checks with syntheticsType not equal to SIMPLE count toward billable subscription usage.

syntheticsType

The type of Synthetics monitor. Possible values: SIMPLE, BROWSER, SCRIPT_BROWSER, SCRIPT_API.

For more information, see Types of synthetic monitors.

syntheticsTypeLabel

Human-readable label for syntheticsType. Possible values: Ping, Simple Browser, Scripted Browser, Scripted API.

timestamp

UNIX timestamp (seconds since epoch) of the day and time when event generation was initiated.

usageType

For APM, this value can be either Application or Host, depending on the type of entity this event records usage for (other New Relic products will have different values for usageType).

Events with both values are recorded so that usage data can be analyzed in several ways. For Application: the event represents usage for a single unique application instance for that day. For Host: the event represents usage for a single unique host for that day. Only Host entities are used to calculate billable usage. Application entities are useful for comparing usage between applications, but are not used for billing or contract purposes.