{{indexmenu_n>4}} ====== "Online Reports" module ====== ===== Purpose ===== The Online Reports module allows real-time monitoring of a subscriber’s current traffic state to assess connection quality based on multiple metrics, as well as monitoring the network state for DPI configuration debugging during initial setup or changes. More details on usage cases can be found [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#usage_cases|here]]. The structure of online reports is the same as in the “NetFlow” section, but with some differences: - Monitoring is performed for only one subscriber or one host. - The aggregation interval can be as low as 5 seconds (instead of 15 minutes in NetFlow), which provides near real-time visualization. ===== Quick start ===== - Go to “QoE Analytics” → “Online Reports”. - Set the “Aggregation period” value.\\ We recommend setting it close to the ''netflow_timeout'' on the [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#step_1_on_the_sender_side_dpi|sender side]]. **If aggregation periods shorter than 10 minutes are unavailable, configure QoE according to the [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#data_collection_and_aggregation_setup|setup instructions]].** - Configure flow capture. On the “Filters” dashboard, click the “magic wand” icon and select the required flow capture type. Enter the subscriber’s login/IP or the host/IP of the monitored target. **Subscriber flow capture** — reports by subscriber (speed, protocols, RTT, clickstream, etc.).\\ **Host flow capture** — analysis of traffic to a specific host. {{:dpi:qoe:use_cases:start.png?nolink&600|}} Data collection starts immediately, and over time the graph fills with more data. To control data collection, use the “Start data collection” and “Stop data collection” buttons in the upper-left corner of the “Reports” dashboard: {{:dpi:qoe:use_cases:startstop.png?nolink&200|}} In the “Full raw log” field (below the graph), you can view which flows are currently active for the selected subscriber or host protocol.\\ Various reports are available for the selected subscriber or host, listed on the left side of the window. These are the same as in the regular “NetFlow” section but display live data. {{:dpi:qoe:use_cases:reports_list.png?nolink&400|}} Example of the “Traffic by application protocols” report for a subscriber: {{:dpi:qoe:use_cases:subscriber_reports.png?nolink&1200|}} Example of the “Traffic by application protocols” report for a host: {{:dpi:qoe:use_cases:host_reports.png?nolink&1200|}} ===== Description of additional report settings ===== * Settings menu: * Aggregation period — frequency of data updates. * Window width — defines the “length” of the graph (number of data points). You can set a value from 1 to 30. * Device — select the DPI to monitor.\\ In the settings menu, you can choose the device for which to view the report.\\ {{:dpi:qoe:use_cases:device_selection.png?nolink&300|}}\\ **Current DPI device — the device currently selected in the “DPI Management” section.** * Settings.\\ Allows adjusting the report update frequency (how often the graph refreshes and new rows appear).\\ {{:dpi:qoe:use_cases:restart_rate.png?nolink&400|}} * Refresh. * Cache clearing.\\ Cache — all data used to form the graph. It can be cleared to restart the graph from scratch. The cache automatically clears every hour.\\ {{:dpi:qoe:use_cases:cache.png?nolink&400|}} * “Filters” dashboard — shows monitored subscribers/hosts. You can add, edit, or delete them.\\ {{:dpi:qoe:use_cases:filters.png?nolink&400|}} * Protocol list — displays current subscriber/host protocols. The color of each protocol matches its line color on the graph. * Traffic variation chart — displays protocol traffic graphically. The vertical axis shows traffic volume; the horizontal axis shows time. * Full raw log — displays full information about the subscriber/host. ===== Data collection and aggregation setup ===== ==== Step 1. On the sender side (DPI) ==== - Go to “DPI Management” → “Configuration”. - In the “Groups” configuration, open “Statistics collection and analysis by protocols and directions”. - In the “Parameters” configuration, change the “Data export interval in seconds (''netflow_timeout'')” value. **This value must be less than or equal to the rotation interval [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#step_2_on_the_receiver_side_qoe|on the receiver side]].**\\ {{:dpi:qoe:use_cases:export_settings.png?nolink&1200|}} - Save the configuration. Select “Save without validation”.\\ {{:dpi:qoe:use_cases:saving1.png?nolink&300|}} - Restart the configuration. **Traffic interruption will occur!**\\ {{:dpi:qoe:use_cases:restart1.png?nolink&500|}} ==== Step 2. On the receiver side (QoE) ==== - Go to “Administrator” → “QoE Stor Configuration”. - In “Settings”, select “Receivers”. - In the “Receivers” configuration, click the “pencil” icon (edit) and set each NetFlow receiver’s rotation period in minutes or seconds (the database load interval). **We recommend setting one minute in the “Rotation in minutes” field. These values must be greater than or equal to the ''netflow_timeout'' [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#step_1_on_the_sender_side_dpi|on the sender side]]!**\\ {{:dpi:qoe:use_cases:сonfiguration_qoe.png?nolink&1200|}}\\ There are no strict limits on the rotation interval. **Settings can be made in either minutes or seconds. Using both fields simultaneously is not allowed.**\\ {{:dpi:qoe:use_cases:receiver_settings.png?nolink&700|}}\\ **It is important to assign identical values to all NetFlow receivers!** - Save and restart the configuration.\\ {{:dpi:qoe:use_cases:saving2.png?nolink&300|}}\\ {{:dpi:qoe:use_cases:restart2.png?nolink&600|}} After applying these settings, the database load will increase, and the graphical interface may run slower than usual. After completing all setup steps, you can [[dpi:qoe_analytics:qoe_gui:reports:online_reports_module#quick_start|generate online reports]]. ===== Usage cases ===== - [[dpi:qoe_analytics:cases:subscriber_analytics:realtime_subscriber_traffic_analysis]] - [[dpi:qoe_analytics:cases:network_health:dpi_conf]]