<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.vasexperts.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.vasexperts.com/feed.php">
        <title>VAS Experts documentation dpi:qoe_analytics:implementation_administration:configuration_setup</title>
        <description></description>
        <link>https://wiki.vasexperts.com/</link>
        <image rdf:resource="https://wiki.vasexperts.com/lib/tpl/vaswiki/images/favicon.ico" />
       <dc:date>2026-04-28T15:18:14+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:db_user_and_password&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:disc&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:dpi&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:fullflow_compress&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:ipfix_receivers&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:nat_flow&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:sharding&amp;rev=1776855610&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:timezone&amp;rev=1776855610&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.vasexperts.com/lib/tpl/vaswiki/images/favicon.ico">
        <title>VAS Experts documentation</title>
        <link>https://wiki.vasexperts.com/</link>
        <url>https://wiki.vasexperts.com/lib/tpl/vaswiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:db_user_and_password&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Database user configuration</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:db_user_and_password&amp;rev=1776855610&amp;do=diff</link>
        <description>Database user configuration



By default, the ClickHouse database connection uses the user default with an empty password. 

If necessary, you can set a username and password.

To do this, on the server where QoE Stor is installed, in the file /etc/clickhouse-server/users.xml under the &lt;users&gt; section:</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:disc&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Disk space configuration</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:disc&amp;rev=1776855610&amp;do=diff</link>
        <description>Disk space configuration



QoE Stor uses several folders for data storage:

	*  /var/qoestor/backend/dump – stores temporary data received by receivers. After loading into the database, this data is deleted.
	*  /var/lib/clickhouse/ – the so-called DEFAULT disk. Stores the database schema and data (raw and aggregated logs).</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:dpi&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>IPFIX export configuration from SSG to QoE</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:dpi&amp;rev=1776855610&amp;do=diff</link>
        <description>IPFIX export configuration from SSG to QoE


Configuration in GUI
Export configuration

IPFIX export is configured in the fastdpi.conf file on the DPI.

Example of minimal recommended export settings:


netflow=8
netflow_dev=em1
netflow_timeout=10
netflow_full_collector_type=2
netflow_full_port_swap=0
netflow_full_collector=YOUR_QOESTOR_IP:1500
ipfix_dev=em1
ipfix_tcp_collectors=YOUR_QOESTOR_IP:1501</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:fullflow_compress&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Fullflow raw log compression</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:fullflow_compress&amp;rev=1776855610&amp;do=diff</link>
        <description>Fullflow raw log compression


Configuration in GUI
SSG sends session information in IPFIX in chunks. In this case, data for a single session may be split into multiple parts and stored in the database as several rows. This creates redundant storage load, especially when long-term raw log storage is required.</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:ipfix_receivers&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>IPFIX receiver configuration</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:ipfix_receivers&amp;rev=1776855610&amp;do=diff</link>
        <description>IPFIX receiver configuration


Configuration in GUI
IPFIX receivers accept statistics from DPI:

	*  Clickstream, Meta, DNS
	*  Full NetFlow
	*  GTP
	*  NAT

IPFIX receivers are configured through the .env file: /var/qoestor/backend/.env

A separate receiver is configured for each stream.

A standard configuration looks as follows:</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:nat_flow&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>NAT Flow configuration</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:nat_flow&amp;rev=1776855610&amp;do=diff</link>
        <description>NAT Flow configuration



There are three ways to generate a NAT log in QoE Stor (statistics server):


	*  Receive the NAT Flow as a separate stream from the SSG. To do this, configure export of translations to external collectors on the SSG device; 

	*  Receive NAT Flow from Netstream of third-party systems (not from</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:sharding&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sharding configuration and QoE cluster setup</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:sharding&amp;rev=1776855610&amp;do=diff</link>
        <description>Sharding configuration and QoE cluster setup



QoE Stor can operate in sharding mode — horizontal cluster scaling, where parts of a single database are distributed across different shards (nodes).

Sharding allows you to:

	*  Distribute the IPFIX insertion load from multiple</description>
    </item>
    <item rdf:about="https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:timezone&amp;rev=1776855610&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T11:00:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Date, time, and time zone configuration</title>
        <link>https://wiki.vasexperts.com/doku.php?id=dpi:qoe_analytics:implementation_administration:configuration_setup:timezone&amp;rev=1776855610&amp;do=diff</link>
        <description>Date, time, and time zone configuration



Before installing QoE Stor on the server, make sure that the correct date, time, and most importantly, the time zone are set!

You can check the current date, time, and time zone using the command 

timedatectl</description>
    </item>
</rdf:RDF>
