This alert is triggered when the health probe status of an Azure Load Balancer falls below 99% for a continuous period of 5 minutes. The health probe status is a critical metric that indicates the overall health of the load balancer and the availability of the backend instances. Customization Guidance: Threshold: The default threshold is set at 99%. Depending on your specific application needs and past performance data, this threshold may need adjustment. For high-availability systems, consider a stricter threshold. Region Specificity: Tailor alerts for different regions based on their roles in your infrastructure. Critical regions handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Adjust the frequency of notifications based on the criticality of the application(s) supported. Action: Upon triggering this alert, immediate actions include investigating the health probe configuration, reviewing recent deployments or changes, and checking the backend instances' health status. Consider scaling operations or switching traffic if needed.

This alert is triggered when the datapath availability of an Azure Load Balancer falls below 25% for a continuous period of 5 minutes. Datapath availability indicates the ability of the load balancer to successfully route traffic to the backend instances. Customization Guidance: Threshold: The default threshold is set at 25%. Consider adjusting this threshold based on your application's tolerance for datapath unavailability. Instance Specificity: Customize alerts for different load balancers depending on their criticality and the nature of the traffic they handle. Response Plan: Have a predefined response plan to address situations where datapath availability falls below the acceptable level. Action: Upon triggering this alert, immediate actions include reviewing the network configuration, checking the health of the backend instances, and ensuring no misconfigurations are present. Additional steps may include rerouting traffic or scaling resources.

This alert is triggered when the overall datapath availability of an Azure Load Balancer falls below 90% for a continuous period of 5 minutes. This metric reflects the percentage of successful traffic routing by the load balancer. Customization Guidance: Threshold:** The default threshold is set at 90%. Depending on the application's criticality, this threshold can be adjusted to ensure a quick response to potential issues. Load Balancer Specificity: Configure this alert for each load balancer individually, taking into account their specific roles and the importance of the traffic they manage. Mitigation Strategies: Prepare mitigation strategies in case of datapath unavailability, such as failover procedures or increased monitoring. Action: When this alert is triggered, steps should include checking the health status of the load balancer, reviewing recent configuration changes, and ensuring that backend services are operational. Further actions may involve traffic rerouting or infrastructure scaling.