This section contains the following sections:

Pools maintain the list of servers assigned to them and perform health monitoring, load balancing, persistence, and functions that involve NSX Advanced Load Balancer-to-server interaction. A typical virtual service will point to one pool; however, more advanced configurations may have a virtual service content switching across multiple pools via HTTP Request Policies or DataScripts. A pool may only be used or referenced by only one virtual service at a time.



Creating a virtual service using the basic method automatically creates a new pool for that virtual service, using the name of the virtual service with a -pool appended. When creating a virtual service via the advanced mode, an existing, unused pool may be specified, or a new pool may be created.

Pools Page

Navigate to Applications > Pools to open the pools page. This page displays a high-level overview of configured pools.

You can create a new pool by clicking on CREATE POOL button, or edit the pool by clicking on the pencil icon.

The following are the information for each pool. The columns shown may be modified using the sprocket icon in the top right of the table:



Field

Description

Name

Lists the name of each pool. Clicking the name opens the Analytics tab of the Pool Details page.

Health

Provides both a number from 1-100 and a color-coded status to provide quick information about the health of each pool. This will be gray if the pool is unused, such as not associated with a virtual service or associated with a VS that can not or has not been placed on a Service Engine.

  • Hovering the cursor over the health score opens the pool’s Health Score popup.

  • Clicking the View Insights link at the bottom of the pool’s Health Score popup opens the health Insights tab of the Pool Detail page.

  • Clicking elsewhere within the pool’s Health Score popup opens the Analytics tab of the Pool Details page.

Servers

Displays the number of servers in the pool that are up out of the total number of servers assigned to the pool. For instance, 2/3 indicates that two of the three servers in the pool are successfully passing health checks and are considered up.

Virtual Service

The VS the pool is assigned to. Clicking a name in this column opens the VS Analytics tab of the Virtual Service Details page. If no virtual service is listed, this pool is considered unused.

Cloud

It displays the relevant cloud.

RPS

It indicates the performance of the CPU.

Open Conns

It displays the open conns of the respective pool.

Throughput

Thumbnail chart of the throughput in Mbps for each pool for the time frame selected.

  • Hovering the cursor over this graph shows the throughput at the selected time.

  • Clicking a graph opens the Analytics tab of the pool’s Details page.

Pool Details Page

Clicking into a pool brings up the Details pages, which provide deeper views into the current pool.



This page contains the following sub-pages:

  • Analytics

  • Logs

  • Health

  • Servers

  • Events

  • Alerts

Pool Analytics Page

The pool’s Analytics tab presents information about various pool performance metrics. The data shown is filtered by the time period selected.



Refer to the following for detailed information about this tab:

  • End-to-End Timing

  • Metric Tiles

  • Chart Pane

  • Overlays Pane

    • Anomalies

    • Alerts

    • Config Events

    • System Events

Pool End-to-End Timing

The End-to-End Timing pane at the top of the Analytics tab of the Pool Details page provides a high-level overview of the quality of the end-user experience and where any slowdowns may be occurring. The chart breaks down the time required to complete a single transaction, such an HTTP request.

It may be helpful to compare the end-to-end time against other metrics, such as throughput, to see how traffic increases impact the ability of the application to respond. For instance, if new connections double but the end-to-end time quadruples, you may need to consider adding additional servers.



From left to right, this pane displays the following timing information:

Field

Description

Server RTT

This is Service Engine to server round trip latency. An abnormally high server RTT may indicate either that the network is saturated or more likely that a server’s TCP stack is overwhelmed and cannot quickly establish new connections.

App Response

The time the servers take to respond. This includes the time the server took to generate content, potentially fetch back-end database queries or remote calls to other applications, and begin transferring the response back to NSX Advanced Load Balancer. This time is calculated by subtracting the Server RTT from the time of the first byte of a response from the server. If the application consists of multiple tiers (such as web, applications, and database), then the App Response represents the combined time before the server in the pool began responding. This metric is only available for a layer 7 virtual service.

Data Transfer

Represents the average time required for the server to transmit the requested file. This is calculated by measuring from the time the Service Engine received the first byte of the server response until the client has received the last byte, which is measured as the when the last byte was sent from the Service Engine plus one half of a client round trip time. This number may vary greatly depending on the size of objects requested and the latency of the server network. The larger the file, the more TCP round trip times are required due to ACKs, which are directly impacted by the client RTT and server RTT. This metric is only used for a Layer 7 virtual service.

Total Time

Total time from when a client sent a request until they receive the response. This is the most important end-to-end timing number to watch, because it is the sum of the other four metrics. As long as it is consistently low, the application is probably successfully serving traffic.

Pool Metrics

The sidebar metrics tiles contain the following metrics for the pool. Clicking any metric tile will change the main chart pane to show the chosen metric.

Field

Description

End to End Timing

