- 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.
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. Usage timestamps correspond to the time that New Relic receives and processes a synthetic check. This may introduce a slight difference in usage data compared to the time the synthetic check was executed.
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:
Most New Relic organization have the ability to add core users. This section includes queries that will work for those organizations. If you're in an older organization that hasn't opted in to unlock core users, see Queries for organizations without core users.
Here are some rules for querying your users:
- Use only the
- The attributes used to query by user type are:
Here are some example NRQL queries for determining user count:
This query shows the billable full platform users for the month. In other words, it shows how much you'd be billed for your full platform users for that month if you were billed right now.
FROM NrMTDConsumption SELECT latest(FullPlatformUsersBillable)
This query shows the number of core users you'd be billed for if you were billed right now:
FROM NrMTDConsumption SELECT latest(CoreUsersBillable)
Here's a query for getting the current month's cost for your full platform users. Note that you'll have to know your organization's full platform user cost.
FROM NrMTDConsumption SELECT latest(FullPlatformUsersBillable) * YOUR_PER_FULL_PLATFORM_USER_COST
These queries apply for some older New Relic organizations that have only two user types available: basic users and full platform users.
Here are some query recommendations for helping you understand the estimated cost for the current month.
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.