@@ -167,17 +167,17 @@ Example configuration files
167167In this section you can see various example configuration files that demonstrate possibilities
168168of IPFIXcol. Always keep in mind that you should modify a configuration to fit you needs.
169169
170- :`udp2json <TODO >`_:
170+ :`udp2json <../data/configs/udp2json.xml >`_:
171171 Receive flow data over UDP, convert them into JSON and provide them as a server on local port.
172- :`tcp2anon2json <TODO >`_:
172+ :`tcp2anon2json <../data/configs/tcp2anon2json.xml >`_:
173173 Receive flow data over TCP, anonymize them and store in JSON format on a local drive.
174- :`tcpUdp2lnf <TODO >`_:
174+ :`tcpUdp2lnf <../data/configs/tcpUdp2lnf.xml >`_:
175175 Receive flow data simultaneously over TCP and UDP and store them on a local drive in
176- a nfdump compatible format (multiple instances of the same input plugin ).
177- :`odidFilter <TODO >`_:
178- Receive flow data over TCP and store flows from different ODIDs to different locations
176+ a nfdump compatible format (multiple instances of input plugins ).
177+ :`odidFilter <../data/configs/odidFilter.xml >`_:
178+ Receive flow data over UDP and store flows from different ODIDs to different locations
179179 (multiple instances of the same output plugin).
180- :`multiOutput <TODO >`_:
180+ :`multiOutput <../data/configs/multiOutput.xml >`_:
181181 Receive flow data over TCP and store them in a nfdump compatible format on a local drive
182182 and simultaneously send to a remote host as JSON.
183183
@@ -198,10 +198,11 @@ increasing verbosity level to see also warning messages (parameter "``-v``") dur
198198 Note: Receiving flow data from an exporter *over UDP transport
199199 protocol * may lead due to IPFIX protocol structure to a situation when the collector
200200 is unable to interpret data immediately after start.
201- For more information, see documentation of `UDP <TODO >`_ plugin.
201+ For more information, see documentation of `UDP <../../src/plugins/input/udp >`_ plugin.
202202
203203We prepared a file with few anonymized IPFIX flows, so you can try your configurations,
204- even without running a flow exporter. Just download the `file <TODO >`_ and use ``ipfixsend2 `` tool
204+ even without running a flow exporter. Just download the `file <../data/ipfix/example_flows.ipfix >`_
205+ and use ``ipfixsend2 `` tool
205206(distributed and installed together with IPFIXcol). For example, to send flow records over UDP
206207protocol with real-time simulation use:
207208
@@ -254,8 +255,12 @@ shown below. The same approach applies to other types of instances too.
254255
255256 Available verbosity levels:
256257
257- :none: Hide all messages
258- :error: Show only error messages (i.e. something went really wrong)
259- :warning: Show error and warning messages (i.e. something is not right, but an action can continue)
260- :info: Show all previous types of messages and informational (status) messages
261- :debug: Show all types of messages (i.e. include messages interesting only for developers)
258+ =========== =========================================================================================
259+ Verbosity Description
260+ =========== =========================================================================================
261+ ``none `` Hide all messages
262+ ``error `` Show only error messages (i.e. something went really wrong)
263+ ``warning `` Show error and warning messages (i.e. something is not right, but an action can continue)
264+ ``info `` Show all previous types of messages and informational (status) messages
265+ ``debug `` Show all types of messages (i.e. include messages interesting only for developers)
266+ =========== =========================================================================================
0 commit comments