• Log inStart now

Query and alert on usage data

For accounts on our usage-based pricing model, we provide a usage UI for understanding your billing-related usage and a UI for managing billing-related data. Additionally, you can:

Note that if you're on our original user model, your account hierarchy may affect your queried data. For more information, see Account structure.

Data ingest usage queries

The usage UI displays your data ingest over time. If you need more detail than the UI provides, here are some example NRQL queries:

Data ingest and query limits

For information about data ingest limits and query limits, see Query system limits.

Synthetics usage

There are a certain number of synthetics checks included for free with each edition. For details on that, see Synthetics limits.

The NrDailyUsage event is the event type that can best help you understand synthetics usage. It's generated once per day.

By using FACET, you can break your consumption into multiple categories, including account, location, monitor type, and monitor name. If you have a parent account structure, ensure you run queries in a parent account to see the aggregated usage for that parent and its child accounts.

Both successful and failed checks contribute to overall synthetics consumption. Below are sample queries to view and facet your synthetics consumption:

User count queries

For a display of your user count, see the usage UI. If you need more detail than that, you can use the example NRQL queries below. For details about how users are calculated, see User calculations.

We have two versions of our usage-based pricing model, and the version you're on impacts how your billable users are calculated, and thus affects how you query those users:

Here are example queries for these two pricing versions:

Cost-related queries

Here are some query recommendations for helping you understand the estimated cost for the current month.

Set usage alerts

To help manage your billing, you can set alerts to notify you of unexpected increases in data ingest or user count.

Before building usage-related alert conditions, here are some tips:

Here are some NRQL alert condition examples.

For setting up alerts related to data ingest limits and query limits, see Set alerts for hitting data limits.

Query changes to your account

To see changes made to your account (for example, changes related to managing users), you can query NrAuditEvent.

Usage-related data types

Tip

For an advanced deep dive into managing data ingest in a complex organization, see Data ingest governance.

Usage data is attached to the following events. For more detail on which event to use for querying users, see Query users.

  • NrUsage records usage every hour and is used to see the types of data being reported (for example, APM data or browser monitoring data).
  • NrConsumption records usage every hour, and is the equivalent of "real-time" usage. Use this event to observe usage trends over time.
  • NrMTDConsumption generates aggregate values from the NrConsumption event. Use this event to see usage by monthly billing period. For organizations on the core users release, this is the best event for querying user count.

Data ingest attributes

Below are some of the most important attributes attached to usage events.

Attribute

Description

productLine

The category of usage. There are three options: DataPlatform, FullStackObservability, and ProactiveDetection. (Starting November 1, 2021, IncidentIntelligence is no longer a billing factor.) For more details about these categories, see New Relic platform.

metric

This consolidates multiple categories of usage into a single metric. Helpful when faceting by productLine. It's an enum with possible values of BasicUsers, FullUsers, and GigabytesIngested. Values for the core user release include FullPlatformUsers and CoreUsers.

consumingAccountId

ID of the New Relic account directly responsible for the stored events, as determined from the license key used.

Copyright © 2022 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.