When setting up an Azure Load Balancer, you configure a health probe that your load balancer can use to determine if your instance is healthy. If your instance fails its health probe enough times, it will stop receiving traffic until it starts passing health probes again.
Effects
The part of your application served by the load balancer will not be available
Fixes
Blue Matador detects when all your instances in your load balancer are failing their health probes by monitoring the DipAvailability metric. To troubleshoot this issue, try taking the following actions:
- Check the health probe endpoint for errors
- Check general host health. Look at application logs, server metrics, or APM metrics to determine what is making your virtual machines unhealthy.
- Set up scaling actions with your load balancer to ensure that you always have enough servers to handle load
