New Relic infrastructure monitoring provides an integration for Microsoft Azure Load Balancer that reports data from your Azure Load Balancer service to New Relic. 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.
- 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.
To enable the integration:
- Make sure you are using the Microsoft Load Balancer Standard SKU.
- Follow standard procedures to activate your Azure service in New Relic Infrastructure.
You can change the polling frequency and filter data using configuration options.
New Relic queries 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
To view metrics reported by the Azure Load Balancer integration, query the
AzureLoadBalancerSample event type. Use the metadata associated with each metric to filter and facet the data being reported. For detailed metric information, see the Azure supported metrics documentation.
Average Load Balancer data path availability per time duration.
Average Load Balancer health probe status per time duration.
Total number of Bytes transmitted within time period.
Total number of Packets transmitted within time period.
Total number of SYN Packets transmitted within time period.
Total number of new SNAT connections, that is, outbound connections created within time period.
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.