Understand and use data from infrastructure integrations

With New Relic infrastructure integrations, you can monitor the performance of popular services, including AWS, Azure, Google Cloud Platform, Kubernetes, Redis, MySQL, and more.

Here are some tips on how to find, understand, and use data reported from infrastructure integrations.

Explore your infrastructure integration's data

The best way to understand infrastructure integrations's data and see what you can do with it is to enable an integration and explore the data in the New Relic UI.

Some recommendations for exploring:

• View dashboards: You can find your dashboards in New Relic One. For details, see Integration dashboards.
• Query data: You can run custom queries and charts of your integration data. For more information, see Query New Relic data.
• Create alert conditions: See Alert conditions.
• Learn more about what metrics and inventory data an integration reports: See an integration's documentation: cloud integrations and on-host integrations.

Types of integration data

New Relic infrastructure integrations are separated into two main categories:

• Cloud integrations: Integrations for cloud platform services, including AWS, Azure, and GCP.
• On-host integrations: "On-host" refers to core services integrations that you can install directly on a host. Examples: MySQL, NGINX, Kubernetes, Redis.

An infrastructure integration can generate four types of data:

• Metrics: Numeric measurement data. Examples: message counts, error counts, and CPU used percentage. Metric data appears in an integration's charts. For details about what metrics are reported and how to query them, see the documentation for a specific integration. For details about data structure, see Data types.
• Inventory: Information about the state and configuration of a service or host. Examples of inventory data: configuration settings, the name of the host the service is on, the AWS region, the port being used. Inventory data appears in the Inventory UI page. Inventory data also appears in integration dashboards. Changes to inventory data generates event data.
• Events: Events represent important activity on a system. Examples of event data: an admin logging in; a package install or uninstall; a service starting; a table being created. Most events represent changes to inventory data.
• Attributes: Some integrations will generate other non-metric attributes (key-value pairs) that can be queried in New Relic.

Create alert conditions

To create an alert condition for integration data in infrastructure, Go to one.newrelic.com > Infrastructure, choose an integration, and then select an available alert option. For more information, see Infrastructure and alerts.

For on-host integrations, you can also create alert conditions using NRQL queries. (NRQL alerts are not supported or recommended for cloud integrations, due to issues related to data latency.)