The Service Map for APM is here!

AWS Load Balancer

Crawler Crawler
ELB default dashboard

Overview

Elastic Load Balancing (ELB) is an AWS service used to dispatch incoming web traffic from your applications across your Amazon EC2 backend instances, which may be in different availability zones. ELB helps ensure a smooth user experience and provide increased fault tolerance, handling traffic peaks and failed EC2 instances without interruption.

Datadog collects metrics and metadata from all three flavors of Elastic Load Balancers that AWS offers: Application, Classic, and Network Load Balancers.

Setup

Installation

If you haven’t already, set up the Amazon Web Services integration first.

Metric collection

  1. In the AWS integration tile, ensure that ELB is checked under metric collection. Check also ApplicationELB checkbox for Application ELB metrics, and the NetworkELB checkbox for Network ELB metrics.

  2. Add those permissions to your Datadog IAM policy in order to collect Amazon ELB metrics:

    • elasticloadbalancing:DescribeLoadBalancers: List ELBs, add additional tags and metrics.
    • elasticloadbalancing:DescribeTags: Add custom ELB tags to ELB metrics.
    • elasticloadbalancing:DescribeInstanceHealth: Add state of your instances.

    For more information on ELB policies, review the documentation on the AWS website.

  3. Install the Datadog - AWS ELB integration.

Log collection

Enable AWS ELB logging

Enable the logging on your ELB first to collect your logs. ELB logs can be written in a AWS S3 bucket and consumed by a Lambda function. For more information, refer to the AWS documentation

aws elb log enable

Set interval to 5 minutes and define your s3 buckets:

aws elb log configuration

Send logs to Datadog

  1. If you haven’t already, set up the Datadog log collection AWS Lambda function.
  2. Once the lambda function is installed, there are two ways to collect your ELB logs:

Manual installation steps

  1. If you haven’t already, set up the Datadog log collection AWS Lambda function.
  2. Once the lambda function is installed, manually add a trigger on the S3 bucket that contains your ELB logs in the AWS console, in your Lambda, click on S3 in the trigger list:
    S3 trigger configuration
    Configure your trigger by choosing the S3 bucket that contains your ELB logs and change the event type to Object Created (All) then click on the add button.
    S3 Lambda trigger configuration

Once done, go in your Datadog Log section to start exploring your logs!

Data Collected

Metrics

aws.elb.healthy_host_count
(gauge)
Average number of healthy instances in each Availability Zone.
shown as host
aws.elb.healthy_host_count.minimum
(gauge)
Minimum number of healthy instances in each Availability Zone.
shown as host
aws.elb.healthy_host_count.maximum
(gauge)
Maximum number of healthy instances in each Availability Zone.
shown as host
aws.elb.un_healthy_host_count
(gauge)
Average number of unhealthy instances in each Availability Zone.
shown as host
aws.elb.un_healthy_host_count.minimum
(gauge)
Minimium number of unhealthy instances in each Availability Zone.
shown as host
aws.elb.un_healthy_host_count.maximum
(gauge)
Maximum number of unhealthy instances in each Availability Zone.
shown as host
aws.elb.healthy_host_count_deduped
(gauge)
Deduped number of healthy instances in each Availability Zone.
shown as host
aws.elb.un_healthy_host_count_deduped
(gauge)
Deduped number of unhealthy instances in each Availability Zone.
shown as host
aws.elb.request_count
(rate)
Total number of completed requests that were received and routed to the registered instances.
shown as request
aws.elb.backend_connection_errors
(rate)
Number of connections that were not successfully established between the load balancer and the registered instances.
shown as error
aws.elb.estimated_processed_bytes
(count)
The estimated total number of bytes processed by an Application Load Balancer.
shown as byte
aws.elb.estimated_albnew_connection_count
(count)
The estimated total number of new TCP connections established from clients to the load balancer and from the load balancer to targets
aws.elb.estimated_albconsumed_lcus
(gauge)
The estimated total number of load balancer capacity units (LCU) used by an Application Load Balancer.
aws.elb.estimated_albactive_connection_count
(gauge)
The estimated total number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.
aws.elb.surge_queue_length
(gauge)
Maximum number of requests that are pending submission to a registered instance.
shown as request
aws.elb.latency
(gauge)
Average time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.latency.maximum
(gauge)
Maximum time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.latency.p95
(gauge)
95th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.latency.p99
(gauge)
99th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.latency.minimum
(gauge)
Minimum time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.spillover_count
(rate)
Total number of requests that were rejected because the queue was full.
shown as request
aws.elb.spillover_count.maximum
(rate)
Maximum number of requests that were rejected because the queue was full per load balancer node.
shown as request
aws.elb.httpcode_backend_2xx
(rate)
Number of HTTP 2XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_backend_3xx
(rate)
Number of HTTP 3XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_backend_4xx
(rate)
Number of HTTP 4XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_backend_5xx
(rate)
Number of HTTP 5XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_elb_4xx
(rate)
Number of HTTP 4XX client error codes generated by the load balancer.
shown as response
aws.elb.httpcode_elb_5xx
(rate)
Number of HTTP 5XX client error codes generated by the load balancer.
shown as response
aws.elb.httpcode_target_2xx
(count)
Number of HTTP 2XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_target_3xx
(count)
Number of HTTP 3XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_target_4xx
(count)
Number of HTTP 4XX response codes generated by registered instances.
shown as response
aws.elb.httpcode_target_5xx
(count)
Number of HTTP 5XX response codes generated by registered instances.
shown as response
aws.elb.target_response_time.maximum
(gauge)
Maximum time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.target_response_time.average
(gauge)
Average time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.target_response_time.p95
(gauge)
95th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.target_response_time.p99
(gauge)
99th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.elb.target_connection_error_count
(count)
Number of connections that were not successfully established between the load balancer and the registered instances.
shown as error
aws.elb.client_tlsnegotiation_error_count
(count)
Number of TLS negociation errors
shown as error
aws.elb.consumed_lbcapacity_units
(gauge)
Number of ELB capacity units consumed
shown as unit
aws.applicationelb.consumed_lbcapacity_units
(gauge)
Number of ELB capacity units consumed
shown as unit
aws.applicationelb.client_tlsnegotiation_error_count
(gauge)
Number of TLS negociation errors
shown as error
aws.applicationelb.httpcode_elb_4xx
(count)
Number of HTTP 4XX client error codes generated by the load balancer.
shown as response
aws.applicationelb.httpcode_elb_5xx
(count)
Number of HTTP 5XX client error codes generated by the load balancer.
shown as response
aws.applicationelb.httpcode_target_2xx
(count)
Number of HTTP 2XX response codes generated by registered instances.
shown as response
aws.applicationelb.httpcode_target_3xx
(count)
Number of HTTP 3XX response codes generated by registered instances.
shown as response
aws.applicationelb.httpcode_target_4xx
(count)
Number of HTTP 4XX response codes generated by registered instances.
shown as response
aws.applicationelb.httpcode_target_5xx
(count)
Number of HTTP 5XX response codes generated by registered instances.
shown as response
aws.applicationelb.request_count
(count)
Total number of completed requests that were received and routed to the registered instances.
shown as request
aws.applicationelb.target_connection_error_count
(count)
Number of connections that were not successfully established between the load balancer and the registered instances.
shown as error
aws.applicationelb.healthy_host_count
(gauge)
Average number of healthy instances in each Availability Zone.
shown as host
aws.applicationelb.healthy_host_count.minimum
(gauge)
Minimum number of healthy instances in each Availability Zone.
shown as host
aws.applicationelb.healthy_host_count.maximum
(gauge)
Maximum number of healthy instances in each Availability Zone.
shown as host
aws.applicationelb.un_healthy_host_count
(gauge)
Average number of unhealthy instances in each Availability Zone.
shown as host
aws.applicationelb.un_healthy_host_count.minimum
(gauge)
Minimium number of unhealthy instances in each Availability Zone.
shown as host
aws.applicationelb.un_healthy_host_count.maximum
(gauge)
Maximum number of unhealthy instances in each Availability Zone.
shown as host
aws.applicationelb.healthy_host_count_deduped
(gauge)
Deduped number of healthy instances in each Availability Zone.
shown as host
aws.applicationelb.unhealthy_host_count_deduped
(gauge)
Deduped number of unhealthy instances in each Availability Zone.
shown as host
aws.applicationelb.target_response_time.maximum
(gauge)
Maximum time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.applicationelb.target_response_time.average
(gauge)
Average time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.applicationelb.target_response_time.p95
(gauge)
95th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.applicationelb.target_response_time.p99
(gauge)
99th percentile of the time elapsed after the request leaves the load balancer until a response is received.
shown as second
aws.applicationelb.ipv_6request_count
(count)
The number of IPv6 requests received by the load balancer.
shown as request
aws.applicationelb.ipv_6processed_bytes
(count)
The total number of bytes processed by the load balancer over IPv6.
shown as byte
aws.applicationelb.active_connection_count
(gauge)
The total number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.
aws.applicationelb.rejected_connection_count
(count)
The number of connections that were rejected because the load balancer had reached its maximum number of connections.
aws.applicationelb.processed_bytes
(count)
The total number of bytes processed by the load balancer over IPv4 and IPv6.
shown as byte
aws.applicationelb.consumed_lcus
(gauge)
The number of load balancer capacity units (LCU) used by your load balancer.
aws.applicationelb.new_connection_count
(count)
The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets.
aws.networkelb.active_flow_count
(gauge)
The average number of active established connections from clients to targets
aws.networkelb.active_flow_count.maximum
(gauge)
The maximum number of active established connections from clients to targets
aws.networkelb.active_flow_count.minimum
(gauge)
The minimum number of active established connections from clients to targets
aws.networkelb.consumed_lcus
(count)
The number of LCUs used by the load balancer
aws.networkelb.healthy_host_count
(gauge)
Average number of healthy targets
shown as host
aws.networkelb.healthy_host_count.maximum
(gauge)
Maximum number of healthy targets
shown as host
aws.networkelb.healthy_host_count.minimum
(gauge)
Minimum number of healthy targets
shown as host
aws.networkelb.new_flow_count
(count)
The number of new TCP connections from clients to targets
aws.networkelb.processed_bytes
(count)
The number of LCUs used by the load balancer
shown as byte
aws.networkelb.tcpclient_reset_count
(count)
The number of reset (RST) packets created by a client and sent to a target
aws.networkelb.tcpelbreset_count
(count)
The number of reset (RST) packets created by a load balancer
aws.networkelb.tcptarget_reset_count
(count)
The number of reset (RST) packets created by a target and sent to a client
aws.networkelb.un_healthy_host_count
(gauge)
Average number of unhealthy targets
shown as host
aws.networkelb.un_healthy_host_count.maximum
(gauge)
Maximum number of unhealthy targets
shown as host
aws.networkelb.un_healthy_host_count.minimum
(gauge)
Minimum number of unhealthy targets
shown as host

Each of the metrics retrieved from AWS will be assigned the same tags that appear in the AWS console, including but not limited to host name, security-groups, and more.

Events

The AWS Elastic Load Balancing integration does not include any event at this time.

Service Checks

The AWS Elastic Load Balancing integration does not include any service check at this time.

Troubleshooting

Need help? Contact Datadog Support.

Further Reading

Learn more about how to monitor ELB performance metrics thanks to our series of posts. We detail the key performance metrics, how to collect them, and how to use Datadog to monitor ELB.