• Log in

AWS ALB/NLB monitoring integration

Important

Enable the AWS CloudWatch Metric Streams integration to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.

Amazon Application Load Balancing (ALB) distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple availability zones. Amazon Network Load Balancer (NLB) distributes incoming traffic across multiple targets, such as Amazon EC2 instances.

New Relic infrastructure integrations include an integration for reporting your AWS ALB/NLB 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, follow standard procedures to connect AWS services to New Relic.

Configuration and polling

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

Default polling information for the AWS ALB/NLB integration:

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

View and use data

To view and use your integration data, go to one.newrelic.com > Infrastructure > AWS and select one of the AWS ALB integration links.

You can query and explore your data using the LoadBalancerSample event type within four categories of data:

  • ALB: Appears in New Relic with provider value Alb.
  • NLB: Appears in New Relic with provider value Nlb.
  • ALB target group: Appears in New Relic with provider value AlbTargetGroup.
  • NLB target group: Appears in New Relic with provider valueNlbTargetGroup.

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

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

newConnectionCount

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

rejectedConnectionCount

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

processedBytes

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

requestCount

The count of requests processed over IPv4 and IPv6. Requests only increment this metric when the load balancer node was able to select a target. If a request is rejected before a target is choses, it is not reflected.

Stats: Sum provides the most value.

rulesEvaluated

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

clientTlsNegotiationErrorCount

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

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

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

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

IpV6RequestCount

The number of IPv6 requests received by the load balancer.

lambdaTargetProcessedBytes

The total number of bytes processed by the load balancer for requests to and responses from a Lambda function.

ALB target group metrics

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

Metric

Description

requestCount

The average count of requests that each target in a target group receives.

Stats: Only Sum is valid, which represents the average instead of the sum.

healthyHostCount

The number of targets that are considered healthy.

unHealthyHostCount

The number of targets that are considered unhealthy.

targetResponseTime

The time elapsed, in seconds, after the request leaves the load balancer until a response from the target is received.

Available statistics:

  • aws.applicationelb.target_response_time.p90
  • aws.applicationelb.target_response_time.p95
  • aws.applicationelb.target_response_time.p99

httpCodeTarget2XXCount

The number of HTTP 2XX response codes generated by the targets. This does not include any response codes generated by the load balancer.

httpCodeTarget3XXCount

The number of HTTP 3XX response codes generated by the targets. This does not include any response codes generated by the load balancer.

httpCodeTarget4XXCount

The number of HTTP 4XX response codes generated by the targets. This does not include any response codes generated by the load balancer.

httpCodeTarget5XXCount

The number of HTTP 5XX response codes generated by the targets. This does not include any response codes generated by the load balancer.

lambdaInternalError

The number of requests to a Lambda function that failed because of an issue internal to the load balancer or AWS Lambda.

lambdaUserError

The number of requests to a Lambda function that failed because of an issue with the Lambda function.

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

NLB metrics

New Relic Infrastructure Amazon integrations collect the following Amazon NLB data to the provider Nlb.

Metric

Description

activeFlowCount

The total number of concurrent flows (or connections) from clients to targets. This metric includes connections in the SYN_SENT and ESTABLISHED states.

TCP connections are not terminated at the load balancer, so a client opening a TCP connection to a target counts as a single flow.

activeFlowCountTls

The total number of concurrent TLS flows (or connections) from clients to targets. This metric includes only connections in the ESTABLISHED states.

clientTlsNegotiationErrorCount

The total number of TLS handshakes that failed during negotiation between a client and a TLS listener.

consumedLcus

The number of load balancer capacity units (LCU) used by your load balancer. You pay for the number of LCUs that you use per hour.

newFlowCount

The total number of new flows (or connections) established from clients to targets in the time period.

newFlowCountTls

The total number of new TLS flows (or connections) established from clients to targets in the time period.

processedBytes

The total number of bytes processed by the load balancer, including TCP/IP headers.

processedBytesTls

The total number of bytes processed by TLS listeners.

targetTlsNegotiationErrorCount

The total number of TLS handshakes that failed during negotiation between a TLS listener and a target.

tcpClientResetCount

The total number of reset (RST) packets sent from a client to a target. These resets are generated by the client and forwarded by the load balancer.

tcpElbResetCount

The total number of reset (RST) packets generated by the load balancer.

tcpTargetResetCount

The total number of reset (RST) packets sent from a target to a client. These resets are generated by the target and forwarded by the load balancer.

NLB target group metrics

Target group data is stored in New Relic in the provider NlbTargetGroup. For example, you can use this data to facet error metrics by target group.

Metric

Description

healthyHostCount

The number of targets that are considered healthy.

unHealthyHostCount

The number of targets that are considered unhealthy.

Copyright © 2022 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.