Azure Load Balancer insights using Azure Monitor for Networks | Azure Friday

Erich Robinson-Tillenburg joins Scott Hanselman to demo and explain health monitoring and configuration analysis for Azure Load Balancer using Azure Monitor for Networks, a central hub that provides access to health and connectivity monitoring for all your network resources.
0:00 - Overview
1:16 - Load Balancer insights
4:00 - Visualize functional dependencies
6:20 - Exploring the Metrics dashboard
10:58 - Flow Distribution Help
11:57 - Network Connectivity Monitoring
13:18 - Azure Monitor for Networks hub
14:12 - Wrap-up
◉ Azure Load Balancer - aka.ms/azfr/64...
◉ What is Azure Load Balancer? - aka.ms/azfr/64...
◉ Azure Monitor for Networks (Preview) - aka.ms/azfr/64...
◉ Introducing Azure Load Balancer insights using Azure Monitor for Networks - aka.ms/azfr/64...
◉ Create a free account (Azure) - aka.ms/azfr/64...
#Microsoft #Azure

[@Yonderkthx]

Cool work, guys. I've always wondered how to troubleshoot load balancers and check health, and this looks like just the thing. 👍

[@willembont4790]

Indeed very helpful. Thanks for sharing.

[@KK-bc8cq]

Just something to point out, most of the metrics/visualization for the detailed metrics dashboard is available for at least "Standard service"

[@warningforyou1]

Cool

[@IanButterworthyyc]

Now I’m confused:-) Ingress controller vs. load balancer?

[@erichrt9]

Hey Ian! It depends on the application. If you're running an AKS solution you may want to use the Load Balancer as your front end and have this route traffic to ingress controller running within your cluster. This is a common solution that supports the highly elastic nature of Kubernetes containers and gives you the rapid throughput and availability zone redundancy that you get with the Azure Load Balancer

[@IanButterworthyyc]

@@erichrt9 Thanks, so build it first with no Load Balancer and later, if needed, put one on the front end without too much grief?

[@erichrt9]

@@IanButterworthyyc the approach I would take is to do it with a Load Balancer that routes to multiple ingress controllers. This ensures that your service is highly available as the Standard Load Balancer is zone redundant. If you only have 1 ingress controller and the VM(SS) it is running on goes down your service would experience downtime

[@mukut5ul]

One of the worst cloud I have used... Even can not see vm healthy or unhealthy like AWS. Useless workflow and ui where experience people can confuse. Networks security group all. AWS has sg to sg inbound outbound. AWS has all logs debugging very easy.. here no idea how debug load balancer access logs ... Useless MBA product manager might have designed who has no practical knowledge

[@davidanthonyburton2253]

At first I thought what a great GUI. ( I instantly compared it to the ' Audacity ' music capture programme) And then at the end of the video it showed World latency figures!.. and how it can reports on the health of multiple Web sites. Thank you for this insight on this incredible load balancer /metrics interface 👍🙂