Skip to content

Azure Integration - Load Balancer

Mackerel supports obtaining and monitoring metrics for Load Balancer in Azure Integration. When integrating with Azure Integration, billable targets are determined using the conversion 1 resource = 1 Micro Host. In addition to this, depending on the number of metrics retrieved, you may be charged for exceeding the maximum number of metrics per micro host.

Please refer to the following page for Azure Integration configuration methods and a list of supported Azure services.
Azure Integration

Obtaining metrics

The metrics obtainable with Azure Integration’s Load Balancer support are as follows. For Metric explanations, refer to the Azure help page.

The maximum number of metrics obtainable is 4 x (number of front-end IP addresses) + 2 x (number of back-end IP addresses).

Graph nameMetricMetric name in MackerelUnitAggregation Type
Byte CountByteCountazure.load_balancer.byte_count.#.byte_countbytesTotal
Data Path AvailabilityVipAvailabilityazure.load_balancer.data_path_availability.#.vip_availabilitypercentageAverage
Health Probe StatusDipAvailabilityazure.load_balancer.health_probe_status.#.dip_availabilitypercentageAverage
Packet CountPacketCountazure.load_balancer.packet_count.#.packet_countintegerTotal
SNAT Connection CountSnatConnectionCountazure.load_balancer.snat_connection_count.#.snat_connection_countintegerTotal
SYN CountSYNCountazure.load_balancer.syn_count.#.syn_countintegerTotal

Enter either the front-end or the back-end IP address for # in "Metric name in Mackerel".
Corresponding metrics are as follows.

  • Front-end IP address      - Byte Count      - Data Path Availability      - Packet Count      - SYN Count

  • Back-end IP address      - Health Probe Status      - SNAT Connection Count

Each IP address is stored in a hyphen demarcated format.
For example, if the IP address is 127.0.0.1, it will look like this 127-0-0-1.