diff options
| author | Christian Poessinger <christian@poessinger.com> | 2019-11-06 07:23:20 +0100 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2019-11-06 07:23:20 +0100 |
| commit | 4e7fa1b0b8b0e86d7b8483ab3440f3ed14130ba8 (patch) | |
| tree | ec8fa60946c6c4d35e773563619e3460d98e39d1 /docs/system/flowaccounting.rst | |
| parent | ce09e37e8592a0d4e2cf6c65ad2c39a990093d35 (diff) | |
| download | vyos-documentation-4e7fa1b0b8b0e86d7b8483ab3440f3ed14130ba8.tar.gz vyos-documentation-4e7fa1b0b8b0e86d7b8483ab3440f3ed14130ba8.zip | |
netflow: use asterisk on list
Diffstat (limited to 'docs/system/flowaccounting.rst')
| -rw-r--r-- | docs/system/flowaccounting.rst | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/system/flowaccounting.rst b/docs/system/flowaccounting.rst index a3ec5248..0c796f92 100644 --- a/docs/system/flowaccounting.rst +++ b/docs/system/flowaccounting.rst @@ -7,13 +7,11 @@ can determine things such as the source and destination of traffic, class of service, and the causes of congestion. A typical flow monitoring setup (using NetFlow) consists of three main components: -- Flow exporter: aggregates packets into flows and exports flow records towards +* Flow exporter: aggregates packets into flows and exports flow records towards one or more flow collectors - -- Flow collector: responsible for reception, storage and pre-processing of flow +* Flow collector: responsible for reception, storage and pre-processing of flow data received from a flow exporter - -- Analysis application: analyzes received flow data in the context of intrusion +* Analysis application: analyzes received flow data in the context of intrusion detection or traffic profiling, for example For connectionless protocols as like ICMP and UDP, a flow is considered complete |