What does the Data Flow Panel on the right of the vService screen show?
Short answer
Data Flow Panel is the preview panel that stays open on the right in the Dashboard and Load Balancer Management tabs of the vService screen; it has no separate title in the interface, and its name is given in the documentation (Load Balancer - ADC Data Flow Panel). It draws the vService's configuration as a request flow diagram from the listener to the Backend Services: the vService type, listener addresses, virtual domain names, certificate and TLS security profile, actions, the enabled Bot/DDoS, WAF and AGS strips, cache, compression, algorithm, persistence, conditional routing and Backend Services (what the diagram describes). An element that is not defined is not drawn. The lines show not traffic volume but whether it is up. The panel header contains the vService's status dot (panel header); below it are the Details, Log and Status Logs tabs (panel tabs), and at the very bottom is an icon strip summarizing the log, report, notification and other profiles (bottom settings strip).
How Does It Work?
The panel reads the vService's live configuration and draws the diagram accordingly; the diagram is read as follows:
- Lines: The line going to a Backend Service is shown dashed and flowing if the service's health check is successful (or no health check is defined) and at least one listener address is up; otherwise it is shown solid (distribution and Backend Services).
- Boxes: When a box is clicked, a summary window opens; editing is done with Edit in this window, and Go to Page leads to the record's own page.
- Module strips: Bot/DDoS, WAF and AGS are shown in a fixed order and only if the module is enabled on the vService (module strips); the eye icon switches between the summary and detailed views.
- Faded icon: An element that appears faded in the bottom strip is not defined on that vService; for example, a faded Reports icon shows that no Reports profile is assigned (Why can't I see the Report tab?).
- Status dot: In a cluster, it 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. Listener rows and Backend Service boxes are also shown in a separate column per device (What does a status circle split in two mean in the vService list in a cluster?).
Sections of the Panel in TR7
| Section | What it shows |
|---|---|
| Header | The vService's combined status dot (two halves in a cluster), the tcpdump and Edit shortcuts (Edit only for a user with edit permission); Delete, Reload, Enable and Disable in the ⋮ menu |
| Diagram | Request flow: listeners → security modules → actions → routing and algorithm → Backend Services (LB diagram) |
| Details tab | Status messages and configuration errors |
| Log tab | The record of the operations performed on the vService: who made which change and when (How do I see the change history of a single vService or Backend Service?) |
| Status Logs tab | Status transitions and their reasons |
| Bottom icon strip | Logs, Reports and Notifications profiles, XFF, QOS, Timeouts and vService Limits; those not defined appear faded (bottom settings strip) |
Common Misconceptions
- "Line thickness is traffic volume." The lines show only whether something is up; for traffic, Dashboard and Live Stats are used.
- "The panel is open in every tab." The panel is visible only in the Dashboard and Load Balancer Management tabs; it has no close button and is collapsed with the handle outside its left side.
- "A feature not visible in the diagram is off." Elements that are not defined are not drawn at all; profiles are also checked in the bottom icon strip.
How it is done in the documentation
