pmacct/pmacct

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

1237 stars · 283 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

pmacct is a set of multi-purpose passive network monitoring daemons written in C that collect, aggregate, replicate and export IP traffic accounting data via libpcap, NetFlow, IPFIX, sFlow, NFLOG, plus control-plane data from BGP, BMP, RPKI, IGP and Streaming Telemetry. It stores results in SQL/noSQL databases, Kafka, RabbitMQ, memory tables or flat files, and can enrich flow data with BGP correlation.

Use cases

• collect and account NetFlow and IPFIX flows from routers
• capture sFlow samples from switches
• correlate NetFlow data with BGP information
• store traffic accounting data in MySQL or PostgreSQL
• export flows to Kafka or RabbitMQ for downstream analytics
• monitor BGP peers and dump routing tables
• collect streaming telemetry from network devices
• replicate flow exports to multiple collectors

When to choose

• you need ISP/IXP/CDN-grade passive traffic accounting and flow collection
• you want to correlate data-plane flows with BGP/BMP control-plane data
• you need flexible export to databases, Kafka, AMQP or flat files
• you run Linux/BSD servers or embedded network appliances

When to avoid

• you need a GUI dashboard or turnkey network monitoring suite like Nagios or Zabbix
• you only need simple packet sniffing without aggregation (use tcpdump or Wireshark)
• you want active probing or synthetic traffic monitoring

Facets

application · maturity active

monitoring analytics streaming search-engine networking monitoring security big-data bsd cli self-hosted netflow ipfix sflow bgp bmp rpki streaming-telemetry traffic-accounting network-monitoring kafka libpcap linux docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="pmacct/pmacct")