---
title: On-host integrations: Installation and configuration
source: https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/install-infrastructure-host-integrations
---

Some of our [on-host integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) are built in a specific way and tightly bundled with the infrastructure agent, meaning they have similar install and configuration processes.

This documentation contains the basic installation procedures for these types of integrations. For technical details about how these integrations work, see [On-host integration data reporting](https://docs.newrelic.com/docs/infrastructure/host-integrations/understand-use-data/host-integration-data-collection-reporting).

## Installation methods [#install]

Your services may be running on a single physical host, on a VM, or in a container orchestrated by Kubernetes or Amazon ECS. Choose your desired installation method.

After you do the basic install of an integration, you must return to the documentation for a specific integration to read the configuration instructions.

### Orchestrated environments [#orchestrated]

Our options for containerized, orchestrated environments:

-   ![Kubernetes](https://docs.newrelic.com/images/os_icon_k8.webp "Kubernetes") [Install 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") [Install 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)

### Running on VMs or on-premises hosts [#standard]

Choose your scenario:

**Install using MSI files ( Windows)**

To install:

1.  If you don't already have it, [install the infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic).
2.  Download the latest .MSI installer image for the desired integration [from our repository](https://download.newrelic.com/infrastructure_agent/windows/integrations/).
3.  In an admin account, run the install script using an absolute path.
    ```bash
    msiexec.exe /qn /i PATH\TO\integration-name.msi
    ```
4.  Return to the docs for your integration and complete the configuration instructions.

**Install with apt (Debian, Ubuntu)**

To install an integration with `apt`:

1.  If you don't already have it, [install the infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic) for your operating system.
2.  From the command line, run:

    ```bash
    sudo apt-get update
    ```
3.  Run the following command, where `INTEGRATION_FILE_NAME` represents the integration's file name. For more information, see the [integration's documentation](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list).

    ```bash
    sudo apt-get install INTEGRATION_FILE_NAME
    ```
4.  Return to the docs for your integration and complete the configuration instructions.

**Install with yum (Amazon Linux, CentOS, RHEL)**

To install an integration package with `yum`:

1.  If you don't already have it, [install the infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic) for your operating system.
2.  From the command line, run:

    ```bash
    sudo yum -q makecache -y --disablerepo='*' --enablerepo='newrelic-infra'
    ```
3.  Run the following command, where `INTEGRATION_FILE_NAME` represents the integration's file name. For more information, see the [specific on-host integration](https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list).

    ```bash
    sudo yum install INTEGRATION_FILE_NAME
    ```
4.  Return to the docs for your integration and complete the configuration instructions.

**Install with zypper (SLES)**

To install an on-host integration with zypper:

1.  If you don't already have it, [install the infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic) for your operating system.
2.  From the command line, run:

    ```bash
    sudo zypper -n ref -r newrelic-infra
    ```
3.  Run the following command, where `INTEGRATION_FILE_NAME` represents the integration's file name. For more information, see the [integration's documentation](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list).

    ```bash
    sudo zypper -n install INTEGRATION_FILE_NAME
    ```
4.  Return to the docs for your integration and complete the configuration instructions.

**Install from tarball (Other distros)**

> #### 💡 TIP
>
> We recommend [using 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).
5.  Return to the docs for your integration and complete the configuration instructions. If your integration requires use of the JMX tool, details about that are below.

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

    #### Use of the New Relic JMX tool [#nrjmx]

    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.

## Update the agent [#upgrade]

To keep on-host integrations up to date, follow standard procedures to [update the on-host integration package](https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/update-infrastructure-host-integration-package).

## Technical details [#technical-details]

These integrations are built with the same file structure and configuration structure. For details about their structure and how they report data, see [Data reporting](https://docs.newrelic.com/docs/infrastructure/host-integrations/understand-use-data/host-integration-data-collection-reporting).