doc/napatech: formatting fixes

pull/2925/head
Victor Julien 8 years ago
parent e7428b321d
commit 456af8faa8

@ -209,19 +209,20 @@ Now you are ready to start Suricata::
$ suricata -c /usr/local/etc/suricata/suricata.yaml --napatech --runmode workers $ suricata -c /usr/local/etc/suricata/suricata.yaml --napatech --runmode workers
------------------------------------
Counters Counters
--------
For each stream that is being processed the following counters will be output in stats.log: For each stream that is being processed the following counters will be output in stats.log:
nt<streamid>.pkts - The number of packets recieved by the stream.
nt<streamid>.bytes - The total bytes received by the stream. - nt<streamid>.pkts - The number of packets recieved by the stream.
nt<streamid>.drop - The number of packets that were dropped from this stream due to
buffer overflow conditions. - nt<streamid>.bytes - The total bytes received by the stream.
- nt<streamid>.drop - The number of packets that were dropped from this stream due to buffer overflow conditions.
If hba is enabled the following counter will also be provided: If hba is enabled the following counter will also be provided:
nt<streamid>.hba_drop - the number of packets dropped because the host buffer allowance
high-water mark was reached. - nt<streamid>.hba_drop - the number of packets dropped because the host buffer allowance high-water mark was reached.
In addition to counters host buffer utilization is tracked and logged. This is also useful for In addition to counters host buffer utilization is tracked and logged. This is also useful for
debugging. Log messages are output for both Host and On-Board buffers when reach 25, 50, 75 debugging. Log messages are output for both Host and On-Board buffers when reach 25, 50, 75

Loading…
Cancel
Save