Configuring Clickstream, Meta data, DNS export in IPFIX [Документация VAS Experts]

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
en:dpi:dpi_options:opt_li:li_ipfix [2025/10/01 07:03] – [ClickStream export Setup] elena.krasnobryzhen:dpi:dpi_options:opt_li:li_ipfix [2025/10/31 08:56] (current) elena.krasnobryzh
Line 8: Line 8:
 Any universal IPFIX collector that accepts templates or the __[[en:dpi:dpi_components:utilities:ipfixreceiver2|IPFIX Receiver]]__ utility is suitable for collecting information in IPFIX format. Any universal IPFIX collector that accepts templates or the __[[en:dpi:dpi_components:utilities:ipfixreceiver2|IPFIX Receiver]]__ utility is suitable for collecting information in IPFIX format.
  
-To receive, process and store ClickStream, we suggest using the __[[en:dpi:dpi_components:qoestor|QoE Store software]]__ and __[[en:dpi:dpi_components:dpiui|DPIUI2 graphical interface]]__.+To receive, process and store ClickStream, we suggest using the __[[en:dpi:qoe_analytics|QoE Store software]]__ and __[[en:dpi:dpi_components:dpiui|DPIUI2 graphical interface]]__.
  
 If the link quality between SSG and NetFlow/IPFIX collector is insufficient, SSG skips sending some statistics to save performance. A message is displayed in ''fastdpi_alert.log'' when a chunk of information is skipped: If the link quality between SSG and NetFlow/IPFIX collector is insufficient, SSG skips sending some statistics to save performance. A message is displayed in ''fastdpi_alert.log'' when a chunk of information is skipped: