Azure Load Balancer monitoring integration

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.

Features

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:

Requirements

Load Balancer metrics are collected only if you use the Microsoft Load Balancer Standard SKU.

Activate integration

To enable the integration:

  1. Make sure you are using the Microsoft Load Balancer Standard SKU.
  2. 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 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

Find and use data

To explore your integration data, go to one.newrelic.com > Infrastructure > Azure > (select an integration).

You can query and explore your data using the AzureLoadBalancerSample event type, with a provider value of AzureLoadBalancer.

Metric data

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.

Metric Description Metadata

vipAvailability

Average Load Balancer data path availability per time duration.

frontendIPAddress

frontendPort

dipAvailability

Average Load Balancer health probe status per time duration.

frontendIPAddress

frontendPort

backendIPAddress

backendPort

protocolType

byteCount

Total number of Bytes transmitted within time period.

frontendIPAddress

frontendPort

direction

packetCount

Total number of Packets transmitted within time period.

frontendIPAddress

frontendPort

direction

synCount

Total number of SYN Packets transmitted within time period.

frontendIPAddress

frontendPort

direction

snatConnectionCount

Total number of new SNAT connections, that is, outbound connections created within time period.

frontendIPAddress

backendIPAddress

connectionState

allocatedSnatPorts Total number of SNAT ports allocated within time period.

frontendIPAddress

backendIPAddress

protocolType

usedSnatPorts Total number of SNAT ports used within time period.

frontendIPAddress

backendIPAddress

protocolType

Inventory data

This integration collects the following inventory data about your system's state and configuration.

azure/loadbalancer

  • name
  • regionName
  • resourceGroupName
  • sku
  • type

azure/loadbalancer/backend-pool

  • name
  • regionName
  • resourceGroupName
  • virtualMachineIds
  • virtualMachineNames

azure/loadbalancer/frontend-ip

  • ipAddress
  • ipAllocationMethod
  • isPublicIp
  • name
  • regionName
  • resourceGroupName

azure/loadbalancer/inbound-nat-rule

  • backendPort
  • floatingIpEnabled
  • frontendPort
  • name
  • protocol
  • regionName
  • resourceGroupName
  • timeOutInMinutes

azure/loadbalancer/probe

  • intervalInSeconds
  • name
  • numberOfProbes
  • port
  • protocol
  • regionName
  • resourceGroupName
  • requestPath

azure/loadbalancer/rule

  • backendPort
  • frontendPort
  • idleTimeoutInMinutes
  • isFloatingIp
  • name
  • protocol
  • regionName
  • resourceGroupName

For more help

If you need more help, check out these support and learning resources: