QoE Dashboard [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

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

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    en:dpi:qoe_analytics:qoe_gui:dashboard [2025/11/01 09:46] – elena.krasnobryzhen:dpi:qoe_analytics:qoe_gui:dashboard [2025/12/09 13:14] (current) – elena.krasnobryzh
    Line 25: Line 25:
     ===== Custom dashboards ===== ===== Custom dashboards =====
     You can create custom dashboards and fill them with any widgets: 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:   - Fill in information about the new dashboard:
         - Enter a name       - 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”     - Click “Save”  
       - Expand the “Widgets, drag from here” panel, choose widgets you want to include, and drag them to the dashboard.   - 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.\\ You can resize widgets by dragging their bottom-right corner.\\
    Line 124: Line 124:
      
     == RTT from subscriber to DPI == == RTT from subscriber to DPI ==
    -{{ :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) == == RTT to subscriber — from server to DPI (if termination was initiated by the client) ==
    -{{ :dpi:qoe:use_cases:rtt_to.jpg?1000 |}}+{{ :dpi:qoe_analytics:qoe_gui:dashboard:rtt_to.jpg?1000 |}}
      
     == TCP protocol features and RTT calculation == == TCP protocol features and RTT calculation ==
    Line 134: Line 134:
      
     == RTT from client to DPI equals zero for some flows == == RTT from client to DPI equals zero for some flows ==
    -{{ :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. 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.   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) == == Some flows have very high RTT values (tens of seconds) ==
    -{{ :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. 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.