---
title: Introduction to Adaptive Telemetry Processor (ATP)
source: https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/overview
---

> #### 💡 PREVIEW
>
> We're still working on this feature, but we'd love for you to try it out!
>
> This feature is currently provided as part of a preview pursuant to our [pre-release policies](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).

The Adaptive Telemetry Processor (ATP) is an intelligent metric filtering processor for the New Relic Distribution for OpenTelemetry (NRDOT) Collector. ATP dynamically monitors system and process metrics, filtering out low-value telemetry based on configurable thresholds while preserving critical visibility during performance events.

## Why ATP matters

Traditional monitoring approaches create several challenges:

-   Data overload: High-volume telemetry data from all processes increases costs without proportional value
-   Visibility gaps: Stateless filtering creates "data gaps" where processes constantly appear and disappear from telemetry as they fluctuate around thresholds
-   Lack of context: Important processes may be missed during brief but critical resource spikes
-   Manual tuning: Static thresholds require constant adjustment as system conditions change

## What is ATP

Instead of simple threshold-based filtering, ATP combines:

-   Process-based sampling: Monitor specific processes as per your requirement.
-   Multi-metric composite scoring: Combine multiple metrics with configurable weights for holistic assessment
-   Dynamic threshold adjustment: Automatically adapt thresholds based on historical baselines
-   Anomaly detection: Detect sudden metric changes and preserve anomalous data
-   Persistent state management: Maintain context across collector restarts

/\* ## What ATP offers

\### Significant data reduction with maintained visibility

\* Reduction in data ingestion while keeping more context-aware data
\* Eliminates data gaps that traditional stateless filtering creates
\* Preserves critical context through configurable retention periods


\### Two-phase evolution
ATP delivers value through a phased approach:

\* \*\*Phase 1: Stateful retention strategy\*\*

    \- Threshold-based tracking with persistent state
    \- Configurable retention periods for processes exceeding thresholds
    \- Persistent storage across collector restarts

\* \*\*Phase 2: Fully intelligent adaptive system\*\*

    \- Dynamic thresholds that adapt to system load
    \- Multi-metric evaluation using composite scoring
    \- Anomaly detection for sudden usage spikes

\### Enterprise-ready features

\* Lightweight storage: Requires only 5-10MB of storage for tracking state
\* Restart resilience: Maintains tracking context across collector restarts
\* Configurable behavior: Customizable thresholds, retention periods, and weights
\* Universal compatibility: Works with any resource type monitored by NRDOT \*/

## How it works

ATP processes telemetry data through an intelligent filtering system:

-   Process identification: Monitors all processes for resource usage patterns
-   Threshold evaluation: Compares current usage against configured or dynamic thresholds
-   Retention tracking: Maintains state for processes that exceed thresholds
-   Intelligent sampling: Applies advanced logic including anomaly detection and multi-metric evaluation
-   Data forwarding: Sends only relevant telemetry data to New Relic

/\* ## Next steps

Ready to start optimizing your infrastructure monitoring with ATP? Learn how to:

\* \[Set up ATP](#) - Configure ATP in your NRDOT deployment
\* \[Configure retention strategies](#) - Customize thresholds and retention periods
\* \[Monitor ATP performance](#) - Track data reduction and system impact


  ATP is designed for organizations looking to optimize infrastructure monitoring costs while maintaining comprehensive visibility into critical processes.
 \*/

## Related resources

[ATP for host](https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/host)

Learn about setting up ATP for your host environment.

[ATP for Kubernetes](https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/k8s)

Learn how to set up the ATP for your Kubernetes environment.

[Advanced-features](https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/advanced-features)

Learn how to enable advanced features for your ATP deployment.