New Relic's on-host integrations are a type of infrastructure integration that collect data from core services running on your hosts, such as MySQL, Apache, or Redis, among others.
There are multiple ways to install on-host integrations depending on your setup and needs. Here we present a brief overview of all install methods and when it's more appropriate to use them.
To collect data from on-host services, all you need are two things: the infrastructure agent, and the on-host integrations. All on-host integrations require that our infrastructure agent is installed on the host. Besides collecting system's data, the agent acts as a forwarder for integrations's data, and can forward logs.
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 install method.
If you are running services in containerized, orchestrated environments, choose your scenario:
- Install on-host integrations on Kubernetes
- Install on-host integrations on Amazon ECS (EC2 launch type)
If you are running services without orchestration or on-premise, choose your scenario:
To keep on-host integrations up to date, follow standard procedures to update the on-host integration package.