pmacct
pmacct.net
- Free plan
- Linux
- Self-hosted
What pmacct is
pmacct is a free, self-hosted set of passive network monitoring tools for Linux. It collects traffic through NetFlow, IPFIX, sFlow and libpcap, while separate daemons handle BGP, BMP, RPKI, IGP and Streaming Telemetry data. The tools can replicate, export, filter, sample, renormalize, tag, classify and aggregate information, including at layer 7. Traffic may be kept in memory, relational or NoSQL databases, flat files, or sent to AMQP and Kafka brokers. Documented destinations include MySQL/MariaDB, PostgreSQL, SQLite, BerkeleyDB, MongoDB, Elasticsearch, InfluxDB, Druid and ClickHouse. Output can use tab-spaced text, CSV, JSON or Apache Avro, and the command-line client can query memory tables. Official Docker images cover seven daemons for linux/amd64 and experimental linux/arm64. SQL, AMQP and Kafka plugins require compile-time support. The project also documents Docker Compose, Kubernetes, configuration references, examples and troubleshooting guidance.
Who it suits
pmacct suits Linux users who need self-hosted traffic accounting, classification, aggregation or export. It can support deployments using databases, message brokers, Docker or Kubernetes.
Good to know, and what to watch
- Free plan for Linux and self-hosted deployment
- Collects NetFlow, IPFIX, sFlow, BGP and telemetry
- Layer 7 filtering, sampling, tagging and classification
- Supports databases, flat files, AMQP and Kafka
- Offers CSV, JSON, text and Apache Avro output
- SQL, AMQP and Kafka plugins disabled by default
- Arm64 Docker support is marked experimental
- Storing every flow can increase resource use
- Memory plugin targets prototypes and smaller environments
The verdict
pmacct provides broad protocol collection and configurable traffic processing for self-hosted Linux setups. Its plugin requirements and resource guidance matter when planning production-scale retention.
What the maker publishes
- Build requirements
- The quickstart says libpcap and its headers are the package’s only dependency, while SQL, AMQP and Kafka plugins are disabled by default. source
- Collection and processing
- It can collect, replicate and export network information, and aggregate, filter, sample, renormalize, tag and classify traffic at layer 7. source
- Command line client
- The pmacct client can query memory-table data and format output as text, CSV, or JSON. source
- Configuration limit
- SQL, AMQP, and Kafka plugins are disabled by default and require their support to be enabled at compile time. source
- Container platforms
- Official Docker images are built for linux/amd64 and linux/arm64, with arm64 support marked experimental. source
- Data destinations
- The project documents output to MySQL, PostgreSQL, SQLite, flat files, AMQP, and Kafka. source
- Deployment
- The project provides official Docker images for seven daemons and documents use with Docker Compose and Kubernetes. source
- Deployment
- The project provides official Docker images and build instructions for Debian or Ubuntu and CentOS or RHEL. source
- Documentation
- The repository links to a wiki and includes a quickstart, FAQ, configuration key reference, examples and SQL documentation. source
- Integrations
- The documentation names MySQL/MariaDB, PostgreSQL, SQLite, BerkeleyDB, MongoDB, RabbitMQ, Kafka, Elasticsearch, InfluxDB, Druid and ClickHouse among supported storage or consumer options. source
- Message consumers
- The documentation names Elasticsearch, InfluxDB, Druid, and ClickHouse as examples of systems that can consume data through messaging brokers. source
- Output formats
- The print plugin supports tab-spaced, CSV, and JSON output, and the documentation also describes Apache Avro output. source
- Product
- pmacct is a set of passive network monitoring tools for NetFlow, IPFIX, sFlow, libpcap, BGP, BMP, RPKI, IGP and Streaming Telemetry. source
- Protocols
- Its tools collect or export traffic using NetFlow, IPFIX and sFlow; separate daemons collect BGP, BMP and Streaming Telemetry data. source
- Protocols
- Its tools cover NetFlow, IPFIX, sFlow, libpcap, BGP, BMP, RPKI, IGP, and Streaming Telemetry. source
- Purpose
- pmacct is a set of passive network monitoring tools for accounting, classifying, aggregating, and exporting network traffic. source
- Resource considerations
- The FAQ cautions that storing every flow can increase CPU, memory and disk use and recommends planning resources for that level of detail. source
- Scale guidance
- The documentation says the memory plugin is intended for prototyping, lab use without mass traffic generation, and smaller or home production environments. source
- Scaling
- The FAQ says deployments can scale through aggregation, filtering, sampling and tagging, or by distributing input across multiple pmacct instances. source
- Security information
- The opened project pages describe collection and output capabilities but do not state security certifications or compliance attestations. source
- Storage and output
- Traffic data can be stored in memory, relational or NoSQL databases, and flat files, or published to AMQP and Kafka brokers. source
- Support and documentation
- The project points users to online GitHub wiki pages and documentation included in the distribution, including a quickstart and FAQ. source
- Support and troubleshooting
- The Docker documentation provides troubleshooting guidance and says bug reporters may be asked to provide debugging information. source
- Traffic processing
- Traffic data can be filtered, sampled, tagged, classified, and aggregated using configurable primitives. source
Checked against the maker's pages on 4 Oct 2026.