IPFIX Collector

IPFIXcol is a plugin-based framework for collecting, processing, and storing IPFIX (IP Flow Information Export) flow records from network devices.

  • Monitoring & Logging
  • Network Services
IPFIXcol is a plugin-based framework for collecting, processing, and storing IPFIX (IP Flow Information Export) flow records from network devices. It lets network engineers and homelab admins verify that flow data from switches, routers, and other network gear exports correctly into a structured format for monitoring and troubleshooting.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

30/100 Low

Maintained
0last commit 2448 days ago
Popular
3766 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
85no serious findings, tests
GitHub stars
66
Open issues
8
Last commit
2020-03-09
Latest release
v0.9.5
Activity
stale

Checked 3 days ago - source: GitHub (CESNET/ipfixcol)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point the IPFIX output to a real folder Set the `filename` setting to a directory the collector can write to, such as `/tmp/ipfix/...`. If that folder doesn't exist or permissions are wrong, the collector may start but won't be able to save your flow files (files containing network-flow records). source
  • Check the input file path first Set the `path` setting to the exact location of the flow file you want to process. If it points to the wrong file or a folder, the collector may run but produce no records. source
  • Use the viewer plugin to test output Add the viewer output plugin with no parameters if you want a simple test screen. It shows what the collector sees, so blank output usually means the input or data source isn't connected. source

Fetched 43 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should users do if they are running the original IPFIXcol framework?

Users should consider upgrading to IPFIXcol2, because the original framework is no longer supported. The rewrite also means some plugins may not be available.

Where can IPFIXcol store collected flow data?

Storage plugins can write data to FastBit, FastBit with compression, JSON, nfdump files, PostgreSQL, RRD-backed statistics, or UniRec.

Can IPFIXcol read existing nfdump files?

Yes, the external nfdump input plugin reads NFDUMP files.

What flow metadata can IPFIXcol add with intermediate plugins?

It can add country codes, profile and channel information, per-profile/channel statistics, per-ODID statistics, and user identity.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads