Access to this feature depends on your subscription level. Requires Infrastructure Pro.
New Relic Infrastructure provides an integration for Microsoft Azure Load Balancer that reports data from your Azure Load Balancer service to New Relic products. This document explains how to activate this integration and describes the data that can be captured.
New Relic's integration for Azure Load Balancer reports metric data about TCP and UDP load balancers that distribute traffic among instances of services defined in a load-balanced set. Metric data include virtual IP and dynamic IP availability, and processed byte and packet counts. It also collects inventory data about the status and configuration of the service.
Using New Relic, you can:
- View Azure Load Balancer data in pre-built Infrastructure dashboards.
- Run custom queries and visualize the data in New Relic Insights.
- Create alert conditions to notify you of changes in data.
Load Balancer metrics are collected only if you use the Microsoft Load Balancer Standard SKU.
Anyone can view and explore the Azure data reporting to your New Relic Infrastructure account.
To enable the integration:
- Make sure you have installed the Infrastructure agent before you activate Azure integrations from your Infrastructure account.
- Make sure you are using the Microsoft Load Balancer Standard SKU.
- Follow standard procedures to activate your Azure service in New Relic Infrastructure.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
New Relic Infrastructure integrations query your Azure Load Balancer services according to a default polling interval, which varies depending on the integration. Polling frequency for the Azure Load Balancer integration:
- Polling interval: 5 minutes
- Resolution: 1 minute
Find and use data
New Relic reports several sets of metrics for the Azure Load Balancer integration.
Load balancer metrics
||Average count of availability of VIP endpoints, based on probe results.|
||Average count of availability of DIP endpoints, based on probe results.|
||Total number of bytes processed per front-end.|
||Total number of packets processed per front-end.|
||Total number of SYN packets received.|
||Total number of new SNAT connections, that is, outbound connections that are masqueraded to the Public IP address front-end.|
||Total number of SNAT ports allocated within time period|
||Total number of SNAT ports used within time period|
This integration collects the following inventory data about your system's state and configuration.