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:

Option	Comments
New Relic UI	To use the Infrastructure UI to check for on-host integrations versions: Go to one.newrelic.com > Infrastructure. In the search bar, type the name of the integration file that was installed (for example, `nri-cassandra`). Select the relevant dropdown to see the agent versions.
Server	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`

Option

Comments

New Relic UI

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

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

Server

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:

Update on-host integrations on Kubernetes
Update on-host integrations on Amazon ECS (EC2 launch type)

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:

Here are two approaches, depending on the integration you're using.

On-host Microsoft Windows services integration

The Microsoft Windows services integration is bundled with the New Relic infrastructure agent, so to update the integration, you need to update the infrastructure agent. See Update the infrastructure agent.

All other on-host Microsoft Windows integrations

You can update integrations for services running on Windows Server with our MSI installer or the official zip files. We recommend the MSI installation.

Download the latest MSI installer image from our repository.
In an admin account, run the install script using an absolute path.
```
msiexec.exe /qn /i PATH\TO\INSERT_THE_INTEGRATION_NAME.msi
```
Restart the infrastructure agent.

Recommendation: Update the infrastructure agent (version 1.0.703 or higher).

To update the on-host integration using apt-get:

From the command line, run:
```
sudo apt-get update
```
Run this command using the integration file name (for example, nri-cassandra):
```
sudo apt-get install --only-upgrade INSERT_THE_INTEGRATION_FILE_NAME
```
Restart the infrastructure agent.

Recommendation: Update the infrastructure agent (version 1.0.703 or higher).

To update the on-host integration using yum:

From the command line, run this command using the integration file name (for example, nri-cassandra):
```
sudo yum update INSERT_THE_INTEGRATION_FILE_NAME -y
```
Restart the infrastructure agent.

Recommendation: Update the infrastructure agent (version 1.0.703 or higher).

To update the on-host integration using Zypper:

From the command line, run this command using the integration file name (for example, nri-cassandra):
```
sudo zypper update INSERT_THE_INTEGRATION_FILE_NAME -y
```
Restart the infrastructure agent.

Tip

We recommend that you use your distribution package manager to install the infrastructure agent. If you choose to manually install the agent, you may also want to install the on-host integrations from the provided tarballs.

The manual install process is not automated. If you opt for manual install, you must place the different files in the correct folders, and ensure that the agent has all the permissions to execute the integrations.

To install an integration from a tarball:

Download the packaged integration file from the tarball repository.
Unpack the tarball file according to our integration file structure and placement rules, so the agent is able to find the definitions, configurations, and executables of the integration.
Place the binary that contains the definition file inside newrelic-integrations or custom-integrations in the agent directory.
Place the integration's config file under the plugin directory.

For integrations that require our nrjmx tool, follow these additional instructions:

Some integrations (such as JMX, Cassandra, and Kafka) require the nrjmx tool. If your integration needs this, download it from our repository and unpack it.

Important

nrjmx requires Java 8 or higher.

For JMX integration version 2.3.3 or higher and Cassandra integration version 2.3.0 or higher, the nrjmx tool is included as a dependency. For this reason, when using a package manager, the nrjmx tool doesn't have to be installed manually.

If you have nrjmx already installed and install nri-jmx, our JMX tool keeps the already-installed version. If you don't have nrjmx already installed, it gets the latest nrjmx release.

By default, the nrjmx location is /usr/bin/nrjmx/*. To install in a different location, set the new path in the NR_JMX_TOOL environment variable.

Update infrastructure on-host integrations

Find on-host integration versions

Pick your update method based on your environment

You're running services in orchestrated environments

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

Update using MSI files ( Windows Server)

Update with apt (Debian, Ubuntu)

Update with yum (Amazon Linux, CentOS, RHEL)

Update with zypper (SLES)

Update from tarball (Other distros)

Tip

Important