New Relic infrastructure integrations include an Amazon Elastic Classic Load Balancing (ELB) integration for reporting Classic ELB data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported.
New Relic's integration for Amazon Elastic Classic Load Balancing (ELB) reports ELB data, including HTTP code message counts, healthy and unhealthy host counts, latency times, and ELB configuration states. AWS integration data is also available for querying and chart creation in New Relic One.
Amazon offers three types of load balancers: Classic Load Balancer, Application Load Balancer (ALB), and Network Load Balancer (NLB). New Relic also offers an ALB/NLB integration to monitor the last two types of load balancers.
To enable this integration, follow standard procedures to connect AWS services to New Relic.
You can change the polling frequency and filter data using configuration options.
Default polling information for the AWS ELB integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute
The integration collects the following metrics. For additional details about these metrics, see Amazon's ELB Classic Load Balancer metrics documentation.
Rate of the number of connections per second that were not successfully established between the load balancer and the registered instances.
The load balancer retries the connection when there are errors, so this count may exceed the request rate. This count also includes any connection errors related to health checks.
The number of healthy or unhealthy 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
[HTTP listener] The number of HTTP response codes generated per second by registered instances. This count does not include any response codes generated by the load balancer.
[HTTP listener] The number of HTTP
[HTTP listener] The number of HTTP
[HTTP listener] The total 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 total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.
The number of requests completed or connections made per second during the specified interval (1 or 5 minutes).
The total number of requests that were rejected per second, due to the surge queue being full.
The total number of requests that are pending routing. The load balancer queues a request if it is unable to establish a connection with a healthy instance in order to route the request.
The maximum size of the queue is 1,024. Additional requests are rejected when the queue is full. For more information, see
The estimated number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.
The estimated number of load balancer capacity units (LCU) used by an application load balancer.
The estimated number of new TCP connections established from clients to the load balancer and from the load balancer to targets.
The estimated number of bytes processed by an application load balancer.
The following configuration options are available with the New Relic Amazon ELB integration.
Lists one or more availability zones from the same region as the load balancer.
The AWS region that the load balancer runs in.
The ID of the Amazon Route 53 hosted zone name associated with the load balancer.
The name of the Amazon Route 53 hosted zone that is associated with the load balancer.
If you specify
Timestamp with the date and time the load balancer was created.
The public DNS name of the load balancer.
A JSON string representing the list of IDs of EC2 instances associated with the load balancer.
A JSON string representing the list of Listeners associated with the load balancer.
The name of the load balancer.
For load balancers attached to an Amazon VPC, this parameter can be used to specify the type of load balancer to use. For more information, see the AWS ElasticLoadBalancing documentation about LoadBalancer properties.
The security group that you can use as part of your inbound rules for your load balancer's back-end Amazon EC2 application instances.
A JSON string representing the list of subnet IDs in your virtual private cloud (VPC) to attach to your load balancer. Do not specify multiple subnets that are in the same Availability Zone. You can specify the
The ID of the VPC that the load balancer has been configured in.
Data indicated with an asterisk
* is only fetched if extended inventory collection is on.
A boolean. If
A boolean. Use connection draining to ensure that a Classic Load Balancer does not send requests to unhealthy instances. For more information, see the AWS documentation to configure connection draining for your Classic Load Balancer.
The number of seconds the load balancer waits before forcibly closing connections to the de-registering instance. Valid values are
For more information, see the AWS documentation to configure the idle connection timeout for your Classic Load Balancer.
A boolean. For more information, see the AWS documentation to configure cross-zone load balancing for your Classic Load Balancer.
The number of consecutive successful health checks that must occur before declaring an EC2 instance healthy. Valid values:
The amount of time in seconds between health checks of an individual instance. Valid values:
Combination of three properties:
The amount of time in seconds to wait when receiving a response from the health check. Valid values:
The number of consecutive failed health checks that must occur before declaring an EC2 instance unhealthy. Valid values:
JSON string representing security policies associated with this load balancer.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.