# Edgio/vflow

Enterprise Network Flow Collector (IPFIX, sFlow, Netflow)

Repository: https://github.com/Edgio/vflow
Canonical: https://ross.abutalabs.com/products/edgio-vflow
Homepage: http://www.verizonmedia.com
Language: Go
License: Apache-2.0
License Family: permissive
Topics: network, ipfix, sflow, golang, juniper, cisco, ipv4, ipv6, netflow, kafka, monitoring, kubernetes
Last push: 2024-08-22T13:29:15+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3477, "days_push": 741, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1155, forks 231 (observed 2026-08-28T04:03:47.892796+00:00)

## What it is
vFlow is a high-performance, scalable network flow collector written in pure Go that ingests IPFIX (RFC7011), sFlow v5, and Netflow v5/v9 telemetry from network devices. It decodes flow records to JSON and publishes them to Apache Kafka, NSQ, or NATS, with Prometheus and REST API monitoring built in.

## Use cases
- collect netflow data from cisco and juniper routers
- ingest ipfix flow records and export to kafka
- monitor network traffic with sflow collector
- analyze ipv4 and ipv6 flow telemetry at scale
- replicate ipfix and sflow streams to third-party collectors
- build network traffic analytics pipeline in golang

## When to choose
- you need a pure-Go, high-throughput collector for IPFIX, sFlow, or Netflow v5/v9
- you want decoded JSON flow data streamed into Kafka, NSQ, or NATS
- you run Juniper/Cisco gear and need Prometheus-based flow monitoring
- you need IPv4 and IPv6 support with flow replication to downstream collectors

## When to avoid
- you need a full network analysis UI with dashboards and packet capture rather than a collector
- your devices export protocols other than IPFIX, sFlow, or Netflow v5/v9
- you want a managed SaaS flow analytics solution instead of self-hosted infrastructure

## Facets
- artifact type: service
- maturity: active
- function: monitoring, streaming, analytics, message-queue
- domain: networking, monitoring, big-data, analytics
- platform: go, self-hosted
- tags: netflow, ipfix, sflow, flow-collector, kafka, nats, nsq, prometheus, network-telemetry, traffic-analysis, linux, docker, kubernetes

## Member repositories
- Edgio/vflow (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:47.892796+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:32:10.319706+00:00, confidence not recorded.
  - readme: https://github.com/Edgio/vflow (fetched 2026-08-28T04:03:47.892796+00:00, sha 55c813a822c7)
  - homepage: http://www.verizonmedia.com (fetched 2026-08-29T12:37:26.029309+00:00, sha b861e55dbc7a)
  - site_page: https://www.yahooinc.com/contact (fetched 2026-08-29T12:37:26.038483+00:00, sha 94fb2ae658ed)
  - site_page: https://www.yahooinc.com/press (fetched 2026-08-29T12:37:26.040370+00:00, sha 70c55ff6f55c)
- Data as of 2026-08-30T08:39:29.467469+00:00.