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 and the integration files up to date.
Find on-host integration versions
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:
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 docs.
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're running services in containerized, orchestrated environments, choose your update scenario:
Download the latest .exe installer for New Relic's integration from out repository
To install from the Windows command prompt, run:
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.
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.
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.
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.
重要
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 on-host integrations on Kubernetes
Update on-host integrations on Amazon ECS (EC2 launch type)