Can I see which connections are currently open (vService Sessions)?

Short answer

Yes. When vService Sessions is selected as the source in the Logs & Tracking tab of the vService screen, an instant list of the open connections on the vService is shown. Each row is a connection; the route table, connection state (TCP state), source and destination address and port, the Backend Service in L7 TCP, and the client and remaining time in Network are shown (listing screen). The list is not refreshed automatically; Refresh is used for an up-to-date view. It does not require a log profile and works in every vService type; the user must have Load Balancer permission and the vService must be running.

Problem: Open Connections Cannot Be Seen

The aim is to see instantly whether a client is still connected, in which state the connections are waiting, or, in an L7 TCP vService, to which Backend Service they go. Logs show completed requests; a separate list is needed for the connections open at that moment.

Solution

Open connections are listed from a single place, the vService sessions source of the Logs & Tracking tab.

Logs & Tracking → vService Sessions

• How it works When the list is opened, it fetches the open connections of the vService; each row is a connection.
• Where it is opened vService → Logs & Tracking → vService Sessions
• Requirement Load Balancer permission for the user (this source is not visible with WAF permission alone); a running vService
• vService type All vService types

Step-by-Step Configuration

1

Adım 1 Open the vService screen

In the Left Monitor Panel, Load Balancer vServices is selected from the category selector and the vService is clicked (accessing the screen).

2

Adım 2 Open the Logs & Tracking tab

The Logs & Tracking tab is clicked (access).

3

Adım 3 Select the vService sessions source

vService Sessions is selected from the source selector at the start of the toolbar. The columns vary according to the vService type: in L7 TCP, the name, address and port of the Backend Service are shown; in Network, the client address, port and remaining time (Expires In) are shown; in a Network vService whose protocol is ANY or that uses a port range, the columns are Protocol, SNAT IP, Source IP, Destination IP and Status Code. In a cluster, the connections of the two devices are listed together; the Source column, hidden by default, shows which device the row comes from.

4

Adım 4 Filter

Route Table, Status Code, Source IP or Destination IP (in Network, also Client IP) is selected from the filter strip. Status Code is not the HTTP response code but the TCP connection state (e.g. TCP_ESTABLISHED).

5

Adım 5 Refresh

Refresh is clicked for an up-to-date view.

Verification

1ListTR7 side

The record count below the table is checked; a connection is opened from a known client and Refresh is clicked.

ExpectedThe client's connection appears as a TCP_ESTABLISHED row

Common Mistakes

• Assuming the list flows live. The list is fetched once when it opens; Refresh is needed.
• Assuming the status code is an HTTP response code. This column shows the TCP connection state.
• Reading the address columns in a Network vService as in HTTP. In a Network vService, Source IP is the virtual service address and Destination IP is the real server.
• Assuming an empty list on a stopped vService means there is no traffic. If the vService is stopped, the list is not fetched.
• Trying to cut a connection from the list. vService sessions is only for monitoring; there is no connection termination operation in the list.

How it is done in the documentation

• vService Sessions · Accessing vService Sessions
• vService Sessions · vService Sessions Listing Screen
• vService Sessions · Status Code

Related questions

• What does the Live Stats screen show?
• How do I find the requests of a specific client IP in the logs?
• What is the difference between HTTP logs and TCP logs?