New Relic Infrastructure integrations allow you to send data from popular products and services to New Relic.
Integrations fall into two main categories: on-host and cloud. On-host integrations reside on your own servers or hosts and include:
- On-host integrations built by New Relic.
- Open-source on-host integrations built by the open-source community.
- Custom on-host integrations built using New Relic's Integrations SDK.
This document gives a brief introduction to on-host (non-cloud) integrations.
Access to on-host integration data is available only with Infrastructure Pro. For subscription details, see the Infrastructure product page.
To get started with on-host integrations:
- Browse the lists of on-host integrations built by New Relic.
- If you do not already have New Relic Infrastructure, install the Infrastructure agent for your operating system.
- Follow the procedures to install and configure the selected on-host integration, including prerequisites for compatibility and other requirements.
- Optional: If we don't currently offer an integration for the service you use, browse the list of open-source on-host integrations or create your own integration with New Relic's Integrations SDK.
After you install and activate an integration, you will be able to:
- Filter and analyze the metrics and configuration data in New Relic Infrastructure.
- Query your data and create custom dashboards in New Relic Insights.
- Create alert conditions to monitor problems with your services' performance in New Relic Alerts.
Monitor remote and multi-tenant configurations
Some configurations may use third party elements, such as databases, which reside in non-accessible, remote hosts. Most of our existing integrations - with the exception of Apache, MySQL, NGINX, Redis, and StatsD - can fetch data from local and remote hosts or servers, ensuring a continuous monitoring of your service.
On-host integrations monitoring supports multi-tenant clustered configurations - by "abstracting" the service from the host, multiple entities can be monitored as remote instances. Note that since Apache, MySQL, NGINX, Redis, and StatsD integrations do not support remote monitoring, multi-tenant monitoring is not possible either.