Network Elastic Load Balancing (ELB) metrics
Amazon Elastic Load Balancing automatically distributes your incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones. Ensure your cloud platform is configured in SolarWinds Observability SaaS to collect this service's data. See Add an AWS cloud account. CloudWatch metrics must also be enabled for this service in the AWS Console for the metric data to be available.
Many of the collected metrics from Network ELB entities are displayed as widgets in SolarWinds Observability explorers; additional metrics may be collected and available in the Metrics Explorer. You can also create an alert for when an entity's metric value moves out of a specific range. See Entities in SolarWinds Observability SaaS for information about entity types in SolarWinds Observability SaaS.
The following table lists AWS.NetworkELB
in the search box.
Metric | Units | Description |
---|---|---|
sw.metrics.healthscore |
Percent (%) |
Health score. A health score provides real-time insight into the overall health and performance of your monitored entities. The health score is calculated based on anomalies detected for the entity, alerts triggered for the entity's metrics, and the status of the entity. The health score is displayed as a single numerical value that ranges from a Good (70-100) to Moderate (40-69) to Bad (0-39) distinction. To view the health score for Network ELB entities in the Metrics Explorer, filter the |
AWS.NetworkELB.ActiveFlowCount
|
Count |
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. |
AWS.NetworkELB.ActiveFlowCount_TCP
|
Count |
The total number of concurrent TCP flows (or connections) from clients to targets. This metric includes connections in the SYN_SENT and ESTABLISHED state. TCP connections are not terminated at the load balancer, so a client opening a TCP connection to a target counts as a single flow. |
AWS.NetworkELB.ActiveFlowCount_TLS
|
Count | The total number of concurrent TLS flows (or connections) from clients to targets. This metric includes connections in the SYN_SENT and ESTABLISHED state. |
AWS.NetworkELB.ActiveFlowCount_UDP
|
Count | The total number of concurrent UDP flows (or connections) from clients to targets. |
AWS.NetworkELB.ClientTLSNegotiationErrorCount
|
Count | The total number of TLS handshakes that failed during negotiation between a client and a TLS listener. |
AWS.NetworkELB.ConsumedLCUs
|
Count |
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. For more information, see Elastic Load Balancing Pricing. |
AWS.NetworkELB.ConsumedLCUs_TCP
|
Count |
The number of load balancer capacity units (LCU) used by your load balancer for TCP. You pay for the number of LCUs that you use per hour. For more information, see Elastic Load Balancing Pricing. |
AWS.NetworkELB.ConsumedLCUs_TLS
|
Count | The number of load balancer capacity units (LCU) used by your load balancer for TLS. You pay for the number of LCUs that you use per hour. For more information, see Elastic Load Balancing Pricing. |
AWS.NetworkELB.ConsumedLCUs_UDP
|
Count | The number of load balancer capacity units (LCU) used by your load balancer for UDP. You pay for the number of LCUs that you use per hour. For more information, see Elastic Load Balancing Pricing. |
AWS.NetworkELB.HealthyHostCount
|
Count |
The number of targets that are considered healthy. This metric does not include any Application Load Balancers registered as targets. |
AWS.NetworkELB.NewFlowCount
|
Count |
The total number of new flows (or connections) established from clients to targets in the time period. |
AWS.NetworkELB.NewFlowCount_TCP
|
Count |
The total number of new TCP flows (or connections) established from clients to targets in the time period. |
AWS.NetworkELB.NewFlowCount_TLS
|
Count | The total number of new TLS flows (or connections) established from clients to targets in the time period. |
AWS.NetworkELB.NewFlowCount_UDP
|
Count | The total number of new UDP flows (or connections) established from clients to targets in the time period. |
AWS.NetworkELB.PeakPacketsPerSecond
|
Count per second |
Highest average packet rate (packets processed per second), calculated every 10 seconds during the sampling window. This metric includes health check traffic. |
AWS.NetworkELB.PortAllocationErrorCount
|
Count |
The total number of ephemeral port allocation errors during a client IP translation operation. A non-zero value indicates dropped client connections. Network Load Balancers support 55,000 simultaneous connections or about 55,000 connections per minute to each unique target (IP address and port) when performing client address translation. To fix port allocation errors, add more targets to the target group. |
AWS.NetworkELB.ProcessedBytes
|
bytes |
The total number of bytes processed by the load balancer, including TCP/IP headers. This count includes traffic to and from targets, minus health check traffic. |
AWS.NetworkELB.ProcessedBytes_TCP
|
bytes |
The total number of bytes processed by TCP listeners. |
AWS.NetworkELB.ProcessedBytes_TLS
|
bytes | The total number of bytes processed by TLS listeners. |
AWS.NetworkELB.ProcessedBytes_UDP
|
bytes | The total number of bytes processed by UDP listeners. |
AWS.NetworkELB.ProcessedPackets
|
Count |
The total number of packets processed by the load balancer. This count includes traffic to and from targets, including health check traffic. |
AWS.NetworkELB.RejectedFlowCount
|
Count |
The number of network flows rejected by the Network Load Balancer due to security group rules or other policies. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Inbound_ICMP
|
Count | The number of new ICMP messages rejected by the inbound rules of the load balancer security groups. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Inbound_TCP
|
Count |
The number of new TCP flows rejected by the inbound rules of the load balancer security groups. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Inbound_UDP
|
Count | The number of new UDP flows rejected by the inbound rules of the load balancer security groups. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Outbound_ICMP
|
Count | The number of new ICMP messages rejected by the outbound rules of the load balancer security groups. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Outbound_TCP
|
Count | The number of new TCP flows rejected by the outbound rules of the load balancer security groups. |
AWS.NetworkELB.SecurityGroupBlockedFlowCount_Outbound_UDP
|
Count | The number of new UDP flows rejected by the outbound rules of the load balancer security groups. |
AWS.NetworkELB.TargetTLSNegotiationErrorCount
|
Count | The total number of TLS handshakes that failed during negotiation between a TLS listener and a target. |
AWS.NetworkELB.TCP_Client_Reset_Count
|
Count |
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. |
AWS.NetworkELB.TCP_ELB_Reset_Count
|
Count |
The total number of reset (RST) packets generated by the load balancer. For more information, see Troubleshooting. |
AWS.NetworkELB.TCP_Target_Reset_Count
|
Count |
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. |
AWS.NetworkELB.UnHealthyHostCount
|
Count | The number of targets that are considered unhealthy. This metric does not include any Application Load Balancers registered as targets. Reporting criteria: Reported if health checks are enabled. |
AWS.NetworkELB.UnhealthyRoutingFlowCount
|
Count | The number of flows (or connections) that are routed using the routing failover action (fail open). |
AWS.NetworkELB.ZonalHealthStatus
|
Status Indicator | Represents the health status of a Network Load Balancer in each availability zone, helping to identify failover events and potential issues. |