| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:qoe_analytics:description [2025/10/31 09:40] – [General description] elena.krasnobryzh | en:dpi:qoe_analytics:description [2025/11/25 16:03] (current) – elena.krasnobryzh |
|---|
| The analysis of this data allows the operator to identify problems in the quality of provided services, take timely corrective actions, and increase subscriber loyalty. | The analysis of this data allows the operator to identify problems in the quality of provided services, take timely corrective actions, and increase subscriber loyalty. |
| |
| {{ :dpi:qoe_analytics:qoe.png?nolink&600 |}} | {{ :en:dpi:qoe_analytics:qoe.svg?nolink&600 |}} |
| |
| Analysis can be performed in several ways: | Analysis can be performed in several ways: |
| - **In the SSG graphical interface — [[en:dpi:dpi_components:dpiui|DPIUI2]]**. You can monitor the [[en:dpi:qoe_analytics:qoe_gui:dashboard|dashboard]] (it is customizable), view predefined [[en:dpi:qoe_analytics:qoe_gui:reports:qoe_reports|TOPs]] for important [[en:dpi:qoe_analytics:qoe_gui:reports:paramdescript|metrics]], set any [[en:dpi:qoe_analytics:qoe_gui:reports:qoe_filters|filters]] and get on-demand custom exports, or export to Excel for detailed processing.\\ //Recommended for getting acquainted with the statistical capabilities and investigating “complex cases” when it’s necessary to trace unclear behavior in raw logs.// | - **In the SSG graphical interface — [[en:dpi:dpi_components:dpiui|DPIUI2]]**. You can monitor the [[en:dpi:qoe_analytics:qoe_gui:dashboard|dashboard]] (it is customizable), view predefined [[en:dpi:qoe_analytics:qoe_gui:reports:qoe_reports|TOPs]] for important [[en:dpi:qoe_analytics:qoe_gui:reports:paramdescript|metrics]], set any [[en:dpi:qoe_analytics:qoe_gui:reports:qoe_filters|filters]] and get on-demand custom exports, or export to Excel for detailed processing.\\ //Recommended for getting acquainted with the statistical capabilities and investigating “complex cases” when it’s necessary to trace unclear behavior in raw logs.// |
| - **Through notifications to a convenient channel.** They can be configured to [[en:dpi:qoe_analytics:qoe_gui:offline_analytics:triggers_and_notifications|trigger]] on certain events (for example, exceeding a specified RTT value) or as a periodic mailing of useful reports (for example, a list of subscribers visiting competitor websites over the past week).\\ //Recommended for informing line specialists who simply receive lists to work with according to established procedures.// | - **Through notifications to a convenient channel.** They can be configured to [[en:dpi:qoe_analytics:qoe_gui:offline_analytics:triggers_and_notifications|trigger]] on certain events (for example, exceeding a specified RTT value) or as a periodic mailing of useful reports (for example, a list of subscribers visiting competitor websites over the past week).\\ //Recommended for informing line specialists who simply receive lists to work with according to established procedures.// |
| - **Through exports of statistics to external databases**, one-time or periodic. This can be a custom information system or third-party GUI such as [[https://habr.com/ru/articles/881180/|Akvorado]]. It can be done through [[en:dpi:qoe_analytics:cases:queries_from_database|database queries]] or API. This method is most effectively used for aggregating different metrics and enriching them with billing and network monitoring data. It makes sense to first perform preliminary work via sections [[en:dpi:qoe_analytics:cases:queries_from_database:problematic_subscribers#long_term_inactivity|1]]–[[en:dpi:qoe_analytics:cases:queries_from_database:problematic_subscribers#interest_in_competitors|2]] to test hypotheses and refine export parameters, then configure scripts and continue working in external databases.\\ //Recommended for regular work with verified metrics, providing the greatest efficiency. Requires data processing and database administration skills.// | - **Through exports of statistics to external databases**, one-time or periodic. This can be a custom information system or third-party GUI such as [[https://habr.com/ru/articles/881180/|Akvorado]]. It can be done through [[en:dpi:qoe_analytics:cases:queries_from_database|database queries]] or API. This method is most effectively used for aggregating different metrics and enriching them with billing and network monitoring data. It makes sense to first perform preliminary work via sections [[en:dpi:qoe_analytics:cases:queries_from_database:problematic_subscribers#long-term_subscriber_inactivity|1]]–[[en:dpi:qoe_analytics:cases:queries_from_database:problematic_subscribers#interest_in_competitors|2]] to test hypotheses and refine export parameters, then configure scripts and continue working in external databases.\\ //Recommended for regular work with verified metrics, providing the greatest efficiency. Requires data processing and database administration skills.// |
| |
