A high-performance, scalable, and reliable enterprise network flow collector for IPFIX, sFlow, and Netflow protocols.
vFlow is an open-source, high-performance network flow collector that ingests and decodes IPFIX, sFlow, and Netflow data from routers, switches, and other network devices. It transforms raw flow data into structured JSON format, enabling real-time network traffic analysis, monitoring, and security insights for enterprise networks.
Network engineers, DevOps teams, and SREs managing large-scale network infrastructures who need scalable flow data collection for monitoring, troubleshooting, and security analysis.
Developers choose vFlow for its pure Go implementation, which ensures high concurrency and low resource usage, along with support for multiple flow protocols and flexible data export options like Kafka and Prometheus integration.
Enterprise Network Flow Collector (IPFIX, sFlow, Netflow)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Collects and decodes IPFIX, sFlow v5, Netflow v5, and v9, covering major network flow standards for comprehensive data ingestion from diverse devices.
Written in pure Go, it leverages concurrency to handle high-volume flow data efficiently, as emphasized in its philosophy for enterprise-scale workloads.
Exports decoded JSON flow data to Apache Kafka, NSQ, or NATS, enabling seamless integration with real-time processing pipelines and third-party collectors.
Provides Prometheus metrics and RESTful APIs for monitoring, allowing easy incorporation into existing observability stacks without additional tooling.
Requires manual editing of vflow.conf and mq.conf files, with documentation that assumes familiarity with specific technologies like NSQ, making initial deployment non-trivial.
Lacks a graphical interface; users must rely on external tools like Grafana or custom dashboards for data visualization, adding to the integration effort.
Only supports export to Kafka, NSQ, or NATS, forcing teams to adapt their infrastructure or build custom adapters for other messaging systems or databases.