If you need to install the infrastructure agent for the first time, see the installation docs for Linux, Windows, or configuration management tools.
If you need to uninstall the infrastructure agent, see Uninstall the infrastructure agent.
Identify the infrastructure agent version
The infrastructure agent doesn't update itself automatically. To see if you have the latest agent version, see the infrastructure agent release notes.
To view the current infrastructure agent version for a host in the New Relic UI, use any of these options:
- Single hosts: See the
agentVersion
tag on any host entity, or look for itsAgent version
in the Infrastructure UI. - Multiple hosts: Go to Infrastructure > Navigator and group reporting entities by
agentVersion
to see a list of active hosts per version. - Query: Use the
agentVersion
attribute on any standard agent metric to generate a report. For example, the following NRQL query shows number of unique active hosts group by agent version:FROM SystemSample SELECT uniqueCount(hostname)FACET agentVersionLIMIT MAX
To manually check the version on the host, you can log onto a server and run newrelic-infra --version
, or the applicable command for your package manager. The directory where you'd run this differs between operating systems, but here are the default paths:
- Linux:
/usr/bin/newrelic-infra
- Windows:
C:\Program Files\New Relic\newrelic-infra\
- macOS:
/usr/local/bin/newrelic-infra
Identify outdated agent versions from the UI
You'll first need to determine the latest version available from the agent release notes, we recommend running versions that are no older than three months when possible.
To identify active hosts that are running a version that's older than a given major.minor
(for example, 1.45.0
), you can run this NRQL query:
FROM SystemSample SELECT uniques(hostname) WHERE numeric(capture(agentVersion, '(?P<major>.[0-9]*).([0-9]*).([0-9]*)')) <= 1 AND numeric(capture(agentVersion, '([0-9]*).(?P<minor>.[0-9]*).([0-9]*)')) <= 45LIMIT MAX
Update the agent for installs using the package manager
If you used the default installation process, use your package manager to update the program and its dependencies to the latest version. Here are examples for some common systems:
Update the agent for assisted and manual tarball installs
Important
Since there are are no automated scripts, old files may remain when you update. Be sure to manually remove outdated files.
To update the agent, download the file again and follow the installation procedure for Linux (assisted or manual) or Windows (assisted or manual). This will overwrite your old installation.
Update the containerized version of the agent
Use the latest
label to ensure that our Docker image is automatically updated.