The infrastructure agent and its integrations collect data from the system and core services, and is able to forward logs to New Relic. Backend application metrics (APM) are collected by separate APM agents. Notice how each integration and forwarder feed different data types in the New Relic database (NRDB).
The quickest way to get started is through our guided 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 installation method.
You're running services in orchestrated environments
If you are running services in containerized, orchestrated environments, choose your scenario:
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.
For integrations that require our nrjmx tool, follow these additional instructions:
Use of the New Relic JMX tool
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.