Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Azure - Get Current Status of the Load Balancer Probe

Tags:

We have a load balanced set in Azure for our web application, which load balances port 80 and 443 between two VMs. We have used the default tcp probe. Is there a way to get the current status of the probe for the load balancer from Azure?

I know I could just check each individual machines and do a probe myself, but I want to know if we could see what Azure sees for each machine.

like image 261
madaboutcode Avatar asked Aug 24 '15 07:08

madaboutcode


People also ask

How do I check my Azure load balancer health probe status?

Health probes originate from an Azure infrastructure address and are visible within the guest OS of the VM. To get the health probe status for your standard load balancer resources: Select the Health Probe Status metric with Avg aggregation type. Apply a filter on the required frontend IP address or port (or both).

What is Azure load balancer health probe?

A health probe is used to determine the health status of the instances in the backend pool. During load balancer creation, configure a health probe for the load balancer to use. This health probe will determine if an instance is healthy and can receive traffic.

Is Azure load balancer high availability?

Azure load balancer overview An Azure load balancer is a Layer-4 (TCP, UDP) load balancer that provides high availability by distributing incoming traffic among healthy VMs.

What is ILB in Azure?

ILB is a security enhancement over the current public load balancing that is offered in Azure. It restricts the accessibility and creates a trust boundary between the load balanced Virtual IP address to a Cloud Service or a Virtual Network that doesn't require the public internet.


1 Answers

Well as of 2018-06-05 this feature is not available in the Azure Portal. Today you have to configure "Diagnostic Logs" for the Load Balancer. If you choose the "Storage Account" option a JSON file is created with records like below

        {
         "time": "2018-06-05T08:50:04.2266987Z",
         "systemId": "XXXXXXXX-XXXX-XXXX-XXXX-d81b04ac33df",
         "category": "LoadBalancerProbeHealthStatus",
         "resourceId": "/SUBSCRIPTIONS/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX/RESOURCEGROUPS/TEST-INT/PROVIDERS/MICROSOFT.NETWORK/LOADBALANCERS/TEST-LB",
         "operationName": "LoadBalancerProbeHealthStatus",
         "properties": {"publicIpAddress":"XXX.XXX.XXX.XXX","port":8080,"totalDipCount":2,"dipDownCount":0,"healthPercentage":100.000000}
    }
    ,
    {
         "time": "2018-06-05T08:50:09.2415410Z",
         "systemId": "XXXXXXXX-XXXX-XXXX-XXXX-d81b04ac33df",
         "category": "LoadBalancerProbeHealthStatus",
         "resourceId": "/SUBSCRIPTIONS/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX/RESOURCEGROUPS/TEST-INT/PROVIDERS/MICROSOFT.NETWORK/LOADBALANCERS/TEST-LB",
         "operationName": "LoadBalancerProbeHealthStatus",
         "properties": {"publicIpAddress":"XXX.XXX.XXX.XXX","port":8080,"totalDipCount":2,"dipDownCount":1,"healthPercentage":50.000000}
    }

"Log Analytics" suggested by Eric is not mandatory but can be used to analyze these LB logs.

like image 194
Shinva Avatar answered Sep 22 '22 21:09

Shinva