Differences

This shows you the differences between two versions of the page.

--- en:dpi:qoe_analytics:qoe_gui:dashboard [2025/11/01 09:42] – elena.krasnobryzh
+++ en:dpi:qoe_analytics:qoe_gui:dashboard [2025/12/09 13:14] (current) – elena.krasnobryzh
@@ Line 25: / Line 25: @@
 ===== Custom dashboards =====
 You can create custom dashboards and fill them with any widgets:
-  - Click “+” (Add dashboard) on the “Dashboards” panel on the right side of the screen\\ {{:en:dpi:qoe_analytics:qoe_gui:new_dashboard.png?nolink&400|}}
+  - Click “+” (Add dashboard) on the “Dashboards” panel on the right side of the screen\\ {{:en:dpi:qoe_analytics:qoe_gui:dashboard:new_dashboard.png?nolink&400|}}
   - Fill in information about the new dashboard:
     - Enter a name
-    - Configure access. If “For users with roles” is selected, you can mark which roles will have access to this dashboard\\ {{:en:dpi:qoe_analytics:qoe_gui:dashboard_settings.png?nolink&400|}}
+    - Configure access. If “For users with roles” is selected, you can mark which roles will have access to this dashboard\\ {{:en:dpi:qoe_analytics:qoe_gui:dashboard:dashboard_settings.png?nolink&400|}}
   - Click “Save”
   - Expand the “Widgets, drag from here” panel, choose widgets you want to include, and drag them to the dashboard.
-{{:en:dpi:qoe_analytics:qoe_gui:dashboard_content.png?nolink&1100|}}
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:dashboard_content.png?nolink&1100|}}
 You can resize widgets by dragging their bottom-right corner.\\
@@ Line 58: / Line 58: @@
   - Set //UPLINK LOAD RATE statistics collection// to //Enabled//
 Then click //Save// at the top of the screen.\\
-{{:en:dpi:qoe:use_cases:uplink_settings.png?1100 |}}
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:uplink_settings.png?1100 |}}
 === Appearance ===
@@ Line 65: / Line 65: @@
 Each widget can be configured (1) or deleted (2) from the side panel.\\
-{{:en:dpi:qoe:use_cases:widget_panel.png?300|}}\\
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_panel.png?300|}}\\
 In the widget settings window (1), you can rename the widget in English and Russian (3) and configure its visibility (4).\\
-{{:en:dpi:qoe:use_cases:widget_setup_1.png?300|}}\\
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_setup_1.png?300|}}\\
 At the top of the screen, you can select the time period for displaying traffic (5) and choose the data source (6).\\
-{{:en:dpi:qoe:use_cases:widget_setup_2.png?600|}}\\
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_setup_2.png?600|}}\\
 For each protocol, the following data is displayed:
@@ Line 80: / Line 80: @@
     - 4–7 points — satisfactory (yellow curve)
     - 8–10 points — poor (red curve)
-  * **Curve** showing changes in the health score over time (12)\\ {{:en:dpi:qoe:use_cases:widget_estimate.png?350|}}
+  * **Curve** showing changes in the health score over time (12)\\ {{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_estimate.png?350|}}
 === Configuring protocols in the widget ===
 When hovering over a widget, a ☰ icon appears in the top right corner. Clicking it allows you to access settings or delete the widget.
-{{:en:dpi:qoe:use_cases:widget_protocols_setup.png?200|}}
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_protocols_setup.png?200|}}
 Clicking //Settings// opens the configuration form.
@@ Line 100: / Line 100: @@
 Recommended default values for the impact of traffic delta (%) and RTT thresholds are provided by the developer, then adjusted by the operator as needed.
-{{:en:dpi:qoe:use_cases:widget_setup_form.png?400|}}
+{{:en:dpi:qoe_analytics:qoe_gui:dashboard:widget_setup_form.png?400|}}
 === What to do in case of issues ===
@@ Line 124: / Line 124: @@
 == RTT from subscriber to DPI ==
-{{ :en:dpi:dpi_components:dpiui:rtt_from.jpg?1000 |}}
+{{ :dpi:qoe_analytics:qoe_gui:dashboard:rtt_from.jpg?1000 |}}
 == RTT to subscriber — from server to DPI (if termination was initiated by the client) ==
-{{ :en:dpi:qoe:use_cases:rtt_to.jpg?1000 |}}
+{{ :dpi:qoe_analytics:qoe_gui:dashboard:rtt_to.jpg?1000 |}}
 == TCP protocol features and RTT calculation ==
@@ Line 134: / Line 134: @@
 == RTT from client to DPI equals zero for some flows ==
-{{ :en:dpi:dpi_components:dpiui:rtt_no_ack.jpg?1000 |}}
+{{ :dpi:qoe_analytics:qoe_gui:dashboard:rtt_no_ack.jpg?1000 |}}
 This happens if DPI does not receive an ACK from the client for a sent SYN/ACK.
 It may occur if the client closed the connection physically or sent a RST packet.
@@ Line 140: / Line 140: @@
 == Some flows have very high RTT values (tens of seconds) ==
-{{ :en:dpi:dpi_components:dpiui:rtt_zero.jpg?1000 |}}
+{{ :dpi:qoe_analytics:qoe_gui:dashboard:rtt_zero.jpg?1000 |}}
 For example, this may occur during a TCP HALF CLOSED CONNECTION, when one side stops sending but still receives data. The transmitting side may send FIN/ACK only after finishing all data transfer, leading to a high RTT value.
@@ Line 148: / Line 148: @@
   - Retransmissions from subscriber traffic
   - Retransmissions to subscriber traffic
-{{ :en:dpi:dpi_components:dpiui:tcp-retransmission.jpg?900 |}}
+{{ :en:dpi:qoe_analytics:qoe_gui:dashboard:tcp-retransmission.jpg?900 |}}
 Retransmission types:
   * **TCP Retransmission** — standard packet retransmission. If the sender does not receive an ACK within the retransmission timer, it resends the packet, assuming it was lost. The timer adapts dynamically to the network’s RTT, as defined in RFC6298 *Computing TCP’s Retransmission Timer*.