Skip to main content
Version: NG-2.14

AWS Classic ELB

Introduction

Amazon Classic ELB is a classic load balancer that is used to distribute incoming application traffic across multiple EC2 instances in multiple Availability Zones.

Getting Started

Compatibility

vuSmartMaps supports the monitoring of the flow of traffic in your AWS Classic Load Balancer (ELB)

Data Collection Method

vuSmartMaps collects health and performance data for AWS Classic ELB using VuNet's Internal Data Collector.

Prerequisites

Dependent Configuration

To configure this O11ySource, create a 'credential' of type 'aws' under the 'Definition' tab.

Inputs for Configuring Data Source

  • Load Balancer Name: The name of the load balancer instance.
  • AWS Region: AWS Region where the instance of this component is running. For eg: Asia Pacific (Mumbai), the region would be ap-south-1.
  • AWS Credential: AWS credential that provides Access key and Secret key to access Cloudwatch.
  • Period (in minutes): Specifies the interval in minutes at which data is collected. Data collection occurs once every specified period. The period should be between 1 - 60 minutes.

Firewall Requirement

To collect data from this O11ySource, ensure the following ports are opened:

Source IPDestination IPDestination PortProtocolDirection
vuSmartMaps IPAWS CloudWatch IPs443*TCPOutbound

*Before providing the firewall requirements, please update the port based on the customer environment.

Configuring the Target

Health and Performance metrics of AWS Classic ELB is collected through CloudWatch service. So AWS CloudWatch services must be enabled in your AWS account.

An IAM role or user with the following permissions to access CloudWatch metrics:

  • cloudwatch:GetMetricData
  • cloudwatch:ListMetrics

Configuration Steps

  • Enable the O11ySource.
  • Select the sources tab and press the + button to add a new instance that has to be monitored.
  • Provide the required configurations:
  • *Source Name
  • *AWS Region
  • *Credential
  • *Period
  • Click Save to close the data source window.

Metrics Collected

NameDescriptionData Type
TimestampTimestamp at which metrics are collected from source.DateTime
O11ySource NameThe name of the observability source.String
Tenant IDTenant ID.String
BU IDBU ID.String
TargetTarget server at which the agent is running.String
IntervalTime interval at which data are polling.UInt8
RegionAWS Region at which the load balancer instance is configured.String
Availability ZoneThe availability zone of the load balancer instance.String
Load Balancer NameThe name of the load balancer instance.String
BackendConnectionErrorsThe number of connections that were not successfully established between the load balancer and the registered instances. Because the load balancer retries the connection when there are errors, this count can exceed the request rate. Note that this count also includes any connection errors related to health checks.UInt64
EstimatedALBActiveConnectionCountThe estimated number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.UInt64
EstimatedALBConsumedLCUsThe estimated number of load balancer capacity units (LCU) used by an Application Load Balancer. You pay for the number of LCUs that you use per hour.Float64
EstimatedALBNewConnectionCountThe estimated number of new TCP connections established from clients to the load balancer and from the load balancer to targets.UInt64
EstimatedProcessedBytesThe estimated number of bytes processed by an Application Load Balancer.Float64
HealthyHostCountThe number of healthy instances registered with your load balancer. A newly registered instance is considered healthy after it passes the first health check. If cross-zone load balancing is enabled, the number of healthy instances for the LoadBalancerName dimension is calculated across all Availability Zones. Otherwise, it is calculated per Availability Zone.UInt32
HTTPCode_Backend_2XX[HTTP listener] The number of HTTP 2xx response codes generated by registered instances. This count does not include any response codes generated by the load balancer.UInt64
HTTPCode_Backend_3XX[HTTP listener] The number of HTTP 3xx response codes generated by registered instances. This count does not include any response codes generated by the load balancer.UInt64
HTTPCode_Backend_4XX[HTTP listener] The number of HTTP 4xx response codes generated by registered instances. This count does not include any response codes generated by the load balancer.UInt64
HTTPCode_Backend_5XX[HTTP listener] The number of HTTP 5xx response codes generated by registered instances. This count does not include any response codes generated by the load balancer.UInt64
HTTPCode_ELB_4XX[HTTP listener] The number of HTTP 4XX client error codes generated by the load balancer. Client errors are generated when a request is malformed or incomplete.UInt64
HTTPCode_ELB_5XX[HTTP listener] The number of HTTP 5XX server error codes generated by the load balancer. This count does not include any response codes generated by the registered instances. The metric is reported if there are no healthy instances registered to the load balancer, or if the request rate exceeds the capacity of the instances (spillover) or the load balancer.UInt64
Latency[HTTP listener] The avg time elapsed, in seconds, from the time the load balancer sent the request to a registered instance until the instance started to send the response headers. [TCP listener] The avg time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.Float64
RequestCountThe number of requests completed or connections made during the specified interval (1 or 5 minutes). [HTTP listener] The number of requests received and routed, including HTTP error responses from the registered instances. [TCP listener] The number of connections made to the registered instances.UInt64
SpilloverCountThe total number of requests that were rejected because the surge queue is full. [HTTP listener] The load balancer returns an HTTP 503 error code. [TCP listener] The load balancer closes the connection.UInt64
SurgeQueueLengthThe total number of requests (HTTP listener) or connections (TCP listener) that are pending routing to a healthy instance. The maximum size of the queue is 1,024. Additional requests or connections are rejected when the queue is full.UInt64
UnHealthyHostCountThe number of unhealthy instances registered with your load balancer. An instance is considered unhealthy after it exceeds the unhealthy threshold configured for health checks. An unhealthy instance is considered healthy again after it meets the healthy threshold configured for health checks.UInt32