Update infrastructure on-host integrations

Infrastructure on-host integrations do not update themselves automatically. To update them, use your package manager to update the programs and their dependencies to the latest version. We recommend that you keep both the infrastructure agent and the integration files up to date.

Find on-host integration versions

Use either of these options to check whether your infrastructure on-host integration is up to date:



New Relic UI

To use the Infrastructure UI to check for on-host integrations versions:

  1. Go to one.newrelic.com > Infrastructure.
  2. In the search bar, type the name of the integration file that was installed (for example, nri-cassandra).
  3. Select the relevant dropdown to see the agent versions.


To manually check for on-host integration versions, connect to a server. Then invoke the OS package manager and grep the integration's file name (for example, nri-cassandra):

  • Debian or Ubuntu:

    dpkg -l | grep INTEGRATION_FILE_NAME
  • Amazon Linux, CentOS, SLES, or RHEL:

    rpm -qa | grep INTEGRATION_FILE_NAME
  • Windows Server

    In PowerShell:

    get-package -name "*INTEGRATION_FILE_NAME*" | select name, version

    For example, if you wanted to find Cassandra:

    get-package -name "*nri-mssql*" | select name, version

To find the file name for a specific integration, see the integration documentation.

Pick your update method based on your environment

Your services may be running on a single physical host, on a VM, or in a container orchestrated by Kubernetes or ECS. Whatever the setup, our on-host integrations can adapt to your environment and send data to New Relic; all you have to do is choose the appropriate update method.

You're running services in orchestrated environments

If you are running services in containerized, orchestrated environments, choose your update scenario:

Our on-host integrations and the ECS and Kubernetes integration can run together; see Intro to Kubernetes integration and Intro to ECS integration to learn more.

You're running on-premises services or services on single VMs

If you are running services without orchestration or on-premises, choose your scenario: