> If there would be a new NfSen incarnation, I would write it in Golang as it provides far more flexibility and speed.
Should there be a rewrite, I'd like to ask to preserve the backend plugin API (or at least make a wrapper for it), so that we can reuse our old backend plugins (like this: https://github.com/mad-ady/nfsen-prefixStats). Sure, a lot needs to be rewritten, but until there is time to rewrite stuff it's better to reuse when possible. Backend plugins should also be run as threads (currently they are sequential). Also, a +1 for some prometheus exporter of netflow statistics. This is doable right now - with a custom exporter that runs queries via nfdump, but it may be slow if there are a lot of queries, so aggregating data based on user filters at collection time and exposing prometheus metrics from it might be tons more efficient. I like nfsen because it scales, it has an intuitive filter syntax (ok, it's intuitive because I've been using it for almost 15 years now) and it's free! What's not to like? Cheers! On Thu, Aug 19, 2021 at 9:39 AM Brian Candler <b.cand...@pobox.com> wrote: > On 19/08/2021 07:35, Alfredo Sola wrote: > > Perhaps this chap has a fair idea of what the GUI could look like, > although the backend (at least the last time I checked it out) is hacky: > https://github.com/mbolli/nfsen-ng > > In my opinion, that UI is terrible. I tried *very* hard to like it. In > my home network I have nfsen-ng and nfsen installed alongside each other, > and I always go back to nfsen. > _______________________________________________ > Nfsen-discuss mailing list > Nfsen-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfsen-discuss >
_______________________________________________ Nfsen-discuss mailing list Nfsen-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
