PDF

AWS ELB Sensor

AWS ELB Sensor allows monitoring metrics of AWS Elastic Load Balancers.

Elastic Load Balancing allows you to monitor the health of your applications and their performance in real-time with Amazon CloudWatch metrics.

Requirements

This sensor requires sufficient rights to query data from the AWS API. In IAM (Identity and Access Management), you need to create policy with statements (JSON format):

[{ "Sid": "Stmt1338559359622", "Action": [ "elasticloadbalancing:DescribeLoadBalancers" ], "Effect": "Allow", "Resource": "" }, { "Sid": "Stmt1338559372809", "Action": [ "cloudwatch:GetMetricStatistics", "cloudwatch:GetMetricData", "cloudwatch:ListMetrics" ], "Effect": "Allow", "Resource": "" }]

Options

This sensor requires credentials for AWS API. Select the region for which you want to monitor Load Balancers instances. Metrics can be collected for each Load Balancer instance or by Availability Zones.

Alerts
  • Backend Connection Errors - when any backend connection error occurs
  • Unhealthy Host Count > 0
  • Surge Queue is full - when any request were rejected because the surge queue is full

Alerts are defined for all monitored load balancers.

Performance Metrics

  • Load Balancer\Backend Connection Errors - The number of connections that were not successfully established between the load balancer and the registered instances
  • Load Balancer\Healthy Host Count - The number of healthy instances registered with your load balancer
  • Load Balancer\Unhealthy Host Count - The number of unhealthy instances registered with your load balancer
  • HTTP\2XX Responses - The number of HTTP 2XX response codes generated by registered instances
  • HTTP\3XX Responses - The number of HTTP 3XX response codes generated by registered instances
  • HTTP\4XX Responses - The number of HTTP 4XX response codes generated by registered instances
  • HTTP\5XX Responses - The number of HTTP 5XX response codes generated by registered instances
  • HTTP\ELB 4XX Responses - The number of HTTP 4XX client error codes generated by the load balancer
  • HTTP\ELB 5XX Responses - The number of HTTP 5XX client error codes generated by the load balancer
  • Requests\Latency (ms) - The total time elapsed, in milliseconds, from the time the load balancer sent the request to a registered instance until the instance started to send the response headers
  • Requests\Request Count - The number of requests completed or connections made during the specified interval
  • Requests\Spillover Count - The total number of requests that were rejected because the surge queue is full
  • Requests\Surge Queue Length - The total number of requests (HTTP listener) or connections (TCP listener) that are pending routing to a healthy instance
  • ALB\Active Connection Count - The estimated number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets
  • ALB\Consumed LCUs - The estimated number of load balancer capacity units (LCU) used by an Application Load Balancer
  • ALB\New Connection Count - The estimated number of new TCP connections established from clients to the load balancer and from the load balancer to targets
  • ALB\Processed Bytes - The estimated number of bytes processed by an Application Load Balancer

Data for some metrics are available depending on the Load Balancer type and selected dimension.

Reports (Data Collectors)

By default, the sensor collects data for two reports:

  • Load Balancer Report - containing base balancer metrics, such as Requests\Request Count, Load Balancer\Backend Connection Errors, Load Balancer\Healthy Host Count, and others.

  • Application Load Balancer Report - containing ALB metrics.

amazoncloudelasticload balancer