From: Russ Combs (rucombs) <rucombs@cisco.com>
Date: Thu, 10 Nov 2016 19:06:48 +0000 (-0500)
Subject: Merge pull request #698 in SNORT/snort3 from perfmon_docs to master
X-Git-Tag: 3.0.0-233~195
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=45ea1e9fd409bb797024a9a5bf4eefadc237877b;p=thirdparty%2Fsnort3.git

Merge pull request #698 in SNORT/snort3 from perfmon_docs to master

Squashed commit of the following:

commit b8807c17407e8b6b1d65a1ed8d00635eade1f966
Author: Carter Waxman <cwaxman@cisco.com>
Date:   Mon Nov 7 10:09:57 2016 -0500

    added perfmon docs
---

diff --git a/doc/manual/perf_monitor.txt b/doc/manual/perf_monitor.txt
new file mode 100644
index 000000000..2d68731d9
--- /dev/null
+++ b/doc/manual/perf_monitor.txt
@@ -0,0 +1,93 @@
+=== Overview
+
+The new and improved performance monitor! Is your sensor being bogged down by
+too many flows? perf_monitor! Why are certain TCP segments being dropped without
+hitting a rule? perf_monitor! Why is a sensor leaking water? Not perf_monitor, check
+with stream…
+
+The Snort performance monitor is the built-in utility for monitoring system
+and traffic statistics. All statistics are separated by processing thread.
+perf_monitor supports several trackers for monitoring such data:
+
+=== Base Tracker
+
+The base tracker is used to gather running statistics about Snort and its
+running modules. All Snort modules gather, at the very least, counters for the
+number of packets reaching it. Most supplement these counts with those for
+domain specific functions, such as http_inspect’s number of GET requests seen.
+
+Statistics are gathered live and can be reported at regular intervals. The stats
+reported correspond only to the interval in question and are reset at the
+beginning of each interval.
+
+These are the same counts displayed when Snort shuts down, only sorted amongst
+the discrete intervals in which they occurred.
+
+Base differs from prior implementations in Snort in that all stats gathered are
+only raw counts, allowing the data to be evaluated as needed. Additionally,
+base is entirely pluggable. Data from new Snort plugins can be added to the
+existing stats either automatically or, if specified, by name and function.
+
+All plugins and counters can be enabled or disabled individually, allowing for
+only the data that is actually desired instead of overly verbose performance
+logs.
+
+To enable everything:
+
+    perf_monitor = { modules = {} }
+
+To enable everything within a module:
+
+    perf_monitor =
+    {
+        modules = 
+        {
+            {   
+                name = 'stream_tcp',
+                pegs = [[ ]]
+            },
+        }
+    }
+
+To enable specific counts within modules:
+
+    perf_monitor =
+    {
+        modules = 
+        {
+            {   
+                name = 'stream_tcp',
+                pegs = [[ overlaps gaps ]]
+            },
+        }
+
+Note: Event stats from prior Snorts are now located within base statistics.
+
+=== Flow Tracker
+
+Flow tracks statistics regarding traffic and L3/L4 protocol distributions. This
+data can be used to build a profile of traffic for inspector tuning and for
+identifying where Snort may be stressed.
+
+To enable:
+
+    perf_monitor = { flow = true }
+
+=== FlowIP Tracker
+
+FlowIP provides statistics for individual hosts within a network. This data can
+be used for identifying communication habits, such as generating large or small
+amounts of data, opening a small or large number of sessions, and tendency to
+send smaller or larger IP packets.
+
+To enable:
+
+    perf_monitor = { flow_ip = true }
+
+=== CPU Tracker
+
+This tracker monitors the CPU and wall time spent by a given processing thread.
+
+To enable:
+
+    perf_monitor = { cpu = true }
diff --git a/doc/snort_manual.txt b/doc/snort_manual.txt
index 5297b0112..40b4a82d5 100644
--- a/doc/snort_manual.txt
+++ b/doc/snort_manual.txt
@@ -72,6 +72,10 @@ have associated modules.
 
 include::manual/file_processing.txt[]
 
+== Performance Monitor
+
+include::manual/perf_monitor.txt[]
+
 == Logger Modules
 
 All output of events and packets is done by Loggers.