This alert has detected increase in the number of unhealthy targets. The alert is activated when number of unhealthy targets is above 1 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 1 . Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained target issues. Adjust this period based on the criticality of write operations and the operational dynamics of your system. Please adapt it in the query as per your needs. TargetGroup Specificity: Tailor alerts for different Load balancers based on their roles in your infrastructure. Critical instances handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering of this alert, immediate actions include reviewing recent alb status check, reviewing alb configuration changes,checking for any misconfigurations or fine tunings as per your service infrastructure capaity needs. Mitigating failures automatically can be done following best practices of using load balancer health check in Amazon EC2 Auto Scaling, or Amazon Elastic Container Service (Amazon ECS).

This alert has detected increase in the number of rejections by your load balancer. The alert is activated when load balancer rejection is above 10 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 10 . Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a higher threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained rejection issues. Adjust this period based on the criticality of write operations and the operational dynamics of your system.Please adapt it in the query as per your needs. TargetGroup Specificity: Tailor alerts for different Load balancers based on their roles in your infrastructure. Critical instances handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering of this alert, immediate actions include reviewing recent alb status check, reviewing alb configuration changes,checking for any misconfigurations or fine tunings as per your service infrastructure capaity needs.

This alert has detected increase in the number of load balancer capacity units (LCU) used by your load balancer. The alert is activated when load balancer capacity units is above 1 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 1 LCU. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a higher threshold to detect issues earlier. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained consumption issues. Adjust this period based on the criticality of write operations and the operational dynamics of your system.Please adapt it in the query as per your needs. TargetGroup Specificity: Tailor alerts for different Load balancers based on their roles in your infrastructure. Critical instances handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering of this alert, immediate actions include reviewing recent alb status check, reviewing alb configuration changes,checking for any misconfigurations or fine tunings as per your service infrastructure needs. More can be read [here](https://aws.amazon.com/elasticloadbalancing/pricing/)

This alert has detected increase in the number of unhealthy state DNS. The alert is activated when number of unhealthy state DNS is above 1 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 1 . Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained unhealthy DNS issues. Adjust this period based on the criticality of write operations and the operational dynamics of your system.Please adapt it in the query as per your needs. TargetGroup Specificity: Tailor alerts for different Load balancers based on their roles in your infrastructure. Critical instances handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering of this alert, immediate actions include reviewing recent alb status check, reviewing alb configuration changes,checking for any misconfigurations or fine tunings as per your service infrastructure capaity needs. Mitigating failures automatically can be done following best practices of using load balancer health check in Amazon EC2 Auto Scaling, or Amazon Elastic Container Service (Amazon ECS).

The alert is activated when overall availability for the ALB has fallen below 99.5% for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 99.5 % . Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained availability issues. Adjust this period based on the criticality of write operations and the operational dynamics of your system.Please adapt it in the query as per your needs. TargetGroup Specificity: Tailor alerts for different Load balancers based on their roles in your infrastructure. Critical instances handling high-stakes transactions may warrant more stringent monitoring. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering of this alert, immediate actions include reviewing recent alb status check, reviewing alb configuration changes,checking for any misconfigurations or fine tunings as per your service infrastructure capaity needs. Mitigating failures automatically can be done following best practices of using load balancer health check in Amazon EC2 Auto Scaling, or Amazon Elastic Container Service (Amazon ECS).