From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Open source Netflow analysis for monitoring AS-to-AS traffic
Date: Sat, 8 Jun 2024 19:53:39 -0700 [thread overview]
Message-ID: <CAA93jw4f1hcV7w5tg+PxOGHd-_e77R12gO-Y+1ROQ3AbtZr5zQ@mail.gmail.com> (raw)
In-Reply-To: <3939566c-c4e2-4e94-969d-cd41dd8c89ce@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2718 bytes --]
Yes, according to nanog this is popular.
---------- Forwarded message ---------
From: Marinos Dimolianis <dimolianis.marinos@gmail.com>
Date: Wed, Mar 27, 2024, 4:11 PM
Subject: Re: Open source Netflow analysis for monitoring AS-to-AS traffic
To: Andrew Hoyos <hoyosa@gmail.com>, Brian Knight <ml@knight-networks.com>
Cc: North American Operators' Group <nanog@nanog.org>
Brian,
I have used Akvorado in an environment with ~80G of traffic and I was super
happy.
It can be easily set via a docker-compose file and amongst its key benefits
is the user-friendly UI that allows you to gain insight into your network
traffic.
There is also a demo instance available to find out what to expect:
https://demo.akvorado.net/
My only "concern" was that it did not provide an API for consuming data
externally.
- Marinos
On 3/27/2024 2:55 AM, Andrew Hoyos wrote:
Brian,
Take a peek at Akvorado - https://github.com/akvorado/akvorado
We recently set up a lab instance, and seems to check the boxes below.
On Mar 26, 2024, at 19:04, Brian Knight via NANOG <nanog@nanog.org>
<nanog@nanog.org> wrote:
What's presently the most commonly used open source toolset for monitoring
AS-to-AS traffic?
I want to see with which ASes I am exchanging the most traffic across my
transits and IX links. I want to look for opportunities to peer so I can
better sell expansion of peering to upper management.
Our routers are mostly $VENDOR_C_XR so Netflow support is key.
In the past, I've used AS-Stats <https://github.com/manuelkasper/AS-Stats>
for this purpose. However, it is particularly CPU and disk IO intensive.
Also, it has not been actively maintained since 2017.
InfluxDB wants to sell me
<https://www.influxdata.com/what-are-netflow-and-sflow/> on Telegraf +
InfluxDB + Chronograf + Kapacitor, but I can't find any clear guide on what
hardware I would need for that, never mind how to set up the software. It
does appear to have an open source option, however.
pmacct seems to be good at gathering Netflow, but doesn't seem to analyze
data. I don't see any concise howto guides for setting this up for my
purpose, however.
I'm aware Kentik does this very well, but I have no budget at the moment,
my testing window is longer than the 30 day trial, and we are not prepared
to share our Netflow data with a third party.
Elastiflow <https://www.elastiflow.com/> appears to have been open source
<https://github.com/robcowart/elastiflow?tab=readme-ov-file> at one time in
the past, but no longer. Since it too appears to be hosted, I have the same
objections as I do with Kentik above.
On-list and off-list replies are welcome.
Thanks,
-Brian
[-- Attachment #2: Type: text/html, Size: 6074 bytes --]
next prev parent reply other threads:[~2024-06-09 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a172a45cd1896e1a69ce3d6063b0e09f@mail.knight-networks.com>
2024-06-08 18:52 ` Dave Taht
2024-06-09 0:38 ` Hayden Simon
[not found] ` <081FB299-A2AF-44F5-B534-1ACEDBC17040@gmail.com>
[not found] ` <3939566c-c4e2-4e94-969d-cd41dd8c89ce@gmail.com>
2024-06-09 2:53 ` Dave Taht [this message]
[not found] ` <999d91a84220961140c60df66336b47e@mail.knight-networks.com>
2024-06-09 2:55 ` [LibreQoS] " Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4f1hcV7w5tg+PxOGHd-_e77R12gO-Y+1ROQ3AbtZr5zQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox