Tarball manual install of the infrastructure agent for Linux

Our custom Linux installation process for infrastructure monitoring allows you to tailor all aspects of the installation process, and to place files and folders on your filesystem. You have full control of the installation.

Install the agent

Before installation, check the compatibility and requirements.

To install the agent:

1. Download the packaged agent file or use the following command that automatically fetches a specific version of the agent, its checksum and verifies it after download. Replace ARCH=amd64 with desired architecture (amd64, 386, arm64, arm) and V=1.27.4 with latest or specific version.

   bash

   Copy

   $
   V=1.27.4 ARCH=amd64; echo "https://download.newrelic.com/infrastructure_agent/binaries/linux/${ARCH}/newrelic-infra_linux_${V}_${ARCH}.tar.gz" | { read    url; wget "${url}"{,.sum}; shasum -a 256 --check ${url##*/}.sum; }

   From version 1.27.4 on, we provide the tar.gz package GPG signature. You can check the signature procedure and instructions for verification in the infra-agent repository on GitHub.

2. Unpack the file.

3. Make sure the file unpacks with the following structure:

   newrelic-infra
   |-- config_defaults.sh
   |-- etc
   |   |-- init_scripts
   |   |   |-- systemd
   |   |   |   `-- newrelic-infra.service
   |   |   |-- sysv
   |   |   |   `-- newrelic-infra
   |   |   `-- upstart
   |   |       `-- newrelic-infra
   |   `-- newrelic-infra
   |       `-- integrations.d
   |-- installer.sh
   |-- usr
   |   `-- bin
   |       |-- newrelic-infra
   |       |-- newrelic-infra-ctl
   |       `-- newrelic-infra-service
   `-- var
       |-- db
       |   `-- newrelic-infra
       |       |-- custom-integrations
       |       |-- integrations.d
       |       |-- LICENSE.txt
       |       `-- newrelic-integrations
       |-- log
       |   `-- newrelic-infra
       `-- run
           `-- newrelic-infra

   Copy

4. Install the service script.

5. Optional: Additional install steps.

Install: Optional steps

You can also carry out these additional steps:

• Change the location of the configuration file.
• Change the location of the PID file.
• Change the user and runtime mode.
• Configure the plugin directory.
• Configure the agent directory.
• Configure the log file.
• Change the location of the agent binary.

Install the service script

Before you proceed to install the service script, you need to determine which service manager your system is using:

• If you use one of the supported service managers (SystemD, SysV, and Upstart), use the service script provided in the tarball.
• If you use a service manager we do not support, you must write your own service script.

If you use one of the supported service managers, install the service script for your host:

Your service script is configured. Configure the rest of the options and start the service manually.

Change config file's location

The infrastructure agent includes a configuration file, usually named newrelic-infra.yml, to fine-tune the agent's behavior. For more information, see a config file template and how to configure the agent.

By default, the agent searches for the configuration file in one of these locations:

• newrelic-infra.yml (working directory root folder)
• /etc/newrelic-infra.yml
• /etc/newrelic-infra/newrelic-infra.yml

To specify a different location, use the -config flag command-line. For example:

$
usr/bin/newrelic-infra -config /whatever/path/custom_config_name.yml

To make this change permanent, edit the service script:

Change the pid-file location

The infrastructure agent uses a pid-file to keep the process identification number (pid), which is used to identify a running instance of the agent. How to change the location of the pid-file depends on how the agent is configured.

To change the location of the pid-file:

Change the user and runtime mode

The Linux agent runs as root by default, but it also supports running with users with less privileges: PRIVILEGED and UNPRIVILEGED. For more information, see our documentation on agent running modes.

To change the running mode:

1. Edit the service script:

   Systemd

   1. Open the service script ./newrelic-infra/etc/init_scripts/systemd/newrelic-infra.service.
   2. Search for the line [Service].
   3. Add the line User=user_name, and replace user_name with the user that you want to execute the agent (PRIVILEGED or UNPRIVILEGED).
   4. Save the file.

   SysV

   1. Open the service script ./newrelic-infra/etc/init_scripts/sysv/newrelic-infra.
   2. Search for the line USER=root.
   3. Replace root with the user that you want to execute the agent (PRIVILEGED or UNPRIVILEGED).
   4. Save the file.

   Upstart

   1. Open the service script ./newrelic-infra/etc/init_scripts/upstart/newrelic-infra.
   2. Search for the line exec /usr/bin/newrelic-infra.
   3. Replace it with exec su -s /bin/sh -c ‘exec “$0” “$@“’ user_name-- /usr/bin/newrelic-infra.
   4. Replace user_name with the user that you want to execute the agent (PRIVILEGED or UNPRIVILEGED).
   5. Save the file.

2. If you're running the agent as PRIVILEGED, you must give it two additional Linux capabilities:

   1. Make sure the libcap library is installed in your host. (You need the setcap and getcap commands that come with it.)

   2. Extract the contents of the tarball and execute the following command with root permission:

      bash

      Copy

      $
      setcap CAP_SYS_PTRACE,CAP_DAC_READ_SEARCH=+ep ./newrelic-infra/usr/bin/newrelic-infra

   3. The run mode will be selected based on the current user and the Kernel Capabilities assigned to it.

Configure the plugin directory

The infrastructure agent allows you to install integrations that monitor and report data from popular services such as Kubernetes, AWS, MySQL, Redis, Kafka, etc. Each integration has its own configuration file, named by default integration-name-config.yml, placed in the predefined location /etc/newrelic-infra/integrations.d/. On initialization, the agent loads the config file.

To overwrite the predefined location of the integration configuration file, use one of the following methods:

• Set the location in the NRIA_PLUGIN_DIR environment variable.
• Set the custom path in the newrelic-infra.yml configuration file using the plugin_dir field.
• Pass it as a command line argument using -plugin_dir when you run the newrelic-infra binary.

Configure the agent directory

The agent requires its own defined directory to run the installed integrations, caching data (inventory), etc. The default location is /var/db/newrelic-infra/.

The agent directory has the following structure and content:

• LICENSE: Text file containing the New Relic infrastructure agent license.
• custom-integrations: Directory that stores the installed the custom integrations.
• newrelic-integrations: Directory that stores the New Relic official integrations.
• data: Directory where the agent stores cache data (inventory).

To overwrite the predefined location of the agent directory, use one of the following methods:

• Set the location in the NRIA_AGENT_DIR environment variable.
• Set the custom path in the newrelic-infra.yml configuration file using the agent_dir field.
• Pass it as a command line argument using -agent_dir when you run the newrelic-infra binary.

Configure the log file

By default the agent stores the log files in /var/db/newrelic-infra/newrelic-infra.log.

To overwrite the predefined location of the log file, use one of the following methods:

• Set the location in the NRIA_LOG_FILE environment variable.
• Set the custom path in the newrelic-infra.yml configuration file using the log_file field.
• Pass it as a command line argument using -log_file when you run the newrelic-infra binary.

Change the location of the agent binary

To change the location of the executable, edit the service script:

What's next?

You may also want to:

• Add custom attributes to annotate your infrastructure data.
• Connect your AWS account if your servers are hosted on Amazon EC2.
• Enable log forwarding.
• Enable our Flex integration by manually adding the Flex executable.
• Add other infrastructure integrations to collect data from external services.
• Manually start, stop, restart, or check the agent status.