Skip to main content

Load Balancer Statistics Monitoring

Load Balancer Stats provides detailed statistics on load balancer performance and operational status, including traffic throughput, listener and server status, and session counts. This information helps you assess operational effectiveness and detect potential system issues early.

Accessing Statistics​

To access Load Balancer statistics:

  1. Log in to the vCloud system
  2. Navigate to Load Balancers > Monitoring > Stats

Figure needed: [Load Balancer Stats interface showing detailed statistics for listeners and backend servers with traffic metrics]

Statistics Overview​

The Load Balancer Stats interface displays detailed statistics for each listener, helping you monitor real-time performance.

Key Listener Metrics​

Each Load Balancer listener displays the following important information:

FieldDescription
NameListener identifier (e.g., listener-lb0)
StatusListener operational status (Open, Close)
PortPort the listener is monitoring (e.g., 10254, 80, 443)
Data TransferTotal IN/OUT traffic throughput (KB)
Session RateConnection session rate: Max/s and Current/s

Backend Server Details​

Within each listener, the server (backend server) list displays the following metrics:

FieldDescription
Server NameInternal server identifier associated with Load Balancer
StatusServer operational status (Up, Down)
PortPort open to receive traffic from Load Balancer
Total SessionTotal sessions processed through this server

Understanding and Analyzing Metrics​

1. Status Indicators​

  • Open: Listener is operating normally and ready to process traffic
  • Close: Listener is currently unavailable or disabled

2. Data Transfer Metrics​

  • IN: Total traffic coming into Load Balancer from clients
  • OUT: Total traffic going out from Load Balancer to clients

Monitoring IN/OUT ratios can help detect abnormal traffic patterns or performance issues.

3. Session Rate Analysis​

  • Max/s: Maximum connection sessions processed per second
  • Current/s: Current connection sessions being processed per second

If Current/s approaches Max/s, consider scaling Load Balancer configuration or adding backend servers.

4. Backend Server Status​

  • Up: Server is operational and ready to receive traffic
  • Down: Server is unavailable and removed from load balancing rotation

Servers in Down status will not receive traffic from the Load Balancer until they return to Up status.

Best Practice

When Session Rate consistently approaches 80% of maximum for several consecutive days, consider expanding configuration or adding backend servers to ensure load capacity.

Performance Monitoring Considerations​

Beyond basic resource metrics, consider these factors when monitoring Load Balancer performance:

1. Concurrent Connections​

Concurrent connections are a key metric for assessing Load Balancer processing capacity. If concurrent connections approach your configuration package limits, consider upgrading.

2. Response Time (Latency)​

High response times may indicate:

  • System overload
  • Suboptimal configuration
  • Backend server performance issues

3. Traffic Distribution​

Check traffic distribution balance across backend servers. Imbalanced distribution may indicate load balancing algorithm issues or backend server health problems.

Key Performance Indicators​

  • Session distribution: Should be evenly spread across healthy backend servers
  • Error rates: Monitor for increased 5xx errors indicating backend issues
  • Health check failures: Track patterns in backend server unavailability
  • Peak traffic handling: Ensure capacity during high-traffic periods
Important Note

Load Balancer serves as the single point of entry for many applications. Monitoring its performance is critical to ensuring high system availability.