New Relic Coverage
Inventory of New Relic users, ingested data, entities and synthetic monitors, savings findings on seats, ingest and checks, and monthly spend estimated from the account's own usage data.
3 min read
How it works
Inventory, findings and cost estimates run today.
- Inventory
- Discovers every user of the organization (all authentication domains) with their user type and last activity, every event type the account ingests with its monthly volume and who reads it, the monitored services, hosts and apps, and the synthetic monitors.
- Cost visibility
- New Relic has no billing API, so spend is estimated: billable data ingest and paid seats from the NrMTDConsumption usage event, priced at New Relic's list prices for your edition, data option and data center.
- Optimization
- Flags Full platform and Core users with no logins or UI queries in the last 30 days, event types no query, dashboard or alert has read in 30 days, DEBUG/TRACE logs that make up a large share of log ingest, non-ping synthetic monitors running more often than every 15 minutes once the account is over its included checks, and entities that stopped reporting. Ingest savings only count GB beyond the free 100 GB.
Coverage by service
One card per service. Each card lists its resource types and the capabilities they support.
Entities
-
Entities
Data
-
Event Types
Synthetics
-
Synthetic Monitors
Users
-
Users
Costs
Estimated monthly, from usage.
One row per month and meter lands in the costs dashboard under the New Relic service: data ingest beyond the free 100 GB, split by source (logs, traces, metrics...), Full platform users and Core users. Prices are the published list prices (Pro uses the annual-commitment seat price), so negotiated contracts differ. Compute (CCU) usage is not priced: New Relic publishes no CCU list price.
User API key
The key acts as its user — create it as an organization admin.
Create a User key in New Relic at API keys (the account's credentials tab links there). License and browser keys only send data and cannot query it. The user list needs a key whose owner can read user management, which in practice means an organization admin. Nothing this app does needs write access.
Go to Organization → Integrations → Cloud Accounts → Add Account, pick New Relic, and fill in the key and the account ID.
Plan options
What the cost estimates are priced with.
Pick the data center the account lives in (US or EU — the EU adds a per-GB surcharge), your edition (Free, Standard or Pro) and your data option (Original Data or Data Plus). New Relic's API doesn't expose them, and they only change the estimates, never what is collected.
Data usage queries
Run at most once a day.
Measuring each event type's volume and who reads it scans the account's data, and New Relic bills compute for those queries — so they run at most once a day per account, not on every hourly inventory sync. Alert conditions are read too: alerts don't show up as queries, and data only an alert uses is never reported as unused.
First sync
Once the account is saved, inventory runs on the next hourly cycle — or trigger it immediately from the account's detail page. Discovered users, data, entities and monitors appear under Audit → New Relic.