• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

Configure ATP for host

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.

Learn how to install and configure the Adaptive Telemetry Processor (ATP) with the NRDOT Collector. ATP is included with the standard NRDOT distribution to reduce telemetry data volume while maintaining critical visibility.

Installation options

Choose the installation approach that matches your current setup:

Before you begin

Ensure you have:

  • Your New Relic license key
  • Root or sudo privileges.
  • Network access to GitHub releases

Install NRDOT collector host

ATP comes pre-packaged with the NRDOT collector distribution. Based on your OS, choose your installation method:

Configure ATP

Once the NRDOT collector is installed, edit the collector's configuration file to enable and customize ATP. The configuration file paths vary depending on your installation method:

  • For DEB/RPM installations, the config file is located at /etc/nrdot-collector/config.yaml.
  • For manual binary installations, the config file is located inside the extracted folder.

To edit the configuration file:

  1. Open the configuration file (config.yaml) with a text editor:

    • For DEB/RPM installations:

      bash
      $
      sudo nano /etc/nrdot-collector/config.yaml
    • For manual binary installations:

      bash
      $
      nano config.yaml
  2. To collect the process metrics, in the scrapers section of hostmetrics receiver, add the following process configuration:

    receivers:
    hostmetrics:
    scrapers:
    # Your existing scrapers...
    process:
    metrics:
    process.cpu.utilization:
    enabled: true
    process.memory.utilization:
    enabled: true
    mute_process_name_error: true
    mute_process_exe_error: true
    mute_process_io_error: true
    mute_process_user_error: true
  3. To enable ATP, locate the existing processors section, and add the adaptivetelemetry configuration underneath it:

    processors:
    adaptivetelemetry:
    enable_storage: true
    retention_minutes: 30
    include_process_list:
    - "/usr/bin/postgres"
    - "/usr/sbin/nginx" # Replace with your target processes
    metric_thresholds:
    process.cpu.utilization: 0.05 # 5% CPU
    process.memory.utilization: 0.05 # 5% memory
  4. Add the ATP processor to your metrics pipeline under the service section:

    service:
    pipelines:
    metrics/host:
    receivers: [hostmetrics]
    processors:
    - memory_limiter
    - adaptivetelemetry # ADD THIS LINE
    - metricstransform
    - filter/exclude_cpu_utilization
    - filter/exclude_memory_utilization
  5. (Optional) Update the ATP configuration such as metric thresholds as required. For more details on configuration options, see the Configuration parameters.

  6. Save the configuration file.

  7. Restart the NRDOT collector to apply changes:

    bash
    $
    sudo systemctl restart nrdot-collector

Access the ATP data in New Relic

Once the ATP is configured, it starts collecting data from your Linux host. You can access this data in New Relic OpenTelemetry UI. For more information on New Relic OpenTelemetry UI, refer to OpenTelemetry APM UI.

To view the ATP process metric data in New Relic:

  1. Go to one.newrelic.com > All Entities.

    OR

    Go to one.newrelic.com > Catalogs > Infrastructure.

  2. Search for entity where you installed the NRDOT collector with ATP.

  3. Select the entity then click Process in the left pane.

    On the Process page, you can view all the processes running on your host, along with their IDs, CPU and memory utilization metrics. It also displays the parent-child relationship between processes if a process spawns other processes.

    ATP process metrics in New Relic OpenTelemetry UI

Before you begin

Ensure you have:

  • Existing NRDOT Collector version 1.11.0 or later
  • Your New Relic license key
  • Root or sudo privileges
  • Backup of current configuration

Backup current configuration

Safeguard your current settings before proceeding:

bash
$
sudo cp /etc/nrdot-collector/config.yaml /etc/nrdot-collector/config.yaml.bak

Upgrade NRDOT collector

To upd the NRDOT collector to the latest version with ATP support, rerun the installation commands for the latest version. This will overwrite the old binary while preserving your existing configuration file.

Configure ATP

The upgrade preserved your previous settings, so your config.yaml doesn't yet contain the new ATP settings. You must add them manually.

To edit the configuration file:

  1. Open the configuration file (config.yaml) with a text editor using root or sudo privileges:

    • For DEB/RPM installations:

      bash
      $
      sudo nano /etc/nrdot-collector/config.yaml
    • For manual binary installations:

      bash
      $
      nano config.yaml
  2. To collect the process metrics, in the scrapers section of hostmetrics receiver, add the following process configuration:

    processes:
    process:
    metrics:
    process.cpu.utilization:
    enabled: true
    process.memory.utilization:
    enabled: true
    mute_process_name_error: true
    mute_process_exe_error: true
    mute_process_io_error: true
    mute_process_user_error: true
  3. To enable ATP, locate the existing processors section, and add the adaptivetelemetry configuration underneath it:

    processors:
    # Your existing processors...
    adaptivetelemetry:
    enable_storage: true
    retention_minutes: 30
    include_process_list:
    - "/usr/bin/postgres"
    - "/usr/sbin/nginx" # Replace with your target processes
    metric_thresholds:
    process.cpu.utilization: 0.05 # 5% CPU
    process.memory.utilization: 0.05 # 5% memory
  4. Add the ATP processor to your metrics pipeline under the service section:

    service:
    pipelines:
    metrics/host:
    receivers: [hostmetrics]
    processors:
    - memory_limiter
    - adaptivetelemetry # ADD THIS LINE
    - metricstransform
    - filter/exclude_cpu_utilization
    - filter/exclude_memory_utilization
  5. (Optional) Update the ATP configuration such as metric thresholds as required. For more details on configuration options, see the Configuration parameters.

  6. Save the configuration file.

  7. Restart the NRDOT collector to apply changes:

    bash
    $
    sudo systemctl restart nrdot-collector

Access the ATP data in New Relic

Once the ATP is configured, it starts collecting data from your Linux host. You can access this data in New Relic OpenTelemetry UI. For more information on New Relic OpenTelemetry UI, refer to OpenTelemetry APM UI.

To view the ATP process metric data in New Relic:

  1. Go to one.newrelic.com > All Entities.

    OR

    Go to one.newrelic.com > Catalogs > Infrastructure.

  2. Search for entity where you installed the NRDOT collector with ATP.

  3. Select the entity then click Process in the left pane.

    On the Process page, you can view all the processes running on your host, along with their IDs, CPU and memory utilization metrics. It also displays the parent-child relationship between processes if a process spawns other processes.

    ATP process metrics in New Relic OpenTelemetry UI

To install ATP by migrating from the New Relic native infrastructure agent to the NRDOT collector host distribution, you need to uninstall the native agent and set up NRDOT with ATP.

Before you begin

Ensure you have:

  • Your New Relic license key
  • Root or sudo privileges
  • Plan for minimal service interruption

Stop and disable native agent

  1. To stop the existing infrastructure agent to prevent data conflict, run:

    bash
    $
    # Stop the service
    $
    sudo systemctl stop newrelic-infra
  2. To disable the infrastructure agent from starting on boot, run:

    bash
    $
    # Disable from starting on boot
    $
    sudo systemctl disable newrelic-infra

Install NRDOT collector host

ATP comes pre-packaged with the NRDOT collector distribution. Based on your OS, choose your installation method:

Configure ATP

Once the NRDOT collector is installed, edit the collector's configuration file to enable and customize ATP. The configuration file paths vary depending on your installation method:

  • For DEB/RPM installations, the config file is located at /etc/nrdot-collector/config.yaml.
  • For manual binary installations, the config file is located inside the extracted folder.

To edit the configuration file:

  1. Open the configuration file (config.yaml) with a text editor:

    • For DEB/RPM installations:

      bash
      $
      sudo nano /etc/nrdot-collector/config.yaml
    • For manual binary installations:

      bash
      $
      nano config.yaml
  2. To collect the process metrics, in the scrapers section of hostmetrics receiver, add the following process configuration:

    receivers:
    hostmetrics:
    scrapers:
    # Your existing scrapers...
    process:
    metrics:
    process.cpu.utilization:
    enabled: true
    process.memory.utilization:
    enabled: true
    mute_process_name_error: true
    mute_process_exe_error: true
    mute_process_io_error: true
    mute_process_user_error: true
  3. To enable ATP, locate the existing processors section, and add the adaptivetelemetry configuration underneath it:

    processors:
    adaptivetelemetry:
    enable_storage: true
    retention_minutes: 30
    include_process_list:
    - "/usr/bin/postgres"
    - "/usr/sbin/nginx" # Replace with your target processes
    metric_thresholds:
    process.cpu.utilization: 0.05 # 5% CPU
    process.memory.utilization: 0.05 # 5% memory
  4. Add the ATP processor to your metrics pipeline under the service section:

    service:
    pipelines:
    metrics/host:
    receivers: [hostmetrics]
    processors:
    - memory_limiter
    - adaptivetelemetry # ADD THIS LINE
    - metricstransform
    - filter/exclude_cpu_utilization
    - filter/exclude_memory_utilization
  5. (Optional) Update the ATP configuration such as metric thresholds as required. For more details on configuration options, see the Configuration parameters.

  6. Save the configuration file.

  7. Restart the NRDOT collector to apply changes:

    bash
    $
    sudo systemctl restart nrdot-collector

Verify migration

Once the installation is successful, check that data is flowing to New Relic:

  1. To verify service status, run:

    bash
    $
    sudo systemctl status nrdot-collector
  2. To check logs, run:

    bash
    $
    sudo journalctl -u nrdot-collector -f

Access the ATP data in New Relic

Once the ATP is configured, it starts collecting data from your Linux host. You can access this data in New Relic OpenTelemetry UI. For more information on New Relic OpenTelemetry UI, refer to OpenTelemetry APM UI.

To view the ATP process metric data in New Relic:

  1. Go to one.newrelic.com > All Entities.

    OR

    Go to one.newrelic.com > Catalogs > Infrastructure.

  2. Search for entity where you installed the NRDOT collector with ATP.

  3. Select the entity then click Process in the left pane.

    On the Process page, you can view all the processes running on your host, along with their IDs, CPU and memory utilization metrics. It also displays the parent-child relationship between processes if a process spawns other processes.

    ATP process metrics in New Relic OpenTelemetry UI

Configuration parameters

Troubleshooting

Learn how to troubleshoot ATP issues for your environment.

Query your data

Learn how to query ATP data in New Relic using NRQL.

Advanced-features

Learn how to enable advanced features for your ATP deployment.

Copyright © 2026 New Relic Inc.

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