• EnglishEspañol日本語한국어Português
  • Log inStart now

Understand and manage data ingest

You may want to manage your New Relic data ingest for several reasons, including:

Data ingest UI

The Data ingestion tab is located in the Data management UI. The data ingestion UI shows a summary of your usage by data source. For organizations with multiple accounts, you can also view the usage of specific accounts.

From the user menu, select Manage your data.

For detailed definitions of the metrics shown in the chart, see Data ingest sources.

To see the underlying NRQL query used to create that chart, click View NRQL.

For a video showing a brief tour of this and other administration UIs, see Account settings.

Get more detail

To get more detail about a specific data source shown in the chart, hover over the band in the chart and click it. A modal will open up, as shown in the image below.

When you click on a band in the ingestion chart, you'll get more details about that data.

For some technical details about how the chart displays data and error messages, see Chart details.

Estimate future data ingest

If you're trying to estimate future data ingest, see this blog post on estimating ingest.

Manage ingest and avoid ingest spikes

How you manage your New Relic data will depend on a lot of factors specific to your organization and your needs. That said, here are some general tips for managing data ingest and avoiding unexpected spikes:

  • Assign team members. Assign team members who'll be in charge of reviewing your ingest on a cadence, and managing it. Ensure they understand the data-related billing factors, including what does and doesn't count towards billing.
  • Get to know your data. Spend some time getting acquainted with your data. Get to know its ebbs and flows, and understand where it's coming from.
  • Monitor when you make significant changes. When you first activate a new data-reporting tool, or when you upgrade an agent or integration, or when you make any big change in your system, you should monitor your ingest to ensure there's no unexpected spike in data.
  • Set up alerts. If you're concerned about specific scenarios causing sudden spikes in data, set up an alert condition to notify you if that occurs. For tips on that, see Usage queries.

Reducing ingest

Below are some tips for common approaches New Relic customers take to reduce the ingest of data that's not helpful to them.

All New Relic solutions have various configuration options that give you control over how data is reported to New Relic. Below we have some popular methods for reducing data ingest, but to learn about all the options available, we recommend reading the docs for specific tools you're using.

Data ingestion sources

The data ingestion UI chart shows you a high level breakdown of your billable data usage. The table below explains those sources. In this table, "usage metric group" refers to the value of that source's usageMetric attribute value on the NrConsumption event.

Optimize your data ingest

We also have an in-depth tutorial on how to optimize data ingest.

Stream ingested data

For more about streaming ingested data to other sources, see Streaming export.

Data from multiple data center regions

If you have accounts in multiple data center regions, learn more about how to understand your usage.

Technical details about the ingestion chart

Some technical details about the ingest UI:

  • Displays are estimates. The ingest value shown on the ingest chart can vary slightly from the actual amount you may see when running your own query. This is because the calculation used for the chart is an estimate.
  • No chart data available. The data ingestion chart can display a slightly longer time frame than that covered by your data retention settings. For this reason, you may get message that there's no chart data available.
  • Chart time buckets. If an account has less than a terrabyte of data, we compute the volume over a 24-hour period; otherwise, we compute it for a 1-hour period.
Copyright © 2024 New Relic Inc.

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