Shows the total time from the pool’s End to End Timing graph. To see the complete end-to-end timing, including the client latency, refer to Analytics tab of the Virtual Service Details page, which includes the client to Service Engine metric.

Open Connections

The number of open (existing) connections during the selected time period.

New Connections

The number of client connections that were completed or closed over the selected time period. Refer to this article for an explanation of new versus closed connections per second.

Throughput

Total bandwidth passing between the virtual service and the servers assigned to the pool. This throughput number may be different than the virtual service throughput, which measures throughput between the client and the virtual service. Many features may affect these numbers between the client and server side of NSX Advanced Load Balancer, such as caching, compression, SSL, and TCP multiplexing. Hovering your mouse cursor over this graph displays the throughput in Mbps for the selected time period.

Requests

The number of HTTP requests sent to the servers assigned to the pool. This metric also shows errors sent to servers or returned by servers. Any client requests that received an error generated by NSX Advanced Load Balancer as a response (such as a 500 when no servers are available) are not be forwarded to the pool and will not be tracked in this view.

Servers

Displays the number of servers in the pool and their health. The X-axis represents the number of HTTP requests or connections to the server, while the Y-axis represents the health score of the server. The chart enables you to view servers in relation to their peers within the pool, thus helping to spot outliers. Within the chart pane, click and drag the mouse over server dots to select and display a table of the highlighted servers below the Chart pane. The table provides more details about these servers, such as hostname, IP address, health, new connections or requests, health score, and the server’s static load balanced ratio. Clicking on the name of a server will jump to the pool’s Server Insight page, which shows additional health and resource status.

Pool Chart Pane

The main chart pane in the middle of the Analytics tab displays a detailed historical chart of the selected metric tile for the current pool.

  • Hovering the mouse over any point in the chart will display the results for that selected time in a popup window.

  • Clicking within the chart will freeze the popup at that point in time. This may be useful when the chart is scrolling as the display updates over time.

  • Clicking again will unfreeze the highlighted point in time.



Many charts contain radio buttons in the top right that allow customization of data that should be included or excluded from the chart. For instance, if the End to End Timing chart is heavily skewed by one very large metric, then deselecting that metric by clearing the appropriate radio button will re-factor the chart based on the remaining metrics shown. This may change the value of the vertical Y-axis.

Some charts also contain overlay items, which will appear as color-coded icons along the bottom of the chart.

Pool Overlays Pane

The overlays pane is used to highlight important events within the timeline of the chart pane. This feature helps correlate anomalies, alerts, configuration changes, or system events with changes in traffic patterns.



Within the overlays pane:

  • Each overlay type displays the number of entries for the selected time period.

  • Clicking an overlay button toggles that overlay’s icons in the chart pane. The button lists the number of instances (if any) of that event type within the selected time period.

  • Selecting an overlay button displays the icon for the selected event type along the bottom of the chart pane. Multiple overlay icon types may overlap. Clicking the overlay type’s icon in the chart pane will bring up additional data below the overlay Items bar. The following overlay types are available:

    • Anomalies — Display anomalous traffic events, such as a spike in server response time, along with corresponding metrics collected during that time period.

    • Alerts — Display alerts, which are filtered system-level events that have been deemed important enough to notify an administrator.

    • Config Events — Display configuration events, which track configuration changes made to NSX Advanced Load Balancer by either an administrator or an automated process.

    • System Events — Display system events, which are raw data points or metrics of interest. System Events can be noisy, and are best used as the basis of alerts which filter and classify raw events by severity.

Pool Anomalies Overlay

The anomalies overlay displays periods during which traffic behavior was considered abnormal based on recent historical moving averages. Changing the time interval will provide greater granularity and potentially show more anomalies.

Clicking Anomalies Overlay button displays yellow anomaly icons in the chart pane. Selecting one of these icons within the chart pane brings up additional information in a table at the bottom of the page. During times of anomalous traffic, NSX Advanced Load Balancer records any metrics that have deviated from the norm, which may provide hints as to the root cause of the anomaly.

An anomaly is defined as a metric that has a deviation of 4 sigma or greater across the moving average of the chart.

Anomalies are not recorded or displayed while viewing with the real-time display period.

Pool Alerts Overlay

The alerts overlay displays the results of any events that meet the filtering criteria defined in the alerts tab. Alerts notify administrators about important information or changes to a site that may require immediate attention.

Alerts may be transitory, meaning that they may expire after a defined period of time. For instance, NSX Advanced Load Balancer may generate an alert if a server is down and then allow that alert to expire after a specified time period once the server comes back online. The original event remains available for later troubleshooting purposes.

Clicking the alerts icon in the overlay items bar displays any red alerts icons in the chart pane. Selecting one of these chart alerts will bring up additional information below the overlay Items bar, which will show the following information:



Field

Description

Timestamp

Date and time when the alert occurred.

Resource Name

Name of the object that is reporting the alert.

Level

Severity of the alert. You can use the priority level to determine whether additional notifications should occur, such as sending an email to administrators or sending a log to Syslog servers. The level may be one of the following:

  • High — Red

  • Medium — Yellow

  • Low — Blue

Summary

Brief description of the event.

Pool Config Events overlay

The config events overlay displays configuration events, such as changing the NSX Advanced Load Balancer configuration by adding, deleting, or modifying a pool, virtual service, or Service Engine, or an object related to the object being inspected. If traffic dropped off at precisely 10:00am, and at that time an administrator made a change to the virtual services security settings, there’s a good chance the cause of the change in traffic was due to the (mis)configuration.



Clicking Config Events icon in the Overlay Items bar displays any blue config event icons in the chart pane. Selecting one of these chart alerts will bring up additional information below the Overlay Items bar, which will show the following information:

Field

Description

Timestamp

Date and time when the configuration change occurred.

Resource Type

This event type will always be scoped to configuration event types.

Resource Name

Name of the object that has been modified.

Event Code

  • There are three event codes:

    • CONFIG_CREATE

    • CONFIG_UPDATE

    • CONFIG_DELETE

User

It displays the user.

Description

Brief description of the event.

Expand/Contract

Clicking the plus (+) or minus sign (-) for a configuration event either expands or contracts a sub-table showing more detail about the event. When expanded, this shows a difference comparison of the previous configuration versus the new configuration, as follows:

  • Additions to the configuration, such as adding a health monitor, will be highlighted in green in the new configuration.

  • Removing a setting will be highlighted in red in the previous configuration.

  • Changing an existing setting will be highlighted in yellow in both the previous and new configurations.

Pool System Events Overlay

This overlay displays system events relevant to the current object, such as a server changing status from up to down or the health score of a virtual service changing from 50 to 100.

Clicking the system events icon in the overlay items bar displays any purple system event icons in the Chart Pane. Select a system event icon in the chart pane to bring up more information below the overlay items bar.

Pool Logs Page

Client logs viewed from within a pool are identical to the logs shown within a virtual service, except they are filtered to only show log data specific to the pool. For instance, information such as End to End Timing is only shown from the Service Engine to the servers, rather than from the clients to the servers. Viewing logs within a pool may be useful when a virtual service is performing content switching across multiple pools. It is still possible within the virtual service logs page to add a filter for a specific pool, which would then provide complete End to End Timing for connections or requests sent to the specified pool.

For the complete descriptions of logs, refer to the VS logs page for more details.

Pool Health Page

The health tab presents a detailed breakdown of health score information for the pool.



The health score of a pool is comprised of the following scores:

Field

Description

Performance Score

Performance score (1-100) for the selected item. A score of 100 is ideal, meaning clients are not receiving errors and connections or requests are quickly returned.

Resources Score

Any score assessed because of resource availability issues is assigned a score, which is then subtracted from the performance score. A penalty score of 0 is ideal, meaning there are no obvious resource constraints on NSX Advanced Load Balancer or servers.

Anomaly Score

Any score assessed because of anomalous events is assigned a score, which is then subtracted from the performance score. An ideal score is 0, which means NSX Advanced Load Balancer has not seen recent anomalous traffic patterns that may imply future risk to the site.

Health Score

The final health score for the selected item equals the performance score minus the Resource and anomaly penalty scores

The sidebar tiles show the scores of each of the three subcomponents of the health score, plus the total score. To determine why a pool may have a low health score, select one of the first three tiles that are showing a sub-par score.

This will bring up additional sub-metrics which feed into the top-level metric/tile selected. Hover the mouse over a time period in the main chart to see the description of the score degradation. Some tiles may have additional information shown in the main chart section that requires scrolling down to view.

Pool Servers Page

Information for each server within a pool is available on the Server Details page. This page offers views into the correlation between server resources, application traffic, and response times.

Server Page

The Server Page may be accessed by clicking on the server’s name from either the Pool > Servers page or the Pool > Analytics Servers tile. When viewing the Server Details page, the server shown is within the context of the pool it was selected within. Rephrased, if the server (IP: Port) is a member of two or more pools, the stats and health monitors shown are only for the server within the context of the viewed pool.

Not all metrics within the Server Page are available in all environments. For instance, servers that are not virtualized or hooked into a hypervisor are not able to have their physical resources displayed.



The statistics can be changed or skewed by switching between Average Values, Peak Values, and Current Values. To see the highest CPU usage over the past day, change the time to 24 hours and the Value to Peak. This will show the highest stats recorded during the past day.

Field

Description

CPU Stats

The CPU Stats box shows the CPU usage for this server, the average during this time period across all servers in the pool, and the hypervisor host.

Memory Stats

