P1

pmacct 1.7.9 NetFlow, sFlow and IPFIX Network Traffic Accounting Collector on Ubuntu 24.04 LTS

Azure Networking

pmacct is a network traffic accounting collector that ingests NetFlow, sFlow and IPFIX from your routers and switches, aggregates each flow by source, destination, port, protocol and autonomous system, and writes the results to a database you can query.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

pmacct is a mature, widely deployed suite of network traffic accounting tools. Its collector daemon receives flow exports, NetFlow v5 and v9, IPFIX and sFlow, from the routers, switches and firewalls on your network, and it can also account traffic directly from a captured interface. Every flow is aggregated in memory by the primitives you choose, such as source and destination host, source and destination port, IP protocol and source and destination autonomous system, and the running totals of packets and bytes are periodically written out to a backend. That turns a firehose of raw flow records into compact, queryable accounting: who talked to whom, over which ports and protocols, and how much traffic each conversation carried. It is the engine many organisations use for capacity planning, traffic engineering, peering analysis, billing and security investigation, without sending any of the data to a third party.

Why the cloudimg image

cloudimg ships pmacct wired up to a PostgreSQL database already installed alongside it on the same instance, so the collector has somewhere to write aggregated accounting from the moment first boot finishes, with no external database to stand up. A lightweight flow generator is also bundled and pointed at the collector on the loopback interface, so the appliance is genuinely accounting its own traffic out of the box and you can prove the pipeline works before you point a single router at it. It is secure by default: the only port open to the network is the flow collector port that your routers export to, while the database is bound to the loopback interface and reachable only from the instance itself, protected by a credential generated uniquely on each instance at first boot and stored in a root only file, so no password is ever baked into the image or shared between customers. The base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide, backed by 24/7 cloudimg support.

Common uses

  • Collect NetFlow, sFlow and IPFIX from routers and switches in one place
  • Aggregate traffic by source, destination, port, protocol and AS number
  • Feed per host and per conversation accounting into a SQL database for analysis