{{indexmenu_n>14}}
======Statistics======
=====stat flow ip4=====
Displays IPv4 flow statistics. Analogous to the output in ''fastdpi_stat.log''.
<code bash>fastdpi_cli stat flow ip4</code>

=====stat flow ip6=====
Displays IPv6 flow statistics
<code bash>fastdpi_cli stat flow ip6</code>

=====stat netflow=====
Displays general Netflow/IPFIX statistics (same as what is output in ''fastdpi_stat.log'' in the "Statistics on NFLW_export" section)
<code bash>fastdpi_cli stat netflow</code>

=====stat firewall=====
Displays general firewall statistics
<code bash>fastdpi_cli stat firewall</code>

===== stat http =====
Displays internal statistics on HTTP, SSL_SAVEBL, QUIC_IETF_SAVEBL, BitTorrent. Equivalent to the output in ''fastdpi_stat.log''.
<code bash>fdpi_cli stat http</code>

The command output also shows memory usage by HTTP parsers — this data can be used to monitor HTTP parser utilization.

For each thread (''slave #N'') and in total for all threads (''Total''), the ''http parser'' line is displayed (equivalent to ''MEMUSE : 'http parser''' in ''fastdpi_stat.log''):
<code>
Detailed statistics on HTTP
  slave #0
    http parser: total_recs=1000, cntr_allocated=1, free_recs=999
    ...
  Total
    http parser: total_recs=4000, cntr_allocated=4, free_recs=3996
    ...
</code>
where:
  * ''total_recs'' — number of HTTP parsers allocated to the thread;
  * ''cntr_allocated'' — number of parsers in use;
  * ''free_recs'' — number of free parsers.

Statistics for the shared HTTP parser memory pool are also displayed (equivalent to ''MEMUSE : 'http parser' mem_manager'' in ''fastdpi_stat.log''):
<code>
http parser mem_manager:
  sizeof_T=6744 size_rec_insizet=843 recs_per_block=1000
  total_block=80, used_blocks=4, free_blocks=76 ( 95.00% )
  total_recs=80000, used_recs=4000, free_recs=76000
</code>
where:
  * ''recs_per_block'' — number of parsers in one memory block;
  * ''total_block'', ''used_blocks'', ''free_blocks'' — total number of blocks, number of blocks allocated to threads, and number of free blocks (the percentage of free blocks is shown in parentheses);
  * ''total_recs'', ''used_recs'', ''free_recs'' — total number of parsers in the pool, number of parsers allocated to threads, and number of free parsers.

HTTP parser utilization is calculated as follows:
  * per thread — ''cntr_allocated / total_recs × 100%'' (from the thread's ''http parser'' line);
  * overall — ''used_recs / total_recs × 100%'' (from the ''http parser mem_manager'' block).