The memory Stats box shows the Memory usage for this server, the average during this time period across all servers in the pool, and the hypervisor host.

Health Monitor

This table shows the name of any health monitors configured for the pool. The Status column shows the most current up or down health of the server. The Success column shows the percentage of health monitors that passed or failed during the display time frame. Clicking the plus will expand the table to show more info for a down server. Refer to Why a Server Can Be Marked Down for more details.

Main Panel

The large panel shows the highlighted metric, similar to the Virtual Service Details and Pool Details pages. Overlay Items shows anomalies, alerts, configuration events, and system events that are related to this server within the pool.

Pool Tile Bar

The pool in the top right bar shows the health of the pool. This can also be used to jump back up to the Pool Page. Under the pool name is a pull-down menu that enables quick access to jump to the other servers within the pool.

Metrics Tile Bar

The metrics options will vary depending on the hypervisor NSX Advanced Load Balancer is plugged into. For non-virtualized servers, the metrics are limited to non-resource metrics, such as end-to-end timing, throughput, open connections, new connections, and requests. Other metrics that may be shown include CPU, memory, and virtual disk throughput.

Pool Events Page

The events tab presents system-generated events over the time period selected for the pool. System events apply to the context in which you are viewing them. For instance, when viewing events for a pool, only events that are relevant to that pool are displayed.



The top of this tab displays the following items:

Field

Description

Search

The search field enables you to filter the events using whole words contained within the individual events.

Refresh

Clicking refresh updates the events displayed for the currently selected time.

Number

The total number of events being displayed. The date/time range of those events appears beneath the search field on the left.

Clear Selected

If filters have been added to the Search field, clicking the Clear Selected (X) icon on the right side of the search bar will remove those filters. Each active search filter will also contain an X that you can click to remove the specific filter.

Histogram

The histogram shows the number of events over the period of time selected. The X-axis is time, while the Y-axis is the number of events during that bar’s period of time.

  • Hovering the cursor over a Histogram bar displays the number of entries represented by that bar, or period of time.

  • Click and drag inside the histogram to refine the date/time period which further filters the events shown. When drilling in on the time in the histogram, zoom to the selected link appears above the histogram. This expands the drilled in time to expand to the width of the histogram and also changes the displaying pull-down menu to custom. To return to the previously selected time period, use the displaying pull-down menu.

The table at the bottom of the Events tab displays the events that matched the current time window and any potential filters. The following information appears for each event:

Field

Description

Timestamp

Date and time the event occurred. Highlighting a section of the histogram provides further filtering of events within a smaller time window.

Event Type

This may be one of the following:

  • System — System events are generated by NSX Advanced Load Balancer to indicate a potential issue or create an informational record, such as VS_Down.

  • Configuration — Configuration events track changes to the NSX Advanced Load Balancer configuration. These changes may be made by an administrator (through the CLI, API, or GUI), or by automated policies.

Resource Name

Name of the object related to the event, such as the pool, virtual service, Service Engine, or Controller.

Event Code

A short event definition, such as Config_Action or Server_Down.

Description

A complete event definition. For configuration events, the description will also show the username that made the change.

Expand/Contract

Clicking the plus (+) or minus sign (-) for an event log either expands or contracts that event log. Clicking the + and – icons in the table header expands and collapses all entries in this tab.

For configuration events, expanding the event displays a different comparison between the previous and new configurations.
  • New fields will appear highlighted in green in the new configuration

  • Removed fields will appear highlighted in red.

  • Changed fields will show highlighted in yellow

Pool Alerts Page

The alerts tab displays user-specified events for the selected time period. You can configure alert actions and proactive notifications via Syslog or email in the Notifications tab of the Administration page. Alerts act as filters that provide notification for prioritized events or combinations of events through various mechanisms. NSX Advanced Load Balancer includes a number of default alerts based on events deemed to be universally important.



The top of this tab shows the following items:

Field

Description

Search

The search field enables you to filter the alerts using whole words contained within the individual alerts.

Refresh

Clicking refresh updates the alerts displayed for the currently-selected time.

Number

The total number of alerts being displayed. The date/time range of those alerts appear beneath the search field on the left.

Dismiss

Select one or more alerts from the table below then click dismiss to remove the alert from the list.

Alerts are transitory, which means they will eventually and automatically expire. They intend to notify an administrator of an issue, rather than being the definitive record for issues. Alerts are based on events, and the parent event will still be in the Events record.

The table at the bottom of the Alerts tab displays the following alert details:

Field

Description

Timestamp

Date and time when the alert was triggered. Changing the time interval using the display pull-down menu may potentially show more alerts.

Resource Name

Name of the object that is the subject of the alert, such as a Server or virtual service.

Level

Severity level of the alert, which can be high, medium, or low. Specific notifications can be set up for the different levels of alerts via the Administration page’s Alerts Overlay.

Summary

Summarized description of the alert.