For the complete documentation index, see llms.txt. This page is also available as Markdown.

Multiple Kafka broker groups

Introduced in ASN 2.5

Overview

ASN 2.5 introduces support for multiple Kafka broker groups, allowing session metadata to be exported simultaneously to up to six independent Kafka broker groups. This enhancement improves deployment flexibility by enabling parallel data distribution for redundancy, disaster recovery, analytics, and integration with multiple downstream systems.

Each broker group can be configured independently using dedicated configuration parameters.

Configuration

The following configuration parameters are introduced:

  • kafka_server_config_1

  • kafka_server_config_2

  • kafka_server_config_3

  • kafka_server_config_4

  • kafka_server_config_5

  • kafka_server_config_6

A broker group is considered active when:

  • A valid broker address is configured.

  • The corresponding Kafka producer is successfully initialized.

At least one broker group must be configured for Kafka export to remain enabled.

Export behavior

ASN replicates every exported session record to all active Kafka broker groups.

The following metadata is exported simultaneously to each configured broker group:

  • User session data

  • Control session data

  • PFCP session data

  • Diameter session data

  • RADIUS session data

  • Priority exports for User, Control, and Diameter sessions

Each broker group operates independently. Exports continue if one or more groups become unavailable.

Backward compatibility

The legacy kafka_server_config parameter is no longer supported.

Deployments must migrate to the new broker group configuration parameters (kafka_server_config_1 through kafka_server_config_6).

A broker group is active when its configured address is non-empty and its Kafka producer initializes successfully.

Last updated