nanog mailing list archives

Re: Flow collection and analysis


From: David Bass <davidbass570 () gmail com>
Date: Tue, 25 Jan 2022 14:04:52 -0400

Most of these things, yes.

Add:
Troubleshooting/operational support
Customer reporting




On Tue, Jan 25, 2022 at 1:38 PM Christopher Morrow <morrowc.lists () gmail com>
wrote:



On Tue, Jan 25, 2022 at 10:53 AM David Bass <davidbass570 () gmail com>
wrote:

Wondering what others in the small to medium sized networks out there are
using these days for netflow data collection, and your opinion on the tool?


a question not asked, and answer not provided here, is:
  "What are you actually trying to do with the netflow?"

Answers of the form:
  "Dos detection and mitigation planning"
  "Discover peering options/opportunities"
  "billing customers"
  "traffic analysis for future network planning"
  "abuse monitoring/management/investigations"
  "pretty noc graphs"

are helpful.. I'm sure other answers would as well.. but: "how do you
collect?" is "with a collector" and isn't super helpful if the collector
can't feed into the tooling / infrastructure / long-term goal you have.


Current thread: