Download PDF
Download page Amazon Application, Classic, and Network Load Balancers.
Amazon Application, Classic, and Network Load Balancers
The Amazon Application, Classic, and Network load balancers distribute incoming HTTP and HTTPS traffic, referred to as the load, from clients to your backend targets in one or more Availability Zones. To do this, Amazon load balancers examine the health status of targets to determine which ones are healthy and routes traffic only to healthy targets. They automatically reconfigure themselves as your incoming traffic changes over time.
You must configure cloud connections to monitor this entity. See Set up Cisco AppDynamics Cloud Collectors to Monitor AWS.
Cisco Cloud Observability displays AWS entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.
This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.
Detail View
To display the detail view for an Amazon load balancer:
- Navigate to the Observe page.
- Under Networking & App Delivery, click a Load Balancers group.
The Load Balancers list view now displays. - Click the AWS tab to display only AWS load balancers.
- From the list, click a load balancer Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the load balancer you selected.
Metrics and Key Performance Indicators
Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for Amazon load balancers.
See the following pages in the AWS documentation for details:
- CloudWatch metrics for your Application Load Balancer
- CloudWatch metrics for your Classic Load Balancer
- Troubleshoot a Classic Load Balancer: Response code metrics
- CloudWatch metrics for your Network Load Balancer
Display Name | Source Metric | Description |
---|---|---|
Active Connection Count |
| The total number of active concurrent Transmission Control Protocol (TCP) connections from clients to the load balancer and from the load balancer to targets. |
Consumed Load Balancer Capacity Units (Count) |
| The number of load balancer capacity units (LCUs) used by the load balancer. |
HTTP Error Code Summary (Count) |
| The number of HTTP 4XX redirection codes and 5XX error codes originating from the load balancer. |
Healthy Host Count | HealthyHostCount | The number of healthy targets. |
HTTP 500 Errors (Count) |
| The number of HTTP 5XX error codes originating from the load balancer. |
HTTP 502 Errors (Count) |
| The number of HTTP 502 error codes originating from the load balancer. |
HTTP 503 Errors (Count) |
| The number of HTTP 503 error codes originating from the load balancer. |
HTTP 504 Errors (Count) |
| The number of HTTP 504 error codes originating from the load balancer. |
HTTP Fixed Response Count | HTTP_Fixed_Response_Count | The number of successful fixed-response actions. |
HTTP Redirect Count | HTTP_Redirect_Count | The number of successful redirect actions. |
HTTP Redirect URL Limit Exceeded Count | HTTP_Redirect_Url_Limit_Exceeded_Count | The number of redirect actions that could not be completed because the URL in the response location header exceeded 8K. |
New Connections |
| The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets. |
Non Sticky Request Count | NonStickyRequestCount | The number of requests where the load balancer chose a new target because it couldn't use an existing sticky session. |
Processed Bytes |
| The total number of bytes processed by the load balancer over IPv4 and IPv6. |
Requests (Count) |
| The number of requests processed over IPv4 and IPv6. |
Rule Evaluations (Count) |
| The number of rules processed by the load balancer. |
Sum Rejected Connections |
| The number of connections that were rejected because the load balancer had reached its maximum number of connections. |
Target Connection Errors |
| The number of connections that were not successfully established between the load balancer and target. |
Target HTTP Code (Count) |
| The number of HTTP 2XX and 3XX response codes generated by targets. |
Target HTTP Code (Count) |
| The number of HTTP 4XX and 5XX response codes generated by targets. |
Target Response Time (MS) | TargetResponseTime | The time elapsed after a request leaves the load balancer until it receives a response from the target. |
TLS Negotiation Errors |
| The number of client-initiated TLS connections that did not establish a session with the load balancer due to a TLS error and the number of load balancer-initiated TLS connections that did not establish a session with the target due to a TLS error. |
Unhealthy Host Count | UnHealthyHostCount | The number of unhealthy targets. |
Display Name | Source Metric | Description |
---|---|---|
Average Latency (Sec) |
| The total time elapsed from the time the load balancer sent the request to a registered instance until the instance started to send the response headers. |
Backend Connection Errors (Count) | BackendConnectionErrors | The number of failed connections between the load balancer and the registered instances. |
Backend HTTP Code (Count) |
| For HTTP listeners, this metric is the number of HTTP response codes generated by registered instances. |
ELB HTTP Error Code (Count) |
| The number of HTTP 4XX redirection codes and 5XX error codes originating from the load balancer. |
Estimated Processed Bytes |
| The total number of bytes processed by the load balancer over IPv4 and IPv6. |
Healthy Hosts (Count) |
| The number of healthy instances registered with the load balancer. |
Requests (Count) |
| The number of requests processed over IPv4 and IPv6. |
Spillover Count |
| The total number of requests that were rejected because the surge queue is full. |
Surge Queue Length (Count) |
| The total number of requests (HTTP listener) or connections (TCP listener) that are pending routing to a healthy instance. |
Unhealthy Hosts (Count) |
| The number of unhealthy instances registered with the load balancer. |
Display Name | Source Metric | Description |
---|---|---|
Active Flow Count | ActiveFlowCount | The total number of concurrent flows (or connections) from clients to targets. |
Active Flow Count TCP | ActiveFlowCount_TCP | The total number of concurrent TCP flows (or connections) from clients to targets. |
Active Flow Count TLS |
| The total number of concurrent TLS flows (or connections) from clients to targets. |
Active Flow Count UDP | ActiveFlowCount_UDP | The total number of concurrent UDP flows (or connections) from clients to targets. |
Consumed Load Balancer Capacity Units (Count) |
| The number of load balancer capacity units (LCUs) used by the load balancer. |
Healthy Hosts (Count) |
| The number of healthy targets registered with the load balancer. |
New Flow Count | NewFlowCount | The total number of new flows (or connections) established from clients to targets in the time period. |
Processed Bytes | ProcessedBytes | The total number of bytes processed by the load balancer over IPv4 and IPv6. |
TCP Reset Count |
| The total number of reset (RST) packets sent from a client to a target or from a target to a client or generated by the load balancer. |
TLS Negotiation Error Count |
| The number of client-initiated TLS connections that did not establish a session with the load balancer due to a TLS error and the number of load balancer-initiated TLS connections that did not establish a session with the target. |
Unhealthy Hosts (Count) |
| The number of unhealthy targets registered with the load balancer. |
Properties (Attributes)
Cisco Cloud Observability displays the following properties for Amazon load balancers.
For more information, see:
Display Name | Property Name | Description |
---|---|---|
Name |
| The name of the load balancer. |
Created At |
| The time that the load balancer was created. |
DNS Name |
| The DNS name of the load balancer. |
Load Balancer ARN |
| The Amazon Resource Name (ARN) of the load balancer. |
AWS Account ID |
| The cloud account ID where the resource is assigned. |
AWS Region |
| The geographical region where the resource is running. |
AWS Availability Zone |
| The logical zone list for the load balancer. |
VPC ID |
| The ID of the virtual private cloud (VPC) where the load balancer is connected. |
Display Name | Property Name | Description |
---|---|---|
Name |
| The name of the load balancer. |
DNS Name |
| The DNS name of the load balancer. |
Load Balancer ARN |
| The Amazon Resource Name (ARN) of the load balancer. |
AWS Account ID |
| The cloud account ID where the resource is assigned. |
AWS Region |
| The geographical region where the resource is running. |
AWS Availability Zone |
| The logical zone list for the load balancer. |
VPC ID |
| The ID of the virtual private cloud (VPC) where the load balancer is connected. |
Display Name | Property Name | Description |
---|---|---|
Name |
| The name of the load balancer. |
Created At |
| The time that the load balancer was created. |
DNS Name |
| The DNS name of the load balancer. |
Load Balancer ARN |
| The Amazon Resource Name (ARN) of the load balancer. |
AWS Account ID |
| The cloud account ID where the resource is assigned. |
AWS Region |
| The geographical region where the resource is running. |
AWS Availability Zone |
| The logical zone list for the load balancer. |
VPC ID |
| The ID of the virtual private cloud (VPC) where the load balancer is connected. |
Retention and Purge Time-To-Live (TTL)
For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).
Amazon Web Services, the AWS logo, AWS, and any other AWS Marks used in these materials are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.