FAQ
Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform

English

Türkçe

English

Türkçe

Appearance

Basic

Where do I monitor the current status of my vService? ​

Short answer

The status of all vServices is read from the colored strip on the left of the row in the Left Monitor Panel's Load Balancer vServices list (OK, Warning, Error, Disabled, Evaluating, Unknown) (status strip). On the screen that opens when the vService is clicked, the status dot in the header of the panel on the right and the Details tab show the reason for the status, and the Live Stats tab shows live counters refreshed every second by default. The Dashboard, in turn, gives the same metrics spread over time. In WEB-CLI, the lb service status commands list the status, CPU, memory, throughput and uptime.

Problem: The Current Status of the vService Is Unknown ​

When a user reports being unable to reach the service, or after a change, there is a need to see quickly whether the vService is working, whether the Backend Services are healthy and what the current load is.

Solution: Four Methods ​

The methods are not alternatives to each other; the list shows the overall status, the right panel the reason for the status, and Live Stats the current load.

Your situationSuitable method
All vServices at a glanceMethod 1: Left Monitor Panel
The reason for the status and its historyMethod 2: vService screen → right panel
Per-second live countersMethod 3: Live Stats
From the command lineMethod 4: WEB-CLI
  • How it works In the list, each vService's row is shown with its status color and the selected metric; the status strip above the list gives the number of vServices per status.
  • Where it is opened Left Monitor Panel → Load Balancer vServices
  • Requirement Load Balancer or WAF permission; a user with only the WAF permission sees the HTTP vServices with WAF protection enabled
  • vService type All vService types

Step-by-Step Configuration ​

1
Adım 1 Open the list

In the Left Monitor Panel, Load Balancer vServices is selected in the category selector. The colored strip on the left of the row shows the status of the vService; the status name appears when the pointer is over it. The list is refreshed every 5 seconds by default (Refresh Interval).

2
Adım 2 Filter by status

A status (e.g. Error) is clicked in the status strip above the list; the list shows only the vServices in that status. When the same box is clicked again, the filter is removed.

Verification ​

1StatusTR7 side

The pointer is moved over the strip on the left of the row.

ExpectedOK
The strip of a vService that is running and receiving traffic is green.

Method 2: vService Screen → Right Panel ​

  • How it works The panel on the right of the vService screen shows the combined status of the vService in its header, the status messages and configuration errors in the Details tab, and the status transitions with their reasons in the Status Logs tab.
  • Where it is opened vService → Dashboard or Load Balancer Management tab → right panel
  • Requirement Load Balancer or WAF permission
  • 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 in the category selector and the vService is clicked (accessing the screen). The screen opens with the Dashboard tab; the right panel appears only in the Dashboard and Load Balancer Management tabs.

2
Adım 2 Look at the status dot in the header

The colored dot in the panel header shows the combined status of the vService: green OK, red Error, yellow (amber) Warning, the theme's accent color (blue in the default theme) Evaluating, gray Disabled (turned off manually or the license has stopped the traffic) (panel header). In a cluster, the dot is split into two halves; the left half is the status of the device logged in to, and the right half is the status of the peer device (What does a status circle split in two mean in the vService list in a cluster?).

3
Adım 3 Review the Details tab

In the Details tab of the panel, the status messages and configuration errors are listed per device (panel tabs).

4
Adım 4 Open the Status Logs tab

The Status Logs tab is clicked; the status transitions of the vService are listed with their reasons.

Verification ​

1DetailsTR7 side

The status messages in the Details tab are read.

ExpectedThe reason for the status (e.g. an unhealthy Backend Service)

Method 3: Live Stats ​

  • How it works The live counters are refreshed every second by default; the data is not stored. A live stream lasts about 30 minutes.
  • Where it is opened vService → Live Stats
  • Requirement A running vService
  • vService type All vService types (in a Network vService, the refresh interval is at least 5 seconds)

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 Live Stats

The Live Stats tab is clicked; the Frontend cards, the Backend Services table and (except in a Network vService) the Live Traffic section are monitored. Details: What does the Live Stats screen show?

Verification ​

1Live dataTR7 side

The LIVE indicator on the screen is checked.

ExpectedThe indicator pulses, the counters change

Method 4: WEB-CLI ​

  • How it works The status commands list the Status, CPU, Memory usage, Memory limit, Throughput and Uptime values of all vServices or of a single vService.
  • Where it is opened TR7 WEB-CLI → lb service status
  • Requirement WEB-CLI access
  • vService type All vService types

Step-by-Step Configuration ​

1
Adım 1 List all vServices

The status of all vServices is listed (restart and status):

text
lb service status list
2
Adım 2 Query a single vService

The status of a single vService is queried; the vService is given directly as a value, without writing the field name:

text
lb service status id <vService>

Verification ​

1OutputTR7 side

The Status column in the command output is checked.

ExpectedvService status, CPU, Memory usage, Throughput, Uptime

Common Mistakes ​

  • Assuming the Dashboard is real-time. The Dashboard shows the recorded data of the last 1 day by default; the real-time view is in Live Stats.
  • Leaving Live Stats open for a long time and assuming the values are current. The live stream stops by itself after about 30 minutes; it is restarted by turning LIVE off and on, or by refreshing the page.
  • Looking at a single color in a cluster. The status dot in the right panel is split into two halves for the two devices; the problem may be on only one device (What does a status circle split in two mean in the vService list in a cluster?).
  • Assuming the vService was deleted when it cannot be seen in the list. A user with only the WAF permission sees only the HTTP vServices with WAF protection enabled in the Load Balancer vServices list.

How it is done in the documentation

Related questions