akvorado VS udp-replicator

i recently started using:https://github.com/akvorado/akvorado - very happy about it.

I played with Elastiflow extensively some years ago - it was excellent, if a little hungry on memory, but I suspect most of that was the logstash & elasticsearch overhead.

Rob did a big rewrite about 4 years ago, I think, licensing the new codebase in a way that led us to look elsewhere.

There's some alternatives that aren't elastic under the hood, of course. The hard-to-type Akvorado looks very promising, especially given its heritage:

https://github.com/akvorado/akvorado

Because we're moving to opentel / prometheus, this project (seems quite active) is especially interesting, with the promise of integrating OS & app metrics, tracing, and netflow insights:

https://github.com/netobserv/flowlogs-pipeline

I'm trying to deploy Akvorado, this has gone fine in my home lab. However I'm struggling to make this work in my work's lab and it's something we are keen to get working.

Akvorado is a flow collector for Netflow/IPFIX and sFlow that enriches the data with interface names and geo information, and then exports the results or lets you browse them via a web interface. Kindly suggested by brynx97.

I would look at https://github.com/akvorado/akvorado.

Akvorado, a free and opensource flow collector, developed by Vincent Bernat (Free)

I would also suggest Akvorado as an open source alternative.

If you need to split your existing netflow stream between FastNetMon and nfdump, try UDP replicator. This will take an inbound UDP flow and forward it to N destinations. Alternatively, create a subnet for your flow receivers on your network somewhere, set the destination of your netflow traffic to the broadcast address of the subnet, and place your collectors like nfdump and FastNetMon inside that. (Note: not all software supports receiving netflow data sent to the broadcast.)