Quick Start Observability for AWS NLB
Thank you!
We got your information.
Coralogix Extension For AWS NLB Includes:
Dashboards - 1
Gain instantaneous visualization of all your AWS NLB data.
Alerts - 3
Stay on top of AWS NLB key performance metrics. Keep everyone in the know with integration with Slack, PagerDuty and more.
AWS Network LB - Unhealthy targets
This alert has detected an increase in the number of unhealthy targets in your AWS Network Load Balancer. The alert is activated when the number of unhealthy targets exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 1 unhealthy target. Depending on your specific application needs and past performance data, this threshold may need adjustment. Critical applications might require a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained target issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. Target Group Specificity: Tailor alerts for different target groups 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 this alert, immediate actions include reviewing recent NLB status checks, reviewing NLB configuration changes, and checking for any misconfigurations. Mitigating failures automatically can be done following best practices of using load balancer health checks in Amazon EC2 Auto Scaling or Amazon Elastic Container Service (Amazon ECS).
AWS Network LB - Increases capacity units (LCU)
This alert has detected an increase in the load balancer capacity units (LCU) usage for your AWS Network Load Balancer. The alert is activated when the LCU usage exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set based on historical LCU usage. Adjust this threshold according to your service's expected usage patterns and capacity planning strategies. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained capacity issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. Resource Allocation: Evaluate the current resource allocation and ensure your load balancer is adequately provisioned to handle increased traffic and usage. 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 this alert, immediate actions include reviewing recent traffic patterns, analyzing service performance, and considering capacity upgrades if needed. Adjust your LCU limits according to traffic forecasts and service requirements.
AWS Network LB - Port allocation error
This alert has detected a port allocation error in your AWS Network Load Balancer. The alert is activated when port allocation errors are reported for a continuous period. Customization Guidance: Threshold: The default threshold is set to detect any port allocation errors. Adjust this threshold based on your application's tolerance for port issues and expected performance metrics. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained port allocation issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. Port Specificity: Tailor alerts for specific ports or services that are critical to your application’s functionality. Prioritize ports that handle essential traffic and services. 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 this alert, immediate actions include reviewing load balancer settings, verifying port availability, and ensuring proper network configuration. Consider implementing port ranges or adjusting listener rules to address allocation constraints.
Integration
Learn more about Coralogix's out-of-the-box integration with AWS NLB in our documentation.