Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Hayden Simon <h@uber.nz>
To: Dave Taht <dave.taht@gmail.com>,
	libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Fwd: Open source Netflow analysis for monitoring	AS-to-AS traffic
Date: Sun, 9 Jun 2024 00:38:38 +0000	[thread overview]
Message-ID: <TYZPR03MB828210A4FEE55D95473C60CDA8C52@TYZPR03MB8282.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <CAA93jw5MePRoMeTcQ-6+NWJ6uNbG+cXepLoemYA5mNN+nR88Ew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2768 bytes --]

We run Akvorado (which has its own interface, but can also interface with Grafana.

Depending on the level of traffic you are doing it is pretty hungry though – we recently moved ours to bare metal.

Hope that helps?

HAYDEN​​​​ SIMON
UBER GROUP LIMITED
MANAGING DIRECTOR
[https://uber.nz/app/uploads/signatures/uber-facebook-icon.png]<https://www.facebook.com/UberGroup?_rdr=p>
[https://uber.nz/app/uploads/signatures/uber-twitter-icon.png]<https://twitter.com/ubergroupltd>
E: h@uber.nz<mailto:h@uber.nz>
M: 021 0707 014<tel:021%200707%20014>
W: www.uber.nz<http://www.uber.nz/>
53 PORT ROAD | PO BOX 5083 | WHANGAREI | NEW ZEALAND





From: LibreQoS <libreqos-bounces@lists.bufferbloat.net> On Behalf Of Dave Taht via LibreQoS
Sent: Sunday, June 9, 2024 6:53 AM
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Open source Netflow analysis for monitoring AS-to-AS traffic


---------- Forwarded message ---------
From: Brian Knight via NANOG <nanog@nanog.org<mailto:nanog@nanog.org>>
Date: Tue, Mar 26, 2024, 5:06 PM
Subject: Open source Netflow analysis for monitoring AS-to-AS traffic
To: <nanog@nanog.org<mailto:nanog@nanog.org>>

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: 15929 bytes --]

  reply	other threads:[~2024-06-09  0:38 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 [this message]
     [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
     [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=TYZPR03MB828210A4FEE55D95473C60CDA8C52@TYZPR03MB8282.apcprd03.prod.outlook.com \
    --to=h@uber.nz \
    --cc=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