AWS ALB monitoring integration

Access to this feature depends on your subscription level. Requires Infrastructure Pro.

Amazon Application Load Balancing (ALB) distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple Availability Zones. New Relic Infrastructure integrations include an integration for reporting your AWS ALB data to New Relic products. This document explains how to activate this integration and describes the data that can be captured.

New Relic also offers an integration for Amazon's Elastic Load Balancing (ELB) service.

Activate integration

To enable this integration:

  1. Make sure you have installed the Infrastructure agent before you activate AWS integrations from your Infrastructure account.
  2. Follow standard procedures to Connect AWS services to Infrastructure.

Configuration and polling

You can change the polling frequency and filter data using configuration options.

Default polling information for the AWS ALB integration:

  • New Relic polling interval: 5 minutes
  • Amazon CloudWatch data interval: 1 minute

Find and use data

To find your integration data in Infrastructure, go to infrastructure.newrelic.com > Integrations > Amazon Web Services and select one of the AWS ALB integration links.

In New Relic Insights, data is attached to the LoadBalancerSample event type. There are two categories of data: ALB and ALB target group. In Insights, these would have provider values of Alb and AlbTargetGroup.

For more on how to use your data, see Understand and use integration data.

Metric data

There are two ALB integration categories of data: ALB and ALB target group.

ALB metrics

New Relic Infrastructure Amazon integrations collect the following Amazon ALB data to the provider Alb.

Metric Description

activeConnectionCount
count

The total number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.

newConnectionCount
count

The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets.

rejectedConnectionCount
count

The number of connections that were rejected because the load balancer had reached its maximum number of connections.

processedBytes
count

The total number of bytes processed by the load balancer over IPv4 and IPv6.

requestCount
count

The number of requests received by the load balancer. This includes requests over IPv4 and IPv6.

rulesEvaluated
count

The number of rules processed by the load balancer given a request rate averaged over an hour.

clientTlsNegotiationErrorCount
count

The number of TLS connections initiated by the client that did not establish a session with the load balancer. Possible causes include a mismatch of ciphers or protocols.

httpCodeElb5XXCount
count

The number of HTTP 5XX server error codes that originate from the load balancer. This count does not include any response codes generated by the targets.

httpCodeElb4XXCount
count

The number of HTTP 4XX client error codes that originate from the load balancer. Client errors are generated when requests are malformed or incomplete. These requests have not been received by the target.

IpV6ProcessedBytes
count

The total number of bytes processed by the load balancer over IPv6.

IpV6RequestCount
count

The number of IPv6 requests received by the load balancer.

ALB target group metrics

Target group data is stored in Insights in the provider AlbTargetGroup. For example, you might use this data to facet error metrics by target group.

Metric Description
requestCount
count
The number of requests received by the load balancer. This includes requests over IPv4 and IPv6.
healthyHostCount
count
The number of targets that are considered healthy.
unHealthyHostCount
count
The number of targets that are considered unhealthy.
targetResponseTime
count
The time elapsed, in seconds, after the request leaves the load balancer until a response from the target is received.
httpCodeTarget2XXCount
count
The number of HTTP response codes generated by the targets. This does not include any response codes generated by the load balancer.
httpCodeTarget3XXCount
count
The number of HTTP response codes generated by the targets. This does not include any response codes generated by the load balancer.
httpCodeTarget4XXCount
count
The number of HTTP response codes generated by the targets. This does not include any response codes generated by the load balancer.
httpCodeTarget5XXCount
count
The number of HTTP response codes generated by the targets. This does not include any response codes generated by the load balancer.

Inventory data

Inventory data provides information about the service's state and configuration. ALB configuration options are reported as inventory data. For more about inventory data, see Understand and use data.

AWS ALB inventory

Name Description
LoadBalancerArn The Amazon Resource Name (ARN) of the load balancer.
DNSName The public DNS name of the load balancer.
CanonicalHostedZoneId The ID of the Amazon Route 53 hosted zone associated with the load balancer.
CreatedTime Timestamp with the date and time the load balancer was created.
LoadBalancerName The name of the load balancer.
Scheme

The nodes of an Internet-facing load balancer have public IP addresses. The DNS name of an Internet-facing load balancer is publicly resolvable to the public IP addresses of the nodes. Therefore, Internet-facing load balancers can route requests from clients over the Internet.

The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can only route requests from clients with access to the VPC for the load balancer.

VpcId The ID of the VPC for the load balancer.
State Structure indicating the state of the load balancer.
Code The state code. The initial state of the load balancer is provisioning. After the load balancer is fully set up and ready to route traffic, its state is active. If the load balancer could not be set up, its state is failed.
Reason A description of the state.
Type The type of load balancer.
AvailabilityZones

Can be a list or a structure.

As list: the Availability Zones for the load balancer.

As structure: information about an Availability Zone.

ZoneName The name of the Availability Zone.
SubnetId The ID of the subnet.
SecurityGroups List of the security group IDs for the load balancer.
IpAddressType The type of IP addresses used by the subnets for your load balancer. The possible values are ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses).

ALB target group inventory

Name Description
TargetGroupArn The Amazon Resource Name (ARN) of the target group.
TargetGroupName The name of the target group.
Protocol The protocol to use for routing traffic to the targets.
Port The port on which the targets are listening.
VpcId The ID of the VPC for the targets.
HealthCheckProtocol The protocol to use to connect with the target.
HealthCheckPort The port to use to connect with the target.
HealthCheckIntervalSeconds The approximate amount of time, in seconds, between health checks of an individual target.
HealthCheckTimeoutSeconds The amount of time, in seconds, during which no response means a failed health check.
HealthyThresholdCount The number of consecutive health checks successes required before considering an unhealthy target healthy.
UnhealthyThresholdCount The number of consecutive health check failures required before considering the target unhealthy.
HealthCheckPath The destination for the health check request.
Matcher Structure showing the HTTP codes to use when checking for a successful response from a target.
HttpCode The HTTP codes. You can specify values between 200 and 499. The default value is 200. You can specify multiple values (for example, "200,202") or a range of values (for example, "200-299").
LoadBalancerArns List with the Amazon Resource Names (ARN) of the load balancers that route traffic to this target group.

For more help

Recommendations for learning more: