Flow collection and analysis
David Bass
davidbass570 at gmail.com
Tue Jan 25 18:04:52 UTC 2022
Most of these things, yes.
Add:
Troubleshooting/operational support
Customer reporting
On Tue, Jan 25, 2022 at 1:38 PM Christopher Morrow <morrowc.lists at gmail.com>
wrote:
>
>
> On Tue, Jan 25, 2022 at 10:53 AM David Bass <davidbass570 at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220125/9cd54929/attachment.html>
More information about the NANOG
mailing list