How to Interpret the TR7 vService Flow Diagram?
About
What Is Flow Diagram?
TR7's Dynamic Flow Technology provides a logical flow diagram on a single screen that details the configurations made on vServices, allowing users to monitor real-time changes easily. This patented feature of TR7 enhances the usability and clarity of the TR7 Load Balancer and Web Application Firewall devices.
With the Dynamic Flow Panel, users can simultaneously track changes made to vServices, including vService Status, IP Status, Backend Service Status, Added Conditions/Actions, SSL Certificate Information, and Used Profiles.
In addition to ease of use, the Dynamic Flow Panel also provides information on the flow of traffic to the vServices, including which modules are handling it and in what order. Its modern interface and graphics significantly improve usability and manageability.
Interface
Flow Diagram
How to Interpret a Flow Diagram?
When clicking on a desired vService, the top of the Dynamic Flow Panel displays the service type and an icon indicating whether Debug Mode is active.
You will see that traffic is handled by the IP address 135.181.188.109, requests coming to port 80 are automatically redirected to port 443, and SSL termination is performed on TR7, as indicated by the SSL visual.
Traffic is limited by the defined Bandwidth Limiting to 50 Mbps, and requests that do not hit the limit will undergo checks from the L7 DDoS profile.
Details of the certificate used for SSL termination can be reviewed through the Dynamic Flow Panel.
Next, you will see the information about the Request Actions defined on the vService. Actions/Conditions created on TR7 can be divided into two categories: those that execute upon the request and those that execute upon the response. Information about response actions can also be viewed on this screen. Incoming requests are processed through the Request Actions before being subject to the checks of the TR7 WAF module. Here, you can check what protection mode the WAF is in, and you can click on the WAF text to access the WAF configuration screen for the relevant vService.
Requests that do not trigger WAF checks are processed through the defined "Cache" and "Compression" profiles before being sent to the Backend Services. Details of the relevant profiles can also be viewed.
Then, based on the selected distribution algorithm and persistence value, requests are sent to the Backend Services. In vServices with Conditional Backend Services, the system first checks whether incoming requests meet the relevant conditions before sending them to the selected Backend Services by default.
You can also view details about profiles defined on the vService, such as Logs, Reports, and Notifications.
