How to resolve Sprinto check for monitoring AWS Application Load Balancer (ALB) or Classic Load Balancer (CLB) latency
In this article:
About
Sprinto Check: AWS load balancer latency should be monitored or AWS classic load balancer latency should be monitored
When you integrate your AWS account with Sprinto, the platform automatically fetches the list of services from your AWS account. If you're using AWS Application Load Balancers (ALB) or AWS Classic Load Balancer (ELB) and haven't configured a monitoring alert for the TargetResponseTime or Latency metric, Sprinto activates this check for all ALBs under your account.
Note: At this time, our platform does not support AWS CloudWatch Composite Alarms or Math-Based Alarms.
This means you cannot create alarms that:
Combine multiple alarms using logical conditions (e.g., ALARM1 AND ALARM2)
Use metric math expressions (e.g., calculating averages or deltas across metrics)
Purpose
Monitoring latency in your AWS Load Balancer, specifically focusing on the TargetResponseTime or Latency metric, is crucial to ensure the responsiveness and performance of your applications. Sprinto promptly sends notifications if the response time exceeds the defined threshold, allowing you to proactively address potential performance issues.
How to Resolve
To address this check, follow the steps below to create an AWS CloudWatch alert for monitoring AWS Load Balancer latency.
Before you Begin
Ensure you have "Admin" access on the AWS account to create alerts.
Ensure you have an Application Load Balancer (ALB) or Classic Load Balancer (ELB) created on your AWS account to set up CloudWatch alerts.
Log in to Sprinto as an administrator.
Create Monitoring Alert
Follow the below applicable steps to create load balancer latency alert on CloudWatch:
Create Application load balancer (ALB) latency alert.
Log in to your AWS console using your credentials.
Navigate to Load Balancer web service and select your desired ALB load balancer you wish to create an alarm.
On the Load balancer page, select the Monitoring tab, and click View in Metric for the Target Response Time metric.
Now, click the alert icon under Actions.
Specify the conditions to define the alert trigger point, then click Next.
On the Configure Action page:
Create New Topic: Enter the topic name and email address for alert notifications.
Click Next at the bottom of the page.
Enter a name and description for the created alert, then click Next.
Preview your created alarm, and if necessary, edit any parameters before clicking Create Alarm.
Create Classic Load Balancer (ELB) latency alert.
Log in to your AWS console using your credentials.
Navigate to the Load Balancer web service and select the desired classic load balancer you wish to create an alarm.
On Load balancer page, select the Monitoring tab, and click View in Metric for the Average Latency metric.
Now, click the alert icon under Actions.
Specify the conditions to define the alert trigger point, then click Next.
On the Configure Action page:
Create New Topic: Enter the topic name and email address for alert notifications. Ensure your created user gets selected for SNS.
Click Next at the bottom of the page.
Enter a name and description for the created alert, then click Next.
Preview your created alarm, and if necessary, edit any parameters before clicking Create Alarm.
Final step
Once the monitoring alert is set up on CloudWatch for AWS Load Balancer or Classic load balancer latency, Sprinto retrieves the changes, and the Sprinto check status is marked as "Passing."
For additional assistance with the Sprinto check, please reach out to Sprinto Support. We're here to help!