AWS ELB / ALB Integration
Monitor load balancer health, target response times, and HTTP error rates. Per-target-group SLO tracking, access log analysis, and AI traffic anomaly detection for your load balancing layer.
How It Works
Deploy CloudFormation Stack
Launch the TigerOps CloudFormation template to configure Metric Streams for the AWS/ApplicationELB and AWS/ELB namespaces and grant the necessary IAM permissions.
Enable Access Logs
Enable ALB access logs to an S3 bucket. TigerOps subscribes to the S3 event notifications and parses access logs to provide per-path and per-client request rate and latency breakdowns.
Map Target Groups to Services
TigerOps maps ALB target groups to your application services using ALB tags and target group names. Dashboards are organised by service so each team sees their own load balancer metrics.
Set SLO-Based Alerts
Define error budget alerts based on 5xx rates and p99 latency. TigerOps computes SLO burn rate and alerts you when you are burning through your error budget faster than planned.
What You Get Out of the Box
Request Count & Throughput
Total requests per second, processed bytes, and new/active connection counts per load balancer and target group. Trend charts with anomaly detection surface traffic spikes instantly.
HTTP Error Rate Tracking
4xx and 5xx error counts broken down by HTTP error code and target group. TigerOps distinguishes between client errors (4xx), backend errors (5xx), and ELB-generated errors for accurate fault attribution.
Target Response Time
p50, p95, and p99 target response time per target group. TigerOps alerts when response time percentiles breach SLO thresholds and links latency spikes to the correlated backend service metrics.
Target Health Monitoring
Healthy and unhealthy target counts per target group with health check failure reasons. TigerOps alerts immediately when the healthy target count drops and links it to the corresponding EC2 or container metrics.
WAF Rule Hit Rates
If AWS WAF is attached to your ALB, TigerOps ingests WAF allowed, blocked, and counted request metrics alongside load balancer metrics for a unified security and performance view.
AI Traffic Anomaly Detection
TigerOps baselines normal request patterns per target group and alerts on statistically anomalous traffic spikes, error rate changes, or latency shifts that static thresholds would miss.
ALB Access Logs + Metric Streams
Enable ALB access logs and deploy the TigerOps ELB monitoring stack.
# Enable ALB access logs
aws elbv2 modify-load-balancer-attributes \
--load-balancer-arn arn:aws:elasticloadbalancing:us-east-1:123456789:loadbalancer/app/my-alb/abc123 \
--attributes \
Key=access_logs.s3.enabled,Value=true \
Key=access_logs.s3.bucket,Value=my-alb-logs-bucket \
Key=access_logs.s3.prefix,Value=alb-logs
# Deploy TigerOps ELB/ALB monitoring stack
aws cloudformation deploy \
--template-url https://tigerops-cfn.s3.amazonaws.com/elb-integration.yaml \
--stack-name tigerops-elb \
--capabilities CAPABILITY_IAM \
--parameter-overrides \
TigerOpsApiKey=${TIGEROPS_API_KEY} \
AccessLogsBucket=my-alb-logs-bucket \
EnableAccessLogParsing=true \
TargetResponseTimeP99Threshold=2.0
# Tag your ALB for team-based routing in TigerOps
aws elbv2 add-tags \
--resource-arns arn:aws:elasticloadbalancing:us-east-1:123456789:loadbalancer/app/my-alb/abc123 \
--tags Key=Team,Value=platform Key=Environment,Value=production Key=Service,Value=api-gatewayCommon Questions
Does TigerOps support both Application Load Balancer and Classic Load Balancer?
Yes. TigerOps collects metrics from AWS/ApplicationELB (ALB), AWS/ELB (Classic), and AWS/NetworkLoadBalancer (NLB) namespaces via Metric Streams. ALB provides the richest metrics including per-target-group latency and HTTP code breakdowns.
How does TigerOps use ALB access logs?
ALB access logs are delivered to S3 every 5 minutes. TigerOps uses S3 event notifications to trigger a log ingestion pipeline that parses each log file and provides per-URI and per-client-IP request rate, latency, and error code distributions.
Can TigerOps alert when the number of healthy targets drops below a threshold?
Yes. TigerOps monitors HealthyHostCount and UnHealthyHostCount per target group. You can set an absolute threshold (e.g., alert if healthy hosts drop below 2) or a percentage threshold (e.g., alert if more than 20% of targets are unhealthy).
How does TigerOps handle ALB weighted target group routing?
TigerOps tracks metrics per target group and labels each with its current routing weight from the ALB API. This lets you monitor canary deployments — comparing error rates and latency between the primary and canary target groups during a weighted rollout.
Does TigerOps support ALB Listener Rule metrics?
TigerOps correlates ALB access logs with listener rule ARNs to provide per-rule request counts and error rates. This is particularly useful when you have path-based routing rules that direct traffic to different microservices.
Catch Load Balancer Issues Before Users Do
Target health alerts, SLO-based error budgets, and AI traffic anomaly detection. Connect your ALB in minutes.