--- title: Update infrastructure on-host integrations source: https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/update-infrastructure-host-integration-package --- Our 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](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent) and the integration files up to date. ## Find on-host integration versions [#check-version] Use either of these options to check whether your on-host integration is up to date: | **Option** | **Comments** | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | New Relic UI | To use the infrastructure UI to check for on-host integration versions: - Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > 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**: ```bash dpkg -l | grep INTEGRATION_FILE_NAME ``` - **Amazon Linux, CentOS, SLES, or RHEL**: ```bash rpm -qa | grep INTEGRATION_FILE_NAME ``` - **Windows Server** In PowerShell: ```powershell get-package -name "*INTEGRATION_FILE_NAME*" | select name, version ``` For example, if you wanted to find Cassandra: ```powershell get-package -name "*nri-cassandra*" | select name, version ``` | To find the file name for a specific integration, see the [integration docs](https://docs.newrelic.com/docs/infrastructure/host-integrations). ## Pick your update method based on your environment [#install] 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 [#orchestrated] If you're running services in containerized, orchestrated environments, choose your update scenario: - ![Kubernetes](https://docs.newrelic.com/images/os_icon_k8.webp "Kubernetes") [Update on-host integrations on Kubernetes](https://docs.newrelic.com/docs/integrations/kubernetes-integration/link-apps-services/monitor-services-running-kubernetes) - ![ECS](https://docs.newrelic.com/images/os_icon_ecs.webp "ECS") [Update on-host integrations on Amazon ECS](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/monitor-services-running-amazon-ecs) (EC2 launch type) ### You're running on-premises services or services on single VMs [#standard] If you're running services without orchestration or on-premises, choose your scenario: **Update using MSI files ( Windows Server)** Here are three approaches, depending on the integration you're using. **On-host Microsoft Windows services integration** The [Microsoft Windows services integration](https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/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](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/update-infrastructure-agent). **Nri-kafka, nri-jmx integration** These two integrations have .exe installers 1. Download the latest .exe installer for New Relic's integration [from out repository](https://download.newrelic.com/infrastructure_agent/windows/integrations) 2. To install from the Windows command prompt, run: ```bash PATH\TO\YOUR_INTEGRATION_FILE_NAME.exe ``` **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. 3. Download the latest MSI installer image [from our repository](https://download.newrelic.com/infrastructure_agent/windows/integrations/). 4. In an admin account, run the install script using an absolute path. ```bash msiexec.exe /qn /i PATH\TO\YOUR_INTEGRATION_FILE_NAME.msi ``` **Update with apt (Debian, Ubuntu)** Recommendation: [Update](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent) the infrastructure agent ([version 1.0.703 or higher](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes)). To update the on-host integration using `apt-get`: 1. From the command line, run: ```bash sudo apt-get update ``` 2. Run this command using the integration file name (for example, `nri-cassandra`): ```bash sudo apt-get install --only-upgrade YOUR_INTEGRATION_FILE_NAME ``` 3. [Restart](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#linux) the infrastructure agent. **Update with yum (Amazon Linux, CentOS, RHEL)** Recommendation: [Update](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent) the infrastructure agent ([version 1.0.703 or higher](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes)). To update the on-host integration using `yum`: 1. From the command line, run this command using the integration file name (for example, `nri-cassandra`): ```bash sudo yum update YOUR_INTEGRATION_FILE_NAME -y ``` 2. [Restart](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#linux) the infrastructure agent. **Update with zypper (SLES)** Recommendation: [Update](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent) the infrastructure agent ([version 1.0.703 or higher](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes)). To update the on-host integration using Zypper: 1. From the command line, run this command using the integration file name (for example, `nri-cassandra`): ```bash sudo zypper update YOUR_INTEGRATION_FILE_NAME -y ``` 2. [Restart](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status#linux) the infrastructure agent. **Update from tarball (Other distros)** > #### 💡 TIP > > We recommend that you [use your distribution package manager to install the infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/install-infrastructure-linux-using-package-manager). If you choose to [manually install the agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/tarball-manual-install-infrastructure-linux), 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: 1. Download the packaged integration file from the [tarball repository](https://download.newrelic.com/infrastructure_agent/binaries/linux/amd64/). 2. Unpack the tarball file according to our [integration file structure and placement rules](https://docs.newrelic.com/docs/integrations/integrations-sdk/getting-started/integration-file-structure-activation), so the agent is able to find the definitions, configurations, and executables of the integration. 3. Place the binary that contains the definition file inside `newrelic-integrations` or `custom-integrations` in the [agent directory](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/tarball-manual-install-infrastructure-linux#agent-directory). 4. Place the integration's config file under the [plugin directory](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/linux-installation/tarball-manual-install-infrastructure-linux#configure-plugin). For integrations that require our `nrjmx` tool, follow these additional instructions: Some integrations (such as [JMX](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/jmx-monitoring-integration), [Cassandra](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/cassandra-monitoring-integration), and [Kafka](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration)) require the `nrjmx` tool. If your integration needs this, download it from [our repository](https://download.newrelic.com/infrastructure_agent/binaries/linux/noarch/) 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.