--- title: Optimize your telemetry data with New Relic source: https://docs.newrelic.com/docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry --- Telemetry data, or data that's collected from one source and reported to a monitor for analysis, is becoming increasingly used in modern organizations with multiple data sources to collect. But navigating and managing that data comes with its own considerations, and optimizing how you deal with your telemetry data can save you time and money. This is especially true for complex organizations that have numerous business units and working groups. This is where **Data ingest governance**, or the practice of ensuring optimal value for the telemetry data your organization has collected, comes in. Our guide will help you prepare for and carry out the best practices for using this concept within your oganization. After completing this tutorial series, you'll: - Reduce redundant or unnecessary telemetry data, saving you time and money. - Understand exactly which groups within the organization are contributing which data. - Expose where your telemetry data is coming from and reduce data management silos. - Account for ingest costs in a clear and concise way. - Adjust your ingest volume with full context of the observability value of the data. ![A diagram displaying the path for setting up data ingest governance with New Relic. The path is 1. Baseline your data, 2. detect anomalies, and 3. optimize your telemetry](https://docs.newrelic.com/images/telemetry_diagram_data-ingest-path.webp "Data ingest governance path") ## Before you begin [#before-begin] You'll need to make sure that you have data managed with New Relic so that you can use **data ingest governance** to optimize it. See our [data management doc](https://docs.newrelic.com/docs/data-apis/manage-data/manage-your-data/) if you need more information. **Understand consumption event types** All billable telemetry is tracked with our `NrConsumption` and `NrMTDConsumption` events. This guide focuses on how to query `NrConsumption`, which provides more granular, real-time data than `NrMTDConsumption`. The `NrConsumption` attribute `usageMetric` denotes the telemetry type. Using `NrConsumption`, you can ask questions like "How much browser monitoring data has each account ingested in the last 30 days?" and "How has the ingest changed since the previous 30 days?" Here's a query returning that data: ```sql FROM NrConsumption SELECT sum(GigabytesIngested) WHERE usageMetric = 'BrowserEventsBytes' SINCE 30 days AGO COMPARE WITH 30 days AGO FACET consumingAccountName ``` The response shows you how many GBs of browser monitoring data you've ingested by account. ```shell Banking platform, 75 GB, +2.9% Marketing platform, 40 GB, -1.3% ``` Below is a breakdown of the different `usageMetric` types, the constituent events (event types where the data is stored), and the type of agent or mechanism responsible for creating the data ingest. ### Billable telemetry breakdown table | NrcConsumption.usageMetric | Constituent events | Source | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | InfraHostBytes | `SystemSample`, `StorageSample`, `InfrastructureEvent`, `NetworkSample` | Infrastructure agent | | InfraProcessBytes | `ProcessSample` | Infrastructure agent | | InfraIntegrationBytes | Various events for third party platform integrations as well as `ContainerSample` | [On-host integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) and certain [cloud integrations](https://docs.newrelic.com/docs/infrastructure/infrastructure-integrations/get-started/introduction-infrastructure-integrations/#cloud) | | ApmEventsBytes | `Transaction`, `TransactionError`, and possibly `WorkloadStatus` | APM agent(s) | | TracingBytes | `Span`, `SpanEvent` | APM agent(s) and OpenTelemetry | | BrowserEventsBytes | `Browser`, `BrowserInteraction`, `Browser:EventLog`, `Browser:JSErrors`, `JavaScriptError`, `PageView`, `PageViewTiming`, `PcvPerf` | Browser agent | | MobileEventsBytes | `Mobile`, `MobileReqest`, `MobileRequestError`, `MobileSession`, `MobileHandleException`, `MobileCrash` | Mobile agent | | SeverlessBytes | Cloud-specific (i.e., AWS Lambda events) | Cloud-specific (i.e., AWS Lambda integration) | | LoggingBytes | `Log` as well as partition-specific events of the pattern `[partition].Log` | Various (Fluentd, FluentBit, Syslog, cloud-specific streaming services) | | MetricEventBytes | `Metric` | From the Metric API and integrations that use that ([dimensional metrics](https://docs.newrelic.com/docs/data-apis/understand-data/new-relic-data-types/#dimensional-metrics)), or from agents such as browser agent, APM agent, or mobile agent ([metric timeslice data](https://docs.newrelic.com/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data)). | | CustomEventBytes | Various | Various APIs. [Use `SHOW EVENT TYPES` to view all event types available in an account](#show-event-types). | You'll also need to ensure that you or your team have the ability to track and manage: - Working with a manager to stay within monthly ingest targets, if applicable. - Monitoring data ingest baselines and respond to anomalies. - Drafting and approving plans for data optimization/reduction as needed. - Participating in scheduled check-ins for analyzing baseline data and comparing it to ingest targets. - Making modifications to ingest targets as needed. If you don't already, you should consider having an observability center of excellence team (or something similiar) which is responisble for: - Maintaining the relationship with New Relic. - Governing accounts and users. - Onboarding new teams and individuals. - Maintaining an observability knowledge base. - Promoting collaboration and sharing among teams. Having a team like this can be instrumental in helping you achieve high quality observabilty for your entire organization. ## What's in this series? [Create baseline reports](https://docs.newrelic.com/docs/tutorial-optimize-telemetry/create-baseline-report/) Learn how to use the correct dashboard to create your ingest baselines [Find anomalies](https://docs.newrelic.com/docs/tutorial-optimize-telemetry/detect-anomalies/) Learn how to use your baseline report to help you find anomalies with your telemetry [Create an optimization plan](https://docs.newrelic.com/docs/tutorial-optimize-telemetry/develop-optimize-plan/) Learn how to develop an optimization plan to help reduce your ingest costs [Optimize your ingest data](https://docs.newrelic.com/docs/tutorial-optimize-telemetry/data-optimize-techniques/) Learn how to use various techniques to optimize your overall ingest