- 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.
Note that account hierarchy may affect queried data. See Account structure.
Usage data is attached to these events:
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 or estimated cost for a billing period.
NrUsagerecords usage every hour and is used to see usage reported per product.
To see changes made to your account (for example, user management changes), you can query
Here are some data usage query examples:
Here are some user-related query examples. For details on how users are counted, see User count calculations.
When creating alert conditions, you should set the Evaluation offset value to 60 minutes or your conditions may not trigger.
Here are some NRQL alert condition examples. For attribute definitions, see Attributes.
Below are some of the important attributes attached to usage events.
The category of usage. There are four options:
Consolidates multiple categories of usage into a single metric. Helpful when faceting by productLine.
ID of the New Relic account that is directly responsible for the stored events, as determined from the license key used.
Calculates a cost estimate based on usage and metric cost. This is an estimate of costs to date, not your monthly invoice.
For more attributes, see the data dictionary.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.