- Query your usage data to get more detail than is available in the UI.
- Set up NRQL alert conditions to get notifications about changes in your usage.
For information about data ingest limits and query limits, see Query system limits.
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:
- Our primary version (with core users): See example queries for this version.
- Our version without core users (only two available user types: basic and full platform): See example queries for this version.
Here are example queries for these two pricing versions:
In May of 2022, we deprecated the
estimatedCost attribute from usage events and removed the current month's estimated cost from the UI (learn more). If you currently use the
estimatedCost attribute in your queries or alert conditions, you should remove them, or replace them with the recommended queries below.
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:
- For basics about how to set up alerts, see NRQL alert conditions.
- The event timer aggregation method is recommended because it works best for infrequent data.
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.
To see changes made to your account (for example, changes related to managing users), you can query
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.
NrUsagerecords usage every hour and is used to see the types of data being reported (for example, APM data or browser monitoring data).
NrConsumptionrecords usage every hour, and is the equivalent of "real-time" usage. Use this event to observe usage trends over time.
NrMTDConsumptiongenerates aggregate values from the
NrConsumptionevent. 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.
Below are some of the most important attributes attached to usage events.
The category of usage. There are three options:
This consolidates multiple categories of usage into a single metric. Helpful when faceting by
ID of the New Relic account directly responsible for the stored events, as determined from the license key used.