Aviz Networks details multi-destination network data export
Aviz Service Node now supports simultaneous export of real-time session and flow data to multiple Kafka clusters and IPFIX collectors, with up to six destinations of each type. The update is aimed at enterprise network teams that need parallel delivery for security, analytics, compliance, and operations without changing existing export paths.
Research Overview
The blog describes network environments where the same session records must be shared across several teams and systems at once. It says ASN exports millions of records each day, including user, control, PFCP, RADIUS, Diameter, and priority-event data used for subscriber analytics, monitoring, and reporting.
It also notes that a single export destination can become difficult to manage when multiple consumers need the same data stream. The example use cases include security analytics, performance monitoring, fraud detection, customer-specific Kafka clusters, and regulatory reporting.
Product Update
ASN can publish session and flow data to up to six Kafka clusters and up to six IPFIX collectors at the same time. The blog says this is centrally managed and does not require external replication tools or added infrastructure.
The product also keeps each destination separate from the others. A failure, maintenance window, or credential rotation in one destination does not stop exports to the remaining destinations unless all configured destinations fail.
Technical Breakdown
For Kafka, each cluster keeps its own configuration, and clusters that are set up the same way receive the same stream in parallel. The blog says teams can add a new cluster, retire an older one, or change broker addresses without interrupting delivery to other destinations.
The same model applies to IPFIX export. ASN can send session and flow data to multiple collectors in real time using RFC 7011 templates, with an export interval and metadata selection that are independent from Kafka export.
Operational Impact
The blog frames the feature as a way to support separate operational domains without forcing them to share one pipeline. It says this can reduce conflicts between analytics, security, compliance, and customer environments when each group needs the same data.
It also emphasizes zero-downtime reconfiguration. Configuration updates describe the full desired state for each destination, which the blog says helps keep changes predictable and limits ambiguity about what changed.
Leadership Perspective
The article positions multi-destination export as a response to growing demand for the same network data in more than one place. It says the approach lets service providers and operators keep production exports running while testing new clusters or adding new consumers.
For enterprise decision-makers, the update centers on continuity, independent destination management, and the ability to distribute session data without replacing existing exports. This Blog Signals brief is a fact-based summary of the vendor blog.